Scribd
Upload
116 views1 page

Experiment 7: (Requirements)

The document outlines the elements that should be included in a software requirement specification document. A typical SRS includes a system overview, objectives of the proposed system and how it improves upon existing systems, and analysis of functional and non-functional requirements. The problem overview describes a company approaching a software developer to automate and move their processes online, and the software developer agreeing to develop the project using a waterfall model. The SRS is then expected to include a system overview, use cases, differences in scope from the current to proposed system, non-functional requirements, and features of the new portal.

Uploaded by

Sanket Duhoon
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
116 views1 page

Experiment 7: (Requirements)

The document outlines the elements that should be included in a software requirement specification document. A typical SRS includes a system overview, objectives of the proposed system and how it improves upon existing systems, and analysis of functional and non-functional requirements. The problem overview describes a company approaching a software developer to automate and move their processes online, and the software developer agreeing to develop the project using a waterfall model. The SRS is then expected to include a system overview, use cases, differences in scope from the current to proposed system, non-functional requirements, and features of the new portal.

Uploaded by

Sanket Duhoon
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

EXPERIMENT 7

(Requirements)

AIM: Identify the elements of Software Requirement Specification document.

THEORY: The output of requirement analysis is software requirement specification


document. It should clearly specify what the system should do. A typical SRS consists of
system overview, objectives of proposed system such that it is proven significant over the
existing system, analysis of functional and non-functional requirements etc.

PROBLEM OVERVIEW: AS, a giant books franchise has approached IT company ABC
Ltd. to automate its processes and shift them online. ABC Ltd agrees to take on the project and,
both the companies sits down and strikes a deal. After detailed discussion ABC Ltd decides to
follow water fall model for development of the project. The concerned team at ABC designed
and developed the SRS. Which of these are expected to be present in the SRS?

ELEMENT PRESENT OR NOT?


System Overview Yes, it is required and it comes under the
Introduction.

Class Diagram Not mandatory.

Source Code Not required.

Use Cases Yes, it is required and it comes under Overall


Description.

Flow Charts for algorithms realizing the Not required as it comes under designing part.
functionality of the system

Code review Comments Not required as it comes under designing part.

Test results Test results of existing system are required and it


comes under System Overview.
The Difference in the scope of the current Yes, it is required and it comes under System
system to be proposed system. Overview.
Non-Functional requirements Yes, it comes under Non-functional
requirements.
Features of new portal to be developed Yes, it is required and it comes under Functional
requirements.

You might also like