New model transformation using requirement tracebility from requirement to UML behavioral design.

Model transformation (MT) has become an important concern in Software Engineering [1],because it is related to system design.Model transformation can be used in many different application scenarios, for instance, to provide interoperability between models of different size and complexity[2]. Traditionally, model transformations are done for purposes such as code generation, refinement, and refactoring[3].Currently, there are researches on Model Transformation from Requirement to Use Case diagram, Use Case description to Activity diagram and Use Case to Sequence Diagram and many more. However, the research is based on only one specific output and not comprehensive as it should be because it only converts the requirement into one specific Unified Modeling Language (UML)diagram at a time.Transformation model need one important approach ,which is the requirement traceability in order to trace the keywords as input before automatically converted into UML diagram. In this paper, we propose an approach and tool to transform the requirement in to UML model that are Use Case diagram and Activity diagram since there are still not exist the transformation which is required from requirement into behavioral UML diagram called RETRANS.It is different from the existing program because this tool will convert the requirement into two different UML diagrams at a time which is not provided by the existing tool. We have also come out with a framework as the main guidance for developing this project.

[1]  Robert B. France,et al.  Model-driven development using UML 2.0: promises and pitfalls , 2006, Computer.

[2]  Eelco Visser,et al.  Code generation by model transformation: a case study in transformation modularity , 2008, Software & Systems Modeling.

[3]  Boris Roussev,et al.  Generating OCL specifications and class diagrams from use cases: a Newtonian approach , 2003, 36th Annual Hawaii International Conference on System Sciences, 2003. Proceedings of the.

[4]  Khaled Alghathbar.  Enhancement of Use Case Diagram to Capture Authorization Requirements , 2009, 2009 Fourth International Conference on Software Engineering Advances.

[5]  Gabor Karsai,et al.  A transformation instance-based approach to traceability , 2010, ECMFA-TW '10.

[6]  Leilei Kong,et al.  Extension Features-Driven Use Case Model for requirement traceability , 2009, 2009 4th International Conference on Computer Science & Education.

[7]  Lionel C. Briand,et al.  An Automated Approach to Transform Use Cases into Activity Diagrams , 2010, ECMFA.

[8]  Jeanine Souquières,et al.  Modeling class operations in B: Application to UML behavioral diagrams , 2001, Proceedings 16th Annual International Conference on Automated Software Engineering (ASE 2001).

[9]  Nary Subramanian,et al.  Transforming Functional Requirements from UML into BPEL to Efficiently Develop SOA-Based Systems , 2009, OTM Workshops.

[10]  Jane Cleland-Huang.  Just Enough Requirements Traceability , 2006, COMPSAC.

[11]  Houari A. Sahraoui,et al.  Search-based model transformation by example , 2010, Software & Systems Modeling.

[12]  Patrick Valduriez,et al.  Towards the efficient development of model transformations using model weaving and matching transformations , 2009, Software & Systems Modeling.

[13]  Bhuvan Unhelkar,et al.  Challenges in mobile transformations: a requirements modeling perspective for small and medium enterprises , 2005, International Conference on Mobile Business (ICMB'05).

[14]  Krzysztof Czarnecki,et al.  Classification of Model Transformation Approaches , 2003 .

[15]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[16]  Ananya Kanjilal,et al.  Traceability of requirements and consistency verification of UML use case, activity and Class diagram: A Formal approach , 2009, 2009 Proceeding of International Conference on Methods and Models in Computer Science (ICM2CS).