RUP (Rational Unified Process , unified software development process): is an object-oriented and network-based program development methodology.
RUP acts like an online mentor, providing guidelines, templates, and case support for all aspects and levels of program development.
1. The software engineering process defines who is doing what, how, and when. RUP is expressed in four main modeling elements:
· Roles (Workers) - "who"
Activities - "how to"
Artifacts - "what to do"
Workflows - "when to do it"
1. Role: It defines a set of activities performed and a set of documents and models owned. It is an abstract definition of responsibility that describes the behavior and responsibilities of a person or a group. Roles do not represent individuals, but describe how individuals should behave in the business and their responsibilities.
RUP predefines many roles:
Analyst role set: The analyst role set is used for various roles in an organization mainly engaged in requirements acquisition and research
Development role set: The developer role set is used to organize various roles mainly engaged in software design and development. Tester role set: The tester role set is used to organize various roles mainly engaged in software testing.
Manager role set: The manager role set is used to organize various roles mainly engaged in the management and configuration of software engineering processes.
2. Activity: is an independent unit of work with a clear purpose. That is, the set of tasks that must be done by the person in this role.
3. Product (Artifact): A product is a piece of information that is produced, modified, or used by a process. A product is the tangible outcome of a project, something the project manufactures or uses to produce the final product. Products can have different forms such as
· Models, such as use-case models or design models.
· Model elements such as classes, use cases or subsystems.
Documentation, such as business use case or software architecture documentation.
· Source code.
·Executable program
4. Workflow: simply enumerating all roles, activities, and products does not constitute a process. In addition, an efficient way is needed to describe the sequence of activities that produce valuable results, and to show the interaction between roles . A workflow is a sequence of activities that produce observable results. In UML, a workflow can be represented by a sequence diagram, collaboration diagram or activity diagram.
2. RUP is divided into six core "engineering " workflows: Business Modeling Workflow, Requirements Workflow, Analysis and Design Workflow, Implementation Workflow, Test Workflow, and Deployment Workflow
RUP divides a development cycle into four consecutive phases:
1. Inception phase : Establish business use cases for the system and determine the boundaries of the project. Milestones at the end of the inception phase are lifecycle goals;
2. Elaboration phase : Analyze the problem area, establish a sound architectural foundation, prepare a project plan, and eliminate the most risky elements of the project. The milestone at the end of the Elaboration phase is the Lifecycle Architecture;
3. Construction phase : All remaining components and application parts will be developed, tested, and integrated into the product. - Initial operational capability milestones. The milestone at the end of the build phase is the initial operational capability;
4. Transition phase : The software product is delivered to the user group. The milestone of the handover phase is the product release.