1 / 19

Team: __________________________ System: __________________________

Strategic Values/Objectives ? ? ? ? ? ?. Team: __________________________ System: __________________________. Descriptive Statement ?. System: __________________________. Change the lines and bubbles, this is not a fill-in-the-blank model. Strategic Values/Objectives

delfina
Télécharger la présentation

Team: __________________________ System: __________________________

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Strategic Values/Objectives ? ? ? ? ? ? Team: __________________________System: __________________________ Descriptive Statement ?

  2. System: __________________________ Change the lines and bubbles, this is not a fill-in-the-blank model Strategic Values/Objectives Functional Activity Strategic Activity ConOps Web

  3. System: __________________________ ? ? ? ? ? ? ? ? ? ? ? ? ? Strategic Values/Objectives Functional Activity Strategic Activity ConOps Web

  4. Proactive Reactive System: __________________________ General Issues

  5. Proactive Reactive Response Situation Analysis Change Domain Change/Response Issue Creation (and Elimination) • Make or eliminate something. Issues are generally involved with the development of something new where nothing was before, or the elimination of something in use. Improvement • Incremental improvement. Issues are generally involved with competencies and performance factors, and are often the focus of continual, open-ended campaigns. Migration • Foreseen, eventual, and fundamental change. Issues are generally associated with changes to supporting infrastructure, or transitions to next generation replacements. Modification (Add/Sub Capability) • Addition or subtraction of unique capability. Issues are generally involved with the inclusion of something unlike anything already present, or the removal of something unique. • Rectify a dysfunction. Issues are generally involved with the failure to perform as expected, recovery from malfunction and side effects, and the rectification of a problem. Correction Variation • Real-time routine situational change within the mission. Issues are generally associated with resource, performance, and interaction variances which can be expected and must be accommodated. Expansion (and Contraction of Capacity) Increase or decrease existing capacity. Issues are generally involved with quantity and capacity changes, when either more or less of something is demanded or desired. Reconfigu-ration • Reorganize resource or process relationships. Issues are generally involved with the reconfiguration of existing elements and their interactions, sometimes with added elements as well.

  6. Proactive Reactive RS Analysisfor an Agile Engineering Process Change Domain General Issues Creation (and Elimination) • What must an Agile Development process be creating in the course of its operational activity? • ? • ? Improvement • What performance characteristics will an ADP process be expected to improve as it is used repeatedly? • ? • ? Migration • What major event coming down the road will require a change in the initially adopted ADP infrastructure? • ? • ? Modification (Add/Sub Capability) • What modifications in resources-employed might need accommodation as the process is used? • ? • ? Correction • What can go wrong that will need a highly responsive fix? • ? • ? Variation • What process variables will range across what values and need accommodation? • ? • ? Expansion (and Contraction of Capacity) • What are the key resource, application, and/or performance bounds on process accommodation? • ? • ? Reconfigu-ration • What types of resource relationship configurations will need changed in the course of process operation? • ? • ?

  7. Proactive Reactive RS Analysis for System ____________________ with [t,c,q,s] metric-priorities for each issue, t = time of change, c = cost of change, q = quality of change, s = scope of change Change Domain General Issues Creation (and Elimination) • What must the system be creating in the course of its operational activity? • ? • ? Use as many bullet points as appropriate • ? Improvement • What performance characteristics will the system be expected to improve during operational life cycle? • ? • ? • ? Migration • What major events coming down the road will require a change in the system infrastructure? • ? • ? • ? Modification (Add/Sub Capability) • What modifications in resources-employed might need made as the system is used? • ? • ? • ? Correction • What can go wrong that will need an automatic systemic detection and response? • ? • ? • ? Variation • What process variables will range across what values and need accommodation? • ? • ? • ? Expansion (and Contraction of Capacity) • What are the key resource and/or performance bounds on necessary system response? • ? • ? • ? Reconfigu-ration • What types of resource relationship configurations will need changed during operation? • ? • ? • ?

  8. Proactive Reactive Response Situation Analysis for System: __________________________ Change Domain Change/Response Issue Creation (and Elimination) • ? • ? Improvement • ? • ? Migration • ? • ? Modification (Add/Sub Capability) • ? • ? Correction • ? • ? • ? • ? Variation Expansion (and Contraction of Capacity) • ? • ? Reconfigu-ration • ? • ?

  9. Correction • ? Variation • ? Expansion (Capacity) • ? Reconfig-uration • ? System __________________________________Key Reactive Response Issues & Metrics(t = time of change, c = cost of change, q = quality of change, s = scope of change) Response Type • ? • ? Reactive • ? • ?

  10. Creation • ? Improvement • ? Migration • ? Modification(Capability) • ? System __________________________________Key Proactive Response Issues & Metrics(t = time of change, c = cost of change, q = quality of change, s = scope of change) Response Type • ? • ? Reactive • ? • ?

  11. System: ________________________ • (Think … Drag-and-Drop / Plug-and-Play) • Self-Contained Units (Encapsulated Modules) • ? • Evolving Standards (Infrastructure/Framework) • ? Scalable Reusable

  12. RRS Principles for System: ________________________ (Think: Plug-and-Play, Drag-and-drop) Evolving Standards (Framework)Component interaction standards, responsibilities/processes for evolving the standards. x Self-Contained Units (Modules) Components are distinct, separable, loosely-coupled, self-sufficient units. x Plug Compatibility (Facilitated Interfacing) Components easily inserted/removed, component evolution responsibility designated. x Redundancy and Diversity Duplicate components provides fail-soft & capacity options; diversity provides functional options. x Reusable Scalable Facilitated ReuseComponents are reusable and replicable; with responsibilities designated for inventory ready-for-use availability. x Elastic Capacity Component populations and functional capacity may be increased and decreased widely within the existing framework. x Reconfigurable Flat Interaction Components communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored. x Distributed Control and Information Decisions made at point of maximum knowledge; information accessible globally but kept locally. x Deferred Commitment Component relationships are transient when possible; decisions & fixed bindings are postponed until necessary. x Self-Organization Component relationships are self-determined; and component interaction is self-adjusting or negotiated. x

  13. RRS Principles for System: ________________________ • Self-Contained Units (Encapsulated Modules) • ? • Evolving Standards (Infrastructure/Framework) • ? • Plug Compatibility (Facilitated Interfacing) • ? • Unit Redundancy & Diversity • ? Scalable Reusable • Facilitated Reuse • ? • Elastic Capacity (Scalable) • ? Reconfigurable • Flat Interaction (Peer-Peer, Non-Hierarchical) • ? • Distributed Control & Information (Decentralization) • ? • Deferred Commitment • ? • Self Organization • ?

  14. Self Contained Units Plug Compatibility Facilitated Re-Use Peer-Peer Interaction Deferred Commitment Distributed Control & Info Self Organizing Flexible Capacity Unit Redundancy Evolving Standards RRS Principles Core Competency Development Activities Establish Personal Values 1 Analyze External Case for Ideas 2 Analyze Local Case for Principles 3 Design a Business Practice 4 Package as Metaphor Models 5 Rotate Student / Mentor Roles 6 Review and Select for Quality7 Excel template version (a different template file) may be easier to use Issues Principle-Based Activities and Issues Served Capturing Hidden Tacit Knowledge3567 35 356 57 3 37 6 3 3 37 Creating Student Interest and Value124 1 1 1 12 124 124 1 1 Improving Knowledge Accuracy3467 6 34 37 6 34 34 7Improving Knowledge Effectiveness12345 345 245 45 1 12 5 2 Migrating the Knowledge Focus247 27 4 2 4 7 247 4 47 Accommodating Different Student Types (all) 25 6 347 2 12345 1 17 2Injecting Fresh Outside Knowledge26 26 26 2 6 2 Finding and Fixing Incorrect Knowledge 367 7 7 3 3 6 3 3 7Excising Poor Value Knowledge2357 7 7 3 3 2 23 35 257 Allowing Flexible Student Schedules34 34 34 34 Accommodating Any Size Group 2345 2345 234 2 25 34 234 Reinterpret Rules for New Applications 23457 27 5 2 357 23457 Reactive Proactive

  15. Self Contained Units Plug Compatibility Facilitated Re-Use Peer-Peer Interaction Deferred Commitment Distributed Control & Info Self Organizing Flexible Capacity Unit Redundancy Evolving Standards RRS Principles <your system> Activities ?? 1 ?? 2 ?? 3 ?? 4 ?? 5 ?? 6 ??7 Excel template version(a different template file) may be easier to use Issues Principle-Based Activities and Issues Served ?? ?? ???? ?? ???? ???? ?? ?? ?? Reactive Proactive

  16. System: _______________________ Reality Factors Human Behavior – Human error, whimsy, expediency, arrogance... • ? • Organizational Behavior – Survival rules rule, nobody's in control... • ? • Technology Pace – Accelerating vulnerability-introductions, sparse testing... • ? • System Complexity – Incomprehensible, highly networked, unintended consequences, emergence... • ? • Globalization – Partners with different ethics, values, infrastructures... • ? • Creeping Agile Practices – Outsourcing, webservices, transparency, COTS, SOA... • x • Agile Adversaries/Competitors/Customers – Distributed, collaborative, self organizing, proactive, impatient, innovative... • ? • Other? • ?

  17. Module Mix/Evolution(who decides/specifies/adds which new types of modules, excises old useless modules): ? ? ? Inventory Management (who maintains servicability/readiness and quantity on hand of which modules): ? ? ? Real-Time Configuration (who assembles/configures/reconfigures the systems): ? ? Framework Evolution (who reviews and modifies the various framework elements): ? ? ? ? System _______________________Who Does What to Keep the Systems Effective(as part of their job description/responsibility/evaluation)

  18. Your System Sample Graphics for your modification into your system needs Do not use this template – refer to file: TemplatesAgileArchitecturePatterns.pptx for many examples Modules/Components Integrity Management eee fff bbb ccc ddd aaa who Module mix who Module inventory who System assembly who Infrastructure evolution Active Infrastructure Passive Config 2 Config 1 Config n www xxx yyy zzz

More Related