Object Management Group OMG (2003) - "Unified Modeling Language Specification, version 1.5", 1st ed., http://www.omg.org  Home/Search   Document Not in Database   Summary   Related Articles   Check

....and complex domains. Special emphasis lies on the modeling and design phase, the concurrent implementation and the recurring maintenance and evolution activities. We also provide a tool suite to support the XGuide process that is presented in Chapter 6. Figure 4. 1 depicts the activity diagram [27, 122, 128] for the XGuide process. Figure 4.1: The XGuide Development Process At the beginning of the process, a detailed requirements analysis creates a common vision of the goal and a shared vocabulary and domain understanding among all the parties involved. At the end of the requirements phase, all ....

....responsible for the user interface and represents the third tier. Compared to the requirements phase, the design is a more complex process. In the field of traditional software engineering, established design notations for software systems exist among which the Unified Modeling Language (UML) [122,128] has a prominent position today. In Web engineering, however, a widely accepted notation for modeling Web applications does not exist. Instead, every approach defines its own notation to best represent the main focus of the respective method. Well known examples of such notations include the ....

Object Management Group. Unified Modeling Language Specification Version 1.4. Technical report, Sep 2001.

....modeling, reuse and roundtrip development of metalevel designs. We also demonstrate the seamless model exchange between different development tools and model continuity across development phases with application neutral interchange formats. 1 Introduction The Unified Modeling Language (UML) [1] has been widely accepted as a stan dard modeling language in the software engineering community. It defines semantics and their notations of model elements required for documenting object oriented software. It is a single and universal language that can be used with any design methodology. UML ....

....model interchange is a very important capability, because there are few application neutral model exchange formats between development tools. To solve this problem, we developed the UML exchange Format (UXF) 21] which is similar in some respects to the XML Metamodel Interchange (XMI) format [1], standardized by the Object Management Group. Both UXF and XMI are based on XML and allow model semantics to be de scribed explicitly and transferred precisely. Such application neutral interchange format facilitates: Interchangeability and reuse of metalevel descriptions: Software models ....

[Article contains additional citation context not shown here]

Object Management Group. Unified Modeling Language Specification version 1.3. OMG document number: ad/99-06-08, 1999.

....techniques and heuristics gained through experience, so members continue to benefit even though they are already high performing experts. This course is intended to help the development teams gain skills in distributed software development. Our courses use the Unified Modeling Language (UML) [4] as the modeling language. UML is a standard objectoriented modeling method that provides most of the semantics and their notations required for representing software constructs, and has been widely accepted by academic and commercial developers. Our courses also use an XML based format for ....

Object Management Group, Unified Modeling Language Specification version 1.3 beta R1, 1999, at http://uml.systemhouse.mci.com/artifacts.htm.

....Oriented Modelling (OOM) 4, 5 and 6] is especially related to the provided reuse resources. However, it still requires more formalism for the Requirements Specification [7] and, if compared to Formal Techniques, presents gaps, which result in problems [3] UML (The Unified Modeling Language) [8, 9, 10] is an important step forward the standardisation of the OO models representation [11] but it doesn t provide mapping procedures between the development phases. The use of formal techniques [7, 12] allows consistence analysis and system behaviour simulation, through wellSilvino Jos Silva Bastos ....

....The formal language SDL (Specification and Description Language) 13] was selected as a transformation target language. The selection was based on the great conceptual similarity between the modelling elements of both languages. 2 UML The Unified Modeling Language [8] standardised by OMG [9], is defined as a collection of diagrams that represent the different properties of the modelled system [14] UML also includes the concept of packages, which are containers used to group the model elements inside a same container. 2.1 UML System Modelling Different authors [15, 16] suggest ....

OBJECT MANAGEMENT GROUP. Unified Modeling Language Specification: version 1.3. OMG, 1999.

....which have to be detected and resolved 1 . Sequence diagrams alone do not contain enough semantic information to enable the automatic detection of conflicts, but this information can be obtained by allowing the user to express constraints on the diagrams, using the Object Constraint Language [2] (OCL) The addition of semantic information also allows a justified merging of multiple scenarios. Different scenarios will often contain identical or similar behav 1 This is similar to the feature interactions problem of the telecommunications industry [3] 1 iors, and the use of OCL allows ....

....together. This is not straightforward, however. In this context, OCL is being used to express dynamic rather than static constraints. 4 None of the approaches to semantics so far adequately address timing constraints which are important in a real time setting. According to the UML documentation [2], timing constraints can be attached as annotations at the side of sequence diagrams. In [6] the authors examine the the problem of respecting these constraints in a translation into FSMs, but they do not address how to check the consistency of timing constraints. In addition, they do not ....

Object Management Group. Unified modeling language specification version 1.3. Available from Rational Software Corporation, Cupertino, CA, June 1999.

....integrated into more comprehensive information models. This task is greatly simplified by concentrating on the integration of conceptual models rather than the integration of isolated concrete MIB data definitions. 3 Representing Conceptual MIB Models in UML The Unified Modeling Language (UML) [2, 3] has become the lingua franca for visualizing, specifying and documenting artifacts of software intensive systems. UML is very rich and features several diagram types to represent structural, behavioral and architectural aspects. Current MIB modules only specify structural aspects in a machine ....

Object Management Group. Unified Modeling Language Specification Version 1.3. Formal Specification, Object Management Group, March 2000.

....development With the aspect support, the incremental and roundtrip development of aspect oriented software is possible, e.g. aspect code design model translation, model aspect code, woven code model translation, aspect refactoring (see also Figure 1) 2. 2 Unified Modeling Language (UML) UML [4] is the union of the previous leading object modeling methodologies; Booch, OMT and OOSE. It is the state of the art convergence of practices in the academic and industrial community, and has been a standard modeling language by the Object Management Group (OMG) 5] UML defines 9 diagrams for ....

....class to the metamodel, and reused an existing element for the aspect class relationship. 3.1 Aspect First of all, the aspect should be added to the UML metamodel. It is no doubt the aspect is a construct derived from the Classifier element, which describes behavioral and structural features [4] (Figure 3) All the Class, Interface and Component are kinds of Classifier. Aspect can have attributes, operations and relationships. Attributes of an aspect is used by its set of weave definition. Operations of an aspect is considered as its weave declarations. Relationships of an aspect ....

[Article contains additional citation context not shown here]

Object Management Group, Unified Modeling Language Specification version 1.3 bata 1, 1999. available at uml.shl.com.

No context found.

Object Management Group OMG (2003) - "Unified Modeling Language Specification, version 1.5", 1st ed., http://www.omg.org

No context found.

Object Management Group. Unified Modeling Language specification version 1.5. formal/2003-03-01, March 2003.

No context found.

Object Management Group. Unified Modeling Language specification version 1.5. formal/2003-03-01, March 2003.

No context found.

Object Management Group, "Unified Modeling Language Specification, Version 1.4", September 2001.

No context found.

Object Management Group, 1999, "Unified Modeling Language Specification, Version 1.3", http://www.rational.com/uml/resources/documentat ion

No context found.

Unified Modeling Language Specification Version 1.3, Framingham, MA, USA: Object Management Group.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC