Erstellt von Joel Johnson
vor etwa 2 Jahre
|
||
Frage | Antworten |
Access Controls | Limit who can use and change records in the system; for example, passwords control who can use an application. |
Accounts Receivable | Monies owed by customers for prior sales of goods or services. In a data modeling context, accounts receivable are calculated as each customer’s sales less corresponding cash receipts. |
Agents | The people or organizations, such as customers or salespeople, who participate in business events. |
Application Controls | Specific to a subsystem or an application to ensure the validity, completeness, and accuracy of the transaction. |
Cash | The organization’s monies in bank or related accounts. The instances of the class are individual accounts. This is considered a resource. |
Cash Receipts | Record receipts of cash from external agents (e.g., customers) and the corresponding deposit of those receipts into cash accounts. This is considered an event. |
Choreography | The science of examining raw data (now often Big Data), removing excess noise from the dataset, and organizing the data with the purpose of drawing conclusions for decision making. |
Collaboration | A BPMN model showing two participant pools and the interactions between them within a process. |
Customer | The external agent in the sales and collection process. |
Error Event | An intermediate event in a BPMN model showing processing for exceptions to the normal process flow. |
Events | (UML) Classes that model the organization’s transactions, usually affecting the organization’s resources, such as sales and cash receipts; (BPMN) important occurrences that affect the flow of activities in a business process, including start, intermediate, and end events. |
Many-to-Many Relationship | Exists when instances of one class (e.g., sales) are related to many instances of another class (e.g., inventory) and vice versa. These relationships are implemented in Access and relational databases by adding a linking table to convert the many-to-many relationship into two one-to-many relationships. |
One-to-Many Relationship | Exists when instances of one class are related to multiple instances of another class. For example, a customer can participate in many sales, but each sale involves only one customer. |
Orchestration | In BPMN, the sequence of activities within one pool. |
Product | Class representing the organization’s goods held for sale—that is, the organization’s inventory. This is considered a resource. |
Quote | Description of the products and/or services to be provided to a customer if ordered. |
REA | Resource-event-agent framework for modeling business processes, originally developed by William McCarthy. |
Resources | Those things that have economic value to a firm, such as cash and products. |
Sales | Events documenting the transfer of goods or services to customers and the corresponding recognition of revenue for the organization. |
Sales Order | Event documenting commitments by customers to purchase products. The sales order event precedes the economic event (sale). |
Subprocess | Represent a series of process steps that are hidden from view in BPMN. The use of subprocesses in modeling helps reduce complexity. |
Type Image | Class that represents management information (such as categorizations, policies, and guidelines) to help manage a business process. Type image often allows process information to be summarized by category. |
Möchten Sie mit GoConqr kostenlos Ihre eigenen Karteikarten erstellen? Mehr erfahren.