Which object should i use and in what context?

In 2c8 Apps, there are various symbols/objects available for use in modeling. Below is an explanation of how different objects are used in modeling.

 

Process: A process is a repetitive activity that can be cross-functional and measurable, performing a task. It is used at various levels of detail, from high and general levels to detailed levels. The process is named with an infinitive verb and a noun describing what happens, e.g., "Build cars," "Bake bread," "Care for patients."

 

Activity: An activity is a planned event within a process. An activity always has an executor, inherits input from the process it is part of, and always produces a result. It is part of a detailed level of a process, and its name must reflect the desired activity. Use infinitive verbs plus the object, expressed in a noun, involved in the activity. A strict standard is recommended, e.g., "Register order," "Establish application," etc.

 

Project: Used to describe a specific project with a defined start and end, a measurable goal, and a fixed budget. The project is named as it is in the organization, e.g., "Develop new offers" or "Project Via Appia."

 

Interested party: A interested party is a person or group with a relationship to and demands on the organization or vice versa. It is often a two-way relationship between two interested parties. A interested party can also be symbolized as an external executing group in a process model and is named after its official name, e.g., "Social welfare board," or as a group name like "Supplier," "Owners," and "Authorities."

 

 

Forum/Meeting: A forum is a grouping of people with a predetermined purpose and responsibility. Examples of purposes are exchanging/forwarding information, problem-solving, decision-making, follow-up/evaluating results/outcomes. Typical forums include boards, management groups, steering groups, product councils, safety committees, etc.

 

Business Object: The business object is a resource or transformation in the form of a thing or substance, or an information package. It can be used as an abstract entity related to a process, e.g., "Need for supplementation." The business object is named with a noun, often accompanied by an adverb to explain the status, e.g., "Registered order," "Raw materials available."

 

Document: Business objects can be specialized as documents if the object is, for example, a price list, schedule, etc.

 

 

Message: Business objects can be specialized as messages if the object is an electronic message.

 

 

Tool: Business objects can be specialized as tools if the object is a physical resource/equipment used by a process/activity, e.g., measuring machine, lathe, conveyor belt, truck, calculation program.

 

Requirement: A requirement is a specific attribute defined for a process, business object, or role, issued by a stakeholder, organization, or process. A requirement is named with imperative verb form, e.g., Achieve, Reduce, Increase + direction. For example, "Improve delivery accuracy" and "Reduce waste quantity."

 

Goal: Goals express a future desirable state for an organization, department, process, project, individual, etc. Described according to the SMART model: Specific, Measurable, Accepted, Realistic, Time-bound. For example, "Respond to customer quotes within 3 working days" or "Less than 50 PPM defective parts delivered to the customer per year."

 

Indicator: An indicator is a gauge showing the current outcome for a goal or key performance indicator.

Organization: Used to specify an organization or department/unit/section with resources in the form of Positions, Roles, and Individuals. The organization is usually named based on the function where resources with similar competencies are found, e.g., Finance, Sales, Planning.

 

 

Position: A position is the title someone is employed in. It is a position in an organization and can be responsible for or belong to an organizational unit. A position can consist of one or more roles, e.g., CFO, Finance Assistant, System Developer, or CEO. It may vary from organization to organization whether a person's title is a position or a role, e.g., System Developer, Project Manager, Purchaser.

 

 

Role: A role is a competency or responsibility profile derived from a need in a process, project, meeting, or around an IT system, e.g., Budget Responsible, Project Member, Meeting Leader, System Manager. It may vary from organization to organization whether a person's title is a position or a role, e.g., System Developer, Project Manager, Purchaser.

 

 

Individual: An individual is a real specific person named with a personal name. An individual holds a Position, including the Roles the position consists of. Roles can be directly linked to an individual with the relations Possesses or Can perform.

 

 

Time: The time object is used to show dates/times when processes and activities are to be performed, or when business objects should be available.

 

 

Location: A physical place.

 

Application and Archive: An application is an information system that supports a process/activity, usually used in process and application models. Archive is used when the support in question is an archive of some kind. Named in accordance with traditional usage in the organization.

 

Rules (or/and/join): A rule can be used when an activity is followed by two or more activities. If several subsequent activities can be performed, "And" is used. If it is only one among several possible ones, "Or" is used. Rules are usually named as a question, a choice where the answers are written out on the relationships to subsequent activities. For example, "Quote?" or "Approved supplier?" "Join" can be used when a flow that was previously divided with a rule of the type "And" converges. It should be interpreted as all previous parallel activities must be completed before proceeding.

 

Problem/Risk/Possibility/Strength/Weakness/Note: Problems/opportunities/risks/strengths/weaknesses and notes are different indications and notes on a model or directed to specific objects. Usually used in construction and analysis.

Problem

A problem is a condition that exists here and now that is not positive and should be addressed.

Risk

A risk is something that can occur and that entails deficiencies
There is a probability of it happening and a consequence if it happens

Possibility

An opportunity is an idea for an action to reduce the likelihood or consequence of a risk, eliminate a risk, or solve a problem.

Strength

Represents something internal that is positive for the business. It can be used for SWOT analyses.

Weakness

Represents something internal that is negative for the business. IT can be used for SWOT analyses.

Note

A comment for further analysis or action at a later time.