1. The principles of an object oriented software development process Week 04 1

2. Objectives 1.Recognize the benefits of a software development process 2.Describe the stages of Rational Unified Process (RUP) 2 Describe the stages of Rational Unified Process (RUP)

3. Advantages of efficient software development methodology 1. Since significant effort is put into recording and analyzing customer’s needs and producing a requirements document, the chances of large requirement changes should be minimal during a phased delivery which increases confidence that each delivery will be on time. 3

4. 2. The length of time between deliveries is longer Requirement can change more useful and meaningful functionality can be provided to the customer. 4

5. 3. The developers always know where they are going. A functional specification document is produced as well as pseudo code which is used to design the software. Programmer has opportunity to think about the code and design the code well from the start. 4. They can provide quality product with minimum errors or error free. 5

6. Software development stages 1.Requirement specification and analysis 2.Design 3.Implementation 4.Testing 5.Maintenance

7. A development process Unified Software Development process(DSDP) – USDP has been developed by the team that created UML. It is claimed that the USDP embodies much of the currently accepted best practice in information systems development – These include: Iterative and incremental development. Component-based development; Requirements driven development; Configurability; Architecture centrism; Visual modeling techniques

8. Unified Process The Unified Process or Rational Unified Process (RUP) is a framework for object oriented software engineering using UML. This is a use-case driven, architecture centric, iterative and incremental software development model. Planning Communication Modeling ConstructionDeployment Software Increment Inception Elaboration ConstructionTransition Release Production

9. Unified Process Inception Phase The Inception Phase of UP includes both customer communication and planning activities. By collaborating with the customer and end-users, business requirements for the software are identified, a rough architecture for the system is proposed, and a plan for the iterative, incremental nature of the project is developed.

10. Unified Process Elaboration Phase The Elaboration Phase encompasses the planning and modeling activities of the generic process model. Elaboration refines and expands the primary use-cases that were developed as part of the inception phase and expands the architectural representation to include five different views of the software – the use-case model, the analysis model, the design model, the implementation model and the deployment model.

11. Unified Process Construction Phase The construction phase of the UP is identical to the construction activity defined in the generic software process. Using the architectural model as input, the construction phase develops or acquires the software components that will make each use- case operational for end-users. As components are developed unit tests are designed and executed for each component. Integration testing and acceptance testing are carried out using use-cases to derive required test cases.

12. Unified Process Transition Phase The Transition Phase of the UP encompasses the later stages of the generic construction activity and the first part of the generic deployment activity. Software is given to end-users for beta testing. The software team creates necessary support information (user manual, installation manual etc.). At the end of transition phase, the software increment becomes a usable software release. Production Phase The production phase of the UP coincides with the deployment activity of the generic process. During this phase, the on going use of the software is monitored, support for operating environment is provided, and defect reports and requests for change are submitted and evaluated.

13. Unified Process It is likely that at the same time the construction, transition and production phases are being conducted, work may have already begun on the next software increment. This means that the unified process do not occur in a sequence, but rather with staggered concurrency.

14. Major work products produced for each UP phases. Inception Phase Vision document Initial use-case model Initial risk assessment Project Plan Business model Prototypes Transition Phase Delivered software increment Beta test reports General user feedback Construction Phase Design model Software components Integrated software increment Test cases Test Plan and Procedures Support documentation Elaboration Phase Use-case model Requirements functional, non-functional Analysis model Software architecture Preliminary design model Revised risk list, revised prototypes

15. USDP This approach incorporates the following characteristics. – Iterative; – Incremental; – Requirements driven – Component-based – architectural

16. Main activities 1.Requirements capture and modeling 2.Requirements Analysis 3.System design 4.Class design 5.Interface design 6.Data management design 7.Construction 8.Testing 9.Implementation

17. ActivityTechniquesKey Deliverables Requirements capture and modeling Requirements elicitation use case modeling prototype Use case model Requirements list Initial architecture Prototypes Glossary Requirements analysisCollaboration Diagrams Class and object models Analysis modeling Analysis model System designDevelopment model Component model Package modeling Architectural model Overview design and implementation architecture Class designClass and object modeling Interaction modeling State modeling Design patterns Design models

18. ActivityTechniquesKey Deliverables Interface DesignClass and object modeling Interaction modeling State modeling Package modeling Prototyping Design patterns Design models with interface specification Data Management designClass and object modeling Interaction modeling State modeling Package modeling Design patterns Design models with database specification ConstructionProgramming component reused Database DDL Programming idioms Constructed system documentation TestingProgramming test procedures Tested system ImplementationInstalled system

19. END 19