Towards Use Case and Conceptual Models through Business Modeling
A guide to requirements modeling is presented in this paper, in which use cases and the conceptual model are directly obtained from a business modeling based on UML activity diagrams. After determining the business processes of the organization, and describing their workflows by means of activity diagrams, use cases are elicited and structured starting from the activities of each process, while the concepts of the conceptual model are obtained from the data that flow between activities. Furthermore, business rules are identified and included in a glossary, as part of the data and activities specification. One notable aspect of our proposal is that use case and conceptual modeling are performed at the same time, thus making the identification and specification of suitable use cases easier. Both use case and conceptual modeling belong to the requirements analysis phase, which is part of a complete process model on whose definition we are currently working. This process is being experimented in a mediumsized organism of a Regional Public Administration.
Unable to display preview. Download preview PDF.
- 1.Booch, G., Rumbaugh, J., Jacobson, I.: The Unified Modeling Language User Guide. Addison-Wesley (1999)Google Scholar
- 2.Ceri, S., Fraternalli, P.: Designing Database Applications With Objects and Rules. The IDEA Methodology. Addison-Wesley (1997)Google Scholar
- 4.Coleman, D.: A Use Case Template: Draft for discussion (1998) http://www.bredemeyer.com/use_case.pdf
- 6.Jacobson, I., Booch, G. Rumbaugh, J.: The Unified Software Development Process. Addison-Wesley Longman, Inc. (1999)Google Scholar
- 7.Korson, T.: Misuse of Use Cases. (1998) http://software-architects.com/publications/korson/korson9803om.htm.
- 8.Korson, T.: Constructing Useful Use Cases (1999) http://software-architects.com/publications/korson/usecase3
- 9.Martin, J. Odell, J.J.: Object-Oriented Methods: A Foundation. Prentice Hall. (1997)Google Scholar
- 10.Ortín, M.J., García Molina, J., Martínez, A., Pellicer, A.: Combining OOram and IDEA for Information Systems Modeling. Technical Report TR-01-00. (December 1998)Google Scholar
- 11.Ortín, M.J., García Molina, J.: Role-Based Modeling with UML. IV Jornadas de Ingeniería del Software y Bases de Datos. Cáceres, Spain (1999)Google Scholar
- 12.Reenskaug, T.: Working with Objects: the OOram Software Engineering Method. Addison-Wesley / Manning Publications (1996)Google Scholar
- 13.Reenskaug, T.: Working with Objects: a Three-Model Architecture for the Analysis of Information Systems. JOOP vol. 10 no. 2 (May 1997) 22–30Google Scholar
- 14.Whitenack, B.: RAPPeL: A Requirements Analysis Process Pattern Language for Object-Oriented Development. In: Coplien, J.O., Schmidt, D.C. (eds.): Pattern Languages of Program Design. Addison-Wesley (1995) 259–291Google Scholar