Systems Engineering the Product Realisation Process OR Soft Systems Methodology for Business Improvement - PowerPoint PPT Presentation

1 / 19
About This Presentation
Title:

Systems Engineering the Product Realisation Process OR Soft Systems Methodology for Business Improvement

Description:

OR Soft Systems Methodology for Business Improvement Dr Alison Boardman Elipsis Inc. Overview Process as Product Integrity Integration Institution Close Process as ... – PowerPoint PPT presentation

Number of Views:292
Avg rating:3.0/5.0
Slides: 20
Provided by: AlisonB73
Learn more at: https://www.incose.org
Category:

less

Transcript and Presenter's Notes

Title: Systems Engineering the Product Realisation Process OR Soft Systems Methodology for Business Improvement


1
Systems Engineering the Product Realisation
ProcessOR Soft Systems Methodology for Business
Improvement
  • Dr Alison Boardman
  • Elipsis Inc.

2
Overview
  • Process as Product
  • Integrity
  • Integration
  • Institution
  • Close

3
Process as Product
  • Corporate Asset
  • Differentiating -gt Essential
  • Product need SE lifecycle
  • Req Design VV Prodn Installation
  • Process need SE lifecycle
  • Req - Design VV Instantiation Institution
  • SSM can provide a SE lifecycle for Business
    Improvement

4
Checkland SSM
5
Your Turn
  • Process has become a dirty word and yet we all
    process every day. I transformed an opportunity
    to speak into these Power Point Slides
  • Question
  • Who believes in writing down the process like we
    believe in documenting the design?
  • Raise your hand if definitely believe
  • DONT raise your hand if not sure OR disagree

6
Process Integrity
  • Process Models Design Specifications
  • Process Design involves many parties
  • reps of all who do - not all are designers
  • Therefore
  • Notation must have system integrity
  • Notation must be accessible

7
Traditional Flow Chart
??
??
??
8
Increasing the Integrity
Start
  • Dependencies are justified
  • All inputs are included
  • Inputs have sources
  • Outputs have destinations
  • PLUS
  • Descriptions for Activities and Deliverables
  • Skill Types/Roles to fulfil activity
  • Ability to append procedures, templates,
    exemplars etc.

Act 2
Act 4
Finish
9
Your Turn
  • Your opinion on the merit of specifying inputs
    and outputs between activities in this way?

10
Process Integration
  • Functional Processes in Product Realisation
  • Project Management
  • Systems Engineering
  • Software Engineering
  • Hardware Engineering
  • Configuration Management
  • Quality Management
  • Procurement and Contracts
  • Finance and Administration
  • Etc.

11
Integration-Ability
START
FTN 2 Process
FTN1 Activity 1
FTN1 Activity 2
FTN 3 Process
12
Integration Protocols
Function 1
Function 2
FTN 1 Internal
Activity
AKA
Inbound Deliverable
Outbound Deliverable
FTN 2 Internal
Activity
AKA
Inbound Deliverable
Outbound Deliverable
AKA Also Known As
13
Your Turn
  • What are your thoughts on advantages or
    disadvantages of having to specify the source of
    all inputs and destinations for outputs so that
    integration of functional processes can be
    achieved?

14
Process Institution
  • Working to the Best or Next Practice youve so
    carefully designed (and VVd)
  • Degrees of Institution
  • As a personal guide unmonitored
  • Means for a team to plan and monitor status
  • Enforced Workflow (hard-wired process) e.g. ERP
    systems

15
The Middle Ground Means for team to plan and
monitor status
Start
Task Name Owner Start Finish Del
Act 1 J Bloggs xx/xx/xx xx/xx/xx
Act 2 C Choo xx/xx/xx xx/xx/xx




Act 1
Act 2
Finish
16
(No Transcript)
17
Statusing
Start
Task Name Owner Start Finish Del
Act 1 J Bloggs xx/xx/xx xx/xx/xx
Act 2 C Choo xx/xx/xx xx/xx/xx
Etc.



Act 1
Act 2
Finish
18
Discussion
  • What are your views on working this way?

19
Thanks for listening
  • alison_at_elipsis.com
  • 1 863 557 8269
Write a Comment
User Comments (0)
About PowerShow.com