Object-oriented analysis and design

It is often useful to identify and record those domain rules that influence the requirements, usually realized in the use cases, because they can clarify incomplete or ambiguous use case content.

Caution on Rules

Rules are not application requirements.

Do not record system features as rules.

They describe the constraints and behaviors of how the domain works, not the application.

Information in Domains of Interest

It is often valuable for a subject matter expert to write (or provide URLs to) some explanation of domains related to the new software system (sales and accounting, the geophysics of underground oil/water/gas flows, ...), to provide context and deeper insight for the development team. It may contain pointers to important literature or experts, formulas, laws, or other references.

1.2 Vision

Content:

• The Vision artifact template
• Are We Solving the Same Problem? The Right Problem?
• System Features -Functional Requirements
• Other Requirements in the Vision
• Vision, Features, or Use CasesóWhich First?

The Vision artifact template

Revision History (Version, Date, Description, Author) Introduction Positioning Business Opportunity Problem Statement Product Position Statement Alternatives and Competition... Stakeholder Descriptions Market Demographics... Stakeholder (Non-User) Summary... User Summary... Key High-Level of Goals and Problems the Stakeholders User-Level Goals User Environment...

Product Overview Product Perspective Summary of Benefits