Team: AlphaDroners System: Team WikiSpeed Descriptive Statement: To build a street legal vehicle that gets at least 100 miles per gallon, is capable of.

Slides:



Advertisements
Similar presentations
Demand Response: The Challenges of Integration in a Total Resource Plan Demand Response: The Challenges of Integration in a Total Resource Plan Howard.
Advertisements

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Lecture # 2 : Process Models
Presentation begins at 6:30 p.m.
IACT 901 Module 9 Establishing Technology Strategy - Scope & Purpose.
The Production Process
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
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.
Operations Management
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
BA 351 Managing Organizations Operations Management 1.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Chapter 7: Architecture Design Omar Meqdadi SE 273 Lecture 7 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
1 Tassimo Beverage System attributed copies permitted.
Agile Systems and Enterprises Response Ability Tool Templates Robert Douglas Gault Randy Hosier.
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Dr. Tom WayCSC Software Processes CSC 4700 Software Engineering.
Agile Software Development Chapter 3 – Lecture 1 Adrián Susinos.
11 1 Object oriented DB (not in book) Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Learning objectives: What.
Transportation Infrastructure
Slides 8 Integrating Supply Chain and Development Chain
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.
Architectural Design To explain the advantages and disadvantages of different distributed systems architectures To discuss client-server and distributed.
Software Engineering Management Lecture 1 The Software Process.
Agile Systems and Enterprises Response Ability Tool Templates Randy Hosier Robert Douglas Gault.
May05-36: Boone Cemetery Management Software Boone Cemetery Management Software May05-36 Greg Thede, Director, Boone Parks Department Dr. Kothari Joseph.
Agile Systems and Enterprises Response Ability Tool Templates.
Can architecture descriptions help prospective users to visualise the solution in terms of meeting its requirements? Peter Henderson Open Middleware Infrastructure.
CERN Equipment Management Integrates Safety Aspects EDMS Doc Eva Sanchez-Corral Mena, Stephan Petit / CERN 1 CERN Equipment Management Integrates.
Team: _Island Breeze_____________ System:_WikiSpeed________________ Strategic Values/Objectives Flexibility Iterative Timelines Efficient Boundless Descriptive.
Service Level Agreements Service Level Statements NO YES The process of negotiating and defining the levels of user service (service levels) required.
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
SOFTWARE ENGINEERING. Objectives Have a basic understanding of the origins of Software development, in particular the problems faced in the Software Crisis.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
LESSON 5 Introduction to Materials Requirements Planning (MRP)
Team Name: Team 1 Modular Test Unit (MTU)
Software Engineering Management
Drone D-Fence EMP Based Drone Defense System
Team Name: Team 1 Agile Engineering Process
Part The smallest removable item on a car Not normally disassembled
System: Team WikiSpeed Process
Team Name: OCD Solutions
Software Processes (a)
Team: Three Maintainers and a *ing Op System: Team WikiSpeed
Agile Trainers – AEP Analysis
“Right Side” Technology Systems
“Right Side” Technology Systems
ES 678 Agile Systems Pat Bullock Brian Dodds Mike Leonard
Team: _____JAR_________________ System: ____Agile Bid System (ABS)_
Team: ______Houston Euler________
Team: Jeff Olvera Ron Palmer Alli Roland
Team Name: OCD Solutions
IENG 475: Computer-Controlled Manufacturing Systems
Descriptive statement
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
Information Hidding Dr. Veton Kepuska.
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
Distributed Systems and Concurrency: Distributed Systems
Presentation transcript:

Team: AlphaDroners System: Team WikiSpeed Descriptive Statement: To build a street legal vehicle that gets at least 100 miles per gallon, is capable of 100 miles per hour, and has minimal manufacturing time. Vehicle will attain 5 star crash ratings. (Presentation Note: Descriptive statement needs to describe the process. What does the process need to do?) Strategic Values/Objectives: Safety Affordable Low Cost to Operate Easily Upgradable Reconfigurable Team members: Jesse Dimas, Tim Adams, David Waters

Proactive Reactive General Issues Creation – Hardware, Test Software, Integration, Test Plans, Iterations Improvement – Coordination, 24 hr shifts, communication, sprint plans, user stories Migration – New technology, new requirements, mass manufacturing, testing Modifications – More Team Members, more facilities, equipment (Presentation Note: More items would be a better fit in the “Expansion” section). Correction – Test Plans, Scrum process, Loss of key personnel, Money Variation – Work Shifts, Work Loads, Personnel, Skill Range, Communication Tools (Online could change) Expansion – New Hierarchy, New Scrum Groups, New Technology (Presentation Note: New Technology would be a better fit in “Modifications” section) Reconfiguration – Attrition, Skill Sets, Rewards System: _____AlphaDrone 1_____

Team WikiSpeed Electrical SuspensionPower TrainFrame/Chasis SoftwareHardware Infrastructure evolution System assembly Module mix Module inventory Electronically Compliant Street Legal Regulations Crash Safety Standards Emission Regulations Infrastructure Gas Car Ethanol CarElectric Car Modules/Components Integrity Management Active Passive Scrum Master Product Lead Volunteers Scrum

Reconfigurable Scalable Reusable Self-Contained Units (Modules) Components are distinct, separable, loosely-coupled, self-sufficient units. -Electrical Components-Software -Power Train-Hardware -Frame/Chassis Plug Compatibility (Facilitated Interfacing) Components easily inserted/removed, component evolution responsibility designated. -Engine Type (Gas, Electrical, Ethanol, etc) -Aesthetic Cover (Car, Truck etc) -Seat Capacity (Sporty Two Seater, Family Four Seater, etc) -Suspension Facilitated Reuse Components are reusable and replicable; with responsibilities designated for inventory ready-for-use availability. -Tires/Wheels -Gas Tank -Steering Wheel Flat Interaction Components communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored. -Engine drives the fuel type used -User communicates with many aspects of car. Deferred Commitment Component relationships are transient when possible; decisions & fixed bindings are postponed until necessary. - Car is automatic Evolving Standards (Framework) Component interaction standards, responsibilities/processes for evolving the standards. -Fuel -Emissions -Expected End User Application Redundancy and Diversity Duplicate components provides fail-soft & capacity options; diversity provides functional options. -Aesthetic Cover -Engine -Suspension Elastic Capacity Component populations and functional capacity may be increased and decreased widely within the existing framework. -Seats Distributed Control and Information Decisions made at point of maximum knowledge; information accessible globally but kept locally. -Cover Designs Available -Engine Types Self-Organization Component relationships are self-determined; and component interaction is self-adjusting or negotiated. -Fuel type determines engine type or vice versa -Fuel economy is partially determined by user driving habits (Think: Plug-and-Play, Drag-and-drop) RRS Principles for System: __Team WikiSpeed_______