Situational requirements engineering processes: Reflecting on method engineering and requirements practice

Software Process Improvement and Practice

Volumn 11, Issue 5, 2006, Pages 447-450

  Ågerfalk, Pär J ^a,b   Ralyté, Jolita ^c  

^a UNIVERSITY OF LIMERICK   (Ireland)

^b ÖREBRO UNIVERSITY   (Sweden)

^c UNIVERSITY OF GENEVA   (Switzerland)

Author keywords

Method engineering; Requirements engineering; Software process improvement

Indexed keywords

COMPUTER SOFTWARE; CONSTRAINT THEORY; ENGINEERING RESEARCH; PROJECT MANAGEMENT; SOFTWARE ENGINEERING;

INFORMATION SYSTEMS; METHOD ENGINEERING; SOFTWARE PROCESS IMPROVEMENT;

REQUIREMENTS ENGINEERING;

EID: 33750309448     PISSN: 10774866     EISSN: 10991670     Source Type: Journal    
DOI: 10.1002/spip.289     Document Type: Review

References (23)

1. Ågerfalk PJ, Fitzgerald B. 2006. Exploring the concept of method rationale: A conceptual tool for method tailoring. In Advanced Topics in Database Research, Vol. 5., Siau K (ed.)- Idea Group: Hershey, PA.
2. Basili VR, Rombach HD. 1987. Tailoring the software process to project goals and environments. In Proceedings of the 9th International Conference on Software Engineering. IEEE Computer Society Press: Los Alamitos, CA, 345-357.
3. Brinkkemper S. 1996. Method engineering: engineering of information systems development methods and tools. Information and Software Technology 38(4): 275-280, DOI:10.1016/0950-5849(95)01059-9.
4. Brinkkemper S, Saeki M, Harmsen F. 1999. Metamodelling based assembly techniques for situational method engineering. Information Systems 24(3): 209-228, DOI: 10.1016/50306-4379(99)00016-2.
5. Cattaneo F, Fuggetta A, Sciuto D. 2001. Pursuing coherence in software process assessment and improvement. Software Process: Improvement and Practice 6(1): 3-22, DOI: 10.1002/spip.131.
6. Davis GB. 1982. Strategies for information requirements determination. IBM Systems Journal 21(1): 4-30.
7. Dömges R, Pohl K. 1998. Adapting traceability environments to project-specific needs. Communications of the ACM 41(12): 54-62, DOI: 10.1145/290133.290149.
8. Firesmith D. 2002. Requirements Engineering. Journal of Object Technology 1(4): 93-103.
9. Fitzgerald B, Russo NL, O'Kane T. 2003. Software development method tailoring at Motorola. Communications of the ACM 46(4): 65-70, DOI: 10.1145/641205.641206.
10. Gupta D, Prakash N. 2001. Engineering methods from method requirements specifications. Requirements Engineering 6(3): 135-160, DOI: 10.1007/s007660170001.
11. Henderson-Sellers B, Serour MK. 2005. Creating a dual-agility method: The value of method engineering. Journal of Database Management 16(3): 1-23.
12. Karlsson F, Ågerfalk PJ. 2004. Method configuration: Adapting to situational characteristics while creating reusable assets. Information and Software Technology 46(9): 619-633, DOI:10.1016/j.infsof.2003.12.004.
13. Karlsson F, Wistrand K. 2006. Combining method engineering with activity theory: Theoretical grounding of the method component concept. European journal of Information Systems 15(1): 82-90, DOI: 10.1057/palgrave.ejis.3000596.
14. Kumar K, Wellke RJ. 1992. Methodology engineering: A proposal for situation specific methodology construction. In Challenges and Strategies for Research in Systems Development, Cotterman WW, Senn JA, (eds). John Wiley and Sons: Washington, DC, 257-269.
15. Lundell B, Lings B. 2004. Method in action and method in tool: A stakeholder perspective. Journal of Information Technology 19(3): 215-223, DOI: 10.1057/palgrave.jit.2000022.
16. Lyytinen K, Welke R. 1999. Guest editorial: Special issue on meta-modelling and methodology engineering. Information Systems 24(2): 67-69, DOI: 10.1016/S03064379(99)00005-8.
17. Mirbel I, Ralyté J. 2006. Situational method engineering: Combining assembly-based and roadmap-driven approaches. Requirements Engineering 11(1): 58-78, DOI: 10.1007/S00766-005-0019-0.
18. Nuseibeh B, Easterbrook S. 2000. Requirements engineering: A roadmap. In Proceedings of the International Conference on Software Engineering 2000. ACM Press: Limerick, Ireland, New York, 35-46, DOI: 10.1145/336512.336523.
19. Ralyté J, Deneckère R, Rolland C. 2003. Towards a generic model for situational method engineering. In Proceedings of 15th International Conference on Advanced Information Systems Engineering (CAiSE 2003), Klagenfurt, Austria, June 16-18, 2003, Eder J, Missikoff M, (eds). Springer-Verlag: Heidelberg, Germany, 95-110.
20. Rolland C, Prakash N, Benjamen A. 1999. A multi-model view of process modelling. Requirements Engineering 4(4): 169-187, DOI: 10.1007/s007660050018.
21. Rossi M, Ramesh B, Lyytinen K, Tolvanen J-P. 2004. Managing evolutionary method engineering by method rationale. Journal of the Association for Information Systems 5(9): 356-391.
22. Sawyer P, Sommerville I, Viller S. 1997. Requirements process improvement through the phased introduction of good practice. Software Process: Improvement and Practice 3(1): 19-34, DOI: 10.1002/(SICI)1099-1670(199703)3:1 〈19::AID-SPIP66〉 3.0.CO;2-X.
23. Serour MK, Henderson-Sellers B. 2004. Introducing agility: A case study of situational method engineering using the open process framework, 28th Annual International Computer Software and Applications Conference (COMPSAC'04). IEEE Computer Society: Los Alamitos, CA, DOI: 10.1109/CMPSAC.2004.1342805.