Team: Jeff Olvera Ron Palmer Alli Roland

Slides:



Advertisements
Similar presentations
Conclusions: Sessions 2 & 3 James Gover, IEEE VTS.
Advertisements

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
VSE Corporation Proprietary Information
Lecture # 2 : Process Models
SANCHEZ, R., & MAHONEY, J. T. (1996). STRATEGIC MANAGEMENT JOURNAL, 17, PRESENTED BY CHRISTINA L. FRYE Modularity, Flexibility, and Knowledge Management.
Eric Bryant Joe Brooks Matt Delgadillo.  The RCT is a mobile training platform designed in response to the need for modular and interactive training.
Unified theory of software evolution Reengineering – Business process reengineering and software reengineering BPR model – Business definition, process.
© 2006 Carnegie Mellon University Establishing a Network Centric Capability: Implications for Acquisition and Engineering Dennis Smith Complex System Symposium.
Team: Juan Pablo Pods System:Modular Aircraft Exterior Pods Strategic Values/Objectives Inexpensive Low Certification Costs Quick Reaction Capable Universal.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
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.
Chapter 1- Introduction Lecture 1 Ready, fire, aim (the fast approach to software development). Ready, aim, aim, aim, aim... (the slow approach to software.
Chapter 7: Architecture Design Omar Meqdadi SE 273 Lecture 7 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
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.
Team: Juan Pablo Pods System:Team WikiSpeed Strategic Values/Objectives High Fuel Efficiency (Green Design) 5 Star Crash Safety Customizable design Uses.
Agile Systems and Enterprises Response Ability Tool Templates Randy Hosier Robert Douglas Gault.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Agile Systems and Enterprises Response Ability Tool Templates.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
Team: _Island Breeze_____________ System:_WikiSpeed________________ Strategic Values/Objectives Flexibility Iterative Timelines Efficient Boundless Descriptive.
Sanchez and Mahoney (1996). Modularity, flexibility, and knowledge management in product and organization design. SMJ.
SAFENET The OSU SAFENET Project The Ohio State University Center for Automotive Research & Center for Intelligent Transportation Research.
LESSON 3. Properties of Well-Engineered Software The attributes or properties of a software product are characteristics displayed by the product once.
Software Engineering Issues Software Engineering Concepts System Specifications Procedural Design Object-Oriented Design System Testing.
Anti-lock Brake System Group 2 Presenters: Christan Balnius, Zain Kazim, Mark Pulver Demo Given by: Brian Lawnichak.
Design Engineering 1. Analysis  Design 2 Characteristics of good design 3 The design must implement all of the explicit requirements contained in the.
Distributed Systems Architectures. Topics covered l Client-server architectures l Distributed object architectures l Inter-organisational computing.
Chapter 7 Managing Diverse IT Infrastructures
Three Maintainers and a *ing Op
CompSci 280 S Introduction to Software Development
Rapid Application Development Paradigm
Team Name: Team 1 Modular Test Unit (MTU)
Drone D-Fence EMP Based Drone Defense System
The Insiders Guide To Traction Control.
Team Name: Team 1 Agile Engineering Process
System: Team WikiSpeed Process
Rapid Application Development Paradigm
Team Name: OCD Solutions
Design and Implementation
Frequently asked questions about software engineering
Team: Three Maintainers and a *ing Op System: Team WikiSpeed
Agile Trainers – AEP Analysis
“Right Side” Technology Systems
“Right Side” Technology Systems
School of Systems and Enterprises Stevens Institute of Technology, USA
ES 678 Agile Systems Pat Bullock Brian Dodds Mike Leonard
Team: _____JAR_________________ System: ____Agile Bid System (ABS)_
Team: ______Houston Euler________
Software Engineering Lecture #14.
School of Systems and Enterprises Stevens Institute of Technology, USA
Team Name: OCD Solutions
Descriptive statement
School of Systems and Enterprises Stevens Institute of Technology, USA
Top Reasons to Choose Android Today. Over the years the Android OS has progressed largely by acquiring major percent of global market share. A number.
Top Reasons to Choose Android Today. Over the years the Android OS has progressed largely by acquiring major percent of global market share. A number.
Term Project D1 Retrospective L3: Class
Team: ______Houston Euler________ System:_____WikiSpeed___________
WikiSpeed Work Team: Car Riders Team members: Dmitry Retunski
ES 678 Agile Systems Pat Bullock Brian Dodds Mike Leonard
Physics data processing with SOA
Team: Remote Site Team: Virtual System Integration Lab (VSIL)
Descriptive Statement
Robotics & Engineering Academy TERRA Environmental Research Institute
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
Presentation transcript:

Team: Jeff Olvera Ron Palmer Alli Roland Team: JAR Team: Jeff Olvera Ron Palmer Alli Roland

Team: JAR System: Wikispeed Descriptive Statement Wikispeed is a road legal car capable of 100+ mpg. Strategic Values/Objectives Rapidly reconfigurable design Low cost Rapid prototyping Customer focused requirements Customer involved design

Team: JAR System: Wikispeed RS Analysis Creation Efficient vehicle - Safe driving environment - Improvement Fuel economy Development and manufacturing rates Migration Engine power sources Technology advancements (i.e. automation…autonomous vs driver) Modification Size of vehicle for other application Changes in regulations for roadworthy applications Correction Braking system - Traction system - Seat placement - Variation Variety of vehicle type per customer Operating environment Expansion(Capacity) Prototyping turning into production – (want to produce 1k cars within 2 years) Production based off of desire of customer Reconfiguration Reconfig of subsystems (i.e. suspension, fuel, engine…)

System ______Wikispeed______________________ Sample Graphics for your modification into your system needs Resources Integrity Management Team members Fab materials Scrum master Design software Test facility Subsystem modules Situational awareness Resource mix evolution Resource readiness Activity assembly Infrastructure evolution Subsystem Modules and Design Software Scrum Master and Development Teams Team members Sprints Subsystem Modules and Test Facility Active Infrastructure Passive Model 1- MPG Model 2- Speed Model 3- Capacity Sockets Signals Security Safety Service Standard Interconnects and Hardware Modular requirements Trustworthy Transparency Road Worthy Standards Retrospective Changes Rules/Standards

RRS Principles for System: _____Wikispeed_____________ (Think: Plug-and-Play, Drag-and-drop) Reconfigurable Scalable Reusable Encapsulated Resources Resources are encapsulated independent units loosely coupled through the passive infrastructure. Suspension modules Drive modules Fuel modules Evolving Infrastructure ConOps and resource interface and interaction standards that evolve slowly. Team members Regulations Technology Facilitated Interfacing (Pluggable) Resources & infrastructure have features facilitating easy resource insertion/removal. Standard interfacing of modules Team members are pluggable for where they are needed Redundancy and Diversity Duplicate resources provide fail-soft & capacity options; diversity provides functional options. Team members Modules Facilitated Reuse Resources are reusable and/or replicable; with supporting facilitation for finding and employing appropriate resources. Chassis Team Members Manufacturing process Elastic Capacity Resource populations & functional capacity may be increased and decreased widely within existing infrastructure. Prototyping Modules make for differn Peer-Peer Interaction Resources communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored. Parallel teams working while talking with the radio Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally. ? Deferred Commitment Resource relationships are transient when possible; decisions & fixed bindings are postponed until necessary. Small teams Self-Organization Resource relationships are self-determined; and resource interaction is self-adjusting or negotiated. ?