Michael Jackson
- Abadi 93.Martin Abadi and Leslie Lampom, Com-posing specifications; ACM TOPLAS Volume 15 Number 1 pp73-132, January 1993. Google Scholar
Digital Library
- Dubois 89.Eric Dubois; A Logic of Action for Sup-porting Goal-Oriented Elaboration of Require-ments; in Proc IWSSD-5; IEEE CS Press, 1989. Google ScholarDigital Library
- Feather 87.M S Feather; Language Support for the Specification and Development of Composite Systems; ACM TOPLAS Volume 9 Number 2 pp198-234, April 1987. Google ScholarDigital Library
- Feather 91.Martin S Feather, Stephen Fickas, and B Robert Heti, Composite System Design the Good News and the Bad News; in Proc 6th RADC KBSE Conference; IEEE CS Press, 1992,Google Scholar
- Feather 94.Martin S Feather; Towards a Deriva-tional Style of Distributed System Design - An Examplcx Automated Software Engineering Vol-ume 1 Number 1 pages 31-60, March 1994.Google Scholar
- Jackson 92.Michael Jackson and Pamela Zav% Do-main Descriptions; in Proc RE'93; IEEE CS Press, 1992.Google Scholar
- Jackson 94.M A Jacksom Software Development Methcxl in A Classical Mind Essays in Honour of C A R Hoar& A W Roscoe et Prentice-Hall International 1994. Google ScholarDigital Library
- Johnson 88.W Lewis Johnsom Deriving Specifica-tions from Requirements; in Proc ICSE- 10; IEEE CS Press, 1988. Google ScholarDigital Library
- Morgan 90.Carroll Morgaw Programming from Specifications; Prentice-Hall International 1990. Google ScholarDigital Library
- Mostow 83.Jack Mostow; A Problem-solver for Making Advice Operationati in Proc AAAI-83, pages 279-283; William Kaufmann Inc, 1983.Google Scholar
- Zave 93.Pamela Zave and Michael Jacksom Con-junction as Composition ACM Transactions on Sofiware Engineering and Methodology, Volume 2 Number 4 pages 379-411, October 1993. Google ScholarDigital Library
Index Terms
- Deriving specifications from requirements: an example
Recommendations
Semantic analysis of functional and non-functional requirements in software requirements specifications
Canadian AI'12: Proceedings of the 25th Canadian conference on Advances in Artificial IntelligenceSoftware Requirements Specifications (SRS) documents are important artifacts in the software industry. A SRS contains all the requirements specifications for a software system, either as functional requirements (FR) or non-functional requirements (NFR). ...
Requirements, domain and specifications: a viewpoint-based approach to requirements engineering
ICSE '02: Proceedings of the 24th International Conference on Software EngineeringViewpoint-based Requirements Engineering (VBRE) is based on the fact that there is a multiplicity of stakeholders that take part in any requirements process. This will inevitably lead to conflicts and inconsistencies that, if adequately managed, can be ...
Deriving security requirements from crosscutting threat descriptions
AOSD '04: Proceedings of the 3rd international conference on Aspect-oriented software developmentIt is generally accepted that early determination of the stakeholder requirements assists in the development of systems that better meet the needs of those stakeholders. General security requirements frustrate this goal because it is difficult to ...
Comments