1 |
Wiegers, K. E. (2000), When telepathy won't do: Requirements engineering key practices, Cutter IT Journal, May 2000, www.processimpact.com/articles/telepathy.html.
|
2 |
Wiegers, K. E. (2003), Software requirements, 2nd ed. Microsoft Press.
|
3 |
Ross, A. M., Rhodes, D. H., and Hastings, D. E. (2008), Defining changeability: Reconciling flexibility, adaptability, scalability, modifiability, and robustness for maintaining system lifecycle value, Systems Engineering, 11, 246-262.
DOI
ScienceOn
|
4 |
Rouibah, K. and Caskey, K. R. (2003), Change management in concurrent engineering from a parameter perspective, Comput Ind, 50(1), 15-34.
DOI
ScienceOn
|
5 |
Schach, S. R. and Tomer, A. (2000), A maintenanceorientated approach to software construction, J Softw Maint-Res Pract, 12(1), 25-45.
DOI
ScienceOn
|
6 |
SERENA (2011), RTM product overview. Accessed at: www.sciti.com.ar/productos/pdf_serena/RTM%20overview.pdf, on 3 May 2011.
|
7 |
Sommerville, I. (2007), Software Engineering, 8th ed.: Addison-Wesley.
|
8 |
Standish Group Report (1995), 'CHAOS,' http://www.projectsmart.co.uk/docs/chaos_report.pdf, Accessed on 1 May 2011.
|
9 |
Strens, M. R. and Sugden, R. C. (1996), Change analysis: a step towards meeting the challenge of changing requirements, Proc. IEEE Symposium and Workshop on Engineering of Computer-Based Systems, IEEE Comput. Soc. Press, 278-283.
|
10 |
Tavassoli, D. (2009), Ten steps to better requirements management, IBM white paper. Accessed on 3 May 2011 at: ftp://ftp.boulder.ibm.com/software/uk/pdf/RAW14059-USEN-00-1.pdf.
|
11 |
Ullman, D. G. (2010), The mechanical design process, 4th edn, McGraw-Hill Education, Boston.
|
12 |
Ulrich, K. T. and Eppinger, S. D. (2008), Product design and development, 4th edn. McGraw-Hill HE, Boston.
|
13 |
Uspenskiy, D. (2004), Requirements management (RM) tools.
|
14 |
Verganti, R. (1997), Leveraging on systematic learning to manage the early phases of product innovation projects, R&D Management, 27, 377-392
DOI
ScienceOn
|
15 |
Ward, J., Shefelbine, S., and Clarkson, P. J. (2003), Requirements capture for medical device design. Int. Conf. on Engineering Design, ICED'03, Stockholm.
|
16 |
McGee, S. and Greer, D. (2009), A software requirements change source taxonomy, Fourth Int. Conf. on Software Engineering Advances, IEEE, 51-58.
|
17 |
Nurmuliani, N., Zowghi, D., and Williams, S. P. (2004), Using card sorting technique to classify requirements change, 12th International Requirements Engineering Conference (RE).
|
18 |
O'Neal, J. S. and Carver, D. L. (2001), Analyzing the impact of changing requirements, Proc. IEEE Int. Conf. on Software Maintenance, ICSM 2001, IEEE Comput. Soc, 190-195.
|
19 |
Otto, K. and Wood, K. (2001), Product design: techniques in reverse engineering and new product development, Prentice Hall, Upper Saddle River.
|
20 |
Pahl, G. and Beitz, W. (1996), Engineering design-a systematic approach, 2nd edn. Springer, London.
|
21 |
Peterson, C., Paasch, R. K., Ge, P., and Dietterich, T. G. (2007), Product innovation for interdisciplinary design under changing requirements, Int. conf. on engineering design, ICED, Cite Des Sciences et de l'Industrie, Paris, France.
|
22 |
Ramzan, S. and Ikram, N. (2005), Making decision in requirement change management, Proc. Int. Conf. on Information and Communication Technologies, IEEE, 309-312.
|
23 |
Pressman, R. (2005), Software Engineering: A Practitioner's Approach, 6th ed.: Mc Graw Hill.
|
24 |
Qureshi, A., Murphy, J. T., Kuchinsky, B., Seepersad, C. C., Wood, K. L. and Jensen, D. D. (2006), Principles of product flexibility. Proc. IDETC/CIE 2006, ASME 2006 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference, Philadelphia, Pennsylvania, USA.
|
25 |
Rajlich, V. (2000), Modelling software evolution by evolving interoperation graphs, Ann Softw Eng, 9, 235-248.
DOI
ScienceOn
|
26 |
Ramzan, S. and Ikram, N. (2006), Requirement change management process models: activities, artifacts and roles, Proc. IEEE Int. Multitopic Conf., IEEE, 219-223.
|
27 |
Koh, E. C. Y. and Clarkson, P. J. (2009), A modelling method to manage change propagation, Int. Conf. on Engineering Design, ICED Stanford University, Stanford, CA, USA.
|
28 |
Kotonya, G. and Sommerville, I. (1998), Requirements Engineering: Processes and Techniques, Wiley.
|
29 |
Kujala, S. M., Kauppinen, L., and Lehtola, K. T. (2009), The role of user involvement in requirements quality and project success, Proc. 13th IEEE Int. Conf. on Requirements Engineering, Paris, 75-84.
|
30 |
Lamsweerde, A. (2009), Requirements Engineering John Wiley and Sons, Incorporated.
|
31 |
Land, F. (1982), Adapting to Changing User Requirements, Information and Management, 5(2), 59-75.
DOI
ScienceOn
|
32 |
Larson, A. L. (2000), Sustainable innovation through an entrepreneurship lens, Business Strategy and the Environment, 9, 304-317.
DOI
ScienceOn
|
33 |
McLellan, J. M., Morkos, B., Mocko, G. G., and Summers, J. S. (2010), Requirement modeling systems for mechanical design: a systematic method for evaluating requirement management tools and languages, Proc. of IDETC/CIE 2010, ASME 2010 international design engineering technical conferences and computers and information in engineering conference, Montreal, Canada, Paper # DETC2010-28989.
|
34 |
Leffingwell, D. and Widrig, D. (2003), Managing Software Requirements: A Use Case Approach, 2nd ed.: Addison Wesley.
|
35 |
Lemmens, Y., Guenov, M., Rutka, A., Coleman, P., and Schmidt-Schaffer, T. (2007), Methods to analyse the impact of changes in complex engineering systems, 7th AIAA Aviation Technology, Integration and Operations Conference (ATIO).
|
36 |
Martin, M. V. and Ishii, K. (2002), Design for variety: developing standardized and modularized product platform architectures, Research in Engineering Design, 13, 213-235.
DOI
|
37 |
Mathelin, S., Boujut, J.-F., and Tollenaere, M. (2005), Improving collaborative design tools in automotive industry: A case study, Int. Conf. on Engineering Design, ICED'05, Melbourne.
|
38 |
Ibrahim, S., Idris, N. B., Munro, M., and Deraman, A. (2005), Integrating software traceability for change impact analysis, Int. Arab J. of Information Technology, 2(4).
|
39 |
IEEE-Standard-830 (1984), IEEE Guide to Software Requirements Specifications.
|
40 |
IEEE (1990), IEEE Standard glossary of software engineering terminology, IEEE Std. 610.
|
41 |
IEEE (1998), IEEE Standard 830: Recommended Practice for Software Requirements Specifications.
|
42 |
Imtiaz, S., Ikram, N., and Imtiaz, S. (2008), Impact analysis from multiple perspectives: Evaluation of traceability techniques, The Third International Conference on Software Engineering Advances, IEEE, 457-464.
|
43 |
Keller, R., Eger, T., Eckert, C. M. and Clarkson, P. J. (2005), Visualising change propagation, Int. Conf. on Engineering Design, ICED05, Melbourne.
|
44 |
Jarratt, T. A. W., Eckert, C. M., and Clarkson, P. J. (2004), Engineering change. In: Clarkson, P. J., and Eckert, C. M. (eds) Design process improvement, Springer, N. Y.
|
45 |
Jarratt, T. A. W., Eckert, C. M., Caldwell, N. H. M., and Clarkson, P. J. (2011), Engineering change: an overview and perspective on the literature, Res Eng Des, 22, 103-124.
DOI
ScienceOn
|
46 |
Jiao, J. and Chen, C.-H. (2006), Customer requirement management in product development: A review of research issues, Concurrent Engineering: Research and Applications, 14(3), 1-25.
|
47 |
Keller, R., Alink, T., Pfeifer, C., Eckert, C. M., Clarkson, P. J., and Albers, A. (2007), Product models in design: A combined use of two models to assess change risks, International Conference on Engineering Design, ICED, Cite des Sciences et de l'Industrie, Paris, France.
|
48 |
Keller, R., Eckert, C. M., and Clarkson, P. J. (2008), Through-life change prediction and management. Proceedings International Conference on Product Lifecycle Management, PLM-SP$, Chapter 3, 212-221.
|
49 |
Darlington, M. J. and Culley, S. J. (2004), A model of factors influencing the design requirement, Design Studies, 25(4), 329-350.
DOI
ScienceOn
|
50 |
De Lucia, A., Fasano, F., and Oliveto, R. (2008), Traceability management for impact analysis, Frontiers of Software Maintenance, IEEE, 21-30.
|
51 |
Eckert, C. M., Clarkson, P. J., and Zanker, W. (2004), Change and customization in complex engineering domains, Res Eng Des, 15(1), 1-21.
DOI
ScienceOn
|
52 |
Eckert, C., Clarkson, J., and de Weck, O. (2010), Call for papers for a special issue on 'Engineering Change,' Research in Engineering Design.
|
53 |
Gause, D. C. and Weinberg, G. M. (1989), Exploring Requirements: Quality Before Design, Dorset House, N. Y.
|
54 |
Eger, T., Eckert, C. M., and Clarkson, P. J. (2005), The role of design freeze in product development: In Samuel, A., and Lewis, W. (eds) Proc. 15th int. conf. on engineering design (ICED'05), Melbourne, 164-165.
|
55 |
Eleiche, A. M. (2010), Engineering change management in sustainable innovative projects, APIEMS 2010: The 11th Asia Pacific Industrial Engineering and Management Systems Conference, and The 14th Asia Pacific Regional Meeting of Int. Foundation for Production Research, 501.
|
56 |
Fricke, E., Gebhard, B., Negele, H., and Igenbergs, E. (2000), Coping with changes: causes, findings and strategies. Syst Eng, 3(4), 169-179.
DOI
ScienceOn
|
57 |
Giaglis, G. (2001), A Taxonomy of Business Process Modeling and Information Systems Modeling Techniques, Information Systems, 13, 209-228.
|
58 |
Harker, S. D. P., Eason, K. D. and Dobson, J. E. (1993), The change and evolution of requirements as a challenge to the practice of software engineering, Proc. IEEE International Symposium on Requirements Engineering, San Diego, CA, USA.
|
59 |
Hintersteiner, J. D. (2000), Addressing Changing Customer Needs by Adapting Design Requirements. In First International Conference on Axiomatic Design, ICAD2000, Cambridge, MA, 290-299.
|
60 |
Ahmed, S. and Kanike, Y. (2007), Engineering change during a product's lifecycle, In: Bocquet, J-C (ed) Proceedings of the 16th international conference on engineering design (ICED'07), Paris, France, 633-634.
|
61 |
Agouridas, V., Marshall, A., Mckay, A., and Pennington, A. D. (2006), Establishing stakeholder needs for medical devices, ASME 2006 Int. Design Engineering Technical Conferences and Computers and Information in Engineering Conference, Philadelphia, Pennsylvania, USA.
|
62 |
Aurum, A. and Wohlin, C. (Editors) (2005), Engineering and Managing Software Requirements, Springer, Heidelberg.
|
63 |
Blackburn, J. D., Scudder, G. D., and Van Wassenhove, L. N. (1996), Improving Speed and Productivity of Software Development: A Global Survey of Software Developers, IEEE Trans. on Software Engineering, 22(12), 875-885.
DOI
ScienceOn
|
64 |
Bohner, S. A. (2002), Software change impacts-an evolving perspective, Proc. Int. Conf. on Software Maintenance, IEEE Comput. Soc, 263-272.
|
65 |
Bourque, P. and Dupuis, R. (2004), Guide to the Software Engineering Body of Knowledge, IEEE Computer Society
|
66 |
Braude, E. (2010), Software Engineering: Modern Approaches, 2nd ed., Wiley.
|
67 |
CCWCE (Center for Clean Water and Clean Energy Research) (2008), Online at: http://ccwce.mit.edu.
|
68 |
Cross, N. (1989), Engineering design methods, Wiley, Chichester.
|
69 |
Darlington, M. J. and Culley, S. J. (2002), Current research in the engineering design requirement, Proc Instn Mech Engrs, Part B: J Engng Manufacture, 216, 375-388.
DOI
ScienceOn
|