component diagram shows the 3 layers of
user layer (interface)
login layer (business rules)
data layer (database)
* Use of interfaces and menus guide who had created the interface design class -> identity + state + behavior
denormalization: process by which one goes back in the process of normalization and accepted levels of redundancy and data dependencies in order to improve the perfomance of Data - Entity (instance, records)
Object properties: "encapsulation: objects hide their attributes, state and behavior of other objects. - Inheritance: an object can inherit attributes and behavior of other objects. - Overriding: ownership (of some languages) by which change or modify the inherited, inheritance is rejected. --composition: an object can be composed of other objects created that any action on the whole also affect the parties (propagation). - Polymorphism, polymorphism, an object or different objects respond or operate differently d (method) to a single message.
- Wheat procediemineo running cuandose meets one condition. - An association provides for the possibility of passing messages between the 2 objects associated classes.
when associated with 2 subjects or 2 classes the association can be:-bi (you can do but more time means more ode etc) (the objects of both classes can send messages). -way (is the best, only objects of a class can send messages to the objects of the associated class)
association class: only submit CUNADO in the ratio of long to many single instance is generated. mensaje:is the invocation of an operation from an object from one class to another class of some object with which this partnership. ----- Message type: - synchronous: sender waits asynchronous receiver-response: sender does not wait for the receiver's response. "Timeout: receiver has a time limit to respond to the sender. -emitter control messages according to receiver's response.
propagation property - composition: what happens when everything goes to parties, always when the parties are contained in the whole.