1. Object Oriented Analysis and Design
Software Development Process

2. Advantages of Efficient Software Development methodology
Minimum requirement changes which increases confidence that each delivery will be on time.
The length of time between deliveries is longer compared to most agile methods, which reduces costs since delivering software has overhead associated with it.

3. Advantages of Efficient Software Development methodology
Producing a requirements document, specification document, a design document (pseudo code / diagram) gives the developer opportunity to think about the code and design the code well from the start.
Bug fixing and code changes can be done faster and more efficiently which saves time and money.

4. Advantages of Efficient Software Development methodology
If the developer is sick, on vacation or leave the project, a substitute developer can be assigned the work
Developer can focus on designing and writing the code and not spend any time on the tests until all the code is written

5. Unified Software Development Process(USDP)
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.

6. Unified Software Development Process(USDP)
USDP embodies
Iterative and incremental development.
Component based development
Requirements driven development
Configurability
Architecture centrism
Visual modeling techniques

7. Main Activities in USDP
Activity
Technique
Deliverable
Requirement capturing
Use case modeling
Initial use case model
Requirements analysis
Class and object models
Analysis modeling
Analysis model
System design
Component model
Package modeling
Architectural model
Overview design and implementation architecture
Class design
Class and object modeling Interaction modeling
State modeling
Design patterns
Design models
Data Management design
Class and object modeling
Interaction modeling
Design models with database specification

8. Main Activities in USDP
Activity
Technique
Deliverable
Interface Design
Class and object modeling
Interaction modeling
State modeling
Package modeling
Prototyping
Design patterns
Design models with interface specification
Construction
Component reuse, DDL
Constructed system documentation
Testing
Test procedures
Tested system
Implementation

9. Unified Software Development Process(USDP)
The Unified Software Development Process or Unified Process is a iterative and incremental software development process framework. The best-known and extensively documented refinement of the Unified Process is the Rational Unified Process (RUP). Other examples are OpenUP and Agile Unified Process.

10. Rational Unified Process
Rational Unified Process is a software development process from Rational Software, a division of IBM for object oriented software development in UML. RUP is a specific implementation of the Unified Process. This is a use-case driven, architecture centric, iterative and incremental software development model. It divides the development process into four distinct phases that each involve business modeling, analysis and design, implementation, testing, and deployment. 

11. Rational Unified Process
Inception
Construction
Transition
Production
Elaboration

12. Phases in RUP Inception Phase:
It 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.

13. Phases in RUP Inception Phase: Major work products Vision document
Initial use case model
Initial risk assessment
Project Plan
Business model
Prototypes

14. Phases in RUP Elaboration Phase:
This 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.

15. Phases in RUP Elaboration Phase: Major Work Products Use-case model
Requirements functional, non-functional
Analysis model
Software architecture
Preliminary design model
Revised risk list, revised prototypes

16. Phases in RUP 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.

17. Phases in RUP Construction Phase : Major Work Products Design model
Software components
Integrated software increment
Test cases
Test Plan and Procedures
Support documentation

18. Phases in RUP 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.

19. Phases in RUP Transition Phase : Major Work Products
Delivered software increment
Beta test reports
General user feedback

20. Phases in RUP 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.

21. Phases in RUP
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.