Transcription of Requirements Definition and Management Processes
{{id}} {{{paragraph}}}
Example: bankruptcy
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. Project-Specific Enterprise-wide Requirements provide Re-Use Requirements common to a project can be obtained by referring to enterprise-wide Requirements Project-specific Requirements should be evaluated for re-factoring into enterprise-wide requirements6 RequirementsNon-Functional RequirementFunctionalRequirement Interface ConstraintOperational Constraint47 The Big Process Picture Requirements Analysis process fits into other Processes within Integrated Requirements Deliverables output from o
1 1 Software Engineering G22.2440-001 Session 1 – Sub-Topic 1 Requirements Definition & Management Processes and Tools Dr. Jean-Claude Franchitti New York University
Loading..
Tags:
Information
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document: