Bibliographic Item (1.0)

1. Michael A Jackson
2. Problem Frames: Analyzing and structuring software development problems
3. Addison Wesley 2001 ISBN 0-201-59627-X QA76.76 D47 J32 2001
4. =ESSAY PROBLEM ANALYSIS REQUIREMENTS REALITIES SYSTEMS METHODS
5. An in depth attempt at deconfusing a critical part of software development: understanding the problems and planning how to tackle them. Includes detailed references to several methods and some classic examples from the literature,
6. Five basic problem frames Required Behavior, Commanded Behavior, Information Display, Simple Workpieces, Transformation.
7. Plus many variants and compositions,
8. Classification of domains: lexical(symbolic, formal, data like), causal (contolable), biddable( may not follow commands...)
9. Domains are collections of phenomena: events, entities, values.
10. Connected by shared phenomena.
11. Good discussion of the concerns that arise with different types of problems and domains. For example: Allowing for messages that don't make it through mail to the recipient.
12. Many examples. New Glossary, Careful definitions of what the diagrams mean,
13. Diagrams show domains, conections, and requirements.
14. Distinguishes: the machine, the parts of reality, the requirements, the existence of parts of reality that a symbolic descriptions, ...
15. Some advice for decomposing a problem into subproblems -- for example introducing a designed model of a part of reality and a machine to keep it synchronized, plus other machines to meet other requirements.
16. Notes problems of synchronizing the different machines that solve different subproblems.
17. Introduces the idea of a formal/lexical/symbolic domain which specifies requirements to be imposed on another doamin by the machine.
18. Good discussion of problems caused by dome doamins not being 100% under control and a suggestion of a special type of problem of auditting compliance.

Search for a specific bibliographic item by name.

To see the complete bibliography (1Mb+) select:[Bibliography]