Object-oriented analysis and design

System sends payment authorization request to an external Payment Authorization Service, and requests payment approval.

"Payment authorization request" is a nickname for an aggregate of data, which needs to be explained in the Glossary.

1.4 Reliable Specifications: An Oxymoron?

Writing a Vision and Supplementary Specification is worthwhile as an exercise in clarifying a first approximation of what is wanted, the motivation for the product, and as a repository for the big ideas.

But they are not - nor is any requirements artifact - a reliable specification.

Only writing code, testing it, getting feedback, ongoing close collaboration with users and customers, and adapting, truly hit the mark.

1.5 Online Artifacts at the Project Website

Should be digital artifacts recorded only online at the project website. And instead of being plain static documents, they may be hyperlinked, or recorded in tools other than a word processor or spreadsheet. For example, the Glossary could be stored in a database table.

1.6 Not Much UML During Inception?

The purpose of inception is to collect just enough information to establish a common vision, decide if moving forward is feasible, and if the project is worth serious investigation in the elaboration phase.

As such, beyond simple UML use case diagrams, not much diagramming is often motivated.

There is more focus in inception on understanding the basic scope and 10% of the requirements, expressed in textual forms.

In practice, most UML diagramming will occur in the next phase - elaboration.

1.7 Other Requirement Artifacts Within the UP

s - start;
r - refine

Inception

Requirements artifacts in the inception phase will barely be started.