System Specification and Use Cases

1. System and Environment: Represent your system (i.e., the system you are to develop) in graphical form.
   1. Identify external subsystems that your system will interact with. These might be parts of your computing environment. Represent these as subsystems and show with which subsystems (that you are to develop) they interact.
   2. Conceptualize your system as a system consisting of a number of subsystems (say two).
   3. Use the UML tool and the UML Component Diagram notation to represent the whole system.
      1. Mark each subsystem with the <<subsytem>> stereotype.
      2. Show relationships among subsystems (the "use" type of relationship) and between your system and the external systems.
      3. Identify interfaces. Show which subsystems implement the interfaces. Also show which systems use the interfaces
2. Use Cases: For the system (or subsystems) you are to develop identify actors and Use Cases, i.e., types of interactions with your system (types of functionality). Identify relationships among particular Use Cases, i.e., association (communication), extend, use case generalization, include.
   1. Represent the dependencies graphically.
   2. Describe each Use Case (text).
   3. For each use case provide an Activity Diagram

3. Design  User Interfaces and  represent them in graphical form. Use a tool, e.g., Powerpoint, to represent the interfaces.

4. Allocation: Allocate functionality to hardware, software, people, databases, procedures, documents. (Should analyze options according to predefined trade-off criteria.)

5. Technical risks: List all risks associated with lack of adequate experience or resources.