Object Oriented Analysis

Unit -6 Object Oriented Analysis

Iterative development means building the software step by step through repeated iterations, where each iteration goes through requirements analysis, design, implementation, and testing using object-oriented concepts.
· Each iteration adds more classes, objects, and functionality, improves the system design, and reduces risk.

· This approach allows continuous user feedback, better management of complexity, and gradual development of a robust object-oriented architecture.

·Instead of defining all requirements, OOSE focuses on identifying use cases early and refining them across iterations.

Rational Unified Process (RUP) is a structured, iterative software development process that provides guidelines for building object-oriented systems.

It divides the development life cycle into four phases—
· Inception,
· Elaboration,
· Construction,
· Transition—with each phase consisting of one or more iterations.

· RUP is use-case driven, architecture-centric, and risk-focused, meaning system requirements are captured as use cases, a strong architecture is established early, and major risks are addressed in early iterations.

· This process supports incremental development, continuous testing, and clear documentation, making it suitable for medium to large and complex software projects.

Inception phase of the Rational Unified Process (RUP), the main goal is to define the project scope and feasibility. During this phase, key system requirements are identified at a high level, major use cases are outlined, and critical risks are recognized.
· A basic business case is prepared, along with initial project planning, cost estimation, and resource allocation.

· The inception phase ensures that all have a clear understanding of the project objectives.

Understanding requirements is the process of clearly identifying and analyzing what the users expect from a software system.

· It involves gathering requirements through discussions, interviews, observations, and use cases, then organizing and validating them to avoid ambiguity.

·The goal is to understand what the system should do, not how it will be built, ensuring that the final software meets user needs and reduces the risk of errors and rework later in development.

The use case model from Inception to Elaboration in the Rational Unified Process (RUP) evolves a requirement.

· In the Inception phase, the use case model is high-level and incomplete.
· the most important use cases are identified to define the system scope and understand how users will interact with the system.

· use cases help estimate cost, identify major risks.
In the Elaboration phase, the use case model is refined and expanded. system use cases are identified and described in detail, including main flows and alternative flows. The use case model is used to validate requirements, drive system architecture, and address high-risk functionality.

Milan Tomic

Hi. I’m Designer of Blog Magic. I’m CEO/Founder of ThemeXpose. I’m Creative Art Director, Web Designer, UI/UX Designer, Interaction Designer, Industrial Designer, Web Developer, Business Enthusiast, StartUp Enthusiast, Speaker, Writer and Photographer. Inspired to make things looks better.