Pages

Wednesday 3 February 2016

Software Requirement Specification Document


After analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing   system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the specifications and then successful design proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing run in system is also difficult, improper understanding of present system can lead diversion from solution.

2.2.1 PERFORMANCE REQUIREMENTS
We don’t have an exact idea for the performance requirements at this stage. Maybe at this stage we must say.
1. A powerful server.
2. A good hard disk (fast and big) that is essential for a database.
3. The files must be saved so that they can be downloaded any time.

2.2.2 DEPENDENCY REQUIREMENTS
The project depends on the user’s ability to understand the features of the online sharing and able to use the best of it. If the internet connection is not proper then this application will not work.

2.2.3 SECURITY REQUIREMENTS
1.      The system shall use secure sockets in all sharing that include any confidential Information.                                                                                
2.      The system shall automatically log out all users after a period of inactivity.
3.      The system shall confirm all sharing with the user’s web browser.
4.      The system shall not leave any cookies on the user’s computer containing the user’s password.
5.      The system shall not leave any cookies on the user’s computer containing any of the user’s confidential information.
1.      The user’s web browser shall never display a user’s password.  It shall always be echoed with special characters representing typed characters.
2.      The user’s web browser shall never display a user’s files after retrieving from the database.
3.       The system’s back-end servers shall never display a user’s password.  The user’s password may be reset but never shown.
4.      The system’s back-end servers shall only be accessible to authenticated administrators.
5.      The system’s back-end databases shall be encrypted.




2.2.4 FUNCTIONAL REQUIREMENTS:
This includes the list of the things that need to be includede i.e. the functions the project must accomplish.

2.2.5 MAINTENANCE REQUIREMENTS
The source code developed for this system shall be maintained in configuration management tool.

2.3 VALIDATIONS:
We will load the database with sample data and show the smooth functioning of the various facilities. Tests correctness will be conducted.

2.4 SDLC MODEL
The model is that is basically being followed is the WATER FALL MODEL, which states that the  phases are organized in a linear order .First of all the feasibility study is done .Once that part is over the requirement analysis and project planning begins,. If system exists one and modification and addition of new module is needed, analysis of present system can used as basic model.
The design starts after the requirement analysis is complete and the coding begins after the design is complete. Once the programming is completed, the testing is done .In this model the sequence of activities performed in software development project are:-
·         Requirement Analysis
·         Project Planning
·         System design
·         Detail design
·         Coding
·         Unit testing
·         System integration
    

No comments:

Post a Comment