Presentation is loading. Please wait.

Presentation is loading. Please wait.

attributed copies permitted 1 Agile Architecture Pattern … Examples.

Similar presentations


Presentation on theme: "attributed copies permitted 1 Agile Architecture Pattern … Examples."— Presentation transcript:

1 attributed copies permitted 1 Agile Architecture Pattern … Examples

2 attributed copies permitted 2 Infrastructure evolution System assembly Module mix evolution Module readiness Infrastructure Configuration Y Configuration ZConfiguration X Modules/Components Rules/Standards Integrity Management Active Passive who/what? who/what?. who/what? Pool A ? ? ? Pool B ? ? Pool C ???? Pool D ? ? ? Pool n ? ? ? Next gen need? ? ?? ????? ?? ????? ????? Sockets Signals Security Safety Service System ____________________________ What? Sample Graphics for your modification into your system needs

3 attributed copies permitted 3 MotorsGears/Pulleys Infrastructure evolution System assembly Module mix evolution Module readiness Infrastructure Helicopter Mobile RadarPlane Modules/Components Integrity Management Active Passive Product Manager Owner/Builder Product System Eng. Retail Distribution Process Wheels Structural Material Joiners, Axles, Small Parts Tools Agile Architecture Pattern (AAP) Notional Concept: System Response-Construction Kit Details in Rules/Standards Radio Control Standards Control Protocol Parts Interconnect Standards Sockets Signals Security Safety Service (None) Harm-Proofing Standards Process Rules & ConOps

4 attributed copies permitted 4 CubeSat Agile Architectural Pattern Chassis Infrastructure evolution System assembly Module mix evolution Module readiness Infrastructure JHU/APL Integrity Management Active Passive Cal Poly SLO Satellite Builder COTS Developers & CPSLO COTS Suppliers Electronics Communications Auburn University Sensors Power 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 Fundamentals of Agile Systems Engineering – Part 1. International Council on Systems Engineering IS14, Los Angeles, CA, 30-Jun-03Jul. Sockets Signals Security Safety Service

5 attributed copies permitted 5 Infrastructure evolution Assembly in SIL Module mix evolution Module readiness Infrastructure Modules Rules/Standards Integrity Management 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 aircraft hardware Sockets Signals Security Safety Service Physical interconnect standards Data/power/cooling transmission Personnel/Sil/supply-chain/et al. Weight/space/installation rules Agile system/process ConOps Boss, Jason and Rick Dove Agile Aircraft Installation Architecture In a Quick Reaction Capability Environment. INCOSE International Symposium, Chicago, July

6 attributed copies permitted 6 Classic Scrum: an Agile Architecture Pattern (AAP) Structure suitable for agile SW development, but not for agile systems-engineering … Infrastructure evolution System assembly Module mix evolution Module readiness Infrastructure Sprint 2 Sprint nSprint 1 Modules/Components Rules/Standards Integrity Management Active Passive Product Owner (PO) Scrum Master PO with Team Collaboration Developers Product OwnersDevelopers Scrum Masters Stakeholders Retrospective Change Product Backlog Planning, I&I Sprint, Review Daily Scrum, Retrospective Full Info Transparency Scrum 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 Sockets Signals Security Safety Service Dove, Rick and Ralph LaBarge Agile Systems Engineering – Part 2. International Council on Systems Engineering IS14 Conference, Los Angeles, CA, 30-Jun-03Jul.

7 attributed copies permitted 7 Task Backlog Buffer Infrastructure evolution: Task assembly: Task elements: Task readiness: Infrastructure Standards Integrity Management Active Passive Last Planner Process Manager Supes/Foreman Project Manager Supes/Foremen/Expediters Last Planner Agile Project Management Planner.pdf Planner.pdf Active management of the anticipated schedule and work flow to ensure there is always a buffer of “quality” jobs ready to work on and matched with resources. master sched CPM tasks 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 production units activity definitions Key Practices: Rules and Lookahead Make ready Learn & Correct Work Task Task Lookahead Window weekweekweekweekweekweek Components Task Soundness/Sequence/Size Task Definitions Physical Site Security Construction Safety Standards/Regs Master Sched, Learning, R1-2-3 Sockets Signals Security Safety Service MS Learning Change

8 attributed copies permitted 8 BSAs DepartmentsSSAsContractors COTS Apps ETLs & BIMs Infrastructure evolution System assembly/reconfiguration Module mix evolution Module readiness Infrastructure Phase 2: Desired Phase 3: Refined Components/Modules Rules/Standards Integrity Management Active Passive Prog Mgr Dept User Proj Mgr BSAs Silterra Agile ERP – Development System Sockets Signals Security Safety Service Scrum-Like Team Collaboration Scrum-Like Progress/Needs Supply Chain Protection (Team) No Req Changes Development ConOps/Rules Phase 1: Out of Box

9 attributed copies permitted 9 COTS ERP Apps Custom Other Apps COTS Other Apps App ETLs Data Bases Custom ERP Apps Infrastructure evolution System assembly/reconfiguration Module mix evolution Module readiness Infrastructure Customer MyFab Components/Modules Integrity Management Active Passive SSAs Dept Users & BSAs BSAs System examples are SOA-like instances of departmental needs Silterra Agile ERP – Developed System Planning/SchedulingEOM Financial Rpt Rules/Standards ETL Template Sockets Signals Security Safety Service API, ETL, BIM, ESB Initial XML Protocol SEA -Appropriate Strategy Pub/Sub Bus Architecture/ConOps Rules

10 attributed copies permitted 10 HH PNM Agile Substation System Design Development engineers switchgeartransformers termination structures low-voltage feeders station steel Infrastructure evolution System assembly Component evolution Component readiness Infrastructure H Station Fly-Thru StationT Station Components Rules/Standards Integrity Management Active Passive chief engineer design engineer DASL program mgr min/max purchaser T T H H H TT Agile Architectural Pattern Diagram Sockets Signals Safety Security Service DASL module interconnects Power flow Construction policies/regs No development customization DASL design tool ConOps H-pad standards Fly-pad standards

11 attributed copies permitted 11 AAP for Tassimo BrewBot In-Operation System base units brew steps discs Infrastructure evolution System assembly Component evolution Component readiness Infrastructure Components Rules/Standards Integrity Management Active Passive Prod eng mgr Automated recipe Product eng mgr Product mktng mgr recipes display text 2-step latte chocolate espresso crème multilingual display Disc holder, RFID placement RFID scan content Consumer product regs Ignored Owners manual Sockets Signals Safety Security Service Nov2011:

12 attributed copies permitted 12 Infrastructure evolution: System assembly: Module evolution: Module readiness: Infrastructure Drag & Drop Components Plug & Play Standards Integrity Management Active Passive Configuration-Process Team Production Teams Component Team P41 Deck Lid System Area B A47 Fender A47 Fender System Area A Hemmers Weld Tips Roller Tables Racks Controllers Production Team Members Standing Platforms Mastic Tables * * * Ctrl Programs Assem Areas Turn Tables Agile JIT Assembly Line Construction at GM Plant for Low-Volume High-Variety After-Market Body Parts Sockets Signals Safety Security Service AB Controls Only Parts flow Work rules None ConOps

13 attributed copies permitted 13 Examples of Typical Reconfigurable/Scalable System Configurations Plug-and-Play Evolving Active Infrastructure Responsibility Designation Plug-and-Play Evolving Passive Infrastructure Rules/Standards/Principles Drag-and-Drop Reusable Modules/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 standards Signals: Module data interconnection standards Security: Module (dis)trust interconnection standards Safety: user, system, and environment safety principles/standards/regulations Service: system operations manual with ConOps and agility sustainment concepts/principles/rules Next gen?

14 attributed copies permitted 14 System ____________________________ aaa cccbbbddd eeefff Infrastructure evolution System assembly Module mix evolution Module inventory readiness Infrastructure Components/Modules Rules/Standards Integrity Management Active Passive who Next Gen Addition? Sockets Signals Security Safety Service Config 2 Config nConfig 1 Sample Graphics for your modification into your system needs

15 attributed copies permitted 15 Adaptable Immune System Bow-Tie Antigen-Detector Generator detector sequence n short chain long chain detector sequence n+1 short chain long chain detector sequence n+2 short chain long chain 123 V segments 6 J segments27 D segments random nucleotides Infrastructure evolution Detector assembly Module pools and mix evolution Module inventory condition Combine two assemblies Add random nucleotides Use one each V-D-J Use one each V-J Infrastructure Modules Assembly Rules Integrity Management Active Passive genetic evolution bone marrow and thymus genetic evolution massive redundancy cell Y detector antibody B-Cell V--D--J V--J

16 attributed copies permitted 16 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/stds safety stds full system testsub-sys testswarm system test component mix: Who? test config stds HLA interop stds security policy Four active responsibilities, each with embedded security personnel as integrated collaborative team members. As an emergent property security 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 all other passive infrastructure standards, and evolves simultaneously with each. active passive personneltestsprocedures …et al. INFRASTRUCTURE 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.

17 attributed copies permitted 17 developers/ engineers owners/usersteam leadersprocesses tests codes/ designs Infrastructure evolution System assembly Component mix evolution Component inventory readiness Self organizing Incremental delivery Iterative convergence Emergent requirements Infrastructure Iteration 2 Iteration nIteration 1 Components Rules/Standards Integrity Management Active Passive Time Process manager Team leaders (key core practices detailed in a process manual) Agile Software-DevelopmentProcess

18 attributed copies permitted 18 Agile SoftwareDevelopment-thru-OperationsProcess Time Infrastructure evolution System assembly Component mix evolution Component inventory readiness Migration DevelopmentOperation Rules/Standards Active Infrastructure Passive Self organizing Incremental delivery Iterative convergence Emergent requirements Integrity Management Process manager Team leaders ??? developers/ engineers owners/usersteam leadersprocesses tests codes/ designs Components (key core practices detailed in a process manual)

19 attributed copies permitted 19 Agile Data-Center Location, Capability, Capacity on Demand Air Water Power Network Air standards Water stds Power stds Network stds Drag and Drop Modules Plug and Play Infrastructure Type A Type B Type A Type C New Orleans Type B (Classified) New YorkDenver Seattle Sun Microsystems New product Data 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.

20 attributed copies permitted 20 Characterization of Home Entertainment System-Migration Type examples depict chronology and a range of different system-assembly possibilities

21 attributed copies permitted 21 Characterization of Internet System-Migration

22 attributed copies permitted 22 Joint Mission Capabilities Packages CAS aircraft soldiers ground vehicles practiced procedures command & control Infrastructure evolution: System assembly: Component mix evolution: Component inventory readiness: SADL tactic/procedure stds Infrastructure Components Rules/Standards Integrity Management Active Passive JMCP Prog Mgr? daily mission command? JMCP Prog Mgr? JMCP who? NCO stds mission type 1 config 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 mission type 1 config mission type 1 config additional tac/proc stds + tac/proc stds (D1: a work in process)

23 attributed copies permitted 23 F6 Responsive Deployment System imaging sats comm sats power sats launch vehicles launch sites Infrastructure evolution: System assembly: Component mix evolution: Component inventory readiness: Launch vehicle stds Harness standards Infrastructure Components Standards Integrity Management Active Passive scheduled replacements “OIC of Mission Ops” (Master Planning Dept?) (suppliers choreographed by who? “Inventory Department” Launch pad stds purpose specific payload emergency cluster launch three typical types of deployments pay load harnesses 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)

24 attributed copies permitted 24 Examples of Typical Reconfigurable/Scalable System Configurations Plug-and-Play Evolving Active Infrastructure Responsible-Party Designation Plug-and-Play Evolving Passive Infrastructure Rules/Standards/Principles Drag-and-Drop Reusable Components This is an agile architectural pattern Infrastructure evolution: Who? System assembly: Who? Component mix: Who? Component inventory: Who? Variety/Time/Maturity/Range/Increments/Migrations/Evolutions/etc Patterns of Class 1 (reconfigurable) Agile Systems

25 attributed copies permitted 25 Patterns of Class 2 (reconfiguring) Agile Systems (Self-Organizing Systems-of-Systems) Plug-and-Play Evolving Active Infrastructure Systemic Regulation Plug-and-Play Evolving Passive Infrastructure Rules/Standards/Principles Infrastructure evolution: What? System assembly: What? Component mix: What? Component inventory: What? Examples of Typical Reconfigurable/Scalable System Configurations Drag-and-Drop Reusable Components Variety/Time/Maturity/Range/Increments/Migrations/Evolutions/etc This is an agile architectural pattern

26 attributed copies permitted 26


Download ppt "attributed copies permitted 1 Agile Architecture Pattern … Examples."

Similar presentations


Ads by Google