Software requirements & specifications: a lexicon of practice, principles and prejudices
Software requirements & specifications: a lexicon of practice, principles and prejudices
Functional documents for computer systems
Science of Computer Programming
Four dark corners of requirements engineering
ACM Transactions on Software Engineering and Methodology (TOSEM)
Domain modeling-based software engineering: a formal approach
Domain modeling-based software engineering: a formal approach
Requirements analysis and system design: developing information systems with UML
Requirements analysis and system design: developing information systems with UML
Problem frames: analyzing and structuring software development problems
Problem frames: analyzing and structuring software development problems
Systems Analysis and Design Methods 5e
Systems Analysis and Design Methods 5e
Requirements, domain and specifications: a viewpoint-based approach to requirements engineering
Proceedings of the 24th International Conference on Software Engineering
Annals of Software Engineering
Elements underlying the specification of requirements
Annals of Software Engineering
A Reference Model for Requirements and Specifications
IEEE Software
An ontology-guided process for developing problem frame specification: an example
Proceedings of the 3rd international workshop on Applications and advances of problem frames
An ontology of problem frames for guiding problem frame specification
KSEM'07 Proceedings of the 2nd international conference on Knowledge science, engineering and management
An approach for selecting implementation strategies of non-functional requirements
Proceedings of the Fourth Asia-Pacific Symposium on Internetware
| Hi-index | 0.01 |
In this paper, we propose a conceptual description schema based on the Problem Frames (PF) approach, which treats environment as a first-class concept. Requirements are defined as problem descriptions in terms of the environment model. Thus, knowledge about the environment can be used to facilitate the derivation of software specifications from requirements. Heuristic rules that help structuring software problems are given. Major idea of the proposed approach is illustrated with a simple real world example.