Requirements wg RUP.pptVIP

Requirements wg RUP Materia?y na seminarium ?Metodyki tworzenia SI” Wykona? Marcin Wi?cek Styczeń 2006 Artifacts Either final or intermediate work products produced and used during a project. Artifacts capture and convey project information, and may take various shapes or forms. Requirements/Glossary Requirements/Glossary Po co ? There is one Glossary for the system that provides a consistent set of definitions to help avoid misunderstandings. Project members initially use the Glossary to understand the terms that are specific to the project. This document is also important to people performing these roles: Developers, who make use of the terms in the Glossary when designing and implementing classes, database tables, user-interfaces, and so forth Analysts, who use the Glossary to capture project-specific terms so they can clearly define business rules, and to ensure that requirement specifications make correct and consistent use of those terms Course developers and technical writers, who use the Glossary to construct training material and documentation using recognized terminology Requirements/Glossary Punkty do sprawdzenia Does each term have a clear and concise definition? Is each glossary term included somewhere in the use-case descriptions? If not, it may imply that a use case is missing or that the existing use cases are not complete. It is more likely, though, that the term is not included because it is not needed. In that case, you should remove it. Are terms used consistently in the brief descriptions of actors and use cases? Does a term represent the same thing in all use-case descriptions? Requirements/Glossary Course Registration SystemGlossary? Version 2.0 Revision History Date Version Description Author 26/Dec/1998 1.0 Draft version Bill Collings 19/Feb/19