High Level Use Case Diagram

De productpatterns_wiki
Revisión a fecha de 22:37 12 feb 2015; PfcEsther (Discusión | contribuciones)

(dif) ← Revisión anterior | Revisión actual (dif) | Revisión siguiente → (dif)
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Inputs

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

Box-Out.png
Output

  • High Level Use Case Diagram(using Craig Larman Method)
    • Can it be used confiuration management ?: Yes

Star.png
Solution

time-24px.png
Development time

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

video-24px.png
Explanatory video

    • Not applicable

Search-32px.png
Quality Controllers

  • Not applicable

start-flag.png
Initial Context

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

end-flag.png
Resulting context

It has been described in general terms all use cases of the use case diagram of the system, using the format proposed in Craig Larman Method.

cloud.png
Problema

It is desired to create an overview of all use cases diagram, including its type and the actors interacting in 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 [Fuensanta Medina-Dominguez, 2008]
    • 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 representation that is useful to show the client what will be the system's functionality and roles are involved.
    • It has a high level description of the purpose of each use case diagram.

award.png
Maturity level

  • Maturity 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.