Requirements engineering

Requirements Engineering

Volumn , Issue , 2017, Pages 1-240

  Dick, Jeremy ^a   Hull, Elizabeth ^b   Jackson, Ken ^c  

^a Costain Group PLC ^*  (United Kingdom)

^b UNIVERSITY OF ULSTER   (United Kingdom)

^c NONE

Author keywords

[No Author keywords available]

Indexed keywords

SYSTEMS ENGINEERING;

EFFECTIVE SOLUTION; GENERIC PROCESS; MODELLING TECHNIQUES; PRACTICAL EXPERIENCE; VALIDATION AND VERIFICATION;

REQUIREMENTS ENGINEERING;

EID: 85035030312     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/978-3-319-61073-3     Document Type: Book

References (80)

1. Abrial J-R (1996) The B-book: assigning programs to meanings. Cambridge University Press, New, NY.
2. Alderson A, Hull MEC, Jackson K, Griffiths LE (1998) Method engineering for industrial real-time and embedded systems. Inf Softw Tech 40:443-454.
3. Andriole SJ (1996) Managing systems requirements: methods, tools and cases. McGraw-Hill, New York.
4. Babich W (1986) Software configuration management - coordination for team productivity. Addison-Wesley Longman Publishing Co., Inc. Boston, MA, USA.
5. Bernstein P (1996) Against the gods - the remarkable story of risk. John Wiley & Sons Inc., Somerset, New Jersey, U.S.A.
6. Bjorner D, Jones CB (1978) The Vienna Development Method: The Meta-Language, Lecture Notes in Computer Science, Springer Verlag, Berlin, p 61.
7. Boehm B (1981) Software engineering economics, Prentice Hall PTR, Upper Saddle River, NJ, U.S.A.
8. Bolognesi T, Brinksma E (1987) Introduction to the ISO specification language LOTOS. Computer Networks and ISDN Systems 14(1):25-59.
9. Booch G (1994) Object-oriented design with applications. Benjamin Cummins, Redwood City.
10. Brown AW, Earl AN et al (1992) Software engineering environments. McGraw-Hill, London
11. Budgen D (1994) Software design. Addison-Wesley.
12. CarnegieMellon (2006) CMMI® for development, version 1.2. Software Engineering Institute, CMMI-DEV, Pitsburg., p 15213-3890.
13. Chaochen Z, Hoare CAR, Ravn AP (1991) A calculus of durations. Inf Process Lett 40(5):269-276.
14. Chen P (1976) The entity-relationship model-toward a unified view of data. In: ACM transactions on database systems 1/1/1976, ACM-Press. ISSN 0362-5915, S. 9-36.
15. Clark KB, Fujimoto T (1991) Product development performance. Harvard Business School Press, Boston, MA.
16. Coad P, Yourdon E (1991a) Object-oriented analysis. Yourdon Press, Englewood.
17. Coad P, Yourdon E (1991b) Object-oriented design. Yourdon Press, Englewood.
18. Cooper RG (1993) Winning at new products. Addison-Wesley, Reading, MA.
19. Crosby PB (1979) Quality is free. McGraw-Hill, New York.
20. Crosby PB (1984) Quality without tears. New American Library, New York.
21. Darke P, Shanks GG (1997) User viewpoint modelling: understanding and representing user viewpoints during requirements definition. Inf Syst J 7(3):213-240.
22. Davis AM (1993) Software requirements: objects, functions and states. Prentice-Hall, Englewood Cliffs.
23. DeGrace P (1993) The Olduvai Imperative: CASE and the state of software engineering practice. Yourdon Press, Englewood Cliffs, NY.
24. DeMarco T (1978) Structured analysis and system specification. Yourdon Press, Englewood Cliffs, NJ.
25. DeMarco T (1982) Controlling software projects. Yourdon Press, Englewood Cliffs, NJ.
26. DeMarco T, Lister T (1987) Peopleware - Productive projects and teams. Dorset House Publishing, New York.
27. Dick J, Faivre A (1993) Automating the generation and sequencing of test cases from modelbased specifications. In: Conf. Proc. FME '93, Odense, Denmark, April 1993.
28. Dick J, Jones B, (2012) On the Complexity of Requirements Flow-down Structures. INCOSE International Symposium 22 (1):1197-1206.
29. Dick J, Llorens J (2012) Using statement-level templates to improve the quality of requirements. In: Proc. 24th Int. Conf. on software & systems engineering and their applications, Paris, October 2012.
30. Easterbrook S, Nuseibeh B (1996) Using viewpoints for inconsistency management. Softw Eng J 11(1):31-43.
31. Faulk S, Brackett J, Ward P, Kirby J (1992) The core method for real-time requirements. IEEE Softw 9(5):22-33.
32. Finkelstein A, Kramer J, Nuseibeh B, Goedicke M (1992) Viewpoints: a framework for integrating multiple perspectives in systems development. Int J Softw Eng Knowl Eng 2(10): 31-58.
33. Fowler M, Scott K (1997) UML distilled: applying the standard object modeling language. Addison-Wesley, Reading.
34. Gilb T (1988) Principles of software engineering management. Addison-Wesley, Reading, MA.
35. Gilb T (2005) Competitive engineering: a handbook for systems engineering, requirements engineering and software engineering management using planguage. Elsevier Butterworth- Heinemann, Oxford.
36. Gorchels L (1997) The product manager's handbook. NTC Business Books, Chicago, IL.
37. Gotel OCZ, Finkelstein ACW (1995) Contribution structures. Proceedings RE'95. IEEE Press, York, UK.
38. Harel D (1987) Statecharts: a visual formalism for complex systems. Sci Comput Program 8:231-274.
39. Hull MEC, Taylor PS, Hanna JRP, Millar RJ (2002) Software development processes - an assessment. Inf Softw Tech 44(1):1-12.
40. Humphrey WM (1989) Managing the software process. Addison-Wesley, NY.
41. IEEE STD 1220-1998 (1998) Standard for application and management of the systems engineering process. IEEE, New York.
42. INCOSE (2007) INCOSE SE Vision 2020, INCOSE-TP-2004-004-02. In: International council on systems engineering (INCOSE) 7670 opportunity road, Suite 220, San Diego, California 92111-2222 USA.
43. INCOSE (2017) Guide for writing requirements, INCOSE-TP-2010-006-02, version 2.1, 2017, prepared by requirements working group. In: International council on systems engineering (INCOSE) 7670 opportunity road, Suite 220, San Diego, California 92111-2222 USA.
44. Jackson M (1995) Software requirements & specifications: a lexicon of practice, principles and prejudices. Addison-Wesley, Wokingham, UK.
45. Jacobsen I, Christerson M et al (1993) Object-oriented software engineering. Addison-Wesley, Wokingham, UK.
46. Kennedy L (2005) Keeping the promise: a work ethic for doing things right. Reliable Man Books, Orlando, FL.
47. Kotonya G, Sommerville I (1996) Requirements engineering with viewpoints. Softw Eng J 11(1):5-11.
48. Kotonya G, Sommerville I (1998) Requirements engineering: processes and techniques. John Wiley & Sons, Chichester.
49. Leite JCP, Freeman PA (1991) Requirements validation through viewpoint resolution. Trans Softw Eng 12(2):1253-1269.
50. Loucopoulos P, Karakostas V (1995) Systems requirements engineering. McGraw-Hill, London.
51. Mazza C et al (1994) ESA - Software engineering standards. Prentice-Hall, New Jersey.
52. Monroe RT, Kompanek A, Metlon R, Garlan D (1997) Architectural styles, design patterns, and objects. IEEE Software 14(1):43-52. Jan.
53. Mumford E (1989) User participation in a changing environment - Why we need it. In: Knight K Ed Participation in systems development. Kogan Page, London.
54. Nuseibeh B, Kramer J, Finkelstein A (1994) A framework for expressing the relationships between multiple views in requirements specification. Trans Softw Eng 20(10):760-773.
55. Oliver DW, Kelliher TP, Keegan JG (1997) Engineering complex systems with models and objects. McGraw-Hill, New York.
56. OMG (2003) The unified modelling language version 2, www.omg.org.
57. Page-Jones M (1980) The practical guide to structured systems. Yourdon Press, NY.
58. Perrow C (1984) Normal accidents. Basic Books, NY
59. Petroski H (1982) To engineer is human - the role of failure in successful design. Vintage Books, NY.
60. Petroski H (1996) Invention by design: how engineers get from thought to thing. Harvard University Press, Cambridge, MA.
61. Poots C, Takahashi K et al (1994) Inquiry-based requirements analysis. IEEE Softw 11(2):21-32.
62. Pressman RS (1997) Software engineering: a practitioner's approach. McGraw-Hill, London.
63. Ross DT (1977) Structured analysis (SA): a language for communicating ideas. IEEE Trans Softw Eng 3(1):16-34.
64. Ross DT (1985) Applications and extensions of SADT. IEEE Comput 18(4):25-34.
65. Ross DT, Schoman KE (1977) Structured analysis for requirements definition. IEEE Trans Softw Eng 3(1):6-15.
66. Rumbaugh J, Blaha M, Premerlani W, Eddy F, Lorenzen W (1991) Object-oriented modeling and design. Prentice-Hall, NY.
67. Shlaer S, Mellor SJ (1991) Object life cycles - modeling the world in states. Yourdon Press, NY.
68. Shlaer S, Mellor SJ (1998) Object-oriented systems analysis. Prentice-Hall, Englewood Cliffs
69. Software Engineering Institute (Carnegie-Mellon) (1991) Capability maturity model for software. In: Tech. report CMU/SEI-91-TR-24.
70. Sommervile I (1996) Software engineering. Addison-Wesley, Wokingham.
71. Sommervile I, Sawyer P (1997) Requirements engineering: a good practice guide. John Wiley and Sons, Chichester.
72. Spivey JM (1989) The Z notation: a reference manual. Prentice Hall International Series in Computer Science, Hemel Hempstead, Hertfordshire, UK.
73. Standish Group (1995), The CHAOS Report 1995, Standish Group International. Inc., Boston MA.
74. Standish Group (2015), The CHAOS Report 2015, Standish Group International. Inc., Boston MA.
75. Stevens R, Brook P, Jackson K, Arnold S (1998) Systems engineering: coping with complexity. Prentice-Hall, Europe.
76. SyntheSys (2014) SPIRIT - UML modelling, white paper, http://www.synthesys.co.uk/brochures_ new/5.4SPIRIT%20Modelling%20Tech%20Sheet.pdf.
77. Wheatcroft L, Ryan M, Dick J (2016) On the use of attribute to manage requirements. Syst Eng J Pub. Wiley 19(5):448-458.
78. Woodcock H, Chard J (2013) A proposed Agile systems engineering manifesto. In: INCOSE UK ASEC 2013. https://www.slideshare.net/hazel-woodcock/a-proposed-agile-systems-engineeringmanifesto- noteless.
79. Yourdon EN (1990) Modern structured analysis. Prentice-Hall, Englewood Cliffs, NY.
80. Zave P (1997) Classification of research efforts in requirements engineering. ACM Comput Surv 29(4):315-321.