Year-end Sale % OFF 
Abstract
Software Configuration Management (SCM) aims to control the development of complex software systems. Traditional SCM systems treat text files as central artifacts, so they are mainly developed for source code. Such a system is not suitable for model-based software development with model-centric artifacts. When applying traditional systems to model-based software development, new challenges such as model mapping, differentiation, and merging arise. Many existing methods mainly use UML or domain-specific languages to determine model differences. However, as far as we know, there is no such technology for System Modeling Language (SysML) models. SysML covers the entire development life cycle of various complex systems, covering information, processes, hardware and software. SysML contains nine types of diagrams for system modeling. One of them is the SysML requirement diagram, which is used to capture the functional requirements of the system. We propose a differentiation method for the SysML demand model. We recommend to create a SysML requirement model in the CASE tool first, and then export the SysML model in the form of XMI. Then, we parse the XMI representation through difference calculations. Finally, we summarize the results in annotated form. We implemented our method in a satellite system case study and demonstrated the experimental use of the method.
Highlights
The development of complex software system development requires coordination between different team members working in actual projects [1]
Software development is a model-centric process in which Model Driven Engineering (MDE) applies Unified Modeling Language (UML) models for analysis and design purposes
Since the models are conceptual diagrams, they cannot be treated as text files
Summary
The development of complex software system development requires coordination between different team members working in actual projects [1]. Many existing methods mainly use Unified Modeling Language (UML) or domain-specific languages (UML) to determine model differences [8–10] In this regard, Model Driven Engineering (MDE) aims to reduce the complexity of software development by treating models as central artifacts [11–13]. Model Driven Engineering (MDE) aims to reduce the complexity of software development by treating models as central artifacts [11–13] This type of model must be designed, analyzed, and maintained according to the version control mechanism, and the quality of the model must be ensured. In MDE software, documents are both text files and models, just like different types of diagrams in UML These diagrams are usually stored in XML Metadata Interchange (XMI) format to facilitate interpretation and manipulation of system models.
Sign-in/Register to view highlights & summary 
Published Version (
Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
