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 UMLUse-Case ModelRequirements Overview Topics• Introduction• Key Concepts• Use-Case Model• Glossary• Supplementary Specifications• CheckpointsMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 103 - 10

Module 3 - Requirements OverviewWhat Is a Use-Case Model?What Is a Use-Case Model?• A model that describes a system’s functionalrequirements in terms of use cases• A model of the system’s intended functionality(use cases) and its environment (actors)View Report CardRegister for CoursesStudentLoginMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 11• A Use-Case Model describes a system’s functional requirements in terms of usecases. It is a model of the system's intended functionality and its environment.The Use-Case Model serves as a contract between the customer and thedevelopers. Because it is a very powerful planning instrument, the Use-CaseModel is generally used in all phases of the development cycle.• When the customer approves the Use-Case Model, you know the system is whatthe customer wants. You can also use the model to discuss the system with thecustomer during development.• Potential users use the Use-Case Model to better understand the system.• Designers use it as a basis for their work and to get a system overview.• Testers use it to plan testing activities (use case and integration testing) as early aspossible.• Those developing the next version of the system use it to understand how theexisting version works.• Documentation writers use the use cases as a basis for writing the system userguides.• The architect uses the Use-Case Model to identify architecturally significantfunctionality.• The manager uses it to plan and follow up on use-case modeling and subsequentdesign.3 - 11

<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>Use-Case ModelRequirements Overview Topics• Introduction• Key Concepts• Use-Case Model• Glossary• Supplementary Specifications• Checkpoints<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 103 - 10

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

Saved successfully!

Ooh no, something went wrong!