【文章內(nèi)容簡介】 t of the system. It means for use by developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.　　SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.　　　 As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project. 　　The steps for Spiral Model can be generalized as follows:　　 The new system requirements are defined in as much details as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.　　 A preliminary design is created for the new system.　　 A first prototype of the new system is constructed from the preliminary design. This is usually a scaleddown system, and represents an approximation of the characteristics of the final product.　　 A second prototype is evolved by a fourfold procedure:　　1. Evaluating the first prototype in terms of its strengths, weakness, and risks.　　2. Defining the requirements of the second prototype.　　3. Planning an designing the second prototype.　4. Constructing and testing the second prototype.　　 At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involved development cost overruns, operatingcost miscalculation, or any other factor that could, in the customer’s judgment, result in a lessthansatisfactory final product.　 The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above.　 The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.　 The final system is constructed, based on the refined prototype.　 The final system is thoroughly evaluated and tested. Routine maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time.　　　　　　　　　　　　　　　　　　　　　　　　　　　Fig Model　　　　　　　　The developer is responsible for:　　　 Developing the system, which meets the SRS and solving all the requirements of the system?　　 Demonstrating the system and installing the system at client39。s location after the acceptance testing is successful.　　　 Submitting the required user manual describing the system interfaces to work on it and also the documents of the system.　　 Conducting any user training that might be needed for using the system.　　 Maintaining the system for a period of one year after installation. 　　　　　　. STUDY OF THE SYSTEM　　　In the flexibility of the uses the interface has been developed a graphics concept in mind, associated through a browses interface. The GUI’S at the top level have been categorized as　　　1. Administrative user interface　2. The operational or generic user interface　　　　　The administrative user interface concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. The interfaces help the administrations with all the transactional states like Data insertion, Data deletion and Data updating along with the extensive data search capabilities.　　　　　　The operational or generic user interface helps the users upon the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information helps the ordinary users in managing their own information in a customized manner as per the assisted flexibilities.　NUMBER OF MODULES　　　　The system after careful analysis has been identified to be presented with the following modules:　　　The modules involved are: 　　1. Administration　　　2. Users　　　 　　Administrator : 　　　Admin has all privileges to add/modify employee and generate reports. In this there are sub modules like　 　1. UserDetails/CustomerDetails　　　2. Stock Details　　3. Employee Details　4. Reports　User Details: 　　This module contains 2 parts. User maintenance and password change.　 User maintenance is used to create a new user, modify the details of existing user or remove the existing user. Only the admin type user will have access to this part. Normal user won’t have access to this. While storing into database the password should be encrypted and stored. The user can choose its own logic to encrypt the password.　 User password is used to change own password. Both admin and normal user will have access to this.　　　Stock Details:　This module is used to maintain the various products available in the store. Each product available in the store should be classified under a product category. This module will be enabled only to the admin type of users. If a new product is received it should be added to the system with the corresponding details like product information, quantity, category, etc.　 　Reports:　This module is used to print various online reports. This module will be enabled only to the admin type of users. This contains various information about the users are available. Coming to sales reports it generates the reports by date wise as input and gives details of sale made on that date along with item information. This report should be available for a given date or for a date range.　 　　　Users:　 In this user maintenance is used to create a new user, modify the details of existing user or remove the exi