REQUIREMENTS ENGINEERING

 

Objectives

• To write an unambiguous, correct and consistent SRS

 

Description

The origin of most software systems is in the needs of some clients. The software system itself is created by some developers. Finally, the completed system will be used by the end users. Thus, there are three major parties interested in a new system: the client, the developer, and the users. The requirements for the system that will satisfy the needs of the clients and the concerns of the users have to be communicated to the developer. The client usually does not understand software or the software development process, and the developer often does not understand the client’s problem and application area. This causes a communication gap between the parties involved in the development project. The basic purpose of the SRS is to bridge this communication gap so that they have a shared vision of the software being built. Once the requirements are obtained, a standard software requirements document is prepared.

 

Tools

Open Source Requirements Management Tool (OSRMT): Requirements management tool is designed to achieve full SDLC traceability for features, requirements, design, implementation and testing. UI for requirements derivation, version control, attributes etc. 

 

Procedure

Each group should analyze problem definition proposed by him/her in the previous lab session. Through sheer brainstorming, each group has to derive functional and non-functional requirements of the product. Requirements engineering process consists of following steps:

• Requirements elicitation

• Requirements analysis

• Requirements validation

• Requirements management

In each group, the members designate themselves as clients and developers. Requirements are obtained by brainstorming. They are managed and documented using the OSRMT. A standard SRS document is generated

 

Deliverables

• SRS

 

Problem

Analyze the high level problem statement. Obtain a thorough understanding of what the software needs to provide by holding a series of meetings with the clients and the end users. The understanding obtained by problem analysis forms the basis of requirements specification. Validate the requirements. The final output of this exercise is a Software Requirements Specification document. It should focus on the following:

• Functionality

• Performance

• Design constraints imposed on an implementation

• External interfaces

Follow the IEEE standard (Annexure I)

 

References

 

• Pankaj Jalote: A Concise Introduction to Software Engineering , Springer, 2008, pg. 37-46

• Roger S. Pressman: Software Engineering A Practitioner's Approach, 7th Edition, McGraw Hill, 2010, pg. 174-203