Wiki Home

Use Case Model

Namespace: WIN_COM_API
A Use Case Model is a model of what the system is supposed to do and the system environment. It captures both Functional Requirements and Non Functional Requirements.
More formally, a Use Case Model is one or more Use Case Diagram s and supporting documentation describing the actors, Use Case s, and the relationships between them for the system. Use Case Model s describe Functional Requirements and Behavioral Requirements
The Use Case Model is developed for the users and the customers by the analysts.
Since the use case model embodies the Functional Requirements and Behavioral Requirements, it can serve as a de-facto contract between the customer and the developers. Among other things:

  • Customers approve the use-case model. The model is also useful whenever discussing the system with the customer.
  • Software architects and designers use the use-case model to get a system overview and use it as a basis for their work.
  • Testers use the use-case model to plan testing (ie to verify that the system satisfies all the scenarios in the Use Cases.
  • Future developers use the use-case model to understand how the existing version works (imagine that!).
  • Documentation writers use the use cases as a basis for writing the system's user guides
    See Use Cases
    Category Modeling, Category Project Management, Category Use Case
  • ( Topic last updated: 1999.08.22 01:33:21 AM )