ES 678 Agile Systems Pat Bullock Brian Dodds Mike Leonard

Slides:



Advertisements
Similar presentations
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Advertisements

Unified theory of software evolution Reengineering – Business process reengineering and software reengineering BPR model – Business definition, process.
1 CISR-consultancy Challenges “Customer ask us what to do next” Keywords: “Customer ask us what to do next” From Policy to Practise The world is going.
© 2006 Carnegie Mellon University Establishing a Network Centric Capability: Implications for Acquisition and Engineering Dennis Smith Complex System Symposium.
Effective systems development requires a team effort from stakeholders, users, managers, systems development specialists, and various support personnel,
Team: Juan Pablo Pods System:Modular Aircraft Exterior Pods Strategic Values/Objectives Inexpensive Low Certification Costs Quick Reaction Capable Universal.
Team: AlphaDroners System: Alpha Drone 1 Strategic Values/Objectives: Unmanned Reconfigurable Adaptable Safe Autonomous/Manual Descriptive Statement: The.
Team: AlphaDroners System: Team WikiSpeed Descriptive Statement: To build a street legal vehicle that gets at least 100 miles per gallon, is capable of.
1 Tassimo Beverage System attributed copies permitted.
Agile Systems and Enterprises Response Ability Tool Templates Robert Douglas Gault Randy Hosier.
ES 678 Engineering of Agile Systems and Enterprises Team Members: Brian Andrews Craig Kerr John Parker.
UNIT – II ARCHITECTING WEB SERVICES. WHAT ARE WEB SERVICES ? Web Services are loosely coupled, contracted components that communicate via XML-based interfaces.
1 Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
Team: Juan Pablo Pods System:Team WikiSpeed Strategic Values/Objectives High Fuel Efficiency (Green Design) 5 Star Crash Safety Customizable design Uses.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Agile Systems and Enterprises Response Ability Tool Templates Randy Hosier Robert Douglas Gault.
Agile Systems and Enterprises Response Ability Tool Templates.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Team: _Island Breeze_____________ System:_WikiSpeed________________ Strategic Values/Objectives Flexibility Iterative Timelines Efficient Boundless Descriptive.
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
CORBA1 Distributed Software Systems Any software system can be physically distributed By distributed coupling we get the following:  Improved performance.
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
SOFTWARE ENGINEERING. Objectives Have a basic understanding of the origins of Software development, in particular the problems faced in the Software Crisis.
Modern Systems Analysis and Design Third Edition Chapter 2 Succeeding as a Systems Analyst 2.1.
United Nations Economic Commission for Europe Statistical Division CSPA: The Future of Statistical Production Steven Vale UNECE
Design Engineering 1. Analysis  Design 2 Characteristics of good design 3 The design must implement all of the explicit requirements contained in the.
Three Maintainers and a *ing Op
Embedded Systems Software Engineering
CompSci 280 S Introduction to Software Development
Team Name: Team 1 Modular Test Unit (MTU)
EI Architecture Overview/Current Assessment/Technical Architecture
Allocation of costs in complex cropping and mixed farming systems
Drone D-Fence EMP Based Drone Defense System
Game Design, Development, and Technology
Chapter 7 The agile supply chain
Team Name: Team 1 Agile Engineering Process
PLM, Document and Workflow Management
System: Team WikiSpeed Process
The University of Jordan Mechatronics Engineering Department
Team Name: OCD Solutions
Team: Three Maintainers and a *ing Op System: Team WikiSpeed
Agile Trainers – AEP Analysis
“Right Side” Technology Systems
“Right Side” Technology Systems
Introduction to Software Engineering
MBA 8220: Organizational Agility
Team: _____JAR_________________ System: ____Agile Bid System (ABS)_
How to Successfully Implement an Agile Project
Team: ______Houston Euler________
Team: Jeff Olvera Ron Palmer Alli Roland
CS223: Software Engineering
Team Name: OCD Solutions
Descriptive statement
School of Systems and Enterprises Stevens Institute of Technology, USA
Term Project D1 Retrospective L3: Class
An Introduction to Software Architecture
Team: ______Houston Euler________ System:_____WikiSpeed___________
IENG 475: Computer-Controlled Manufacturing Systems
WikiSpeed Work Team: Car Riders Team members: Dmitry Retunski
ES 678 Agile Systems Pat Bullock Brian Dodds Mike Leonard
Team: Remote Site Team: Virtual System Integration Lab (VSIL)
Descriptive Statement
Automation and Mechanization Assessment Template
CHAPTER 13 THE STRUCTURE OF INTERNATIONAL FIRM
School of Systems and Enterprises Stevens Institute of Technology, USA
Team: __Remote Site_____________ System: ___TWS__________________
WikiSpeed Process Team Pest Control Mike McMahon Justin Petersen
Team: Whirlybird System: Adaptive Multi-Rotor UAV Platform
Building a “System” Moving from writing a program to building a system. What’s the difference?! Complexity, size, complexity, size complexity Breadth.
Presentation transcript:

ES 678 Agile Systems Pat Bullock Brian Dodds Mike Leonard PBM Ag Innovations ES 678 Agile Systems Pat Bullock Brian Dodds Mike Leonard

Team: PBM Ag Innovations System: Modular Autonomous Farming Equipment Descriptive Statement: Modular farming equipment that utilizes unmanned, autonomously mobile, remotely commanded crop and terrain adaptable equipment to rapidly and effectively prepare the terrain, and plant, fertilize, and harvest crops. The crop or terrain specific equipment is rapidly interchangeable and adaptable to not only a variety of crops (lettuce to corn), but also differences in terrain type and geometry (flat, hills, soft soil, rocky soil, etc). Strategic Values/Objectives: High availability Low cost of operation Low labor requirement Rapid deployment Rapid (re)configuration (crops/terrain/task) Maximized crop production Maximize land utilization

PBM Ag Innovations Caprice: unknowable situations Weather - reactive Availability of better technology – proactive Equipment failure/breakdown – reactive Uncertainty: randomness with unknowable probabilities Terrain - proactive Insects/disease - proactive/reactive Growing season - reactive Risk: randomness with knowable probabilities Growth rate – reactive Yield margins- reactive Schedule (operational/planning) - proactive Variation: knowable variables and variance range Production - reactive Fuel and maintenance costs – proactive Scalability – proactive/reactive Evolution: gradual (relatively) successive developments Additional equipment - proactive Additional capability (higher production implements) - proactive

System: PBM Ag Innovations Reality Factors Human (Including Customer) Behavior – Human error, whimsy, expediency, arrogance... Education Motivation Idleness and boredom Chemical or emotional influence Organizational Behavior – Survival rules rule, nobody's in absolute control... “Rural ingenuity” solutions Maximize work output while minimizing headcount “Burst/surge” workload schedule Technology Pace – Accelerating technology and security-vulnerability introductions, sparse testing... GPS fidelity Drivetrain efficiency Implement capability System Complexity – Incomprehensible, highly networked, unintended consequences, emergence... Technical prowess required of personnel Technically complex system with intentionally simple interface Unintended machinery behavior Equipment breakdown and failure Globalization – Partners with different ethics, values, infrastructures, cultural assumptions... Geographic variation Work ethic Partially-Agile Enterprise Faddish Practices – Outsourcing, web services, transparency, COTS policies/affects... Implementation of COTS technology Agile Customers/Competitors/Adversaries – Distributed, collaborative, self organizing, proactive, impatient, innovative... System component suppliers Insects, disease, and vermin Cheap physical labor Maximum quality of product Other? Global social responsibility

Response Situation Analysis for System: PBM Ag Innovations with [t,c,p,s] metric-priorities for each issue, t = time of response, c = cost of response, p = predictability of response, s = scope of response Domain Response Issue Proactive Reactive Creation (and Elimination) What artifacts/data/knowledge must the system be creating or eliminating during its operational activity? Produces modularly adaptable system (t) Efficiency in agricultural production (c, s) Improvement What performance characteristics will the system be expected to improve during operational life cycle? Improved crop yield per acre (c, s) Improved crop yield per man hours (t, s) Reduced crop risk (p, s) Migration What major events coming down the road will require a change in the system infrastructure? Driveline technology improvement Change in land utilization or farming technique (c, s) Modification (Add/Sub Capability) What modifications in resources-employed might need made as the system is used? Improved interconnection (multiple tools) (t) New crop rotation (s) Improved control technology (t) Correction What can go wrong that will need an automatic systemic detection and response? Equipment failure/malfunction (guidance, tool, prime mover) (t, c) Variation What system/process variables will range across what values and need accommodation? Operational time (c, p) Fuel and maintenance costs, variation of fuel, scheduled maintenance materials (c) Scalability, increased area or conversion of marginal areas (s) Expansion (and Contraction of Capacity) What are “quantity-based” elastic-capacity range needs on resources/output/activity/other? Scalable tool capacity (t, s) “Swarming” or multiple machine inter-connected deployment (p, s) Reconfigu-ration What types of resource relationship configurations will need changed during operation? Tool/capability conversion (s) Changes to operating methods or technologies (t)

System: PBM Ag Innovations (Think … Drag-and-Drop / Plug-and-Play) Encapsulated Resources Interchangeable tools Chassis/prime mover People (operators, maintainers) Programming interface Scalable Reusable Evolving Infrastructure Standards Sockets: Hydraulic connections Electrical connections (power and data) Mechanical connections Fueling and fluids interface Signals: Telemetry data Security: Physical (doors, keys) Network Safety: Motion limits Safety switches Light barriers Physical barriers Interlocks Service: System documentation Technical support

RRS Principles for System: PBM Ag Innovations (Think: Plug-and-Play, Drag-and-drop) Reconfigurable Scalable Reusable Encapsulated Resources Resources are encapsulated independent units loosely coupled through the passive infrastructure. Interchangeable tools Chassis/prime mover People (operators, maintainers) Programming interface Evolving Infrastructure ConOps and resource interface and interaction standards that evolve slowly. Iterative design tools Documented procedures Facilitated Interfacing (Pluggable) Resources & infrastructure have features facilitating easy resource insertion/removal. Standard interface definitions Plug and play implements Redundancy and Diversity Duplicate resources provide fail-soft & capacity options; diversity provides functional options. Multiple control protocols Pairing and joint design teams Facilitated Reuse Resources are reusable and/or replicable; with supporting facilitation for finding and employing appropriate resources. Modular design concept Standard interfaces Multiple standardized configurations Elastic Capacity Resource populations & functional capacity may be increased and decreased widely within existing infrastructure. Scalable design teams and tasking Automated design testing Peer-Peer Interaction Resources communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored. Collaborative design environment Open communication tools and expectations Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally. Independent yet interconnected design teams Deferred Commitment Resource relationships are transient when possible; decisions & fixed bindings are postponed until necessary. Flexible team collaboration Short duration design iteration Self-Organization Resource relationships are self-determined; and resource interaction is self-adjusting or negotiated. Design teams working independently to schedule

System: PBM Ag Innovations Resources Integrity Management People Movers Tools Parameters Situational awareness Resource mix evolution Resource readiness Activity assembly Infrastructure evolution Land owner Maintainer All parties Land Owner Program Manager Active Infrastructure Passive Config 1 Config 2 Config n Sockets Signals Security Safety Service Hyd/pwr/mech Telemetry/comms Phys/Net Access and interlock System Documentation Hyd/pwr/mech Telemetry/comms Phys/Net Access and interlock System Documentation Rules/Standards