Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Writing Effective Use Cases
Model-Based Development of Embedded Systems
OOIS '02 Proceedings of the Workshops on Advances in Object-Oriented Information Systems
Method construction - a core approach to organizational engineering
Proceedings of the 2005 ACM symposium on Applied computing
Requirements Abstraction Model
Requirements Engineering
EMF: Eclipse Modeling Framework 2.0
EMF: Eclipse Modeling Framework 2.0
Requirements engineering: from craft to discipline
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Eclipse Modeling Project: A Domain-Specific Language (DSL) Toolkit
Eclipse Modeling Project: A Domain-Specific Language (DSL) Toolkit
Integrated software process and product lines
SPW'05 Proceedings of the 2005 international conference on Unifying the Software Process Spectrum
Field study on requirements engineering artefacts and patterns
EASE'10 Proceedings of the 14th international conference on Evaluation and Assessment in Software Engineering
Information and Software Technology
A mapping study on method engineering: first results
Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering
Information and Software Technology
| Hi-index | 0.00 |
Requirements Engineering (RE) processes are highly volatile due to dependencies on customers' capabilities or used process models, both complicating a standardised RE process. A promising solution is given by artefactorientation that emphasises the results rather than dictating a strict development process. At such a basis one is able to incorporate domain-specific methods for producing artefacts without having to take into account the variability of process definitions. Although artefacts are known to support customisable development processes, there still is no common agreement about the structure and semantics of artefact-based methodologies. In this paper we discuss different interpretations of the term artefact considering aspects like process integration capabilities and necessities within individual project environments. We contribute a meta model for artefact-orientation that is inferred from two RE models elaborated within industrial cooperation projects of our research group. We conclude with a discussion of performed case studies and ongoing work.