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