Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

Enterprise Unified Process

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Wird geladen in …3
×

Hier ansehen

1 von 14 Anzeige

Weitere Verwandte Inhalte

Diashows für Sie (20)

Anzeige

Ähnlich wie Enterprise Unified Process (20)

Aktuellste (20)

Anzeige

Enterprise Unified Process

  1. 1. Enterprise Unified Process Ritika Jangid 07030244019 MBA(SDM)
  2. 2. Agenda <ul><li>RUP and its limitations </li></ul><ul><li>Need for EUP </li></ul><ul><li>EUP: an extension to RUP </li></ul><ul><li>EUP lifecycle </li></ul><ul><li>EUP Phases </li></ul><ul><li>EUP Disciplines </li></ul><ul><li>EUP Best practices </li></ul>
  3. 3. RUP <ul><li>One of the first iterative software development processes in the market. </li></ul><ul><li>Based on six best practices: </li></ul><ul><ul><li>develop iteratively, </li></ul></ul><ul><ul><li>manage requirements, </li></ul></ul><ul><ul><li>use component architecture, </li></ul></ul><ul><ul><li>model visually (UML), </li></ul></ul><ul><ul><li>continuously verify quality, </li></ul></ul><ul><ul><li>manage change </li></ul></ul><ul><li>RUP is initially created on the basis of diagnosing the characteristics of different software projects that failed. </li></ul><ul><li>RUP is a reverse-engineering effort to ensure the success of IT projects </li></ul>
  4. 4. RUP Limitations <ul><li>RUP is very much development focused process </li></ul><ul><li>It can not see anything beyond the development boundary like enterprise level issues and different management aspects of the organizations. </li></ul>
  5. 5. Need for EUP <ul><li>Although software development clearly is important, it’s only part of overall information technology (IT) picture. </li></ul><ul><li>We need to not only develop systems, we must operate and support them once in production. </li></ul><ul><li>We must handle cross-system enterprise issues such as portfolio management, enterprise architecture, and strategic reuse etc. </li></ul>
  6. 6. EUP <ul><li>The Enterprise Unified Process (EUP) is an extension of the Rational Unified Process developed by Scott W. Ambler </li></ul><ul><li>EUP fits RUP with all enterprise essences </li></ul><ul><li>Best suited for: Enterprise organizations </li></ul><ul><li>Introduces five new best practices </li></ul><ul><li>EUP includes two new phases </li></ul><ul><li>Also includes seven new enterprise management disciplines </li></ul>
  7. 7. EUP adds to RUP <ul><li>EUP augments RUP to address the enterprise features rather than just software development which is a part of enterprise lifecycle. </li></ul><ul><li>Introduces a proper enterprise project lifecycle within the enterprise </li></ul><ul><li>EUP is continuously aiming to reduce the process complexities and increasing perpetuating best practices </li></ul><ul><li>It handles multi-geographic presence and cross-system issues that organizations should address to be successful at IT. </li></ul>
  8. 8. EUP Lifecycle
  9. 9. Two New Phases <ul><li>Production Phase </li></ul><ul><ul><li>Primary focus: offering required assistance to the end users </li></ul></ul><ul><ul><ul><li>clarifying their queries </li></ul></ul></ul><ul><ul><ul><li>resolving the production issues through the combination of root-cause analysis </li></ul></ul></ul><ul><ul><ul><li>applying appropriate fixes </li></ul></ul></ul><ul><ul><ul><li>dealing with change request from users </li></ul></ul></ul><ul><li>Retirement Phase </li></ul><ul><ul><li>Guides how to effectively decommission the product from the production phase to the retired phase </li></ul></ul>
  10. 10. Seven New Disciplines <ul><li>Operations and Support Discipline </li></ul><ul><ul><li>Project discipline </li></ul></ul><ul><ul><li>Facilitates uninterrupted operations of software systems </li></ul></ul><ul><ul><li>Aimed to ensure a fault tolerant environment and recoverable system through appropriate backup & disaster recovery plan. </li></ul></ul><ul><ul><li>critical for any enterprise to maintain and improve ROI of the enterprise economy </li></ul></ul><ul><li>Enterprise Business Modeling Discipline </li></ul><ul><ul><li>Enterprise discipline </li></ul></ul><ul><ul><li>Enterprise models help to distinguish the relationship between Business process, domain process, enterprise activities, functional entities and functional operations. </li></ul></ul><ul><ul><li>Enterprise business modelers will work closely with the enterprise stakeholders to delimit the scope of their project, in particular helping them to identify the goals, targets, and vision for the enterprise. </li></ul></ul>
  11. 11. Enterprise Disciplines <ul><li>Portfolio Management Discipline </li></ul><ul><ul><li>Enterprise success factor depends on the overall efficiency and the effectiveness of managing a diversified mix of software portfolio. </li></ul></ul><ul><ul><li>Continuous activity throughout the enterprise system lifecycle to mitigate enterprise risks. </li></ul></ul><ul><li>Enterprise Architecture Discipline </li></ul><ul><ul><li>Defines state-of-the art enterprise architecture </li></ul></ul><ul><ul><li>Includes: </li></ul></ul><ul><ul><ul><li>architectural frameworks </li></ul></ul></ul><ul><ul><ul><li>reference architectures </li></ul></ul></ul><ul><ul><ul><li>architectural standard & guidelines. </li></ul></ul></ul><ul><li>Strategic Reuse Discipline </li></ul><ul><ul><li>Reusing wide varieties of software assets; from source code to architectural frameworks </li></ul></ul>
  12. 12. Enterprise Disciplines <ul><li>People Management Discipline </li></ul><ul><ul><li>Focuses on the human oriented management aspect development of any IT organization. </li></ul></ul><ul><ul><li>HR strategies should be aligned with the organization’s unique IT strategy </li></ul></ul><ul><li>Enterprise Administration Discipline </li></ul><ul><ul><li>Covers the enterprise level administrative responsibilities and initiatives to provide an active support towards the project teams. </li></ul></ul>
  13. 13. Best Practices of RUP <ul><li>The EUP introduces five new best practices </li></ul><ul><ul><li>Proven architecture </li></ul></ul><ul><ul><li>Modeling </li></ul></ul><ul><ul><li>Collaborative development </li></ul></ul><ul><ul><li>Look beyond development </li></ul></ul><ul><ul><li>Deliver working software on a regular basis and Manage risk. </li></ul></ul>
  14. 14. Thank You

×