PDF4PRO ⚡AMP

Modern search engine that looking for books and documents around the web

Example: bankruptcy

Requirements Definition and Management Processes

Back to document page

11Software 1 Sub-Topic 1Requirements Definition & ManagementProcesses and ToolsDr. Jean-Claude FranchittiNew York UniversityComputer Science DepartmentCourant Institute of Mathematical Sciences2Part IRequirements Definition and Management Processes23Requirements Best Practices A requirement should be: 9Unambiguous9Complete9Consistent9Measura ble9Testable9Traceable9Design Free9Understandable9Concise9Necessary 9Feasible/Attainable Documenting Requirements ensures the 9Stable9Implementation - independent 9Traceable4Requirements 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 paralysis35Enterprise-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 requirements6RequirementsNon-Functional RequirementFunctionalRequirement Interface ConstraintOperational Constraint47The Big Process Picture Requirements Analysis process fits into other Processes within Integrated Requirements Deliverables output from one process become inputs

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

  Processes

Download Requirements Definition and Management Processes


Information

Domain:

Source:

Link to this page:

Please notify us if you found a problem with this document:

Spam in document Broken preview Other abuse

Related search queries