Object oriented modeling
Introduction: In object-oriented modeling, a system is seen as a set of objects. Objects interact with each other through the services they provide. Some objects also interact with users through their services so that users can get the desired services. Therefore, the purpose of modeling is to identify the objects present in the problem area, by defining the class to define the class of which they enclose the information of which state and what services they provide, and relationships between the objects of different classes Identifies, such as the overall model. It is such that it supports the desired user services.
Object-oriented modeling and systems are being given a lot of attention in recent times. The root cause of this is the belief that Object Oriented systems are going to be easy to build and maintain. It is also believed that object-oriented analysis will be easy to transition into object-oriented design (and implementation), and it is more immune to change the object-oriented analysis because the object is more stable than the function.
Basic Concepts & Notations
Each object has some features, which define the object together. Separating any object from its properties is a natural method that we use to understand the system (a person is different from their properties of height, weight, etc.). In object-oriented systems, the attributes are defined by the state of an object (or state).
An attribute is a pure data value (such as integer, string, etc.), not an object. To create an object class, similar types of objects are put together. A class is essentially a type of definition, which defines the position and operation of its type of objects (and their semantics) which can be applied to those types of objects. The construction of orbits is also a common technique that is used by humans to understand systems and to differentiate between orbits.
One object also provides some services or operations. These services are the only means by which the position of the object can be modified or seen from outside. For conducting a service, a message is sent for that service. Generally, these services are defined for one class and are provided for each object in that category. Encapsulating services and features simultaneously in one object is one of the main features which separates object-oriented modeling approaches from data modeling approaches like ER diagrams.

Class structure illustrates a structure of the problem using a precise notation. In a square diagram, a square is represented as divided into three-part picture-style rectangle. The class is named after the class. The middle part lists the attributes that are close to the objects of this class.
And the third part lists the services provided by the objects of this class. To make the connection between the classes, some structures are used. The generalization-specialization structure can be used by any class to achieve all or more of the general class or certain features and services and to add more features and services. This structure is modeled in object-oriented modeling through heritage. By using a common class and by inheriting some of its features and services, adding more to it can create a class, which is a special edition of the general category. And many special classes can be made from the general category, which gives us the class hierarchy. The aggregation structure models the whole relation. One object can be made of many things; It is built through aggregation structure.
The generalization-specialization structure can be used by any class to achieve all or more of the general class or certain features and services and to add more features and services. This structure is modeled in object-oriented modeling through heritage.
Apart from these, examples of a class can be related to the objects of another category. For example, an object of class employer might be related to many things of class enterprise. If the system is to be properly modeled, then this relationship must also be caught between objects. It is captured through associations. Having a line between the two squares, a union is shown in the class diagram. The plurality of a union specifies how many instances of a class can be related to examples of second class through this union. A relation between the two classes can be one-to-one (i.e., an example of a class relates to just one instance of the other class), one-to-many, or some other special case. Having a star (*) on the line adjacent to the orbital class representing zero or more examples is a multiplicity which may be related to the example of another class.
Object-oriented modeling and systems are being given a lot of attention in recent times. The root cause of this is the belief that Object Oriented systems are going to be easy to build and maintain. It is also believed that object-oriented analysis will be easy to transition into object-oriented design (and implementation), and it is more immune to change the object-oriented analysis because the object is more stable than the function.
Basic Concepts & Notations
Each object has some features, which define the object together. Separating any object from its properties is a natural method that we use to understand the system (a person is different from their properties of height, weight, etc.). In object-oriented systems, the attributes are defined by the state of an object (or state).
An attribute is a pure data value (such as integer, string, etc.), not an object. To create an object class, similar types of objects are put together. A class is essentially a type of definition, which defines the position and operation of its type of objects (and their semantics) which can be applied to those types of objects. The construction of orbits is also a common technique that is used by humans to understand systems and to differentiate between orbits.
One object also provides some services or operations. These services are the only means by which the position of the object can be modified or seen from outside. For conducting a service, a message is sent for that service. Generally, these services are defined for one class and are provided for each object in that category. Encapsulating services and features simultaneously in one object is one of the main features which separates object-oriented modeling approaches from data modeling approaches like ER diagrams.

Class structure illustrates a structure of the problem using a precise notation. In a square diagram, a square is represented as divided into three-part picture-style rectangle. The class is named after the class. The middle part lists the attributes that are close to the objects of this class.
And the third part lists the services provided by the objects of this class. To make the connection between the classes, some structures are used. The generalization-specialization structure can be used by any class to achieve all or more of the general class or certain features and services and to add more features and services. This structure is modeled in object-oriented modeling through heritage. By using a common class and by inheriting some of its features and services, adding more to it can create a class, which is a special edition of the general category. And many special classes can be made from the general category, which gives us the class hierarchy. The aggregation structure models the whole relation. One object can be made of many things; It is built through aggregation structure.
The generalization-specialization structure can be used by any class to achieve all or more of the general class or certain features and services and to add more features and services. This structure is modeled in object-oriented modeling through heritage.
Also read
DATA FLOW MODELING
The aggregation structure models the whole relation. One object can be made of many things; It is built through aggregation structure. The representation of these in a square diagram is shown in the picture.Apart from these, examples of a class can be related to the objects of another category. For example, an object of class employer might be related to many things of class enterprise. If the system is to be properly modeled, then this relationship must also be caught between objects. It is captured through associations. Having a line between the two squares, a union is shown in the class diagram. The plurality of a union specifies how many instances of a class can be related to examples of second class through this union. A relation between the two classes can be one-to-one (i.e., an example of a class relates to just one instance of the other class), one-to-many, or some other special case. Having a star (*) on the line adjacent to the orbital class representing zero or more examples is a multiplicity which may be related to the example of another class.
from Technology development http://bit.ly/2Hoo0Zp
Comments
Post a Comment