Scribd
Upload
23 views2 pages

Broad SRS Documentation

The document outlines the Software Requirement Specification (SRS) for selected projects, detailing hardware and software requirements, as well as the purpose and characteristics of an effective SRS. It emphasizes the importance of mutual understanding between clients and organizations, and the need for clear, measurable, and organized requirements. The SRS serves as a foundational document for project completion, ensuring functionality, performance, and design constraints are well-defined.

Uploaded by

DAN ANGEL
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
23 views2 pages

Broad SRS Documentation

The document outlines the Software Requirement Specification (SRS) for selected projects, detailing hardware and software requirements, as well as the purpose and characteristics of an effective SRS. It emphasizes the importance of mutual understanding between clients and organizations, and the need for clear, measurable, and organized requirements. The SRS serves as a foundational document for project completion, ensuring functionality, performance, and design constraints are well-defined.

Uploaded by

DAN ANGEL
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
You are on page 1/ 2

SOFTWARE REQUIREMENT

SPECIFICATION (SRS)
AIM:
To prepare broad SRS (Software Requirement Specification) for the selected projects.

Requirements:

Hardware Requirements:
- PC with 300 megahertz or higher processor clock speed recommended; 233 MHz
minimum required.
- 128 megabytes (MB) of RAM or higher recommended (64 MB minimum supported)
- 1.5 gigabytes (GB) of available hard disk space
- CD ROM or DVD Drive
- Keyboard and Mouse (compatible pointing device).

Software Requirements:
Rational Rose, Windows XP, 7, 8, 10

Theory:
1. An SRS is basically an organization's understanding (in writing) of a customer or
potential client's system requirements and dependencies.
2. It's a two-way insurance policy that assures mutual understanding between client and
organization.
3. It states functions, capabilities, and constraints of the software system.
4. It functions as a blueprint for project completion with minimal cost growth.
5. SRS is often the 'parent' document for all project-related documentation.
6. It includes only functional and non-functional requirements—not design suggestions.

A well-designed, well-written SRS accomplishes four major goals:


7. Provides feedback to the customer in natural language, including diagrams and tables.
8. Decomposes the problem into components and organizes information.
9. Serves as input to the design specification.
10. Serves as a product validation check.

Requirements development may involve surveys, interviews, and ROI or needs analysis.
The specification is written after gathering and analyzing requirements.
Basic Issues Addressed by an SRS:
- Functionality: What is the software supposed to do?
- External interfaces: How does it interact with hardware/software/users?
- Performance: Speed, availability, response/recovery time?
- Attributes: Portability, correctness, maintainability, security?
- Design Constraints: Standards, policies, implementation languages, environments?

Characteristics of a Good SRS:


 Correct – Specification must reflect the true requirements.
 Unambiguous – Every requirement should have only one interpretation.
 Complete – All necessary information for development is included.
 Consistent – No conflicting definitions or terms.
 Ranked for Importance – Requirements prioritized by necessity or feasibility.
 Verifiable – All requirements should be measurable and testable.
 Modifiable – Organized to allow easy updates.
 Traceable – Connects each requirement to its source or related document.

Conclusion:
The Software Requirement Specification was written successfully by following the steps
described above.

You might also like