WHAT IS OBJECT?<\/p>\n
\uf0b7 In our awareness, an “object” is anything to which a concept applies.<\/p>\n
\uf0b7 Things drew from the problem domain or solution space.<\/p>\n
E.g., a living person in the problem domain, a software component in the solution space<\/p>\n
WHAT IS OBJECT ORIENTATION?<\/p>\n
\uf0e8 If any application was developed based on the following concepts then that application will comes under object orientation:<\/p>\n
Class and Object in UML<\/p>\n
UML class is a classifier which describes a set of objects that share the same<\/p>\n
\uf0fc features,<\/p>\n
\uf0fc constraints,<\/p>\n
\uf0fc semantics (meaning).<\/p>\n
An object is an individual [thing] with a state and relationships to other objects. The state of an object identifies the values for that object of properties of the object’s classifier.<\/p>\n
Message in UML<\/strong> Operation and Method in UML<\/strong> Encapsulation in UML<\/strong> Abstraction in UML<\/strong> The Unified Modeling Language (UML)<\/strong> is a general-purpose, developmental, modeling language in the field of software engineering that is intended to provide a standard way to visualize the design of a system.<\/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 Rational Software in 1994\u20131995, with further development led by them through 1996.<\/p>\n In 1997, UML was adopted as a standard by the Object Management Group (OMG), and has been managed by this organization ever since. In 2005, UML was also published by the International Organization for Standardization (ISO) as an approved ISO standard. Since then the standard has been periodically revised to cover the latest revision of UML. In 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 UML has been evolving since the second half of the 1990s and has its roots in the\u00a0object-oriented programming<\/a>\u00a0methods developed in the late 1980s and early 1990s. The timeline (see image) shows the highlights of the history of object-oriented modeling methods and notation.<\/p>\n It is originally based on the notations of the\u00a0Booch method<\/a>, the\u00a0object-modeling technique<\/a>\u00a0(OMT) and\u00a0object-oriented software engineering<\/a>\u00a0(OOSE), which it has integrated into a single language.<\/sup><\/p>\n Rational Software Corporation<\/a>\u00a0hired\u00a0James Rumbaugh<\/a>\u00a0from\u00a0General Electric<\/a>\u00a0in 1994 and after that the company became the source for two of the most popular object-oriented modeling approaches of the day:<\/sup>\u00a0Rumbaugh’s\u00a0object-modeling technique<\/a>\u00a0(OMT) and\u00a0Grady Booch<\/a>‘s method. They were soon assisted in their efforts by\u00a0Ivar Jacobson<\/a>, the creator of the\u00a0object-oriented software engineering<\/a>\u00a0(OOSE) method, who joined them at Rational in 1995.<\/sup><\/p>\n Under the technical leadership of those three (Rumbaugh, Jacobson and Booch), a consortium called the\u00a0UML Partners<\/a>\u00a0was organized in 1996 to complete the\u00a0Unified Modeling Language (UML)<\/i>\u00a0specification, and propose it to the Object Management Group (OMG) for standardization. The partnership also contained additional interested parties (for example\u00a0HP<\/a>,\u00a0DEC<\/a>,\u00a0IBM<\/a>\u00a0and\u00a0Microsoft<\/a>). The UML Partners’ UML 1.0 draft was proposed to the OMG in January 1997 by the consortium. During the same month the UML Partners formed a group, designed to define the exact meaning of language constructs, chaired by\u00a0Cris Kobryn<\/a>\u00a0and administered by Ed Eykholt, to finalize the specification and integrate it with other standardization efforts. The result of this work, UML 1.1, was submitted to the OMG in August 1997 and adopted by the OMG in November 1997.<\/sup><\/sup><\/p>\n After the first release a task force was formed <\/sup>to improve the language, which released several minor revisions, 1.3, 1.4, and 1.5.<\/sup><\/p>\n The standards it produced (as well as the original standard) have been noted as being ambiguous and inconsistent.<\/sup><\/sup><\/p>\n As with database Chen, Bachman, and ISO\u00a0ER diagrams<\/a>, class models are specified to use “look-across”\u00a0cardinalities<\/a>, even though several authors (Merise<\/a>,<\/sup>\u00a0Elmasri & Navathe<\/sup>\u00a0amongst others<\/sup>) prefer same-side or “look-here” for roles and both minimum and maximum cardinalities. Recent researchers (Feinerer,<\/sup>\u00a0Dullea et al.<\/sup>) have shown that the “look-across” technique used by UML and ER diagrams is less effective and less coherent when applied to\u00a0n<\/i>-ary relationships of order strictly greater than 2.<\/p>\n Federer says: “Problems arise if we operate under the look-across semantics as used for UML associations. Hartmann<\/sup>\u00a0investigates this situation and shows how and why different transformations fail.”, and: “As we will see on the next few pages, the look-across interpretation introduces several difficulties which prevent the extension of simple mechanisms from binary to\u00a0n<\/i>-ary associations.”<\/p>\n UML 2.0 major revision replaced version 1.5 in 2005, which was developed with an enlarged consortium to improve the language further to reflect new experience on usage of its features.<\/sup><\/p>\n Although UML 2.1 was never released as a formal specification, versions 2.1.1 and 2.1.2 appeared in 2007, followed by UML 2.2 in February 2009. UML 2.3 was formally released in May 2010.<\/sup>\u00a0UML 2.4.1 was formally released in August 2011.<\/sup>\u00a0UML 2.5 was released in October 2012 as an “In progress” version and was officially released in June 2015.<\/sup>\u00a0Formal version 2.5.1 was adopted in December 2017.<\/sup><\/p>\n There are four parts to the UML 2.x specification:<\/p>\n Until UML 2.4.1, the latest versions of these standards were:<\/sup><\/p>\n Since version 2.5, the UML Specification has been simplified (without Superstructure and Infrastructure), and the latest versions of these standards are now:[21]<\/a><\/sup><\/p>\n It continues to be updated and improved by the revision task force, who resolve any issues with the language.<\/p>\n","protected":false},"excerpt":{"rendered":"
\nA message defines a specific kind of communication between lifelines of an interaction. A communication can be, for example, invoking an operation, replying back, creating or destroying an instance, raising a signal. It also specifies the sender and the receiver of the message.<\/p>\n
\nAn operation has a signature, which may restrict the actual parameters that are possible.
\nMethod is defined as the implementation of an operation. It specifies the algorithm or procedure associated with an operation.<\/p>\n
\nObject is defined as an entity with a well-defined boundary and identity that encapsulates state (attributes and relationships) and behavior (operations, methods, and state machines).<\/p>\n
\nAbstraction in UML corresponds to the concept of abstraction in OOD. UML provides different types (subclasses) of abstraction, including realizations (i.e. implementations).<\/p>\nBefore UML 1.0<\/span><\/h3>\n
UML 1.x<\/span><\/h3>\n
Cardinality notation<\/span><\/h4>\n
UML 2<\/span><\/h3>\n
\n
\n
\n