SOFTWARE REQUIREMENT SPECIFICATION

Views:
 
     
 

Presentation Description

BCA 5th sem

Comments

Presentation Transcript

SOFTWARE REQUIREMENT SPECIFICATION:

SOFTWARE REQUIREMENT SPECIFICATION BY LAVANYA

Slide 2:

A requirements specification for a software system – is a complete description of the behavior of a system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. These requirements reflect the needs of customers for a system that helps to solve some problem A Software Requirements Specification ( SRS )

FUNCTIONAL REQUIREMENTS:

FUNCTIONAL REQUIREMENTS Describe functionality or system services. Depend on the type of software, expected users and the type of system where the software is used. Functional user requirements may be high-level statements of what the system should do but functional system requirements should describe the system services in detail

NON FUNCTIONAL REQUIREMENTS:

NON FUNCTIONAL REQUIREMENTS These define system properties and constraints e.g. reliability, response time and storage requirements. Constraints are I/O device capability, system representations, etc. Process requirements may also be specified mandating a particular CASE system, programming language or development method. Non-functional requirements may be more critical than functional requirements. If these are not met, the system is useless.

Slide 5:

Introduction Purposes Scope Definitions System Overview References Overall Description Product Perspective Product Functions User Characteristics Constraints, Assumptions and Dependencies Specific Requirements External interfaces Functions Performance requirements gf Logical database requirement Design constraints Key features SRS DOCUMENT

Slide 6:

VALIDATION CHECKS Validity check Consistency check Realism check Verifiability check Completeness check VALIDATION TECHNIQUES Requirement reviews Prototyping techniques Test case generation

Slide 7:

A system model is the conceptual model that describes and represents a system. A system comprises multiple views such as planning, requirement (analysis), design, implementation, deployment, structure, behavior, input data, and output data views. A system model is required to describe and represent all these multiple views Types Context process Behavioral data flow Data state machine Object inheritance object aggregation object behaviour THANK YOU