Enabling Problem Domain Knowledge Transformation during Object Oriented Software Development
Nowadays one the most desirable characteristics of software development process is a high speed of development. However, in many cases the speed of software development is hindered by problems of knowledge acquisition and transformation. Sometimes software developers focus on their tacit knowledge and do not use proper knowledge acquisition and representation techniques for problem domain and requirements description. In that case developers take a known risk to fail with a final product, yet they hasten the process of software development. However, such a risk shall be avoided in large, complex, and expensive software projects.
KeywordsSoftware Development Problem Domain Class Diagram Business Process Model Software Development Process
Unable to display preview. Download preview PDF.
- 1.I. Jacobson, G. Booch, J. Rumbaugh, The Unified Software Development Process, Addison-Wesley, 1999.Google Scholar
- 2.Microsoft Solution Framework“. Available at http://www.erigami.com/development.html.
- 3.B. Henderson-Sellers, The OPEN - Mentor Methodology, Object Magazine, 1998.Google Scholar
- 4.O. Nikiforova, General Framework for Object-Oriented Software Development Process, Scientific Proceedings of Riga Technical University, Series - Computer Science, Applied Computer Systems, 13 vol., 2002.Google Scholar
- 5.OMG Unified Modelling Language Specification, Version 1. 3, June 1999.Google Scholar
- 6.O. Ivasiuta (since 2001 - O. Nikiforova), Comparison Methodology of Software Development Means, PhD Thesis, Riga Technical University, Latvia, 2001.Google Scholar
- 7.Rational Rose, Rational Corporation web-site - http://www.rational.com.
- 8.M. Kirikova, Towards completeness of business models, in: Information Modelling and Knowledge Bases X H. Jaakola et al., eds., IOS Press, 1999, pp. 42–54.Google Scholar
- 9.M. Kirikova, Consistency of Information in Requirements Engineering, in: Information Modelling and Knowledge bases IX, P-J. Charrel, H.Jaakola, Hkangassalo, E Kawaguchi, eds., IOS Press, Amsterdam, Berlin, Tokyo,Washigton, DC, 1998, pp. 192–205.Google Scholar
- T. Quatrany, Visual Modeling with Rational Rose 2000 and UML,Second Edition, Addison-Wesley, 2000.Google Scholar
- 11.J. Rumbaugh, Getting started: Using Use-cases to Capture Requirements, Journal of Object Oriented Programming, Sept., 1994, 8–11.Google Scholar
- 12.L. Mathiassen et al., Object Oriented Analysis & Design, Forlaget, 2000.Google Scholar
- 13.Cr. Latman, Applying UML and Patterns: An Introduction to Object Oriented Analysis and Design, Prentice Hall PTR, 1998.Google Scholar
- 14.M. Fawler, Analysis Patterns: Reusable Software Models, Addison-Wesley, 1996.Google Scholar
- 15.J. Martin and J. Odell, Object Oriented Methods: A Foundation, Prentice Hall, 1995.Google Scholar
- 16.J. Rumbaugh, Models Through the Development Process, Journal of Object Oriented Programming, May 1997.Google Scholar
- 17.R. Abbot, Program Design by Informal English Descriptions, Communications of the ACM, Vol. 26 (11), 1983.Google Scholar
- 18.D. Leffingwell and D. Widrig, Managing Software Requirements: A Unified approach, Addison-Wesley, 2000.Google Scholar
- 19.J. Bubenk jr. and M. Kirikova, Improving the quality of Requirements Specification by Enterprise Modelling, in: Perspectives on Business Modelling: Understanding and Changing Organistions, A.G. Nilsson et al., eds., Springer-Verlag, 1999, pp. 243–268.Google Scholar
- 20.J. R. Anderson, Cognitive Psychology and Its Implications, W.H. Freeman and Company, New York, 1995.Google Scholar
- 21.M. Kirikova, Modelling the boundaries of workspace: A business process perspective, in: Information Modelling and Knowledge Bases XIII, H. Kangassalo, H. Jaakkola, E. Kawaguchi, T. Welzer, eds., IOS Press, Ohmsha, Amsterdam, Berlin, Oxford, Tokyo, Washington, DC, 2002, pp. 266–278.Google Scholar
- 22.M. Kirikova, Business Modelling and Use Cases in Requirements Engineering, in: Information Modelling and Knowledge Bases XII, H. Jaakkola, H. Kangassalo E. Kawaguchi, eds., IOS Press, Ohmsha, Amsterdam, Berlin, Oxford, Tokyo, Washington, DC, 2001, pp. 410–420.Google Scholar