Object Oriented Software Engineering (CS-802 (D)) Notes

How unit 2 is examined

This unit covers the Rational Unified Process: its concepts and roles, best practices, the four-phase life cycle with its diagram, and the nine workflows; each carries one 7-mark question.

Basic Concepts

<span style="display:inline-block;padding:.16em .6em;border:1.5px solid currentColor;border-radius:999px;font-size:.68em;font-weight:700;letter-spacing:.06em;text-transform:uppercase;opacity:.75">Low weight</span>

Definition. <mark>The Rational Unified Process (RUP) is an iterative, incremental, use-case driven and architecture-centric software development process framework, built around UML, that guides teams through phases and workflows to build quality software.</mark>

Key points.

RUP is iterative and incremental, so each iteration produces a tested, executable version that grows into the final system.
Its objectives are to manage requirements, use component-based architecture, model visually with UML, verify quality continuously and control change.
Its building blocks are roles (who), activities (what they do), artifacts (what they produce) and workflows (the sequence of activities).
Roles: business analyst (finds business needs), system analyst (writes use cases and requirements), architect (defines structure), developer (designs and codes), tester (plans and runs tests), project manager (plans, staffs, tracks risk). Together they give clear ownership and a shared plan.

Basis	Waterfall (traditional)	RUP
Flow	Linear, one pass	Iterative, repeated cycles
Delivery	One release at the end	Incremental, working builds each iteration
Risk	Found late, at testing	Tackled early, in elaboration
Requirements	Frozen up front	Use-case driven, change managed
Focus	Documents and phases	Architecture and executable software
Testing	After coding	In every iteration

Answer frame. Open with the RUP definition; list objectives; give the table as the comparison; close with the point that RUP suits large, changing projects. For roles, list the six roles with one sentence each and close on collaboration.

Asked: [7 marks] (Jun 2025) What is the Rational Unified Process (RUP), and what are its primary objectives? Discuss how RUP differs from traditional software development methodologies. Asked: [7 marks] (Jun 2025) What roles are defined within the RUP framework, and what are the responsibilities associated with each role? How do these roles contribute to the successful execution of a project?

Symptoms in Software Development and their Root Causes

Definition. <mark>Symptoms are the visible signs of project failure, and root causes are the underlying process faults that produce them; RUP best practices are designed to remove those causes.</mark>

Key points.

Symptoms include inaccurate understanding of user needs, inability to handle changing requirements, late discovery of defects and poor quality.
Further symptoms are an unmaintainable or badly structured architecture and uncontrolled changes that break the build.
Root causes are ad hoc requirements management, ambiguous communication, brittle architecture and undetected inconsistencies in requirements, design and code.
Other root causes are insufficient testing, subjective assessment of status, waterfall development and uncontrolled change propagation.

Best Practices of RUP

Definition. <mark>RUP's best practices are six proven software engineering practices that together reduce risk and raise quality.</mark>

Key points.

Develop iteratively: build in short cycles, so risks and defects surface early and users give feedback on working software.
Manage requirements: track and trace every requirement with use cases, so changes are controlled and the team builds the right product.
Use component-based architecture: build reusable, replaceable components, which eases change and speeds development.
Model visually: use UML so everyone shares one unambiguous picture, which improves collaboration.
Verify quality continuously: test in every iteration, so defects are cheap to fix.
Control changes: use version and configuration management, so parallel teams do not overwrite each other.

Answer frame. Open with "RUP recommends six best practices"; develop the six in the order above with one outcome each (early risk removal, right product, reuse, shared understanding, fewer defects, safe teamwork); close on better outcomes and collaboration.

Asked: [7 marks] (Jun 2025) What are the best practices recommended by RUP? Provide examples of how these practices can improve project outcomes and enhance team collaboration.

RUP software life cycle

Definition. <mark>The RUP life cycle has four phases, Inception, Elaboration, Construction and Transition, each ending in a milestone and each containing one or more iterations across the workflows.</mark>

<figure class="ds-fig" style="margin:1.4rem 0;overflow-x:auto"><svg xmlns="http://www.w3.org/2000/svg" id="dsfig-u2-01" viewBox="0 0 467 80" width="467" height="80" role="img" aria-label="RUP phases. I Inception, E Elaboration, C Construction, T Transition. Milestones LCO objectives, LCA architecture, IOC initial operational capability. Each phase holds iterations across all workflows."><style>#dsfig-u2-01 .e{stroke:#454C5A;stroke-width:1.4;fill:none}#dsfig-u2-01 .e.hi{stroke:#2340B8;stroke-width:2.6}#dsfig-u2-01 .n{fill:#FFFFFF;stroke:#16181D;stroke-width:1.4}#dsfig-u2-01 .n.hi{fill:#E3E9FC;stroke:#2340B8;stroke-width:2.2}#dsfig-u2-01 .n.rb-b{fill:#16181D;stroke:#16181D}#dsfig-u2-01 .n.rb-r{fill:#BD3227;stroke:#BD3227}#dsfig-u2-01 text{font-family:"JetBrains Mono",ui-monospace,Menlo,Consolas,monospace;font-size:13px}#dsfig-u2-01 .t{fill:#16181D;font-weight:500}#dsfig-u2-01 .t.inv{fill:#FFFFFF;font-weight:700}#dsfig-u2-01 .kd{stroke:#16181D;stroke-width:1.2}#dsfig-u2-01 .dot{fill:#16181D}#dsfig-u2-01 .ann{fill:#2340B8;font-size:11px;font-weight:700}#dsfig-u2-01 .lbl{fill:#6F7787;font-family:system-ui,-apple-system,sans-serif;font-size:12px;font-weight:700}#dsfig-u2-01 .ptr{fill:#2340B8;font-size:12px;font-weight:700}#dsfig-u2-01 .ah{fill:#454C5A}#dsfig-u2-01 .ah.hi{fill:#2340B8}#dsfig-u2-01 .wl rect{fill:#FFFFFF;stroke:#DCE0E7}#dsfig-u2-01 .wl .t{font-size:12px;font-weight:700}#dsfig-u2-01 .wl.hi rect{fill:#2340B8;stroke:#2340B8}#dsfig-u2-01 .wl.hi .t{fill:#FFFFFF}html.dark #dsfig-u2-01 .e{stroke:#B1B7C3}html.dark #dsfig-u2-01 .e.hi{stroke:#8FA3FF}html.dark #dsfig-u2-01 .n{fill:#161920;stroke:#E6E8ED}html.dark #dsfig-u2-01 .n.hi{fill:#1E2748;stroke:#8FA3FF}html.dark #dsfig-u2-01 .n.rb-b{fill:#E6E8ED;stroke:#E6E8ED}html.dark #dsfig-u2-01 .n.rb-r{fill:#FF7E71;stroke:#FF7E71}html.dark #dsfig-u2-01 .t{fill:#E6E8ED}html.dark #dsfig-u2-01 .t.inv{fill:#0F1115}html.dark #dsfig-u2-01 .kd{stroke:#E6E8ED}html.dark #dsfig-u2-01 .dot{fill:#E6E8ED}html.dark #dsfig-u2-01 .ann{fill:#8FA3FF}html.dark #dsfig-u2-01 .lbl{fill:#858D9C}html.dark #dsfig-u2-01 .ptr{fill:#8FA3FF}html.dark #dsfig-u2-01 .ah{fill:#B1B7C3}html.dark #dsfig-u2-01 .ah.hi{fill:#8FA3FF}html.dark #dsfig-u2-01 .wl rect{fill:#161920;stroke:#2A2E37}html.dark #dsfig-u2-01 .wl.hi rect{fill:#8FA3FF;stroke:#8FA3FF}html.dark #dsfig-u2-01 .wl.hi .t{fill:#0F1115}</style><defs><marker id="ah3" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="7" markerHeight="7" orient="auto-start-reverse"><path class="ah" d="M0,1 L9,5 L0,9 z"/></marker><marker id="ahh3" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="7" markerHeight="7" orient="auto-start-reverse"><path class="ah hi" d="M0,1 L9,5 L0,9 z"/></marker></defs><path class="e" d="M59,40 L148,40" marker-end="url(#ah3)"/><path class="e" d="M188,40 L277,40" marker-end="url(#ah3)"/><path class="e" d="M317,40 L406,40" marker-end="url(#ah3)"/><g class="wl"><rect x="87.7" y="31" width="33.6" height="18" rx="9"/><text class="t" x="104.5" y="40" dy=".35em" text-anchor="middle">LCO</text></g><g class="wl"><rect x="216.7" y="31" width="33.6" height="18" rx="9"/><text class="t" x="233.5" y="40" dy=".35em" text-anchor="middle">LCA</text></g><g class="wl"><rect x="345.7" y="31" width="33.6" height="18" rx="9"/><text class="t" x="362.5" y="40" dy=".35em" text-anchor="middle">IOC</text></g><circle class="n" cx="40" cy="40" r="18"/><text class="t" x="40" y="40" dy=".35em" text-anchor="middle">I</text><circle class="n" cx="169" cy="40" r="18"/><text class="t" x="169" y="40" dy=".35em" text-anchor="middle">E</text><circle class="n" cx="298" cy="40" r="18"/><text class="t" x="298" y="40" dy=".35em" text-anchor="middle">C</text><circle class="n" cx="427" cy="40" r="18"/><text class="t" x="427" y="40" dy=".35em" text-anchor="middle">T</text></svg><figcaption style="font-size:.82em;opacity:.72;margin-top:.45rem">RUP phases. I Inception, E Elaboration, C Construction, T Transition. Milestones LCO objectives, LCA architecture, IOC initial operational capability. Each phase holds iterations across all workflows.</figcaption></figure>

Key points.

Inception sets the scope, business case and rough cost; its milestone is Lifecycle Objectives (LCO).
Elaboration analyses the problem, builds an executable architecture baseline and removes major risks; its milestone is Lifecycle Architecture (LCA).
Construction builds the remaining components and features to produce the beta product; its milestone is Initial Operational Capability (IOC).
Transition delivers the product to users through beta testing, training and deployment; its milestone is Product Release.
Effort on each workflow varies by phase: requirements dominate early, implementation and test in construction, deployment in transition.

Answer frame. Open with the RUP definition; draw the phase-versus-workflow chart (four phases across, nine workflows down, iterations marked) and label milestones; explain each phase with objective and milestone; close on iterative delivery.

Asked: [7 marks] (May 2022) What do you mean by RUP? With a neat diagram, explain RUP software life cycle.

4+1 view model

Definition. <mark>The 4+1 view model (Kruchten) describes a software architecture through four views tied together by a fifth view of scenarios (use cases).</mark>

Key points.

The Logical view shows the classes and object model for the end user's functionality.
The Process view shows concurrency, threads and synchronization for integrators.
The Development (implementation) view shows the modules and components for programmers.
The Physical (deployment) view maps software onto hardware nodes for system engineers.
The +1 Scenarios (use case) view links and validates all four views.

Various Workflows

Definition. <mark>RUP has nine workflows: six core engineering workflows and three supporting workflows, each a set of activities that produce artifacts.</mark>

Key points.

Business modeling documents the business processes and organisation so developers understand the context.
Requirements captures what the system must do, using use cases and supplementary specifications.
Analysis and design turns requirements into a design model and architecture of classes and components.
Implementation codes and unit-tests the components and integrates them into a working system.
Test finds defects by planning, running and evaluating tests against requirements.
Deployment packages the product and delivers it to users.
Configuration and change management (supporting) controls versions and change requests.
Project management (supporting) plans iterations, manages risk and tracks progress.
Environment (supporting) provides tools, process and guidelines to the team.

Answer frame. Open with "RUP has six core and three supporting workflows"; explain in the order above, one sentence each, grouping core then supporting; close by saying all nine run in every phase with varying effort.

Asked: [7 marks] (May 2022) What are the various work flows used in RUP, Explain them.

Last-minute revision

RUP = Rational Unified Process: iterative, incremental, use-case driven, architecture-centric.
Six best practices: iterate, manage requirements, components, visual modeling (UML), verify quality, control change.
Four phases: Inception, Elaboration, Construction, Transition.
Milestones: LCO, LCA, IOC, Product Release.
Nine workflows: 6 core, 3 supporting.
Core: business modeling, requirements, analysis and design, implementation, test, deployment.
Supporting: configuration and change management, project management, environment.
Roles: business analyst, system analyst, architect, developer, tester, project manager.
4+1 views: logical, process, development, physical, plus scenarios.
Elaboration removes major risk and fixes the architecture.

Memory hooks

IECT: Inception, Elaboration, Construction, Transition.
Six core: "Big Ross Always Is Testing Daily" = Business, Requirements, Analysis, Implementation, Test, Deployment.
Supporting three: "CPE" = Configuration, Project, Environment.
LCO, LCA, IOC: Objectives, Architecture, Operational capability.
4+1: Logical, Process, Development, Physical, plus Scenarios in the middle.

Coverage checklist

Basic Concepts: RUP definition, objectives, waterfall comparison, roles (Q Jun 2025, Q Jun 2025).
Symptoms in Software Development and their Root Causes: no past questions.
Best Practices of RUP: six practices (Q Jun 2025).
RUP software life cycle: phases, milestones, diagram (Q May 2022).
4+1 view model: no past questions.
Various Workflows: nine workflows (Q May 2022).

Account

Object Oriented Software Engineering (CS-802 (D)) - Unit 2 Short Notes

How unit 2 is examined

Basic Concepts

Symptoms in Software Development and their Root Causes

Best Practices of RUP

RUP software life cycle

4+1 view model

Various Workflows

Last-minute revision

Memory hooks

Coverage checklist