1. Descriptive statement
The Multi-Generation Lab (MGL) simulator is designed to provide a configurable lab environment for developers, lab monitors, training personnel, and testers to support legacy, current, and next-generation versions of a system. Lab configuration is rapidly modified, by minimally trained personnel, in a standalone or full-integration mode allowing research and development of future technologies.
Strategic value/objective
Inexpensive
High availability
Rapid Configuration
Risk Reduction
Description of an Agile System Project with an uncertain environment / effective response (2:53-55)
Fundamentals – Problem & Solution Space
Team: El Cuatro
Team Members: Bruce Rowe, Luke Wilson & Steven Johnson
Class: Engineering of Agile Systems and Enterprises (ES-678)
This document contains no export controlled technical data as defined under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR). This document consists of general capabilities information that is not defined as controlled technical data under ITAR Part or EAR Part 772.

2. CURVE environment Caprice: Uncertainty: Risk: Variation: Evolution:
Unavailability of Lab Monitor (Reactive)
Train all users to configure lab environment (Proactive)
Uncertainty:
Scheduling conflict for Lab Resources (Reactive)
Funding Gaps (Reactive)
Risk:
Scheduled delivery change (Reactive)
Lab Configuration Control (Proactive)
Variation:
Classification Requirements (Reactive)
Performance differences in multiple Generation System Configuration Template (Proactive)
Evolution:
Change in targeted operating environment (Reactive)
Availability of Superior Technology (Proactive)
CURVE is used to develop requirements. It is also utilized to frame the problem that needs to be addressed. It explains the internal and external process and product as systems. Each of the environmental forces are known as elements (1:24 – 1:28).
CURVE is used to design and develop a system that can deal effectively with changing environments. It is used to articulate the nature of change to be considered (3:4-7).
Analysis – Response Types, Metrics, Value and Situational Analysis & Strategy
This document contains no export controlled technical data as defined under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR). This document consists of general capabilities information that is not defined as controlled technical data under ITAR Part or EAR Part 772.

3. Reality factors Human Behavior –
Lack of attention to details by personnel
Schedule Deadline Stress
Organizational Behavior –
Lack of training or experience
Lack of cooperation across organizational boundaries
Technology Pace –
Changing delivery requirements
Schedule change due to operational need
System Complexity –
High knowledge / experience required
System outages due to inexperienced personnel
Globalization –
Diverse ethnicities and cultural beliefs and values among customers
Priority lists are different based on cultural diversity
Partially-Agile Enterprise Reality (Faddish Practices) –
Virtualization
Cloud (PAAS, IAAS etc.)
Agile Customers/Competitors/Adversaries –
Competitors with less process = faster-to-market
Other –
Security protocols delays process
Analysis – Response Types, Metrics, Value and Situational Analysis & Strategy (3:8-11).
This document contains no export controlled technical data as defined under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR). This document consists of general capabilities information that is not defined as controlled technical data under ITAR Part or EAR Part 772.

4. Change/Response situation analysis
Domain
Response Issue
Proactive
Creation & Elimination
System design allows unlimited reconfiguration w/o need for new resources (hardware)
System design allows elimination of multiple labs (hardware, space, manpower)
Improvement
Reduction of specially-trained personnel (manpower)
Develop/test system in “as-is” environment; reduce potential deficiencies (S/W delivery)
Migration
Replace storage, N/W, and compute modules w/ next-gen equiv (reduce wastage)
Modification (of Capability)
Special training for new system features (manpower)
Ability to run in multiple classification configuration (cost)
Reactive
Correction
Improper configured virtual environment (time/money)
Variation
Schedule prioritization (classification, instantiation, etc.)
Expansion (of Capacity)
1-4 instantiations supported
Reconfigurable environment
Reconfiguration
Increased lab need during delivery
Response Analysis is a heuristic tool for solving problems that are ill-defined (2:41). Exercise & Definition 3: Identifying the problem but not the solution (PROCESS).
What requirement do I have to solve? What is the important metric?
Proactive (Leadership)
Innovative
Agile
Fragile
Resilient
Reactive (Viability)
This document contains no export controlled technical data as defined under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR). This document consists of general capabilities information that is not defined as controlled technical data under ITAR Part or EAR Part 772.

5. references
Dove, R. (2018). Engineering of Agile Systems and Enterprises (ES-678). Stevens Institute of Technology.
Dove, R. (2001). Response Ability – The Language, Structure, and Culture of the Agile Enterprise. John Wiley & Sons, Inc. New York.
(2:40)
This document contains no export controlled technical data as defined under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR). This document consists of general capabilities information that is not defined as controlled technical data under ITAR Part or EAR Part 772.

6. Agile architecture pattern
Resources
Integrity
Management
Network
Computers
Power
Software
People AC
Situational awareness
Resource mix evolution
Resource readiness
Activity assembly
Infrastructure evolution
Systems Engineers / Developers
Lab Monitor
Program Manager
Test Director
Project Engineer
Active
(2:40, 5:11-18)
Infrastructure
Passive
Legacy
Current
Future
Sockets
Signals
Security
Safety
Service
Part Interconnect Standard
ICD, NetConfig, IPConfig, API
Trusted vendors & Fortification
Safety/Security Regulations
Testing Standards
This document contains no export controlled technical data as defined under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR). This document consists of general capabilities information that is not defined as controlled technical data under ITAR Part or EAR Part 772.

7. RRS Principles Encapsulated Resources Reusable Scalable
Reconfigurable Processor Environment (RPE)
Virtual Machine (VM) App–centric implementation
Reusable
Scalable
Evolving Infrastructure
Standards based architecture is hardware agnostic.
Facilitated Interfacing (Pluggable)
Power source configurable per customer reqs
published VM standards.
Redundancy & Diversity
COTS computers
Facilitated Reuse
Compartmentalized lab w/ raised floor; allows equipment swap-out w/ little impact
Elastic Capacity
NW expandable to meet increasing IO requirements.
Expandable/upgradable compute and storage modules.
Reconfigurable
Peer-Peer Interaction
Teams can make real-time config changes per lab reqs
Lab can be split allowing multiple teams to work concurrent
Distributed Control & Information
SW Matrix determines overall configuration; each machine reports version to single machine for verification
Differed Commitment
Resources assigned as needed automatically.
Self-Organization
Teams deliver software with system resource requirements.
(2:40, 5:11-18)
This document contains no export controlled technical data as defined under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR). This document consists of general capabilities information that is not defined as controlled technical data under ITAR Part or EAR Part 772.