Advertisement

On the Structure of Convincing Specifications

  • Haim Kilov
  • Allan Ash
Part of the The Springer International Series in Engineering and Computer Science book series (SECS, volume 523)

Abstract

Recent popular management literature suggests that when you solve problems you ought to “think outside the box”. You should not get too constrained by the (existing?) problem statement, but think about better ways of restructuring the problem so that it can be more effectively solved. In recent papers describing systems development based on rigorous business requirements, theauthors have sketched a framework for realizing solutions which encourages such feedback from the solution to the problem set. This may be successfully applied to various, even seemingly quitedifferent, businesses — including the business of creating an information management system.

Keywords

System Specification Business Operation Information Management System Business Specification Realization Relationship 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. [C97]
    B. Cohen. Set theory as a semantic framework for object-oriented modeling. In: Proceedings of the ECOOP’97 Workshop on precise semantics of object-oriented modeling techniques (Jyväskylä, Finland, 9–13 June 1997), ed. by H. Kilov, B. Rumpe, Munich University of Technology, TUM-I9725, pp. 61-68.Google Scholar
  2. [D01]
    Charles F. Dunbar. Chapters on the theory and history of banking. (Second edition, enlarged and edited by O.M.W. Sprague). G.P.Putnams Sons, New York and London, 1901.Google Scholar
  3. [D63]
    E W Dijkstra. Some meditations on advanced programming. Proceedings of the IFIP Congress 1962, North Holland, 1963, pp. 535–538.Google Scholar
  4. [D65]
    E W Dijkstra. Programming considered as a human activity. Proceedings of the IFIP Congress 1965, Spartan Books, Macmillan and Co, 1965, pp. 213–217.Google Scholar
  5. [D72]
    E.W. Dijkstra. The humble programmer. Communications of the ACM, Vol. 15, No. 10, 1972, pp. 859–866CrossRefGoogle Scholar
  6. [G97]
    Joseph Goguen. Semiotic morphisms. TR-CS97-553, University of California at San Diego, August 1997.Google Scholar
  7. [ISO95a]
    ISO/EC JTC1/SC21, Open Distributed Processing-Reference Model: Part 2: Foundations (IS 10746-2/ITU-T Recommendation X.902, 1995).Google Scholar
  8. [ISO95b]
    ISO/EC JTC1/SC21, Information Technology. Open Systems Interconnection-Management Information Services-Structure of Management Information-Part 7: General Relationship Model, 1995. ISO/IEC 10165-7.2.Google Scholar
  9. [IS095c]
    ISO/IEC JTC1/SC21. Open Distributed Processing-Reference Model: Part 3: Architecture (ITU-T Recommendation X.903 ISO/IEC 10746-3).Google Scholar
  10. [KA97]
    H. Kilov, A. Ash. How to ask questions: Handling complexity in a business specification. In: Proceedings of the OOPSLA’97 Workshop on object-oriented behavioral semantics (Atlanta, October 6th, 1997), ed. by H. Kilov, B. Rumpe, I. Simmonds, Munich University of Technology, TUM-I9737, pp. 99–114.Google Scholar
  11. [KA98]
    H. Kilov, A. Ash. An information management project: what to do when your business specification is ready. In: Proceedings of the Second ECOOP Workshop on Precise Behavioral Semantics, Brussels, July 24, 1998 (ed. by H. Kilov and B. Rumpe). Technical University of Munich, TUM-I9813, pp. 95–104.Google Scholar
  12. [KMS96]
    H. Kilov, H. Mogill, I.Simmonds. Invariants in the trenches. In: Object-oriented behavioral specifications (Ed. by H. Kilov and W. Harvey), Kluwer Academic Publishers, 1996, pp. 77–100.Google Scholar
  13. [KR94]
    Haim Kilov, James Ross. Information Modeling: an Object-oriented Approach. Prentice-Hall, Englewood Cliffs, NJ, 1994.zbMATHGoogle Scholar
  14. [KS96]
    Haim Kilov, Ian Simmonds. Business patterns: reusable abstract constructs for business specification. In: Implementing Systems for Supporting Management Decisions: Concepts, methods and experiences, Edited by Patrick Humphreys et al, Chapman and Hall, 1996, pp. 225–248.Google Scholar
  15. [KS96a]
    H. Kilov, I. Simmonds. How to correctly refine business specifications, and know it. In: Proceedings of the Fifth OOPSLA Workshop on specifications of behavioral semantics (Edited by H. Kilov and V. J. Harvey), San Jose, California, 6 October 1996, pp.57–69.Google Scholar
  16. [K99]
    H. Kilov. Business specifications: a key to successful software engineering. Prentice-Hall, 1999.Google Scholar
  17. [L97]
    Maureen linaugh-Nean. Private communication. June 1997.Google Scholar
  18. [LBR99]
    Gary T. Leavens, Albert L. Baker, and Clyde Ruby. JML: a Java Modeling Language. Behavioral Specifications in Businesses and Systems, Kluwer Academic Publishers, 1999 (ed. by H. Kilov, B. Rumpe, I. Simmonds).Google Scholar
  19. [M97]
    B. Meyer. Object-oriented software construction. Second edition. Prentice-Hall, 1997.Google Scholar
  20. [T49]
    A.M. Turing. Checking a Large Routine. Report of a Conference on High Speed Automatic Calculating Machines, University Mathematical Laboratory, Cambridge, England, June, 1949, pp. 67–69.Google Scholar

Copyright information

© Springer Science+Business Media New York 1999

Authors and Affiliations

  • Haim Kilov
    • 1
  • Allan Ash
    • 2
  1. 1.UK
  2. 2.Software Arts, IncUK

Personalised recommendations