[PatternD-01] Pattern ABEs Level 1

The diagram below lists the Pattern Domain's ABEs.  <br/><b>Base Types ABE</b><br/><ul>
<li>The Base Types ABE contains entities used for defining complex types of attributes like money or a date range.</li></ul>
<b>Root Business Entities ABE</b><br/><ul>
<li>The Root Business Entities ABE contains a set of common business entities that collectively serve as the foundation of the Information Framework. This set of abstract superclasses and associations provide a basis for entities in other domains of the SID Framework as well as entity interrelationships, providing greater overall coherence to the Information Framework.</li><li>In addition, this ABE contains some Basic Patterns such as Entity / Entity Specification, Entity / Entity Role and Characteristic Specification / Characteristic Value.</li></ul>
<b>Account ABE</b><br/><ul>
<li>The Account ABE contains all entities needed for specifying basic attributes and relationships that describe an account.</li></ul>
<b>Business Interaction ABE</b><br/><ul>
<li>The Business Interaction ABE represents an arrangement, contract, or communication between an enterprise and one or more other entities such as individuals and organizations (or parts of organizations). Business Interactions take on the form of requests, responses, and notifications.</li></ul>
<b>Agreement ABE</b><br/><ul>
<li>An Agreement represents a contract or arrangement, either written or verbal and sometimes enforceable by law, such as a service level agreement or a customer price agreement. An agreement involves a number of other business entities, such as products, services, and resources and/or their specifications.</li></ul>
<b>Capacity ABE</b><br/><ul>
<li>The Capacity ABE describes a pattern for specifying capacity and capacity demand from an Entity. This pattern is used for Products, Services, and Resources.</li><li>Capacity is the ability to provide some capability.  For example, one measure of network capacity is the ability of a network to provide a certain amount of bandwidth during the month of May.</li></ul>
<b>Catalog ABE</b><br/><ul>
<li>The Catalog ABE is a pattern that represents common Catalog Specification and Catalog entities, attributes, and associations shared (inherited) by components of the Entity, Federated, Product, Service, and Resource Catalog ABEs.</li></ul>
<b>Configuration and Profiling ABE</b><br/><ul>
<li>The Configuration and Profiling ABE is a pattern that represents the specification of the different possible configurations of an Entity as well as the Entity Configurations instantiated for an Entity.</li><li>This pattern provides a flexible dynamic basis for the configuration of products, services, and resources, as well as the interrelationships between these entities.</li></ul>
<b>Metric ABE</b><br/><ul>
<li>The Metric ABE specifies measurements definitions including units and values and how the values are determined.</li><li>It also includes thresholds used to evaluate the metric and the consequences of violating the thresholds. It also contains the results of measurements.</li></ul>
<b>Performance ABE</b><br/><ul>
<li>The Performance ABE is a pattern that represents a measure of the manner in which a Product and/or Service and/or Resource is functioning.</li></ul>
<b>Policy ABE</b><br/><ul>
<li>The Policy ABE represents specification of Policy (i.e. set of Policy Rules) as well as Policy Entities. It also carries information needed for managing Policies and tracking Policy application.</li></ul>
<b>Project ABE</b><br/><ul>
<li>The Project ABE represents the tools used by project managers to ensure that enterprise objectives of quality, cost and time are achieved by planning and scheduling work. It uses common industry definitions of Project, Work Breakdown Structure and Activity to provide support to project managers.</li></ul>
<b>Test ABE</b><br/><ul>
<li>The Test ABE carries all information specifying Test and the Test results. The Test ABE corresponds to a pattern that can be applied in several Domains such as Service Test ABE in the Service Domain.</li></ul>
<b>Usage ABE</b><br/><ul>
<li>The Usage ABE contains all the Entities to define Usages types specifying a type of employment of an Entity and track their records.  The Usage ABE pattern  can be applied in several Domains such as Product Usage ABE in the Product Domain. For example, Product Usage Specification enables describing different types of usages enabled by a type of Product such as SMS, MMS, Voice call... enabled by a Mobile Line Product Specification.</li></ul>
<b>Segmentation ABE</b><br/><ul>
<li>The Segmentation ABE contains all entities used for specifying rules to divide a large set of Entities instances into subsets according to criteria. These subsets are called segments.</li></ul>
<b>Intent ABE</b><br/><ul>
<li>The Intent ABE contains the entities needed for specifying basic attributes and relationships that describe an Intent.</li></ul>
<b>Closed Loop ABE</b><br/><ul>
<li><font color="#29313b">The Closed Loop ABE describes a "management framework" in which current outcomes are used to improve future outcomes in order to achieve specified goals. The management framework includes the feedforward workflow and a feedback workflow, where the feedforward is a control loop meant to continually optimize and improve</font></li></ul>
<b>Goal ABE (Preliminary)</b><br/><ul>
<li>Goal ABE represents a set of information that captures the definition of a goal or target for a process (task/activity/workflow/etc.) to reach or achieve.</li></ul>
<font color="#29313b"><b>Workflow ABE </b></font><b>(Preliminary)</b><br/><ul>
<li>A Workflow represents a set of business activities orchestrated together based on a set of goals/objectives and specific partyRoles that collectively through them a piece of work passes from initiation to completion. A workflow ties business activities together in sequence to enable realize specified objectives.</li><li>The Workflow ABE contains all information enabling the definition of Workflow Specifications and Workflows.</li></ul>
<b>Anomaly ABE</b><br/><ul>
<li>Anomaly ABE represents any unusual or unexpected event, observation, pattern, or item that is significantly different from the norm that an enterprise wishes to detect, analyze, assess and mitigate within an autonomous environment.</li></ul>
<b>Topology ABE (not fully developed)</b><br/><ul>
<li>The Topology ABE enables specifying Graphs and their instantiation.</li><li>Graphs are mathematical structures used to model pairwise relations between objects. A graph in this context is made up of Vertices (also called nodes or points) which are connected by Edges (also called arcs, links or lines) [ ref graph theory - Wikipedia ].</li></ul>
<b>Event ABE (not fully developed)</b><br/><ul>
<li>The Event ABE contains entities that are used to represent events, their occurrence and their recording within systems.</li></ul>
<b>Trouble Ticket ABE (not fully developed)</b><br/><ul>
<li>Trouble Ticket ABE represents a record used for reporting and managing the resolution of Trouble or Problem..</li></ul>
<b>Trouble or Problem ABE (not fully developed)</b><br/><ul>
<li>Trouble or Problem ABE collects all information describing a problem that can be shared between several PartyRoles such as the service provider and the customer. Trouble or Problem is an indication that an entity (such as Resource, Service or Product) is no longer functioning according to the expected SLA.</li></ul><p/>