Representing knowledge in requirements engineering: An empirical study of what software engineers need to know

Proceedings of the IEEE International Conference on Requirements Engineering

Volumn , Issue , 1993, Pages 273-276

  Kuwana, Eiji ^a   Herbsleb, James D ^b  

^a NTT CORPORATION   (Japan)

^b UNIVERSITY OF MICHIGAN   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

ELECTRICAL ENGINEERING; SOFTWARE ENGINEERING;

DEVELOPMENT PROCESS; EMPIRICAL PREDICTIONS; EMPIRICAL STUDIES; PRELIMINARY DESIGN; SOFTWARE REQUIREMENTS;

REQUIREMENTS ENGINEERING;

EID: 84954664423     PISSN: 1090705X     EISSN: 23326441     Source Type: Conference Proceeding    
DOI: 10.1109/ISRE.1993.324846     Document Type: Conference Paper

References (18)

1. Coad, P. & Yourdon, E. (1990). Object-oriented analysis. Englewood Cliffs, NJ: Yourdon Press.
2. Conklin, E. J., & Yakemovic, K. C. B. (1991). A process-oriented approach to design rationale. Human-Computer Interaction. 6, 357-391.
3. Conklin, J., & Begeman, M. L. (1988). gIBIS: A hypertext tool for exploratory policy discussion. In Conference on CSCW88. (pp. 140-152).
4. Curtis, B., Krasner, H., Iscoe, N. (1988) A field study of the software design process for large systems. Communications of the ACM. 31 (pp. 1258-1287)
5. Davis, A. M. (1990). Software requirements: Analysis and specification. Englewood Cliffs, NJ: Prentice Hall.
6. Ghezzi, C., Jazayeri, M., & Mandrioli, D. (1991). Fundamentals of software engineering. Englewood Cliffs, NJ: Prentice Hall.
7. IEEE (1984). Guide for software requirements specifications No. Std 830-1984).
8. IEEE (1987). Recommended practice for software design despciptions No. Std 1016-1987).
9. Jacobson, I. (1992). Object-Oriented Software Engineering. Addison-Wesley.
10. Lee, J. (1990). SIBYL: A tool for managing group design. In CSCW '90. (pp. 79-92).
11. Lee, J., & Lai, K.-Y. (1991). What's in design rationale. Human-Computer Interaction. 6, 251-280.
12. Leite, J. C, & Freeman, P. A. (1991). Requirements validation through viewpoint resolution. IEEE Trans, on Software Engineering. 17. 1253-1269.
13. MacLean, A.,Young, R. M.,Bellotti, V. M. E., & Moran, T. P. (1991). Questions, options, and criteria: Elements of design space analysis. Human-Computer Interaction. 6, 201-250.
14. MacLean, A., Young, R. M., & Moran, T. P. (1989). Design rationale: The argument behind the artifact In Proc. of CHI'89. (pp. 247-252).
15. Moran, T., & Carroll, J. (Ed.), (in press). Design Rationale.
16. Potts, C, Bruns, G (1987). Recording the Reasons for Design Decisions, MCC Technical Report STP-304-87
17. Ross, D. T., & Schoman, K. E. (1977). Structured analysis for requirements definition. IEEE Transactions on Software Engineering. 3. 6-15.
18. Yourdon, E. (1989). Modem structured analysis. Englewood Cliffs, NJ: Yourdon Press.