Unified Software Development Process-Object-Oriented Design-Lecture 2 Slides-Computer Engineering, Slides of Object Oriented Analysis and Design

Download Unified Software Development Process-Object-Oriented Design-Lecture 2 Slides-Computer Engineering and more Slides Object Oriented Analysis and Design in PDF only on Docsity! Department of Computer Engineering 1 Sharif University of Technology Object-Oriented Design Lecturer: Raman Ramsin Lecture 2: USDP Overview Object-Oriented Design – Lecture 2 Department of Computer Engineering 2 Sharif University of Technology Software Development Methodology (SDM)  A framework for applying software engineering practices with the specific aim of providing the necessary means for developing software-intensive systems  Consisting of two main parts:  A set of modeling conventions comprising a Modeling Language (syntax and semantics)  A Process, which  provides guidance as to the order of the activities,  specifies what artifacts should be developed using the Modeling Language,  directs the tasks of individual developers and the team as a whole, and  offers criteria for monitoring and measuring a project’s products and activities Object-Oriented Design – Lecture 2 Department of Computer Engineering 5 Sharif University of Technology Phases and Iterations Inception Elaboration Construction Transition Prelim Iteration Arch Iteration Dev Iteration Trans Iteration Dev Iteration Release Release Release Release Release Release Release Release Object-Oriented Design – Lecture 2 Department of Computer Engineering 6 Sharif University of Technology Iterations and Workflows P r e l i m i n a r y I t e r a t i o n ( s ) i t e r . # 1 i t e r . # 2 i t e r . # n i t e r . # n + 1 i t e r . # n + 2 i t e r . # m i t e r . # m + 1 I n c e p t i o n E l a b o r a t i o n C o n s t r u c t i o n T r a n s i t i o n P h a s e s W o r k f l o w s A n i t e r a t i o n i n t h e e l a b o r a t i o n p h a s e Requirements Design Implementation Test Analysis Iterations Object-Oriented Design – Lecture 2 Department of Computer Engineering 7 Sharif University of Technology  Continuous integration  Not done in one lump near the delivery date  Frequent, executable releases  Some internal; some delivered  Attack risks through demonstrable progress  Progress measured in products, not documentation or engineering estimates Features of the iterative approach Object-Oriented Design – Lecture 2 Department of Computer Engineering 10 Sharif University of Technology Inception Phase  The purpose of Inception is to "get the project off the ground":  establishing feasibility - this may involve some technical prototyping to validate technology decisions or proof of concept prototyping to validate business requirements;  creating a business case to demonstrate that the project will deliver quantifiable business benefit;  capturing essential requirements to help scope the system;  identifying critical risks. Object-Oriented Design – Lecture 2 Department of Computer Engineering 11 Sharif University of Technology Inception – Concerns  The inception phase is a preparatory stage that attempts to answer the following questions: What is the purpose and objectives of the project? Is it worth the effort?  Is the project feasible (e.g. technologically, financially, with current personnel)?  Should we buy the system, or build it? Will it be developed now, or built from an existing system? What are the estimated costs and risks?  Should we proceed with the project?  This phase also deals with project planning and project management  This includes Gantt charts and plans, budgets, etc. Object-Oriented Design – Lecture 2 Department of Computer Engineering 12 Sharif University of Technology Inception – Postconditions and Deliverables Object-Oriented Design – Lecture 2 Department of Computer Engineering 15 Sharif University of Technology Elaboration and the Workflows  In the Elaboration phase, the focus in each of the core workflows is as follows:  requirements - refine system scope and requirements;  analysis - establish what to build;  design - create a stable architecture;  implementation - build the architectural baseline;  test - test the architectural baseline. Object-Oriented Design – Lecture 2 Department of Computer Engineering 16 Sharif University of Technology Elaboration - Concerns  After Elaboration, project risks are essentially eliminated  The Architecture and UI have been approved by customers and managers  Technically difficult software components have been implemented, or proof-of-concept code has been created to prove it was possible  Cost estimates are finalized, so budgets can be approved  Preliminary user manuals have been created and analyzed  Analysis, architecture and design well underway after Elaboration Object-Oriented Design – Lecture 2 Department of Computer Engineering 17 Sharif University of Technology Elaboration – Postconditions and Deliverables Object-Oriented Design – Lecture 2 Department of Computer Engineering 20 Sharif University of Technology Construction – Postconditions and Deliverables Object-Oriented Design – Lecture 2 Department of Computer Engineering 21 Sharif University of Technology Transition Phase  The purpose of Transition is the ultimate deployment of the software produced at the end of Construction:  conduct beta test and acceptance test, and correct defects;  prepare the user sites for the new software;  tailor the software to operate at the user sites;  modify the software if unforeseen deployment problems arise;  create user manuals and other documentation;  provide user consultancy;  conduct a post-project review. Object-Oriented Design – Lecture 2 Department of Computer Engineering 22 Sharif University of Technology Transition and the Workflows  We can summarize the kind of work undertaken in each workflow during Transition as follows:  Requirements - not applicable.  Analysis - not applicable.  Design - modify the design if problems emerge in testing.  Implementation - tailor the software for the user site and correct problems uncovered in testing.  Test - beta testing and acceptance testing at the user site.