{"id":7159,"date":"2022-06-02T04:14:22","date_gmt":"2022-06-02T04:14:22","guid":{"rendered":"https:\/\/www.booksofall.com\/?post_type=product&p=7159"},"modified":"2022-06-15T02:52:01","modified_gmt":"2022-06-15T02:52:01","slug":"ooad-lecture-notes","status":"publish","type":"product","link":"https:\/\/www.booksofall.com\/fr\/ooad-lecture-notes\/","title":{"rendered":"OOAD Lecture Notes"},"content":{"rendered":"

The UML is a graphical language for visualizing, specifying, constructing, and documenting the artifacts of a software-intensive system. The UML gives you a standard way to write a system’s blueprints, covering conceptual things, such as business processes and system functions, as well as concrete things, such as classes written in a specific programming language, database schemas, and reusable software components.<\/p>\n

Importance of modeling<\/h4>\n

A model is a simplification of reality. A model provides the blueprints of a system. A model may be structural, emphasizing the organization of the system, or it may be behavioral, emphasizing the dynamics of the system.<\/p>\n

Aims of modeling<\/h4>\n

We build models so that we can better understand the system we are developing.<\/p>\n

Through modeling, we achieve four<\/strong> aims.<\/p>\n

    \n
  1. Models help us to visualize a system as it is or as we want it to be.<\/li>\n
  2. Models permit us to specify the structure or behavior of a system.<\/li>\n
  3. Models give us a template that guides us in constructing a system.<\/li>\n
  4. Models document the decisions we have made.<\/li>\n<\/ol>\n

    We build models of complex systems because we cannot comprehend such a system in its entirety.<\/p>\n

    Principles of Modeling<\/h4>\n

    There are four basic principles of model<\/p>\n

      \n
    1. The choice of what models to create has a profound influence on how a problem is attacked and how a solution is shaped.<\/li>\n
    2. Every model may be expressed at different levels of precision.<\/li>\n
    3. The best models are connected to reality.<\/li>\n
    4. No single model is sufficient. Every nontrivial system is best approached through a small set of nearly independent models.<\/li>\n<\/ol>\n

      Object Oriented Modeling<\/h4>\n

      In software, there are several ways to approach a model. The two most common ways are<\/p>\n

        \n
      1. Algorithmic perspective<\/li>\n
      2. Object-oriented perspective<\/li>\n<\/ol>\n

        Algorithmic Perspective<\/h4>\n
          \n
        • The traditional view of software development takes an algorithmic perspective.<\/li>\n
        • In this approach, the main building block of all software is the procedure or function.<\/li>\n
        • This view leads developers to focus on issues of control and the decomposition of larger algorithms into smaller ones.<\/li>\n
        • As requirements change and the system grows, systems built with an algorithmic focus turn out to be very hard to maintain.<\/span><\/li>\n<\/ul>\n

          Object-Oriented Perspective<\/h4>\n
            \n
          • The contemporary view of software development takes an object-oriented perspective.<\/li>\n
          • In this approach, the main building block of all software systems is the object or class.<\/li>\n
          • A class is a description of a set of common objects.<\/li>\n
          • Every object has identity, state, and behavior.<\/li>\n
          • Object-oriented development provides the conceptual foundation for assembling systems out of components using technology such as Java Beans or COM+.<\/li>\n<\/ul>\n

            An Overview of UML<\/h4>\n
              \n
            • The Unified Modeling Language is a standard language for writing software blueprints. The UML may be used to visualize, specify, construct, and document the artifacts of a software-intensive system.<\/li>\n
            • The UML is appropriate for modeling systems ranging from enterprise information systems to distributed Web-based applications and even to hard real time embedded systems. It is a very expressive language, addressing all the views needed to develop and then deploy such systems.<\/li>\n<\/ul>\n

              The\u00a0Unified Modeling Language<\/b>\u00a0(UML<\/b>) is a general-purpose, developmental,\u00a0modeling language<\/a>\u00a0in the field of\u00a0software engineering<\/a>\u00a0that is intended to provide a standard way to visualize the design of a system.<\/sup><\/p>\n

              The creation of UML was originally motivated by the desire to standardize the disparate notational systems and approaches to software design. It was developed at\u00a0Rational Software<\/a>\u00a0in 1994\u20131995, with further development led by them through 1996.<\/sup><\/p>\n

              In 1997, UML was adopted as a standard by the\u00a0Object Management Group<\/a>\u00a0(OMG), and has been managed by this organization ever since. In 2005, UML was also published by the\u00a0International Organization for Standardization<\/a> (ISO) as an approved ISO standard.\u00a0<\/sup>Since then the standard has been periodically revised to cover the latest revision of UML.<\/sup>\u00a0In software engineering, most practitioners do not use UML, but instead produce informal hand drawn diagrams; these diagrams, however, often include elements from UML.<\/p>\n","protected":false},"excerpt":{"rendered":"