Application of a business process modeling architecture in software development
DOI:
https://doi.org/10.5935/1809-2667.20040020Keywords:
Software development, Business process modeling, Unified process, Requirements modelingAbstract
Requirements definition in information systems projects has been done without support of more systematic methods that will guarantee development based on the business. The Unified Process presents good practices in software development, and is the basis for defining several methodologies found in the market. This study proposes activities for the different phases in business modeling and for definition requirements to be incorporated into the UP. Such activities are based on a business modeling architecture so that development will be more systematic and focused in the objectives of the organization.Downloads
References
ERIKSSON, H. E.; PENKER, M. Business modeling with UML. Estados Unidos: Wiley & Sons, 2000.
FELICIANO, A. Sistemas flexíveis de informações. São Paulo: Makron Books, 1996.
JACOBSON, I.; BOOCH, G.; RUMBAUGH, J. The Unified Software Development Process. Boston: Addison Wesley, 1999.
JOHANSSON, H. J. et al. Processos de negócio. Rio de Janeiro: Pioneira, 1995.
KALPIC, B.; BERNUS, P. Business process modelling in industry: the powerful tool in enterprise management. Computers in Industry, v. 47, n. 3, p. 299-318, march 2002.
KIRIKOVA, M. Explanatory capability of enterprise models. Data & Knowledge Engineering, v. 33, p. 119-136, 2000.
KOSANKE, K. et al. CIMOSA: enterprise engineering and integration. Computers in Industry, v. 40, p. 83-97, 1999.
LILLY, S. Use Case Pitfalls: top 10 problems from real projects using use cases. In: Proceedings of technology of object oriented languages and systems-tools, 1999.
MARSHALL, C. Enterprise modeling with UML. Estados Unidos: Addison-Wesley, 1999.
OBJECT MANAGEMENT GROUP. UML especifications. 1997. Disponível em: <http://www.rational.com/uml>. Acesso em: 10 nov. 2003.
PAULA, W. P. F. Engenharia de software: fundamentos, métodos e padrões. Rio de Janeiro: LTC, 2001.
PRESSMAN, R. S. Engenharia de software. 5 ed. Rio de Janeiro: McGraw-Hill, 2002.
SANTANDER, V. F.; CASTRO, J. F. Integrating use cases and organizacional modeling. Conferência Internacional de Engenharia de Requisitos da IEE, Anais do RE’02. Alemanha, 2002.
SCHNEIDER, G.; WINTERS, J. P. Applying use cases: a practical guide. Boston: Addison Wesley, 1998.
VERNADAT, F. B. Enterprise modeling and integration: principles and application. Londres: Chapman & Hall, 1996.
Downloads
Issue
Section
License
The authors of the manuscript submitted to Vértices, hereby represented by the corresponding author, agree to the following terms:
The authors retain the copyright and grant Vértices the right of first publication.
At the same time the work is licensed under the Creative Commons Attribution 4.0 International License, allowing third parties to copy and redistribute the material in any medium or format and to remix, transform, and build upon its content for any legal purpose, even commercially, provided the original work is properly cited.
Authors will not receive any material reward for the manuscript and Essentia Editora will make it available online in Open Access mode, through its own system or other databases.
Authors are authorized to enter into additional contracts separately for non-exclusive distribution of the version of the work published in Vértices (eg, publish in institutional repository or as book chapter), with acknowledgment of authorship and initial publication in this journal.
Authors are permitted and encouraged to disseminate and distribute the post-print (ie final draft post-refereeing) or publisher's version/PDF at online information sources (eg, in institutional repositories or on their personal page) at any time after the first publication of the article by Vértices.
Essentia Editora may make normative, orthographic and grammatical changes in the originals in order to maintain the standard language, with the final consent of the authors.
The content and opinions expressed in the manuscript are the sole responsibility of the author (s).