17-01-2013, 01:01 PM
Strategy Software Planning Tool
Strategy Software.docx (Size: 5.95 MB / Downloads: 200)
AIM & SCOPE OF THE PROJECT
The purpose of this Software Requirement Specification (SRS) is to help the project. It is provided with some requirements which are used in Strategy Software Planning Tool. All parts; design, coding and testing will be prepared with helping of SRS. The purpose of this document is to detail the requirements placed on the Strategy software Planning Tool System and serves as a contract between the admin. client, employee and the developers as to what is to be expected of the Strategy software Planning Tool, and how the components of the system are to work with each other with external systems.
This document will be checked by group member’s supervisor and it will corrected by members if supervisor orders.
EXISTING SYSTEM:
The existing system is manual and the manual system works in the following way:
• Present system is manual. It also maintains the user information in records. Which is much of time consuming process and more importantly it is error prone.
• The existing system is a manual system. Here the user’s needs to save his information in the form of excel sheets or Disk Drives.
• It is difficult to store and process of data and their information manually. Less security was provided for the valuable information of a Project.
• This system each and every information we are rectifying time very high. It consumes lot of manpower to better results. It lacks of data security
• It’s impossible to generate the quick reports and it to make accuracy and efficient calculations.
• There is no sharing is possible if the data is in the form of paper or Disk drives.
• The manual system gives us very less security for saving data; some data may be lost due to mismanagement.
PROPOSED SYSTEMS:
To overcome all the difficulties of the existing system the management has proposed automated the whole system and the development of the new automated system contains the following activities, which try to automate the entire process keeping in view of the database integration approach
• It provides complete activity as automated system.
• It is not limited to a single system because it is aimed to develop for web based environment.
• User friendliness (Graphical User Interface) is provided in the application.
• Provide Interactive interface through which a user can interact with different areas of application easily.
• The system makes the overall task much easier and flexible.
• It can be accessed over the Internet/Intranet.
• There is no risk of data mismanagement at any level while the project development is under process.
• Report generation feature is provided using ASP.Net Data Control like Grid View/Data List/Repeater/Form View to generate different kinds of reports easily using this application which is essential requirement now a day in any company.
• It provides session management technique for providing good security.
• It provides role based authentication to the different users like Administrator, Employees, clients.
SDLC METHODOLOGY
It play a vital role in the development of life cycle (SDLC) as it describes the complete requirement 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 scaled-down system, and represents an approximation of the characteristics of the final product.
CONCLUSION
It also provides knowledge about the latest technology used in developing web enabled application and client server technology that will be great demand in future. This will provide better opportunities and guidance in future in developing projects independently.
BENEFITS:
The project is identified by the merits of the system offered to the user. The merits of this project are as follows: -
• It’s a web-enabled project.
• This project offers user to enter the data through simple and interactive forms. This is very helpful for the client to enter the desired information through so much simplicity.
• The user is mainly more concerned about the validity of the data, whatever he is entering. There are checks on every stages of any new creation, data entry or updation so that the user cannot enter the invalid data, which can create problems at later date.
• Sometimes the user finds in the later stages of using project that he needs to update some of the information that he entered earlier. There are options for him by which he can update the records. Moreover there is restriction for his that he cannot change the primary data field. This keeps the validity of the data to longer extent.
• User is provided the option of monitoring the records he entered earlier. He can see the desired records with the variety of options provided by him.