Relating domain model based requirements management and situational method engineering

In this paper we revisit our earlier proposed domain model based approach to requirements management from a situational method engineering perspective. The approach has originally been developed dedicatedly for a small- and medium-sized enterprise (SME) in the field of control system development. Broadening the perspective by considering situational method engineering helps to generalize the approach to support any kind of flexible and customer-oriented enterprise that works in highly innovative fields. The investigation has opened up our method for new strategies to make domain model choices and to tailor the requirements-based search for similar projects. Furthermore, the feedback loop that we provide to adapt domain models according to the concrete experiences of an SME within recent projects raises an issue that possibly applies to knowledge management in situational method engineering in general.

[1]  Eric Yu,et al.  Modeling Strategic Relationships for Process Reengineering , 1995, Social Modeling for Requirements Engineering.

[2]  Jan Bosch,et al.  Evolution in software product lines: Two cases , 1999 .

[3]  Matthias Jarke,et al.  Mapping Requirement Models to Mathematical Models in Control System Development , 2009, ECMDA-FA.

[4]  Rick Rabiser,et al.  Tool Support for Evolution of Product Lines through Rapid Feedback from Application Engineering , 2010, VaMoS.

[5]  Matthias Jarke,et al.  Requirements Engineering for Control Systems Development in Small and Medium-Sized Enterprises , 2008, 2008 16th IEEE International Requirements Engineering Conference.

[6]  Colette Rolland,et al.  Towards a Generic Model for Situational Method Engineering , 2003, CAiSE.

[7]  John A. McDermid,et al.  Ten steps towards systematic requirements reuse , 2008, Requirements Engineering.

[8]  Matthias Jarke,et al.  Evolution in Domain Model-Based Requirements Engineering for Control Systems Development , 2009, 2009 17th IEEE International Requirements Engineering Conference.

[9]  Kuldeep Kumar,et al.  Methodology Engineering R : a proposal for situation-specific methodology construction , 1992 .

[10]  Matthias Jarke,et al.  Goal-Based Domain Modeling as a Basis for Cross-Disciplinary Systems Engineering , 2010, Intentional Perspectives on Information Systems Engineering.

[11]  Colette Rolland,et al.  A Multi-Model View of Process Modelling , 1999, Requirements Engineering.

[12]  Klaus Pohl,et al.  Software Product Line Engineering - Foundations, Principles, and Techniques , 2005 .

[13]  Matthias Jarke,et al.  How to Keep Domain Requirements Models Reasonably Sized , 2009, 2009 Second International Workshop on Managing Requirements Knowledge.

[14]  Eric S. K. Yu,et al.  A Repository of Agile Method Fragments , 2010, ICSP.

[15]  Nan Niu,et al.  Extracting and Modeling Product Line Functional Requirements , 2008, 2008 16th IEEE International Requirements Engineering Conference.

[16]  Jan Bosch,et al.  Evolution in software product lines: two cases , 1999, J. Softw. Maintenance Res. Pract..

[17]  张友安,et al.  使用MATLAB WITH SIMULINK仿真语言的几点体会 , 1998 .

[18]  Matthias Jarke,et al.  Telos: Representing Knowledge about Control Systems? , 2008, 2008 First International Workshop on Managing Requirements Knowledge.

[19]  A. F. Harmsen,et al.  Situational Method Engineering , 1997 .

[20]  Klaus Schmid,et al.  Applying Product Line Concepts in Small and Medium-Sized Companies , 2000, IEEE Software.

[21]  Neil A. M. Maiden,et al.  Use of Domain Knowledge for Requirements Validation , 1993, Information System Development Process.