Transcription of Requirements Definition and Management Processes
{{id}} {{{paragraph}}}
Example: air traffic controller
Requirements Definition and Management Processes
11 Software 1 Sub-Topic 1 Requirements Definition & ManagementProcesses and ToolsDr. Jean-Claude FranchittiNew York UniversityComputer Science DepartmentCourant Institute of Mathematical Sciences2 Part IRequirements Definition and Management Processes23 Requirements Best Practices A requirement should be: 9 Unambiguous9 Complete9 Consistent9 Measurable9 Testable9 Traceable9 Design Free9 Understandable9 Concise9 Necessary 9 Feasible/Attainable Documenting Requirements ensures the 9 Stable9 Implementation - independent 9 Traceable4 Requirements Best Practices (cont.) Peer reviews Test each requirement against attribute standards For example: Traceable - Each requirement must be traceable to a businessneed. Baselining Define a clear scope Lock down Establish and enforce change impact analysis and approval process Things to avoid Ambiguous terms ( , easy, user-friendly, etc.) Analysis paralysis35 Enterprise-Wide vs.
6 11 What is Requirements Management? • Opportunity to determine Impact and control changes to Requirements •A systematic approach to eliciting, organizing and documenting the requirements of the system, and
Loading..
Tags:
Information
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
Related search queries
Using Microsoft Word's track changes, Word, Tracking, Using Microsoft Word's "track changes, Microsoft Word, For Formatting Resumes Using Microsoft, For Formatting Resumes Using Microsoft Word, Director Changes, Weathering and Erosion, Virginia Department of Education, Changes, Owner’s Manual, A Guide for Tactical Planners, University of Scranton