Analysis is a creative activity or an investigation of the problem and requirements. Design is to provide a conceptual solution that satisfies the requirements of a given problem. Object Oriented Analysis is a process of identifying classes that plays an important role in Eg. For a Book Bank System, Classes or Objects identified are Book-details, Student-details, Membership-Details.<\/p>\n Object Oriented Design is to design the classes identified during analysis phase and to provide Eg. Book Bank System<\/p>\n The Unified Process has emerged as a popular iterative software development process for building object oriented systems. The Unified Process (UP) combines commonly accepted best practices, such as an iterative lifecycle and risk-driven development, into a cohesive and welldocumented description. The best-known and extensively documented refinement of the Unified Process is the Rational Unified Process(RUP).<\/p>\n \u2022 UP is an iterative process \u2022 Tackle high-risk and high-value issues in early iterations There are 4 phases in Unified Process,<\/p>\n Inception is the initial stage of the project. Inception is not a requirements phase but it is a feasibility phase where complete investigation takes place to support a decision to continue or stop . It deals with<\/p>\n In Elaboration phase the project team is expected to capture a healthy majority of the system requirements It deals with<\/p>\n Construction phase encompasses on iterative implementation of the remaining lower risk and easier elements, and preparation for deployment.<\/p>\n","protected":false},"excerpt":{"rendered":"
\nEg. To develop a Banking system
\nAnalysis:<\/strong><\/p>\n\n
DESIGN<\/h5>\n
\nEg. For a Book Bank System
\nDesign:<\/strong><\/p>\n\n
OBJECT ORIENTED ANALYSIS (OOA)<\/h5>\n
\nachieving system goals and requirements.<\/p>\nOBJECT ORIENTED DESIGN (OOD)<\/h5>\n
\nthe relationship that exists between them that satisfies the requirements.<\/p>\n\n
OBJECT ORIENTED ANALYSIS AND DESIGN (OOAD)<\/h5>\n
\n
UNIFIED PROCESS (UP)<\/h5>\n
Reasons to use UP<\/h6>\n
\n\u2022 UP practices provide an example structure to talk about how to do, and how to learn OOA\/D.<\/p>\nBest Practices and Key Concepts in UP<\/h6>\n
\n\u2022 Engage users continuously for evaluation, feedback, and requirements
\n\u2022 Build a cohesive, core architecture in early iterations
\n\u2022 Apply use cases
\n\u2022 Provides visual modeling using UML
\n\u2022 Practice change request and configuration management.<\/p>\nUP PHASES<\/h6>\n
\n
INCEPTION<\/h5>\n
\n
ELABORATION<\/h5>\n
\n
CONSTRUCTION<\/h5>\n