Model-Based System Design Using SysML

Author(s):  
Anargyros Tsadimas ◽  
Mara Nikolaidou ◽  
Dimosthenis Anagnostopoulos

Model-based system design is served by a single, multi-layered model supporting all design activities, in different levels of detail. SysML is a modeling language, endorsed by OMG, for system engineering, which aims at defining such models for system design. It provides discrete diagrams to describe system structure and components, to explore allocation policies crucial for system design, and to identify design requirements. In this chapter, SysML is used for the model-based design of enterprise information system architecture, supporting a systemic view of such systems, where software and hardware entities are treated as system components composed to create the system architecture. SysML extensions to facilitate the effective description of non-functional requirements, especially quantitative ones, and their verification are presented. The integration of evaluation parameters and results into a discrete SysML diagram enhances the requirement verification process, while the visualization of evaluation data helps system engineers to explore design decisions and properly adjust system design. Based on the proposed extensions, a SysML profile is developed. The experience obtained when applying the profile for renovating the architecture of a large-scale enterprise information system is also briefly discussed to explore the potential of the proposed extensions.

2016 ◽  
pp. 278-301
Author(s):  
Anargyros Tsadimas ◽  
Mara Nikolaidou ◽  
Dimosthenis Anagnostopoulos

Model-based system design is served by a single, multi-layered model supporting all design activities, in different levels of detail. SysML is a modeling language, endorsed by OMG, for system engineering, which aims at defining such models for system design. It provides discrete diagrams to describe system structure and components, to explore allocation policies crucial for system design, and to identify design requirements. In this chapter, SysML is used for the model-based design of enterprise information system architecture, supporting a systemic view of such systems, where software and hardware entities are treated as system components composed to create the system architecture. SysML extensions to facilitate the effective description of non-functional requirements, especially quantitative ones, and their verification are presented. The integration of evaluation parameters and results into a discrete SysML diagram enhances the requirement verification process, while the visualization of evaluation data helps system engineers to explore design decisions and properly adjust system design. Based on the proposed extensions, a SysML profile is developed. The experience obtained when applying the profile for renovating the architecture of a large-scale enterprise information system is also briefly discussed to explore the potential of the proposed extensions.


2018 ◽  
Author(s):  
Ανάργυρος Τσαδήμας

Η σχεδίαση της αρχιτεκτονικής των συστημάτων είναι μια πολύπλοκη διαδικασία, στην οποία υπάρχουν πολλοί εμπλεκόμενοι και διάφορετικά θέματα ενδιαφέροντος. Όταν σχεδιάζουμε Εταιρικά Πληροφοριακά Συστήματα (ΕΠΣ) θα πρέπει να σχεδιάζουμε παράλληλα την αρχιτεκτονική του λογισμικού και του δικτύου, μιας και σχετίζονται άμεσα μεταξύ τους, με σκοπό να διασφαλιστεί η αποτελεσματικότητα του συστήματος.Η SysML, η οποία έχει προταθεί από την INCOSE και το OMG, είναι μια ευρέως αποδεκτή γλώσσα μοντελοποίησης η οποία υποστηρίζει πλήρως τη μοντελοεντρική σχεδίαση συστημάτων. Η INCOSE είναι ένας μη-κερδοσκοπικός οργανισμός ο οποίος υποστηρίζει τη διασύνδεση και τη διαλειτουργικότητα μεθόδων και εργαλείων, όσον αφορά τη σχεδίαση συστημάτων.Η διαχείριση των απαιτήσεων κατά τη σύνθεση συστημάτων αποτελούμενα από υποσυστήματα SoS, είναι επίσης μια πολύπλοκη διαδικασία. Οι απαιτήσεις συγκεντρώνονται και αναπροσαρμόζονται κατά τη διάρκεια όλων των φάσεων της εξέλιξης του συστήματος κι αυτό κάνει ακόμη πιο δύσκολη τη διαδικασία της διαχείρισής τους. Για το λόγο αυτό απαιτείται μια συστηματική μελέτη και ταξινόμηση των απαιτήσεων, ώστε να είναι εφικτή η αξιοποίησή τους κατά τη διαδικασία της αποτίμησης. Ως εκ τούτου, κατα τη σχεδίαση της αρχιτεκτονικής του συστήματος πρέπει να δωθεί έμφαση στις Μη-Λειτουργικές απαιτήσεις(ΜΛΑ), όπως για παράδειγμα αυτές που σχετίζονται με την απόδοση, μιας και αυτές παίζουν καθοριστικό ρόλο στην αποτελεσματικότητα του συστήματος.Ο σκοπός της παρούσας έρευνας είναι η παροχή μιας μοντελο-κεντρικής προσέγγισης για τη σχεδίαση της αρχιτεκτονικής των ΕΠΣ αξιοποιώντας σαν γλώσσα μοντελοποίησης τη SysML. Για το σκοπό αυτό, ο σχεδιαστής του συστήματος εφοδιάζεται με εναλλακτικές όψεις του συστήματος, οι οποίες εστιάζουν στην αρχιτεκτονική του λογισμικού και του υλικού και διευκολύνουν την επαλήθευση των ΜΛΑ. Αυτό επιτυγχάνεται με τον ορισμό ενός προφιλ ΕΠΣ στη SysML.Παρόλο που η SysML υποστηρίζει την έννοια των απαιτήσεων, στα σχετικά σχεδιαστικά εργαλεία λείπει ένας αυτοματοποιημένος μηχανισμός επαλήθευσης των απαιτήσεων. Η διατριβή παρουσιάζει ένα ολοκληρωμένο σχεδιαστικό περιβάλλον, στο οποίο όχι μόνο είναι δυνατόν να οριστούν εναλλακτικές αρχιτεκτονικές του συστήματος , αλλά επίσης μπορούν να αποτιμηθούν χρησιμοποιώντας προσομοίωση. Τα αποτελέσματα της προσομοίωσης ενσωματώνονται στο μοντέλο του συστήματος και με αυτόν τον τρόπο γίνεται εφικτή η διαδικασία της αυτοματοποιημένης επαλήθευσης των ΜΛΑ.Εν τέλει, η προτεινόμενη προσέγγιση εφαρμόστηκε επιτυχώς σε και σε άλλα πεδία όπως οι μεταφορές και η ανάλυση κόστους στο cloud.


Author(s):  
Mara Nikolaidou ◽  
Nancy Alexopoulou

System design is an important phase of system engineering, determining system architecture to satisfy specific requirements. System design focuses on analyzing performance requirements, system modeling and prototyping, defining and optimizing system architecture, and studying system design tradeoffs and risks. Modern enterprise information systems (EIS) are distributed systems usually built on multitiered client server architectures, which can be modeled using well-known frameworks, such as Zachman enterprise architecture or open distributed processing reference model (RM-ODP). Both frameworks identify different system models, named views, corresponding to discrete stakeholder’s perspectives, specific viewpoints, and could serve as a basis for model-based system design. The main focus of this chapter is to explore the potential of model-based design for enterprise information systems (EIS). To this end, the basic requirements for model-based EIS design are identified, while three alternative approaches are discussed based on the above requirements, namely, rational unified process for systems engineering (RUP SE), UML4ODP and EIS design framework.


2021 ◽  
Vol 10 (1) ◽  
pp. 141-149
Author(s):  
Mangapul Siahaan

PT.XYZ is a gas oil manufacturing company, which produces offshore oil and gas drilling equipment. In supporting its business processes, this company uses a separate module application which causes data flow to be interrupted and results in the company experiencing delays in managing data and getting information on time. Based on the analysis of the problem, the researcher will design an integrated enterprise information system architecture for sales, finance, raw material procurement, production, project plan, and inventory. The method used is the TOGAF ADM 9.2 framework which consists of four phases, namely the vision architecture, business architecture, information system architecture, and technology architecture phases. This enterprise architecture design produces a blueprint as a guideline or framework in the development of information systems at PT. XYZ. The overall result of this research is to produce an enterprise architecture information system design


Author(s):  
Malihe Tabatabaie ◽  
Richard Paige ◽  
Chris Kimble

The concept of an Enterprise Information System (EIS) has arisen from the need to deal with the increasingly volatile requirements of modern large-scale organisations. An EIS is a platform capable of supporting and integrating a wide range of activities across an organisation. In principle, the concept is useful and applicable to any large and SMEs, international or national business organisation. However, the range of applications for EIS is growing and they are now being used to support e-government, health care, and non-profit / non-governmental organisations. This chapter reviews research and development efforts related to EIS, and as a result attempts to precisely define the boundaries for the concept of EIS, i.e., identifying what is and what is not an EIS. Based on this domain analysis, a proposal for using goal-oriented modelling techniques for building EIS is constructed; the proposal is made more concrete through illustration via an example.


Author(s):  
Malihe Tabatabaie ◽  
Richard Paige ◽  
Chris Kimble

The concept of an Enterprise Information System (EIS) has arisen from the need to deal with the increasingly volatile requirements of modern large-scale organisations. An EIS is a platform capable of supporting and integrating a wide range of activities across an organisation. In principle, the concept is useful and applicable to any large and SMEs, international or national business organisation. However, the range of applications for EIS is growing and they are now being used to support e-government, health care, and non-profit / non-governmental organisations. This chapter reviews research and development efforts related to EIS, and as a result attempts to precisely define the boundaries for the concept of EIS, i.e., identifying what is and what is not an EIS. Based on this domain analysis, a proposal for using goal-oriented modelling techniques for building EIS is constructed; the proposal is made more concrete through illustration via an example.


Sign in / Sign up

Export Citation Format

Share Document