Network Programme - References

Benner, K.; Feather, M.; Johnson, W.L. & Zorman, L. (1992);

Utilizing Scenarios in the Software Development Process; Proc. IFIP WG 8.1 Working Conference on Information Systems Development Process; North-Holland.
Blyth, A., Chudge, J., Dobson, J. & Strens, M. (1993);

ORDIT: a new methodology to assist in the process of eliciting and modelling organisational requirements; ACM Conference on Organizational Computing Systems 1993; pp 216-223, ACM Press.
Boehm, B.; Bose, P.; Horowitz, E. & Lee, M.J. (1994);

Software Requirements as Negotiated Win Conditions; Proc. 1st International Conference on Requirements Engineering; pp 74-83, IEEE CS Press.
Boehm, B.W & Papaccio, P.N. (1988);

Understanding and Controlling Software Costs; IEEE Transactions on Software Engineering, SE4, 10, pp 1462-77.
Brown, P. (1991);

QFD: echoing the voice of the customer; AT&T Technical Journal; March-April; pp18-32.
Christel, M.; Wood, D.; Stevens, S. (1993);

AMORE: The Advanced Multimedia Organizer for Requirements Elicitation; CMU Technical Report; CMU/EI-93-TR-12.
Conklin, J. (1989);

Design Rationale and Maintainability; Proc 22nd Hawaii International Conference on System Sciences; II, pp533-539; IEEE CS Press.
Curtis, B. (1987);

Five Paradigms in the Psychology of Programming; MCC Technical Report; STP-132-87.
Dardenne, A.; Fickas, S. & van Lamsweerde, A. (1993);

Goal-directed Requirements Acqusition; Science of Computer Proigramming; 20, pp 3-50.
Davis, A.M. (1990);

Software Requirements: analysis and specification; Prentice Hall Inc.
Dorfman, M. & Thayer, R.H. (1990);

Standards, Guidelines and Examples on System and Software Requirements Engineering; IEEE CS Press Tutorial.
Fagan, M.E. (1976);

Design and Code Inspections to Reduce Errors in Program Development; IBM Systems Journal; 15, 3, pp 182-211.
Feather, M.S. (1987);

Language Support for the Specification and Development of Composite Systems, ACM Transactions on Programming Languages and Systems; 9, 2, pp 198-234.
Fenton, N.E. (1991);

Software Metrics: a rigorous approach; Chapman & Hall.
Fickas, S. & Helm, R. (1992);

Knowledge Representation and Reasoning inthe Design of Composite Systems; IEEE Transactions on Software Engineering; pp 470- 482.
Fickas, S. & Nagarajan, P. (1988);

Being Suspicious: critiquing problem specifications; Proc AAAI 88; 1, pp19-24; Morgan Kaufmann Pub.
Finkelstein, A. & Finkelstein, L.(1983);

Review of Design Methodology; Proc. IEE,130 ptA,4, pp213-222.
Finkelstein, A. & Kramer, J. (1991);

TARA: Tool Assisted Requirements Analysis; Conceptual Modelling, Databases & CASE: an integrated view of information systems development; [Eds] Loucopoulos, P. & Zicari, R.; Addison-Wesley.
Finkelstein, A. (1992);

Reviewing and Correcting Specifications; Instructional Science, 21, pp183-198.
Finkelstein, A.; Gabbay, D.; Hunter, A.; Kramer, J.; & Nuseibeh, B. (1994);

Inconsistency Handling in Multiperspective Specifications; IEEE Transactions on Software Engineering; 20, 8, pp 569-578.
Garlan, D. (1989);

The Role of Formalized Domain-Specific Software Frameworks; Proc. 5th International Software Process Workshop; IEEE CS Press
Goguen, J. & Linde, C. (1993);

Techniques for Requirements Elicitation; Proc. IEEE International Symposium on Requirements Engineering; pp 152-164, IEEE CS Press.
Gotel, O. & Finkelstein, A. (1994);

An Analysis of the Requirements Traceability Problem; Proc. International Conference on Requirements Engineering; pp 94-101; IEEE CS Press.
Greenspan, S.; Mylopoulos, J. & Borgida, A. (1994);

On Formal Requirements Modelling Languages: RML revisited; Proc. 16th International Conference on Software Engineering; pp 135-147, IEEE CS Press
Humphrey, W.S. (1988);

Characterizing the Software Process: a maturity framework; IEEE Software; 5, 2, pp 73-79.
Humphrey. W.S.; Kitson, D.H. & Kasse, T.C. (1989);

The State of Software Engineering Practice: a preliminary report; Proc. 11th International Conference on Software Engineering; pp 277-288, IEEE CS Press.
IWSSD (1993);

Proc. of the 7th International Workshop on Software Specification and Design; IEEE CS Press.
Jackson, M. & Zave, P. (1993);

Domain Descriptions; Proc. IEEE International Symposium on Requirements Engineering; pp 56-64, IEEE CS Press.
Jacobsen, I; Christerson, M.; Jonsson, P. & Overgaard, G. (1992);

Object-Oriented Software Engineering: a use-case driven approach; Addison-Wesley.
James, L. (1994);

Practical Experience in Automatic Requirements Elicitation: the real issues; Proc. of Workshop on Requirements Elicitation for Software-based Systems (RESS); University of Keele, UK.
Johnson, P. (1992);

Human Computer Interaction: psychology, task analysis and software engineering; McGraw-Hill.
Johnson, P. (1994);

An Instrumented Approach to Improving Software Quality through Formal Technical Review; Proc. 16th International Conference on Software Engineering; pp113-122, IEEE CS Press.
Jones, M. & Brooks, L. (1994);

Addressing Organisational Context in Requirements Analysis Using Cognitive Mapping; Proc. of Workshop on Requirements Elicitation for Software-based Systems (RESS); University of Keele, UK.
Kaplan, S.M. et al (1992);

Supporting Collaborative Software Development with Conversation Builder; Proc. ACM SDE; pp 11-20.
Kotonya, G. & Sommerville, I (1992);

Viewpoints for Requirements Definition; Software Engineering Journal; 7, 6, pp 375-387.
Lee, J. & Lai, K-Y. (1991);

What's in Design Rationale?; Human-Computer Interaction; 6, 3-4, pp 251-280.
Lim, K.Y; Long, J.B. & Silcock, N. (1990);

Requirements, Research and Strategy for Integrating Human Factors with Structured Analysis and Design Methods: The Case of the Jackson System Development Method; [In] Contemporary Ergonomics 1990; Proc. Ergonomics Society Conference; Taylor and Francis.
Lubars, M. & Potts, C. & Richter, C. (1993);

Developing Initial OOA Models; Proc. 15th International Conference on Software Engineering; IEEE CS Press.
Luqi (1992);

Computer-aided Prototyping for a Command-and-Control System Using CAPS; IEEE Software; 9, 1, pp 56-67.
Macaulay, L. (1993);

Requirements Capture as a Cooperative Activity; Proc. IEEE International Symposium on Requirements Engineering; pp 174-181, IEEE CS Press.
Maiden, N. & Sutcliffe, A. (1993);

Exploiting Reuseable Specifications Through Analogy; Communications of the ACM; 35, 4, pp 55-64.
Porter, A.A. & Votta, L.G. (1994);

An Experiment to Assess Different Defect Detection Methods for Software Requirements Inspection; Proc. 16th International Conference on Software Engineering; pp 103-112, IEEE CS Press.
Potts, C.; Takahashi, K.; Anton, A. (1994);

Inquiry-Based Scenario Analysis of System Requirements; Georgia Tech Technical Report; GIT-CC-94-14.
Reubenstein, H. & Waters, R. (1989);

The Requirements Apprentice: an initial scenario; Proc 5th International Workshop on Software Specification & Design; pp 211-218, IEEE CS Press.
Robinson, W. (1990);

Negotiation Behaviour During Requirements Specification; Proc. 12th International Conference on Software Engineering; pp 268-276, IEEE CS Press.
Rumbaugh, J.; Blaha, W.; Premerlani, F. & Lorenson, W. (1991);

Object-Oriented Modelling and Design; Prentice-Hall Inc.
Scharer, L. (1985);

Pinpointing Requirements; Datamation; April, 1981; pp 139-151.
Thayer, R.H. & Dorfman, M. (1990);

System and Software Requirements Engineering; IEEE CS Press Tutorial; IEEE CS Press.
Yadav, S.B. (1983);

Determining an Organisations Information Requirements: a state-of-the-art survey; Database; 3-20.
Zave, P. (1994);

Call for Papers and Associated Classification Scheme; IEEE International Symposium on Requirements Engineering 1995.

Back to title

Previous section

Contents page

Last up-date: 30 July 1998