CHAPTER 4.3 -:SOFTWARE REQUIREMENT ANALYSIS AND SPECIFICATION

Sponsored Links

The quality of a software product is only as good as the process that creates it. Requirements engineering one of the most crucial steps in this creation process. Without well-written requirements specification, developers do not know what to build, customers do not know what to expect, and there is no way to validate that the built system satisfies the requirements. Requirements engineering includes all activities related to the following:

· Identification and documentation of customer and user’s needs

· Creation of a document that describes the external behaviour and the associated constraints hat will satisfies those needs

· Analysis and validation of the requirements documents to ensure consistency, and feasibility

· Evolution of needs

Sponsored Links

The primary output of requirements engineering is requirements specification. If it describes both hardware and software, it is a system requirement specification. If it describes only software, it is a software requirement specification. Requirement stage end with creating a document called the Software Requirement Specification (SRS), which contain s a complete description of the external behaviour of the software system.

Nature of the SRS:

The basic issues that SRS writers shall address are the following:

1. Functionality: What the software is supposed to do?

2. External interfaces: How does the software interact with people, the system’s hardware, other hardware, and other software?

3. Performance: What is the speed, availability, response time, recovery time, etc of various software functions?

4. Attributes: What is the consideration for portability, correctness, maintainability, security, reliability etc.?

5. Design constraints imposed on an implementation: Are there any required standards on effect, implementation language, policies for database integrity etc.?

Since the SRS has specific role to play in the software development process, SRS writers should be careful not o go beyond the bounds of that role. This means the SRS

1. Should correctly define all the software requirements. A software requirement may exit because of the nature or the task to be solved or because of a special characteristic of the project.

2. Should not describe any design or implementation details. These should be described in the design stage of the project.

3. Should not impose additional constraints on the software. These are properly specified in other documents such as a software quality assurance plan.

Therefore, a properly written SRS limits the range of valid designs, but does not specify any particular design.

CHARACTERISTICS OF A GOOD SRS:

1. Correct: An SRS is correct if; every requirement stated therein one that the software shall meet. There is no tool or procedure that assures correctness.

2. Unambiguous: An SRS is unambiguous if, and only if; every requirement stated therein has only one interpretation

Sponsored Links

This site is designed to help BCA MCA student to develop final project and synopsis Download Free BCA Project, MCA Project, IT Projects, Final report and Project synopsis with Full documentation and code From www.ignousupport.blogspot.com for ignou students and other IT students.

Free download MCA projects in ASP.NET with documentation, Free download MCA projects in VB.NET with documentation, Free download MCA BSc CS projects in C#.NET with documentation,

Free download MCA projects in JAVA with documentation, Free download MCA projects in PHP with documentation, Free Download MCA BTech BE MSc BSc IT CS projects in PHP with MY SQL

Free Download BCA Final Year Project Synopsis, Free Download BCA Final Year Project Report, Free Download MCA Final Year Project Synopsis, Free Download MCA Final Year Project Report