The meaning of requirements

Annals of Software Engineering - Tập 3 Số 1 - Trang 5-21 - 1997
Jackson, Michael1
1London, England

Tóm tắt

We use the term requirements to denote what are often called functional requirements. Requirements are located in the environment, which is distinguished from the machine to be built. A requirement is a condition over phenomena of the environment. A specification is a restricted form of requirement, providing enough information for the implementer to build the machine (by programming it) without further environment knowledge. To describe requirements appropriately we must fit our descriptions into an appropriate structure. This structure must respect the distinction between the machine and the environment, and the distinction between those environment properties that are given (indicative descriptions) and those that must be achieved by the machine (optative descriptions). Formalisation is a fundamental problem of requirements engineering. Since most environments are parts of the physical world, and therefore informal, the formalisation task is inescapable. Some techniques are discussed for tackling this task. In particular, the use of designations is explained, and the distinction between definition and assertion. By using the smallest possible set of designated terms, augmented by appropriate definitions, the developer can create a narrow bridge between the environment and its descriptions in the requirements. In this way a sufficiently faithful approximation to the informal reality can be obtained.

Từ khóa


Tài liệu tham khảo

citation_journal_title=Science of Computer Programming; citation_title=Goal-Directed Requirements Acquisition; citation_author=A. Dardenne, A. van Lamsweerde, S. Fickas; citation_volume=20; citation_issue=1; citation_publication_date=1993; citation_pages=3-50; citation_doi=10.1016/0167-6423(93)90021-G; citation_id=CR1

citation_title=Domain Modelling with Hierarchies of Alternative Viewpoints; citation_inbook_title=Proceedings of the IEEE International Symposium on Requirements Engineering; citation_publication_date=1993; citation_pages=65-72; citation_id=CR2; citation_author=S. Easterbrook; citation_publisher=IEEE Computer Society Press

citation_title=Managing Inconsistencies in an Evolving Specification; citation_inbook_title=Proceedings of the Second IEEE International Symposium on Requirements Engineering; citation_publication_date=1995; citation_pages=48-55; citation_id=CR3; citation_author=S. Easterbrook; citation_author=B. Nuseibeh; citation_publisher=IEEE Computer Society Press

citation_journal_title=ACM Transactions on Programming Languages and Systems; citation_title=Language Support for the Specification and Development of Composite Systems; citation_author=M. S. Feather; citation_volume=9; citation_issue=2; citation_publication_date=1987; citation_pages=198-234; citation_doi=10.1145/22719.22947; citation_id=CR4

citation_title=Engineering and the Mind's Eye; citation_publication_date=1992; citation_id=CR5; citation_author=E. S. Ferguson; citation_publisher=MIT Press

citation_title=Software Requirements and Specifications; citation_publication_date=1995; citation_id=CR6; citation_author=M. Jackson; citation_publisher=Addison-Wesley

citation_title=Domain Descriptions; citation_inbook_title=Proceedings of the Second IEEE International Symposium on Requirements Engineering; citation_publication_date=1993; citation_pages=56-64; citation_id=CR7; citation_author=M. Jackson; citation_author=P. Zave; citation_publisher=IEEE Computer Society Press

citation_title=Deriving Specifications from Requirements: An Example; citation_inbook_title=Proceedings of the 17th International Conference on Software Engineering; citation_publication_date=1995; citation_pages=15-24; citation_id=CR8; citation_author=M. Jackson; citation_author=P. Zave; citation_publisher=ACM and IEEE Computer Society Press

citation_journal_title=IEEE Computer; citation_title=An Investigation of the Therac-25 Accidents; citation_author=N. G. Leveson, C. S. Turner; citation_volume=26; citation_issue=7; citation_publication_date=1993; citation_pages=18-41; citation_id=CR9

citation_title=Computer-Related Risks; citation_publication_date=1995; citation_id=CR10; citation_author=P. Neumann; citation_publisher=Addison-Wesley

citation_title=Questioning Representations; citation_inbook_title=Proceedings of the Second European Conference on Computer-Supported Cooperative Work ECSCW-91; citation_publication_date=1991; citation_id=CR11; citation_author=M. Robinson; citation_author=L. Bannon; citation_publisher=Kluwer

citation_title=Goal-Directed Elaboration of Requirements for a Meeting Scheduler: Problems and Lessons Learnt; citation_inbook_title=Proceedings of the Second IEEE International Symposium on Requirements Engineering; citation_publication_date=1995; citation_pages=194-203; citation_id=CR12; citation_author=A. Van Lamsweerde; citation_author=R. Darimont; citation_author=P. Massonet; citation_publisher=IEEE Computer Society Press

Woodcock, J. and J. Davies (1996), Using Z: Specification, Refinement and Proof, Prentice-Hall.

Wordsworth, J. B. (1992), Software Development with Z: A Practical Approach to Formal Methods in Software Engineering, Addison-Wesley.

Thông tin
Thông tin xuất bản

Annals of Software Engineering

Tập 3 Số 1

5-21

Thông tin tác giả