SOFTWARE REQUIREMENT SPECIFICATION
Download as DOCX, PDF•1 like•283 views
This document outlines the structure and contents of a project proposal, including chapters on the introduction, general project description, requirements, design, and testing. The introduction defines the project scope and team roles. The general description provides an overview and problem statement. The requirements section specifies functional and non-functional needs, including modules, interfaces, performance, and constraints. The design chapter presents high-level and low-level representations of the system. Testing involves test plans and strategies to validate the project meets requirements.
SOFTWARE REQUIREMENT SPECIFICATION
- 1. Chapter 1 Introduction – 1.1 - Background 1.2 Scopeof the project 1.3 Team architecture (Role of each team member ) 1.4 Definition and aggregation . 1.5 references Chapter 2 General Description of Project 2.1 Overview 2.2 Problem statement objective . Chapter 3 Requirements 3.1 Functional requirements 3.2 Modules (Description of each modules . i.e. input , processing , o/p ) 3.3 Non functional requirements (User interface specification , i.e. menu , button form etc). 3.4 H/w interface (if used in the project). 3.5 Communication interface . 3.6 S/w interface . 3.7 Performance requirement (such as speed ,memory etc). 3.8 Design constraints. ( What precautions taken by the designer )
- 2. Chapter - 4 Design 4.1 High level design (Block diagram). 4.2 Low level design (Pseudo codeDataflow diagram, flow chart etc). 4.3 Functional description (i.e. Passing parameter, which function can call which function ). Chapter 5 Testing 5.1 Test plan 5.2 Testing used .