CORAMOD: A checklist-oriented model-based requirements analysis approach

Requirements Engineering

Volumn 19, Issue 1, 2014, Pages 1-26

  Brace, William ^a   Ekman, Kalevi ^a  

^a AALTO UNIVERSITY   (Finland)

Author keywords

CORAMOD; Formalize requirement; Model based; Model based requirements analysis; Requirement models; Requirements analysis

Indexed keywords

PRODUCT DEVELOPMENT; SOFTWARE ENGINEERING;

CORAMOD; FORMALIZE REQUIREMENT; MODEL-BASED; MODEL-BASED REQUIREMENTS; REQUIREMENT MODELS; REQUIREMENTS ANALYSIS;

REQUIREMENTS ENGINEERING;

EID: 84897579755     PISSN: 09473602     EISSN: 1432010X     Source Type: Journal    
DOI: 10.1007/s00766-012-0154-3     Document Type: Article

References (51)

1. Hall T, Beechem S, Rainer A (2002) Requirements problems in twelve software companies: an empirical analysis. IEE Proc Softw 149: 153-160. doi: 10. 1049/ip-sen: 20020694.
2. Kauppinen M, Savolainen J, Lehtola L, Komssi M, Töhönen H, Davis A (2009) From feature development to customer value creation. In: Proceedings of 17th IEEE international requirements engineering conference (RE'09), pp 275-280.
3. Darlington MJ, Culley SJ (2004) A model of factors influencing the design requirement. Des Stud 25(4): 329-350. doi: 10. 1016/j. destud. 2003. 12. 003.
4. Pahl G, Beitz W (2007) Engineering design: a systematic approach. In: Wallace K, Blessing L (eds, trans) 3rd edn. Springer, Berlin.
5. Blanchard B, Fabrycky W (2006) Systems engineering and analysis. In: Fabrycky W, Mize J (eds) Prentice Hall international series in industrial and systems engineering, 4th edn. Pearson, Prentice Hall, Englewood Cliffs.
6. Ulrich KT, Eppinger SD (2001) Product design and development, 2nd edn. McGraw-Hill International, New York.
7. Piaszczyk C (2011) Model based systems engineering with Department of Defense Architectural Framework. J Syst Eng Manage 14(3): 305-326. doi: 10. 1002/sys. 20180.
8. Pugh S (1997) Total design: integrated methods for successful product engineering. Addison-Wesley Longman Ltd, Essex, UK.
9. Dieter G (2000) Engineering design: a material and processing approach, 3rd edn. McGraw- Hill, International Editions, New York.
10. Grady JO (2006) System requirements analysis. Elsevier Academic Press, Burlington.
11. Otto K, Wood K (2001) Product design -techniques in reverse engineering and new product development. Prentice Hall, Upper Saddle River.
12. Cross N (2008) Engineering design methods, strategies for product design, 4th edn. Wiley, West Sussex.
13. Darlington MJ, Culley SJ (2002) Current research in the engineering design requirement. IMechE, Part B: J Eng Manuf 216(3): 375-388. doi: 10. 1243/0954405021520049.
14. Ullman D (1992) The mechanical design process. McGraw-Hill, Inc., New York.
15. Hoffmann HP (2005) UML 2. 0-based systems engineering using a model-driven development. J Def Softw Eng(CROSSTALK).
16. McKay A, Pennington A, Baxter J (2001) Requirements management: a representation scheme for product specifications. Comput Aided Des 33(7): 511-520.
17. Daniela E, Damian H, Jonker CM, Treur J, Wijngaards NJ (2005) Integration of behavioural requirements specification within compositional knowledge engineering. Knowl-Based Syst 18(7): 353-365. doi: 10. 1016/j. bbr. 2011. 03. 031.
18. Chakrabarti A, Morgenstern S, Knaab H (2004) Identification and application of requirements and their impact on the design process: a protocol study. Res Eng Des 15: 22-39. doi: 10. 1007/s00163-003-0033-5.
19. Gilb T (1997) Viewpoints: towards the engineering of requirements. Requir Eng 2(3): 165-169. doi: 10. 1007/BF02802774.
20. Davis A, Zowghi D (2006) Good requirements practices are neither necessary nor sufficient. Requir Eng J 11(1): 1-3. doi: 10. 1007/s00766-004-0206-4.
21. Loucopoulos P, Karakostas V (1995) System requirements engineering. McGraw-Hill International, New York.
22. Kotonya G, Sommerville I (1998) Requirements engineering: process and techniques. John Wiley & Sons, New York.
23. Nuseibeh B, Easterbrook S (2000) Requirements engineering: a roadmap. In: Proceedings of the conference on the future of software engineering. ACM Press, pp 35-46.
24. Dorfman M (1997) Requirements engineering. in software requirements engineering. In: Thayer H, Dorfman M (eds) 2. IEEE Computer Society Press, Los Alamitos, California, pp 7-22.
25. Jiang L (2005) A framework for the requirements engineering process development. PhD Thesis, University Of Calgary, Department of Electrical and Computer Engineering, Alberta.
26. Friedenthal S, Moore A, Steiner R (2008) A practical guide to SysML. The systems modeling language. Morgan Kaufmann OMG Press, Burlington.
27. Finger S, Dixon J (1989) A review of research in mechanical engineering design, part I: descriptive, prescriptive and computer-based models of design processes. Res Eng Des 1(1): 51-68. doi: 10. 1007/BF01580003.
28. Estefan JA (2008) Survey of model-based systems engineering (MBSE) methodologies. International Council on Systems Engineering (INCOSE). Technical Document INCOSE-TD-2007-003-02, Revision B.
29. Boucher M, Houlihan D (2008) System design: new product development for mechatronics. Publication of Aberdeen Group, Boston.
30. Arthurs G (2008) Model-based system engineering elements for deploying an efficient development environment. Publication of Telelogic, an IBM Company.
31. Forsberg K, Mooz H (1995) Application of the "Vee" to incremental and evolutionary development. In: Proceedings of the fifth annual international symposium of the national council on systems engineering (INCOSE).
32. Boehm BW (1988) A spiral model of software development and enhancement. IEEE Comput 21: 61-72. doi: 10. 1109/2. 59.
33. OMG (2008) Systems modelling language V1. 1. OMG Available specification.
34. Follmer M, Hehenberger P, Punz S, Zeman K (2010) Using SysML in the product development process of mechatronic systems. In: 11th international design conference (DESIGN 2010), pp 1513-1522.
35. Amihud H, Kasser J, Weis M (2007) How lessons learned from using QFD led to the evolution of a process for creating quality requirements for complex systems. J Syst Eng Manage 10(1): 45-63. doi: 10. 1002/sys. 20065.
36. Rehman F, Yan XT (2007) Evaluation of a context knowledge based tool to support decision making in the conceptual design. In: Proceedings of the international conference on engineering design, ICED'07.
37. Tseng MM, Jiao J (1998) Computer-aided requirement management for product definition: a methodology and implementation. Concurr Eng Res Appl 6(2): 145-160. doi: 10. 1177/1063293X9800600205.
38. Mamat R, Wahab DA, Abdullah S (2009) The integration of CAD and life cycle requirements in automotive seat design. Eur J Sci Res 31(1): 148-156.
39. Galea A, Borg J, Grech A, Farrugia P (2010) Intelligent life-oriented design solution space selection. In: Proceedings of the 11th international design conference DESIGN 2010 Dubrovnik, Croatia, pp 1295-1304.
40. Davis AM, Hickey AM (2002) Requirements researchers: do we practice what we preach? Requir Eng J 7(2): 107-111. doi: 10. 1007/s007660200007.
41. SLATE (2004) System Level Automation for Enterprises (SLATE), now part of UGS Teamcenter Requirements. http://www. ugs. com.
42. DOORS (2006) Dynamic Object Oriented Requirements System (DOORS). http://www. telelogic. com.
43. Booch G, Jacobson I, Rumbaugh J (1998) The unified modeling language user guide. Addison, Wesley.
44. Yin R (1994) Case study research: design and methods, 2nd edn. Sage Publishing, Edition Thousand Oaks, CA.
45. Peak RS, Burkhart RM, Friedenthal SA, Wilson MW, Bajaj M, Kim I (2007) Simulation-based design using SysML Part 1 and Part 2,. INCOSE international symposium, San Diego, USA.
46. Reisig W (1992) A primer in petri net design. Springer-Verlag, New York.
47. Wagenhals W, Haider S, Levis A (2003) Synthesizing executable models of object oriented architecture. J Syst Eng Manage 6(4): 266-300. doi: 10. 1002/sys. 10049.
48. Brace W, Coatanéa E, Kauranne H, Heiska M (2010) Formalization approach to early design synthesis. Int J Des Innov Res, IJODIR 5(2): 25-45.
49. IEEE-830 (1984) Guide to software requirements specification. ANSI/IEEE Std. 830.
50. Restrepo J, Christiaans H (2004). Problem structuring and information access in design. J Des Res 4(2): doi: 10. 1504/JDR. 2004. 009842.
51. Gawande A (2009) The checklist manifesto: how to get things right. Metropolitan Books, New York.