Workflow Process Of Relational Unified Process

Published Date: 02 Nov 2017

This project examines workflow of the process under Rational Unified Process (RUP) as the one of life circle approach that is well suited to the Unified Modified Language (UML). Unified Modeling Language was introduced in 1970s and late 1980s as object-oriented language to investigate and design software’s, Unified Modeling Language is a uniform all-purpose modeling language on an area of object oriented software engineering. UML is used in the development of objects oriented software- intensive system to identify, envision, adjust, and assemble the artifacts of object oriented software engineering. Rational Unified Process and Unified Modeling Language are related due to the fact that they both use object and class to develop an application.

The main aim of the study was to

Discuss the workflow of the Rational Unified Process

Find out the Rational Unified Process

Identify the characteristics of Rational Unified Process

Investigate the life cycle of Rational Unified Process

INTRODUCTION

Relational Unified Process is software that offers a well managed process in appointing tasks and responsibilities in an advanced or development organization. Its main concern is basically to manufacture software’s of high class that will satisfy the requirements of customers. When defining the Relational Unified Process four fundamentals are taken into consideration, these fundamentals include workers, activities, artifacts and workflows. This project is based on the workflow of the Relational Unified Process; a workflow is an organized series of activities performed to achieve a certain goal and in this case the goal is to produce software’s of high value. Workflow of this process includes business modeling, requirements, analysis and design, implementation, test and deployment.

BACKGROUND

WORKFLOW OF THE RELATIONAL UNIFIED PROCESS

Business Modeling: Starzhinsky (2010) its function is to evaluate the organization in which the system will be implemented. In this workflow process problems are analyzed and solutions for improvement are identified. Furthermore the author indicated that it is also very important to make sure that there is a mutual understanding about the organization between developers and customers.

Requirements: it’s mainly concerned with capturing and assessing the requirements of the project. Its purpose is to help system managers to have a clear perceptive of the system requirements; it also offers a way of calculating cost and time approximately to develop the system Starzhinsky (2010). With this workflow there is a contract between consumers and stakeholders on what the system must actually do and it consists of the use of case model and domain model.

Analysis and design: According to Starzhinsky (2010) the function of this workflow is to convert the model into a desired system by using the identified requirements which are used to define the nature of the system.

Implementation: its purpose is to put the system into operation in the approved implementation background. All important information such as data files, software components and logs about the compilation of the system just to mention a few are saved Starzhinsky (2010).

Test: Starzhinsky (2010) explained that in this set the system is evaluated in a way that the project managers should make sure that the system is the one that was proposed and even ensure that there are no errors in the implementation. A test plan is followed to track those errors, which include test cases, testing criteria and allocation of the resource for testing.

Deployment: according to Starzhinsky (2010) project managers must make certain that software products are available for end users. This workflow includes software packages, installation of files and the location where the application is to be installed.

BENEFITS OF THE RELATIONAL UNIFIED PROCESS

Easily Resolves Risks: Daniel (2011) Relational Unified Process assists to determine any risks that can be encountered on the projects, so as to meet the needs of the customers without any failure.

Control Changes: according to Daniel (2011) developers can perform an action at the same time hence different components of the project would be managed well due to the fact that different teams are involved. The author indicated that these changes can be changing of requirements, technology, products, and platforms just to mention few. With control changes developers should make certain that changes are handled and controlled well. For example, during the workflow process project managers should ensure that software’s are well evaluated in each flow.

Flexible Patterns: with Relational Unified Process managers have the chance of reusing a certain process when addressing a familiar or common problem that has been tackled before. This process is said to be flexible because managers can modify certain processes so as to meet project needs rather than starting from scratch, this is even time consuming Daniel (2011).

Efficient Delivery Process: with this process there is well managed delivery process that provides project managers with the prospect to plan and begin the project Daniel (2011). The development project is basically responsible for supplying the manager with assets or resources required for the entire project.

Support Iterative Development: according to Daniel (2011) "RUP software development organizes systems into phases to ensure each process has better executable iterations, not to mention these processes have been used successfully by other organizations"

CHARACTERISTICS OF RATIONAL UNIFIED PROCESS

Iterative Process: Eeles, P.et al (2002), has noted that, Rational Unified Process use iteration to go behind steps from the initialization of application until it is finished. This feature assists to identify the problems in the project, come up with solutions to problems, develop software, and test the end products.

Architecture Centric: According to Rumbaugh et al, (2000), this feature helps to highlight the development of software design, dynamic architecture helps comparable development, minimize rework by modifying the system and improve the reusability of the component and maintenance of the system.

Object Oriented Techniques: Rational Unified Process together with Unified Modeling Language is Object Oriented Technique because they both deal with the use of objects, classes, and its relationship so as to implement the flow of designing a system Eeles, P.et al (2002).

Configured Process: Rational Unified Process allow configuration because ones process are not suitable for software’s development. On the other hand, Rational Unified Process is flexible with other platforms that are self-motivated due to development.

Control and Risk Management: according to Eeles, P.et al (2002) Rational Unified Process make certain that when application are developed all steps are followed pertain the requirement of the company and customers. In addition the author emphasized that all activities those are carried out during the project development objectives measurements are taken into considerations.

LIFE CYCLE OF RELATIONAL UNIFIED PROCESS

Inception Phase: Singha (n.d) its main objective is to convert main ideas into the product image or vision; this is carried out by describing the product scope and its implementation plan. Furthermore the author states that inception phase uses business case when developing the project, this concept covers the most vital part of the application such as risk management, success criteria, and analysis of the resources and also the goal of the project. In general, this phase identifies all the resources needed to complete the project.

Elaboration Phase: This phase is mainly concerned with structural design, project plan is taken into consideration, and any factors that might hinder the newly developed project are determined Singha (n.d). Some of the workflow of the process included in this phase is the implementation, design and test of the application so as to find solutions to errors if at all there are errors.

Construction Phase: according to Singha (n.d) like the name explains, this phase is basically about building the software system or project, this is where the actual system or product is made. Singha (n.d) indicated that in this phase managers should ensure that software’s are of high quality, features of applications and apparatus are well developed in order to produce a high class system.

Transition Phase: under this phase the developers make sure that the products reach its end users, it’s also the responsibility of managers to ensure that the products meet the needs of customers. On the other hand, the system should be installed to the customer for assessment and testing, end users should also be trained on how to use the system Singha (n.d).

CONCLUSION

Relational Unified Process is software that offers a well managed process in appointing tasks and responsibilities in an advanced or development organization. Its main concern is basically to manufacture software’s of high class that will satisfy the requirements of customers. To achieve this development of high quality software’s Relational Unified Process implemented the use of workflows, which includes business modeling, requirements, analysis and design, implementation, test and deployment. This Relational Unified Process has a life cycle which includes four phases been Inception, Elaboration, Construction and Transition, this phases work hand in hand to obtain a very high quality system or project and to meet the needs of end users.