System Sequence Diagram

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

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

Box-Out.png
Exit

  • System Sequence Diagrams
    • Can it be used configuration management ?: Yes

Star.png
Solution

process-descending-24px.png
Process

System Sequence Diagram2.png

time-24px.png
Development time

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

video-24px.png
Explanatory video

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 and it wanted to detail more explicitly, the use cases and features of the system they represent.

end-flag.png
Result Context

It has a graphical representation showing a real execution of each use case, with the possible bifurcations and resolved alternatives in particular way.

cloud.png
Problem

It is desired to represent, more explicitly, the intercción of actors (identified in the use case diagram) with the software system being developed from the perspective of each of the use cases.

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

  • None

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
  • UML notiones, especially the technique of modeling use cases and sequence diagrams.

help-24px.png
Abilities

  • Capacity of abstraction.
  • Capacity of Analysis.

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.