Unified software Development process (RUP)

RUP (Rational Unified process, unified Software development): an object-oriented, Web-based program development methodology.

Rup appears to be an online mentor who can provide guidelines, templates, and case support for all aspects and levels of program development.

First, the software engineering process defines who is doing what, how and when, Rup uses four main modeling elements to express:

• Character (Workers)--"who"

• Activities (Activities)--"How To Do"

• Product (workpiece) (artifacts)--"What to Do"

• Workflow (Workflows)--"when to do"

1. Role: It defines a set of activities that are performed and a set of documents and models that are owned. is an abstract responsibility definition that describes the behavior and responsibilities of a person or a group. Roles do not represent individuals, but rather describe how individuals should behave in the business and the responsibilities they should take.

RUP defines a number of roles in advance:

Analyst role set: The role set of analysts is used to organize roles that are primarily engaged in demand acquisition and research

Development Role sets: The developer role set is used to organize the various roles that are primarily engaged in software design and development. Tester role set: The tester role set is used to organize the various roles that are primarily engaged in software testing.

Manager role set: The manager role set is used to organize the various roles that are primarily engaged in the management and configuration of software engineering processes.

2. Activity: an independent unit of work with a clear purpose. A group of work that the person who assumes this role must complete.

3. Product (workpiece): a product is a process of production, modification or use of a piece of information. A product is a tangible result of a project, something that the project makes 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.

• Documents, such as business use cases or software architecture documents.

• Source code.

• Executable program

4. Workflow: Simply enumerating all roles, activities, and products is not a process, but it also requires an effective way to describe the sequence of activities that produce valuable results and to show the interactions between roles. A workflow is an activity sequence that produces an observable result. In UML, you can use a sequence diagram, a collaboration diagram, or an activity diagram to represent a workflow.

Ii. Rup is divided into six core "engineering" Workflows: Business modeling workflows, requirements workflows, analyzing and designing workflows, implementing workflows, testing workflows, and expanding workflows

RUP divides a development cycle into four successive phases:

1. Initial phase (Inception phase): Establish business use cases for the system and determine the boundaries of the project. Milestones at the end of the initial phase are life cycle objectives;

2. Refinement phase (elaboration Phase): Analyze problem areas, establish a sound Architecture foundation, prepare project plans, and eliminate the most risky elements in the project. The milestone at the end of the refinement phase is the life cycle architecture;

3. Construction phase (construction phase): All remaining components and application parts will be developed, tested and integrated into the product. --Initial Operational capability milestone. The milestone at the end of the construction phase is the initial operational capacity;

4. Handover phase (Transition phase): Delivery of software products to the user base. Milestones in the handover phase are product launches.