%0 Conference Paper %1 kherraf_transformation_2008 %A Kherraf, S. %A Lefebvre, E. %A Suryn, W. %B Software Engineering, 2008. ASWEC 2008. 19th Australian Conference on %D 2008 %K , Language; Unified}, activity, analysts; archetypes; architects; architecture; business, components; computation-independent, data, diagrams; formal, inter-enterprise, model, model-driven, model; modeling, models; platform-independent, platform-specific, processes; processing; requirement, software, specification; system, transformations; {UML2} {requirements; %P 338 --346 %R 10.1109/ASWEC.2008.4483222 %T Transformation from CIM to PIM Using Patterns and Archetypes %X Model transformations form a key part of MDA (model-driven architecture). Most of the studies deal with the transformations from PIM (platform-independent model) to PSM (platform-specific model) and PSM to Code, but very few deal with the transformation from CIM (computation-independent model) to PIM. This last transformation usually depends on business analysts' and software architects' experience and creativity. This paper proposes a disciplined approach to transform a CIM into a PIM. It first uses UML2 activity diagrams to model the business processes up to the users' tasks. The activity diagrams are then detailed to specify the system requirements. The system components are directly deduced from the requirement model elements. Finally, a set of business archetypes helps detail the system components to yield the PIM. The same approach applies equally to CIM and PIM built to model inter-enterprise processes and systems. A case study illustrates our approach. It demonstrates how it reinforces the components traceability and reusability and how it globally improves the modeler's efficiency. Furthermore, the use of the activity diagrams, as a single technique to build business process and requirement models, is an important facilitator which prepares our further work to automate this approach.

@inproceedings{kherraf_transformation_2008, abstract = {Model transformations form a key part of {MDA} (model-driven architecture). Most of the studies deal with the transformations from {PIM} (platform-independent model) to {PSM} (platform-specific model) and {PSM} to Code, but very few deal with the transformation from {CIM} (computation-independent model) to {PIM.} This last transformation usually depends on business analysts' and software architects' experience and creativity. This paper proposes a disciplined approach to transform a {CIM} into a {PIM.} It first uses {UML2} activity diagrams to model the business processes up to the users' tasks. The activity diagrams are then detailed to specify the system requirements. The system components are directly deduced from the requirement model elements. Finally, a set of business archetypes helps detail the system components to yield the {PIM.} The same approach applies equally to {CIM} and {PIM} built to model inter-enterprise processes and systems. A case study illustrates our approach. It demonstrates how it reinforces the components traceability and reusability and how it globally improves the modeler's efficiency. Furthermore, the use of the activity diagrams, as a single technique to build business process and requirement models, is an important facilitator which prepares our further work to automate this approach.}, added-at = {2013-02-28T11:13:35.000+0100}, author = {Kherraf, S. and Lefebvre, E. and Suryn, W.}, biburl = {https://www.bibsonomy.org/bibtex/222c6a4269de1ca9bf547e6319cb17c86/fritzsolms}, booktitle = {{Software Engineering, 2008. {ASWEC} 2008. 19th Australian Conference on}}, doi = {10.1109/ASWEC.2008.4483222}, interhash = {4525e63dd9ddf3542cea26231a938065}, intrahash = {22c6a4269de1ca9bf547e6319cb17c86}, keywords = {, Language; Unified}, activity, analysts; archetypes; architects; architecture; business, components; computation-independent, data, diagrams; formal, inter-enterprise, model, model-driven, model; modeling, models; platform-independent, platform-specific, processes; processing; requirement, software, specification; system, transformations; {UML2} {requirements;}, lccn = {0011}, month = mar, pages = {338 --346}, timestamp = {2013-02-28T11:13:53.000+0100}, title = {{Transformation from {CIM} to {PIM} Using Patterns and Archetypes}}, year = 2008 }