Table of Contents
            Introduction
            Perspectives
                    Overall Organizational Intent
            Detailed Assertions
            Responsibilities
            Contributions
            QA IOCounts


Introduction:

---

Descriptions of how an organizational group works (or should work) and why are performed throughout the organization. All of these are planning initiatives. There is a set of these activities that have a difficulty finding a home. There are all the methods that help planning changes to the information systems. These methods of Business Analysis, Business Architecture, Agile Development, and many more, struggle to work effectively because of balkanized approaches and the confusion of where the business and it start and end. This model is intended to elaborate on the role of business description as a discipline, as a planning discipline, so much more needed as the ability of organization to change how it works by applying software assistance.
This Model is driven by introspection. Trying to describe the business of business with a business description method. The method used in the model is Assertion Modeling. And if it is a good method it will not get in the way of providing well thought out information.
It reflects thought in particular about the role that the Business Analysis and Business Architecture communities play in our fast changing organizations.
And it steps back to take a broader perspective of the organization. I do not think that typical analysts and architects would immediately describe themselves as planners.
This model contains assertions on the kind of initiatives undertaken, and asks where does that information to support those plans come from. And where does it persist in the organization as a whole. The roles and capabilities or these practices do not get the respect they deserve in the organization as a whole. And often their perspective is insular and introspective. Struggling to get traction in the organization by promoting a vocabulary that even the practitioners struggle to define accurately.
So this model tries to position these efforts in a broader perspective and proposes a broader way of describing an organization that provides the gl
Domain Summary:
This model includes the endeavours of Enterprise Architecture, Business Analysis, Agile Methods, Business Architecture, Requirements Analysis. The all incorporate intent of an organization, and more accurately, they are considered to address intent to change automated systems.

Note that BAG has an Architecture Maturity Model that can feed into and align as practical.
Designer Note: Separate Model from AM Strat to simplify and Isolate.
This model can also show where and how AM methods can enhance some of the assertions, Particularly the knowledgebase.
What is the scope of this model. Is it decision to change methods or how to do planning in an organization.
This should show how to do assessment of current tools for various planning initiatives can be performed.
Developing this model has shown that all these are planning initiatives that are usually considered local ( ie Architecture group just needs these to do something that they want to do).
BAG is making a pitch to incorporate BArch at a more corporate level.
Enterprise Arch did have some traction a decade ago but has eroded.
How would a senior exec perceive value and promote with verbal and resources?

If this is a good model it will show where and how scoping is done. And resourcing.
The knowledgebase is a capability.
Important in this will be assessments on capabilities of business planning.
Somewhere there is a need for a Business Philosophy section ( perhaps in AMStrat for now).

Version: 01           Modeler: RL


Perspectives

---

Perspectives provide a good way of isolating various business concerns out of the fully aligned business model itself.

Responsibilities for Strategic Planner excluded



  Overall Organizational Intent

---

Draft of pertinent decisions supporting ultimate value proposition of BA
ModelNote
It is becoming clear that the Use Cases are all decisions around planning. Thus the reference to intent. It is also clear that it is valuable to have planning exercises use the same set of information! So the coherence of the knowedgebase is important. Another observation is that many of the planning assertions bring together groups or comittees with different perpectives. Providing logical coherent perspectives helps consolidate the domain vocabulary. This is confusing and needs careful thought about the decisions and why they are being made by the auth. Problem Definition is very eclectic and non-automatable. At some point an initiative starts to gel perhaps articulated by a project charter, business case, statement of work etc. Every one of these should include an augmentation of the knowlegebase! Every initiative requires investigation and capture of current or desired state. All these business descriptions should augment eachother.


      BD01       BD02       BD03       BD04       BD05       BD06       BD07       BD08       BD09       BD10       BD12       SI01                   Diagram Name is: PI_ipojj7687934377.png


Detailed Assertions

---

Assertions Tables of Contents
By SpecID: BD01 - Present the parts and interactions of the organization BD02 - Organizational Knowledgebase BD03 - Initiative Requirements BD04 - Sprint Business Requirements BD05 - Value Proposition of Assertion Modeling BD06 - Key Performance Indicators (KPIs) Identification BD07 - Identified Problem BD08 - Capability to Define Automation Requirements BD09 - Ad-hoc Business Documents BD10 - Industry Reference Model BD11 - User Interview BD12 - Capability to do Business Architecture SI01 - Strategic Initiative or Plan	By Name: BD09 - Ad-hoc Business Documents BD08 - Capability to Define Automation Requirements BD12 - Capability to do Business Architecture BD07 - Identified Problem BD10 - Industry Reference Model BD03 - Initiative Requirements BD06 - Key Performance Indicators (KPIs) Identification BD02 - Organizational Knowledgebase BD01 - Present the parts and interactions of the organization BD04 - Sprint Business Requirements SI01 - Strategic Initiative or Plan BD11 - User Interview BD05 - Value Proposition of Assertion Modeling	By Date Created: BD09 - Ad-hoc Business Documents BD08 - Capability to Define Automation Requirements BD12 - Capability to do Business Architecture BD07 - Identified Problem BD10 - Industry Reference Model BD03 - Initiative Requirements BD06 - Key Performance Indicators (KPIs) Identification BD02 - Organizational Knowledgebase BD01 - Present the parts and interactions of the organization BD04 - Sprint Business Requirements SI01 - Strategic Initiative or Plan BD11 - User Interview BD05 - Value Proposition of Assertion Modeling

Details for each assertion including its frame .

BD01 - Present the parts and interactions of the organization

Present the parts and interactions of the organization Assess the ability of an organization to present a perspective (or perspectives) which assists in understanding of the parts and relationships, so that beneficial changes can be identified and planned. Updated: Tue Nov 19 2024 09:35:33 GMT-0800 (Pacific Standard Time)	Top Authority: Strategic Planner Owner: null Automatic: null Activity Type: capability
Sizing         Hours to comlete: 5     Why:         Yearly Repeat: 4   Why: Information Management        BD01 creates Standard Information Other Information Sources (ad hoc):	Specification (business rules) : Consider the current capabilities of the Knowlegebase and how they support the current planning initiatives at the operational and strategic level. UI Function : Modeling Status: INIT ModelNote: There are a range of improvement initiatives that may require this capability.Each may require a different perspective. These initiatives can be financial restructuring, medium goal setting, systems change, or market assessment.

Inputs: from: BD02 Organizational Knowledgebase - From BD02 -Organizational Knowledgebase A_Organizational Knowledgebase STRING More definition required here. prototype value:

Out A_Present the parts and interactions of the organization STRING -- New Desc -- prototype value:

BD02 - Organizational Knowledgebase

Organizational Knowledgebase An arranged, interrelated set of information that describes the organization from a number of planning perspectives.May be called the architecture repository. Updated: Mon Nov 18 2024 13:18:15 GMT-0800 (Pacific Standard Time)	Top Authority: Lead Architect Owner: null Automatic: null Activity Type: EXTRACTION
Sizing         Hours to comlete: 4     Why: null         Yearly Repeat: 20   Why: null Information Management        BD02 creates   Corporate Record Information Other Information Sources (ad hoc):	Specification (business rules) : Deliver captured business description. UI Function : Modeling Status: INIT ModelNote: Information from this will be complex. And depend on metamodel.Challenge to define frames, particularly for different planning initiatives.Is this the Enteprise Architeture or more?

Inputs: -

Out A_Organizational Knowledgebase STRING More definition required here. prototype value: To: BD03 Initiative Requirements To: BD01 Present the parts and interactions of the organization

BD03 - Initiative Requirements

Initiative Requirements A Requirements Document that addresses the goals of an initiative to build or acquire software. Updated: Sat Nov 02 2024 09:23:56 GMT-0700 (Pacific Daylight Time)	Top Authority: Business Analyst Owner: null Automatic: null Activity Type: FINDING
Sizing         Hours to comlete: 300     Why: May be 1 to 20         Yearly Repeat: 3   Why: null Information Management        BD03 creates Standard Information Other Information Sources (ad hoc):	Specification (business rules) : null UI Function : Modeling Status: INIT ModelNote: In an organization that develops its SW this could be at a Sprint level.The structure and layout of the REquirements (represented by the Frame) may be different for different organizations. It may be necessary to make a general summary and have an assertion that creates the frame. Thus the assertion design assertion emits updated (or added) assertions. This is facinating but may be a red herring at this point.

Inputs: from: BD02 Organizational Knowledgebase from: BD09 Ad-hoc Business Documents from: BD10 Industry Reference Model - From BD02 -Organizational Knowledgebase A_Organizational Knowledgebase STRING More definition required here. prototype value: From BD09 -Ad-hoc Business Documents From BD10 -Industry Reference Model A_Industry Reference Model STRING -- New Desc -- prototype value: A reference model such as BIZBOK or APQS? This will provide input into scoping and resourceing business intent resources

Out A_Initiative Requirements STRING variable prototype value: List of Requirements Ability to register user Ability to Deregister User To: BD08 Capability to Define Automation Requirements

BD04 - Sprint Business Requirements

Sprint Business Requirements Descriptions of requirements for sprint planning or an individual sprint. Updated: Fri Oct 25 2024 10:12:22 GMT-0700 (Pacific Daylight Time)	Top Authority: Agile Business Analyst Owner: null Automatic: null Activity Type: FINDING
Sizing         Hours to comlete: null     Why: null         Yearly Repeat:    Why: null Information Management        BD04 creates Standard Information Other Information Sources (ad hoc):	Specification (business rules) : Identify use cases, user journey, user story for requirements to define an agile sprint.Uses knowledge of decisions made and the information they need. UI Function : Modeling Status: null ModelNote: In an Assertions Knowledgebase this will be the Assertions to be implemented in an initiative. The format and structure of this frame may be governed by the ability to implement this assertion. And by the structure of the information available from the knowledgebase.

Inputs: -

Out A_Sprint Business Requirements STRING -- New Desc -- prototype value:

SI01 - Strategic Initiative or Plan

Strategic Initiative or Plan A set of decisions and their rationale for allocationg change resources or guiding organizational resource allocation. Updated: Mon Nov 18 2024 17:04:08 GMT-0800 (Pacific Standard Time)	Top Authority: Strategic Planner Owner: null Automatic: null Activity Type: FINDING
Sizing         Hours to comlete: null     Why: null         Yearly Repeat:    Why: null Information Management        SI01 creates Standard Information Other Information Sources (ad hoc):	Specification (business rules) : null UI Function : Modeling Status: INIT ModelNote: This may be determined at a comittee or workshop but is asserted by the sponsor.

Inputs: -

Out A_Strategic Initiative or Plan STRING -- New Desc -- prototype value:

BD05 - Value Proposition of Assertion Modeling

Value Proposition of Assertion Modeling The value to an organization provided by Planning methods and tools. Updated: Sun Oct 27 2024 09:40:14 GMT-0700 (Pacific Daylight Time)	Top Authority: Planning Lead Owner: null Automatic: null Activity Type: null
Sizing         Hours to comlete: 4     Why: null         Yearly Repeat: 2   Why: null Information Management        BD05 creates Standard Information Other Information Sources (ad hoc):	Specification (business rules) : State the value of having planning methods and tools.And state how well AM meets those methods and tools. UI Function : Modeling Status: INIT ModelNote: Is this the general case for planning tools and methods or is it the statement of value that AM specifically adresses.The various usecases of planning tools and how they are assessed feed this assessment.The inputs to this are the metadata. IE to assess how well you are planning you must look at Business description asserions and how well they are performed.

Inputs: -

Out A_Value Proposition of Assertion Modeling STRING -- New Desc -- prototype value: Expect this to point to: Quicker learning curve. Reduced set of different tools. Reduced cross mapping. More focussed emphasis on responsibility Understanding of Environments. Use of Simulator. Lower cost. Single source of truth Problems solved: Low barrier to entry Strong training support -- where is this?

BD07 - Identified Problem

Identified Problem -- Updated: Mon Oct 28 2024 06:43:17 GMT-0700 (Pacific Daylight Time)	Top Authority: Problem Identifier Owner: null Automatic: null Activity Type: null
Sizing         Hours to comlete: null     Why: null         Yearly Repeat:    Why: null Information Management        BD07 creates Standard Information Other Information Sources (ad hoc):	Specification (business rules) : null UI Function : Modeling Status: null ModelNote: This Assertion added to reflect many general methods for addressing business problems (particularly Lean Six Sigma.Most advocate ID problem, analyze, root cause, proposed solution, prototype, Much of this moves into a planning sphere where root cause may be revealed by knowlegebase and candidate solutions identified. AM, in this regard requires identification of responsibility, particularly in specifications for participating assertions.Methodologies seem to be weak on who performs them.

Inputs: -

Out A_Identified Problem STRING -- New Desc -- prototype value: This can be general. But more likley this identification is made in a business context perhaps at a yearly monthly daily level. Categorizing issues and problems ( and initiatives and change) is best done at the timescale level. This removes the organizational level as a guide. There may be a change at the yearly level ( taking 1 to 2 years to effect) in a small organization at the operational level. Unlikely, there may be a change at the monthly level that can be effected in a very large organization (perhaps a DEI Policy) Steps in Problem Solution STRING -- New Desc -- prototype value: When a problem is identified it will be in a context. Probably a statement by an Authority. The first step is to id the issue. Which may call upon some existing knowledgebase. Then a solution approach is chosen that might include a practice and some resources to follow it. This may be a configuration by one Auth or a more extended approach. The articulation of the problemmay be done with an AM! including resources. At some point the foreseen approach may be estimated and a first pass at scope articulated. The approaches may be new or expanded business archtecture with BIZBOK. Or a Business Case, And an assigned Sponsor (Auth charged with change). Some artifacts may exist. A project plan (and its Auth) is identified. If it goes more to the operational level then perhaps some operational documentaion/artifacts such as BPMN. (even though BIZBOK MMM may have elements) Or it may be a more local/ operational issue that can be assigned to an Agile Team. Other practices to apply are RACII, Context Diagram, Stakeholers, BPMN, Capability and Value Stream, Information Concept etc.

BD06 - Key Performance Indicators (KPIs) Identification

Key Performance Indicators (KPIs) Identification -- Updated: Mon Jan 13 2025 09:36:37 GMT-0800 (Pacific Standard Time)	Top Authority: Business Analyst Owner: null Automatic: null Activity Type: null
Sizing         Hours to comlete: null     Why: null         Yearly Repeat:    Why: null Information Management        BD06 creates Standard Information Other Information Sources (ad hoc):	Specification (business rules) : null UI Function : Modeling Status: null ModelNote: null

Inputs: -

Out

BD08 - Capability to Define Automation Requirements

Capability to Define Automation Requirements How well our organization defnes the needs to automate decisions and information flows in an organizatinal group. Updated: Sat Nov 02 2024 09:09:56 GMT-0700 (Pacific Daylight Time)	Top Authority: Planning Lead Owner: null Automatic: null Activity Type: capability
Sizing         Hours to comlete: 2     Why: null         Yearly Repeat: 1   Why: null Information Management        BD08 creates Standard Information Other Information Sources (ad hoc):	Specification (business rules) : Identify how well the team, methods and tools meet the needs to clearly articulate the automation support.This includes improve responsibility,increase user participation,ensure completeness,ensure explicit enough for implementation,ensure explicit enough to estimate,ensure advamcement to expected value can be incrementally evaluated. UI Function : Modeling Status: INIT ModelNote: The exsmple prototype can choose a general case.What is important is to identify the factors that inform this and perhaps articulate changes (intent) to improve the business of requirements.

Inputs: from: BD03 Initiative Requirements - From BD03 -Initiative Requirements A_Initiative Requirements STRING variable prototype value: List of Requirements Ability to register user Ability to Deregister User

Out A_Capability to Define Automation Requirements STRING -- New Desc -- prototype value:

BD09 - Ad-hoc Business Documents

Ad-hoc Business Documents Procedures, previous business analysis deliverables etc. Updated: Mon Nov 18 2024 13:09:15 GMT-0800 (Pacific Standard Time)	Top Authority: tbd Owner: null Automatic: null Activity Type: FINDING
Sizing         Hours to comlete: null     Why: null         Yearly Repeat:    Why: null Information Management        BD09 creates   Corporate Record Information Other Information Sources (ad hoc):	Specification (business rules) : Search and deliver documents to support an analysis request. UI Function : Modeling Status: INIT ModelNote: null

Inputs: -

Out To: BD03 Initiative Requirements

BD10 - Industry Reference Model

Industry Reference Model Standard reference models from various disciplines Updated: Wed Nov 20 2024 08:27:41 GMT-0800 (Pacific Standard Time)	Top Authority: tbd Owner: null Automatic: null Activity Type: FINDING
Sizing         Hours to comlete: null     Why: null         Yearly Repeat:    Why: null Information Management        BD10 creates Standard Information Other Information Sources (ad hoc):	Specification (business rules) : null UI Function : Modeling Status: INIT ModelNote: How do assertions that occur from a variety of sources show an Authority.

Inputs: -

Out A_Industry Reference Model STRING -- New Desc -- prototype value: A reference model such as BIZBOK or APQS? This will provide input into scoping and resourceing business intent resources To: BD03 Initiative Requirements

BD11 - User Interview

User Interview Statements by a stakeholder describing their perspective of part of a business endeavor. Updated: Wed Nov 20 2024 16:41:07 GMT-0800 (Pacific Standard Time)	Top Authority: tbd Owner: null Automatic: null Activity Type: null
Sizing         Hours to comlete: null     Why: null         Yearly Repeat:    Why: null Information Management        BD11 creates Standard Information Other Information Sources (ad hoc):	Specification (business rules) : null UI Function : Modeling Status: null ModelNote: null

Inputs: -

Out

BD12 - Capability to do Business Architecture

Capability to do Business Architecture -- Updated: Mon Jan 13 2025 09:39:10 GMT-0800 (Pacific Standard Time)	Top Authority: Strategic Planner Owner: null Automatic: null Activity Type: capability
Sizing         Hours to comlete: null     Why: null         Yearly Repeat:    Why: null Information Management        BD12 creates Standard Information Other Information Sources (ad hoc):	Specification (business rules) : null UI Function : Modeling Status: null ModelNote: null

Inputs: -

Out

Responsibilities

---

Each Authority is responsible for a number assertions, some are determined manually, others are calculated automatically.

Calculate
Automatic assertions are determined from instructions specified by the Authority. Most often these instructions are business rules translated into scripts or code modules where they are implemented.

Determine
With manual assertions The Authority is guided by the Specification. but uses their own judgement, supplied information from other sources (inputs), or the experience expected of their profession. There may be automated support to augment these manual decisions, usually they asist searching and organizing the input information, and aid in the configuration and sequencing of the output.
The Specification describing how the assessment is determined or calculated is also shown in this report.

Authorities are not job descriptions for organizational positions, but they certainly are clear duties for the various Authority given to organizational positions. The list of Authorities is the list of Stakeholders. It spans the range of those who inform or will be informed by the model set of assertions.

tbd   Default Authority
            Responsible to make the following determinations:

Determine
	BD09 - Ad-hoc Business Documents   ------ Search and deliver documents to support an analysis request.
	BD10 - Industry Reference Model   ------ null
	BD11 - User Interview   ------ null
Calculate

Strategic Planner   Responsible for effective planning activities.
            Responsible to make the following determinations:

Determine
	BD12 - Capability to do Business Architecture   ------ null
	BD01 - Present the parts and interactions of the organization   ------ Consider the current capabilities of the Knowlegebase and how they support the current planning initiatives at the operational and strategic level.
	SI01 - Strategic Initiative or Plan   ------ null
Calculate

Lead Architect   Responsible for supporting Planning initiatives.
            Responsible to make the following determinations:

Determine
	BD02 - Organizational Knowledgebase   ------ Deliver captured business description.
Calculate

Business Analyst   Responsible for producing software specifications.
            Responsible to make the following determinations:

Determine
	BD03 - Initiative Requirements   ------ null
	BD06 - Key Performance Indicators (KPIs) Identification   ------ null
Calculate

Agile Business Analyst   BA responsible for business alignment for a sprint
            Responsible to make the following determinations:

Determine
	BD04 - Sprint Business Requirements   ------ Identify use cases, user journey, user story for requirements to define an agile sprint.Uses knowledge of decisions made and the information they need.
Calculate

Planning Lead   Person responsible for effective planning initiatives and projects in an organization.
            Responsible to make the following determinations:

Determine
	BD08 - Capability to Define Automation Requirements   ------ Identify how well the team, methods and tools meet the needs to clearly articulate the automation support.This includes improve responsibility,increase user participation,ensure completeness,ensure explicit enough for implementation,ensure explicit enough to estimate,ensure advamcement to expected value can be incrementally evaluated.
	BD05 - Value Proposition of Assertion Modeling   ------ State the value of having planning methods and tools.And state how well AM meets those methods and tools.
Calculate

Problem Identifier   General purpose responsibility until problem is assigned.
            Responsible to make the following determinations:

Determine
	BD07 - Identified Problem   ------ null
Calculate

---

Contribution Appendix for Model BusInt1

QA IOCounts

---

            QA The following assertions require confirmation of missing connections:

	BD01 - Present the parts and interactions of the organization   IN: 2     OUT: 0
	BD02 - Organizational Knowledgebase   IN: 0     OUT: 2
	BD04 - Sprint Business Requirements   IN: 0     OUT: 0
	SI01 - Strategic Initiative or Plan   IN: 0     OUT: 0
	BD05 - Value Proposition of Assertion Modeling   IN: 0     OUT: 0
	BD07 - Identified Problem   IN: 0     OUT: 0
	BD06 - Key Performance Indicators (KPIs) Identification   IN: 0     OUT: 0
	BD08 - Capability to Define Automation Requirements   IN: 1     OUT: 0
	BD09 - Ad-hoc Business Documents   IN: 0     OUT: 1
	BD10 - Industry Reference Model   IN: 0     OUT: 1
	BD11 - User Interview   IN: 0     OUT: 0
	BD12 - Capability to do Business Architecture   IN: 0     OUT: 0