Software Requirements Specification Tutorial with Example

Software Requirements Specification Tutorial with Example:The Complete Guide of Computer Science and Information Technology to Crack any Examination:-In this  cyberpoint9 tutorial we are going to describe about the  concept of Any Competitive Examination in Computer Science and Information Technology and cyber programming. And also we will describe that how can we crack any Competitive Examination Like GATE-CS ,UGC-NET,BARC,VSSC, DRDO, ISRO, NASA, BHEL,SPACEX,GOOGLE,FACEBOOK, etc .This is the free Full Complete Guide for Computer Science and Information Technology Students and Achievers Scientist.In this tutorials: course for Beginners to Advance And why we  use  Handbook of CS AND IT  to make  more interactive and  save our time  for our Daily life. Best Online Tutorial for Computer Science and It students .When ever we want to learn any thing the things become more earlier is somebody/tutorial/study material taught us through Examples. Here we have tried to describe each and every concept of  Programming and Cyber Security   in the light of cyberpoint9.com  best Hindi  Short tutorial using simple and best possible example. These examples are so simple that even a beginner who had never even heard about hacking and Cyber law can easily learn and understand How  the  isro and barc drdo for computer science books works in our today’s Technical Field. This is  the best  tutorial/Study Material  very beneficial for beginners  as well as Professional.The Complete Guide of Computer Science and Information Technology.

Software Requirements

Software requirement is a process to understand the exact requirements of the customer and to document them properly. The hardest part of building a software system is deciding precisely what to build.

Analysis and Specifications

• Requirements describe the ‘what’ of a system not the ‘how’.
• Requirements engineering produces one large document, contains a description of what the system will do.

Requirement Elicitation

This is also known as gathering of requirements. Here, requirements are identified with the help of customer and existing system processes available.

There are following methods that can be used in requirement elicitation

• Interviews: First step to understand the problem statement of customer e., meeting with customer.
• Brainstorming Sessions: It is a kind of group discussion which ma_y lead to new ideas quickly and help to promote creative thinking.
• Facilitated Application Specification Technique: (FAST) The objecti_ve of FAST approach is to bridge the expectation gap, a difference between what developers think they are supposed to build and what custome_rs think they are going to get.
• The Use Case Approach: This approach uses a combination of text and pictures in order to improve the understanding of requirements.

Use case diagrams are graphical representations that may b_e decomposed into further levels of abstraction.

Design of the Use Case Approach

The following components are used for the design of the use case approach.

Actor or external agent lies outsides the system model but interacts with it in some way. An actor may be a person, machine or an information system.

Use case is initiated by a user with a particular goal in mind and competes  successfully when that goal is satisfied. It describes the sequence of  interactions between actors and the system necessary to deliver services that satisfies the goal.

Requirement Analysis

Requirement analysis allows the system analyst to refine the software  allocation and build conceptual models of the data, functional and bhavioural domains that will be treated by software.

Data Modeling

• Define data objects attributes and relationship.
• We use E-R diagrams for this purpose,

bhavioural Modeling

• Finding out different states of the system,
• Specifying events that cause the system to change state.
• We use state transition diagrams for behavioural modeling.

Function Modeling

• Identify functions that transform data objects .
• Indicate how data flows through system.
• Represent producers and consumers of data.

Requirement Documentation

Requirement document is the way to represent requirements in a consistent format. Requirement document is called SRS i.e., Software Requirements Specification. The SRS should be correct, unambiguous, complete, consistent, verifiable, modifiable, traceable.

–Key Points —–

• For function modeling, we use Data Flow Diagrams (DFDs). DFD shows the flow of data through a system.
• The requirement review process is carried out to improve the quality of the SRS.
• The requirement review process may also be called as requirements verification.

For maximum benefits, review and verification should not be treated as a discrete activity to be done only at the end of preparation of SRS. It should be treated as continuous activity that is incorporated into the elicitation, analyst and documentation.

Requirement Validation

After the completions of SRS document, we may like to check the documents for

• Completeness and consistency
• Conformance to standards
• Requirements conflicts
• Technical errors
• Ambiguous requirements

Validation Process with Inputs and Outputs

The objective of requirements validation is to certify that the SRS is an acceptable document of the system to be implemented.

---

Sorting in Design and Analysis of Algorithm Study Notes with Example

Learn Sorting in Handbook Series:  Click here 

Follow Us on Social Platforms to get Updated : twiter,  facebook, Google Plus