Unified Software Development Process Cycle

During the Creation of High-Level Requirements (Inception)

  1. With the customer, develop a High-Level Conceptual Diagram of labeled Use Cases within the System to be developed
  2. Use Case circles labeled with actions
  3. Determine Actors (external) that interact with Use cases (internal)
  4. Determine Boundary between System and domain Environment
  5. Write stories describing essential activities that occur within each labeled Use Case and label the activities in the Use Case; these form an informal statement of the Requirements
  6. Write algorithmic, or pseudo code, definitions of each Use Case; these form a more formal definition of the Requirements; follow the format of the USDP Use Cases
  7. Solicit additional requirements from the customer, particularly the non-functional ones
  8. Collect all of the requirements into a Requirements Document
  9. Link each requirement in the Document to the Use Cases that involve it
  10. Construct a Use Case Base that describes briefly what occurs in each labeled Use Case, for all of the Use Cases, and points to the corresponding Use Case definitions from 3.
  11. Include links into the Requirements Document indicating the requirements that each Use Case involves
  12. For each Use Case, describe each chain of activities in the Use Case via an Activity Diagram or simple State Diagram
  13. Label the Diagram with the name of the Use Case
  14. Include in the Use Case Base a pointer to the Diagram
  15. For each Use Case, identify objects by locating important subjects and objects of activities (can be phrases in the Use Case descriptions). Label these.
  16. Identify other important objects mentioned in the Use Case that interact with the objects and label them
  17. Review with the customer the labeled objects in the collection of Use Cases and eliminate the least important ones
  18. For each Use Case, prepare a Stereotype Diagram showing these important labeled objects in the Use Case and the links among them and the external Actors
  19. It is permissible to introduce important control entities that do not appear among the labeled objects; label these according to their roles
  20. Label the Diagram with the name of the Use Case and include in the Use Case Base a pointer to the Diagram
  21. Associate with each Use Case in the Use Case Base the important objects found in the Use Case along with brief descriptions of their meanings or purposes. This should include links to all of the Use Case activities in the Use Case Base in which each object participates and associations connecting it to all of the other labeled objects with which it relates.
  22. For each Use Case in the Use Case Base, associate each object and activity of the Use Case with the high-level requirements in the Requirements Document that involve them; consult the customer in doing this