Software Requirement Specification(SRS)

SOFL - Structured Object-oriented Formal Language

1
2
3
4
5
6
7
module
const//a=1
process 1
process 2
...
process n
end_module

CDFD

Validation

Software Prototype

√ Making it alive

√ Easy yo be understood by non-experts

helps

  • Fast
  • Closes gaps in customers’ understanding of the requirements
  • Stimulates customers’ thinking
  • Early feedbacks
  • Deals with variability

Prototype

By Description

Horizontal

  • Does Not dive into all the layers or into system details
  • Demonstrate how the user interacts with the target system

Vertical

  • Touches in all levels of the system implementation
  • Looks like a subsystem of target software

By Purpose

Throwaway

  • For answering questions and resolving uncertainties
  • Discard or being integrated into the final system

Evolutionary

  • A solid architectural foundation
  • must be built with robust, production-quality code
  • Takes longer time

Building tool

  • Paper or software
  • after requirements analysis

Paper

  • Cheap
  • Fast
  • Anytime
  • Hardly any interaction
  • Throw away

Software

  • Software without interface

Animation

Evolutionary Prototype

Environment

Risks

Misunderstanding in performance

Away from requirements analysis

Misunderstanding in progress

Review

peer deskcheck

passaround

walkthrough

Inspection - formal peer review

Author

Moderator

Reader

Recorder

The reader describes each requirements in his or her own words

The inspectors brings up defects

The recorder captures the information