ArcStyler/MDA Glossary. For ArcStyler Version 4
|
|
- Katherine Wiggins
- 6 years ago
- Views:
Transcription
1 ArcStyler/MDA Glossary For ArcStyler Version 4
2
3 Copyright Copyright October 22, 2003 Interactive Objects Software GmbH. All rights reserved. The software described in this manual is provided by Interactive Objects Software under a license agreement. The software may be used only in accordance with the terms of the agreement. This document or portions of it may only be transmitted or copied in units of unmodified complete pages or larger unmodified document segments. This copyright notice must be clearly visible at the beginning of each copy. Interactive Objects Software GmbH registered trademarks: Interactive Objects, Convergent Architecture, ArcStyler, ArcExchange. All other brand or product names are trademarks or registered trademarks of their respective companies or organizations. Interactive Objects Software GmbH. Basler Strasse Freiburg, Germany Tel: Fax:
4 iv
5 ArcStyler/MDA Glossary A Abstract Blueprint. (CARAT). Blueprint which houses basic Jython functions like functions for evaluating method names (get<xxx>/set<xxx>) or decision functions (dec<xxx>). Used in derived Blueprints, mainly in Context-dependent Blueprints. Usually represented by a Python script file (e.g. attribute.py). Accessor. Part of the ArcStyler MDA Accessor Architecture. Component of an MDA/UML model which represents an external interface of a software system: A User interface or a System interface. Specialization of the UML type Class, stereotype Accessor. The dynamic behavior of an Accessor is described in a UML state/activity diagram. Within the Model-View-Control (MVC) paradigm, the Accessor takes the role of the controller. An Accessor uses Representers in UML to define an external representation or interface. Moreover, Accessors are reusable components (i.e. reusable models) and may be embed other Accessors or be embedded to form composite Accessors. Just as any MDA Modeling Style in ArcStyler, Accessor support is pluggable via an MDA-Cartridge, the default Web Accessors Cartridge, for example. The Web Accessors Cartridge supports MDA automation of multi-tiered, scalable web front ends based on open standards. Accessor Container. Part of the ArcStyler MDA Accessor Architecture. A portable, standardbased runtime environment for Accessor components on the target platform (e.g. J2EE or.net). Provides a simple, standard interface to high-level services. For example, it activates Accessors, starts the top-level Representer Container, manages the global configuration parameters, and sends messages in the form of events. The Accessor Container fulfills the role of the leading controller object in the MVC paradigm. All other Accessors are created and managed either by the leading controller or by an Accessor created by the Accessor Container. In general, Accessor Containers are not modeled explicitly in UML, but are made available automatically via the corresponding Accessor MDA-Cartridge as part of the tartget infrastructure Accessor framework. Accessor framework. Part of the ArcStyler MDA Accessor Architecture. Enables portable UML modeling of external interfaces and connectivity for diverse software systems using high-level UML State Machines and UML Activity Diagrams. Provides design assistants, wizards, property sheets and model-to-model transformations for modeling Accessors and ArcStyler Glossary 5
6 Representers in the ArcStyler UML Engine, as well as framework classes for the portable Accessor runtime environment. Analysis by Design (ABD), (CA). An agile design process for model-driven development described in the Convergent Architecture. Used to identify and structure OPRs, their relations and the associated constraints and requirements of the business. ABD includes the following steps: Identify the critical organizations of the business. Analyze the core processes of each organization. Determine the essential resources required by each process. Optimize resources. Make them intelligent and self-managing. Simplify the process to reduce time and cost. Reorganize around the new business process. ANT build environment. A de-facto standard Java/XML based build environment developed by the Apache Software Foundation and supported by ArcStyler. The ANT-based build environment consists of the following files: The build.bat is a script file which triggers the build process. The build.xml defines the targets for the build process. A target knows the tasks necessary to build the target. A target can depend on other targets which have to be built earlier. The build.properties file is a Java properties file. It defines properties which serve as configuration parameters for the build process. For further details, please refer to ArcStyler. IT-Architectural IDE and MDA platform for high-end support of model-driven development including unique model-driven extension capabilities to customize the MDA support for both horizontal and vertical domains. Enables model-driven automation of any design approach or any Architectural Style. The optional, default Architectural Style is Convergent Architecture. ArcStyler configuration files. XML files with sufficers *.cfg or *.xml. Global configuration files which store configuration information at the domain level (i.e. across one or more users and projects). They are located in %ARCSTYLER_HOME%/configuration/<configuration_name>, where <configuration_name> is the name of the configuration the ArcStyler is booting from. The 6 ArcStyler Glossary
7 default UML tool configuration is called as4md. The global configuration is complemented by ArcStyler project files. ArcStyler project files. XML file with the suffices *.asprj or *.guicfg. Configuration file which stores configuration information on the project level. It includes user specific and machine specific settings and is complementary to (but may override) the global configuration. Artifact. (CARAT). Jython class responsible for the generation of one or more artifacts/files for a Primary UML model element. Controls the generation flow for one artifact/file. Usually written as Include file (e.g. class_source.inc). A Template file (*.tpl) exists per artifact/file to be generated (e.g. class_source.tpl). ArtifactSet. (CARAT). Jython class derived from Artifact. Maintains a set of Artifact objects registered with it and delegates the generation to these Artifacts. B Business design. (CA). One of the three pillars of holistic architecture defined in the MDAoriented Convergent Architecture. Is concerned with simplifying the development of effective IT systems by achieving synergies with Project design and System design. Blueprint. (CARAT). Jython class derived from ArtifactSet. Corresponds to a UML model element and comprises all patterns used for the generation of the model element (e.g. class.py, cbean_attribute.inc). The following types of Blueprints exist: Abstract Blueprint RootBlueprint Context-dependent Blueprint BlueprintRegistry. (CARAT). Jython class which serves as a central registry for Blueprints within an MDA-Cartridge. Blueprints registered with the BlueprintRegistry are looked up by name. C Cartridge. Abbreviation for MDA-Cartridge. Cartridge Architecture (CARAT). An open, public domain, MDA-centric architecture for the model-driven design and automated generation of MDA-Cartridges that are plug-compatible with any other MDA-Cartridges. CARAT(tm) is analogous to Adobe PostScript(tm) in that it is freely available and enables reusable, independently developed compatibility of MDA capabilities for diverse infrastructures. Just as with PostScript, the a patent-pending exists only ArcStyler Glossary 7
8 8 ArcStyler Glossary to protect integrity and thus guarantee portability and pluggability of Cartridges developed with CARAT. CARAT verifies the ROI of MDA concepts by using them to create new levels of MDA automation along the lines of practice what you preach. C-GEN. Synonym for the ArcStyler s MDA Engine for both model-to-model and model-toinfrastructure transformations based on pluggable MDA-Cartridges. Together with the MDA- Cartridges, it automates a large portion of the model and infrastructure creation activities. Its capabilities are extensible via the MDA-Cartridge extension mechanisms using the MDA- Cartridge IDE. C-GEN-IDE. Synonym for the MDA-Cartridge IDE. C-MOD. Common Model Repository, based on UML, which integrates and coordinates the results from the various ArcStyler modules and their respective views into one standard-based, integrated repository. Throughout the development path, the C-MOD structures are refined with detailed about the modeled components and infrastructure. The common repository prevents information loss between MDA development steps and supports a realistic, incremental development process. Compact Bean. An optional J2EE/JSP design pattern used for high-level modeling of EJBs in the UML Engine. With this pattern all parts and properties of an EJB (e.g. home interface, remote interface, the bean implementation class, primary key class etc.) are modeled as a single UML class. The partitioning and creation of the code infrastructure is then done automatically by the respective MDA-Cartridge. A Compact Bean is represented in UML models by the UML stereotype ComponentSegment. Context-dependent Blueprint. (CARAT). Blueprint which comprises all patterns for the generation of a Secondary UML model element. Usually consists of a Python script file (*.py) which provides basic Jython functions, e.g. decision functions (dec<xxx>), and an Include file (*.inc) which provides the actual patterns for the generation. Convergent Architecture (CA). An MDA-centric IT-architectural style leveraging the benefits of agile development and Convergent Engineering in practice. Signifies the alignment of business and IT models into one common, synchronized model and takes a holistic approach to project, business and system design. Provides a practical, architecture-driven MDA process and techniques enabling business and software design to become a consolidated effort. The ArcStyler provides optional features supporting high-end Convergent Architecture. For details, please refer to and [Hub01]. Convergent Architecture metamodel (CA). Defines the top-level vision, principles and rules by which decisions are made within the optional ArcStyler support for Convergent Architecture.
9 Constitutes a common reference frame of engineering and project management principles shared by all stakeholders of IT systems built according to the CA. These principles are: Three pillars of holistic architecture: Project design, Business design, System design Convergence and Convergent Engineering Machine shop metaphor Reduced Abstraction Set Computing ( RASC) Conceptual isomorphism Component metamorphosis For details, refer to [Hub01]. Convergent Components (CC), (CA). Meaningful set of named design entities used throughout the optional ArcStyler support for Convergent Architecture. Serve as a focal point for development organizations, development activities, design techniques and tools. There are four types of CCs which form a layered infrastructure: Organization, Process and Resource business components ( OPRs) for modeling businesses Accessor components for multi-channel user, Web and system interface access Utility components denoting purely technical utilities of the IT environment Assembly components ( Deployable components) representing top-level units of design and deployment For details, please refer to [Hub01]. Convergent Components metamodel. (CA). Defines Convergent Components as vehicles transporting the principles of the Convergent Architecture into elements of concrete design, tools and technologies. Based on Convergent Engineering, UML and MDA. Convergent Engineering (CA). Introduced by David A. Taylor in [Tay95]. Design vision with an XP/Agile methodology which provides a set of design patterns and a design techniques to align (converge) business and IT systems based on the perfection of the object paradigm. One model is used to describe both the business and the IT perspective of a system. Business systems designed using the concepts of CE are understandable, maintainable and easily modified in response to changing business conditions. ArcStyler Glossary 9
10 D Default Accessor. Special type of an Accessor which is automatically generated (both its model and then subsequent code) based on an existing business component. Enables immediate MDA creation of Web and other types of system access based on existing UML models. Is designed to cover the most common access use-case scenarios such as: Show/Externalize a particular instance of a business component. List/Browse all existing instances of a business component. Create/Add an instance of a business component. Remove a particular instance of a business component. Modify/Edit a particular instance of a business component. Deployable component. Special type of a UML component representing a physical deployment unit such as an EAR file (the J2EE/EJB incarnation of assemblies), an EJB JAR file, a Java JAR file or a Web application WAR file. Defines an implementation-independent deployment structure which is used by an MDA-Cartridge to managed dependencies and generate complete build, test and deployment infrastructure for a particular implementation infrastructure. Development model. (CA). Feature of an IT-Architectural style which describes the development organization, development process and design structure in terms of a UML model. The development model of the optional Convergent Architecture distinguishes the following three interacting models: IT-Organization model Development process model Convergent Components metamodel E EJB. Acronym for Enterprise JavaBeans. Server-side component architecture introduced by SUN to build component-based, distributed, transaction oriented software systems. A subset of J2EE. For details, please refer to EJBArchive. Special type of a Deployable component representing an EJB archive. Packages Compact Beans, Dependent values and explicitly modeled EJB remote interfaces. Specialization of the UML type Component, stereotype EJBArchive. EJBClientArchive. Special type of a Deployable component representing an EJB client archive. Packages the stubs for the remote access of EJBs. Contains the home and remote 10 ArcStyler Glossary
11 interfaces of EJBs and classes which are passed by value in the EJB interfaces and exception classes used in the EJB interfaces. Specialization of the UML type Component, stereotype EJBClientArchive. Executable MDA Configuration. An executable MDA configuration is a group of one or more MDA Cartridge Features to be executed in a certain order where each of the features has an execution context associated with it. Every MDA Cartridge defines a set of default executable MDA configurations. In addition to these default configurations, the user may define any number of additional configurations. G Generic Accessor. Reusable Accessor which can be used to perform a specific task on different types of objects. Cf. Generic Data Accessor for an example of Generic Accessors designed to perform data maintenance. Generic Data Accessor. A set of Generic Accessors that undertakes typical tasks in the maintenance of objects. Examples of these tasks are the creation of new instances (Generic Creator Accessor), editing component properties (Generic Property Accessor), editing associations, and the selection of an object or component from a collection. I Include file. (CARAT). Template file with the suffix *.inc. A CARAT include file written in template syntax. Used to modularly redefine or add Jython functions. IT-Architectural IDE. Denotes an Integrated Development Environment (IDE) as a platform for automating architecture-driven design with MDA. An IT-Architectural IDE is model-centric in contrast to code-centric Programming IDEs and is most often used to automate an IT- Architectural Style, in part or in whole (e.g. Corporate Architectural Style), for horizontal or vertical design domains. IT-Architectural style. (CA). The concept of a classical architectural style applied to the design of IT systems. Consists of four high-level features: An Architectural Metamodel A Full Cycle Development Model A Full Coverage Tool Suite or IT-Architectural IDE And Formal Technology projections For details, refer to [Hub01]. ArcStyler Glossary 11
12 Iterator. (CARAT). JPython class which triggers the generation of a UML model segment. Recursively dispatches each Primary UML model element to the corresponding RootBlueprint registered for the model element type with the RootBlueprintRegistry. J J2EE. Acronym for Java 2 Enterprise Edition. A component architecture standard introduced by SUN to build component-based, distributed, transaction oriented software systems. For details, please refer to JavaArchive. Special type of a Deployable component representing a Java archive. Packages classes and interfaces. Specialization of the UML type Component, stereotype JavaArchive. JPython variable. (CARAT). Variable used by the MDA Engine to make model and configuration information accessible from the Templates in an MDA-Cartridge. JMI (Java Metadata Interchange). Standard that defines how to access MOF-specified metamodels and their metadata using Java. ArcStyler is entirely based on JMI. It is the common basis for any model access throughout the tool. Currently, ArcStyler specifies JMI version 1.0. M Mark. see MDA Mark Model Driven Architecture(tm) (MDA). Standardization initiative and architectural direction of the OMG (Object Management Group) which offers a full life cycle approach for solving the problems of developing, deploying and integrating existing distributed systems with emerging technology, assembling virtual enterprises that span multiple companies and implementing business intelligence solutions and enterprise information portals in a multi-vendor environment. For details, please refer to MDA-Cartridge. An individually developed, distributed and installed package of well-defined MDA-automation features. May be plugged into the ArcStyler individually or together with other MDA-Cartridges. Defines and package a set of related MDA and development features (e.g. MDA transformation rules, formatting templates, quality verifier rules, pattern models, generation templates for diverse aspects of infrastructure etc.) and mechanisms (mapping engines, verifier engines, pattern matchers and generators, parser rules etc.) that are required to automate, configure, model and manage diverse development activities in a simple, compatible manner. Enforces and operates according to a well-defined Modeling Style. Is pluggable as one of many Transformations in the ArcStyler. Often available in open-source form and downloadable in the Internet from 12 ArcStyler Glossary
13 MDA-Cartridge Feature. Each MDA-Cartridge offers a set of MDA Cartridge features. A feature represents a certain capability of a cartridge. Among the most important cartridge features are generate, verify, and profile. A cartridge feature s execution flow may be atomic or it may possess an internal structure. In the latter case it is possible to configure the execution of a feature in such a way that only certain partsof the feature functionality are enabled. In addition, the execution of a cartridge feature is influenced by the settings of the properties of the cartridge the feature belongs to. The combination of execution flow configuration and cartridge property settings are referred to as the feature s execution context. Every feature has a default execution context defined by the full feature functionality and the default values of all cartridge properties. See also Executable MDA Configuration. MDA-Cartridge IDE. Visual integrated development environment (IDE) for the creation and extension of MDA capabilities. Supports a model-driven approach to creation and maintenance of pluggable MDA-Cartridges. Provides all of the customary features of classic programming IDEs at the new level of MDA-Cartridge development. Often referred to as metaprogramming or meta-development environment. The MDA-Cartridge IDE s support for CARAT enables engineers to develop and deliver compatible, pluggable MDA-Cartridges to support any MDA transformation or target infrastructures. MDA Cartridge Sourceforge. Exchange platform for MDA-Cartridge sources and models that can be used with the ArcStyler. ArcStyler s free Community Edition allows everyone to create MDA-Cartridges. Such MDA-Cartridges can be uploaded to the MDA-Cartridge Source Forge server. All MDA-Cartridges available via the MDA-Cartridge Source Forge can be downloaded using the ArcStyler MDA Cartridge Wizard. Most MDA Cartridge have a set of cartriudge wizards associated with them. These wizards simplify the creation and configuration of UML model elements relevant to the modeling styles defined by the cartridge. MDA Custom Diagram Types. Most MDA Cartridge have a set of custom diagram types associated with them. These diagram types support the transformation-specific modeling style by customized buttons contained on the diagrams toolbar. MDA Enabling. Creates precise MDA/UML models from existing code and infrastructure. Creates reusable models according to a well-defined MDA Modeling Style thus enabling the advantages of high-end MDA immediately from existing infrastructures. MDA Engine. Automates bi-directional transformations between models-to-models as well as models-to-infrastructures. Is used in multiple phases and at multiple levels of a MDA development. Analogous to a compiler in many ways, it is well specified, dependable, ArcStyler Glossary 13
14 optimizing, efficient, flexible, configurable, and enables MDA development and debugging via visual development, see MDA-Cartridge IDE. MDA-Horizontal Cartridges (syn. MDA-Horizontals). Designates MDA-Cartridges that provide MDA support that may be widely reused across many business domains. MDA- Horizontals normally use Aspect Oriented or Pattern Transformation features to enhance or complement other MDA Modeling Styles with new modeling, verification and transformation capabilities. Examples of MDA-Horizontal Cartridges are the MDA-Cartridges for J2EE,.NET or MDA-Security. Compare MDA-Verticals below. MDA Marks. Light-weight annotations to model elements that can hold any information that serves as additional input to MDA-Cartridges. These marks can hold platform-specific information. Any ArcStyler MDA-Cartridge brings with it a definition of the sets of marks it expects on an input model. These mark set definitions can be installed into and removed from a repository. An intelligent mark set editor evaluates the mark set definitions at modeling time and provides convenient support for marking a model for a specific mapping. MDA Modeling Style. Standardizes MDA/UML modeling conventions to increase the quality, information value and automation capabilities of models. Defines the precision, completeness, and consistent abstraction levels of models. Is crucial to delivering high-end MDA benefits since model verifiers, model-transformations, model reuse and model exchange can only be achieved when based on well-formed models with well-defined characteristics as provided by a Modeling Style. The advantages of a modeling style apply to any model-based development process, independent of the particular development methodology: Each MDA-Cartridge is accompanied by a well-defined, verifiable Modeling Style. See [Hub01] for more detail. MDA Project. With ArcStyler all MDA activities are performed within the context of an MDA project. An MDA Project, contains, among other things, configuration information for each ArcStyler tool, including, for example associated UML Projects, configured MDA Transformations and other settings of different ArcStyler tools. All this information is saved in files with the extension.asprj. GUI settings, such as the size and location of windows, are saved in an extra file with the extension.guicfg. MDA Profiles. A default UML package (normally transparent to the MDA modeler) which provides foundation MDA/UML model elements such as elementary pattern types, UML extension packages, Java extension packages, etc. MDA-Security(tm). Adds pre-tested, model-driven security capabilities to the Architectural IDE. The MDA-Security Cartridge is an MDA-Cartridge enabling any number of designers and developers to provide high-precision security features of consistent quality-of-service by 14 ArcStyler Glossary
15 modeling and verifying these features in UML and generating the secure infrastructure automatically from these models. MDA-Security defines, implements and verifies a precise MDA Modeling Style and UML-Profile called SecureUML. See the documentation for the ArcStyler MDA-Security Cartridge for more terms and information. MDA-Security Designer. Graphical tool in MDA-Security providing unique features to visualize, refine, and validate the security policies at the UML-level. The MDA-Security Designer contains the three sub-components Subject-Role Editor, Permission Editor, and User s Permission editor. MDA-Vertical Cartridges (syn. MDA-Verticals). Designates MDA-Cartridges that provide MDA support that may be widely reused to provide high-end MDA support within a specific business domains or for very business-near functionality. MDA-Verticals often use Aspect Oriented or Pattern Transformation features to enhance or complement other MDA Modeling Styles with new modeling, verification and transformation capabilities. Examples of MDA- Horizontal Cartridges are the MDA-Cartridges for diverse UML Archetypes, or for Telecom and Pharmaceutical specific MDA approaches. Compare MDA-Horizontals above. MOF (Meta-Object Facility). Meta-modeling standard defined and maintained by the OMG. It specifies how to define modeling languages, such as the UML, and how to access and exchange the models expressed in these languages. ArcStyler uses MOF internally for all of its UML and C-MOD support. N.NET. A language framework and component architecture introduced by Microsoft to build component-based, distributed, transaction oriented software systems..net enables software integration through the use of XML Web services. For details, please refer to O OPR. (CA). Acronym for Organizations, Processes and Resources. An optional MDA Modeling Style and technique based on the concept of Convergent Engineering and RASC. P Perspective. Collection of related MDA tools displayed on the screen at the same time. The user can switch between different perspectives at runtime. The ArcStyler default configuration contains two perspectives - the Modeling Perspective displaying UML modeling-related tools and the Cartridge Perspective displaying cartridge development-related tools. ArcStyler Glossary 15
16 Primary UML model element. (CARAT). UML model elements which can be selected individually in a model for MDA Transformation or infrastructure generation. Examples include: Packages Classes (including dependent values and exceptions) Interfaces Compact Beans EJB remote interfaces Java archives EJB archives EJB client archives Project design. (CA). One of the three pillars of holistic architecture defined in the Convergent Architecture. Defines how to achieve project design using modern modeling and convergence techniques. Is concerned with simplifying the development of effective IT systems by achieving synergies with the Project design and Business design. Indicates how projects operating at various levels of an organization are set up, organized, managed and coordinated. Enables projects to effectively achieve the advantages of convergence and MDA, among other things. Protected area (PA). Segment of code or other infrastructure preserved and intelligently managed across subsequent activations of an MDA-Cartridge. PAs contain business logic and other information which cannot be adequately expressed or specified in the model. Any file may contain a PA. Examples of files with protected areas are Java source files, EJB deployment descriptors, and ANT build scripts. Python script file. (CARAT). Template file with the suffix *.py. Part of an MDA-Cartridge. Pure Jython script file. Used to define Jython functions which execute evaluations and perform computations based on repository contents and configuration information. R RASC. (CA). Acronym for Reduced Abstraction Set Computing. Defines the core component abstractions ( OPRs) and corresponding architectural layers to achieve the goals of Convergent Engineering. Representer. Component of an Accessor model which describes basic external interface types and input/output properties. Output properties represent information provided in a suitable form by the Representer to a human user or service user from the software system. Input properties specify the input facilities the Representer supplies enabling the user or external services to 16 ArcStyler Glossary
17 trigger activities in the software system. Specialization of the UML type Class, stereotype Representer. An external service interface ( Accessor) may consist of one or more Representers. Within the MVC paradigm, the Representer fulfils the role of the view. Representer Container. A portable, standard-based runtime environment for Representers on the target platform (e.g. JSP/Servlet, mobile, Web Services). Provides the Representers with services, e.g. defining methods for registering and unregistering Representers or messaging via events. Houses and manages active Representers and displays their interfaces to the user. Representer Containers may be freely composed to form a hierarchy. The root container in the hierarchy is the top-level Representer Container, which is managed by its associated Accessor Container. Resource mapping. Rule for passing a single value from a source element to a target element upon occurrence of a particular event. In an Accessor model, it describes the data flow within the Accessor s state model, i.e. it is used to pass parameters within the Accessor model: Between Accessor and associated Representer components Between superordinate and embedded Accessor components Responsibility-Driven Design. (CA). A widely used design modeling technique (also adapted by newer XP/Agile design techniques) which defines components and objects in terms of the roles they play in a business model and/or an IT-system. In this approach, an components carrying out specific responsibilities in order to fulfil a defined contract. Run-through. (CA). The final quality verification of a business model after the design has been fully debugged using Walk-throughs. A faster version of a walk-through where only component/object communications are permitted with no on-the-spot debugging of the design. S Secondary UML model element. (CARAT). UML model element which cannot be independently selected in the UML model for the infrastructure or code generation since it depends on or is owned by a Primary UML model element. Examples are: Attributes Operations Association ends Dependencies SecureUML. The formal MDA Modeling Style for MDA-Security. ArcStyler Glossary 17
18 System design. (CA). One of the three pillars of holistic architecture defined by the Convergent Architecture. Defines how to achieve system design using MDA techniques. Is concerned with simplifying the development of effective IT systems by achieving synergies with the Project design and Business design. System interface. Denotes external interface of a software system which enables the interaction between software systems. Necessary when a software system is to be integrated with other existing systems to solve a certain task. Examples are Web Services, CORBA interfaces, Java JMS and JCA based communication interfaces and XML based standards for Enterprise Application Integration (EAI). T TAS (Tool Adapter Standard). container for MDA tools that defines a set of interfaces and services for tool interaction, GUI integration, repository access, and MDA profile and cartridge management. The TAS APIs and the steps necessary to develop your own ArcStyler TAS plugin are described in the ArcStyler MDACartridge Development and Extensibility Guide. Technology projection. Synonym for the Transformation carried out by an MDA- Cartridge. A feature of an MDA-centric approach or IT-Architectural style which transforms (or maps) a model to another model or, as a final step, maps a model to runnable system infrastructure. Is implemented by an MDA-Cartridge. Technology projection cartridge. Synonym for MDA-Cartridge. Transformation property file. XML file with the suffix *.tpr which contains configuration information of a specific MDA-Cartridge. Each *.tpr file describes and configures all the parts of a particular MDA-Cartridge. Stored in of the %ARCSTYLER_HOME%/carat/<cartridge_name>/gen/cartridges directories. Template. (CARAT). Contains a generation pattern or formatting blueprint as part of an MDA- Cartridge. Defines the formats and content to be generated from a UML model or other input to the MDA-Cartridge. Implements the mapping rules that prescribe how the input elements (e.g. UML model elements) are mapped to generated artifacts. Template file. (CARAT). File with the suffix *.tpl that contains a Template. Tool information file. XML file with the suffix *.info which contains configuration information (type designation, installation path, license information, properties) for external tools used and managed by ArcStyler (e.g. J2EE/.NET products, JDKs, Build-tools, Programming IDEs). Is stored in of the %ARCSTYLER_HOME%/carat/<cartridge_name>/gen/tools directories. 18 ArcStyler Glossary
19 Transformation. Denotes a well-defined mapping of an input artifact to an output artifact. For example, transformations may convert a model to another model or the map a model to a runtime infrastructure. Well designed transformations require a complex set of items (mapping rules, format templates, verifier rules, pattern models, include files, configuration files etc.) and mechanisms (mapping engines, verifier engines, pattern matchers, parser rules etc.) are required to automate, configure, model and manage diverse transformations in a simple, compatible manner. Packaging and managing these items and mechanisms in a simple manner is the job of an MDA-Cartridge. U UML (Unified Modeling Language). Standard software modeling language defined and maintained by the OMG. Currently, the UML tool embedded in ArcStyler supports UML version 1.5. UML Engine. The high-end UML module in ArcStyler. Complements world-class UML capabilities with MDA features such as architecture-driven modeling assistants, MDA precision verifiers, MDA-Cartridge management etc. UML Project. UML projects are managed by the UML Engine. The main ingredient of a UML project is a UML model. In addition, a UML project contains configuration information relating to e.g. diagram display or module locations. An MDA project can include one or more UML projects. User interface. External interface of a software system which allows a user to interact with the software system. MDA support via Accessors in the ArcStyler. W Walk-through. (CA). XP/Convergent Engineering role playing technique used to identify and record dynamic aspects of the business during business modeling. In this technique, the design team walks through the operation of the model under various conditions, making sure the model demonstrates the appropriate behavior in all cases. Used to further refine and check the completeness and business relevance of the model. Web application. Special type of Deployable component in the ArcStyler representing a Web application archive. Packages Accessor and Representer components. Specialization of the UML type Component, stereotype Webapplication. ArcStyler Glossary 19
20 Workspace Area. The workspace of the ArcStyler GUI is divided into five areas: center, right, left, bottom, and top. Each tool configured in a Perspective can be assigned to one of the five Workspace Areas of the ArcStyler. X XMI (XML Metadata Interchange). Standard that defines for a given metamodel how to represent the corresponding models in XML. Part of the MOF specification. Currently, ArcStyler supports XMI versions 1.0 and 1.1. You can use it to load existing models that are provided in XMI format into ArcStyler, or to export models you have created with ArcStyler for use with other XMI-capable tools. 20 ArcStyler Glossary
21 Appendix Symbols *.asprj. Suffix of ArcStyler project files. *.bin. Suffix of precompiled Template libraries. *.cfg. Suffix of ArcStyler configuration files. *.guicfg. Suffix of ArcStyler project files *.inc. Suffix of Include files. *.info. Suffix of Tool information files. *.jpr / *.jpx. Suffix of JBuilder project files. *.py. Suffix of Python script files. *.timestamp. Suffix of files with timestamp control. *.tpr. Suffix of Technology projection files. *.tpl. Suffix of Template files. *.xml. Suffix of ArcStyler configuration files. Acronyms CA - Convergent Architecture CC - Convergent Components CE - Convergent Engineering C-MOD - Common UML/JMI/XMI Model Repository and Integrator CARAT - ArcStyler MDA Cartridge ArchiTecture EJB - Enterprise JavaBeans OPR - Organizations, Processes and Resources RASC - Reduced Abstraction Set Computing ArcStyler Glossary 21
22 Synonyms Cartridge: MDA-Cartridge C-GEN-IDE: MDA-Cartridge IDE C-GEN: MDA Engine Technology Projection: MDA-Cartridge Transformation: MDA-Cartridge JPython: Jython (has replaced the name JPython) MDA-Harvesting: MDA-Enabling MDA-Security Cartridge: MDA-Security Support For further information please visit the ArcStyler home page at or e- mail to Bibliography [Hub01] [Tay95] Hubert, Richard. Convergent Architecture: Building Model-Driven J2EE Systems with UML. J. Wiley & Sons Inc./OMG Press, Taylor, David A. Business Engineering with Object Technology. J. Wiley & Sons Inc., ArcStyler Glossary
Model-Driven Architecture
THE IT-ARCHITECTURE PROFESSIONALS Model-Driven Architecture Stephen J. Mellor, Kendall Scott, Axel Uhl, Dirk Weise Interactive Objects Software info@io-software.com Agenda 2 Motivation for MDA Terminology:
More informationNetBeans IDE Field Guide
NetBeans IDE Field Guide Copyright 2005 Sun Microsystems, Inc. All rights reserved. Table of Contents Extending Web Applications with Business Logic: Introducing EJB Components...1 EJB Project type Wizards...2
More informationChapter 1 GETTING STARTED. SYS-ED/ Computer Education Techniques, Inc.
Chapter 1 GETTING STARTED SYS-ED/ Computer Education Techniques, Inc. Objectives You will learn: WSAD. J2EE business topologies. Workbench. Project. Workbench components. Java development tools. Java projects
More informationVision of J2EE. Why J2EE? Need for. J2EE Suite. J2EE Based Distributed Application Architecture Overview. Umair Javed 1
Umair Javed 2004 J2EE Based Distributed Application Architecture Overview Lecture - 2 Distributed Software Systems Development Why J2EE? Vision of J2EE An open standard Umbrella for anything Java-related
More informationComputation Independent Model (CIM): Platform Independent Model (PIM): Platform Specific Model (PSM): Implementation Specific Model (ISM):
viii Preface The software industry has evolved to tackle new approaches aligned with the Internet, object-orientation, distributed components and new platforms. However, the majority of the large information
More informationIDERA ER/Studio Software Architect Evaluation Guide. Version 16.5/2016+ Published February 2017
IDERA ER/Studio Software Architect Evaluation Guide Version 16.5/2016+ Published February 2017 2017 IDERA, Inc. All rights reserved. IDERA and the IDERA logo are trademarks or registered trademarks of
More informationThe Eclipse Modeling Framework and MDA Status and Opportunities
The Eclipse Modeling Framework and MDA Status and Opportunities David Frankel Consulting df@davidfrankelconsulting.com www.davidfrankelconsulting.com Portions adapted from the book Model Driven Architecture:
More information* Corresponding Author
A Model Driven Architecture for REA based systems Signe Ellegaard Borch, Jacob Winther Jespersen, Jesper Linvald, Kasper Østerbye* IT University of Copenhagen, Denmark * Corresponding Author (kasper@it-c.dk)
More informationDeveloping Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach
Developing Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach Ninat Wanapan and Somnuk Keretho Department of Computer Engineering, Kasetsart
More informationImplementing a Web Service p. 110 Implementing a Web Service Client p. 114 Summary p. 117 Introduction to Entity Beans p. 119 Persistence Concepts p.
Acknowledgments p. xvi Introduction p. xvii Overview p. 1 Overview p. 3 The Motivation for Enterprise JavaBeans p. 4 Component Architectures p. 7 Divide and Conquer to the Extreme with Reusable Services
More informationinnoq Deutschland GmbH innoq Schweiz GmbH D Ratingen CH-6330 Cham Tel Tel
innoq Deutschland GmbH innoq Schweiz GmbH D-40880 Ratingen CH-6330 Cham Tel +49 2102 77 1620 Tel +41 41 743 01 11 www.innoq.com Stefan Tilkov, stefan.tilkov@innoq.com 1 Goals Introduce MDE, MDA, MDD, MDSD,...
More informationAppendix A - Glossary(of OO software term s)
Appendix A - Glossary(of OO software term s) Abstract Class A class that does not supply an implementation for its entire interface, and so consequently, cannot be instantiated. ActiveX Microsoft s component
More informationJ2EE Interview Questions
1) What is J2EE? J2EE Interview Questions J2EE is an environment for developing and deploying enterprise applications. The J2EE platform consists of a set of services, application programming interfaces
More informationFREQUENTLY ASKED QUESTIONS
Borland Together FREQUENTLY ASKED QUESTIONS GENERAL QUESTIONS What is Borland Together? Borland Together is a visual modeling platform that enables software teams to consistently deliver on-time, high
More informationComponent-based Architecture Buy, don t build Fred Broks
Component-based Architecture Buy, don t build Fred Broks 1. Why use components?... 2 2. What are software components?... 3 3. Component-based Systems: A Reality!! [SEI reference]... 4 4. Major elements
More informationDesigning a Distributed System
Introduction Building distributed IT applications involves assembling distributed components and coordinating their behavior to achieve the desired functionality. Specifying, designing, building, and deploying
More informationChapter 1 GETTING STARTED. SYS-ED/ Computer Education Techniques, Inc.
Chapter 1 GETTING STARTED SYS-ED/ Computer Education Techniques, Inc. Objectives You will learn: The IDE: Integrated Development Environment. MVC: Model-View-Controller Architecture. BC4J: Business Components
More informationIntroduction to componentbased software development
Introduction to componentbased software development Nick Duan 8/31/09 1 Overview What is a component? A brief history of component software What constitute the component technology? Components/Containers/Platforms
More informationAppDev StudioTM 3.2 SAS. Migration Guide
SAS Migration Guide AppDev StudioTM 3.2 The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2006. SAS AppDev TM Studio 3.2: Migration Guide. Cary, NC: SAS Institute Inc.
More informationMETADATA INTERCHANGE IN SERVICE BASED ARCHITECTURE
UDC:681.324 Review paper METADATA INTERCHANGE IN SERVICE BASED ARCHITECTURE Alma Butkovi Tomac Nagravision Kudelski group, Cheseaux / Lausanne alma.butkovictomac@nagra.com Dražen Tomac Cambridge Technology
More informationindex_ qxd 7/18/02 11:48 AM Page 259 Index
index_259-265.qxd 7/18/02 11:48 AM Page 259 Index acceptance testing, 222 activity definition, 249 key concept in RUP, 40 Actor artifact analysis and iterative development, 98 described, 97 136 in the
More informationIBM Rational Application Developer for WebSphere Software, Version 7.0
Visual application development for J2EE, Web, Web services and portal applications IBM Rational Application Developer for WebSphere Software, Version 7.0 Enables installation of only the features you need
More informationModel Driven Development of Component Centric Applications
Model Driven Development of Component Centric Applications Andreas Heberle (entory AG), Rainer Neumann (PTV AG) Abstract. The development of applications has to be as efficient as possible. The Model Driven
More informationB. Assets are shared-by-copy by default; convert the library into *.jar and configure it as a shared library on the server runtime.
Volume A~B: 114 Questions Volume A 1. Which component type must an integration solution developer define for a non-sca component such as a Servlet that invokes a service component interface? A. Export
More informationMetamodeling. Janos Sztipanovits ISIS, Vanderbilt University
Metamodeling Janos ISIS, Vanderbilt University janos.sztipanovits@vanderbilt.edusztipanovits@vanderbilt edu Content Overview of Metamodeling Abstract Syntax Metamodeling Concepts Metamodeling languages
More informationPOAD Book: Chapter 4: Design Patterns as Components Chapter 5: Visual Design Models
POAD Book: Chapter 4: Design Patterns as Components Chapter 5: Visual Design Models Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU Outline Chapter 4: Design Patterns
More informationFrom Models to Components. Rapid Service Creation with
From Models to Components Rapid Service Creation with Marc Born, Olaf Kath {born kath}@ikv.de Evolutions in Software Construction C O M P L E X I T Y Model Driven Architectures Meta Object Facility and
More informationAn introduction to MOF MetaObject Facility.
An introduction to MOF MetaObject Facility pierre-alain.muller@irisa.fr About The MetaObject Facility Specification is the foundation of OMG's industry-standard standard environment where models can be
More informationApplication Servers in E-Commerce Applications
Application Servers in E-Commerce Applications Péter Mileff 1, Károly Nehéz 2 1 PhD student, 2 PhD, Department of Information Engineering, University of Miskolc Abstract Nowadays there is a growing demand
More informationIBM Rational Software Architect
Unifying all aspects of software design and development IBM Rational Software Architect A complete design & development toolset Incorporates all the capabilities in IBM Rational Application Developer for
More informationIBM. IBM WebSphere Application Server Migration Toolkit. WebSphere Application Server. Version 9.0 Release
WebSphere Application Server IBM IBM WebSphere Application Server Migration Toolkit Version 9.0 Release 18.0.0.3 Contents Chapter 1. Overview......... 1 Chapter 2. What's new........ 5 Chapter 3. Support..........
More informationComposer Guide for JavaScript Development
IBM Initiate Master Data Service Version 10 Release 0 Composer Guide for JavaScript Development GI13-2630-00 IBM Initiate Master Data Service Version 10 Release 0 Composer Guide for JavaScript Development
More informationSocket attaches to a Ratchet. 2) Bridge Decouple an abstraction from its implementation so that the two can vary independently.
Gang of Four Software Design Patterns with examples STRUCTURAL 1) Adapter Convert the interface of a class into another interface clients expect. It lets the classes work together that couldn't otherwise
More informationSecond OMG Workshop on Web Services Modeling. Easy Development of Scalable Web Services Based on Model-Driven Process Management
Second OMG Workshop on Web Services Modeling Easy Development of Scalable Web Services Based on Model-Driven Process Management 88 solutions Chief Technology Officer 2003 Outline! Introduction to Web Services!
More informationModel driven Engineering & Model driven Architecture
Model driven Engineering & Model driven Architecture Prof. Dr. Mark van den Brand Software Engineering and Technology Faculteit Wiskunde en Informatica Technische Universiteit Eindhoven Model driven software
More informationModellierung operationaler Aspekte von Systemarchitekturen. Master Thesis presentation. October 2005 March Mirko Bleyh - Medieninformatik
Modellierung operationaler Aspekte von Systemarchitekturen Master Thesis presentation October 2005 March 2006 Agenda Goals Model-Driven Software Development Pro-active Infrastructure (PAI) Operational
More informationNew Features Summary PowerDesigner 15.2
New Features Summary PowerDesigner 15.2 Windows DOCUMENT ID: DC10077-01-1520-01 LAST REVISED: February 2010 Copyright 2010 by Sybase, Inc. All rights reserved. This publication pertains to Sybase software
More informationJAVA COURSES. Empowering Innovation. DN InfoTech Pvt. Ltd. H-151, Sector 63, Noida, UP
2013 Empowering Innovation DN InfoTech Pvt. Ltd. H-151, Sector 63, Noida, UP contact@dninfotech.com www.dninfotech.com 1 JAVA 500: Core JAVA Java Programming Overview Applications Compiler Class Libraries
More informationOMG Specifications for Enterprise Interoperability
OMG Specifications for Enterprise Interoperability Brian Elvesæter* Arne-Jørgen Berre* *SINTEF ICT, P. O. Box 124 Blindern, N-0314 Oslo, Norway brian.elvesater@sintef.no arne.j.berre@sintef.no ABSTRACT:
More informationDictionary Driven Exchange Content Assembly Blueprints
Dictionary Driven Exchange Content Assembly Blueprints Concepts, Procedures and Techniques (CAM Content Assembly Mechanism Specification) Author: David RR Webber Chair OASIS CAM TC January, 2010 http://www.oasis-open.org/committees/cam
More informationPractical Model-Driven Development with the IBM Software Development Platform
IBM Software Group Practical Model-Driven Development with the IBM Software Development Platform Osmond Ng (ong@hk1.ibm.com) Technical Consultant, IBM HK SWG 2005 IBM Corporation Overview The Challenges
More informationIBM. Developing with IBM Rational Application Developer for WebSphere Software V6
IBM 000-255 Developing with IBM Rational Application Developer for WebSphere Software V6 Download Full Version : http://killexams.com/pass4sure/exam-detail/000-255 Answer: C QUESTION: 99 A developer is
More informationSUN Enterprise Development with iplanet Application Server
SUN 310-540 Enterprise Development with iplanet Application Server 6.0 http://killexams.com/exam-detail/310-540 QUESTION: 96 You just created a new J2EE application (EAR) file using iasdt. How do you begin
More informationWorkpackage 15: DBE Business Modeling Language. Deliverable D15.5: BML Editor Final Release
Contract n 507953 Workpackage 15: DBE Business Modeling Language Deliverable D15.5: BML Editor Final Release Project funded by the European Community under the Information Society Technology Programme
More informationMDA & Semantic Web Services Integrating SWSF & OWL with ODM
MDA & Semantic Web Services Integrating SWSF & OWL with ODM Elisa Kendall Sandpiper Software March 30, 2006 Level Setting An ontology specifies a rich description of the Terminology, concepts, nomenclature
More informationEMC Documentum Composer
EMC Documentum Composer Version 6.0 SP1.5 User Guide P/N 300 005 253 A02 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748 9103 1 508 435 1000 www.emc.com Copyright 2008 EMC Corporation. All
More informationArchiMate 2.0. Structural Concepts Behavioral Concepts Informational Concepts. Business. Application. Technology
ArchiMate Core Structural Concepts Behavioral Concepts Informational Concepts interaction Technology Application Layer Concept Description Notation Concept Description Notation Actor An organizational
More informationIBM Rational Developer for System z Version 7.5
Providing System z developers with tools for building traditional and composite applications in an SOA and Web 2.0 environment IBM Rational Developer for System z Version 7.5 Highlights Helps developers
More informationIntroduction. Enterprise Java Instructor: Please introduce yourself Name Experience in Java Enterprise Edition Goals you hope to achieve
Enterprise Java Introduction Enterprise Java Instructor: Please introduce yourself Name Experience in Java Enterprise Edition Goals you hope to achieve Course Description This course focuses on developing
More informationModelling in Enterprise Architecture. MSc Business Information Systems
Modelling in Enterprise Architecture MSc Business Information Systems Models and Modelling Modelling Describing and Representing all relevant aspects of a domain in a defined language. Result of modelling
More informationModel Driven Development Unified Modeling Language (UML)
Model Driven Development Unified Modeling Language (UML) An Overview UML UML is a modeling notation standardized by OMG (proposal 1997, ver.1.1 in 1998, ver. 2.0 in 2004) now in 2.4.1 mature based on notations
More informationEnterprise JavaBeans. Layer:01. Overview
Enterprise JavaBeans Layer:01 Overview Agenda Course introduction & overview. Hardware & software configuration. Evolution of enterprise technology. J2EE framework & components. EJB framework & components.
More informationOracle Application Development Framework Overview
An Oracle White Paper July 2009 Oracle Application Development Framework Overview Introduction... 1 Oracle ADF Making Java EE Development Simpler... 2 THE ORACLE ADF ARCHITECTURE... 3 The Business Services
More informationESPRIT Project N Work Package H User Access. Survey
ESPRIT Project N. 25 338 Work Package H User Access Survey ID: User Access V. 1.0 Date: 28.11.97 Author(s): A. Sinderman/ E. Triep, Status: Fast e.v. Reviewer(s): Distribution: Change History Document
More informationImproving Military Information Technology Through Common Conceptual Models
Improving Military Information Technology Through Common Conceptual Models Andreas Tolk, Ph.D. Virginia Modeling Analysis and Simulation Center Old Dominion University Presentation Outline Common Conceptual
More informationTeiid Designer User Guide 7.5.0
Teiid Designer User Guide 1 7.5.0 1. Introduction... 1 1.1. What is Teiid Designer?... 1 1.2. Why Use Teiid Designer?... 2 1.3. Metadata Overview... 2 1.3.1. What is Metadata... 2 1.3.2. Editing Metadata
More informationJ2EE Application Development with WebSphere Studio
. J2EE Application Development with WebSphere Studio page 2 IBM Application Development Vision Delivering a rapid and efficient response to business needs through a powerful development and deployment
More informationCHAPTER 6. Organizing Your Development Project. All right, guys! It s time to clean up this town!
CHAPTER 6 Organizing Your Development Project All right, guys! It s time to clean up this town! Homer Simpson In this book we describe how to build applications that are defined by the J2EE specification.
More informationModel Driven Architecture - The Vision
Model Driven Architecture - The Vision Marko Fabiunke Fraunhofer Institut für Rechnerarchitektur und Softwaretechnik marko.fabiunke@first.fraunhofer.de The Fraunhofer FIRST Institut Your partner We support
More informationChapter 2 FEATURES AND FACILITIES. SYS-ED/ Computer Education Techniques, Inc.
Chapter 2 FEATURES AND FACILITIES SYS-ED/ Computer Education Techniques, Inc. Objectives You will learn: JDeveloper features. Java in the database. Simplified database access. IDE: Integrated Development
More informationGenerating JMI model transformation code from UML profile models for SDM Aligning Graph Rewriting with MDA-light
Segravis School on Foundations of Visual Modelling Techniques, May 2004, Schloss Dagstuhl Generating JMI model transformation code from UML profile models for SDM Aligning Graph Rewriting with MDA-light
More information(9A05803) WEB SERVICES (ELECTIVE - III)
1 UNIT III (9A05803) WEB SERVICES (ELECTIVE - III) Web services Architecture: web services architecture and its characteristics, core building blocks of web services, standards and technologies available
More informationMobile Application Workbench. SAP Mobile Platform 3.0 SP02
SAP Mobile Platform 3.0 SP02 DOCUMENT ID: DC-01-0302-01 LAST REVISED: January 2014 Copyright 2014 by SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced
More informationSUMMARY: MODEL DRIVEN SECURITY
SUMMARY: MODEL DRIVEN SECURITY JAN-FILIP ZAGALAK, JZAGALAK@STUDENT.ETHZ.CH Model Driven Security: From UML Models to Access Control Infrastructres David Basin, Juergen Doser, ETH Zuerich Torsten lodderstedt,
More informationArchitecture. Readings and References. Software Architecture. View. References. CSE 403, Spring 2003 Software Engineering
Readings and References Architecture CSE 403, Spring 2003 Software Engineering http://www.cs.washington.edu/education/courses/403/03sp/ References» Software Architecture, David Garlan, CMU, 2001 http://www-2.cs.cmu.edu/~able/publications/encycse2001/»
More informationFusion Registry 9 SDMX Data and Metadata Management System
Registry 9 Data and Management System Registry 9 is a complete and fully integrated statistical data and metadata management system using. Whether you require a metadata repository supporting a highperformance
More informationBusiness Process Testing
Business Process Testing Software Version: 12.55 User Guide Go to HELP CENTER ONLINE http://admhelp.microfocus.com/alm/ Document Release Date: August 2017 Software Release Date: August 2017 Legal Notices
More informationSoftware Industrialization
Software Industrialization A Perspective on MDA David Frankel Consulting df@davidfrankelconsulting.com www.davidfrankelconsulting.com Portions adapted from the book Model Driven Architecture: Applying
More informationJ2EEML: Applying Model Driven Development to Autonomic Enterprise Java Bean Systems
J2EEML: Applying Model Driven Development to Autonomic Enterprise Java Bean Systems Jules White jules@dre.vanderbilt.edu Institute for Software Integrated Systems (ISIS) Vanderbilt University Nashville,
More informationThe Model-Driven Semantic Web Emerging Standards & Technologies
The Model-Driven Semantic Web Emerging Standards & Technologies Elisa Kendall Sandpiper Software March 24, 2005 1 Model Driven Architecture (MDA ) Insulates business applications from technology evolution,
More informationQoS-aware model-driven SOA using SoaML
QoS-aware model-driven SOA using SoaML Niels Schot A thesis submitted for the degree of MSc Computer Science University of Twente EEMCS - TRESE: Software Engineering Group Examination committee: Luís Ferreira
More informationEMC Documentum Composer
EMC Documentum Composer Version 6.5 SP2 User Guide P/N 300-009-462 A01 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.emc.com Copyright 2008 2009 EMC Corporation. All
More informationActive Endpoints. ActiveVOS Platform Architecture Active Endpoints
Active Endpoints ActiveVOS Platform Architecture ActiveVOS Unique process automation platforms to develop, integrate, and deploy business process applications quickly User Experience Easy to learn, use
More informationVocabulary-Driven Enterprise Architecture Development Guidelines for DoDAF AV-2: Design and Development of the Integrated Dictionary
Vocabulary-Driven Enterprise Architecture Development Guidelines for DoDAF AV-2: Design and Development of the Integrated Dictionary December 17, 2009 Version History Version Publication Date Author Description
More informationObject Security. Model Driven Security. Ulrich Lang, Rudolf Schreiner. Protection of Resources in Complex Distributed Systems
Object Security TM The Security Policy Company Protection of Resources in Complex Distributed Systems Ulrich Lang, Rudolf Schreiner ObjectSecurity Ltd. University of Cambridge Agenda COACH Project Model
More informationBEAWebLogic. Server. Deploying Applications to WebLogic Server
BEAWebLogic Server Deploying Applications to WebLogic Server Version 9.2 Revised: August 10, 2006 Copyright Copyright 1995-2006 BEA Systems, Inc. All Rights Reserved. Restricted Rights Legend This software
More informationArchitecture. CSE 403, Winter 2003 Software Engineering.
Architecture CSE 403, Winter 2003 Software Engineering http://www.cs.washington.edu/education/courses/403/03wi/ 21-February-2003 cse403-14-architecture 2003 University of Washington 1 References Readings
More informationDeveloping Java TM 2 Platform, Enterprise Edition (J2EE TM ) Compatible Applications Roles-based Training for Rapid Implementation
Developing Java TM 2 Platform, Enterprise Edition (J2EE TM ) Compatible Applications Roles-based Training for Rapid Implementation By the Sun Educational Services Java Technology Team January, 2001 Copyright
More informationJBoss SOAP Web Services User Guide. Version: M5
JBoss SOAP Web Services User Guide Version: 3.3.0.M5 1. JBoss SOAP Web Services Runtime and Tools support Overview... 1 1.1. Key Features of JBossWS... 1 2. Creating a Simple Web Service... 3 2.1. Generation...
More informationOracle9i Application Server Architecture and Com
Oracle9i Application Server Quick Tour: Architecture Page 1 de 7 Oracle9i Application Server Architecture and Com Standard Edition Enterprise Edition Wireless Edition Services and Components To provide
More informationchallenges in domain-specific modeling raphaël mannadiar august 27, 2009
challenges in domain-specific modeling raphaël mannadiar august 27, 2009 raphaël mannadiar challenges in domain-specific modeling 1/59 outline 1 introduction 2 approaches 3 debugging and simulation 4 differencing
More informationDEV427 MODEL-DRIVEN DEVELOPMENT USING PowerDesigner. Xiao-Yun WANG PowerDesigner Chief Architect
DEV427 MODEL-DRIVEN DEVELOPMENT USING PowerDesigner Xiao-Yun WANG PowerDesigner Chief Architect xwang@sybase.com OBJECTIVES 1. Understand what s Model-Driven Development 2. Understand why Model-Driven
More informationThe Unified Modelling Language. Example Diagrams. Notation vs. Methodology. UML and Meta Modelling
UML and Meta ling Topics: UML as an example visual notation The UML meta model and the concept of meta modelling Driven Architecture and model engineering The AndroMDA open source project Applying cognitive
More informationIBM WebSphere Studio Asset Analyzer, Version 5.1
Helping you quickly understand, enhance and maintain enterprise applications IBM, Version 5.1 Highlights n Provides interactive textual n Helps shorten the learning curve and graphic reports that help
More informationDefining Domain-Specific Modeling Languages
Defining Domain-Specific Modeling Languages 1 st Oct 2008 Juha-Pekka Tolvanen MetaCase 1 Relevant language classifications to start with General-Purpose / Domain-Specific Narrow area of interest Often
More informationData Center Management and Automation Strategic Briefing
Data Center and Automation Strategic Briefing Contents Why is Data Center and Automation (DCMA) so important? 2 The Solution Pathway: Data Center and Automation 2 Identifying and Addressing the Challenges
More informationJ2EE Development. Course Detail: Audience. Duration. Course Abstract. Course Objectives. Course Topics. Class Format.
J2EE Development Detail: Audience www.peaksolutions.com/ittraining Java developers, web page designers and other professionals that will be designing, developing and implementing web applications using
More informationSRI VENKATESWARA COLLEGE OF ENGINERRING AND TECHNOLOGY THIRUPACHUR,THIRUVALLUR UNIT I OOAD PART A
SRI VENKATESWARA COLLEGE OF ENGINERRING AND TECHNOLOGY THIRUPACHUR,THIRUVALLUR UNIT I OOAD PART A 1. What is an object? An object is a combination of data and logic; the representation of some realworld
More informationJ2EE Application Development : Conversion and Beyond Osmond Ng
IBM Software Group J2EE Application Development : Conversion and Beyond Osmond Ng IBM Software Group Practitioner View Point IBM Rational Application Developer J2EE/EJB Tooling J2EE construction tools
More informationBuilding JavaServer Faces Applications
IBM Software Group St. Louis Java User Group Tim Saunders ITS Rational Software tim.saunders@us.ibm.com 2005 IBM Corporation Agenda JSF Vision JSF Overview IBM Rational Application Developer v6.0 Build
More informationCHARLES UNIVERSITY, PRAGUE FACULTY OF MATHEMATICS AND PHYSICS. Master Thesis. Michael Cífka Visual Development of Software Components
CHARLES UNIVERSITY, PRAGUE FACULTY OF MATHEMATICS AND PHYSICS Master Thesis Michael Cífka Visual Development of Software Components Supervisor: Ing. Petr Tůma, Dr. I would like to thank my supervisor,
More informationISO INTERNATIONAL STANDARD. Financial services Universal financial industry message scheme Part 3: Modelling
INTERNATIONAL STANDARD ISO 20022-3 First edition 2013-05-01 Financial services Universal financial industry message scheme Part 3: Modelling Services financiers Schéma universel de messages pour l'industrie
More informationComparative analysis of MDA tools
STUDIA INFORMATICA Nr 1-2(16) Systems and information technology 2012 Comparative analysis of MDA tools Krzysztof Pietraszek 1 1 Institute of Computer Science, University of Natural Sciences and Humanities,
More informationDistributed Multitiered Application
Distributed Multitiered Application Java EE platform uses a distributed multitiered application model for enterprise applications. Logic is divided into components https://docs.oracle.com/javaee/7/tutorial/overview004.htm
More informationI Got My Mojo Workin'
I Got My Mojo Workin' Gary Murphy Hilbert Computing, Inc. http://www.hilbertinc.com/ glm@hilbertinc.com Gary Murphy I Got My Mojo Workin' Slide 1 Agenda Quick overview on using Maven 2 Key features and
More informationTeiid Designer User Guide 7.7.0
Teiid Designer User Guide 1 7.7.0 1. Introduction... 1 1.1. What is Teiid Designer?... 1 1.2. Why Use Teiid Designer?... 2 1.3. Metadata Overview... 2 1.3.1. What is Metadata... 2 1.3.2. Editing Metadata
More informationOverview p. 1 Server-side Component Architectures p. 3 The Need for a Server-Side Component Architecture p. 4 Server-Side Component Architecture
Preface p. xix About the Author p. xxii Introduction p. xxiii Overview p. 1 Server-side Component Architectures p. 3 The Need for a Server-Side Component Architecture p. 4 Server-Side Component Architecture
More informationIntelligence on Demand. Elixir Report Migration Guide
Intelligence on Demand Elixir Report Migration Guide Elixir Report Migration Guide Migration Guide This document describes how to migrate from Elixir Report version 4 to Elixir Report version 5 or later.
More informationKlocwork Architecture Excavation Methodology. Nikolai Mansurov Chief Scientist & Architect
Klocwork Architecture Excavation Methodology Nikolai Mansurov Chief Scientist & Architect Overview! Introduction Production of software is evolutionary and involves multiple releases Evolution of existing
More informationModel Driven Architecture
Name: Anish Mehta Year: 3 Lecturer: Dr. Wolfgang Emmerich Supervisor: Dr. Graham Roberts Model Driven Architecture For many years architects have been designing buildings by looking at other architects
More information