Lecture 6 October 22, 2009. Agenda HW presentations Acceleration of materials Midterm discussion Product Architecture Exercise Team Assessment.

Slides:



Advertisements
Similar presentations
Product Design L8- Ch9: Product Architecture Dr. Husam Arman 1.
Advertisements

Product Platforming Effective Management and Creation.
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Prescriptive Process models
1 Software Processes A Software process is a set of activities and associated results which lead to the production of a software product. Activities Common.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Lecture # 2 : Process Models
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
CSE 470 : Software Engineering The Software Process.
What is Software Design?. Systems Development Life- Cycle Planning Analysis Design Implementation Design.
The software process A software process is a set of activities and associated results which lead to the production of a software product. This may involve.
1 Systems Engineering Part 2 Product Architectures.
Teaching materials to accompany:
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Gu & Maher University of Sydney, October 2004 DECO2005 Monitoring Team Process.
Azad Madni Professor Director, SAE Program Viterbi School of Engineering Platform-based Engineering: Rapid, Risk-mitigated Development.
Development and Use of Architectures in System Engineering Rosalind Lewis USC-CSSE Workshop October 2007 © 2007 The Aerospace Corporation Motivated by.
SWE Introduction to Software Engineering
1 Introduction to System Engineering G. Nacouzi ME 155B.
1 Systems Engineering and Product Architectures October 24, 2006.
André Weiß, DLR Institute of Space Systems Concurrent Evaluation – An Application for DLR’s Concurrent Engineering Facility SECESA 2010, October,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CSC230 Software Design (Engineering)
Development Processes and Organizations
Software Life Cycle Model
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
Computer Systems & Architecture Lesson Software Product Lines.
Operations Management
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
1 These are the Skills You Need to Build a House – What’s Missing?
Chapter 2 The process Process, Methods, and Tools
Requirements Analysis
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Panel Three - Small Businesses: Sustaining and Growing a Market Presence Open Interfaces and Market Penetration Protecting Intellectual Innovation and.
New Product Development Management NPDM 8 Mohsen SADEGHI Department of Graduate School of Management and Economics Sharif University of Technology.
Software Engineering Management Lecture 1 The Software Process.
Design engineering Vilnius The goal of design engineering is to produce a model that exhibits: firmness – a program should not have bugs that inhibit.
Software Engineering MCS-2 Lecture # 6
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 11 Slide 1 Design.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
Kuliah 9 : Product Architecture. Dira Ernawati, ST.MT2 Planning Concept Develop. System- Level Design Detail Design Testing And Refinement Production.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Product Architecture, Industrial Design, Design for Manufacturing.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Product Architecture Chapter 9 EIN 6392, summer 2012 Product Design for Manufacturability and Automation.
Chapter 4 프로세스 모델 Process Models
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
EPT 221 CONFIGURATION DESIGN. Objective of This Lecture Describe the configuration design phase Describe ways to generate product and parts configurations.
Chapter 12 EIN 6392, Product Design summer 2012
CSE 303 – Software Design and Architecture
Prototyping life cycle Important steps 1. Does prototyping suit the system 2. Abbreviated representation of requirements 3. Abbreviated design specification.
Software Development Life Cycle (SDLC)
Spring CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Senior Design Lecture 2 Technical staff Prototype phase: DEP, TOP.
Outlines Overview Defining the Vision Through Business Requirements
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
CompSci 280 S Introduction to Software Development
Software Engineering Management
Lecture 3 Prescriptive Process Models
OVERVIEW Impact of Modelling and simulation in Mechatronics system
Software Quality Engineering
Software development life cycle models
Software Process Models
Ron Sanchez Joseph Mahoney
Software Life Cycle Models
Magister Sistem Informasi Universitas Komputer Indonesia
Model-Driven Analysis Frameworks for Embedded Systems
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Evolutionary Software Process Models
Product Design for Manufacturability and Automation
Chapter 2: Development process and organizations
Presentation transcript:

Lecture 6 October 22, 2009

Agenda HW presentations Acceleration of materials Midterm discussion Product Architecture Exercise Team Assessment

Expectations Final expectations – I would prefer a plan for implementation without a prototype rather than a prototype without a plan for implementation

Acceleration I am posting my mkt lectures for your reading enjoyment. In both cases they were only partially presented There is some important info in them relating to the business context of your product I would like you to extract some useful info from them for application to your project and show this in the Final paper

Midterm Midterm Tuesday11/3/09. from 1:30 to 5:00 PM Presentation: 30 minutes ion (15 minutes plus 15 minutes discussion) Paper 10 pages plus appendices Mission Statement - explain what you hope to achieve by designing your product. Has your mission statement evolved? Evaluation of previous approaches. In the cases where prototypes do not exist evaluate the product that have existed till date to meet that particular need. What needs to be improved? Give a list of contacts of people Give one paragraph on what you have learned from them. A more detailed description can go in the appendix Architecture of product. Detailed sketch of planned prototype. If you have a model built then a detailed description of this (see slide to follow) How are you going to fabricate and test your prototype and refine your business thoughts (a timeline is good here) What are the problems that you see (risk analysis)? How will you meet these challenges? Results of Team assessment. On a scale of 1-10 how well has your team functioned? 9see slide to follow) See slide 28 for Architectural analysis On Tuesday - We will go over risk and explain how to do a risk analysis

6 For Midterm Architecture 1.Which architecture did you select and why (modular, integral, etc.) 2.create a schematic of the product 3.cluster the elements of the schematic 4.create a rough geometric layout 5.identify the fundamental and incidental interactions between clusters 6.Define subsystems from clusters Sketch the Product from this architectural analysis

7 Suggested Questionnaire on Team member effectiveness Each member does for each other member of team Leader collates and team discusses Improvements discussed member 1 member 2 etc. Criteria Regularly attended meetings Was on time Made positive contribution to meetings Shared project load equally Helped to manage conflict Helped to advance project This is just an example of how you can “take the temperature” of your team’s effectiveness

Next Tuesday No homework We will go over risk analysis so you know what to do for the midterm. There will be an in-class exercise Nothing should stop your work on market research

9 What is Product Architecture? Three related parts – The definition and the arrangement of functional elements – The mapping of these elements to physical components – The specification of interfaces among interacting physical components

10 Some System Engineer Roles... Formulate and structure the System Architectural Structure create a schematic of the product reflects the teams best understanding of the product’s functionality cluster the elements of the schematic reflect geometric integration, function sharing, vendor expertise considerations, localization of change accommodate variety, enable standardization, portability of interfaces (laser light, electrical vs mechanical) create a rough geometric layout identify the fundamental and incidental interactions between clusters define secondary sub-systems

11 Define subsystems from clusters Subsystem Architecture repeat above at the subsystem level Optimizing design across sub-system interfaces consider migration of components Trade Studies Alternative technologies Create detailed Specifications Planned Evolutionary Changes including Technology transparency Establishing Error Budgets, weight budgets, power budgets, etc.

12 A Functional Structure for a Trailer What other functions are possible?

13 Functional Elements Components Modular Architecture

14 What are the advantages and disadvantages of a modular architecture Plus Minus

15 ? What are the advantages and disadvantages of a modular architecture Plus Freedom to optimize Simplifies problem Prioritization Isolates problems Same device for different purposes Cheaper because of volume Minus More people with more specific expertise Harder to streamline More parts Constrained to fit in slot Single module failure Blame game

16 Types of Modular Architectures Slot – each component has a different coupling so cannot be interchanged (instrument panel of some airplanes, some parts of back plane of computers, others?) Bus – Common element which all components can connect to (track lighting, Ethernet, others?) Sectional – All interfaces are the same type (set of blocks, others?)

17 Interfaces Advantages and Disadvantages?

18 Integral Architecture

19 Examples of an Integral Architecture Fully custom VLSI chip One piece “monkey suit’ One room studio apartment? All in one printer/fax/scanner? Cell phone etc Other?

20 What are the advantages and disadvantages of a integral architecture? + _

21 What are the advantages and disadvantages of a integral architecture? Higher functionality Can be cheaper Inflexible Longer to design Harder to maintain Difficult to upgrade More complicated

22

23

24 Product Evolution Upgrade Add-ons Adaptation Wear Consumption Flexibility Maintainability Feature bundling Well-designed product architectures accommodate these life cycle changes

25 Product Families Spin out a variety of products from a common set of modules Reuse extensively Fast turn-around experiments to test market acceptance of features and to satisfy different segments Change Technology platforms infrequently

26 Trailer Example Different load strength trailer beds (modularized) normal or heavy duty environmental protection? Three sets of suspension springs Air drag streamlining or standard

27 Modular/Integral Which is preferred? FeatureMI Performance Time to Market Cost Upgrade Competitive defense Developing World

28 How to achieve product variety

29 Developing World Product Architectures Given conditions in Guatemala is there a bias for any particular architectural style? Condition Extreme cheapness Maintainability Scarce resources Poor Transportation infrastructure High uncertainty in product acceptance ? Architecture Integral Modular Integral Hybrid?

Class exercise Sketch a (first draft) architecture for your product Why did you choose this approach