RUP and Introduction to Enterprise Analysis

RUP and Introduction to Enterprise Analysis

• 1.
  Business Analysis Training RUP andEnterprise Analysis
• 2.
  Page 2Classification: Restricted Agenda •RUP-Rational unified process • Enterprise Analysis • What is Enterprise Analysis • Why Enterprise Analysis • Different Architectures
• 3.
  Page 3Classification: Restricted Whatis RUP? The Rational Unified Process (RUP) is an iterative software development process framework created by the Rational Software Corporation, a division of IBM.
• 4.
  Page 4Classification: Restricted Definitionand Overview of RUP What is RUP? • Process Used for UML • Used for designation • Assigns responsibility Overview of RUP • Two-Dimensional: • Dynamic • Cycles • Phases • Iterations • Milestones • Static • Activities • Artifacts • Workers • Workflows
• 5.
  Page 5Classification: Restricted InceptionPhase What Happens at this Phase? • Creation of: • Business Case • Preliminary Use Cases • Vision Document • Possible Prototypes of the Product/Software Outcomes of Inception Phase • Agreement between stakeholders on scope and cost estimates • Understanding of requirements • Initial exposure to estimates, priorities, risks and the overall development process
• 6.
  Page 6Classification: Restricted ElaborationPhase What Happens at this Phase? Analysis of: • Domain • Requirements • Project Plan • Project Stability & Flexibility Outcomes of the Elaboration Phase •More complete Use-Case Model with detailed descriptions • Description of the Software Architecture • Development plan for overall project and any projected iterations/evaluations
• 7.
  Page 7Classification: Restricted ConstructionPhase What Happens at this Phase? • Development of: • The Final Product • Test Cases to test the final product • Management Tools • Resource Management • Quality Management • Schedule Management Outcomes of the Construction Phase • A fully functional product or software • User Manuals • Description of a release or current product
• 8.
  Page 8Classification: Restricted TransitionPhase and Iterations What Happens in the Transition Phase? Release of the Final Product • Provide: • Product • Post-Release debugging/troubleshooting • End-User Support & Training Outcome of the Transition Phase • Rollout of final product • User feedback may be available • Comparison of cost & time forecasts to actual costs & time Outcome of Iterations • Risk Mitigation • Better Change Management • Continuous Learning • Better Overall Quality
• 9.
  Page 9Classification: Restricted StaticStructure of the Process A process describes who is doing what, how, and when. • Workers, The ‘who’ • Activities, The ‘how’ • Artifacts, The ‘what’ • Workflows, The ‘when’
• 10.
  Page 10Classification: Restricted Worker Aworker defines: • The behavior • The responsibility of an individual or a group of individual working as a team
• 11.
  Page 11Classification: Restricted Activity Activityof a worker is a unit of work that an individual will perform or given to perform in a given time frame. An activity should be usable as an element of planning and progress; if it is too small, it will be neglected, and if it is too large, progress would have to be expressed in terms of an activity’s parts. Example of activities: Plan an iteration, for the Worker: Project Manager Find use cases and actors, for the Worker: System Analyst Review the design, for the Worker: Design Reviewer Execute performance test, for the Worker: Performance Tester
• 12.
  Page 12Classification: Restricted Artifacts Anartifact is a piece of information that is Produced Modified or used by a process Artifacts are used as input by workers to perform an activity Parameters of activities Artifacts may take various shapes or forms: • A model, such as the Use-Case Model or the Design Model • A model element, i.e. an element within a model, such as a class, a use case or a subsystem • A document, such as Business Case or Software Architecture Document • Source code • Executables
• 13.
  Page 13Classification: Restricted Workflow Aworkflow is a sequence of activities that produces a result of observable value. A workflow can be expressed as a sequence diagram, a collaboration diagram, or an activity diagram.
• 14.
  Page 14Classification: Restricted CoreWorkflow There are nine core process workflows in the Rational Unified Process.
• 15.
  Business Analysis Training Enterprise Analysis
• 16.
  Page 16Classification: Restricted Whatis Enterprise Analysis? Describes the Business Analysis activities necessary to identify a business need, problem, or opportunity, define the nature of a solution that satisfies the identified need and justify the investment necessary to deliver the solution. Enterprise Analysis Outputs create context to requirements analysis.
• 17.
  Page 17Classification: Restricted Providescontext to requirements analysis and solution identification Often serves as the starting point for initiating a new project Business requirements are identified and documented through enterprise analysis activities Why Enterprise Analysis?
• 18.
  Page 18Classification: Restricted DifferentArchitectures The Enterprise Architecture consists of five architectures which in total comprise • Business Architecture • Information Architecture • Application Architecture • Technology Architecture • Security Architecture
• 19.
  Page 19Classification: Restricted Thankyou
• 20.
  Page 20Classification: Restricted Thankyou