CS510 Handouts Complete by 404

CS510: Software Requirements and Specification

Overview

Why this course needed?

• Let’s visualize how it is difficult to understand others point of view

What the customer really needed. How the customer explain it. How the projector leader understood it. How the analyst design it. How the projector was documented.

Course learning objectives

• To understand the role of Software Requirement and Specification(SRS) in software projects.
• To understand the essential nature of SRS.
• To study current techniques, notations, methods, processes and tools used in SRS.
• To gain practical experience in writing of the SRS document

Course Evaluation

• Assignments
• Discussion/Presentation
• Quizzes

◦ Mid term exam and · Final term exam · Course Textbooks

• Requirements Engineering: Processes and Techniques, Gerald Kotonya and Sommerville, John-Wiley Sons, 1998 (or Latest Edition).
• Software Requirements, Karl E. Wiegers, Microsoft Press, 2003(or Latest Edition).
• Software Requirements Specification, David Tuffley, CreateSpace Independent Publishing Platform, 2010 (or Latest Edition).
• System Requirements Engineering, Loucopoulos and Karakostas, McGraw-Hill, 1995 (or Latest Edition).

Topics to be covered · o Software Requirement basic concepts ·  What, Why and Who o SRS processes ·  Sequence of activities that ·  need to be performed in ·  the requirement phase o · Requirement Elicitation

•  Process of discovering, reviewing, documenting, and understanding the user's needs and constraints for the system.

o Requirement Modeling

•  Visualization of requirements for better understanding and analysis o Requirement Analysis

 Refining the user's needs and constraints o Requirement Specification

•  Process of documenting the user's needs and constraints clearly and precisely.

o Requirement verification and validation

•  Process of ensuring that the system requirements are complete, correct, consistent, and clear. o Requirement Management
•  Scheduling, coordinating, and documenting the requirements engineering activities o Requirement Traceability

 if the source of the requirements can be identified

Introduction

What is a Requirement?

◦ Something required, something wanted or needed

◦ A statement of a system service or constraint

◦ A condition or capability that must be possessed by a system (IEEE)

Why requirement is needed?

◦ Requirements form the basis for all software products · Requirement Challenges ·  Challenges · ◦ Necessarily involves people interaction · ◦ Cannot be automated

Why it is hard to Understand Requirements?

◦ Visualizing a future system is difficult

◦ Capability of the future system not clear, hence needs not clear

◦ Requirements change with time · Requirement Task · Input · ◦ Users need in mind of people · Output · ◦ precise statement of what the future system will do · Requirement Examples