A Business Ontology

This is a growing description of the parts of a business and how they relate. It connects strategic consulting, financial models, and computer system design, build, and maintenance.

100 terms.

Strategic consulting34 terms
01Strategic consulting
Helping a business choose how to solve a problem, with or without a computer system, including a financial component and financial model.
02Purpose
The reason something exists or is done.
03Vision
A description of the future you want to create.
04Mission
The work you commit to doing to serve a purpose.
05Goal
A result you want to achieve.
06Objective
A specific target that supports a goal.
07Outcome
A change that results from an action.
08Value
The benefit something provides to someone.
09Stakeholder
A person or group that affects or is affected by the work.
10Need
Something required to solve a problem or achieve a result.
11Problem
A condition that prevents a desired result.
12Opportunity
A situation that offers a chance to create value.
13Context
The surrounding conditions that shape a decision.
14Scope
The boundaries of what the work includes.
15Constraint
A limit that a decision or solution must respect.
16Assumption
Something treated as true before it is confirmed.
17Evidence
Information that supports or challenges a claim.
18Uncertainty
A lack of knowledge about conditions or outcomes.
19Risk
The possibility that uncertainty will affect a goal.
20Trade-off
Giving up one benefit to gain another.
21Priority
The importance of something relative to other things.
22Decision
A choice between possible actions.
23Principle
A guiding belief or rule for making decisions.
24Policy
A rule that directs decisions or behavior.
25Resource
Something available for use, such as time, money, or materials.
26Capability
The ability to perform a particular kind of work.
27Financial component
The costs, revenues, cash needs, and financial effects considered in strategic consulting.
28Financial model
Linked assumptions and calculations showing how a proposed approach could affect revenue, costs, profit, and cash over time.
29Alignment
Agreement between goals, choices, and actions.
30Plan
The intended actions, resources, and timing for doing work.
31Tactic
A specific action used to carry out a chosen approach.
32Roadmap
A broad sequence of intended work over time.
33Milestone
A significant point used to track progress.
34Metric
A defined measure used to assess something.
Computer system design, build, and maintenance66 terms
35Computer system
Interacting software, data, and computing resources that perform defined functions.
36Element
An individual part of a computer system.
37Relationship
A connection between elements.
38Boundary
The distinction between the computer system being designed and its users or external dependencies.
39Environment
The conditions, users, and external systems that affect a computer system.
40Subsystem
A computer system that forms part of a larger computer system.
41Structure
The arrangement of parts and their relationships.
42Function
What a system or part does.
43Behavior
How a system acts under particular conditions.
44State
The condition of a system at a particular time.
45Input
Something that enters a system.
46Output
Something a system produces or sends out.
47Process
A sequence of operations that transforms inputs into outputs.
48Flow
The movement of data, requests, or work through a computer system.
49Stock
An accumulated quantity in a system, such as stored records or queued work.
50Feedback
Information about results that influences later behavior.
51Reinforcing loop
A cycle in which a change causes further change in the same direction.
52Balancing loop
A cycle that counteracts change and moves toward a target or limit.
53Delay
The time between an action and its effect.
54Dependency
A relationship in which one thing relies on another.
55Interface
A defined way for software components, external systems, or users to interact.
56Coupling
The degree to which parts depend on one another.
57Emergence
Behavior of the whole that arises from interactions among its parts.
58Complexity
The difficulty of understanding behavior caused by many interacting parts.
59Bottleneck
The part that limits the flow of the whole process.
60Capacity
The amount a system can hold or handle under stated conditions.
61Throughput
The amount a system processes in a given time.
62Variation
Differences in conditions, behavior, or results.
63Stability
The ability to remain near or return to a condition after disturbance.
64Resilience
The ability to absorb disruption and recover essential functions.
65Adaptation
A change that helps a system operate under changed conditions.
66Control
Actions that guide a system toward a desired condition.
67Leverage point
A place where a change can strongly affect the whole system.
68Software engineering
Designing, building, testing, deploying, and maintaining computer software.
69Requirement
A condition or capability that the software must satisfy.
70Specification
A precise description of required software behavior or design.
71Design
The definition of how a computer system will work.
72Architecture
The major software components, data stores, and interfaces, and how they fit together.
73Model
A simplified representation used to understand or examine something.
74Abstraction
Keeping relevant details while leaving others out.
75Component
A distinct software part designed to perform a function.
76Module
A unit of software that groups related functions behind a defined interface.
77Prototype
An early version built to explore or test an idea.
78Experiment
A planned investigation used to test an idea.
79Simulation
Using a model to examine how something behaves under chosen conditions.
80Implementation
Turning a software design into working code and configuration.
81Integration
Connecting software components or systems so they work together.
82Test
A check of behavior or performance under specified conditions.
83Verification
Checking that a solution meets its specified requirements.
84Validation
Checking that a solution serves its intended use and users.
85Acceptance criteria
The conditions a result must meet to be accepted.
86Failure
The inability to perform a required function.
87Defect
A flaw in software, configuration, or design that can cause incorrect behavior or failure.
88Root cause
An underlying cause whose correction helps prevent a problem from recurring.
89Reliability
The ability to perform as required for a stated time under stated conditions.
90Robustness
The ability to keep working despite variation or disturbance.
91Maintenance
Keeping software useful and reliable through fixes, updates, and adaptation.
92Safety
Freedom from unacceptable risk of harm.
93Security
Protection against unauthorized access, use, damage, or disruption.
94Performance
How well a solution does its work under stated conditions.
95Efficiency
Useful output relative to the resources used.
96Scalability
The ability to handle more work as resources are added.
97Maintainability
How easily software can be understood, repaired, tested, or changed.
98Observability
How well a software system’s internal condition can be inferred from its outputs and telemetry.
99Optimization
Finding the best available solution against chosen criteria and constraints.
100Lifecycle
The stages software passes through, from initial design to retirement.

Relationships.

Strategic consulting45 relationships
SubjectRelationshipObject
StakeholderhasNeed
NeedmotivatesGoal
GoalservesPurpose
Objectivemakes specificGoal
MissionservesPurpose
VisioninformsGoal
ProblemobstructsGoal
Opportunitymay help achieveGoal
Strategic consultingpursuesGoal
Strategic consultingaddressesProblem
Strategic consultingresponds toOpportunity
Strategic consultingguidesPlan
StakeholderownsDecision
Decisionis informed byEvidence
DecisionacceptsTrade-off
PrincipleguidesDecision
PolicygovernsDecision
ConstraintlimitsDecision
Assumptionis assessed usingEvidence
PlanorganizesSoftware engineering
PlanallocatesResource
Strategic consultingselectsTactic
RoadmapordersPlan
Milestonemarks progress inPlan
OutcomeaffectsStakeholder
Outcomeis assessed againstGoal
Outcomemay createValue
Metricmeasures properties ofComputer system
Metricmeasures properties ofProcess
Metricmeasures properties ofOutcome
ContextshapesDecision
ScopeboundsPlan
Uncertaintycontributes toRisk
Riskmay affectGoal
Priorityorders attention toGoal
Capabilityis enabled byComputer system
Strategic consultingincludesFinancial component
Strategic consultingrequiresFinancial model
Alignmentdescribes consistency betweenGoal
Alignmentdescribes consistency betweenPlan
Financial modelis aModel
Financial modelmakes explicitAssumption
Financial modelquantifiesFinancial component
Financial modelinformsDecision
Financial componentinformsTrade-off
Computer system design, build, and maintenance79 relationships
SubjectRelationshipObject
Software engineeringcreates or changesComputer system
Software engineeringusesDesign
Computer systemcontainsElement
Computer systemhasBoundary
Computer systemoperates inEnvironment
Computer systemperformsFunction
Computer systemsupportsProcess
Subsystemis aComputer system
Subsystemis anElement
Componentis anElement
Elementinteracts throughInterface
Moduleexposes functions throughInterface
Architecturedescribes structure inDesign
ProcessusesResource
ProcesstransformsInput
ProcessproducesOutput
Outputcan becomeInput
Outputcontributes toOutcome
Requirementderives fromNeed
RequirementsupportsGoal
Requirementmay derive fromPolicy
Requirementmay derive fromConstraint
DesignaddressesRequirement
Specificationstates preciselyRequirement
Specificationmay describeDesign
ModelrepresentsComputer system
Prototypeembodies selected aspects ofDesign
ProcesschangesStock
FlowchangesStock
FeedbackinformsControl
Reinforcing loopis a pattern ofFeedback
Balancing loopis a pattern ofFeedback
DelayaffectsFeedback
BottlenecklimitsThroughput
DependencyconnectsElement
Couplingdescribes strength ofDependency
ExperimentproducesEvidence
SimulationusesModel
SimulationproducesEvidence
TestproducesEvidence
Verificationchecks evidence againstRequirement
Validationchecks evidence againstNeed
Acceptance criteriadefine acceptance ofOutput
Defectcan causeFailure
Root causeexplainsProblem
OptimizationusesMetric
OptimizationrespectsConstraint
RelationshipconnectsElement
Structuredescribes arrangement ofElement
Behavioris exhibited byComputer system
Statedescribes a condition ofComputer system
Emergencearises throughRelationship
ComplexitycharacterizesComputer system
Capacitylimits available room forStock
CapacityconstrainsThroughput
Variationoccurs inProcess
StabilitycharacterizesComputer system
ResiliencecharacterizesComputer system
AdaptationchangesComputer system
Leverage pointis a place for change withinComputer system
Abstractionselects relevant detail forModel
ImplementationrealizesDesign
IntegrationconnectsComponent
ReliabilitycharacterizesComputer system
RobustnesscharacterizesComputer system
Maintenancepreserves or improvesComputer system
Safetyis assessed forComputer system
SecurityprotectsComputer system
PerformancecharacterizesComputer system
Efficiencyrelates useful output toResource
ScalabilitycharacterizesComputer system
MaintainabilitycharacterizesComputer system
Observabilitysupports inference ofState
Lifecycledescribes stages ofComputer system
ControlguidesComputer system
FailureimpairsFunction
Software engineeringincludesMaintenance
MaintenanceaddressesDefect
Maintenanceresponds toRequirement