Definition and modeling of process using object orientation

ABSTRACT

Software development processes can be represented as objects because they and the elements that compose them have attributes and operations, can be linked by relationships and have behavior and states. Therefore, this paper proposes a way to represent processes and their elements as objects. This proposal can be used to represent process models benefiting from the object orientation properties and to define tools to automate processes.

REFERENCES

• 1: Grady Booch, Object oriented design with applications, Benjamin-Cummings Publishing Co., Inc., Redwood City, CA, 1990
• 2: Taylor, D. A. (2003): Engenharia de negócios com tecnologia de objetos, Axcel Books.
• 3: OMG - Object Management Group (2005): UML - Unified modeling language: superstructure, version 2.0.
• 4: Alexander Lazovik , Marco Aiello , Mike Papazoglou, Associating assertions with business processes and monitoring their execution, Proceedings of the 2nd international conference on Service oriented computing, November 15-19, 2004, New York, NY, USA [doi>10.1145/1035167.1035182]
• 5: Lindsay, A. Downs, D., and Lunn, K. (2003): Business processes - attempts to find a definition. Information and Software Technology, vol. 45, pp. 1015--1019.
• 6: ABNT. Associação Brasileira de Normas Técnicas (1999): NBR ISO/IEC 12207:1998. Tecnologia de informação - Processos de ciclo de vida de software, Rio de Janeiro: ABNT.
• 7: Wangenheim, C. G. V., et al. (2006): Experiences on establishing software processes in small companies, Information and Software Technology, vol. 48, n. 9, p. 890--900.
• 8: Pressman, R. S. (2002): Engenharia de software, 5^a ed., Rio Janeiro: McGraw-Hill.
• 9: Lepasaar, M., and Makinen, T. (2002): Integrating software process assessment models using a process meta model. In IEMC'02 - Engineering Management Conference, IEEE International, vol. 1, pp. 224--229.
• 10: ISO/IEC - International Standardization Organization/International Engineering Consortium (1996): ISO/IEC 10746-3: open distributed processing -- reference model -- part 3: architecture.
• 11: Bertollo, G., and Falbo, R. A. (2003): Apoio automatizado à definição de processos em níveis. In II Simpósio Brasileiro de Qualidade de Software, pp. 77--91.
• 12: Sally Shlaer , Stephen J. Mellor, Object lifecycles: modeling the world in states, Yourdon Press, Upper Saddle River, NJ, 1992
• 13: Rumbaugh, J., et al. (1997): Modelagem e projeto baseado em objeto, Rio de Janeiro: Campus.
• 14: Ivar Jacobson, Object-oriented software engineering, ACM, New York, NY, 1991
• 15: Grady Booch , James Rumbaugh , Ivar Jacobson, The Unified Modeling Language user guide, Addison Wesley Longman Publishing Co., Inc., Redwood City, CA, 1999
• 16: Barnett, W. A., et al. (1994): An architecture for the virtual enterprise. In 1994 IEEE International Conference on Systems, Man, and Cybernetics, vol. 1, pp. 506--511.
• 17: Holt, J. (2006): No views in bad news. Process modelling within a framework. In IEE Seminar on Process Modelling Using UML, pp. 27--46.
• 18: Artur Caetano , Antonio Ritó Silva , José Tribolet, Using roles and business objects to model and understand business processes, Proceedings of the 2005 ACM symposium on Applied computing, March 13-17, 2005, Santa Fe, New Mexico [doi>10.1145/1066677.1066973]
• 19: OMG - Object Management Group (2005): SPEM - Software process engineering metamodeling specification, version 1.1.
• 20: Peter J. Kammer, Supporting dynamic distributed work processes with a component and event based approach, Proceedings of the 22nd international conference on Software engineering, p.710-712, June 04-11, 2000, Limerick, Ireland [doi>10.1145/337180.337596]
• 21: White, S. A. (2004): Business process management notation, version 1.0.