How are Requirements organized in UP Artifacts?

The UP offers several requirements artifacts but few are included. They are:

• Use - Case Model − A set of typical scenarios of using a system. There are primarily for functional (behavioral) requirements.


• Supplementary Specification− This artifact is primarily for all non - functional requirements, such as performance or licensing. It is also the place to record functional features not expressed as use cases; for example, a report generation.


• Glossary– In its simplest form, the Glossary defines noteworthy terms. It also encompasses the concept of the data dictionary, which records requirements related to data, such as validation rules, acceptable values, and so forth. The Glossary can detail any element: an attribute of an object, a parameter of an operation call, a report layout, and so forth.


• Vision − Summarizes high - level requirements that are elaborated in the Use-Case Model and Supplementary Specification, and summarizes the business case for the project. A short executive overview document for quickly learning the project's big ideas.


• Business Rules / Domain Rules− describe requirements or policies that go beyond the range of one software project they are required in the domain or business, and many applications may need to conform to them. An example is government tax laws.