Connecting Building Design with the Digital Factory by Design Languages to Explore Different Solutions

2021 ◽  
pp. 1-26
Author(s):  
Christopher Voss ◽  
Frank Petzold ◽  
Stephan Rudolph
Keyword(s):  
Systems Engineering ◽  
Unified Modeling Language ◽  
Building Design ◽  
Formal Representation ◽  
Digital Factory ◽  
Unified Modeling ◽  
Software Applications ◽  
Design Languages ◽  
Model Based Systems Engineering ◽  
Factory Building

In engineering, design decisions in one domain exhibit multiple consequences in other domains. These consequences result from the often more or less hidden coupling between the different design domains. In order to examine these consequences, models need to be created. In practice, this is challenging due to the exchange of data between different engineering domains, since different software applications are often used and the effort involved with manual model creation. In this paper, we explore the use of graph-based design languages in a Model-Based Systems Engineering (MBSE) approach to link the digital factory with building design. We also show that the use of a common formal representation based on the Unified Modeling Language (UML) supports the interoperability between the two domains. Finally, we demonstrate how the engineering knowledge for the preliminary design of a factory building can be formally described using graph-based design languages and how the production line of the digital factory can then be used as an input to automatically create valid preliminary designs for the factory building.1

The Established of Language Training Service Standard System Based on System Engineering

2014 ◽  
Vol 971-973 ◽  
pp. 2671-2676
Author(s):  
Su Li Hao ◽  
Ge Bai
Keyword(s):  
Language Learning ◽  
Systems Engineering ◽  
Rapid Development ◽  
Unified Modeling Language ◽  
Standard System ◽  
Language Training ◽  
Unified Modeling ◽  
Market Operation ◽  
Training Services ◽  
Training Service

With the rapid development of economic globalization, communication between government and civil has become more frequent. Language is an effective tool to promote international communication. Language learning has become more important, so it stimulates the progress of language training market. However the training industry still exist many problems, such as the market operation is not standardized, and the training services quality is low. And it is very important to develop standards to normative. Furthermore the standard system is the foundation for developing standards. Applying the theory of systems engineering and unified modeling language (UML), the paper established language training services standard system by extracting vocabulary, initial class diagram and grouping the classes, based on the analysis of interdependent body.

FMDesign: A Tool and Interchange Format for Product Concept Designs

2005 ◽  
Author(s):  
Olof Johansson ◽  
Petter Krus
Keyword(s):  
Systems Engineering ◽  
Unified Modeling Language ◽  
Product Concept ◽  
Unified Modeling ◽  
Model Driven ◽  
Product Models ◽  
Implementation Techniques ◽  
Concept Evaluation ◽  
Uml Class Diagram ◽  
Interchange Format

This paper presents a formalized approach to design product models in the product concept evaluation phases, and exchange the models with other engineering tools using open formats like XML and relational database tables. FMDesign is used for designing product concepts with the aid of integrated stakeholder trees, requirement trees, function-means trees, product concept trees, and implementation trees. It has its foundation in systems engineering and design methodology, and presents a formalization and integration with theory from software engineering that enable similar engineering tools to be implemented with automated model driven software implementation techniques that support the Unified Modeling Language (UML). The paper provides an overview of the theory behind the tool, its user interface, interchange formats and the formal software specification as an UML class diagram.

Unified Modeling Language

2005 ◽  
pp. 2921-2928 ◽  
Author(s):  
Peter Fettke
Keyword(s):  
Systems Engineering ◽  
Subject Matter ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
General Purpose ◽  
Modeling Language ◽  
Unified Modeling ◽  
Object Oriented Systems

Mature engineering disciplines are generally characterized by accepted methodical standards for describing all relevant artifacts of their subject matter. Such standards not only enable practitioners to collaborate, but they also contribute to the development of the whole discipline. In 1994, Grady Booch, Jim Rumbaugh, and Ivar Jacobson joined together to unify the plethora of existing object-oriented systems engineering approaches at semantic and notation level (Booch, 2002; Fowler, 2004; Rumbaugh, Jacobson, & Booch, 1998). Their effort led to the Unified Modeling Language (UML), a well-known, general-purpose, tool-supported, process-independent, and industry-standardized modeling language for visualizing, describing, specifying, and documenting systems artifacts. Table 1 depicts the origin and descent of UML.

Model Driven Architecture (MDA)

2010 ◽  
pp. 15-33 ◽  
Author(s):  
Liliana María Favre
Keyword(s):  
Unified Modeling Language ◽  
Enterprise Application Integration ◽  
System Specification ◽  
Model Driven Architecture ◽  
Unified Modeling ◽  
Model Driven ◽  
Software Applications ◽  
Enterprise Application ◽  
Architectural Framework ◽  
Requirement Specifications

The architecture of a system is a specification of software components, interrelationships, and rules for component interactions and evolution over time. In 2001 OMG, adopted an architecture standard, the Model Driven Architecture (MDA). MDA is an architectural framework for improving portability, interoperability and reusability through separation of concerns (MDA, 2003) (MDA, 2005). It is not itself a technology specification but it represents an evolving plan to achieve cohesive model-driven technology specifications. MDA is built on OMG standards including the Unified Modeling Language (UML), the XML Metadata Interchange (XMI) (XMI, 2007) and CORBA (CORBA, 1992) (CORBA, 2002) a major middleware standard. MDA is model-driven because it uses models to direct the complete lifecycle of a system. All artifacts such as requirement specifications, architecture descriptions, design descriptions and code, are regarded as models. MDA provides an approach for specifying a system independently of the platforms that it supports, specifying platforms, selecting a particular platform for the system, and transforming the system specification into one implementation for the selected particular platform. Why MDA? OMG has focused on the creation of open specifications to encourage application interoperability. It was defined to solve enterprise application integration. A middleware describes a piece of software that connects two or more software applications, allowing them to exchange data. To achieve this, it must be implemented for all different languages and platforms that need linking.

Integrating Access Control into UML for Secure Software Modeling and Analysis

2012 ◽  
pp. 69-88
Author(s):  
Thuong Doan ◽  
Steven Demurjian ◽  
Laurent Michel ◽  
Solomon Berhe
Keyword(s):  
Access Control ◽  
Unified Modeling Language ◽  
Role Based Access Control ◽  
Software Modeling ◽  
Sequence Diagrams ◽  
Modeling And Analysis ◽  
Unified Modeling ◽  
Software Applications ◽  
Secure Software ◽  
Role Based

Access control models are often an orthogonal activity when designing, implementing, and deploying software applications. Role-based access control (RBAC) which targets privileges based on responsibilities within an application and mandatory access control (MAC) that emphasizes the protection of information via security tags are two dominant approaches in this regard. The integration of access control into software modeling and analysis is often loose and significantly lacking, particularly when security is such a high-priority concern in applications. This paper presents an approach to integrate RBAC and MAC into use-case, class, and sequence diagrams of the unified modeling language (UML), providing a cohesive approach to secure software modeling that elevates security to a first-class citizen in the process. To insure that a UML design with security does not violate RBAC or MAC requirements, design-time analysis checks security constraints whenever a new UML element is added or an existing UML element is modified, while post-design analysis checks security constraints across the entire design for conflicts and inconsistencies. These access control extensions and security analyses have been prototyped within a UML tool.

Ontology Based Behavior Verification for Complex Systems

2018 ◽  
Author(s):  
Ruirui Chen ◽  
Yusheng Liu ◽  
Xiaoping Ye
Keyword(s):  
Complex Systems ◽  
Systems Engineering ◽  
Past Research ◽  
Design Stage ◽  
Early Design ◽  
Early Design Stage ◽  
Unified Modeling ◽  
Ontology Generation ◽  
Model Based Systems Engineering

Model Based Systems Engineering (MBSE) is a mainstream methodology for the design of complex systems. Verification is a necessary part of MBSE. Although there is significant past research on verification, some deficiencies still exist, such as behavior requirement verification in the early design stage is lacking. In this study, behavior verification at the early design stage is presented. First, a unified modeling method based on SysML is proposed and some transformation rules are defined to ensure the correctness and definiteness of the ontology generation. Second, behavior requirements are classified and formalized as rules. Finally, a hierarchical behavior verification approach based on ontology reasoning is proposed. This approach is convenient for designers to use and no additional expertise is needed. A case study is provided to demonstrate its effectiveness.

Unified Modeling Language 2.0

2011 ◽  
pp. 3871-3879
Author(s):  
Peter Fettke
Keyword(s):  
Systems Engineering ◽  
Subject Matter ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
General Purpose ◽  
Modeling Language ◽  
Unified Modeling ◽  
Object Oriented Systems

Mature engineering disciplines are generally characterized by accepted methodical standards for describing all relevant artifacts of their subject matter. Such standards not only enable practitioners to collaborate, but they also contribute to the development of the whole discipline. In 1994, Grady Booch, Jim Rumbaugh, and Ivar Jacobson joined together to unify the plethora of existing object-oriented systems engineering approaches at semantic and notation level (Booch, 2002; Fowler, 2004; Rumbaugh, Jacobson & Booch, 1998). Their effort leads to the unified modeling language (UML), a well-known, general-purpose, tool-supported, processindependent, and industry-standardized modeling language for visualizing, describing, specifying, and documenting systems artifacts.

Sign in / Sign up

Export Citation Format

Share Document