1 / 11

Unified Process March 27, 2006 Chris Armstrong

Unified Process March 27, 2006 Chris Armstrong. What is the Unified Process?. Why use it or why it is needed A way of saving time and increasing quality by explaining how to do something By breaking processes into understandable chunks

ishmael-olson
Download Presentation

Unified Process March 27, 2006 Chris Armstrong

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Unified ProcessMarch 27, 2006Chris Armstrong

  2. What is the Unified Process? • Why use it or why it is needed • A way of saving time and increasing quality by explaining how to do something • By breaking processes into understandable chunks • By providing a common language for expressing a software process and integrating teams • By providing steps, check lists, guidelines, templates, tooling, concepts, etcs. • What is it • It is an adaptable approach that describes how to develop software more effectively using well-evolved techniques • Not a single prescriptive process • It is intended to be tailored, you select the appropriate processes for the specific project and organization • RUP uses UML to model the problem and solution space |

  3. IBM Unified Method Architecture: Comprehensive Evolution • IBM UMA:Unified Method Architecture, comprised of • UML Meta-model Specification(provides one IBM-wide method structure and terminology) • Common Content Architecture Outline(prepares IBM-wide method content reuse) • Developed by interdisciplinary team with members from all three Methods • Provides one integrated Method Engineering Solution: Prepares for common management and structural integration of all of IBM’s method offerings • Submitted to OMG to become SPEM 2.0 standard (software process engineering metamodel) IBM Global Services Method SUMMIT Ascendant RUP Unified Method Architecture SPEM 2.0 |

  4. Unified Process is Based on the Following Principles • Identify risks and deal with them continuously • Provide value to users (develop a useful product) • Focus on writing code • Accommodate change early • Baseline architecture early • Build using components • Focus on quality, test early • Work as one team |

  5. The Basic Elements of RUP |

  6. Project Manager Identify and Assess Risks Vision Risk List Core RUP Elements: Roles, Activities, Artifacts Roles perform activities which have input and output artifacts. Example: The Project Manager role performs the Identify and Assess Risks activity, which uses the Vision artifact as input and produces the Risk List artifact as output. |

  7. Summary of Major Artifacts |

  8. Each discipline in RUP contains one workflow. A workflow is the conditional flow of high-level tasks (Workflow Details) that produce a result of observable value. Workflow Details RUP Workflows |

  9. Example Workflow Detail diagram: Analyze the Problem Workflow Details show roles, activities they perform, input artifacts they need, and output artifacts they produce. Core RUP Element: Workflow Detail Example: Requirements Workflow |

  10. Guidance • Guidance can be attached to both method and process elements in order to provide additional guidance about those elements. • Types • Checklist • Concept • Example • Guideline • Practice • Report • Reusable Asset • Roadmap • Supporting Material • Template • Term Definition • White Paper |

  11. Time Content Content Organization by Disciplines |

More Related