Use Case Diagram in Expanded Format

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

  • High Level Use Case Diagram
    • Can it be used configuration management ?: Yes
  • Requirements Specification Document
    • Can it be used configuration management ?: Yes

Box-Out.png
Exit

  • Use Case Diagram in Expanded Format (using the Craig Larman Method)
    • Can it be used configuration management ?: Yes

Star.png
Solution

process-descending-24px.png
Process

Use Case Diagram in Expanded Format.png

time-24px.png
Development time

    • To acquire the necessary knowledge to develop the software product: 2 hours
    • To create the Product Pattern: 2 hours
    • To apply the Product Pattern: 10 hours.

video-24px.png
Explanatory Video

    • Not applicable

Search-32px.png
Quality Controllers

  • None

start-flag.png
Initial Context

It is developing a software system using the Craig Larman Method. It is already created the use case diagram high-level system.

end-flag.png
Result Context

It has been explained in detail all use cases of the use case diagram of the system, this explanation contains both, information in the format described at a high level, and a description of activities involving each use case including its alternative courses . It has been using the format proposed in Craig Larman Method.

cloud.png
Problem

It is desired to explain in detail all use cases diagram, including a description of system activities involving each.

forces.png
Restrictions (Forces)

  • Type of Organization: SMEs, Large Companies.
  • System Type It applies to all types of systems.
  • Programming Paradigm: OO (Object Oriented).

roles.png
Roles

  • Analyst
  • Customer
  • Project Manager
  • System Users

lightbulb.png
Lessons Learned

  • Benefits of using this pattern
    • A graphic description of how the software system works and how it will be used is provided.
    • It is possible to describe the interactions between the system and its actors.
    • It has a detailed and explicit description of the purpose of each use case diagram.
    • The activities described are useful for creating the class diagram.

award.png
Capability Level

  • Capability Level 2 CMMI.

Options.png
Basic Knowledge and Skills

board-24px.png
Knowledge

  • Definition of software requirements (functional and non-functional).
  • Craig Larman Method
    • Notions of UML, especially the technique of modeling of use cases.

help-24px.png
Abilities

  • Capacity of abstraction.

Information-Sources.png
Information Resources

  • Ferré Grau, X & Sanchez-Segura, M. (2004). Desarrollo Orientado a Objetos con UML. Recuperado el 2009-11-26 de http://www.clikear.com/manuales/uml/index.aspx.
  • Fowler, M. (2004). UML distilled: a brief guide to the standard object modelling language. Addison-Wesley.
  • Larman, C. (2001). Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process (2da. ed.). Prentice Hall.
  • Jacobson, I. & Booch, G.(1999). The unified software development process. Addison-Wesley.
  • Rumbaugh, J. & Jacobson, I. (2005). The unified modeling language reference manual. Addison-Wesley.
  • Rumbaugh, J. (2005). Object-Oriented Modelling and Design. Prentice Hall.