[email protected], attributed copies permitted 1 agile architecture pattern … examples

[email protected], attributed copies permitted 1

Agile Architecture Pattern…

Examples


Infrastructure evolution

System assembly

Module mix evolution

Module readiness

Infrastructure

Configuration Y Configuration ZConfiguration X

Modules/Components

Rules/Standards

IntegrityManagement

Active

Passive

who/what?

who/what?

who/what?.

who/what?

Pool A

? ??

Pool B

? ?? ?

Pool C

????

Pool D

?? ?

Pool n

? ? ?

Next gen need?

?

? ?? ?? ? ?

? ?

?????

?????

SocketsSignalsSecuritySafetyService

System ____________________________

What?What?What?What?What?

Sample Graphics for your modification into your system needs


MotorsGears/Pulleys


System assembly


Module readiness

Infrastructure

Helicopter Mobile RadarPlane

Modules/Components

IntegrityManagement

Active

Passive

Product Manager

Owner/Builder

Product System Eng.

Retail Distribution Process

Wheels Structural MaterialJoiners, Axles,

Small PartsTools

Agile Architecture Pattern (AAP)Notional Concept: System Response-Construction Kit

Details in www.parshift.com/s/140630IS14-AgileSystemsEngineering-Part1&2.pdf

Rules/Standards Radio Control Standards

Control ProtocolParts Interconnect StandardsSockets

SignalsSecuritySafetyService

(None)Harm-Proofing StandardsProcess Rules & ConOps

http://www.parshift.com/s/140630IS14-AgileSystemsEngineering-Part1&2.pdf


CubeSat Agile Architectural Pattern

Chassis


System assembly


Module readiness

Infrastructure

JHU/APL

IntegrityManagement

Active

Passive

Cal Poly SLO

Satellite Builder

COTS Developers & CPSLO

COTS Suppliers

ElectronicsCommunications

Auburn University

SensorsPower

Modules/Components

Rules/Standards

University of Colorado

System Examples of Increasing Complexity and Chronological Order

CP SLO: Cal Poly San Luis Obispo

Dove, Rick and Ralph LaBarge. 2014. Fundamentals of Agile Systems Engineering – Part 1. International Council on Systems Engineering IS14,Los Angeles, CA, 30-Jun-03Jul. www.parshift.com/s/140630IS14-AgileSystemsEngineering-Part1.pdf


http://www.parshift.com/s/140630IS14-AgileSystemsEngineering-Part1.pdf



Assembly in SIL


Module readiness

Infrastructure

Modules

Rules/Standards

IntegrityManagement

Active

Passive

process engineer

production

system engineer

material manager

small upgrade tech refresh large re-fit

QRC Device/Power/Cooling Installation Architecture

boxes rackszones SILs aircrafthardware


Physical interconnect standardsData/power/cooling transmissionPersonnel/Sil/supply-chain/et al.Weight/space/installation rulesAgile system/process ConOps

Boss, Jason and Rick Dove. 2010. Agile Aircraft Installation Architecture In a Quick Reaction Capability Environment. INCOSE International Symposium, Chicago, July 12-15. www.parshift.com/Files/PsiDocs/Pap100712IS10-AgileAircraftInstallationArchitecture.pdf

http://www.parshift.com/Files/PsiDocs/Pap100712IS10-AgileAircraftInstallationArchitecture.pdf


Classic Scrum: an Agile Architecture Pattern (AAP) Structuresuitable for agile SW development, but not for agile systems-engineering …


System assembly


Module readiness

Infrastructure

Sprint 2 Sprint nSprint 1

Modules/Components

Rules/Standards

IntegrityManagement

Active

Passive

Product Owner (PO)

Scrum Master

PO with Team Collaboration

Developers

Product Owners DevelopersScrum Masters Stakeholders

Retrospective Change

Product Backlog

Planning, I&I Sprint, ReviewDaily Scrum, RetrospectiveFull Info TransparencyScrum Master

Process Rules & ConOps

… because the RSA is different for an agile systems-engineering process,and the Scrum AAP strategy is inadequate for systems engineering


Dove, Rick and Ralph LaBarge. 2014. Agile Systems Engineering – Part 2. International Council on Systems Engineering IS14 Conference,Los Angeles, CA, 30-Jun-03Jul. www.parshift.com/s/140630IS14-AgileSystemsEngineering-Part2.pdf

http://www.parshift.com/s/140630IS14-AgileSystemsEngineering-Part2.pdf


Task Backlog Buffer

Infrastructure evolution:

Task assembly:

Task elements:

Task readiness:

Infrastructure

Standards

IntegrityManagement

Active

Passive

Last Planner Process Manager

Supes/Foreman

Project Manager

Supes/Foremen/Expediters

Last Planner Agile Project Managementwww.parshift.com/s/130624Last Planner.pdf

Active management of the anticipated schedule and work flow to ensure there isalways a buffer of “quality” jobs ready to work on and matched with resources.

mastersched

CPMtasks materials tools

Agile architecture Pattern based on:(Ballard 1997) Lookahead Planning: the Missing Link in Production Control(Ballard 1998) Shielding Production: an Essential Step in Production Control(Ballard 1999) Improving Work Flow Reliability(Ballard 2000) The Last Planner System of Production Control-PhD Thesis

equipment

productionunits

activitydefinitions

Key Practices:Rules 1-2-3 and •Lookahead•Make ready•Learn & Correct

Work TaskTask Lookahead Window

week week week week week week6 5 4 3 2 1

Components

Task Soundness/Sequence/SizeTask Definitions Physical Site SecurityConstruction Safety Standards/RegsMaster Sched, Learning, R1-2-3


MS Learning Change

http://www.parshift.com/s/130624Last%20Planner.pdf


BSAs DepartmentsSSAs Contractors COTSApps

ETLs& BIMs


System assembly/reconfiguration


Module readiness

Infrastructure

Phase 2: Desired Phase 3: Refined

Components/Modules

Rules/Standards

IntegrityManagement

Active

Passive

Prog Mgr

Dept User

Proj Mgr

BSAs

Silterra Agile ERP – Development System


Scrum-Like Team CollaborationScrum-Like Progress/NeedsSupply Chain Protection(Team) No Req ChangesDevelopment ConOps/Rules

Phase 1: Out of Box


COTS ERP Apps

CustomOther Apps

COTSOther Apps

AppETLs

DataBases

CustomERP Apps


System assembly/reconfiguration


Module readiness

Infrastructure

Customer MyFab

Components/Modules

IntegrityManagement

Active

Passive

SSAs

Dept Users & BSAs

BSAs

BSAs

System examples are SOA-like instances of departmental needs

Silterra Agile ERP – Developed System

Planning/SchedulingEOM Financial Rpt

Rules/StandardsETL Template


API, ETL, BIM, ESBInitial XML ProtocolSEA -Appropriate StrategyPub/Sub BusArchitecture/ConOps Rules


HH

PNM Agile Substation System Design Developmentwww.parshift.com/Files/PsiDocs/Pap080404Cser2008DevOpsMigration.pdf

engineers switchgeartransformers terminationstructures

low-voltagefeeders

stationsteel


System assembly

Component evolution

Component readiness

Infrastructure

H Station Fly-Thru StationT Station

Components

Rules/Standards

IntegrityManagement

Active

Passive

chief engineer

design engineer

DASL program mgr

min/max purchaser

T T H H H

TT

Agile Architectural Pattern Diagram

SocketsSignalsSafetySecurityService

DASL module interconnectsPower flowConstruction policies/regsNo development customizationDASL design tool ConOps

H-pad standardsFly-pad standards

http://www.parshift.com/Files/PsiDocs/Pap080404Cser2008DevOpsMigration.pdf


AAP for Tassimo BrewBot In-Operation System

base units brew stepsdiscs


System assembly

Component evolution

Component readiness

Infrastructure

Components

Rules/Standards

IntegrityManagement

Active

Passive

Prod eng mgr

Automated recipe

Product eng mgr

Product mktng mgr

recipes display text

2-step lattechocolate

espressocrème

multilingual display

Disc holder, RFID placementRFID scan contentConsumer product regsIgnoredOwners manual

Sockets Signals Safety Security Service

Nov2011: www.tassimodirect.com/home-brewing-machines/hot-beverage-brewers

http://www.tassimodirect.com/home-brewing-machines/hot-beverage-brewers



System assembly:

Module evolution:

Module readiness:

Infrastructure

Drag & Drop Components

Plug & Play Standards

IntegrityManagement

Active

Passive

Configuration-Process Team

Production Teams

Component Team

Component Team

P41 Deck Lid System

• Area B

A47 Fender

A47 Fender System

• Area A

Hemmers

Weld Tips

Roller Tables Racks

Controllers

ProductionTeam

Members

StandingPlatformsMastic

Tables

* * * * * *Ctrl Programs Assem Areas• • •Turn

Tables

Agile JIT Assembly Line Construction at GM Plantfor Low-Volume High-Variety After-Market Body Parts

SocketsSignalsSafetySecurityService

AB Controls OnlyParts flow Work rulesNoneConOps


Examples of TypicalReconfigurable/ScalableSystem Configurations

Plug-and-Play EvolvingActive InfrastructureResponsibility Designation

Plug-and-Play EvolvingPassive InfrastructureRules/Standards/Principles

Drag-and-DropReusableModules/Components

Infrastructure evolution: Who/What?System assembly: Who/What?

Module evolution: Who/What?Module inventory: Who/What?

Variety/Time/Maturity/Range/Increments/Migrations/Evolutions/etc

Generic Agile Architectural Pattern

Sockets?

Safety?Service?

Security?Signals?

Passive Infrastructure – at least five categories of standards and rules should be considered:Sockets: Module physical interconnection standardsSignals: Module data interconnection standardsSecurity: Module (dis)trust interconnection standardsSafety: user, system, and environment safety principles/standards/regulationsService: system operations manual with ConOps and agility sustainment concepts/principles/rules

Next gen?


System ____________________________

aaa cccbbb ddd eee fff


System assembly


Module inventory readiness

Infrastructure

Components/Modules

Rules/Standards

IntegrityManagement

Active

Passive

who

who

who

who

Next Gen Addition?


Config 2 Config nConfig 1

Sample Graphics for your modification into your system needs


Adaptable Immune SystemBow-Tie Antigen-Detector Generator

detector sequence n

shortchain

longchain

detector sequence n+1

shortchain

longchain

detector sequence n+2

shortchain

longchain

123 V segments 6 J segments27 D segmentsrandom

nucleotides


Detector assembly

Module pools and mix evolution

Module inventory condition

Combine two assembliesAdd random nucleotides

Use one each V-D-JUse one each V-J

Infrastructure

Modules

Assembly Rules

IntegrityManagement

Active

Passive

genetic evolution

bone marrow and thymus

genetic evolution

massive redundancy

cell

Y detector antibodyB-Cell

V--D--J V--J


infrastructure evolution: Who?test sys assembly: Who?component inventory: Who?

indicative configurations of test varieties

Multi-Range Weapons Testing System – Unmanned Autonomous Systems(highly stylized architectural concept diagram)

sensors test equip ranges

UAS policy/stdssafety stds

full system testsub-sys test swarm system test

component mix: Who?12

34

5

test config stdsHLA interop stds

security policy

Four active responsibilities, each with embedded security personnel as integrated collaborative team members.

As an emergent propertysecurity does not come in a separate box, e.g., personnel are security trained, equipment is self-secure.

Test system assembly is constrained by test configuration standards informed by security policy.

Security policy informs allother passive infrastructure standards, and evolves simultaneously with each.

act

ive

pa

ssiv

e

personneltestsprocedures …et al.

INF

RA

ST

RU

CT

UR

E

Security is embedded in architecture at points 1-5. Additionally, encapsulated components have internal security distrustful of other components in general, ideally a fractal image of this architecture.

www.parshift.com/Files/PsiDocs/Pap090701Incose-EmbeddingAgileSecurityInSystemArchitecture.pdf


developers/engineers

owners/usersteam leaders processes tests codes/designs


System assembly

Component mix evolution

Component inventory readiness

Self organizingIncremental delivery

Iterative convergenceEmergent requirements

Infrastructure

Iteration 2 Iteration nIteration 1

Components

Rules/Standards

IntegrityManagement

Active

Passive

Time

Process manager

Team leaders

Team leaders

Team leaders

(key core practices detailed in a process manual)

Agile Software-Development Processwww.parshift.com/Files/PsiDocs/Pap080404Cser2008DevOpsMigration.pdf



Agile Software Development-thru-Operations Processwww.parshift.com/Files/PsiDocs/Pap080404Cser2008DevOpsMigration.pdf

Time


System assembly

Component mix evolution

Component inventory readiness

MigrationDevelopment Operation

Rules/Standards

Active

Infrastructure

Passive

Self organizingIncremental delivery

Iterative convergenceEmergent requirements

IntegrityManagement

Process manager

Team leaders

Team leaders

Team leaders

???

???

???

???

developers/engineers

owners/usersteam leaders processes tests codes/designs

Components

(key core practices detailed in a process manual)



Agile Data-Center Location, Capability, Capacity on Demand

AirWater

PowerNetwork

Air standardsWater stds

Power stdsNetwork stds

Drag and Drop Modules

Plug and Play Infrastructure

Type A

Type B

Type B

Type B

Type A

Type C

Type C

New Orleans

Type B Type B

(Classified) New YorkDenverSeattle

Sun Microsystems New productData Center Modules in Shipping Containers

No buildings to build, no space to renovate and lease, no waiting time from moment of additional need.

Put them in the parking lot, on the roof, in the desert.


Characterization of Home Entertainment System-Migration

amplifiersplayback units(tape, CD, DVD) )speakers

video displays(TV, computer)

content sources(TIVO,P2P)

Infrastructure evolution:System assembly:

Component mix evolution:Component inventory readiness:

Power Analog interconnect Physical connection

Infrastructure

Video media Net in/outAudio tape



IntegrityManagement

Active

Passive

‘90s

Industry AssocUser/Owner

MfgrsStores

Video/Surround Digital/Internet

‘40s/’50s ‘00sroughly…

signal tuners

Type 1-2-3 examples depict chronology and a range of different system-assembly possibilities


Characterization of Internet System-Migration

routers DNS Serversswitchesend points,NICs, NOMs

appliances(eg, xml)

Wire standards NCP

IPv6era



IntegrityManagement

’80s/’90s

TCP/IPv4

IPv6 ’70s ’00/’10srough operational start…

filters(eg IDS, Firewall)

Optical stds

IPv4era

NCPera

Wireless stds

Infrastructure evolution:System assembly:

Component mix evolution:Component inventory readiness:

IETFSubnet Owners

Vendor CommunityVendor Community

Infrastructure

Active

Passive


Joint Mission Capabilities Packages

CASaircraft

soldiersgroundvehicles

practicedprocedures

command& control


System assembly:

Component mix evolution:

Component inventory readiness:

SADL tactic/procedure stds

Infrastructure

Components

Rules/Standards

IntegrityManagement

Active

Passive

JMCP Prog Mgr?

daily mission command?

JMCP Prog Mgr?

JMCP who?

NCO stds

missiontype 1config

three typical mision configurations

UAVs

Comments on student work:• Yellow items lifted from story• Green items need identified (who/what are they)• No attempt was made to get iconic aircraft and UAV or

other items of graphic appropriateness for modules• No attempt was made to configure the systems with

typical mission configurations• Note that JMCP is early stage and experimenting with

learning, so the infrastructure will migrate (evolve) and this is perhaps a central point of the story

missiontype 1config

missiontype 1config

additional tac/proc stds + tac/proc stds

(D1: a work in process)


F6 Responsive Deployment System

imagingsats

commsats

powersats

launchvehicles

launchsites


System assembly:

Component mix evolution:

Component inventory readiness:

Launch vehicle stds Harness standards

Infrastructure

Components

Standards

IntegrityManagement

Active

Passivescheduled

replacements

“OIC of Mission Ops”

(Master Planning Dept?)

(suppliers choreographed by who?

“Inventory Department”

Launch pad stds

purposespecificpayload

emergency

clusterlaunch

three typical types of deployments

pay loadharnesses

Comments on student work:• Yellow items lifted from story• Green items need identified (who/what are they)• No attempt was made to get iconic space ships and

sats, or other items of graphic appropriateness• No attempt was made to configure the systems with

positional meaning• No attempt was made to think about or depict a

migration of the infrastructure

I think std comm between sats (mentioned in your “evolving standards” section) is the Class 2 cluster system infrastructure rather than part of this Class 1 deployment system (see next page)

(D1: a work in process)



Plug-and-Play Evolving Active InfrastructureResponsible-Party Designation


Drag-and-DropReusableComponents

This is an agile architectural pattern

Infrastructure evolution: Who?System assembly: Who?

Component mix: Who?Component inventory: Who?


Patterns of Class 1 (reconfigurable) Agile Systems


Patterns of Class 2 (reconfiguring) Agile Systems(Self-Organizing Systems-of-Systems)

Plug-and-Play Evolving Active InfrastructureSystemic Regulation


Infrastructure evolution: What?System assembly: What?

Component mix: What?Component inventory: What?




This is an agile architectural pattern


Config 1Examples of TypicalReconfigurable/ScalableSystem Configurations

Plug-and-Play Evolving Active InfrastructureIntegrity Responsibilities

Plug-and-Play Evolving Passive InfrastructureRules/Standards/Principles


Infrastructure evolutionSystem assembly

Component mixComponent inventory

Systemic MechanismWhat?

What?What?

Responsible PartyWho?

Who?Who?

InfrastructureActive

Passive

Class 1Reconfigurable

Class 2Reconfiguring

Configuration 3Configuration 2

Module Pools

Config 1Examples of TypicalReconfigurable/ScalableSystem Configurations

Plug-and-Play Evolving Active InfrastructureIntegrity Responsibilities

Plug-and-Play Evolving Passive InfrastructureRules/Standards/Principles


Infrastructure evolutionSystem assembly

Component mixComponent inventory

Systemic MechanismWhat?

What?What?

Responsible PartyWho?

Who?Who?

InfrastructureActive

Passive

Class 1Reconfigurable

Class 2Reconfiguring

Configuration 3Configuration 2

[email protected], attributed copies permitted 1 agile architecture pattern … examples

Documents

production system

attributed copies

sil module

pool b

pool c

pool d

pool n

rick dove