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 ...
DEV475 Mastering Object-Oriented Analysis and Design with UMLWhat Are the Benefits of a Use-Case Model?What Are the Benefits of a Use-Case Model?• Communication• Identification• VerificationCommunicationUse CaseVerificationIdentificationEnd UserDomain ExpertUsersMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 12There are many ways to model a system, each of which may serve a differentpurpose. However, the most important role of a Use-Case Model is to communicatethe system's behavior to the customer or end user. Consequently, the model must beeasy to understand.Communication with the end users and domain experts:• Provides buy-in at an early stage of system development.• Ensures a mutual understanding of the requirements.Identification of system users and what the system should do:• Establishes the requirements for the system interfaces.Verification that all requirements have been captured:• Ensures that the development team understands the requirements.The Use-Case Model is also used to identify the actors that interact with the system.Because they represent system users, actors help delimit the system and give a clearerpicture of what it is supposed to do. Use cases are developed on the basis of theactors' needs, ensuring that the system will turn out to be what the users expected.3 - 12
Module 3 - Requirements OverviewHow Would You Read This Diagram?How Would You Read This Diagram?View Report CardRegister for CoursesCourse CatalogMaintain ProfessorInformationStudentLoginSelect Courses toTeachRegistrarMaintain StudentInformationClose RegistrationProfessorSubmit GradesBilling SystemMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 13Answer the following questions:1. Which use cases will a student be able to perform? A professor? The CourseCatalog?2. If Charlie is a student and professor, which use cases will he be able to execute?3. Describe the functionality of this system.4. Describe the actor relationships for the Close Registration and Select Courses ToTeach use cases.5. What doesn’t this model say?6. Which use case needs to run first — Register for Courses or View Report Card?3 - 13
- Page 76 and 77: DEV475 Mastering Object-Oriented An
- Page 78 and 79: DEV475 Mastering Object-Oriented An
- Page 80 and 81: DEV475 Mastering Object-Oriented An
- Page 82 and 83: DEV475 Mastering Object-Oriented An
- Page 84 and 85: DEV475 Mastering Object-Oriented An
- Page 86 and 87: DEV475 Mastering Object-Oriented An
- Page 88 and 89: DEV475 Mastering Object-Oriented An
- Page 90 and 91: DEV475 Mastering Object-Oriented An
- Page 92 and 93: DEV475 Mastering Object-Oriented An
- Page 94 and 95: DEV475 Mastering Object-Oriented An
- Page 96 and 97: DEV475 Mastering Object-Oriented An
- Page 98 and 99: DEV475 Mastering Object-Oriented An
- Page 100 and 101: DEV475 Mastering Object-Oriented An
- Page 102 and 103: DEV475 Mastering Object-Oriented An
- Page 104 and 105: DEV475 Mastering Object-Oriented An
- Page 106 and 107: DEV475 Mastering Object-Oriented An
- Page 108 and 109: DEV475 Mastering Object-Oriented An
- Page 110 and 111: DEV475 Mastering Object-Oriented An
- Page 112 and 113: DEV475 Mastering Object-Oriented An
- Page 114 and 115: DEV475 Mastering Object-Oriented An
- Page 116 and 117: DEV475 Mastering Object-Oriented An
- Page 118 and 119: DEV475 Mastering Object-Oriented An
- Page 120 and 121: DEV475 Mastering Object-Oriented An
- Page 122 and 123: DEV475 Mastering Object-Oriented An
- Page 124 and 125: DEV475 Mastering Object-Oriented An
- Page 128 and 129: DEV475 Mastering Object-Oriented An
- Page 130 and 131: DEV475 Mastering Object-Oriented An
- Page 132 and 133: DEV475 Mastering Object-Oriented An
- Page 134 and 135: DEV475 Mastering Object-Oriented An
- Page 136 and 137: DEV475 Mastering Object-Oriented An
- Page 138 and 139: DEV475 Mastering Object-Oriented An
- Page 140 and 141: DEV475 Mastering Object-Oriented An
- Page 142 and 143: DEV475 Mastering Object-Oriented An
- Page 144 and 145: DEV475 Mastering Object-Oriented An
- Page 146 and 147: DEV475 Mastering Object-Oriented An
- Page 148 and 149: DEV475 Mastering Object-Oriented An
- Page 150 and 151: DEV475 Mastering Object-Oriented An
- Page 152 and 153: DEV475 Mastering Object-Oriented An
- Page 154 and 155: DEV475 Mastering Object-Oriented An
- Page 156 and 157: DEV475 Mastering Object-Oriented An
- Page 158 and 159: DEV475 Mastering Object-Oriented An
- Page 160 and 161: DEV475 Mastering Object-Oriented An
- Page 162 and 163: DEV475 Mastering Object-Oriented An
- Page 164 and 165: DEV475 Mastering Object-Oriented An
- Page 166 and 167: DEV475 Mastering Object-Oriented An
- Page 168 and 169: DEV475 Mastering Object-Oriented An
- Page 170 and 171: DEV475 Mastering Object-Oriented An
- Page 172 and 173: DEV475 Mastering Object-Oriented An
- Page 174 and 175: DEV475 Mastering Object-Oriented An
<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>What Are the Benefits of a Use-Case Model?What Are the Benefits of a Use-Case Model?• Communication• Identification• VerificationCommunicationUse CaseVerificationIdentificationEnd UserDomain ExpertUsers<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 12There are many ways to model a system, each of which may serve a differentpurpose. However, the most important role of a Use-Case Model is to communicatethe system's behavior to the customer or end user. Consequently, the model must beeasy to underst<strong>and</strong>.Communication <strong>with</strong> the end users <strong>and</strong> domain experts:• Provides buy-in at an early stage of system development.• Ensures a mutual underst<strong>and</strong>ing of the requirements.Identification of system users <strong>and</strong> what the system should do:• Establishes the requirements for the system interfaces.Verification that all requirements have been captured:• Ensures that the development team underst<strong>and</strong>s the requirements.The Use-Case Model is also used to identify the actors that interact <strong>with</strong> the system.Because they represent system users, actors help delimit the system <strong>and</strong> give a clearerpicture of what it is supposed to do. Use cases are developed on the basis of theactors' needs, ensuring that the system will turn out to be what the users expected.3 - 12