Digital Business Design, Process Modeling, and Strategic Innovation

Foundations of Business Analysis and Digital Systems

Industry Demand and Workforce Statistics

• Digital transformation across sectors has created a severe supply-demand gap for technology-skilled professionals.

• Reskilled and newly skilled technology workers must increase by $79\%$ by the year 2025.

• Australia requires $6.5 \times 10^6$ (6.5 million) digital workers over a four-year period to sustain digital growth.

• Approximately $64\%$ of Australian workers actively apply digital skills in their daily employment.

• Australian universities currently graduate only about $4000$ new technology-related students per year, resulting in a systemic labor deficit.

• Business Analysts (BAs) with strong technical backgrounds are in high demand across all industry sectors.

Definition and Role of Business Analysis

• Business Analysis is the set of tasks, knowledge, and techniques required to identify business needs and determine solutions to business problems.

• A Business Analyst serves as a vital facilitator and intermediary between affected business units, organizational stakeholders, and technical solution teams.

• BAs leverage knowledge of organizational operations and solution domains (such as information technology, process improvement, and change management) to act as advocates for business units.

• Core functions include validating business needs, ensuring clear requirements definition, and driving timely, effective solution delivery.

• BAs must successfully navigate ambiguity and rapidly altering commercial scenarios.

• Core professional questions for Information Systems (IS) professionals focus on: "How can we analyze and design better business systems?" and "What can technology do for our business?" rather than simply making technology transitions without business alignment.

Inter-Organizational Dynamics and BA Responsibilities

• Information Systems organizational relationships follow a clear stakeholder loop:

  • Client needs and concerns flow directly into the Business Analyst.

  • The BA translates client needs into validated System Requirements.

  • System Requirements are handed over to Programmers and development teams.

  • Programmers generate Prototypes and working software back to the BA and Client for validation.

• BAs fulfill explicit roles across the system design lifecycle:

  • Improving business processes via process modeling.

  • Outlining operational problems, growth opportunities, and functional solutions.

  • Gathering, analyzing, documenting, and reporting requirements to stakeholders.

  • Identifying implementation costs and potential cost savings.

  • Translating complex technical concepts into accessible language for non-technical teams.

  • Facilitating organizational transition and establishing change management frameworks.

  • Supporting digital transformation throughout the entire system lifecycle.

Digital Firms and Contextual System Requirements

• A digital firm is defined as an enterprise where virtually all significant business relationships with customers, suppliers, and employees are digitally enabled and mediated.

• Systems analysts must analyze unique business contexts prior to designing solutions; a retail store, medical practice, and hotel chain possess distinct information system requirements.

Business Processes and Organisational Operations

Mathematical Definitions and Operational Formulas

• At an enterprise level, organizational operations are structured hierarchically:   $\text{Business} = \sum \text{business process}$   $\text{Process} = \sum \text{task/activity}$

• A business process is a specific set of transactions, events, and results that can be rigorously described and documented.

• A business process is defined as a set of related, coordinated, and structured activities and tasks performed by a person, computer, or machine that help accomplish a specific organizational goal.

• Business processes represent logically related tasks developed over time to yield specific operational outcomes. They consume defined inputs and transform them into standardized outputs supported by flows of material, information, and knowledge.

• Common examples include processing an airline reservation, fulfilling a product purchase order, or updating a customer account.

Functional Business Processes across Business Units

• Manufacturing and Production: Assembling physical products, conducting quality assurance checks, and producing detailed bills of materials.

• Sales and Marketing: Identifying customer segments, building product awareness, and completing sales transactions.

• Finance and Accounting: Paying creditors, producing financial statements, and actively managing cash accounts.

• Human Resources: Recruiting new employees, evaluating job performance, and enrolling workers into corporate benefit plans.

End-to-End Business Process Models

• Sales Order Process Model: Initiated by the event Receive Sales Order, proceeds through sequential tasks (Check Customer Status $\rightarrow$ Verify Customer Credit $\rightarrow$ Enter Customer Order Data), resulting in the outcome Completed Sales Order.

• Cross-Functional Order Fulfillment: Crosses multiple departmental boundaries seamlessly:

  • Sales: Generates and submits the initial sales order.

  • Accounting: Checks customer credit, approves credit terms, and generates the formal invoice.

  • Manufacturing and Production: Assembles the ordered physical product and manages shipping logistics.

The Five Core Parts of Business Systems

• Every successful enterprise relies on five interdependent core processes:

  1. Value Creation: Identifying market needs or desires and engineering an appropriate product or service.

  2. Marketing: Generating awareness and developing active market demand.

  3. Sales: Converting prospective leads into paying transactions.

  4. Value Delivery: Fulfilling promotional promises and ensuring customer satisfaction.

  5. Finance: Generating sufficient revenue and profit margins to maintain long-term operations.

• Removing any single element prevents the business from operating successfully; each part requires distinct functional representation in process maps.

Core Enterprise Process Architecture

• Large corporate entities typically manage ten primary business process categories:

  • Customer Strategy and Relationships (Marketing)

  • Employee Development and Satisfaction

  • Quality, Process Improvement, and Change Management

  • Financial Analysis, Reporting, and Capital Management

  • Management Responsibility

  • Customer Acquisition (Sales)

  • Product Development

  • Product/Service Delivery

  • Accounting Management

  • Technology Management

Business Process Model and Notation (BPMN) Specification

Foundations and Element Categories

• Business Process Model and Notation (BPMN) is an internationally recognized, vendor-neutral standard for modeling operational workflows using flowcharting techniques.

• BPMN bridges communication gaps between non-technical business stakeholders, business analysts, solutions architects, and software developers.

• BPMN structural elements are divided into four main categories:

  1. Swim Lanes: Pools (representing entire organizations or independent entities) and Lanes (representing internal roles, departments, or systems).

  2. Flow Objects: Events (things that happen), Activities (work performed), and Gateways (routing controls).

  3. Connecting Objects: Sequence Flows (solid line showing activity execution order), Message Flows (dashed line with open circle showing inter-pool communication), and Associations (dotted line linking artifacts to elements).

  4. Artifacts: Data Objects, Data Stores, Groups, and Text Annotations.

Diagramming Rules and Conventions

• Operational flows are mapped left-to-right and top-to-bottom.

• Tasks must follow strict object-oriented naming conventions using the [verb] + [object] standard format (e.g., Acquire Groceries, not Take care of shopping for groceries).

• Horizontal layout orientation is strongly recommended over vertical diagrams to preserve visual readability across cross-functional lanes.

Gateway Routing Logic

• Exclusive Gateway ($\mathbf{X}$): Creates mutually exclusive alternative paths. Conditions on outgoing sequence flows are evaluated sequentially; exactly one path whose condition evaluates to true is taken.

• Inclusive Gateway ($\mathbf{O}$): Evaluates all outgoing path conditions. One, several, or all paths evaluating to true are executed concurrently. When merging, an inclusive gateway acts as a synchronization barrier, holding execution tokens until all active incoming paths arrive. A designated default path executes if no conditional expressions evaluate to true.

• Parallel Gateway ($\mathbf{+}$): Creates concurrent execution paths without checking any conditions. Every outgoing sequence flow receives a token simultaneously. On converging flows, it acts as a join node, waiting for all incoming parallel tokens before releasing execution to the next step.

Hardware Retailer Shipping Process Example

• Trigger: Start event Goods to ship leads to a decision point splitting normal post from special carriers.

• Normal Post Path: Evaluates whether extra insurance is needed. If true, Take out extra insurance is executed; otherwise flow proceeds to Fill in a Post label, then Package goods.

• Special Carrier Path: Executes Request quotes from carriers, followed by Assign a carrier & prepare paperwork.

• Synchronization: Both paths merge at a Parallel Gateway ($\mathbf{+}$) into Add paperwork and move package to pick area, concluding at the End event Goods available for pick.

Sub-Processes vs. Atomic Tasks

• Task: An atomic activity representing granular work that is not broken down into further detail, performed by a person, an application, or both.

• Sub-Process: A complex, composed activity containing an internal execution sequence. Collapsed sub-processes display a small plus sign ($\mathbf{+}$) icon at the bottom border; expanded sub-processes reveal full internal workflow logic directly within the parent diagram.

Classification of Events

• Start Event: Triggers process execution. Represented by a single thin border circle. Start events can only catch signals/triggers (open icon).

• Intermediate Event: Indicates milestones or conditions occurring during process execution. Represented by a double-line border circle. Can both catch and throw triggers.

• End Event: Represents process termination or results. Represented by a single thick/bold border circle. End events can only throw results (solid filled icon).

• Specific event types include Generic, Message (envelope icon), and Timer (clock icon, such as a $10\,\text{minutes}$ timeout delay).

Process Diagrams vs. Collaboration Diagrams

• Process Diagram: Captures the internal sequence flow of a single process within a single organizational entity (one pool).

• Collaboration Diagram: Models inter-organizational workflows by showing interactions between two or more independent pools using Message Flows.

• Pizza Order Collaboration Case Study:

  • Contains a Customer pool and a Pizza Vendor pool (subdivided into Clerk, Chief, and Delivery Boy lanes).

  • Messages exchanged between pools include Pizza Order, Money, Receipt, status queries (Where is my pizza?), and operational updates (Calm customer).

  • Internal timers track delays (e.g., $60\,\text{minutes}$ elapsed trigger leading to customer inquiry).

Strategic Planning and Problem Analysis Frameworks

Alignment Principles and Strategic Levels

• Business analysis operates across two distinct organizational horizons:

  • Strategic Level: Long-term focus centered on aligning organizational capabilities and resources with overarching mission statements in changing external environments. Examples include entering new markets, automating complete end-to-end operational functions, or developing new product lines.

  • Operational Level: Immediate, short-term ($\le 1\,\text{year}$) execution focus aimed at refining daily performance. Examples include decreasing call center handling times by $5\%$, accelerating delivery fulfillment times by $3\%$, or reducing standard inventory holding levels by $6\%$

SWOT Analysis Framework

• SWOT evaluates internal and external business environments to guide strategic decision-making:

  • Strengths ($S$ - Internal): Organizational advantages, unique selling propositions (USPs), specialized talent, competitive assets, strong client relationships, optimal physical locations, or efficient internal communications.

  • Weaknesses ($W$ - Internal): Operational bottlenecks, resource constraints, high lease costs, stale market research, cash flow deficits, excess inventory retention, or poor record keeping.

  • Opportunities ($O$ - External): Favorable market trends, technological advancements, shifts in government policies, changing population demographics, local events, or unserved customer needs.

  • Threats ($T$ - External): Aggressive competitor strategies, lower-cost market alternatives, changing regulatory compliance laws, unfavorable macroeconomic downturns, or shifting consumer behaviors.

• Strategic outcome: Convert identified weaknesses and threats into strategic opportunities, or minimize their operational impact while aggressively exploiting existing competitive strengths.

Fishbone (Ishikawa) Cause-and-Effect Diagrams

• A structured team-based root-cause analysis tool designed to isolate contributing factors behind operational failures or adverse events.

• The primary problem statement is placed at the head or mouth of the fish; contributing causes are grouped along structural branch bones into primary operational categories.

• Example 1: Coffee Quality Breakdown ("Bad coffee / Coffee not hot enough")

  • People: Untrained staff, rude behavior.

  • Procedures: Outdated software systems, lack of formal training, incorrect fees charged.

  • Material: Low-quality sugar, improper coffee dosage, wet filter packaging, excess water ratio, incorrect filter sizes, spoiled cream, missing cup lids.

  • Equipment: Extended brewing cycles, outdated equipment, dirty filter baskets, unwashed cups, failed heating warmers.

• Example 2: Product Launch Failure ($6\,\text{months}$ late, cost escalation >80\%)

  • Buy-In: Rushed marketing communications, absence of sales reps on the project board.

  • Quality Control: Conflict-driven delays requiring extra hardware and testing resources due to severe performance bottlenecks.

  • Requirements Management: Lack of signed-off requirements leading to missing test scripts, unprioritized scope, and lack of stakeholder approval.

  • Development Over-run: Inaccurate work estimates, project schedule delays, late corporate re-branding efforts ($1\,\text{month}$ delay), and late layout adjustments by product managers.

Technology Trends, Discontinuities, and Prediction Strategies

Historical Prediction Failures and Technological Vision

• Tech forecasting often fails due to conservative bias or lack of vision:

  • Western Union internal memo (1876): Deemed the telephone useless for serious communication.

  • H. M. Warner, Warner Brothers (1927): Questioned why audiences would ever want actors to talk.

  • Thomas Watson, IBM Chairman (1943): Estimated global market demand for approximately five computers.

  • Ken Olson, DEC President (1977): Claimed individuals had no reason to host computers in home environments.

• Science fiction writer William Gibson summarized technological adoption: "The future is here. It’s just not widely distributed yet."

• Historical innovators were frequently condemned before their ideas gained acceptance: Christopher Columbus (spherical Earth), Giordano Bruno (burned at the stake for non-geocentric cosmology), the Wright brothers (ridiculed for mechanical flight), Andreas Vesalius (labeled a heretic for human anatomy research), William Harvey (disgraced for discovering blood circulation), and Galileo Galilei (imprisoned for heliocentrism).

Organizational Technology Adoption Models

• Managers adopt new technology using one of three primary strategies:

  1. Cautious / Wait-and-See Approach: Rejects or delays adoption due to high costs, unproven methods, or skepticism regarding return on investment.

  2. Early-Adopter / Risk-Taking Approach: Rapidly adopts emerging technologies driven by market hype without rigorous evaluation.

  3. Intermediate Evaluation Approach: Systematically evaluates technological capability against functional business needs before committing resources.

Mobile Computing, App Adoption, and Digital Platform Models

Hardware and Embedded Sensor Specifications

• Mobile computing hardware relies on integrated embedded sensors to capture contextual operational data:

  • Accelerometer: Detects phone tilt and linear directional movement without tracking rotational angles.

  • Gyroscope: Measures angular rotational velocity, changes in twist, and axial rotation.

  • Digital Compass: Uses an internal magnetometer to determine physical orientation relative to Earth's magnetic field.

  • Barometer: Measures atmospheric pressure to calculate altitude data, supporting integrated GPS performance.

Mobile App Adoption and Usage Metrics

• The mobile gaming app Draw Something set adoption records by reaching $50 \times 10^6$ ($50\,\text{million}$) downloads in $50\,\text{days}$.

• Users allocate $89\%$ of mobile media interaction time to dedicated mobile applications, compared to only $11\%$ on the mobile web.

• Comparative monthly usage metrics reflect shift toward app-centric engagement:

  • App Usage (Men): $22\,\text{hrs}\,27\,\text{mins}$ (Q4 2012) $\rightarrow$ $29\,\text{hrs}\,32\,\text{mins}$ (Q4 2013).

  • App Usage (Women): $23\,\text{hrs}\,39\,\text{mins}$ (Q4 2012) $\rightarrow$ $30\,\text{hrs}\,58\,\text{mins}$ (Q4 2013).

  • Mobile Web Usage (Men): $4\,\text{hrs}\,8\,\text{mins}$ (Q4 2012) $\rightarrow$ $3\,\text{hrs}\,45\,\text{mins}$ (Q4 2013).

  • Mobile Web Usage (Women): $4\,\text{hrs}\,30\,\text{mins}$ (Q4 2012) $\rightarrow$ $3\,\text{hrs}\,46\,\text{mins}$ (Q4 2013).

• By the end of 2013, connected mobile devices outnumbered human beings on Earth; projections estimated $50 \times 10^9$ ($50\,\text{billion}$) connected hardware devices by 2020.

Asset-Light Platform Business Models

• Digital platforms re-engineer business architecture by decoupling platform coordination from asset ownership:

  • Uber: World’s largest taxi transport provider, yet owns $0$ fleet vehicles.

  • Facebook: World’s most popular media owner, yet creates $0$ original media content.

  • Alibaba: World’s most valuable retail business, yet holds $0$ merchandise inventory.

  • Airbnb: World’s largest accommodation provider, yet holds $0$ real estate assets.

The Internet of Things (IoT), Wearable Computing, and Advanced Analytics

Mobile Health (mHealth) Ecosystem and Clinical Metrics

• Over $97000$ mHealth applications exist across $62$ app store catalogs.

• $15\%$ of mHealth apps are built specifically for healthcare professionals (covering continuing medical education, remote patient monitoring, and clinical management).

• $42\%$ of mHealth apps operate on paid commercial software models.

• The top 10 mHealth applications generate $4 \times 10^6$ ($4\,\text{million}$) free downloads and $300000$ paid downloads per day.

• A survey of $2291$ healthcare professionals (including $649$ physicians) revealed key trends:

  • $89\%$ of physicians would actively recommend a mobile health app to patients.

  • $93\%$ believe mobile health apps can improve overall patient health outcomes.

  • $93\%$ see major clinical value in linking health apps to Electronic Health Records (EHRs).

  • $52\%$ cite automated appointment alerts and reminders as a primary benefit.

  • Primary clinical areas where EHR-linked apps make measurable impacts: Preventative Care ($52\%$), Diabetes Management ($54\%$), and Medication Adherence ($65\%$).

The Quantified Self Movement and Wearable Devices

• The Quantified Self movement involves individuals utilizing tracking technologies to acquire data regarding daily personal behaviors (activity, mass, nutrition, mood, oxygen levels, and blood pressure).

• Includes domain-specific branches like Quantified Baby, which tracks feeding times, sleep durations, and nappy change intervals.

• Wearable Device Implementations:

  • Withings Wireless Blood Pressure Monitor: Captures Systolic (SYS), Diastolic (DIA), and Heart Rate (HR in BPM) metrics, transmitting data over Bluetooth to connected mobile apps.

  • Withings Smart Body Analyzer: Measures physical mass, BMI, body fat percentage, ambient temperature, and indoor air quality ($CO_2$ tracking), displaying parameters on connected mobile apps and cloud dashboards.

Internet of Things (IoT) Analytics Architecture

• Web Analytics vs. IoT Analytics: While web analytics tracks user activity on web pages, IoT analytics captures physical device metrics, environmental context, and operational interactions across dispersed connected hardware.

• Smart Refrigerator Context: Tracks contents mass/free volume (Data), door openings/ice dispenser activations (Interactions), and ambient room temperature (Context).

• Enterprise Case Study: Smart Connected Coffee Makers:

  • Research & Development (R&D): Evaluates actual usage metrics to determine component durability needs for future product revisions.

  • Marketing: Identifies heavy-use consumers to target promotional campaigns for discounted coffee filters and durable commercial models.

  • Field Service: Tracks machine operating hours to offer proactive maintenance or replacements as hardware approaches its $20000\,\text{hour}$ operational lifespan.

  • Customer Experience: Delivers individual dashboards tracking personal coffee consumption, cost savings versus commercial coffee shops, and auto-replenishment alerts for supplies.

Strategic Technology Trends Framework

• Key technology trends driving business innovation include:

  • Artificial Intelligence (AI) integrated into apps and hardware.

  • Virtual and Augmented Reality (VR/AR).

  • Blockchain distributed ledger structures.

  • Conversational systems and AI chatbots.

  • Digital mesh structures and continuous location awareness.

  • Platform matching economies.

  • Autonomous IoT fulfillment systems (delivery drones, automated handling robotics).

  • Event-aware Big Data analytics.

  • Adaptive risk-based security and self-protecting software architectures.

  • 3D Printing / Additive manufacturing.

  • Advanced, pervasive, invisible data analytics.

  • Cloud/Client architecture and Software-Defined Infrastructure (SDI).

  • Web-scale IT infrastructure.

Historical Technology Flops and Case Studies

High-Profile Product Failures

• Segway: Designed as a personal urban transporter. Steve Jobs predicted: "If enough people see the machine you won't have to convince them to architect cities around it. It'll just happen." The product failed to achieve broad commercial adoption or urban redesign.

• Google Glass: Optical head-mounted display built to show smartphone notifications on a small personal screen. Failed commercially due to privacy concerns, ergonomic issues, and unclear consumer value propositions.

• CueCat Barcode Reader: A handheld USB scanner requiring users to physically scan barcodes printed in paper magazines, connect the device to a PC, and launch website URLs. It added procedural steps compared to simply typing web addresses directly into a browser.

• Microsoft SPOT Watch (2004): Smartwatch utilizing FM radio signals to deliver MSN channel updates (weather, news, stock quotes, sports scores, instant messages). Failed to establish market viability due to platform and bandwidth limitations.