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.

Module 1 - Best Practices of Software EngineeringPractice 2: Manage RequirementsPractice 2: Manage RequirementsBest PracticesProcess Made PracticalDevelop IterativelyManage RequirementsUse ComponentArchitecturesModel Visually (<strong>UML</strong>)Continuously Verify QualityManage Change<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 reserved11A report from the St<strong>and</strong>ish Group confirms that a distinct minority of softwaredevelopment projects is completed on-time <strong>and</strong> on-budget. In their report, thesuccess rate was only 16.2%, while challenged projects (operational, but late <strong>and</strong>over-budget) accounted for 52.7%. Impaired (canceled) projects accounted for31.1%. These failures are attributed to incorrect requirements definition from the startof the project to poor requirements management throughout the developmentlifecycle. (Source: Chaos Report, http://www.st<strong>and</strong>ishgroup.com)1 - 11

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

Saved successfully!

Ooh no, something went wrong!