12.07.2015 Views

DEV475 Mastering Object-Oriented Analysis and Design with UML ...

DEV475 Mastering Object-Oriented Analysis and Design with UML ...

DEV475 Mastering Object-Oriented Analysis and Design with UML ...

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>DEV475</strong> <strong>Mastering</strong> <strong>Object</strong>-<strong>Oriented</strong> <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> <strong>with</strong> <strong>UML</strong>Map of the TerritoryMap of the TerritoryNeedsProblemProblemSpaceFeaturesSoftwareRequirementsTraceabilitySolutionSpaceTheProductto BeBuiltTest Scripts<strong>Design</strong>UserDocs<strong>Mastering</strong> <strong>Object</strong> <strong>Oriented</strong> <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> <strong>with</strong> <strong>UML</strong>Copyright © 2003 Rational Software, all rights reserved14Managing requirements involves the translation of stakeholder requests into a set ofkey stakeholder needs <strong>and</strong> system features. These in turn are detailed intospecifications for functional <strong>and</strong> nonfunctional requirements. Detailed specificationsare translated into test procedures, design, <strong>and</strong> user documentation.Traceability allows us to:• Assess the project impact of a change in a requirement.• Assess the impact of a failure of a test on requirements (that is, if the test fails, therequirement may not be satisfied).• Manage the scope of the project.• Verify that all requirements of the system are fulfilled by the implementation.• Verify that the application does only what it is intended to do.• Manage change.1 - 14

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!