Model-based requirements specification of real-time systems with UML, SysML and MARTE.
Saved in:
| Title: | Model-based requirements specification of real-time systems with UML, SysML and MARTE. |
|---|---|
| Authors: | Ribeiro, Fabíola Gonçalves C.1,2 fabiola.ribeiro@ifgoiano.edu.br, Pereira, Carlos E.2,3 cpereira@ece.ufrgs.br, Rettberg, Achim2,4 achim.rettberg@iess.org, Soares, Michel S.2,5 mics.soares@gmail.com |
| Source: | Software & Systems Modeling. Feb2018, Vol. 17 Issue 1, p343-361. 19p. |
| Subjects: | Real-time control, SysML (Computer science), Temporal databases, Software engineering, Database management |
| Abstract: | Activities of specification, analysis and design of real-time systems (RTS) are highly dependent on an effective understanding of the application domain and on the thorough representation of their basic requirements. Model-based approaches using modeling languages such as UML are often applied to contribute to handle complexity of RTS development. However, UML alone does not completely represent important features associated with these systems, such as relationship with hardware elements and an effective representation of timing constraints. This article explores the combined use of UML and its profiles SysML and MARTE for modeling hardware and software requirements of RTS, with application to a case of controlling urban road traffic. The SysML profile alone does not present the representation of temporal, behavioral and performance requirements. The MARTE profile provides key resources to specify non-functional requirements for RTS, in addition to a clear description of the various relevant aspects of requirements definition of RTS, as for instance, temporal aspects and constraints. The main objective is to present the combined application of SysML with MARTE stereotypes, which enables the specification of different features of individual software requirements. Thus, in addition to the factors mentioned above, we can say that the proposed approach has an important role to specify RTS at different levels of detail and levels of abstraction. [ABSTRACT FROM AUTHOR] |
| Copyright of Software & Systems Modeling is the property of Springer Nature and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.) | |
| Database: | Engineering Source |
|
Full text is not displayed to guests.
Login for full access.
|
|
| Abstract: | Activities of specification, analysis and design of real-time systems (RTS) are highly dependent on an effective understanding of the application domain and on the thorough representation of their basic requirements. Model-based approaches using modeling languages such as UML are often applied to contribute to handle complexity of RTS development. However, UML alone does not completely represent important features associated with these systems, such as relationship with hardware elements and an effective representation of timing constraints. This article explores the combined use of UML and its profiles SysML and MARTE for modeling hardware and software requirements of RTS, with application to a case of controlling urban road traffic. The SysML profile alone does not present the representation of temporal, behavioral and performance requirements. The MARTE profile provides key resources to specify non-functional requirements for RTS, in addition to a clear description of the various relevant aspects of requirements definition of RTS, as for instance, temporal aspects and constraints. The main objective is to present the combined application of SysML with MARTE stereotypes, which enables the specification of different features of individual software requirements. Thus, in addition to the factors mentioned above, we can say that the proposed approach has an important role to specify RTS at different levels of detail and levels of abstraction. [ABSTRACT FROM AUTHOR] |
|---|---|
| ISSN: | 16191366 |
| DOI: | 10.1007/s10270-016-0525-1 |
