Object-oriented analysis and design (OOAD) lecture notes P.R.Engineering college

Object-oriented analysis and design (OOAD) lecture notes in Object oriented analysis and design using UML uploaded at P.R.Engineering college

Object-oriented analysis and design (OOAD) lecture notes in Object oriented analysis and design using UML at P.R.Engineering college P.R.Engineering college Staff uploaded in lecturenotes.net

Summary / document preview text:

UNIT  I

INTRODUCTION TO OOAD

 What is OOAD?

 What is UML?

What is OOAD?

• During OOA there is an emphasis on finding and describing the objects or concepts in the problem.
• (Ex) In the case of the flight information system, some of the concepts include plane, flight  and pilot.

• During OOD there is an emphasis on defining software objects and how they collaborate to fulfill the requirements.

• (Ex) a plane software object may have a tail number attribute and a get flight history  method. 
What is UML?  
UML is a language for specifying, constructing, visualizing and documenting the software system and its components. The UML is a graphical language with sets of rules and semantics, the rules and semantics of a model are expressed in English.

 Three ways to apply UML

 Three perspectives to apply UML

 The meaning of class in different perspectives

Three ways to apply UML

 UML as sketch

 UML as blueprint

 UML as programming language

UML as sketch

Informal and incomplete diagrams created to explore difficult parts of the problem or solution space, exploiting the power of visual languages.

UML as blueprint  
  
(1) Reverse engg to visualize and better understanding existing code in UML
 (Or) 
(2) Code generation (forward engg)  
   
• If reverse engg, a UML tool reads the source and generates UML packages, class and sequence diagrams. These blueprints can help the reader understand the big picture elements, structure and collaborations.

• Before programming, some detailed diagrams can provide guidance for code generation, either manually or automatically with a tool.
UML as programming language

Complete executable specification of a software system in UML, executable code will be automatically generated but is not seen or modified by developers.

Three perspectives to apply UML

 Conceptual perspective

 Specification (software) perspective

 Implementation (software) perspective

Conceptual perspective

The diagrams are interpreted as describing things in a situation of the real world or domain of interest.
Specification (software) perspective 
            The diagrams describe software abstractionscoor components with specifications . and interfaces, but no commitment to a particular implementation.

Implementation (software) perspective

The diagrams describe software implementations in a particular technology.

The meaning of class in different perspectives

In UML, a class is drawn as rectangular boxes are called classes.

 Conceptual class- real world concept or thing. A conceptual or essential perspective. 
 Software class- a class representing a specification or implementation perspective of a software component, regardless of the process or method. 
 Implementation class – a class implemented in a specific OO language such as java.

What are the unified process phases?

 Inception

 Elaboration

 Construction

 Transition

Inception

Approximate vision, business case, scope, vague estimates.

Elaboration

Refined vision, iterative implementation of the core architecture, resolution of

high risks, identification of most requirements and scope, more realistic estimates. 
Construction  
  
Iterative implementation of the remaining lower risk and easier elements, and 
preparation for deployment.  
Transition  
  
Beta tests, deployment.

Inception is not a requirements phase, rather, it is a feasibility phase, where just enough investigation is done to support a decision to continue or stop.

Similarly, elaboration is not the requirements or design phase, rather, it is a phase where the core architecture is iteratively implemented, and high risk issues are mitigated.

Inception

It is the initial step to establish a common vision and basic scope for the project. It will include analysis of perhaps 10% of the use cases, analysis of the critical non-functional requirement environment so that programming can start in the following elaboration phase.
Inception artifacts

Vision and business case

Use-case model

Supplementary specification

Glossary

Risk list and risk management plan

Prototypes and proof of concepts

Iteration plan 
Phase plan and software development plan
 
Development case

These artifacts are only partially completed in this phase. They will be iteratively refined in subsequent iterations. Name capitalization implies an officially named UP artifact.

CASE STUDY – the NextGen POS system

In this apparently straightforward problem domain, we shall see that there are interesting requirement and design problems to solve. In addition, it’s a real problem-groups really do develop POS systems with object technologies.

Use case modeling

 The UP defines the use case model within the requirements discipline. Primarily, this is the set of all written use cases; it is a model of the systems functionality and environment. 
 Use cases are text documents, not diagrams, and use case modeling is primarily an act of writing text, not drawing diagrams. 
 The use case model is not only requirement artifact in the UP. There are also the supplementary Specification, Glossary, Vision, and Business Rules. These are all useful for requirements analysis, but secondary at this point. 
 The use case model may optionally include a UML use case diagram to show the names of the use cases and actors, and their relationships. It also provides a quick way to list the use cases by name. 
Relating use cases  
Include  
  
Extend  
  
Generalization

Include relationship

Use includes when you are repeating yourself in two or more separate use cases and you want to avoid repetition.
Another motivation is simply to decompose the long use case into subunits to improve comprehension.
Another use of the include relationship is to describe the handling of an asynchronous event, such as when a user is able to, at any time, select or branch to a particular window, function or within a range of steps.

Extend relationship

The extend relationship is used when we have one use case that is similar to another use case but does a bit more. In essence, it is like a subclass.
Generalization
It is the activity of identifying commonality among concepts and defining super class (general concept) and subclass (specialized concepts) relationships.
It is a way to construct taxonomic classifications among concepts which are then illustrated in class hierarchies.
Various relationships among use cases

Classify type of 
 Appointment <<include>>  
   appointment 
     
     
   <<uses>> <<include>> 
Doctor <<extend>>    
  Doctors’  
    
    
  availability  
    Collect 
    preinformation 
 cancel   <<include>> 
 appointment   
    Fix appointment

Generalization

Validate user

Check password Voice recognition
.

UNIT  I

INTRODUCTION TO OOAD

 What is OOAD?

 What is UML?

What is OOAD?

• During OOD there is an emphasis on defining software objects and how they collaborate to fulfill the requirements.

 Three ways to apply UML

 Three perspectives to apply UML

 The meaning of class in different perspectives

Three ways to apply UML

 UML as sketch

 UML as blueprint

 UML as programming language

UML as sketch

Informal and incomplete diagrams created to explore difficult parts of the problem or solution space, exploiting the power of visual languages.

• Before programming, some detailed diagrams can provide guidance for code generation, either manually or automatically with a tool.
UML as programming language

Complete executable specification of a software system in UML, executable code will be automatically generated but is not seen or modified by developers.

Three perspectives to apply UML

 Conceptual perspective

 Specification (software) perspective

 Implementation (software) perspective

Conceptual perspective

Implementation (software) perspective

The diagrams describe software implementations in a particular technology.

The meaning of class in different perspectives

In UML, a class is drawn as rectangular boxes are called classes.

What are the unified process phases?

 Inception

 Elaboration

 Construction

 Transition

Inception

Approximate vision, business case, scope, vague estimates.

Elaboration

Refined vision, iterative implementation of the core architecture, resolution of

Inception is not a requirements phase, rather, it is a feasibility phase, where just enough investigation is done to support a decision to continue or stop.

Similarly, elaboration is not the requirements or design phase, rather, it is a phase where the core architecture is iteratively implemented, and high risk issues are mitigated.

Inception

Vision and business case

Use-case model

Supplementary specification

Glossary

Risk list and risk management plan

Prototypes and proof of concepts

Iteration plan 
Phase plan and software development plan
 
Development case

These artifacts are only partially completed in this phase. They will be iteratively refined in subsequent iterations. Name capitalization implies an officially named UP artifact.

CASE STUDY – the NextGen POS system

Use case modeling

Include relationship

Extend relationship

Generalization

Validate user

Check password Voice recognition
.

Title:
Object-oriented analysis and design (OOAD) lecture notes

Subject:
Object oriented analysis and design using UML

Institute:
P.R.Engineering college

Object-oriented analysis and design (OOAD) lecture notes P.R.Engineering college

Object-oriented analysis and design (OOAD) lecture notes in Object oriented analysis and design using UML uploaded at P.R.Engineering college

Summary / document preview text:

Modal

Are you sure to delete this information ?