The focus is on software and embedded system domains. This paper presents a comprehensive meta-model for requirements management. Meta-Object Facility (MOF) is a standard language for creating meta-models. Meta-model captures abstractions and relationships of the target domain concepts. Meta-model (i.e., domain model) is a structure of concepts in a certain domain. One of such expansion methods is to use UML profiles that add new domain-specific model elements to the UML language with stereotypes, tag definitions, and constraints. UML2 offers a rich set of diagrams for software architecture modeling but also expansion and tailoring methods for other domains. Unified Modeling Language version 2 (UML2) is a standard language for modeling systems. As these errors are related to requirements capture, they happen early in the development process, and thus, they are likely to incur high in cost in later development phases. Using such tools with no clearly defined templates can lead to errors in communicating requirements between different stakeholders. The most common tools currently used for requirements management in industry are word-processing packages, spreadsheet applications, and internal web pages. However, surveys have indicated problems in requirements management processes used by practitioners related to tool integration, incorrect tool usage, and lack of traceability of requirements to development artifacts. Several solutions and tools for requirements management process have been provided for software development. Requirements Management is a crucial part of systems development. The profile is adopted to create an example model of embedded system requirement specification which is built with the profile. The developed profile is associated with a proof of concept report generator tool that automatically produces up-to-date documentation from the models in form of web pages. The profile is imported into a UML tool which is used for rapid evaluation of meta-model concepts in practice. The created meta-model is prototyped by translating it into a UML profile. ![]() This leads to a portable requirements management meta-model which can be adapted with various system modeling languages. The goal is to define generic requirements management domain concepts and abstract interfaces between requirements management and system development. ![]() This is due to utilized tools with no clear meta-model and semantics to communicate requirements between different stakeholders. Software and embedded system companies today encounter problems related to requirements management tool integration, incorrect tool usage, and lack of traceability.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |