P. 1
Online Shopping

Online Shopping

|Views: 76|Likes:
Published by rv0000s
software engineering project on online shopping.
software engineering project on online shopping.

More info:

Categories:Types, School Work
Published by: rv0000s on Feb 10, 2013
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less






  • 3.2 Scope:
  • 3.3 Need for the proposed system:
  • 3.4.1 Technical Feasibility:
  • 3.4.2 Financial Feasibility:
  • 3.4.3 Operational Feasibility:
  • 4.1 User Class and Characteristics:
  • 4.3 Performance Requirements:
  • 4.4 Non Functional Requirements:
  • 4.5.1 User Interface:
  • 4.5.2 Hardware Interface:
  • 4.5.3 Software Interface:-
  • 4.5.4 Communication Interfaces
  • 4.6.1 General Constraints
  • 4.6.2 Assumptions and Dependencies
  • 5.1. 2. DATABASE DESIGN:
  • 6.1 Unit Testing:
  • 6.2 Integration Testing
  • 6.3 Validation testing
  • 7.Software Quality Assurance Plan
  • 8. Problem reporting and corrective action
  • 9. Tools, techniques and methodologies:
  • 10. Code Control:
  • 11. Media Control:
  • 12. Supplier Control:
  • 13. Records collection, maintenance and retention:

Project Report For Completion Of 4 th Semester Mini Project

ONLINE SHOPPING for Department of Computer Applications, CUSAT

Submitted By:MAITREYEE 4th semester,Reg No-95580020 DEPARTMENT OF COMPUTER APPLICATIONS, cusat


This is to certify that the project entitled

--ONLINE-SHOPPING-- submitted to Cochin University of Science and Technology in partial fulfillment of the requirements for the award of the degree of Master of Computer Applications is the bona fide record of the project work

done by ----MAITREYEE-------------------- under our supervision and guidance during ------------------- to -----------------.

Signature of Internal Guide Name and Designation

Signature of External Guide Name and Designation

Head of Department Official Address

Internal Examiner

External Examiner


The satisfaction and euphoria that accompany the successful completion of any task would be incomplete without mentioning the names of people who made it possible, whose constant guidance and encouragement crowns all efforts with our success. I extend my gratitude to Dr. K.V. Pramod, Head- Department of Computer Applications, Cochin University of Science and Technology, Kochi, Kerala for providing me with excellent infrastructure and awesome environment that laid potentially strong foundation for my professional life. I would like to express my profound thanks to Mr. A. SreeKumar, who guided me through out the project tenure, provided me each and every details, references, and technical helps without which it was impossible to complete this project. I am also thankful to Professor Dr. B. Kannan, and Mrs. S. Malathi for their help and guidance throughout my project future. Finally. I also wish to thank all guest faculties and non-teaching staffs for supporting me during my whole project work.



Title Student’s Name Venue of the Project Duration Platform Application Software Front End Back End : : JSP MYSQL : ONLINE SHOPPING : MAITREYEE : DCA, CUSAT : 4 months : Windows XP/Vista/7


1. Introduction 2. System Study 2.1 2.2 Existing System Drawbacks in the Existing System

3. System Analysis 3.1 Proposed System 3.2 Scope 3.3 Need for the Proposed System 3.4 Feasibility Study 3.4.1 Technical Feasibility 3.4.2 Financial Feasibility 3.4.3 Operational Feasibility 4. Requirement Analysis 4.1 User Class and Characteristics 4.2 Functional Requirements 4.3 Performance Requirements 4.4 Non Functional Requirements 4.5 External Interfaces Requirements 4.6 General Constraints, Assumptions, Dependencies, Guidelines


Scope for further development Bibliography 6 .1.1. Testing 7. System Design Specification 5.1 Data Flow Diagrams 5. Conclusion 10. Output Screen Output of Pages 9. Architectural Design 5.2 Database Tables 5. Software Quality Assurance Plan 8.3 User Case Diagrams 6.

hardware. try on clothing. and walk throughout the store until she locates the products she needs. find a parking place. not everyone chooses to purchase items and services online. Some people like the idea of physically going to a store and experiencing the shopping process. from a seller interactively in real-time without an intermediary service over the internet. Online shopping is the process of buying goods and services from merchants who sell on the Internet. For example. Shoppers can visit web stores from the comfort of their homes and shop as they sit in front of the computer. Online shopping doesn't permit shoppers to touch products or 7 . Books. merchants have sought to sell their products to people who surf the Internet. After finding the items she wants to purchase.1. In fact. she may often need to stand in long lines at the cash register. and be around other people. clothing.Consumers buy a variety of items from online stores. and health insurance are just some of the hundreds of products consumers can buy from an online store. services etc. toys. when a person shops at a brick-and-mortar store. people can purchase just about anything from companies that provide their products online. They like to touch the merchandise.INTRODUCTION Online shopping is the process whereby consumers directly buy goods. she has to drive to the store. Despite the convenience of online shopping. Since the emergence of the World Wide Web. Many people choose to conduct shopping online because of the convenience. software. household appliances.

online. It also doesn't allow them to take the merchandise home the same day they buy it. Shopping via the internet eliminates the need to sift through a store's products with potential buys like pants. If you're searching for a niche product that may not be distributed locally. you're sure to find what you're looking for on the internet. You can search through multiple stores at the same time. Online shopping also eliminates the catchy. similar or not. as well as the hundreds. purchasing and shipping your merchandise. Say 'goodbye' to the days when you stood in line waiting. 8 . 7 days a week to assist you with locating. yet irritating music. if not thousands. shirts. of other like-minded individuals who seem to have decided to shop on the same day. and even offers merchandise that's unavailable in stores. sizes and pricing simultaneously. Online shopping transactions occur instantly-saving you time to get your other errands done! Additionally. belts and shoes all slung over one arm.have any social interaction. unlike a store. comparing material quality. What's even more useful is the ability to compare items. and waiting. Online shopping allows you to browse through endless possibilities. and waiting some more for a store clerk to finally check out your items. online shopping has friendly customer service representatives available 24 hours a day.

9 .2. The activity has three parts: request clarification. feasibility study and request approval 2. When the request is made. senior executives and systems analysis. integration of business areas. reduced cost and better security. better accuracy and improved consistency. begins.SYSTEM STUDY Information systems projects’ originate from many reasons: to achieve greater speed in processing data. But It was found to be inefficient in meeting the growing demands of population . the preliminary investigation. 2.1.1 Existing System: The existing system was an automated system. Sometimes the real origin is an outside source. the first systems activity. such as a government agency which stipulates a systems requiremetns the organisattion must meet.1 Drawbacks in the existing systems: Disadvantage of the existing system:  Time Consuming  Expensive  Needed an agent  We have to out for that. faster information retrieval. The sources also vary project proposals originate with department managers.

• Customer can buy products online after login to the site. • Both admin and customer can see the delivery report. • Administrator can edit or delete the products from the database. • sell at lower rate due to less over head. 10 . • 3. • Customer can write feedback for the product or services. • Administrator is adding the delivery report to the database.3.1 Purpose: Online shopping tries to enhance access to care and improve the continuity and efficiency of services. ranging from linking clients to services to actually providing intensive shopping and delivery services themselves Main objective • To shop wile in the comfort of your own home . • After buying and making payment the products are send to customers address that he has given. • Admin can see daily sell and feedback given by customer.without having to step out of the door. • provide home delivery free of cost. • No wait to see the products if someone else is taking that. case managers are responsible for a variety of tasks. • This system is all about the converting the shopping • system from manual to online. • Administrator is adding product to database.SYSTEM ANALYSIS . Depending on the specific setting and locale.

scalable. so that any unauthorized users can not use your account. which aims to answer a number of questions: 11 . Online shopping Internet software developed on and for the Windows and later versions environments and Linux OS. focused study.2 Scope: This product has great future scope. experience. Features and Benefits:  Providing security  Low cost  Basic computer knowledge required  Configurable and extensible application UI design The proposed system can be used even by the naïve users and it does not require any educational level.3 Need for the proposed system: The online shopping (HOME SHOP) is an easy to maintain. ready to run. 3. and technical expertise in computer field but it will be of good use if the user has the good knowledge of how to operate a computer. The only Authorized that will have proper access authority can access the software.3. and large shopping complex and shopping malls.4 Feasibility study: A feasibility study is a short. This project also provides security with the use of Login-id and Password. 3. medium. affordable and reliable cost saving tool from Software Associates suited for small.

schedule)? 3.2 Financial Feasibility:  Is the project possible. such as problems. including tangible and intangible ones?  What are the development and operational costs? 3.4. if the system is developed.1 Technical Feasibility:  Is the project feasibility within the limits of current technology?  Does the technology exist at all?  Is it available within given resource constraints (i..3 Operational Feasibility: Define the urgency of the problem and the acceptability of any solution. Does the system contribute to the overall objectives of the organizations?  Can the system be implemented using current technology and within given cost and schedule constrains?  Can the system be integrated with systems which are already in place? 3. will it be used? Includes people-oriented manpower and social labour issues: internal issues.4. 12 . objections.4. given resource constraints?  Are the benefits that will accrue from the new system worth the costs?  What are the savings that will result from the system. budget. manager resistance.e.

The Software requirement specification (SRS) is the official statement of what is required of the system developers. social acceptability. legal also external and issues. It specifies constraints on the implementation. SYSTEM REQUIREMENTS SPECIFICATIONS System requirements are expressed in a software requirement document. The requirement set out in this document is complete and consistent. The software specification document satisfies the following:1 2 3 4 5 6 It specifies the external system behaviors.organizational including regulations. It serves as reference tool for system maintainers. It is easy to change. It characterizes acceptable response to undesired events. It should set out what the system should do without specifying how it should be done. 13 . It record forethought about the life cycle of the system. The software requirement document is not a design document. conflicts and policies. aspects government 4. This requirement document includes the requirements definition and the requirement specification.

and provide services to the customer.1 User Class and Characteristics: There are 3 types of user of this software- 1. Administrators can add. General public can use the system to see the product. Customers are using for viewing and buying the products. 2. Customer can also write feedbacks for products and services 3. Administrator can see the daily sell.  4. Customers 3.their prices and quantity available.Administrator 1. General user can not buy the products. 14 .4.edit & delete products.2 Functional Requirements:  The System must provide following functionalities—  Keeping records of admission of customers. Administrator maintaining the deliveries. Can also see the the feedback given by the customer.  keeping the records of products.General public 2.

4 Non Functional Requirements: Following Non-functional requirements will be there in the Insurance on internet: i). and server will be working whole 24X 7 times. 4. etc. keeping details about the product it is delivered or not. Storing the items selected by the customer in the temporary storage. Secure access of confidential data (customer’s details). 4. Also connections to the servers will be based on the criteria of attributes of the user like his location. Storing the feedback given by the customer. 24 X 7 availability. ii). 15 .3 Performance Requirements: In order to maintain an acceptable speed at maximum number of uploads allowed from a particular customer will be any number of users can access the system at any time.     keeping the daily sell .

iv).5. 2. Flexible service based architecture will be highly desirable for future extension Non functional requirements constraints It arise through user needs. 5. Login page followed by Password 16 . Better component design to get better performance at peak time. because of budget constraints or organizational policies. 6. privacy registration and so on. Security Reliability Maintainability Portability Extensibility Reusability Application Affinity/Compatibility Resource Utilization define system properties and 4. Various other Non-functional requirements are: 1. there is no command line interface for any functions of the product. The user will get 2 pages 1. 7. or due to the external factors such as safety regulations.1 User Interface: User of the system will be provided with the Graphical user interface.iii).5 External Interface Requirements: 4. 4. 8. 3.

5. 2.1 General Constraints The interface will be in English only.6 General Constraints.4. The system is working for single server. 20 GB or above. Linux OS which supports networking. 17 . For each party 4. Communication channels Sender Receiver 4.Pentium I or above. Assumptions. JAVA development tool kit 4. Guidelines: Operating System: Windows XP/vista/7 or later version.3 Software Interface:Software required to make working of product is:1. RAM: HD: NIC: 128 MB or above.4 Communication Interfaces The two parties should be connected through either by LAN or WAN for the communication. Dependencies.2 Hardware Interface: Hardware requirements for Insurance on internet will be same for both the parties which are follows: Processor: .

GUI features available. Assumptions: User must be trained for basic computer functionalities.8 kbps in order to support message transfer in reasonable time. User must have the basic knowledge of English The system must be able to respond to database software within reasonable time. The system is a single user system. 4.  The speed of the communication channel (if any) must be. 18 . at a minimum 28.6.There is no maintainability or backup so availability will get affected. Front-end (user interaction):  The product will require a computer with an application program or with any other application program and an communication channel.2 Assumptions and Dependencies The product does require back-end database server MySQL for storing the username and password for different types of user of the system as well as various databases regarding various insurance information.

1 ARCHITECTURAL DESIGN 5. data throughout a system. 19 . So it is the starting point of the design phase that functionality decomposes the requirement specifications down to the lowest level of detail. SYSTEM DESIGN SPECIFICATION 5. or transform. It is also known as ‘bubble chart’. A Data Flow Diagrams is a structured analysis and design tool that can be used for flowcharting in place of. this lead to modular design. A DFD is a network that describes the flow of data and the processes that change. data structure or file organization. software. A DFD describes what data flow (logical) rather than how they are processed.1 DATA FLOW DIAGRAMS: Data flow diagrams (DFD) was first developed by LARRY CONSTANTINE as way representing system requirements in a graphical form.5. or in association with.1. It has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design. This network is constructed by using a set of symbols that do not imply a physical implementation. so it does not depend on hardware. information-oriented and process-oriented systems flowcharts.

These are symbols that represent data flows. data transformations and data storage. An enclosed figure.The symbols used to prepare DFD do not imply a physical implementation. usually circles. data sources. a DFD can be considered to an abstract of the logic of an information-oriented or a process-oriented system flow-chart. A directed line represents the flow of data that is data stream. An open-ended rectangle represents data storage. represent a process that transforms data streams. which are called nodes. usually a circle or an oval bubble. The principle processes that take place at nodes are: 20 . The points at which data are transformed are represented by enclosed figures. The four basic symbols used to construct data flow diagrams are shown below: A rectangle represents a data source or destination. For these reasons DFDs are often referred to as logical data flow diagrams.

SERVER DATA BASE REQUESTS DATA ST BASE CAD(CONTEXT ANALYSIS DIAGRAM) ADMIN ONLINE SHOPPING CUSTOMER 21 . Gen.user use customer user REQUEST DATA ST BASE ADMIN. splitting data streams 3. combining data streams 2.1. modifying data streams.


ER DIAGRAM prod_name prod_id price quantity product Buy product phone no user_name user_id dob make payment Sex Customer details email_id Address write feedback account STORE feedback ORDER_NO acc no pin no bank name feedback type coment feedbac k REPORT 23 .

DATABASE DESIGN: A database design is a collection of stored data organized in such a way that the data requirements are satisfied by the database.The field used to set relation between tables.  Foreign key: . quick. 24 .5. security and performance. There are also some specific objectives like controlled redundancy from failure. A collection of relative records make up a table. Normalization is a technique to avoid redundancy in the tables. The general objective is to make information access easy. Two essential settings for a database are:  Primary key: .1. To design and store data to the needed forms database tables are prepared.The field that is unique for all the record occurrences. 2. inexpensive and flexible for the user. privacy.

DATA BASE TABLE DESIGN: Category table Column name Cat_id Cat_name Data type int Char(20) Key constraint Primary key not null Not null PRODUCT TABLE Column name Prod_id Data type Int Key constraints extra Primary key not null Auto_increment Cat_id Prod_name Prod_descp Price Available Add_date int Char(20) Char(40) double int date Foriegn key Not null Not null null Not null Not null Not null 25 .

Admin Login table Column name User_id password Data type int Char(20) Key constraint Primary key not null Not null Login table Column name User_id password Data type int Char(20) Key constraint Primary key not null Not null 26 .

Store table Column name Order_no report Data type int Char(20) Key constraint Primary key not null null Temp table Column name Prod_id Prod_name Price Items User_id Purchage_date Order_no Data type int Char(20) Double Int Int Date Int Key constraint Foriegn key not null Not null Not null Not null Not null Not null null 27 .

User table Column name User_id Password User_name sex Address Date_of_birth Date_of_registe r Phone_no email Data type int Char(20) Char(20) Char(6) Char(40) date date Char(10) Char(30) Key constraint primary key not null Not null Not null Not null Not null Not null Not null Not null Not null extra Auto_increment Feedback table Column name User_id type feedback comment Feedback_date Data type int Char(10) Char(10) Varchar(40) date Key constraint not null Not null Not null null Not null 28 .

Account table Column name Bank_name Account_no password balance Data type Char(20) Char(20) Char(20) double Key constraint not null not null Not null Not null Sell table Column name Prod_id Prod_name price items User_id Purchage_date Order_no Data type Int Char(20) Double Int Int Date int Key constraint not null not null Not null Not null Not null Not null Not null 29 .

1. Login Validate User Request to the User1 system Perform next task Information Logout User2 (User Case Diagram) 30 .5.3 USER CASE DIAGRAM: User case diagrams are used to model the functional interaction between users and system.

6. 31 . It can also be stated as the process of validating and verifying that a software program/application/product meets the business and technical requirements that guided its design and development. can be implemented at any time in the development process. depending on the testing method employed. Software Testing also provides an objective. the process of executing a program or application with the intent of finding software bugs. with respect to the context in which it is intended to operate. independent view of the software to allow the business to appreciate and understand the risks at implementation of the software. however the most test effort is employed after the requirements have been defined and coding process has been completed. but are not limited to. TESTING Software Testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test. so that it works as expected and can be implemented with the same characteristics. Test techniques include. Software Testing.

isolate it from the remainder of the code. fakes and test harnesses can be used to assist testing a module in isolation. abstract class or derived/child class. which may belong to a base/super class. procedure. mock objects. etc. Unit testing has proven its value in that a large percentage of defects are identified during its use. each test case is independent from the others: substitutes like method stubs.. while in object-oriented programming.6. Its implementation can vary from being very manual (pencil and paper) to being formalized as part of build automation. function. and determine whether it behaves exactly as you expect. In procedural programming a unit may be an individual program. Unit tests are typically written and run by software developers to ensure that code meets its design and behaves as intended. Unit testing is a software verification and validation method where the programmer gains confidence that individual units of source code are fit for use. A unit is the smallest testable part of an application. the smallest unit is a class. Each unit is tested separately before integrating them into modules to test the interfaces between modules. Ideally.1 Unit Testing: The primary goal of unit testing is to take the smallest piece of testable software in the application. 32 .

followed by top-down testing. bottom-up testing is usually done first. also known as integration and testing (I&T). Bottom-up integration testing begins with unit testing. In a comprehensive software development environment. Integration testing is a component of Extreme Programming (XP). a unit is defined as the smallest testable part of an application.2 Integration Testing Integration testing. 33 . a pragmatic method of software development that takes a meticulous approach to building a product by means of continual testing and revision.6. is a software development process which program units are combined and tested as groups in multiple ways. followed by tests of progressively higher-level combinations of units called modules or builds. There are two major ways of carrying out an integration test. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution. the highest-level modules are tested first and progressively lower-level modules are tested after that. In top-down integration testing. called the bottom-up method and the top-down method. In this context.

Sometimes. Versions of the software.  Beta testing comes after alpha testing. are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. known as beta version. Two types of validation testing  Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers' site. before the software goes to beta testing. Validations testing is said to be successful when software functions in a manner that can be reasonably expected by the customer.3 Validation testing : At the validation level. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing.it is used for web application 34 . testing focuses on user visible actions and user recognizable output from the system. beta versions are made available to the open public to increase the feedback field to a maximal number of future users  Gray box testing Grey box testing is the combination of black box and white box testing. Intention of this testing is to find out defects related to bad design or bad implementation of the system.6.

Management 4. the SQA tasks to be performed.Code Control 11. Purpose 2.Media Control 12. Reference documents 3. Scope and Overview: 35 . Documentation 5. the standards against which the development work is to be measured.Software Quality Assurance Plan Each development and maintenance project should have a Software Quality Assurance Plan that specifies its goals. practices and conventions 6. Purpose. Tools. Configuration Management 8. The IEEE Standards for the Software Quality Assurance Plans states that the plan should contain the following sections: 1. Reviews and Audits 7. maintenance and retention.Records collection.Supplier Control 13. techniques and methodologies 10. 1. Problem reporting and corrective action 9.7. Standards. and the procedures and organizational structure.

The purpose of this Software Quality Assurance (SQA) Plan is to establish the goals. Management: An IEEE standard lays down three aspects that should be covered in the Software Quality Assurance Plan: Organization: The organization section includes the roles of the team members. This plan establishes the SQA activities performed throughout the life cycle of the ONLINE SHOPPING. Specifically. and software related groups that include Software Configuration Management (SCM). 2. It will show that the SQA group has a reporting channel to senior management that is independent of the project manager. The ONLINE SHOPPING Software Quality Assurance plan provides the framework necessary to ensure a consistent approach to software quality assurance throughout the project life cycle. Reference documents: a. System and Software Test. Principles and Practice: Nina S Godbole. 3. their hierarchy etc. The goal of the SQA program is to verify that all software and documentation to be delivered meet all technical requirements. It is important that the head of the Software Quality Assurance (SQA) function in the organization has the adequate 36 . processes. and Logistics. Software Quality Assurance. and responsibilities required to implement effective quality assurance functions for the ONLINE SHOPPING. this SQA Plan will show that the SQA function is in place for this project. the project’s software engineering group.

Identifying. Program Management/Line Management (Sponsor) is responsible for the following items: 1. d). e). processes. Implementing the software test practices. b). f). developing and maintaining planning documents Such as the Program Management Plan. The following describes the functional groups that influence and control software quality. Resolving and following-up on any quality issues raised by SQA. Identifying an individual or group independent from the Project to audit and report on the project’s SQA function. System Engineering is responsible for: Implementing the engineering practices. Software Design/Development is responsible for:: Identifying. implementing. Software Test is responsible for: Verifying. System Test is responsible for: 37 . and procedures as defined in program/project planning documents. processes. c). 2. and evaluating the quality factors to be implemented in the software. 2. Identifying the quality factors to be implemented in the system and software.authority to be able to perform independent verification that the processes are adhered to. and procedures as defined in program/project planning documents. Project Management is responsible for: 1. a).

The following are the tasks of SQA plan: 38 . Logistics is responsible for: 1. and procedures as defined in reference and other program/project planning documents. Reviewing and commenting on the “” SQA Plan. j). i). 2. Providing assistance in software process engineering and software process improvement. Implementing the quality program in accord ONLINE SHOPPING assurance with this SQA Plan. h). Maintaining the SQA Process. Independent Verification and Validation (IV& V) is responsible for: Implementing the practices. g). processes. Systems Engineering Process Office (SEPO) is responsible for: 1. Ensuring SQA training availability. processes. and procedures as defined for IV&V in program/project planning documents. 3. 2. Software Configuration Management (SCM) is responsible for: Implementing the SCM practices.Verifying the quality factors are implemented in the system (software and hardware). a) Tasks: An SQA task is performed in relationship to what software development activities are taking place. One or more SQA tasks can be performed concurrently until a task is completed.

 Review the activities performed by project personnel to ensure that the requirements of the quality plan and quality procedures are being satisfied. Evaluate System Requirements Analysis Process  Evaluate System Design Process  Evaluate Software Requirements Analysis Process  Evaluate Software Design Process  Evaluate Software Tools  Evaluate Software Implementation and Unit Testing Process  Evaluate End-item delivery Process  Evaluate Configuration Management Process b) Responsiblities: The project manager and design/development teams have primary responsibility for the quality controls applied during the development of the software project.  Agree to the quality plan with the project manager. 39 .  Resolve any disagreement between the project manager and quality personnel on matters relating to quality. The quality manager will:  Define the responsibilities of quality personnel in the form of quality assurance procedures applicable to the project.  Approve the plan of the audits for the project which are to be carried out by quality personnel.

CMM. Standards.  Evaluate defect trends and take appropriate action. practices and conventions: 40 . IEEE etc) and procedures mentioned and defined as in the Quality Manual and Quality Management System  User guides. The documentation section normally includes the following:  Software Requirements Specification (SRS)  Software Design Description  Software Verification Plan  Software Verification report  Reference to Software Standards (ISO. operators and programmers manual  Configuration Management Plan  Software Quality Objectives. 4. non-conformities found and ensure that corrective action is taken. Documentation: The basic purpose of the documentation section of the Software Quality Assurance Plan is to describe the documentation to be produced and how it is to be reviewed.  Agree on corrective action with the project manager for any discrepancies.Quality personnel will:  Carry out planned internal audits of the project to assess compliance with quality objectives. 5.

To verify the delivery of a fully conforming. SQA effort expended (actual) f. high-quality product. and metrics are met. SQA work scheduled (planned) c. Reviews and Audits: The review and audits sections of Software Quality Assurance Plan will state which technical and managerial reviews will be undertaken and how they will be carried out. the software top-level design document. The ANSI standard suggests that the following would be a minimum set of reviews:  Software Requirements Specification Review: This review is held to approve the document defining the software requirements specifications and it aims to check the adequacy of the requirements.  Primary Design Review: The purpose of this review is to approve formally. This section describes the procedures used by SQA to verify that the quality assurance provisions of this SQA Plan and applicable standards. 41 . conventions. every individual assigned to the project will participate in quality assurance. SQA milestone dates (completed) b. SQA effort expended (planned) e. SQA funds expended (planned) 6. The following measurements will be made and used to determine the cost and schedule status of the SQA activities: SQA milestone dates (planned) a. SQA work completed (actual) d. practices.

configuration status accounting.  In-Process Audit: In-Process audits of a sample design are held to verify the consistency of the design. Configuration Management: This Configuration Management section of the Software Quality Assurance Plan covers configuration identification. Each problem should be analyzed to determine its significance and causes and classified by category and each problem must have severity level and a priority number. which ensures that software problems are documented and resolved. and configuration auditing.  Physical Audit: This is held to verify that the software and its documentation are internally consistent prior to delivery to the user. 42 . 7.  Software Verification Review: The purpose of this review is to approve the test plan.  Functional Audit: This is held to verify that all the requirements in the software requirements specification have been met. acted upon and resolved. Critical Design Review: The purpose of this review is to approve the software detailed design document as a basis for further development work. All the problems should be promptly reported at appropriate level. It should be a closed-loop system. 8. It is the evaluation of the adequacy and completeness of the methods described. Problem reporting and corrective action: This section of the Software Quality Assurance plan describes the system. configuration control.

test case generators. maintenance. requirements tracing. requirements and design verification.SQA software tools include.For each problem. and use of backup copies 43 . statistical analysis packages. execution analyzers. Management should monitor the status of all unresolved problems. some corrective action and a target completion date should be identified. code analyzers. Tools. file comparators. debugging aids. software development folder/files. test drivers. structure analyzers. simulators. 10. reliability measurements and assessments. and information engineering CASE tools. techniques and methodologies: Tools . software traceability matrices. structuring preprocessors.techniques include review of the use of standards. operating system utilities. software inspections. Code Control: Code control includes the items listed below:  Identifying. and rigorous or formal logic analysis. Techniques . The appropriate level of management should be made aware of the problems and adverse trends. static or dynamic test tools. standards auditors. The methodologies should be well documented for accomplishing the task or activity and provide a description of the process to be used.methodologies are an integrated set of the above tools and techniques. and cataloging the software to be controlled  Identifying the physical location of the software under control  Identifying the location. performance monitors. Methodologies . checklists. documentation aids. The corrective action taken will be evaluated to ensure that it solved the problem without introducing any new problems. labeling. but are not limited to. 9.

Part of the evaluation process will require the supplier or vendor to describe their technical support. Distributing copies of the code  Identifying the documentation that is affected by a change  Establishing a new version  Regulating user access to the code. 44 . Security threats to a software project come from the following environmental factors:  Fire Damage  Water Damage  Energy Variations  Structural Damage  Pollution  Unauthorized Intrusion  Viruses and Worms  Misuse of Software. handling of user questions and problems. The Software Tool Evaluation Process will be followed. 11. SQA and project members will define and provide complete requirements to the supplier/vendor. 12. and software product upgrades. Media Control: The Media Control section of the Software Quality Assurance Plan will describe how the media are to be protected from unauthorized access or damage. Supplier Control: Prior to any purchase of software to support the development effort. Data and Services.

13. maintenance and retention: SQA activities are documented by records and reports that provide a history of product quality throughout the software life cycle. All SQA records will be collected and maintained in the SDL or archival storage for the life cycle of the product. SCREEN SHOTS 45 . Measurement data collected will be reviewed for trends and process improvement. Records collection. 8.






delivery report FEEDBACK PAGE 51 .

52 . Most of the have mark and the requirements which have been remaining. can be completed with a 10. FUTURE SCOPE OF PROJECT The project made here is just to ensure that this product could be valid in today real challenging world. Here all the facilities are made and tested. is to been conclude fulfilled that up the to project the that I undertook was worked upon with a sincere effort. In near future it will be extended for many types of insurance policies so that efficiency can be improved. Currently the system works for limited number of administrators to work.9. CONCLUSION This requirements short extension.

Websites referred:http://www.in 53 . by Wilton  The Complete Reference MYSQL  The Complete Referance HTML.0 by Hanna  Beginning JavaScript 2nd Edition. by Cay S. Horstmann and Gary Cornell  The Complete Reference JSP 2.google.co.BIBLIOGRAPHY Books which I referred for the reference  Core Java 2 Volume I and II.11.

THANK U 54 .

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->