Design Requirements in Software and Engineering Systems

다국어 초록 (Multilingual Abstract)

The subject of "Design Requirements" (DR) is central to the design of software and engineering systems. The main reason for this is that quality aspects are usually closely tied to requirements, among other things. In this review paper, we consider how the subject of requirements is being managed in these two seemingly different design disciplines. Two important aspects are covered, namely: (a) requirements development, describing various activities leading to requirements documentation, and (b) requirements change management, describing various activities needed for the proper treatment of the inevitable changes in requirements. Similarities and differences on how these two aspects are handled in software and engineering systems are highlighted. It is concluded from this literature survey that the management of software requirements is quite coherent and well established as a science. On the other hand, management of engineering systems requirements suffer from being unstructured, in particular when requirements changes are involved. Important gaps and future important research areas are identified.

목차 (Table of Contents)

• ABSTRACT
• 1. INTRODUCTION
• 2. REQUIREMENTS
• 3. REQUIREMENTS DEVELOPMENT (RD)
• 4. REQUIREMENTS MANAGEMENT (RM)
• 5. CONCLUDING REMARKS
• ACKNOWLEDGMENT
• REFERENCES

참고문헌 (Reference)

1 Wiegers, K. E., "When telepathy won’ do: Requirements engineering key practices" 2000

2 Keller, R., "Visualising change propagation" 2005

3 Nurmuliani, N., "Using card sorting technique to classify requirements change" 2004

4 De Lucia, A., "Traceability management for impact analysis" IEEE 21-30, 2008

5 Keller, R., "Through-life change prediction and management" PLM-SP$ 212-221, 2008

6 Kujala, S. M., "The role of user involvement in requirements quality and project success" 75-84, 2009

7 Eger, T., "The role of design freeze in product development" 164-165, 2005

8 Ullman, D. G., "The mechanical design process, 4th edn" McGraw-Hill Education 2010

9 Harker, S. D. P., "The change and evolution of requirements as a challenge to the practice of software engineering" 1993

10 Tavassoli, D., "Ten steps to better requirements management, IBM white paper"

11 Larson, A. L., "Sustainable innovation through an entrepreneurship lens" 9 : 304-317, 2000

12 Wiegers, K. E., "Software requirements, 2nd ed" Microsoft Press 2003

13 Bohner, S. A., "Software change impacts-an evolving perspective" IEEE Comput. Soc 263-272, 2002

14 Braude, E., "Software Engineering: Modern Approaches, 2nd ed." Wiley 2010

15 Pressman, R., "Software Engineering: A Practitioner’ Approach, 6th ed." Mc Graw Hill 2005

16 Sommerville, I., "Software Engineering, 8th ed." Addison-Wesley 2007

17 Uspenskiy, D., "Requirements management (RM) tools"

18 Ward, J., "Requirements capture for medical device design" 2003

19 Kotonya, G., "Requirements Engineering: Processes and Techniques" Wiley 1998

20 Lamsweerde, A., "Requirements Engineering" John Wiley and Sons 2009

21 McLellan, J. M., "Requirement modeling systems for mechanical design: a systematic method for evaluating requirement management tools and languages" 2010

22 Ramzan, S., "Requirement change management process models: activities, artifacts and roles" IEEE 219-223, 2006

23 SERENA, "RTM product overview"

24 Keller, R., "Product models in design: A combined use of two models to assess change risks" ICED 2007

25 Peterson, C., "Product innovation for interdisciplinary design under changing requirements" ICED 2007

26 Otto, K., "Product design: techniques in reverse engineering and new product development" Prentice Hall 2001

27 Ulrich, K. T., "Product design and development, 4th edn" McGraw-Hill HE 2008

28 Qureshi, A., "Principles of product flexibility" 2006

29 Rajlich, V., "Modelling software evolution by evolving interoperation graphs" 9 : 235-248, 2000

30 Lemmens, Y., "Methods to analyse the impact of changes in complex engineering systems" 2007

31 Leffingwell, D., "Managing Software Requirements: A Use Case Approach, 2nd ed" Addison Wesley 2003

32 Ramzan, S., "Making decision in requirement change management" IEEE 309-312, 2005

33 Verganti, R., "Leveraging on systematic learning to manage the early phases of product innovation projects" 27 : 377-392, 1997

34 Ibrahim, S., "Integrating software traceability for change impact analysis" 2 (2): 2005

35 Mathelin, S., "Improving collaborative design tools in automotive industry: A case study" 2005

36 Blackburn, J. D., "Improving Speed and Productivity of Software Development: A Global Survey of Software Developers" 22 (22): 875-885, 1996

37 Imtiaz, S., "Impact analysis from multiple perspectives: Evaluation of traceability techniques" IEEE 457-464, 2008

38 IEEE, "IEEE Standard glossary of software engineering terminology"

39 IEEE, "IEEE Standard 830: Recommended Practice for Software Requirements Specifications"

40 "IEEE Guide to Software Requirements Specifications"

41 Standish Group Report, "HAOS"

42 Bourque, P., "Guide to the Software Engineering Body of Knowledge"

43 Gause, D. C., "Exploring Requirements: Quality Before Design" Dorset House 1989

44 Agouridas, V., "Establishing stakeholder needs for medical devices" 2006

45 Pahl, G., "Engineering design-a systematic approach, 2nd edn" Springer 1996

46 Cross, N., "Engineering design methods" Wiley 1989

47 Jarratt, T. A. W., "Engineering change: an overview and perspective on the literature" 22 : 103-124, 2011

48 Jarratt, T. A. W., "Engineering change, In Design process improvement" Springer 2004

49 Eleiche, A. M., "Engineering change management in sustainable innovative projects" 501-, 2010

50 Ahmed, S., "Engineering change during a product’ lifecycle" 633-634, 2007

51 Aurum, A., "Engineering and Managing Software Requirements" Springer 2005

52 Martin, M. V., "Design for variety: developing standardized and modularized product platform architectures" 13 : 213-235, 2002

53 Ross, A. M., "Defining changeability: Reconciling flexibility, adaptability, scalability, modifiability, and robustness for maintaining system lifecycle value" 11 : 246-262, 2008

54 Jiao, J., "Customer requirement management in product development: A review of research issues" 14 (14): 1-25, 2006

55 Darlington, M. J., "Current research in the engineering design requirement" 216 : 375-388, 2002

56 Fricke, E., "Coping with changes: causes, findings and strategies" 3 (3): 169-179, 2000

57 Rouibah, K., "Change management in concurrent engineering from a parameter perspective" 50 (50): 15-34, 2003

58 Eckert, C. M., "Change and customization in complex engineering domains" 15 (15): 1-21, 2004

59 Strens, M. R., "Change analysis: a step towards meeting the challenge of changing requirements" IEEE Comput. Soc. Press 278-283, 1996

60 "Center for Clean Water and Clean Energy Research"

61 Eckert, C., "Call for papers for a special issue on ‘Engineering Change,’, In Research in Engineering Design" 2010

62 O’eal, J. S., "Analyzing the impact of changing requirements" 190-195, 2001

63 Hintersteiner, J. D., "Addressing Changing Customer Needs by Adapting Design Requirements" 290-299, 2000

64 Land, F., "Adapting to Changing User Requirements" 5 (5): 59-75, 1982

65 McGee, S., "A software requirements change source taxonomy" IEEE 51-58, 2009

66 Koh, E. C. Y., "A modelling method to manage change propagation" 2009

67 Darlington, M. J., "A model of factors influencing the design requirement" 25 (25): 329-350, 2004

68 Schach, S. R., "A maintenanceorientated approach to software construction" 12 (12): 25-45, 2000

69 Giaglis, G., "A Taxonomy of Business Process Modeling and Information Systems Modeling Techniques" 13 : 209-228, 2001