An Object-Oriented Approach to UML Scenarios Engineering and Code Generation

Object-oriented software development matured significantly during the past ten years. The Unified Modeling Language (UML) is generally accepted as the de facto standard modeling notation for the analysis and design of the object oriented software systems. This language provides a suitable framework for scenario acquisition using use case diagrams and sequence or collaboration diagrams. In this paper, we suggest a requirement engineering process that composes UML scenarios for obtain a global description of a given service of the system and implementation code from the UML use case (service). We suggest four operators: sequential operator, concurrent operator, conditional operator and iteration operator to compose a set of scenarios that describe a use case of a given system. We developed algorithm and tool support that can automatically produce a global sequence diagram representing any way of composing them and to offer a code generation of sequence diagram resulting.

[1]  Ivar Jacobson,et al.  The unified modeling language reference manual , 2010 .

[2]  Bruce Powel Douglass Real-time UML - developing efficient objects for embedded systems , 1997, Addison-Wesley object technology series.

[3]  Ivar Jacobson,et al.  Use cases – Yesterday, today, and tomorrow , 2004, Software & Systems Modeling.

[4]  Kurt Jensen Coloured Petri Nets , 1992, EATCS Monographs in Theoretical Computer Science.

[5]  Stephen J. Mellor,et al.  Object lifecycles: modeling the world in states , 1992 .

[6]  Kai Koskimies,et al.  Automated Support for Modeling OO Software , 1998, IEEE Softw..

[7]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

[8]  Jesús Manuel Almendros-Jiménez,et al.  Describing Use-Case Relationships with Sequence Diagrams , 2007, Comput. J..

[9]  Jiro Tanaka,et al.  An Object-Oriented Approach To Generate Java Code From UML Statecharts , 2005 .

[10]  Constance L. Heitmeyer,et al.  SCR*: A Toolset for Specifying and Analyzing Software Requirements , 1998, CAV.

[11]  Bruce Powell Douglass,et al.  Real-time UML (2nd ed.): developing efficient objects for embedded systems , 1997 .

[12]  H. Ohno,et al.  (Ga,Mn)As: A new diluted magnetic semiconductor based on GaAs , 1996 .

[13]  Henri Briand,et al.  An approach based on the concept of use case to produce dynamic object-oriented specifications , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[14]  Kurt Jensen,et al.  Coloured Petri Nets: Basic Concepts, Analysis Methods and Practical Use. Vol. 2, Analysis Methods , 1992 .

[15]  H. Ohno,et al.  Zener model description of ferromagnetism in zinc-blende magnetic semiconductors , 2000, Science.

[16]  Marc Frappier,et al.  Integration of sequential scenarios , 1997, ESEC '97/FSE-5.

[17]  Jiro Tanaka,et al.  Converting Statecharts into Java Code , 2001 .

[18]  Ismaïl Khriss,et al.  Automated Prototyping of User Interfaces Based on UML Scenarios , 2006, Automated Software Engineering.

[19]  M. Jarke,et al.  A proposal for a scenario classification framework , 1998, Requirements Engineering.

[20]  A. Jakimi,et al.  Use Cases and Scenarios Engineering , 2007, 2007 Innovations in Information Technologies (IIT).

[21]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[22]  A. Jakimi,et al.  Unified model of interaction: use cases and scenarios engineering , 2008 .

[23]  Jiro Tanaka,et al.  An Object Oriented Approach to Generate Executable Code from the OMT-based Dynamic Model , 1998 .

[24]  Jiannong Cao,et al.  Model-Based Generation of Java Code , 2000, PDPTA.