UML modeling

Developing Chemical Information Systems An Object-Oriented Approach Using Enterprise Java, by Fan Li Copyright 2007 John Wiley Sons, Inc. 

UML diagrams will be used throughout this book. 

---

The Object Constraint Language (OCL), a standard part of UML 1.1, is a specification language used in conjunction with UML models. It is an expression-based, side-effect-free language that eschews mathematical symbols (V, 3, and so on) for textual equivalents (forAII, exists). It uses a syntax more usual in object-oriented languages V x T, p(x) becomes T->forAII (x x.p). 

In our cooperation with innotec, we currently develop an integrator tool between the data structure definition of Comos PT and corresponding UML models. 

Fig. 3.64. UML model of a design process in chemical engineering (modeling environment)...

From the UML model, code is generated to customize the functionality provided by the AHEAD system. For example, the project manager may instantiate only the domain-specific classes and associations defined in the class diagrams. The core system as presented in this section enforces consistency with the process model definition. In this way, we can make sure that design proceeds according to the domain-specific model. A more flexible approach will be discussed in the next section (extending process evolution beyond consistency-preserving instance-level evolution). 

The European process industries have therefore embarked on the CAPE-OPEN initiative [71] in order to accomplish a standardization of simulation interfaces, such that a component-based approach can be followed. This standard has been defined at the conceptual level through UML models. At the middleware implementation level, the standard is both defined in DCOM [847] and CORBA [877]. In IMPROVE, the CORBA version is used. 

Schema evolution is the ability to change deployed schemas, i.e., metadata structures formally describing complex artifacts such as databases, messages, application programs, or workflows. Typical schemas thus include relational database schemas, conceptual ER or UML models, ontologies, XML schemas, software interfaces, and workflow specifications. Obviously, the need for schema evolution occurs very often in order to deal with new or changed requirements, to correct deficiencies in the current schemas, to cope with new insights in a domain, or to migrate to a new platform.

The issue related to this UML modeling tools is that its usage for Human Factors Practitioners and Safety analysts is not so immediate because it is meant to be used primarily by software developers. Furthermore no support is provided for guiding the task analysis interview process. 

The DOORS Next Generation also supports better collaboration and team work in spatial distributed environments [46]. According to the assessment carried out in the survey of CariUo de Gea et al., DOORS is also supporting the elicitation, analysis as well as modeling sub-process of the RE, but is mainly designed for the specification [40]. The use of a proprietary DB reduces the possibility to combine it with the use of other tools, but on the other hand side the support of deriving UML models supports an eflicient development process. 

Weilkiens T (2(X)8) Systems engineering with SysML/UML modeling, analysis, design, 2nd edn. Dpunkt Verlag, Heidelberg... 

Note that the standard MARTE profile [2] has been adopted to specify performance parameters in our UML models. However, it is out of the scope of this paper to provide details of performance annotations, because weU assessed techniques exist for this goal [20]. 

The contribution of this paper can be located among the shaded boxes of Figure 1. A Security Library of UML models is provided in particular, models of Basic Mechanisms are combined to build Composed Mechanisms. 

Majzik, I., Pataricza, A., BondavalU, A. Stochastic Dependability Analysis of System Architecture Based on UML Models. In de Lemos, R., Gacek, C., Romanovsky, A. (eds.) Architecting Dependable Systems. LNCS, vol. 2677, pp. 219-244. Springer, Heidelberg (2003)... 

Giese, H., Klein, E., Burmester, S. Pattern Synthesis from Multiple Scenarios for Parameterized Real-Timed UML Models. In Leue, S., Systa, T.J. (eds.) Scenarios Models, Transformations and Tools. LNCS, vol. 3466, pp. 193-211. Springer, Heidelberg (2005)... 

Our toolset therefore allows UML models to be imported and will generate the corresponding skeletons but the user must add the detailed requirements and specifications. A future version may allow the Perfect specifications and refinements to be embedded in the UML model itself... 

The MDE methodology in MetaMORP(h)OSY is enacted by means of two main components Observer and Translators Observers are used in order to evaluate properties both on (abstract) models and (real) nmning systems. Translators implement both vertical and horizontal transformation [30]. Horizontal transformations translate models into other (formal) ones at the same level of abstraction they are used in order to create analyzable models from descriptive ones (for example real time properties are verified on design models translating UML models into timed automata). Vertical transformation are usually used in MetaMORP(h)OSY in order to translate abstract models into finer grained models. This kind of transformation usually usually is not fully automated. Requirements tracing in vertical transformations requires the creation of proper Observers able to verify abstract requirements on finer grained models. 

The framework covers the entire design phase of models of systems, going beyond the abstraction, next releases will cover largest and varied application contexts in which it makes sense to model the interaction between the components as a multi-agent system for example, anyone familiar with UML models may use the framework and shape it with a MAS system. As already discussed, have been provided tools to extend the framework, that in later versions, could be expanded with new formal verification methods or new properties to be checked on the system. 

A CIM describes a system from the computation independent viewpoint that focuses on the environment of and the requirements for the system. It is independent of how the system is implemented. In general, it is called domain model and may be expressed using business models. The CIM helps to bridge the gap between the experts about the domain and the software engineer. A CIM could consist of UML models and other models of requirements. 

Weilkiens, T. 2008. Systems Engineering with SysML/ UML Modeling, Analysis, Design. Burlington Morgan Kaufmann. 

Schlick, R., Herzner, W., Jobstl, E. Fault-based generation of test cases from UML-models Approach and some experiences. In Flammini, F., Bologna, S., Vittorini, V. (eds.) SAFECOMP 2011. LNCS, vol. 6894, pp. 270-283. Springer, Heidelberg (2011)... 

OCL validation checks concerning consistency and correctness of the functional safety concept are set up. Thus, we provide a computer-aided technique to discover errors in the hazard analysis caused by finding inconsistencies or errors in one or more of the UML models. 

Functional safety concept docnment can be generated by the tool, based on the information contained in our UML models. The resulting documentation can then be used for reviewing purposes. 

Atos Origin Papyrus UML Modelling Tool (February 2011), http //www.papyrusuml.org/... 

---