Published on

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. Session 1 Introduction to OOAD and UML
  2. 2. Objectives <ul><li>Discuss the basic concepts of OOA and UML </li></ul><ul><li>Discuss the concept and use of UML </li></ul><ul><li>Give a whole preview of the elements of UML, and use simple examples to explain the function of UML </li></ul>
  3. 3. Object Oriented Analysis and Design (OOA&D) <ul><li>Object oriented Analysis and Design refers to the analysis and design of a system based on the concepts of object orientation. </li></ul><ul><li>UML is a diagrammatic approach to model the software to be developed. </li></ul>
  4. 4. SDLC <ul><li>Software Development Life Cycle (SDLC) is a sequence of activities carried out by analyst, designers, and users to develop and implement an information system. </li></ul><ul><li>Analyst – Studies requirements </li></ul><ul><li>Designer – Designs the system </li></ul><ul><li>User – An entity </li></ul>
  5. 5. Object Oriented Analysis (OOA) <ul><li>Phase of the project during which a precise and concise model of the problem in terms of real world objects and concepts as understood by the user is developed. </li></ul><ul><li>The analysis must also identify the relevant characteristics, interactions and relations between the entities. </li></ul><ul><li>This kind of real life mapping to computer analysis is the advantage offered by the Object Oriented Analysis . </li></ul>
  6. 6. Object Oriented Design (OOD) <ul><li>Programs are organized as co-operative collections of objects. </li></ul><ul><li>The purpose of Object Oriented Design is to adapt the results of OOA phase. </li></ul><ul><li>Designer defines the responsibilities, operations attributes and relationships of one or several classes. </li></ul><ul><li>Designer also designs the database and applies normalization techniques. </li></ul><ul><li>Diagrams can be classified into static or dynamic. </li></ul>
  7. 7. Advantages of OOA&D over Traditional Analysis and Design <ul><li>Close match between what is being implemented and the actual problem. </li></ul><ul><li>Promotes reuse of objects </li></ul><ul><li>Since reuse of objects is possible, it reduces errors and maintenance problems. </li></ul><ul><li>Reuse of objects also speeds up the process of design and development. </li></ul><ul><li>Appeals to the working of human cognition, as it is our natural way of thinking. </li></ul><ul><li>Propagates data encapsulation </li></ul><ul><li>Helps to handle the complexity of software development and aids generation of adaptable and resilient software systems. </li></ul>
  8. 8. Modeling <ul><li>A model is a simplification of reality </li></ul><ul><li>Provides the blueprints of a system </li></ul><ul><li>Models may encompass detailed plans </li></ul><ul><li>A good model includes those elements that have broad abstraction. </li></ul><ul><li>Helps to visualize a system as it is or according to the need. </li></ul><ul><li>Models permit to specify the structure or behavior of a system. </li></ul><ul><li>Models give a template that guides in constructing a system. </li></ul><ul><li>Models document the decisions that have been made </li></ul>
  9. 9. SDLC Phases-1
  10. 10. SDLC Phases-2 <ul><li>Preliminary Investigation (Feasibility Study) </li></ul><ul><ul><li>An important outcome of the preliminary investigation is </li></ul></ul><ul><li>determining whether the system to be developed is feasible </li></ul><ul><li>or not. </li></ul><ul><li>Requirement Analysis (Analysis) </li></ul><ul><ul><li>Involves study of the current business system in detail and to </li></ul></ul><ul><li>find out how it works and where the improvements have to </li></ul><ul><li>be made. </li></ul>
  11. 11. SDLC Phases-4 <ul><li>Design of the System </li></ul><ul><ul><li>The design phase states how a system will meet the requirements identified during the systems analysis phase as mentioned in the Requirements Specifications. </li></ul></ul><ul><ul><li>Identification of data entry forms, data elements, reports, outputs the new system should produce, data elements and tables for database. </li></ul></ul><ul><ul><li>Sketch the form or display as expected to appear at the end of completion of the system. </li></ul></ul><ul><ul><li>Computation procedures explaining the process of deriving the output from given input. </li></ul></ul>
  12. 12. SDLC Phases-6 <ul><li>Software Construction </li></ul><ul><ul><li>Actual construction (coding) of the programs </li></ul></ul><ul><li>System Testing </li></ul><ul><ul><li>Actual software code construction </li></ul></ul><ul><ul><li>Unit Testing: White Box testing </li></ul></ul><ul><ul><li>Independent Unit Testing </li></ul></ul>
  13. 13. SDLC Phases-8 <ul><li>System Testing </li></ul><ul><ul><li>After the programs are tested individually, the system as a whole needs to be tested. </li></ul></ul><ul><ul><li>All the software modules are integrated and tested to ensure that they do not fail i.e. it will run according to specifications as mentioned in requirement specification document and in the way the users expected it to. </li></ul></ul><ul><ul><li>Special test data is prepared as input for processing and the results are examined to find out any deviations from the desired results. </li></ul></ul>
  14. 14. SDLC Phases-9 <ul><li>System Implementation </li></ul><ul><ul><li>Developed system is deployed at the user’s site for use </li></ul></ul><ul><ul><li>User personnel are trained </li></ul></ul><ul><ul><li>The data files needed by the system are constructed </li></ul></ul><ul><li>System Maintenance </li></ul><ul><ul><li>Due to environmental changes, the software may turn obsolete and it may call for modifications and enhancements for its effective use. </li></ul></ul><ul><ul><li>The activity of system maintenance may vary depending on the scale of modifications and enhancements. </li></ul></ul>
  15. 15. Model <ul><li>The language used to represent a model is called a Modeling Language. </li></ul><ul><li>Object Model can be explained as a model to represent objects of a system. </li></ul><ul><li>Principle of Model Creation </li></ul><ul><ul><li>The choice of what models to create has a profound influence on how a problem is attacked and how a solution is shaped. </li></ul></ul><ul><ul><li>No single model is sufficient. Every nontrivial system is best approached through a small set of nearly independent models. </li></ul></ul>
  16. 16. Object Oriented Model Creation <ul><li>The contemporary view of software development is an object-oriented perspective. In this approach the main building block of all software systems is the object or class. </li></ul>
  17. 17. UML in Brief <ul><li>Use-Case diagrams to illustrate user interactions with the system. </li></ul><ul><li>Class diagrams to illustrate logical structure </li></ul><ul><li>Object diagrams to illustrate objects and links </li></ul><ul><li>State diagrams to illustrate behavior </li></ul><ul><li>Component diagrams to illustrate physical structure of the software. </li></ul><ul><li>Deployment diagrams to show the mapping of software to hardware configuration </li></ul><ul><li>Interaction diagram (i.e., collaboration and sequence diagrams) to illustrate behavior. </li></ul><ul><li>Activity diagrams to illustrate the flow of events in a Use-Case. </li></ul>
  18. 18. Introduction to UML <ul><li>Some of the leading companies that have contributed towards and promoted the development of UML are </li></ul><ul><li>Hewlett – Packard </li></ul><ul><li>Microsoft </li></ul><ul><li>Oracle </li></ul><ul><li>IBM </li></ul><ul><li>Unisys </li></ul>
  19. 19. History of UML
  20. 20. Application in different systems
  21. 21. Application in Software Development Life Cycle <ul><li>Preliminary Investigation: Use Cases to capture the requirements of a customer. </li></ul><ul><li>Analysis: Class diagrams are made at real world abstract level to depict their existence and relationship. </li></ul><ul><li>Design: Classes are modeled </li></ul><ul><li>Development: Programmers refer to the various UML diagrams prepared in the design stage to understand and develop code. </li></ul><ul><li>Testing: UML has different diagrams to support testing of software. </li></ul>
  22. 22. UML Overview <ul><li>Views- would mean ‘to observe’ or ‘to examine’ </li></ul><ul><li>Diagrams- is a part of a specific view and when it is drawn it is allocated to a view. </li></ul><ul><li>Relationships- provide a pathway for communication between objects. </li></ul><ul><li>Modeling Elements- consist of symbols that help in preparing diagrams and views. </li></ul>
  23. 23. Model Elements <ul><li>Use case name </li></ul>Component Name Dependency Generalization Association Aggregation (a form of Association) Class Attributes Operations
  24. 24. “ 4+1” view
  25. 25. UML Hello World
  26. 26. Component <ul><li>Source code components (e.g., .h, .cpp files, shell scripts, data files) </li></ul><ul><li>Binary code components. Examples include: java Beans, ActiveX controls, COM objects (DLL’s and OCX’s from VB), CORBA objects) </li></ul><ul><li>Executable components (.exe’s) </li></ul><ul><li>Stereotypes (with alternatives icons) may be used to define these specific kinds of components. </li></ul>
  27. 27. Summary <ul><li>UML is a modeling tool </li></ul><ul><li>Various Diagrams of UML are used to model a system </li></ul><ul><li>UML is used many areas of applications </li></ul><ul><li>UML is used in all the phases of SDLC </li></ul><ul><li>The “4+1 view” architectural model is a simplified description (an abstraction) of a system from a particular perspective or vantage point, covering particular concerns, and omitting entities that are not relevant to this perspective. </li></ul><ul><li>Different parts of UML are </li></ul><ul><ul><li>Views </li></ul></ul><ul><ul><li>Diagrams </li></ul></ul><ul><ul><li>Relationships </li></ul></ul><ul><ul><li>Model Elements </li></ul></ul>