System Sequence Diagram
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.
It has a graphical representation showing a real execution of each use case, with the possible bifurcations and resolved alternatives in particular way.
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.
- Type of Organization: SMEs, Large Companies.
- System Type: It applies to all types of systems.
- Programming Paradigm: OO (Object Oriented).
- Definition of software requirements (functional and non-functional).
- Craig Larman Method
- UML notiones, especially the technique of modeling use cases and sequence diagrams.
- 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.