Requirements Specification Using Fact-Oriented Modeling: A Case Study and Generalization

  • Gabor Melli
  • Jerre McQuinn
Part of the Lecture Notes in Computer Science book series (LNCS, volume 5333)


We present a case study of the application of fact-oriented modeling to the capture and management of requirement specifications for the introduction of an information technology solution within Microsoft. The delivered solution involves automation and centralization of information about relationships between Microsoft product offerings. The methodology contributed to the project’s fast turn-around time and high quality deliverable largely due to the clarity, completeness and traceability of business concepts and individual specification statements. We conclude with a generalization of the methodology used.


Fact-oriented modeling Case Study 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Choteborsky, P., Gerrits, R.: Business Rules Management without a Rule Engine: Does it make sense? In: Proceedings of 10th International Business Rule Forum Conference (2007)Google Scholar
  2. 2.
    Goedertier, S., Mues, C., Vanthienen, J.: Specifying Process-Aware Access Control Rules in SBVR. In: Paschke, A., Biletskiy, Y. (eds.) RuleML 2007. LNCS, vol. 4824, pp. 39–52. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  3. 3.
    Halpin, T.: Business rules and Object-Role modeling. Database Programming and Design 9(10), 66–72 (1996)Google Scholar
  4. 4.
    Halpin, T.: A Logical Analysis of Information Systems: Static aspects of the data-oriented perspective. PhD Thesis (1989)Google Scholar
  5. 5.
    Nijssen, S.: SBVR ~ Ground Facts and Fact Types in First-Order Logic. Business Rules Journal 9(1) (January 2008)Google Scholar
  6. 6.
    Ross, R.G.: Principles of the Business Rule Approach. Addison-Wesley, Reading (2003)Google Scholar
  7. 7.
    Object Management Group: Semantics of Business Vocabulary and Business Rules (2007)Google Scholar
  8. 8.
    Vos, J.: Is There Fact Orientation Life Preceding Requirements? In: Meersman, R., Tari, Z., Herrero, P. (eds.) OTM-WS 2007, Part I. LNCS, vol. 4805, pp. 688–698. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  9. 9.
    Wan-Kadir, W.M.N., Loucopoulos, P.: Relating evolving business rules to software design. Journal of Systems Architecture 50(7), 367–382 (2004)CrossRefGoogle Scholar
  10. 10.
    International Institute of Business Analysis (IIBA): Business Analysis Body of Knowledge (BABOK ®) v1.6 (2006)Google Scholar
  11. 11.
    McQuinn, J.: Decision Tables-From Specification to Operation. Proceedings of 10th International Business Rule Forum Conference (2007)Google Scholar
  12. 12.
    IEEE: Recommended Practice for Software Requirements Specifications. IEEE Std 830-1998 (1998)Google Scholar
  13. 13.
    Software Engineering Institute: Capability Maturity Model Integration (CMMI) for Development, Version 1.2. Technical Report CMU/SEI-2006-TR-008 (2006)Google Scholar
  14. 14.
    Wiegers, K.E.: Software Requirements, 2nd edn. Microsoft Press (1999) ISBN 0-7356-0631-5 Google Scholar
  15. 15.
    Iacovou, C.L., Nakatsu, R.: A risk profile of offshore-outsourced development projects. Communications of the ACM 51(6) (June 2008)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2008

Authors and Affiliations

  • Gabor Melli
    • 1
  • Jerre McQuinn
    • 2
  1. 1.Prediction Works, Inc.USA
  2. 2.Microsoft CorporationUSA

Personalised recommendations