Requirements engineering (third edition)

Requirements Engineering (Third Edition)

Volumn , Issue , 2011, Pages 1-207

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

^a UNIVERSITY OF ULSTER   (United Kingdom)

^b Gate House   (United Kingdom)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84892297628     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/978-1-84996-405-0     Document Type: Book

References (66)

1. Alderson A, Hull M E C, Jackson K and Griffiths LE (1998) Method Engineering for Industrial Real-Timeand Embedded Systems. Information and Software Technology, 40:443-454.
2. Andriole SJ (1996) Managing Systems Requirements: Methods, Tools and Cases. New York, McGraw-Hill.
3. Babich W (1986) Software Configuration Management - Coordination for Team Productivity. Boston, MA, Addison-Wesley.
4. Bernstein P (1996) Against the Gods - the Remarkable Story of Risk. New York, Wiley.
5. Boehm B (1981) Software Engineering Economics. New York, Prentice-Hall.
6. Booch G (1994) Object-oriented Design with Applications. Redwood City, California, Benjamin Cummins.
7. Brown AW, Earl AN et al. (1992) Software Engineering Environments. London, McGraw-Hill.
8. Budgen D (1994) Software Design. Boston, MA, Addison-Wesley.
9. ® for Development, Version 1.2, CMMI-DEV, Pitsburg, PA 15213-3890
10. Chaochen Z, Hoare C A R, Ravn AP (1991) A Calculus of Durations. Information Processing Letter, 40(5):269-276.
11. Chen, Peter (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
12. Clark KB and Fujimoto T (1991) Product Development Performance. Harvard Business School.
13. Coad P and Yourdon E (1991a) Object-Oriented Analysis. Englewood Cliffs, NJ, Prentice-Hall.
14. Coad P and Yourdon E (1991b) Object-Oriented Design. Englewood Cliffs, NJ, Prentice-Hall.
15. Cooper RG (1993) Winning at New Products. Reading, MA, Addison Wesley.
16. Crosby PB (1979) Quality Is Free. New York, McGraw-Hill.
17. Crosby PB (1984) Quality Without Tears. New York, New American Library.
18. Darke P, Shanks GG (1947) User Viewpoint Modelling: Understanding and Representing User Viewpoints During Requirements Definition.. Information Systems Journal 7(3):213-240.
19. Davis AM (1993) Software Requirements: Objects, Functions and States. Englewood Cliffs, NJ, Prentice-Hall.
20. De Grace P (1993) The Olduvai Imperative: CASE and the State of Software Engineering Practice. Englewood Cliffs, NJ, Prentice-Hall.
21. De Marco T (1978) Structured Analysis and System Specification. New York, Yourdon.
22. De Marco T (1982) Controlling Software Projects. Englewood Cliffs, NJ, Yourdon Press.
23. De Marco T and Lister T (1987) Peopleware - Productive Projects and Teams. New York, Dorset House.
24. Easterbrook S and Nuseibeh B (1996) Using Viewpoints for Inconsistency Management. Software Engineering Journal, 11(1):31-43.
25. Finkelstein A, Kramer J, Nuseibeh B and Goedicke M (1992) Viewpoints: A Framework for Integrating Multiple Perspectives in Systems Development. International Journal of Software Engineering and Knowledge Engineering, 2(10):31-58.
26. Fowler M and Scott K (1997) UML Distilled: Applying the Standard Object Modeling Language. Reading, MA, Addison-Wesley.
27. Gilb T (1988) Principles of Software Engineering Management. Reading, MA, Addison-Wesley.
28. Gilb T (2005) Competitive Engineering: A Handbook for Systems Engineering, Requirements Engineering and Software Engineering Management Using Planguage.. Oxford, Elsevier Butterworth-Heinemann
29. Gorchels L (1997) The Product Manager's Handbook. Lincolnwood, IL, NTC Business Books.
30. Gotel O C Z and Finkelstein A C W (1995) Contribution Structures. Proceedings RE'95. York, UK, IEEE Press.
31. Harel D (1987) Statecharts: A Visual Formalism for Complex Systems. Science of Computer Programming, 8:231-274.
32. Hull M E C, Taylor PS, Hanna J R P and Millar RJ (2002) Software Development Processes - An Assessment. Information and Software Technology, 44(1):1-12.
33. Humphrey WM (1989) Managing the Software Process. Boston, MA, Addison-Wesley.
34. IEEE STD 1220-1998 (1998) Standard for Application and Management of the Systems Engineering Process. New York, NY, IEEE.
35. Jackson M (1995) Software Requirements & Specifications: a Lexicon of Practice, Principles and Prejudices. New York, NY, Addison-Wesley.
36. Jacobsen I and Christerson M et al (1993) Object-Oriented Software Engineering. Wokingham, Addison-Wesley.
37. Kotonya G and Sommerville I (1996) Requirements Engineering with Viewpoints. Software Engineering Journal, 11(1):5-11.
38. Kotonya G and Sommerville I (1998) Requirements Engineering: Processes and Techniques. Chichester, Wiley.
39. Leite J C P and Freeman PA (1991) Requirements Validation Through Viewpoint Resolution. Transactions of Software Engineering, 12(2):1253-1269.
40. Loucopulos P and Karakostas V (1995) Systems Requirements Engineering. New York, NY, McGraw-Hill.
41. Mazza C et al (1994) ESA - Software Engineering Standards. Prentice-Hall.
42. Monroe RT, Kompanek A, Metlon R, and Garlan D (1997) Architectural Styles, Design Patterns, and Objects. IEEE Software.
43. Mumford E (1989) User Participation in a Changing Environment - Why We Need IT. In: Participation in Systems Development. Ed. K Knight. London, Kogan Page.
44. Nuseibeh B, Kramer J and Finkelstein A (1994) A Framework for Expressing the Relationships Between Multiple Views in Requirements Specification. Transactions of Software Engineering, 20(10):760-773.
45. Oliver DW, Kelliher TP and Keegan JG (1997) Engineering Complex Systems with Models and Objects. New York, McGraw-Hill.
46. OMG (2003) The Unified Modelling Language Version 2, www.omg.org
47. Page-Jones M (1980 The Practical Guide to Structured Systems. New York, Yourdon Press.
48. Perrow C (1984) Normal Accidents. Basic Books.
49. Petroski H (1982) To Engineer is Human - the Role of Failure in Successful Design. New York, St Martin's Press.
50. Petroski H (1996) Invention by Design: How Engineers Get from Thought to Thing. Harvard University Press.
51. Poots C, Takahashi K et al (1994) Inquiry-based Requirements Analysis. IEEE Software, 11(2):21-32.
52. Pressman RS (1997) Software Engineering: A Practitioner's Approach. New York, NY, McGraw-Hill.
53. Ross DT (1977) Structured Analysis (SA): A Language for Communicating Ideas. IEEE Transactions on Software Engineering, 3(1):16-34.
54. Ross DT (1985) Applications and Extensions of SADT. IEEE Computer, 18(4):25-34.
55. Ross DT and Schoman KE (1977) Structured Analysis for Requirements Definition. IEEE Transactions on Software Engineering, 3(1):6-15.
56. Rumbaugh J and Blaha M et al (1991) Object Modeling and Design. Englewood Cliffs, NJ, Prentice-Hall.
57. Rumbaugh J, Blaha M, Premerlani W, Eddy F and Lorenzen W (1991) Object-Oriented Modeling and Design. Prentice-Hall.
58. Shlaer S and Mellor SJ (1991) Object Life Cycles - Modeling the World in States. Yourdon Press.
59. Shlaer S and Mellor SJ (1998) Object-Oriented Systems Analysis. Englewood Cliffs NJ, Prentice-Hall.
60. Software Engineering Institute (Carnegie-Mellon) (1991) Capability Maturity Model for Software. Tech. Report CMU/SEI-91-TR-24.
61. Sommervile I (1996) Software Engineering. Wokingham, Addison-Wesley.
62. Sommervile I and Sawyer P (1997) Requirements Engineering: A Good Practice Guide. Chichester, Wileyons.
63. Spivey JM (1989) The Z Notation: A Reference Manual. Englewood Cliffs, NJ, Prentice-Hall.
64. Stevens R, Brook P, Jackson K and Arnold S (1998) Systems Engineering: Coping with Complexity. Prentice-Hall Europe.
65. Yourdon EN (1990) Modern Structured Analysis. Englewood Cliffs, NJ, Prentice-Hall.
66. Zave P (1997) Classification of Research Efforts in Requirements Engineering. ACM Computing Surveys, 29(4):315-321.