A framework to support requirements analysis in engineering design

Journal of Engineering Design

Volumn 23, Issue 12, 2012, Pages 876-904

  Brace, William ^a   Cheutet, Vincent ^b  

^a AALTO UNIVERSITY   (Finland)

^b SUPMECA   (France)

Author keywords

CORA framework; model based requirements; requirements analysis framework; requirements checklist; requirements information

Indexed keywords

REQUIREMENTS ENGINEERING; VERIFICATION;

CORA FRAMEWORKS; MODEL-BASED REQUIREMENTS; REQUIREMENTS ANALYSIS FRAMEWORKS; REQUIREMENTS CHECKLISTS; REQUIREMENTS INFORMATIONS;

INFORMATION MANAGEMENT;

EID: 84868224283     PISSN: 09544828     EISSN: 14661837     Source Type: Journal    
DOI: 10.1080/09544828.2011.636735     Document Type: Article

References (66)

1. Akao, Y. 2004. Quality function deployment: integrating customer requirements into product design, 1, Cambridge: Productivity Press.
2. Amihud, H., Kasser, J. and Weis, M. 2007. How lessons learned from using QFD led to the evolution of a process for creating quality requirements for complex systems. Systems Engineering and Management, 10(1): 45-63. (doi:10.1002/sys.20065)
3. Bahill, A. T. and Dean, F. F. What is systems engineering? A consensus of senior systems engineers. Proceedings of the sixth annual symposium of the international council on systems engineering (INCOSE). July7-11, Boston. Vol. 1, pp.503-508.
4. Bahill, T. A. and Henderson, S. 2005. Requirements development, verification, and validation exhibited in famous failures. Systems Engineering, 8(1): 1-14. (doi:10.1002/sys.20017)
5. Baumberger, C. and Lindemann, U. Requirement oriented process planning and configuration. Proceedings of NordDesign. August16-18, Reykjavik, Iceland. pp.244-254. New York: ACM Press.
6. Baxter, D. 2007. An engineering design reuse methodology using process modelling. Research in Engineering Design, 18(12): 37-48. (doi:10.1007/s00163-007-0028-8)
7. Blanchard, B. and Fabrycky, W. 2006. Systems engineering and analysis, 4, Englewood Cliffs, NJ: Prentice-Hall. International Series in Industrial and Systems Engineering
8. Brace, W. Early design modelling and simulation of behaviours: case study of mobile work machine. Proceedings of ASME-IDETC. San Diego, CA. pp.131-140. New York: ASME. 30 August-2 September
9. Brooks, F. 1987. No silver bullet-essence and accident in software engineering. IEEE Computer, 20(4): 10-19. (doi:10.1109/MC.1987.1663532)
10. Chan, K. Y. 2011. An intelligent fuzzy regression approach for effective product design that captures nonlinearity and fuzziness. Journal of Engineering Design, 22(8): 523-542. (doi:10.1080/09544820903550924)
11. Checkland, P. 1981. Systems thinking, systems practice, Chichester, UK: Wiley.
12. Claros, S. M.P., Prudhomme, G. and Brissaud, D. 2008. Requirement-oriented activities in an engineering design process. International Journal of Computer Integrated Manufacturing, 21(2): 127-138. (doi:10.1080/09511920701607816)
13. Cooper, R., Wootton, A. B. and Bruce, M. 1998. Requirement capture: theory and practice. Technovation, 18(8-9): 497-511. (doi:10.1016/S0166-4972(98)00033-9)
14. Cross, N. 2008. Engineering design methods strategies for product design, 4, Chichester, UK: John Wiley & Sons.
15. Darlington, M. J. and Culley, S. J. 2002. Current research in the engineering design requirement. Proceedings of the Institute of Mechanical Engineers, IMechE, Part B: Journal of Engineering Manufacture, 216(3): 375-388. (doi:10.1243/0954405021520049)
16. Davis, A. M. 1990. Software requirements: analysis and specification, Englewood Cliffs, NJ: Prentice-Hall.
17. Dieter, G. 2000. Engineering design: a material and processing approach, 3, New York: International Editions, McGraw-Hill.
18. Douglass, P. B. 1999. Doing hard time: developing real-time systems with UML-objects, frameworks, and patterns, Upper Saddle River, NJ: Addison-Wesley.
19. Drejer, A. 2008. Are you innovative enough?. International Journal of Innovation and Learning, 5(1): 1-17. (doi:10.1504/IJIL.2008.015944)
20. Flyvbjerg, B. 2006. Five misunderstandings about case-study research. Qualitative Inquiry, 12(2): 219-245. (doi:10.1177/1077800405284363)
21. Follmer, M. Using Sysml in the product development process of mechatronic systems. International design conference-design 2010, pp.17-20. May, Dubrovnik, Croatia
22. Franke, H.-J. 1975. Methodische Schritte beim Klaren Konstruktiver Aufgabenstellenungen, 395-402. Berlin: Springer-Verlag. Konstruktion 27
23. Friedenthal, S., Moore, A. and Steiner, R. 2008. A practical guide to SysML the systems modeling language, Burlington, MA: Morgan Kaufmann, Elsevier Science.
24. Gilb, T. 1997. Viewpoints: towards the engineering of requirements. Springer Computer Science, 2(3): 165-169.
25. Grady, J. 2006. System requirements analysis, Burlington, MA: Elsevier Inc. International ed
26. Greer, J. Enumerating the component space: first steps toward a design naming convention for mechanical parts. September2-6, Chicago, IL. Proceedings of ASME-IDETC, New York: ASME.
27. Gupta, A., Pawara, K. and Smart, P. 2007. New product development in the pharmaceutical and telecommunication industries: a comparative study. International Journal of Production Economics, 106(1): 41-60. (doi:10.1016/j.ijpe.2006.04.008)
28. Hall, T., Beechem, S. and Rainer, A. 2002. Requirements problems in twelve software companies: an empirical analysis. IEE Proceedings Software, 149(5): 153-160. (doi:10.1049/ip-sen:20020694)
29. Hicks, B. J. 2002. A framework for the requirements of capturing, storing and reusing information and knowledge in engineering design. International Journal of Information Management, 22(4): 263-280. (doi:10.1016/S0268-4012(02)00012-9)
30. INCOSE. 1998. Terms glossary version 0, INCOSE SE
31. Jiang, L. 2005. A framework for the requirements engineering process development, University of Calgary. Thesis (PhD)
32. Kotonya, G. and Sommerville, I. 1998. Requirements engineering: process and techniques, Chichester, UK: John Wiley & Sons.
33. Loftus, C., Hicks, B. and McMahon, C. A. Capturing key relationships and stakeholders over the product lifecycle: an email based approach. 6th international conference on product lifecycle management, PLM'09. July6-8. Bath, UK
34. Loucopoulos, P. and Kavakli, E. 1995. Enterprise modelling and the teleological approach to requirements engineering. International Journal of Intelligent and Cooperative Information Systems, 4(1): 45-79. (doi:10.1142/S0218843095000032)
35. Lowe, A., McMahon, C. and Culley, S. 2004. Information access, storage and use by engineering designers-Part 1. The Journal of the Institution of Engineering Designers, 30(2): 30-32.
36. Macaulay, L. Requirements for requirements engineering techniques. Proceedings of the second international conference on requirements engineering-IEEE. pp.157-164. Piscataway, NJ: IEEE. Colorado Springs, CO
37. McAlpine, H. Key themes in design information management. International design conference-design 2010. pp.17-20. May, Dubrovnik, Croatia
38. McConnell, S. 1996. Rapid development: taming wild software schedules, 1., Redmond, WA: Microsoft Press.
39. Moores, T. T. and Gregory, F. H. 2000. Cultural problems in applying SSM for IS development. Journal of Global Information Management, 8(1): 14-19. (doi:10.4018/jgim.2000010102)
40. Nuseibeh, B. and Easterbrook, S. Requirements engineering: a roadmap. June4-11, Limerick, Ireland. Proceedings of the conference on the future of software engineering, pp.35-46. New York: ACM Press.
41. Niksula, U. 2002. BaRE-a ready to use method for requirements engineering, Finland: Lappeenranta University of Technology. Licentiate Thesis
42. OMG, 2008. Systems modeling language V1.1. OMG available specification
43. Otto, K. and Wood, K. 2001. Product design: Techniques in reverse engineering and new product development, Upper Saddle River, NJ: Prentice-Hall.
44. Pahl, G. and Beitz, W. 2007. Engineering design. A systematic approach, 3, Edited by: Wallace, K. and Blessing, L. Berlin: Springer. translation and edition
45. Parviainen, P. 2003. "Requirements engineering. Inventory of technologies". In VTT publications 508, Finland: Espoo.
46. Peak, R. S. Simulation-based design using SysML Part 1 and Part 2. INCOSE international symposium. San Diego, CA
47. Pisano, G. and Wheelwright, S. 1995. The new logic of high-tech R&D. Harvard Business Review, 73(5): 93-104.
48. Pohl, K. 1994. The three dimensions of requirements engineering: a framework and its applications. Information Systems, 19(3): 243-258. (doi:10.1016/0306-4379(94)90044-2)
49. Pugh, S. 1997. Total design: integrated methods for successful product engineering, Harlow, UK: Addison-Wesley Longman Ltd.
50. Rechtin, E. 2000. Systems architecting of organizations: why eagles can't fly, Boca Raton, FL: CRC Press.
51. Short, T. D. Matching the voice of the engineer to the voice of the customer: an evolution of QFD. Proceedings of ICED'09. 17th International conference on engineering design ICED'09. August24-27, Stanford, CA. Edited by: Norell Bergendahl, M., Grimheden, M. and Leifer, L. Glasgow, UK: Design Society.
52. Soares, M. S. and Vrancken, J. 2008. Model-driven user requirements specification using SysML. Journal of Software, 3(6): 57-68. (doi:10.4304/jsw.3.6.57-68)
53. Sommerville, I. 2001. Software engineering, 6, Boston, MA: Addison-Wesley.
54. Stake, R. 1995. The art of case research, Newbury Park, CA: Sage Publications.
55. Strauss, A. and Corbin, J. 1998. Basics of qualitative research: techniques and procedures for developing grounded theory, 2., Thousand Oaks, CA: Sage Publications.
56. Sudin, M. N., Ahmed-Kristensen, S. and Andreasen, M. M. The role of specification in the design process: a case study. International design conference-design 2010. May17-20. Croatia: Dubrovnik.
57. Svensson, D. and Malmqvist, J. Integration of requirement management and product data management systems. Proceedings of DETC'01. September9-12, Pittsburgh, PA.
58. Ullman, D. 2002. The mechanical design process, 3, New York: McGraw Hill.
59. Ulrich, K. and Eppinger, S. 2004. Product design and development, 3, New York: McGraw-Hill.
60. van Lamsweerde, A. 2000. Requirements engineering in the year 2000; a research perspective, 5-19. New York: ACM Press.
61. VAI. 1993. Value analysis, value engineering, and value management, Clifton Park, NY: Value Analysis Inc.
62. Ward, J., Shefelbine, S. and Clarkson, P. J. Requirements capture for medical device design. International conference on engineering design ICED 03. August19-21. Stockholm
63. Weilkiens, T. 2008. Systems engineering with SysML/UML: modelling, analysis, design, Burlington, MA: Morgan Kaufmann.
64. Wiegers, K. E. 2003. Software requirements 2: practical techniques for gathering and managing requirements throughout the product development cycle, 2, Redmond, WA: Microsoft Press.
65. Yin, R. 1994. Case study research: design and methods, 2, Thousand Oaks, CA: Sage Publishing.
66. Zave, P. and Jackson, M. 1997. Four dark corners of requirements engineering. ACM Transactions on Software Engineering and Methodology, 6(1): 1-30. (doi:10.1145/237432.237434)