37451560
Descripción
Fichas por JACKSON BOEVE, actualizado hace más de 1 año
|
|
Creado por JACKSON BOEVE
hace más de 2 años
|
|
| Pregunta | Respuesta |
| Aggregation Relationship | A special-purpose UML notation represents the relationship between two classes often considered together, such as when a sports league comprises a collection of teams. |
| Association | UML symbol depicts the relationship between two classes, modeled as a solid line connecting two types in a model. |
| Attributes | Data elements that describe instances in a class, like fields in a database table, characteristics, properties, or adjectives that define each type. |
| Business Rule | Concise statements of constraints on business processes; provide the logic that guides the behavior of the business in specific situations. |
| Cardinalities | See multiplicities. Multiplicities- UML symbols that describe the minimum and the maximum number of times an instance of one class can be associated with cases of another class for a specific association between those two classes; they indicate whether the two classes are part of one-to-one, one-to-many, or many-to-many relationships. |
| Class | Any separately identifiable collection of things (objects) about which the organization wants to collect and store information. Classes can represent organization resources (e.g., trucks, machines, buildings, cash, investments), persons (e.g., customers, employees), events (e.g., sales, purchases, cash disbursements, cash receipts), and conceptual structures (e.g., accounts, product categories, budgets). Classes are typically implemented as tables in a relational database, where individual class instances are represented as rows in the table. |
| Class Diagrams | Structure models were prepared using UML notation. |
| Composition Relationship | A special-purpose UML notation represents the relationship between two classes that are often considered together, similar to aggregation relationships. In composition relationships, one class cannot exist without the other, such as a book and the chapters that compose the text. |
| Constraints | Optional or mandatory guidance about how a process should perform in certain situations. |
| Data Models | A graphic representation of the conceptual contents of databases; data models support communication about database contents between users and designers of the database. |
| Entities | The people, things, and events in the domain of interest; in UML notation, entities are modeled as classes. |
| Foreign Key (FK) | Attribute that allows database tables to be linked; foreign keys are the primary keys of other tables placed in the current table to support the link between the two tables. |
| Generalization Relationship | A special-purpose UML symbol supports grouping things that share common characteristics; it reduces redundancy because the shared characteristics need only be modeled once. |
| Multiplicities | UML symbols that describe the minimum and the maximum number of times an instance of one class can be associated with cases of another class for a specific association between those two classes; they indicate whether the two classes are part of one-to-one, one-to-many, or many-to-many relationships. |
| Primary Key (PK) | An attribute or a combination of features uniquely identifies an instance of a class in a data model or a specific row in a table. |
| Relationship | The business purpose for the association between two classes or two database tables; see association. |
| Structure Model | A conceptual depiction of a database, such as a UML class or entity-relationship model. |
¿Quieres crear tus propias Fichas gratiscon GoConqr? Más información.