A Meta-Model to Automatically Generate Evolutionary Prototypes from Software Requirements

2016 ◽

Vol 26 (01) ◽

pp. 87-113 ◽

Cited By ~ 3

Author(s):

Hyun-Seok Min

Keyword(s):

South Korea ◽

Software Architecture ◽

Software Requirements ◽

Software Developers ◽

Process Step ◽

Meta Model ◽

Traceability Link ◽

Software Requirement ◽

Practical Guideline ◽

Uml Diagrams

Traceability between software requirements and UML design helps requirement engineers and software developers understand the project goal and software architecture. However, the traceability mapping between the two elements is not well-defined and as a result there is no consistent way to make the traceability between two. A practical guideline is proposed for the traceability between software requirement and UML design. The guideline includes meta-model and process step. The process step defines detailed processes and most importantly, the Requirement-type and its mapping to UML diagrams. Requirements can be categorized based on their aspects and this categorization can be made as Requirement-type. This pre-defined Requirement-type is added to each requirement and this Requirement-type enforces to use certain types of UML diagrams as solutions. This mapping between each Requirement-type and UML diagram is the key of proposed guideline. With the help of the Requirement-type and mapping, traceability link can be made easily and checked automatically. The guideline was applied to the Missile Project and Helicopter Project of ADD (Agency of Defense Development) in South Korea.

Download Full-text

An Approach for Evolution-Driven Method Engineering

Information Modeling Methods and Methodologies ◽

10.4018/978-1-59140-375-3.ch005 ◽

2011 ◽

pp. 80-101 ◽

Cited By ~ 5

Author(s):

Jolita Ralyte ◽

Colette Rolland ◽

Mohamed Ben Ayed

Keyword(s):

Software Requirements ◽

Specific Method ◽

User Requirements ◽

Method Engineering ◽

Evolutionary Perspective ◽

Research Project ◽

New Model ◽

Meta Model ◽

Method Model ◽

Method Construction

This chapter considers the evolutionary perspective of method engineering. It presents an approach for method engineering supporting evolution of an existing method, model, or meta-model into a new one satisfying a different engineering objective. The authors hope that this approach could be helpful for a project-specific method construction. This approach proposes several different strategies to evolve from the initial paradigm model to a new one and provides guidelines supporting these strategies. The approach has been evaluated in the Franco-Japanese research project around the Lyee methodology. A new model called Lyee User Requirements Model has been obtained as an abstraction of the Lyee Software Requirements Model. The chapter illustrates this evolution case.

Download Full-text

An approach to project planning employing software and systems engineering meta-model represented by an ontology

Computer Science and Information Systems ◽

10.2298/csis091110030l ◽

2010 ◽

Vol 7 (4) ◽

pp. 721-736 ◽

Cited By ~ 9

Author(s):

Miroslav Líska ◽

Pavol Návrat

Keyword(s):

Semantic Web ◽

Systems Engineering ◽

Knowledge Engineering ◽

Mutual Influence ◽

System Development ◽

Project Planning ◽

Software Requirements ◽

Model Driven Architecture ◽

Meta Model ◽

Model Driven

Currently, one can witness a growing mutual influence between the Model Driven Architecture (MDA) and the Semantic Web. MDA is an approach that uses models for system development, but its architecture limits usability of these models for knowledge empowered solutions. A lot of research tackles applicability of MDA standards in the technical space of the Semantic Web. In this paper, we present an approach aimed at facilitating the use of Software and Systems Engineering Meta-Model (SPEM) for improvements that are rooted in knowledge engineering approaches. We show how SPEM can be used in the Semantic Web technical space. We describe how following our approach a project plan can be generated and verified. Finally, we present an example of project planning that uses ontology of a software requirements activity.

Download Full-text