2008 RequirementsSpecificationUsingFactOrientedModeling

From GM-RKB
(Redirected from Melli & McQuinn, 2008)
Jump to: navigation, search

Subject Headings: Fact-oriented Modeling, Requirements Specification Task, Business Requirements Document, Software Requirements Specification Document, Capability Maturity Model.

Notes

Cited By

2009

Quotes

Abstract

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.


References

  1. Petr Choteborsky, and Rik Gerrits. (2007). “Business Rules Management without a Rule Engine: Does it make sense?" In: Conference Proceedings 10th International Business Rule Forum.
  2. Stijn Goedertier, Christophe Mues, and Jan Vanthienen. (2007). “Specifying Process-Aware Access Control Rules in SBVR.” Springer Berlin / Heidelberg. Advances in Rule Interchange and Applications. Volume 4824/2007
  3. Terry Halpin. (1996). “Business rules and Object-Role modeling.” In: Database Programming and Design, 9(10).
  4. Terry Halpin: (1989). “A Logical Analysis of Information Systems: Static aspects of the data-oriented perspective.” PhD Thesis.
  5. Sjir Nijssen. (2008). “SBVR ~ Ground Facts and Fact Types in First-Order Logic.” In: Business Rules Journal, 9(1).
  6. (Ross, 2003) ⇒ Ronald G. Ross. (2003). “Principles of the Business Rule Approach." Addison-Wesley. ISBN 9780201788938
  7. Object Management Group. (2007). “Semantics of Business Vocabulary and Business Rules.”
  8. Jos Vos. (2007). “Is There Fact Orientation Life Preceding Requirements?" In: On the Move Workshops to Meaningful Internet Systems.
  9. W. M. N. Wan-Kadir, and Pericles Loucopoulos. (2004). “Relating evolving business rules to software design.” In: Journal of Systems Architecture, 50(7).
  10. International Institute of Business Analysis (IIBA). (2006). “Business Analysis Body of Knowledge (BABOK ®) v1.6.”
  11. Jerre McQuinn. (2007). “Decision Tables-From Specification to Operation.” In: Proceedings on the 10th International Conference of the Business Rule Forum.
  12. IEEE. (1998). “Recommended Practice for Software Requirements Specifications.” In: IEEE Std 830.
  13. Software Engineering Institute. (2006). “Capability Maturity Model Integration (CMMI) for Development, Version 1.2.” Technical Report CMU/SEI-2006-TR-008.
  14. Karl E. Wiegers. (1999). “Software Requirements, 2nd Edition.” Microsoft Press. ISBN:0-7356-0631-5
  15. Charalambos L. Iacovou, and Robbie Nakatsu. (2008). “A risk profile of offshore-outsourced development projects.” In: Communications of the ACM, 51(6).,


 AuthorvolumeDate ValuetitletypejournaltitleUrldoinoteyear
2008 RequirementsSpecificationUsingFactOrientedModelingGabor Melli
Jerre McQuinn
Requirements Specification Using Fact-Oriented Modeling: A Case Study and GeneralizationProceedings of Workshop on Object-Role Modelinghttp://www.gabormelli.com/Publications/2008/2008 RequirementsSpecificationUsingFactOrientedModeling 080630.pdf10.1007/978-3-540-88875-8_982008