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 ...

crnarupa.singidunum.ac.rs
from crnarupa.singidunum.ac.rs More from this publisher
12.07.2015 Views

DEV475 Mastering Object-Oriented Analysis and Design with UMLCheckpoints: Requirements: GlossaryCheckpoints: Requirements: Glossary• Does each term have a clear andconcise definition?• Is each glossary term includedsomewhere in the use-casedescriptions?• Are terms used consistently inthe brief descriptions of actorsand use cases?Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 30If each Glossary term is not included somewhere in the use-case descriptions, thatmay imply that a use case is missing or that the existing use cases are not complete. Itis more likely, though, that the term is not included because it is not needed, and itshould be removed from the Glossary.A term should represent the same thing in all use-case descriptions.3 - 30

Module 3 - Requirements OverviewReviewReview: Requirements Overview• What are the main artifacts of Requirements?• What are the Requirements artifacts used for?• What is a Use-Case Model?• What is an actor?• What is a use case? List examples of use caseproperties.• What is the difference between a use case and ascenario?• What is a Supplementary Specificationand what does it include?• What is a Glossary and what doesit include?Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 313 - 31

<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>Checkpoints: Requirements: GlossaryCheckpoints: Requirements: Glossary• Does each term have a clear <strong>and</strong>concise definition?• Is each glossary term includedsomewhere in the use-casedescriptions?• Are terms used consistently inthe brief descriptions of actors<strong>and</strong> use cases?<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 reserved 30If each Glossary term is not included somewhere in the use-case descriptions, thatmay imply that a use case is missing or that the existing use cases are not complete. Itis more likely, though, that the term is not included because it is not needed, <strong>and</strong> itshould be removed from the Glossary.A term should represent the same thing in all use-case descriptions.3 - 30

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

Saved successfully!

Ooh no, something went wrong!