fINAL RUP

Rational Unified Process By.Rajneesh Sharma & Ashwani Bharatdwaj : 

Rational Unified Process By.Rajneesh Sharma & Ashwani Bharatdwaj Per Kroll, Director of RUP

What is RUP : 

What is RUP A software development approach that is iterative, architecture-centric and use-case driven A well-defined and structured software engineering process A process product providing a customizable process framework

Iterative Development Phases : 

Inception Iterative Development Phases Time Inception: Understand what to build Vision, high-level requirements, business case Not detailed requirements Elaboration: Understand how to build it Baseline architecture, most requirements detailed Not detailed design Construction: Build the product Working product, system test complete Transition: Validate solution Stakeholder acceptance

Iterations and Phases : 

Executable Releases Iterations and Phases An iteration is a distinct sequence of activitieswith an established plan and evaluation criteria,resulting in an executable release.

Iterative Lifecycle Graph : 

Iterative Lifecycle Graph In an iteration, you may walk through all disciplines C O N T E N T S T R U C T U R E T I M E

Inception: Know What to Build : 

Inception: Know What to Build Prepare vision document and initial business case Include risk assessment and resource estimate Develop high-level project requirements Initial use-case and domain models (10-20% complete) Manage project scope Reduce risk by identifying all key requirements Acknowledge that requirements will change Manage change, use iterative process Inception Elaboration Construction Transition

Elaboration: Know How to Build It : 

Inception Elaboration Construction Transition Elaboration: Know How to Build It Detail requirements as necessary (~80% complete) Less essential requirements may not be fleshed out Produce an executable and stable architecture Define, implement and test interfaces of major components Identify dependencies on external components and systems. Integrate shells/proxies of them. Some key components will be partially implemented Roughly 10% of code is implemented. Drive architecture with key use cases 20% of use cases drive 80% of the architecture Design, implement and test key scenarios for use cases

Elaboration: Know How to Build It : 

Inception Elaboration Construction Transition Elaboration: Know How to Build It Verify architectural qualities Reliability: Stress test Scalability and Performance: Load test Continuously assess business case, risk profile and development plan

Construction: Build The Product : 

Inception Elaboration Construction Transition Construction: Build The Product Complete requirements and design model Design, implement and test each component Prototype system and involve end users Incrementally evolve executable architecture tocomplete system Build daily or weekly with automated build process Test each build Automate regression testing Load and stress test to ensure architectural integrity Deliver fully functional software (beta release) Includes training material, user and deployment documentation Produce release descriptions

Transition: Deploy to End Users : 

Inception Elaboration Construction Transition Transition: Deploy to End Users Produce incremental ‘bug-fix’ releases Update user manuals and deployment documentation Update release descriptions Execute cut-over Conduct “post-mortem” project analysis

Key Best Practices and Principles : 

Key Best Practices and Principles Develop only what is necessary Lean process, agility Minimize paperwork Be flexible Requirements, plan, usage of people, etc… Learn from earlier mistakes Feedback loops Process improvement Revisit risks regularly Establish objective, measurable criteria for progress Automate Support process with software development tools Best Practices Process Made Practical Develop Iteratively Manage Reuirements Use Component Architectures Model Visually (UML) Continuously Verify Quality Manage Change

A Structured Process: Role, Artifact, Activity : 

A Structured Process: Role, Artifact, Activity

Guidelines, Templates, Tool Mentors, … : 

Guidelines, Templates, Tool Mentors, …

Expressed as Workflows and Workflow Details : 

Expressed as Workflows and Workflow Details

RUP is an Industry-Wide Process Platform : 

RUP is an Industry-Wide Process Platform

Delivering a More Configurable Process to a Broader Audience : 

Common methodology Shared understanding of terminology, deliverables, and responsibilities Processauthoring Leverage internal knowledge and process assets Process configuration Configure and deploy process for specific tools, technologies, domains Processdelivery Filter project content and customize tree browser Delivering a More Configurable Process to a Broader Audience Development organization Process engineers, program/project offices Project managers & team leads Practitioners Plug-InforJ2EE Plug-InforXP Plug-Infor.NET Large J2EEProject SmallTeamProject .NETProject Core RUP Customize Configure Personalize

Evolution of Content : 

Rational Approach Objectory 3.8 Evolution of Content Requirements College, Test process Config. & Change Mgmt, Data Engineering Business Engineering, UI Design, Performance testing UML 1.0, OMT, Booch Project management, Realtime ROOM RPW Agile best practices, Metrics, J2EE, IBM WebSphere, MS WinDNA Test overhaul, XP, BEA, J2EE, MS .NET,Small RUP, e-Business v4.0 - 1996 v4.1 - 1997 v5.0 - 1998 v5.5 - 1999 v2000 v2001 v2002 RUP Builder Business & data modeling, Test-First Design, Systems Engineering, Creative Web Design, Asset-Based Development, … v2003 MyRUP

Slide 18: 

RUP for Small WSAD Projects RUP: Highly Configurable A large set of plug-ins… many selectable process components RUP Base RUP for XP and .NET RUP for Systems Engineering RUP for … … Technology Tools & middleware Domains IBM WAS J2EE BEAWebLogic Microsoft.NET IBM Rational Rapid Developer Sun iAS SystemsEngineering XP Asset-Based Development

Configuration Tools: RUP Builder : 

Configuration Tools: RUP Builder Right-size your process through fine-granular process selection +100 selectable units Small, medium, and large project configurations available as starting point Produce role-based views Easy access to latest content through RUP plug-in exchange Assemble the right process

Practitioner: MyRUP : 

Practitioner: MyRUP Personalized views Role-based and personalized views into your project’s process Add links to external and internal resources Project Web and Extended help integrated with RUP browser Closer integration with RDN Hotlinks to RDN, etc. from MyRUP Seamless search across RUP and RDN Assets available through MyRUP Easy access through clean workspace

Slide 21: 

Context-sensitive process guidance from tools RUP: Integrated with Tools Tool mentors: Web-based assistance for tool use Extended Help: Process guidance from within any tool

Process Authoring: Rational Process Workbench (RPW) : 

Process Authoring: Rational Process Workbench (RPW) Visually model process elements Add custom process content RUP Organizer feature simplifies management of custom guidance, descriptions, examples and templates RUP Modeler feature leverages IBM Rational XDE for visual process authoring

RUP Versatility : 

RUP Versatility Used in project of varying size and “ceremony” levels Majority of RUP projects have <15 people Also used in programs with thousands of people Facilitates Extreme Programming to formal process standards Used in a broad set of industries such as: Financial institutes and insurance Automotive, system integrators, government, .. Telecommunication, defense industry, … Provides explicit guidance for: Custom application development Systems engineering Legacy evolution Extended by customers to guide in: Package implementation

Slide 24: 

Thank you