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 UMLGlossaryGlossaryGlossaryCourse Registration System Glossary1. IntroductionThis document is used to define terminology specific to the problemdomain, explaining terms, which may be unfamiliar to the reader of theuse-case descriptions or other project documents. Often, this documentcan be used as an informal data dictionary, capturing data definitions sothat use-case descriptions and other project documents can focus onwhat the system must do with the information.2. DefinitionsThe glossary contains the working definitions for the key concepts in theCourse Registration System.2.1 Course: A class offered by the university.2.2 Course Offering: A specific delivery of the course for a specificsemester – you could run the same course in parallel sessions in thesemester. Includes the days of the week and times it is offered.2.3 Course Catalog: The unabridged catalog of all courses offered bythe university.Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 20The Glossary defines important terms used in the project.There is one Glossary for the system. This document is important to many developers,especially when they need to understand and use the terms that are specific to theproject. The Glossary is used to facilitate communications between domain expertsand developers.The Glossary is developed primarily during the Inception and Elaboration phases,because it is important to agree on a common terminology early in the project. InInception and Elaboration, it is used by domain experts (for example, businessanalysts) to explain all the domain-specific terminology used in their use cases. InElaboration and Construction, developers use the Glossary to explain technical termsused in the other four models.A system analyst is responsible for the integrity of the Glossary, ensuring that it isproduced in a timely manner and is continuously kept consistent with the results ofdevelopment.The above is just a sample outline for the Glossary. Not all of these elements need tobe in it. A project needs to establish the template to be used on that particularproject.Introduction: Provides a brief description of the Glossary and its purpose.Terms: Define the term in as much detail as necessary to completely andunambiguously characterize it.3 - 20
Module 3 - Requirements OverviewCase Study: GlossaryCase Study: Glossary• Review the Glossaryprovided in the CourseRegistrationRequirements DocumentGlossaryMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 21The idea is not to go over the Glossary in vivid detail, but to demonstrate how to readit, where to look for information you will need during the Analysis and Designactivities, as well as how to detect if it is insufficient.3 - 21
- 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 126 and 127: 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 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
- Page 176 and 177: DEV475 Mastering Object-Oriented An
- Page 178 and 179: DEV475 Mastering Object-Oriented An
- Page 180 and 181: DEV475 Mastering Object-Oriented An
- Page 182 and 183: DEV475 Mastering Object-Oriented An
Module 3 - Requirements OverviewCase Study: GlossaryCase Study: Glossary• Review the Glossaryprovided in the CourseRegistrationRequirements DocumentGlossary<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 21The idea is not to go over the Glossary in vivid detail, but to demonstrate how to readit, where to look for information you will need during the <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong>activities, as well as how to detect if it is insufficient.3 - 21