Business modeling using the Rational Unified Process (RUP) methodology
Summary
The Business Modeling, which is carried out with greater emphasis on the conceptual phase of the Rational Unified Process (RUP) methodology, aims to understand the structure, the dynamics of the organization, current problems, identify possible improvements and understand the processes. It uses the Business Use Case Model to describe the business processes and customers, the Business Object Model to describe each Business Use Case with the Workers, as well as the Activity and Class Diagrams. It is of utmost importance to choose the right methodology, as well as the right implementation tools, that is why the Rational Unified Process (RUP) methodology based on Business modeling provides us with all the bases to lead software development to success.
The Business Modeling Methodology Using the Rational Unified Process (RUP)
Summary
The Business Modeling which is done with greater emphasis on the conceptual phase of the methodology Rational Unified Process (RUP) aims to understand the structure, organizational dynamics, current issues, identify improvements and understand the processes. Use the Model Business Use Cases to describe business processes and customers, the Business Object Model to describe each use case with Business Workers also use Activity Diagrams and Class. It is important to choose the right methodology and the implementation of appropriate tools, which is why the methodology Rational Unified Process (RUP) based modeling Business provides all the bases for the successful development of software.
Introduction
Many organizations want the software development projects that they need to implement to be successful, which is why they are implementing mechanisms that allow them to achieve these objectives. An exhaustive analysis was carried out on what makes software development projects fail, obtaining as a result that the most important failures lie in the lack of an adequate project management methodology but focused on the software development industry (Torres 2010).
The objective of this review is to highlight business modeling for the successful execution of intensive software development projects using the Unified Software Development Process (RUP) methodology, presenting a prescriptive approach to standardize the best practices of software engineering..
Background
The most important antecedent is located in 1967 with the Ericsson Methodology (Ericsson Approach) elaborated by Ivar Jacobson, a development approach based on components, which introduced the concept of Use Case. Between 1987 and 1995 Jacobson founded the company Objectory AB and launches the Objectory (short for Object Factory) development process.
Later in 1995 Rational
Software Corporation acquires Objectory AB and between 1995 and 1997 the Rational Objectory Process (ROP) is developed from Objectory 3.8 and the Rational Approach (Rational Approach) adopting UML (Unified Modeling Language) as modeling language. Since then, led by Grady Booch, Ivar Jacobson and James Rumbaugh, Rational Software developed and incorporated various elements to expand ROP, especially the workflow known as business modeling. Rational Unified was launched in June 1998
Process, a test phase, with a strengthened UML and the integration of the approaches of Business Engineering and Data Engineering. From here, RUP is born, with the guidelines and aspects that we know today (Vargas 2011).
Business modeling
Business modeling is a discipline in the RUP methodology that is seen in the broader scope of the company. It is used to understand current business processes and determine how they can be improved. Identifying opportunities for automation is one way that you can improve business processes.
You can carry out business modeling as part of a project to help gain a better understanding of the business context or as a separate project spawning multiple software development projects. (Galic, Macisaac, Popescue 2006).
Rational Unified Process (RUP) business modeling
Figure 1 - Rational Unified Process (RUP). (Yana 2013)
According to Balarezo (2013) the following should be taken into account:
- The needs are found by modeling the business. Business modeling focuses on the processes under study and not on the functional areas. Analysis and design of the processes is the best way to meet all the needs.
Ramos (2013) states that the needs must be:
Communicated Needs
- By participants in business processes Clients and users of the organization's services Organizational managers Owners of the organization Other project stakeholders
Analyzed and Designed Needs
- Study of business processes Analysis of activities People who benefit from processes People who execute processes Information used in processes Design of processes
Process Improvement Needs
- Refinement of business processes Optimization of some activities Improved efficiency Changes in the responsibilities of the people who execute the processes New information
Bocanegra (2006) emphasizes the following objectives:
goals
- Understand the structure and dynamics of the target organization Understand current problems of the target organization and identify potential ones Evaluate the impact of change on the target organization Ensure that customers, end users, developers and other roles have a common understanding of the target organization Obtain, in a preliminary way, the system requirements that the target organization needs.
Ramos (2013) defines the following activities:
Activities
- Evaluate the target organization Find the business use cases and actors Build the Business Use Case Model Find the workers and business entities Build the Business Analysis Model Detail the business use cases Maintain business rules Capture a common vocabulary Define the activities to automate
Success stories
One of the many successful cases of business modeling managed under RUP methodologies is the “MAFRE” project that was developed by Information Technology Consulting in Argentina (Information Technology Consulting 2011).
“ASI” Consultores developed the Unitary Control of Merchandise (CUM) system, an application that allows to efficiently manage the flow of merchandise (called Big Ticket) both in warehouses and stores. Using a methodology oriented to the development of projects with object-oriented technologies based on the Rational Unified Process (RUP) allows a company to expand the business horizons of this area (Automatización y Sistemas Integrales Consultores SA de CV 2009)
Contributions
Innovation:
The business modeling of the RUP methodology has allowed companies to acquire all the information necessary for an analysis of the current business and therefore identify which areas can be improved.
Technology:
Business modeling through the software engineering process allows over time to ensure good production of high quality software that meets the need of an end user within a predictable time and budget.
Social:
Obtain a good result that will allow the detection and analysis of structures and automation areas in order to improve processes, determine opportunities, obtaining a good quality of service for society.
Spiritual:
Just as the business model helps to understand which needs are required in the process, so also God in his infinite love, mercy and wisdom wants to supply all our needs as long as you apply the Spiritual Business Model in your life and analyze in the situation you are in.
Conclusions
Any business can be successful and everything will depend on many variables, for this it is necessary to know the key elements in the business model that must be applied appropriately to each type of business.
The study of the business is of vital importance to identify the needs of users in today's companies.
Business modeling is very important because it allows us to see that the parties involved communicate the processes clearly, completely and efficiently.
Rational Unified Process (RUP) provides the activities to model the business and the Unified Modeling Language (UML) provides the symbols necessary to model the business.
We must listen, learn from the best and meet other models.
References
- Galic M. 2006. Using a Single Business Pattern with the Rational Unified Process (RUP). Hernández A. 2005. Identification of business processes. Jonás A, Montilva C. 2007. Business Modeling. Mancin E, Fernandes A, Péraire C, Carroll K. 2007. The IBM Rational Unified Process for System z. (Consulted November 25, 2013) http://www.redbooks.ibm.com/redpapers/pdfs/redp3877.pdf.Ivar Jacobson, Grady Booch, James Rumbaung 2000. The Unified Software Development Process.Bocanegra J, Peña J, Ruiz A. 2006. Interorganizational Business Modeling: An Approach for Traceability between Objectives, Organizational Models and Business Processes. http://businessservices20.com/files/ideas09.pdf.Torres F. 2010. Integration of the PMBOK to the RUP for Software Development projects. (Accessed November 25, 2013) http: //www.iiis.org / CDs2008 / CD2009CSC / CISCI2009 / PapersPdf / C690MI.Pdf.Balarezo S, Yana M, Ramos Y. 2013. Business Modeling: Part 1. Business use case models.http: //booksproyect.googlecode.com. pptVargas Y. 2011. Rup Methodology (Rational Unified Process). Automation and Systems IntegralesConsultores SA de CV Copyright © 1999 - 2009.
