Introduction to Oosad and UML PDF

TOPIC 2 INTRODUCTION TO OOSAD AND UML  O B J E C TI VE S ▪ Describe the Object-Oriented Concept ▪ Define the term used in Object-Oriented ▪ Discuss Unified Process System Development Life Cycle 2  O B J E C T- O R IE N TE D C O NC E P T ▪ A class is t...

TOPIC 2 INTRODUCTION TO OOSAD AND UML  O B J E C TI VE S ▪ Describe the Object-Oriented Concept ▪ Define the term used in Object-Oriented ▪ Discuss Unified Process System Development Life Cycle 2  O B J E C T- O R IE N TE D C O NC E P T ▪ A class is the general template we use to define and create specific instances, or objects. ▪ An object is an instantiation of a class. ▪ Each object has attributes that describe information about the object. ▪ The behaviors specify what the object can do. 3 4  O B J E C T- O R IE N TE D C O NC E P T ▪ Methods implement an object’s behavior. ▪ Messages are information sent to objects to trigger methods. 5  O B J E C T- O R IE N TE D C O NC E P T ▪ Encapsulation is simply the combination of process and data into a single entity. ▪ Information hiding : only the information required to use a software module be published to the user of the module. One cake please! cake ▪ Inheritance, as an 2 eggs 4 cups flour information systems 1 cup milk 1 cup sugar etc....... development characteristic. Pre-heat oven to 350; Put milk, eggs, and sugar in 2 quart mixing bowl... 6  O B J E C T- O R IE N TE D C O NC E P T ▪ Subclasses inherit the appropriate attributes and methods from the superclasses above them. ▪ Inheritance makes it simpler to define classes. 7  O B J E C T- O R IE N TE D C O NC E P T ▪ Polymorphism means that the same message can be interpreted differently by different classes of objects. 8  BE N E F I TS O F O O S A D ▪ Enable analysts to break a complex system into smaller. ▪ Modularity makes systems development easier in many conditions. ▪ Save effort. ▪ Improve software quality. 9  T HE UN IF I E D PRO C E S S (U P) ▪ A specific methodology that maps out when and how to use the various Unified Modeling Language (UML) techniques. ▪ UML provides structural support for developing the structure and behavior of an information system. ▪ UP : use-case driven, architecture-centric, and iterative and incremental, a two- dimensional systems development process. ▪ The phases are inception, elaboration, construction, and transition. ▪ Phases : support an analyst in developing information systems in an iterative and incremental manner. 10  T HE UN IF I E D PRO C E S S (U P) 11  T HE WO R KF L O WS ▪ Engineering workflow : include business-modeling, requirements, analysis, design, implementation, test, and deployment workflows. ▪ Business-modeling workflow : uncovers problems and identifies potential projects within a user organization. ▪ Requirements workflow : includes eliciting both functional and nonfunctional requirements. ▪ Analysis workflow : primarily addresses the creation of an analysis model of the problem domain. ▪ Design workflow : transitions the analysis model into a form that can be used to implement the system: the design model. ▪ Implementation workflow : is to create an executable solution based on the design model (i.e., programming). 12  T HE WO R KF L O WS ▪ Testing workflow : is to increase the quality of the evolving system. ▪ Deployment workflow : includes activities such as software packaging, distribution, installation, and beta testing. ▪ Supporting workflows : include the project management, configuration and change management, and environment workflows. ▪ Project management : workflow is the only truly cross-phase workflow. ▪ Configuration and change management : workflow is to keep track of the state of the evolving system. ▪ Environment workflow : addresses the needs of use different tools and processes. 13  T HE UM L ▪ Unified Modeling Language (UML). ▪ To provide a common vocabulary of object-oriented terms and diagramming techniques rich enough to model any systems development project from analysis through implementation. ▪ A language for specifying, visualizing, constructing, and documenting the artifacts of software systems. ▪ Provides structural support for developing the structure and behavior of an information system. ▪ A standard diagramming notation. 14  THANK YOU 15