Communicating Requirements Lecture 8

Keywords Communicating Requirements Lecture 8 requirements lecture requirements modeling analysis
Standards groups

SRS should not include...
requirements analysts shouldn’t do design!
Requirements and designs have different audiences
Except where application domain constrains the design
Analysis and design are different areas of expertise
limited communication between different subsystems for security reasons.
Designs
Different lifetimes
Different audiences
Product assurance plans
CM, V&V, test, QA, etc
Project development plans
Lifetime of development plans is much shorter
cost, staffing, schedules, methods, tools, etc
Lifetime of SRS is until the software is made obsolete
University of Toronto Department of Computer Science

Metadata
Date published
2003
Document type
conference presentation
Pages
7
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
File MIME type Size (KB) Language Download
08-communicating-4up.pdf application/pdf   506.77 KB English DOWNLOAD!
File attachments
Cover images
Publisher
University of Toronto
Visit also
Copyright