Home

Installation instructions and user manual

1. General H Debug E e Help H Java H Java Browsing Method Authoring B Method Execution MOSKILRAME Guides 4 MCOSEIEL4ME Process om MOSKitt4ME Product Explorer gt MOSEI E e Team Use Fe to display the description For a selected view The Guides view aims to provide software engineers with guidelines on the performance of the method tasks Specifically the Guides view shows the SPEM 2 0 elements of type Guidance associated to the task selected on the Process view In order to see the content of the guidance the user must double click the guidance elements This action opens the Content view provided by the EPF Composer which provides an HTML representation of the guidance contents 7 f v MOSKitt4 ME Process lt VOSKETSIVIE Guides X B a g Titis EI ER O UML Class Model Specification Information System Design ee Key Concepts S P Business Logic Design B7 a Se 2 Creation Process Description J Data Persistence Design D Database Model Generation BD Database Model Revision Fa D Database Scripts Generation ki a N eoesgera k Example Class Model Example Class Model Example This guidance provides a sample instance of the output work product in order to illustrate how the task can be performed Expand All Sections Collapse All Sections Description Attached Files e exampleClassModel uml e exampleCl
2. To solve the dependency errors the user can add remove technical fragments in the dependencies tree by means of the Add Dependency and Remove Dependency buttons The Add Dependency button creates a new technical fragment and adds it to the tree as a child of the fragment that is selected Thus the child fragment represents a dependency of the parent fragment i e the parent fragment requires the use of the child fragment for its correct operation On the other hand the Remove button allows the user to remove the fragment that is selected in the dependencies tree and also all its nested fragments In addition the user can establish dependencies between technical fragments by means of the Import button This button opens the Import technical fragment dialog which allows the user to import technical fragments from the repository When a fragment is imported it is added to the dependencies tree as a child of the selected fragment Note that unlike regular fragments the icon of the imported fragments contains a yellow arrow This arrow represents that these fragments are references to fragments that already exist in the repository Import Technical Fragment Repository fragments 4 DatabaseEditor J DB2DDL_Transformation J EMFT 4 Fefern GlossaryMetamodel h JDT 6 Launcher 4 SketcherEditor TrManager 6 UIMEditor Create Technical Fragment Dependencie
3. Install New Software from the Help menu Then push the Add button to add the MOSKitt4ME update site and follow the wizard to install the tool It is important to activate the checkbox Contact all update sites during install to find required software so that all the MOSKitt4ME dependencies can be resolved during the installation One of these dependencies is Graphiti https eclipse org graphiti it is important to add the Graphiti update site in the same way as the MOSKitt4ME update site so that this dependency can be resolved during the installation process MOSKitt4ME has been tested using Graphiti 0 7 3 The operating system was Windows 7 http www moskitt org Install Available Software Check the items that you wish to install Work with eo awww pros upv es moskithtme Updates Ww Find more software by working with the Available Software Sites preferences Mame Version E e UUU Meorskitt4 Me Pal MosSkitt4ME 1 0 0 201304291149 Details Show only the latest versions of available software Hide items that are already installed Group items by category What is already installed Contact all update sites during install to Find required software lt Back Finish Install Install Details Review the items to be installed Version Ay PI SEICESHE 1 0 0 201304291149 Size Unknown Details Modeling Software KIT MOSKItE is a FREE CASE tool built on Eclipse whi
4. Expand All TE Open Activity Diagram Collapse All Preferences Open Work Product Dependency Diagram If the BPMN 2 0 processes have not been previously generated click OK on the dialog that appears New Diagram File No Activiti Designer diagram exists For this process Do you want bo create a new ones i Cancel This action generates a BPMN 2 0 process for each SPEM 2 0 activity For instance the BPMN 2 0 process generated for the Data Persistence Design activity is the following lt u Activiti Diagram Editor 22 Database Model Ge Database Model Fe Database Scripts G Note that each BPMN 2 0 task corresponds to a SPEM 2 0 task In addition BPMN 2 0 call activities are created to connect all the processes that are generated The Activiti Designer is the editor that has been integrated in MOSKitt4ME to support BPMN 2 0 By means of this editor method engineers can manually modify the generated processes For instance they can add BPMN 2 0 gateways to enhance the process workflows In addition to the Open BPMN 2 0 Diagram action MOSKitt4ME also provides the Delete BPMN 2 0 Diagram action which deletes the generated BPMN 2 0 processes irs InformationSystemDesign 5 Presentation Mame Index Predecessors Model Info Type Planned Repea Multipl B FS Information System Design i a A Delivery Pro ER E E amp 2 Business Logic Design New Child i Activ
5. PQS itt Introduction Installation and User Manual Version 1 0 Contents L NPC IVI SCC VIER er E E E E E A E 3 1 1 MOSKItAME ArchItecCtUrE socrii aree Eer ER A E 3 2 MOSKRA ME INSCAMALION eca E 5 3 Ine CAME Partof MOSKA ME serrer rE E NS 7 AL MEOT EUKO ae o E A E E E A E E A 7 Da REPOS KOY CIEN oeer a 14 3 3 SPEM2BPMN TranstormatiON wicisscesececnsavicoansdptccsnainiausecaneensnssniaveesbeteadnssnucesmenntantersuacesncens 34 sA TOON ONO O eE E E ENEA 37 4 The CASE Part of MOSKItt 4ME cccccccssssssssseccccesscnsssssecccccssenasssseccccesseaansesessccesseaansssecsees 41 41 Project VIAN ACC aiae EEE 41 Appendix A Building the Eclipse plug ins ssssssssssssenssrrrsesrrressreresrrresrrressrrressrersserresrrereserresene 51 1 What is MOSKitt4ME MOSKitt4ME is a Computer Aided Method Engineering CAME environment developed by researchers from the Centro de Investigacion en M todos de Producci n de Software PROS at the Universitat Polit cnica de Val ncia UPV MOSKitt4ME allows method engineers to define software development methods and also to semi automatically obtain Computer Aided Software Engineering CASE environments supporting the method execution To this end MOSKitt4ME makes intensive use of Model Driven Engineering MDE techniques such as meta modeling model transformations and models at runtime 1 1 MOSKitt4ME Architecture MOSKitt4ME CAME Method Editor SPEM2BPMN Modelin
6. Origin Microsoft Office 2013 Objective This tool supports the creation of textual documents Input None Output Textual documents File Extension doc This technical fragment represents an external tool that will not be included in the generated CASE environment In order to have software support for the tasks that require the use of this tool the Microsoft Office 2013 tool surte must be installed in the systern Description Cancel Specifically the Define external tool dialog allows the user to specify the properties name origin objective input and output These properties are equivalent to the properties of the technical fragments described above Additionally the following properties must be defined File Extension this property represents the extension of the files that will be created by means of the external tool The main purpose of this property is to be used by the operating system as a way to identify the software tool that must be launched during the method execution In the example of the above figure the doc extension identifies Microsoft Word as the tool that must be invoked for the creation of the products that are associated to the external tool Description this property provides a textual description of the external tool Typically this property must contain information that can be used by software engineers to configure the system so that the external tool is available during t
7. are completely defined users must obtain executable representations of the method processes The SPEM2BPMN transformation automates this task Specifically the SPEM2BPMN transformation automatically obtains BPMN 2 0 processes from the SPEM 2 0 model Complementing the SPEM 2 0 method definition with BPMN 2 0 has two main advantages First BPMN 2 0 is an executable language and thus the method becomes executable by a BPMN 2 0 process engine Second users can manually modify the BPMN 2 0 processes to specify workflows more complex than those supported by SPEM 2 0 For instance users can manually add gateways which cannot be represented in SPEM 2 0 In order to invoke the SPEM2BPMN transformation open the contextual menu of the root element and select Diagrams gt Open BPMN 2 0 Diagram fy InformatiansystemDesign 2 5 Presentation Mame Index Predecessors Model Info Type Planned Repea Multipl E Information System Design i Delivery Pro B Eo Eo z pA Business Logic Design Mew Child Activity E Ces UML Class Model Specification Add From Method Content Task Descrip E E E LI i L L E L E L E L E E E E oF Data Persistence Design Apply Pattern d Activity Ce Database Model Generation Suparess Task Descrip Les Database Model Revision Task Descrip C Suppress Tasks Database Scripts Generation Task Descrip Update Suppression From Base Roll Up Diagrams d Open BPMN 2 0 Diagram
8. information about the tools that could not be installed in the CASE environment Microsoft Word supports the creation of textual documents This tool cannot be installed in the CASE environment since it is not implemented as Eclipse plug ins In order to have software support for the tasks that require its use the Microsoft Office 2010 toolsuite must be installed in the system Number of tools that have been successfully installed in the CASE environment 6 of 7 85 7 length 563 lines 14 Ln 3 Col 14 Sel 0 4 The CASE Part of MOSKitt4ME The CASE environments that are generated by means of the CAME part of MOSKitt4ME provide software support for software engineers performing software development projects These CASE environments guide them throughout the development process and also partially automate the process performance All this functionality is made available through a component called Project Manager This component is detailed in the next subsection 4 1 Project Manager The Project Manager can be accessed by opening the Method Execution perspective This perspective can be opened by means of the Open Perspective dialog available at Window gt Open Perspective gt Other Open Perspective Browsing F Debug G avMetrica bl Java d Java Browsing fel java Type Hierarchy T Method Design Method Execution M moskitt Resource default eo Team Synchronizing When the Met
9. manipulat i org eclipse jdt debug 0 org eclipse jdt debug ui 0 org eclipse jdt doc isy org eclipse jdt doc user aftr Po rrn ed ee volt Te os r i a Specifically the Define internal tool dialog allows the user to specify the properties name origin objective input and output These properties are equivalent to the properties of the technical fragments described above Additionally the following properties must be defined Description this property provides a textual description of the internal tool Typically this property must contain information that can be used by software engineers during the method execution Plugins this property defines the Eclipse plug ins that implement the internal tool To specify these plugins the Define internal tool dialog provides a graphical component that allows the user to select the plug ins from the whole MOSKitt4ME platform Conceptual Fragments In order to add new conceptual fragments to a repository the Repositories view provides the Create conceptual fragment action of the contextual menu Ii EADE Refresh Discard location Create conceptual fragment Create technical fragment Define external tool 3 Define internal tool The Create conceptual fragment action opens the following dialog Name DatabaseModelSpecification Type Task Origin gyMetrica Objectiwe This task in
10. on the MOSkKitt Resource Explorer view the Project Manager automatically invokes the Activiti Engine which returns the current state of the process instance associated to the project The view in charge of showing this process instance is the Process view By default the Process view only shows those tasks that are executable at the current state of the process These tasks and their parent activities are displayed in green 4 MOSKitt4ME Process es E Selected roles lt None gt amp 7 LS UML Class Model Specification To see all the activities and tasks of the process users can make use of the All Tasks action of the toolbar L This action acts as a toggle button When the button is deactivated the Process view only displays the executable tasks i e the tasks that can be performed in the current state of the process When it is activated all the tasks of the process are displayed In this case non executable tasks are displayed in red executable tasks are displayed in green and the tasks that have already been executed are displayed in blue The color of the activities depends on their nested tasks and sub activities An activity is shown in blue if and only if all its tasks and sub activities have already been executed On the other hand the activity is shown in red if and only if all its tasks and sub activities are non executable Otherwise the activity is shown in green 13 http www a
11. shows a hierarchical representation of the method products that have been created for the project This hierarchy is based on the elements of type Domain and Work Product defined in the SPEM 2 0 method model In SPEM 2 0 domains are defined as hierarchies grouping related work products Domains can be further divided into sub domains with work product elements at the leaf level of this hierarchy Based on this idea the Product Explorer view shows the domains defined in the method and the sub domains and work products contained in these domains Also the Product Explorer shows the files that represent each particular work product SS MOSKitt4ME Product Explorer 3 a Oo Selected roles lt None gt Do Products of project ExperimentProject Fo Models lt B UML Class Model Domains classmodel uml Work Id classmodel uml_diagram F DB Model IN database sqlschema d database sqlschema_diagram io Files Products In a similar way to the Process view the Product Explorer view can also be filtered by role Specifically if one or more roles are selected in the Process view the Product Explorer view only shows the products that are output of the tasks assigned to the selected roles Guides and Help views The Project Manager of MOSKitt4ME also provides the Guides view which can be opened by means of the Window menu Show View gt Other
12. that will support them during execution The repository client also allows users to create and store new technical fragments developed as Eclipse plug ins by means of MOSKitt4ME On the other hand conceptual fragments are reusable method parts such as tasks roles or work products The repository client allows user to create and store conceptual fragments and also to retrieve them in order to facilitate the construction of new methods e SPEM2BPMN Transformation this component provides a Model to Model M2M transformation that automatically obtains executable representations of SPEM 2 0 models These executable representations are defined in terms of the BPMN 2 0 standard e Tool Generator this component allows method engineers to obtain Eclipse based applications supporting the execution of the methods defined by means of the Method Editor The construction of these Eclipse based applications is supported by the Java Development Tools JDT and automated by the Plug in Development Environment PDE The applications that are produced by the Tool Generator constitute the CASE part of the MOSKitt4ME architecture CASE part The CASE part of MOSKitt4ME provides software support to the execution of the methods defined in the CAME part The software components that comprise the CASE part are the following e Project Manager This component provides a set of Eclipse views that assist software engineers during the execution of methods Th
13. ain as not started This means that subsequent execution requests will have again the same effect as if the task had never been executed The Process view also provides support to task filtering based on the role performed by the user To select a specific role users can make use of the Role Selection action of the toolbar E Similarly to the All Tasks action this action acts as a toggle button When the button is deactivated tasks are not filtered When it is activated tasks are filtered based on the selected roles The role selection is performed by means of the Role Selection dialog Role selection f System For instance if the Analyst role is selected the Process view only shows the tasks performed by this role note that the toolbar always shows the roles that are selected eee MOSKItt4ME Process 3_ Re Information System Design DS Business Logic Design D UML Class Model Specification Data Persistence Design D gt Database Model Revision Selected roles Analyst The Process view also provides support to returning to previous states of the process by means of the Undo action of the toolbar This action allows the user to go back in the process execution but does not delete the files that have already been created Product Explorer view When a project is selected on the MOSKitt Resource Explorer view the Product Explorer view
14. an pn Define internal tool This action opens the Define internal tool dialog which allows the method engineer to specify the properties of the internal tool Define Internal Tool Name Origin JDT Eclipse Objectrve This internal tool supports the development of any Java application Input None Output Java Applications Description The Java Development Tools DT project provides the tool plug ins that implement a Java IDE supporting the development of any Java application including Eclipse plug ins It adds a Java project nature and Java perspective to the Eclipse Workbench as well as a number of views editors wizards builders and code merging and refactoring tools The JOT project allows Eclipse to be a development environment for itself Plug ins Platform plug ins ah com collabnet subversion me com google collect com google guice com ibm icu comjcraftjsch com lowagie itext com onpositive richtexteditor com onpositive richtexteditor com sun jna es cv gvcase mdt common gr es cv gvcase mdt common gr java_cup runtime aftr a a pee ep nm Internal tool plug ins i org eclipse jdt i org eclipse jdt apt core i org eclipse jdt apt pluggable c org eclipse jdt apt ui m org eclipsejdt compiler apt i org eclipse jdt compiler tool e org eclipse jdt core 0 org eclipse jdt core
15. an be created by means of the contextual menu of the Library view Eh Library es eee a m Configurations 6 Generate CASE Tool New Method Plug in Open via variability elements Show in Resource Navigator Refresh Method plug ins contain content packages which define method content and process packages which define processes BA Library 3 es Oo lt gt ExperimentPlugin lt Method plugin BA Method Content a Content Packages lt Content BA contentPackage LS Roles packages Tasks cS Work Products L Guidance L Standard Categories e Custom Categories iS Processes EJ Capability Patterns Process H fa Delivery Processes packa ges Configurations In content packages and process packages new elements can be added and existing elements can be deleted by means of the contextual menu viai gle 720 lt gt ExperimentPlugin BA Method Content en Content Packages BA contentPackage ele Ol gt ExperimentPlugin E S Method Content a Content Packages BA contentPackage CB Roles CB Roles amp analyst amp Analyst Fi System a System O B4 Tasi SA Tasks D D Database Model EET D Database Model Re Generate CASE Tool Database Scripts G New Method Plug in D UML Class Model Sp D Generate CASE Tool New Method Plug in Edit o G8 wor Eg S GR Work Products BB cor DB Model Sopy f Paste DDL Scripts P
16. ase Refresh Discard location Create conceptual fragment Create technical fragment Define external tool Define internal tool Technical Fragments In order to add new technical fragments to a repository the Repositories view provides the Create technical fragment action of the contextual menu Refresh Discard location Create conceptual fragment Create technical fragment Aig 23 RD Define external tool h Define internal tool The Create technical fragment action opens the following dialog Create Technical Fragment Dependencies Tree E NewTechnicalFragment Add Dependency Remove Dependency Cancel The Create technical fragment dialog allows the user to create new technical fragments and also to specify their dependencies with other fragments A dependency relationship between two technical fragments F1 and F2 is an unidirectional association that implies that F1 requires F2 for its correct operation Dependency relationships form dependency trees where nodes represent technical fragments and all the descendants of a node represent its dependencies Thus the Create technical fragment dialog supports the creation of technical fragments by means of a Tree Viewer that represents a dependencies tree This dependencies tree initially contains one technical fragment which is the root of the tree and also allows the user to add additional fragments representing its s
17. assModel uml_diagram Back to top As another type of guidelines the Project Manager also provides support to the Eclipse dynamic context help which is shown in the Help view provided by Eclipse Specifically when a task is selected in the Process view the Project Manager obtains the technical fragments of type Guidance that are associated to this task Then the guidelines contained in these fragments are displayed in the Help view 8 Related Topics Definition of UML 2 0 Class diagrams blag n eee i Contextual help for the specification of class diagrams in Y Business Logic Design the Unified Modeling Language version 2 0 gt Be ene 3 A class diagram is a type of static structure diagram that otas Oeta Porsktanca Dogn describes the structure of a system by showing the D Database Model Generation system s classes their attributes operations or gt Database Model Revision methods and the relationships among the classes D Database Scripts Generation See also B Classes attributes and operations B Associations and cardinality B Inheritance More results 2P Search For Definition of UML 2 0 Class diagrams Go To Contents Search lll Bookmarks FA Index Appendix A Building the Eclipse plug ins MOSKitt4ME is an Eclipse based CAME environment that supports the development of Eclipse plug ins that can be encapsulated as reusable software assets i e the technical frag
18. aste UML Class Model B Guid 3 Delete a ren Delete LS Standard C CS Standard Categories Rename CS Custom Cati CS Custom Categories Move iS Processes Refresh O S Processes Open via variability elements 3 ek Capability Pa E3 Capability Patterns Show in Resource Navigator B A Delivery Processes E Information System Design validate Configurations fa Delivery Processes R Information System Design Configurations Refresh The properties of the method content elements can be edited by means of form based editors that are opened by selecting Edit on the contextual menu or double clicking the method content elements gt databaseModelGeneration 2 Task databaseModelGeneration Serer Assign the roles to perform this task Primary performers fz system ExperimentPluginfcontentPackage aM Additional performers 4 Description Steps Roles Work Products Guidance Categories Preview These form based editors provide different tabs which allow the user to edit different types of properties For instance the Roles tab of the editor that is opened for tasks see image above allows setting the performing roles of the tasks Unlike method content elements processes are defined by means of a process editor which is also opened by selecting the Edit action or double clicking the process elements rs InformationSystemDesign Presentation Name Index P
19. cal fragment To specify the plugins that will be contained in the fragment the Edit technical fragment dialog provides a graphical component that allows the user to select the plug ins from the MOSKitt4ME workspace In appendix A we provide further details about how these Eclipse plug ins must be developed since they have to meet a set of requirements depending on the type of tool they implement all these properties are specified errors may appear due to software dependencies That is the plug ins of the technical fragment may require other plug ins that are not included in the fragment In order to see the errors of a technical fragment the user can place the cursor over the fragment area in the dependencies tree Create Technical Fragment Dependencies Tree er GlossaryEditor This technical fragment has the following errors Unsatisfied dependency es cv gvcase qvm glossary formseditor gt es cv gvcase qvm glossary editor Unsatisfied dependency e5 cv gvcase gvm glossary formseditor gt es cv gvcase fefem common Unsatisfied dependency es cv gvcase qvm glossary formseditor gt es cv gvcase emf common Unsatisfied dependency es cv gvcase gqvm glossary navigator gt es cv qvcase ide navigator Unsatisfied dependency es cv gvcase gvm glossary navigator gt es cv gvcase gvm glossary edit Unsatisfied dependency es cv gvcase gvm glossary navigator gt es cv qvcase ide core Cancel
20. ch is being developed by the Valencian Regional Ministry 3 The CAME Part of MOSKitt4ME The installation of MOSKitt 4WME adds the CAME part to MOSKitt As described in section 1 this part is composed of the following software components 1 the Method Editor 2 the Repository Client 3 the SPEM2BPMN transformation and 4 the Tool Generator These components are detailed in the next subsections 3 1 Method Editor The Method Editor of MOSKitt4ME can be accessed by opening the Method Design perspective This perspective can be opened by means of the Open Perspective dialog available at Window gt Open Perspective gt Other Open Perspective 0 Activiti Browsing Bacs Repository Exploring EJ Database Debug is Database Development F Debug D Ecore G av Metrica a Java Gd Java Browsing fet Java Type Hierarchy P Method Design moskitt H Nebula s Plug in Development s When the Method Design perspective is opened the MOSKitt4ME workbench is organized in three different parts Method Design MOSKitt File Edit Navigate Search Project MOSKittRedmine Run Window Help By Qa Qa is aw E3 Method Design A Moskitt Resource Configuration 2 1 The Library view offers a hierarchical view of the elements that compose the method under construction 2 The Configuration view only shows some of the method elements that is it provides a mechanism for defin
21. cific category The types that can be specified by means of the Fdit technical fragment dialog are Graphical Editor Meta Model Form based Editor Model Transformation Guidance and Others In addition to these types MOSKitt4ME also supports two other types of technical fragments External Tool and Internal Tool The main difference between the technical fragments that can be created by means of the Create technical fragment dialog and external internal tools is that the latter do not encapsulate Eclipse plug ins External and internal tools will be detailed at the end of this section Origin this property establishes where the tool contained in the technical fragment originates from For instance a software tool can represent a specific software component extracted from the MOSKitt platform Objective this property defines the goal that the technical fragment helps to achieve Input this property establishes the requirements needed to execute the software tool contained in the technical fragment For instance the input of a model transformation is its input model Output this property defines the artifacts that can be produced by means of the software tool contained in the technical fragment For instance the output of a model transformation is its output model Plugins this property defines the Eclipse plug ins that implement the software tool encapsulated in the techni
22. criptors Task descriptors can be added by means of the contextual menu He InformationSystemDesign 3 Index Presentation Mame E ran Information System Design 0 EJ Business Logic Design Ce UML Class Model Specification 2 Les Date Predecessors Model Info T Phase T Mew Sibling HES Iteration T Add From Method Content Be Activity Ti AER PARE F Task Descriptor Suppress Eh Milestone Suppress Tasks T Update Suppression from Base Once a task descriptor is created it can be linked to a specific task via the Properties view gt General tab gt Link Method Element button E Properties 52 Us Task Descriptor General Documentation Guidance Roles Work Products Steps General Information Provide general information about this task descriptor Name _taskDescriptor1 Presentation name taskDescriptor 1 C Optional Event Driven Dependency Method task C Multiple Occurrences C Ongoing Index Presentation Name _ Planned C Repeatable Dependenc A Link Method Element Work product descriptors and role descriptors are automatically created according to the roles and work products that are associated to the task in the content packages Work product descriptors and role descriptors can als
23. ctiviti org E MOSKItt4ME Process 325 E Selected roles lt None gt A 8 3 R Information System Design 5 ay Business Logic Design gt UML Class Model Specification E Data Persistence Design L gt Database Model Generation gt Database Model Revision gt Database Scripts Generation Displaying tasks in different colors represents a useful guidance for software engineers since it tells them which tasks must be executed based on the current state of the project To execute a specific task software engineers must double click the executable task in the Process view Then different possibilities exist e If the task is associated to a model transformation then the Project Manager launches the execution of the transformation e Ifthe task is not associated to a model transformation there are six cases O If the task has an output work product that has an editor associated to it the Project Manager opens the wizard that enables the creation of an empty model for that editor If the task has an output product with an associated meta model the Project Manager opens the wizard that enables the creation of an empty model editable by means of the default tree based editor for that meta model If the task has an output product with an associated external tool the Project Manager creates a new file The extension of the file name will be the extension stored in the technical fragment representing the exter
24. defines the purpose of the element contained in the conceptual fragment Content this property defines the method elements encapsulated in the conceptual fragment To specify the elements contained in the fragment the Create conceptual fragment dialog provides a graphical component that allows the user to select the elements from the Method Library that is opened in the Method Editor This graphical component only shows the elements that can be contained in the fragment according to the type of fragment that is selected For instance if the type of fragment that is selected is Task then the graphical component only shows the tasks defined in the Method Library In a similar way to technical fragments the conceptual fragments that are created by means of the Repositories view are shown as children of the repository location 10 http www gvpontis gva es fileadmin conselleria images Documentacion migracionSwAbierto gvMET RICA introduccion gvMetrica_Introduccion htm i e I gt gt qap BusinessLogicDesign ras gt ie DatabaseModelSpecification ras gt aie Designer ras gt ie GlossaryModel ras gt qir UMLClassModel ras a KARE Also the Repositories view allows method engineers to examine the fragment properties These properties can be used to select the most appropriate method element for the method under construction P Up DatabaseModelSpec
25. e execution of methods is automated by a process engine which orchestrates the method tasks and also invokes the software tools that enable the creation and manipulation of the method products e Software tools The creation and the manipulation of the method products are supported by a set of software tools i e technical fragments which are represented in the figure above as Tool 1 Tool2 Tool n that the Tool Generator retrieves from the FTP repository and integrates in the CASE environment The Tool Generator only integrates the tools that are strictly necessary to support the method defined by means of the Method Editor is http www omg org spec BPMN 2 0 gt http www eclipse org jdt http www eclipse org pde 2 MOSKitt4ME Installation MOSKitt4ME has been conceived as an extension of the Eclipse based MOSKitt tool In order to install MOSKitt4ME in MOSKitt the following steps must be performed Step 1 Download MOSKitt 1 3 10 from http www moskitt org eng offt moskitt descargas The installation details of MOSKitt can be found at http www moskitt org eng manuales Problems downloading MOSKitt MOSKitt4ME also works on Eclipse so an alternative is to download Eclipse Modeling Tools Galileo and then proceed to Step 2 Step 2 Install MOSKitt4ME from the following update site htto www pros upv es moskitt4me Updates To install MOSKitt4ME from this update site open MOSKitt or Eclipse and select
26. eModelGeneration gt databaseScriptsGeneration O umlClassModelSpecification gt databaseModelRevision E m Work Products ETA UMLclassmodel aa DEmodel ia DDLscripts Cancel Note that only tasks and work products can be selected in this dialog since these are the only elements that can be associated to software tools Specifically tasks can be associated to model transformations and guidance and work products to editors meta models and external internal tools When a task or a product is chosen it is associated to the technical fragment selected in the Repositories view This association is performed by means of the creation of a new element of type Tool Mentor which is automatically displayed on the Library view under the Guidance folder BA Library 52 2 S yY oo E pBmedel 3 gt ExperimentPlugin Work Product Artifact DBmodel BA Method Content l Content Packages v Guidance BA contentPackage Provide links to additional information in the form of quidanck 4 CB Roles HE Tasks Guidance GR work Products Database_Editor ExperimentPlugin contentPackage C DBmodel E DDLscripts Product aa a Association A UMLclassmodel Guidance Database_Editor lt To ol L2 Standard Categories CS Custom Categories Mentor Processes bel Capability Patterns fa Delivery Processes B InformationSystemDesign CE Configurations Brief description of selected element I
27. e_formularios 17 http www eclipse org swt 18 http wiki eclipse org JFace 19 g http www eclipse org atl 2 http www eclipse org modeling m2t project xpand specification and invocation of model transformations and also implements a graphical user interface to make these transformations available in the MOSKitt workbench In the declaration of the transformation by means of the extension point the user must provide a Java class extending the class Transformation of the plug in es cv gvcase trmanager This class is an abstract class that declares two abstract methods transform and inputsValid The first method must implement the invocation of the transformation The second method must implement validation rules for the input model of the transformation Guidance Contextual help can be developed in MOSKitt4ME by means of the HTML and XML languages In order for this help to be compatible with MOSKitt4ME the Eclipse plug in s that implement the help must make use of two extension points 1 2 21 The org eclipse epf authoring ui helpcontextprovider extension point must be used to declare a help context identifier This context identifier will be passed to the Eclipse Help view when the task associated to the Guidance fragment is selected in the MOSKitt4ME Process view The org eclipse help contexts extension point must be used to declare a contexts xml fi
28. ecci n Cr CaseToollmaskitt Tareas de archivo y carpeta mm configuration Features me pz cg Crear nueva carpeta 2 Publicar esta carpeta en Web e artifacts eclipse l plugins Documento MIL Opciones de configuraci n Ea Compartir esta carpeta corer 1 KB Otros sitios Q MOSKitE i CaseTool G Mis documentos Cy Documentos compartidos ig MiPc aj Mis sitios de red In addition to the CASE environment the generation process also produces a generation report This report contains information about the number of tools that are successfully installed in the final CASE environment and how software engineers must proceed to obtain full software support for the method In general all the software tools that are implemented as Eclipse plug ins can be installed in the final CASE environment Therefore the generation report contains information that refers to the external tools CaseTool Archivo Edici n Yer Favoritos Herramientas Ayuda Q Atr s v7 wi P B squeda Key Carpetas 3 A Sincronizaci n de carpetas Direcci n 0 C CaseTool i generationReport Tareas de archivo y carpeta y a moskitt pa repository Documento de texto 1 KB Otros sitios E C Case TooligenerationReport txt Notepad Archivo Editar Buscar Yer Formato Lenguaje Configurar Macro Ejecutar TextFX Plugins Yentanas SARE SRA E a O A Ae eae BE BBIDIFS OAMOMB FearZzey generationRepott txt This file provides
29. g Tools EMF GEF O PDE Eclipse Platform Runtime MOSKitt4ME CASE Repository Repository cli Tool Generator FTP ient Project Manager Eclipse Platform Runtime Eclipse Eclipse MOSKitt4ME is built on Eclipse and is composed of two main parts the CAME part and the CASE part CAME part The CAME part of MOSKitt4ME allows method engineers to define software development methods The software components that comprise the CAME part are the following e Method Editor the main goal of the method editor is to support the creation and manipulation of method models Since MOSKitt4ME has been developed as an Eclipse based application this component builds on the Modeling Tools provided by Eclipse Thus the method editor supports the creation and manipulation of models that instantiate an Ecore meta model The meta model that has been defined in the method editor corresponds to an Ecore representation of the SPEM 2 0 standard http www eclipse org http www eclipse org modeling http www omg org spec SPEM 2 0 e Repository Client this component allows method engineers to connect to FTP repositories containing method fragments that can be of two types conceptual or technical Technical fragments encapsulate tools such as graphical editors and model transformations By means of the repository client method engineers can associate the elements of the methods with the technical fragments
30. he method execution This information will be made available to the software engineer by means of a report that will be produced during the CASE environment generation process Internal tools Another type of technical fragment are the internal tools An internal tool is a tool that is already installed in the CAME part of the MOSKitt4ME environment for instance a specific component of MOSKitt such as the Transformation Manager or FEFEM or an Eclipse framework such as the Graphical Modeling Framework or the Java Development Tools Unlike external tools these tools are implemented as Eclipse plug ins Nonetheless since these tools are already installed technical fragments representing internal tools do not need to encapsulate the plug ins but rather contain references to them One important advantage of internal tools is that they are not subject to the same requirements as regular technical fragments see appendix A Therefore they can represent any type of software tool that can be conceived as Eclipse plug ins The disadvange is that the Project Manager of MOSKitt4ME will not be able to launch them automatically when the method is being executed The definition of internal tools can be performed in MOSKitt4ME by means of the Define internal tool action of the contextual menu Repositories 3 Bsa E mario localhost AssetBase Refresh Discard location Create technical fragment A A R p E Define external tool
31. he process fragment will not be included in the process but rather copied separately and referenced If Copy is selected all the content of the process fragment will be copied into the selected process element Process Fragment Integration Process Element Selection Select the element of the process where the process fragment will be integrated a i ISD a fe ISDProcess les DataPersistenceDesign Select the integration type Extend Finish Cancel In the second step of the wizard the user must select the process package where the process contained in the process fragment will be stored If the process already exists in the package the process will not be copied In this case the third step of the wizard is omitted Process Fragment Integration Process Package Selection Select the process package where the proccess fragment will be stored a 4 ISD 4 bo CapabilityPatterns am ISD_process _package In the third step of the wizard the user must select a content package of the method library In this package the content elements referenced by the process fragment will be stored Process Fragment Integration Content Package Selection Select a content package for the content elements referenced by the proccess fragment a 3 ISD BA ISD_content_package ISD_content_package_2 ISD_content_package_3 Finish 3 3 SPEMZBPMN Transformation Once the method and its supporting tools
32. he properties of the technical fragments These properties can be used to select the most appropriate tool for each particular method element a UMLEditorras 4 amp Descriptor Type Graphical Editor gt i Origin MOSKitt Objective This editor enables the creation of UML 2 0 models a Interface Input None gt Output EMF models based on the UML 2 0 standard metamodel In order to facilitate the search of appropriate tools the Repositories view provides the Search action in the toolbar This action opens the Search dialog Type Origin Objective Input Output The Search dialog allows the user to enter different values for the properties of the fragments Then the Repositories view is filtered to show only the fragments that match the specified properties Thus the Search action acts as a toggle button When it is activated the Repositories view only shows the fragments matching the property values that have been specified When it is deactivated no filter is applied and therefore all the fragments are displayed Once a technical fragment is selected the Integrate Technical Fragment action can be used to associate a specific method element with the selected tool The method element can be selected by means of the Task Work Product selection dialog Task Work Product Selection ER a e e a E S contentPackage E E Tasks L gt databas
33. hod Execution perspective is opened the MOSKitt4ME workbench is organized in four different parts Method Execution MOSKitt File Edit Navigate Search Project MOSKittRedmine Run Window Help R Q igr FY Method Execution L Resource E y J L MOSKitt Resource Explorer 3 gt MOSKItt4ME Process 3 Selected roles lt None gt 30 gt MOSKItt4ME Product Explorer 2 Selected roles lt None gt 0 items selected The MOSKitt Resource Explorer provides a view of the workspace This view is hierarchically organized in projects folders and files From the MOSKitt Resource Explorer software engineers can create new projects delete existing projects add files to these projects etc The Process view shows the current state of the process instance associated to the project that is selected in the MOSKitt Resource Explorer view From the Process view software engineers can invoke the execution of the tasks that are executable at the current state of the process Once a task is finished the Project Manager invokes a process engine that sets the task as executed and proceeds to the next state of the process The Product Explorer view shows a hierarchical picture of the artifacts that have been produced during the course of the project that is selected in the MOSKitt Resource Explorer view This hierarchy is based on domains subdomains and work product elements which are obtained from the SPEM 2 0 mode
34. ification ras 4 amp Descriptor Type Task gt Origin qvMetrica Objective This task involves the creation of a graphical model of a database schema Once a conceptual fragment is selected the ntegrate conceptual fragment action T can be used to integrate the selected fragment into the method under construction The integration of a conceptual fragment is performed in two different ways depending on the type of fragment being integrated The integration of conceptual fragments of type Task Role Work Product and Content Element is performed by means of the Content Package Selection dialog Content Package Selection Select the content package where the fragment will be stored 4 ISD gt Ba ISD_content_package gt Be ISD_content_package 2 gt ISD_content_package 3 Cancel The Content Package Selection dialog allows users to select the content package where the tasks roles and work products will be stored The conceptual fragments of type Process are integrated by means of the Process fragment integration wizard This wizard takes the user through three steps First the user must select an element of a method process The element that is selected will be the destination of the process encapsulated in the process fragment The integration of the process fragment can be performed in two different ways Extend and Copy If Extend is selected t
35. ing partial views on methods 3 The properties of the method elements selected in the Library view can be edited by means of specific editors that are opened by default on the right side of the MOSKitt4ME workbench Both the Library view and the Configuration view of MOSKitt4ME are provided by the EPF Composer The EPF Composer is an open source SPEM 2 0 editor that is provided as part of the Eclipse Process Framework EPF This editor has been integrated in MOSKitt4ME to support the creation and the manipulation of method models In this section we provide a very brief summary of how methods are defined by means of the EPF Composer More details can be found at htto www eclipse org epf general EPF Installation Tutorial User Manual odf i http www eclipse org epf EPF Composer Defining software development methods by means of the EPF Composer comprises two main steps Step 1 Definition of the method content the content of a SPEM 2 0 method is primarily expressed using tasks work products and roles Also guidance can be associated to these elements The method content elements are generic that is they do not take into account the particularities of specific processes Step 2 Definition of processes the generic method content is instantiated in specific development processes The main SPEM 2 0 process elements are activities which can be nested to define breakdown structures as well as related to each other to define a flo
36. ity L L L UML Class Model Specification Add From Method Content Task Descrip O Ll LI o 22 Data Persistence Design Apply Pattern Activity m O Let Database Model Generation Task Descrip L C F E Suppress 4 Database Model Revision Task Descrip L E CJ Suppress Tasks Database Scripts Generation Task Descrip L LI LI Update Suppression From Base Roll Up Diagrams d gt Open BPMN 2 0 Diagram Expand dll TS Open Activity Diagram Collapse All Preferences Open Work Product Dependency Diagram S Delete BPMN 2 0 Diagram 11 http www activiti org In order to facilitate the access to the BPMN 2 0 processes MOSKitt4ME provides the BPMN 2 0 view To open this view Window gt Show View gt Other Show View Aaa H General i Ant E i APT Tooling H CVS Data Management H Debug L Help tL Java E i Java Browsing Method Authoring gt EPMN 2 0 Configuration BA Content BA Library E Repositories HLS MOSKEE Use F2 to display the description For a selected view gt BPMN 2053 7 The BPMN 2 0 view provides a hierarchical representation of the BPMN 2 0 processes generated for the process that is selected in the Library view Each of the elements of the hierarchy represents one specific BPMN 2 0 process The user can double click any of these processes to open the Activiti Designer file storing it EEEn eevre ExperimentPlugin BA Method Content U
37. l The method products can be created and manipulated by means of software tools that are opened by default on the upper right side of the MOSKitt4ME workbench MOSKitt Resource Explorer view In MOSKitt4ME projects are created by means of the MOSKitt Resource Explorer view Specifically new projects can be created by means of the contextual menu New gt Other a MOSKitt Resource Explorer 5 E BS 7 T Project eg Import ge Other gg Export T Refresh FS MOSEIEE Transformations This action opens the New wizard where the user must select the type MOSKitt4ME Project Select a wizard Wizards H General ra Eclipse Modeling Framework gt Example EMF Model Creation Wizards gt Java E E Method Authoring E E MOSKitt MOSKittaMe MOSEIEESKIE Project gt Other Cancel Then on the next page of the wizard enter the project name and select the process to be associated to the project This page allows the user to choose among all the processes that are defined in the method library New MOSKItt4ME Project New MOSKItt4ME Project Select Method Library and Delivery Process Project Mame ExperimentProject Delivery Processes E Experiment r Information System Design When the wizard is finished a new MOSKitt4ME project is added to the MOSKitt Resource Explorer view Process view When a project is selected
38. le This file associates the help context identifier with the HTML files implementing the help http help eclipse org juno index jsp topic 2Forg eclipse platform doc isv 2Fguide 2Fua_help con text htm
39. ments Then these assets can be reused during the definition of methods and the construction of the supporting CASE environments In general eclipse plug ins can implement different types of tools such as graphical editors form based editors or model transformations For each of these types of tools MOSKitt4ME provides different Eclipse based technologies that facilitate the development of the plug ins The plug ins that are developed with MOSKitt4ME must meet a set of requirements so that they are compatible with the Project Manager i e the Project Manager can automatically invoke the tools that the plug ins implement In the following we describe for each type of tool the Eclipse technologies that can be used for their development and also the requirements that the tools must meet Meta Models Meta Models can be specified in MOSKitt4ME by means of the Ecore language which is provided as part of the Eclipse Modeling Framework EMF EMF supports the definition of meta models and also provides generation facilities to obtain 1 the set of Java classes implementing the meta model along with 2 a set of classes that enable editing of the models and also 3 a basic tree editor In order to be compatible with the MOSKitt4ME requirements the plug ins contained in a technical fragment of type Meta Model must define an Ecore meta model In addition the Java classes the editing classes and the tree editor must have been ge
40. n this example the user specifies that the DBModel work product which represents a database schema model will be created during the method execution by means of the tool Database_Editor which represents a graphical editor that supports the definition of database schemas External tools Another type of technical fragments that can be created with MOSKitt4ME is the external tools An external tool is a tool that is installed on the system outside of the context of Eclipse and therefore it is not implemented as Eclipse plug ins This special type of technical fragments support the situations where method engineers want to specify that a particular work product must be developed by means of a tool that cannot be installed in an Eclipse based CASE environment For instance method engineers may want to specify that a work product will be created during the method execution by means of a textual editor such as Microsoft Word The definition of external tools can be performed in MOSKitt4ME by means of the Define external tool action of the contextual menu Repositories 2 e reAY a mario localhost AssetBase Refresh Discard location Create conceptual fragment Create technical fragment Define external tool Define internal tool This action opens the Define external tool dialog which allows the method engineer to specify the properties of the external tool S Define External Tool Mame Word
41. nal tool Once the file is created MOSKitt4ME attempts to open it If the task has an output product with an associated internal tool the Project Manager just provides textual information about the tool This information is retrieved from the technical fragment representing the internal tool If the task has an output product but this product does not have any associated tool the Project Manager does not perform any action If the task does not have output products the Project Manager does not perform any action When the execution of a task has been requested and the output products are already created subsequent execution requests for the same task do not have the same effect Specifically when the user double clicks an executable task that has already been started the Project Manager opens its output products so that the user can modify them Once a task is considered finished the user must manually set the task as executed This can be performed by means of the Run action of the toolbar When a task is set as executed the Project Manager automatically notifies the Activiti Engine which takes the process instance to its next state In addition to the Run action the Process view also provides the Run Repeatable action This action is only enabled for tasks that were set as repeatable during the method definition When the Run Repeatable action is invoked for a task then the task is considered ag
42. nerated Graphical Editors Graphical Editors can be developed in MOSKitt4ME by means of the Eclipse Graphical Modeling Framework GMF GMF is framework that is built on EMF and applies a model driven approach to obtain fully functional graphical editors Specifically GMF is based on the specification of a set of models that define 1 an Ecore meta model 2 the graphical elements to display in the editor and 3 the tools that will appear in the palette menus and toolbars Once these models are defined a set of generative tools http www eclipse org modeling emf D http www eclipse org modeling gmp automatically obtain a graphical editor supporting the construction of models that are compliant with the Ecore meta model that has been specified There are no particular requirements to be met by the plug ins contained in the technical fragments of type Graphical Editor All graphical editors developed by means of GMF are compatible with the Project Manager of MOSKitt4ME Form based Editors Form based Editors can be developed in MOSKitt4ME by means of Fefem Fefem is a development framework that facilitates the construction of form based editors by implementing a set of patterns that are typically found when developing this kind of editors e g the need to show in a Textbox the value of a property of type String Thus the development of Form based editors is reduced to simple pattern composition Fefem is based
43. o be created deleted or modified by means of the Roles and Work Products tabs Finally precedence relationships can be established between process elements by means of the Predecessors column fe InformationsystemDesign X Presentation Mame Index Predecessors Mod SJ ran Information System Design 0 E Business Logic Design 1 i 5 Data Persistence Design a In this example the Business Logic Design activity identified by index 1 is set as predecessor of the Data Persistence Design activity 3 2 Repository Client The Repository Client of MOSKitt4ME can be accessed by opening the Repositories view This view can be opened by means of the Window menu Show View gt Other EE Show View type filter text gt Data Management gt amp Debug gt 2 Help gt gt Java gt Java Browsing gt gt JavaScript Method Authoring BPMN 2 0 Configuration Content Library gt Repositories gt Nebula gt lt Operational QVT gt Plug in Development o Ca Renoet and Chan Necian Use F2 to display the description for a selected view Repositories 2 3 Eg O The Repositories view allows method engineers to connect to FTP repositories that store either technical method fragments or conceptual method fragments Thus the functionality provided by the Repositories view is twofold On the one hand it allows method engineers to as
44. oftware dependencies Additional fragments are added by means of the Add dependency button and existing fragments are deleted by means of the Remove dependency button In order to edit the properties of a technical fragment selected in the dependencies tree the Create technical fragment dialog provides the Edit button which opens the Edit technical fragment dialog Edit Technical Fragment Name GlossaryEditor Type Form based Editor Origin MOSKEE Objective This editor enables the creation and manipulation of glossary models Input No particular requirements are needed for using this tool Output EMF models that instantiate the MOSErtt Glossary metamodel Plug ins Workspace plug ins Technical fragment plug ins E es cv gvcase gvm glossary formsedit E es cv gvcase gvm glossary navigator i amp s cv gvcase emf ui common i es cv gveasefefem common E es cv gvease gvm glossary l amp s cv gvcase gvm glossary edit l amp cv gvcase gvm glossary editor E es cv gveaseide core E es cv gveaseide help l es cv gvcase ide navigator rou at eS m a malls ae a 4 rn Cancel The Edit technical fragment dialog allows method engineers to specify the following set of properties Once Name this property represents the identifier of the technical fragment Type this property classifies the technical fragment in one spe
45. on the use of the SWT and JFace libraries which are two libraries of graphical components that are provided by the Eclipse community Form based editors can directly be built by means of these libraries However we recommend the use of Fefem since it significantly reduces the workload inherent to the development of this kind of tools There are no particular requirements to be met by the plug ins contained in the technical fragments of type Form based Editor All form based editors developed by means of Fefem or directly by means of SWT and JFace are compatible with the Project Manager of MOSKitt4ME Model Transformations Model transformations can be developed in MOSKitt4ME by means of the ATL and Xpand languages which are two programming languages especially designed by the Eclipse community to implement Model to Model and Model to Text transformations respectively To be compatible with MOSKitt4ME the model transformations can be implemented in any language Nonetheless the plug ins contained in a technical fragment of type Model Transformation must meet two requirements 1 The model transformation must be declared by means of the extension point es cv gvcase trmanager transformation This extension point is provided by the Transformation Manager of MOSKitt The MOSKitt Transformation Manager is a software component that provides a set of Java classes for the t6 http www moskitt org eng fefem creacion_d
46. redecessors Model Info Type Planned Repea Multipl Ongoing Event Optional El Ro Information System Design D Delivery Pro U U LJ LJ L oF Business Logic Design 1 Activity L L LJ LJ LJ Les UML Class Model Specification 2 Task Descrip LJ L L E LJ LI El Data Persistence Design 3 1 Activity L L L LJ L Le Database Model Generation 4 Task Descrip Li L LJ LJ LJ E Le Database Model Revision 5 4 Task Descrip L O E C LJ C les Database Scripts Generation 6 5 Task Descrip LI L L E L H By means of this editor processes are defined as work breakdown structures These tree structures define activities which contain references to method content elements i e taks roles and work products Activities can be created by means of the contextual menu References to method content elements can be fe InformationSystemDesign 5 Presentation Mame rE Information System Design ee In Predecessors Model Info LI telis Mew Child Add from Method Content pply Pattern Phase R Iteration Suppress Update Suppression From Base oF os fa ve tim aa Move Up a Move Down g Indent n Outdent le Task Descriptor l Milestone created by adding task descriptors role descriptors and work product des
47. s Processes fel Capability Patterns S Set Delivery Processes S S InformationSystemDesign CE Configurations Or ivi J X Information System Design U gt Business Logic Design g Data Persistence Design e o Database Scripts G 3 4 Tool Generator Once the executable representation of the method is obtained the Tool Generator of MOSKitt4ME automates the construction of a supporting CASE environment The Tool Generator can be invoked by opening the contextual menu of the Library view and selecting the Generate CASE Tool action ie Sa Ex perimentPlugin a Method Content eae Content Packages Gest contentPackage C3 Roles aS Tasks aa eoe Work Products a e Guidance HLS Standard Categories l EE Custom Categories B be Processes jz e ba Capability Patterns ej Paste Seal Delivery Processes i cS Informations ystemDesign I Delete ia Configurations Rename Show in Resource Navigator Validate Refresh This action opens the CASE tool generation dialog which allows the user to enter the destination path and the name of the CASE tool CASE tool generation Select a destination directory For the CASE tool CiiCaseTool CASE bool name The CASE tool generation process automatically performs two main steps Step 1 The Eclipse plug ins contained in the technical fragments associated to the method elements are do
48. s Tree 4 pp GlossaryEditor Edit ay GlossaryMetamodel Add Dependency Import Once all the fragments of the dependencies tree contain no errors they can be stored in the repository by means of the OK button Create Technical Fragment Dependencies Tree a GlossaryEditor Edit an GlossaryMetamodel a Fefem Add Dependency hy EMFT a 4 IDE a MDT Import A EMFT Remove Dependency Cancel Note that a new technical fragment will be created for each of the fragments of the dependencies tree This is not the case of the imported fragments since they represent references to fragments that were previously created The technical fragments that are stored in the repository are shown in the Repositories view as childs of the repository location element l a mario localhost AssetBase gt W DatabaseEditor ras gt A DB2DDLTransformation ras i GlossaryEditor ras h GlossaryMetamodel ras gt UMLEditor ras gt Word ras Note that the fragments of type Others are not shown in this view The reason for this is that only the other types of fragments i e editors meta models model transformations guidance external tools and internal tools can be associated to the products and tasks of the method Thus fragments of type Others are only used to solve dependency problems The Repositories view also allows the user to examine t
49. sociate technical fragments with elements of the method so as to indicate the software tools that will support the method during its execution On the other hand it allows method engineers to reuse method parts which makes the method construction process less error prone and more rapid and cost effective In order to connect to a FTP repository the Repositories view provides the Add Repository Location action p which can be found in the toolbar of the view This action opens the Add Repository Location dialog which allows the user to enter the host that contains the repository the repository path and his username password Add Repository Location Host Repository Path User Password Cancel When the connection with the FTP repository is established a new repository location is added to the Repositories view on a Lane bB mario localhost AssetBase Repository locations are displayed in the Repositories view according to the following pattern user host repositorypath The content of a repository location can be refreshed by means of the Refresh action of the contextual menu bB mario localhost AssetBase Discard location Create conceptual fragment Create technical fragment Define external tool Define internal tool Repository locations can be deleted by means of the Discard location action of the contextual menu ries K a EAE gt mario localhostAssetB
50. volves the construction of a graphical model of a database schema Content Library content Conceptual fragment content jo ISD databaseModelSpecification ISD_content_package E Tasks glossaryOfTermsDefin C businessLogicDesign C gt databaseScriptsGenere C gt databaseScriptsRevisic Add related content elements The Create conceptual fragment dialog allows the user to create new conceptual fragments In order to do so method engineers must specify the following set of properties Name this property represents the identifier of the conceptual fragment Type this property classifies the conceptual fragment in one specific category The conceptual fragment types supported in MOSKitt4ME are Task Role Work Product Content Element and Process The first three types of fragments contain respectively tasks roles and work products Conceptual fragments of type Content Element can contain any combination of these elements for instance a task and its associated input output products Finally fragments of type Process contain reusable processes which are represented in SPEM 2 0 by means of the primitive Capability pattern Origin this property establishes where the method element contained in the conceptual fragment originates from For instance a conceptual fragment can contain a task extracted from the gvMetrica method Objective this property
51. w of work Activities contain references to tasks defined in step 1 which in turn reference their input output work products and their performing roles Method content and processes are defined within method libraries Method libraries can be created in MOSKitt4ME by means of the File menu New gt Method Library This action opens the New Method Library wizard t New Method Library Create a new method library Specify a path and description For the new method library Path CMOSKIRAME Method Libraries Experiment Ww Description Use auto synchronization For all processes The New Method Library wizard allows the user to specify the destination path of the method library and also the library description Once the library is created it can be edited by means of the Library view The library path must not contain blanks The user can also open existing method libraries by means of the File menu Open gt Method Library which opens the Open Method Library wizard i Open Method Library Bel Open Method Library wr Specify a path containing a method library Path C MOSKitt4ME MethodLibraries Experiment y When a method library is opened it can be edited by means of the Library view Note that the Library view can only show one method library at a time In a method library method content and processes are organized in hierarchical structures named method plug ins Method plug ins c
52. wnloaded from the FTP repository and imported into the workspace if they are not already imported Progress Information Downloading tools 1 man O Downloading Database_Editor ras zip Progress Information Downloading tools i Importing projects into workspace Step 2 An Eclipse Product Export process is launched This process produces the final Eclipse based CASE environment Once this tool is produced the plug ins that were imported into the workspace in step 1 are deleted so that the workspace returns to its original state http help eclipse org galileo index jsp topic org eclipse pde doc user guide tools export_wizards export_product htm Export Product The duration of step 1 and step 2 depends on the size and the number of software tools that are required to support the method Thus the CASE tool generation process may take from a few minutes to more than one hour The result of the CASE tool generation process is a reconfiguration of MOSKitt that only contains 1 the plug ins strictly necessary to support the method and 2 a software component that supports the execution of method instances see section 4 The reconfiguration of MOSKitt is available at the path specified in the CASE tool generation dialog moskitt rchiva Edici n Wer Favoritos Herramientas Ayuda Atras 7 F a pe B squeda ey Carpetas EB fa Sincronizaci n de carpetas Dir

Installation instructions and user manual

Contents

Download Pdf Manuals

Related Search

Related Contents