ENGN2225 Systems Engineering Design Semester 1, 2016 Design Toolkit Course Topics and Reading Guide v2016.1 In this guide ENGN2225 Design Processes ............................................1 Getting Started - resources and topic overview ..................4 1. Needs and Opportunities ....................................5 2. Problem Scoping ..............................................10 3. Idea Generation ................................................14 4. Requirements Mapping ....................................18 5. Logic & Functional Analysis ..............................22 6. System Architecture .........................................26 7. Testing, Verification and Evaluation ...................30 8. Design Communication ....................................34 This resource has been compiled to support learning in ENGN2225 Systems Engineering Design, and draws inspiration from a wide variety of sources. This document is supplemented by a detailed assessment guide and course outline [email protected] Note that ALL RESOURCES ARE IN THE RESOURCES DIRECTORY Also see the ONLINE CLASSROOM for videos on certain topics ENGN2225 DESIGN PROCESS The topics covered in ENGN2225 follow a spiral design process. In a spiral design process, as you move towards the centre you get closer to your eventual design. Although formally in the course we cover the topics once, in a spiral process you should move around the topics multiple times and as quickly as possible – you might also jump around across different tools to get to where you need to go. This strategy allows you to advance your ideas faster than your competitors for the benefit of your clients. Desktop Research Field Plan & Interviews Technical Drawing Problem Framing Rapid Prototyping [Start] Needs & Opportunities Roadmapping 1 Discover Problem Scoping Design Communication 8 2 System Boundary [Repeat] Journey Mapping Testing, Stakeholder Analysis Validation & Evaluation Prototype 7 3 Unit Testing Idea Generation Ideate System Validation Structured Brainstorming 6 Concept Generation Evaluation Matrices Describe 4 Scenario Planning System Architecture 5 Requirements Analysis Subsystem Interface Logic & Functional Analysis Pairwise Analysis Subsystem Mapping Logical Flow Technical Performance Measures COTS v Custom Functional Flow Requirements Mapping Functional Breakdown "1 2 Problem Scoping Requirements Analysis Convergent Thinking 4 Logic & Functional Analysis 5 Needs & Opportunities Idea Generation System Architecture Design Communication 1 3 Testing, 6 Validation & Evaluation 8 Divergent Thinking 7 time Prototype Describe Ideate Discover Another way of thinking about your journey through the tools in ENGN2225 is assimilate two complementary design thinking frameworks - IDEO.org’s divergent-convergent approaches, and the Double Diamond approach, where initially the divergent-convergent thinking is done to define the strategy, and then completed again to execute the solution. See the Design Approaches lecture for even more strategies for executing design, including the traditional systems engineering Vee-model and the more competitive approach of OODA loops. "2 ADVICE TO THE STUDENT SYSTEMS ENGINEER Systems engineering is both an art and a science, and as a design science, it sits at the intersection of creativity and the natural sciences. The ideas herein are to be nurtured and explored as you build up the model to describe your system. However, the famous George Box quotation should be at the forefront of your thinking: “All models are wrong, but some are useful.” With that in mind, make sure your analysis is at least useful. "3 GREAT RESOURCES There is no set textbook in this class. However, Idea Generation there are a number of great resources for Once you have empathised with your user and investigating systems design: understand the scope of your opportunity, you’re • IDEO’s human-centred design process (Online ready to start generating ideas about the or download PDF - highly recommended reading) opportunity. The tools in this week help your • Service Design Tools has great collection of group explore the possibilities of design. activities and ideas for design: http://www.servicedesigntools.org/tools/ Requirements Analysis • Stasinopoulos, P., Smith, M., Hargroves, K. and Defining your requirements moves the project Desha, C., 2008. Whole System Design - An from exploratory into the specific. By defining the I n t e g r a t e d A p p ro a c h t o S u s t a i n a b l e requirements, the specific parameters of the Engineering, The Natural Edge Project, project become measurable. Defining the right Earthscan, London. (Online resource) customer requirements will ultimately push you • S y s t e m s E n g i n e e r i n g F u n d a m e n t a l s , towards a high-quality deliverable. Department of Defence (Download PDF) Logical and Functional Analysis • MIT’s Opencourseware subject on systems engineering (Online - check out the reading list You can describe a system using many lenses. too..) Here, you describe your design through logical and functional steps. A logical breakdown can • Hitchens, D.K., 2007, ‘Systems Engineering - A 21st Century Systems Methodology’, John be used to describe how a user interacts with the Wiley & Sons, New Jersey. system to reach their goal, and a functional breakdown examines how functions can be • Blanchard, B.S., W.J. Fabrycky, Systems Engineering and Analysis, Fifth ed. Pearson, grouped together. New Jersey, 2011. System Architecture Building on the functional analysis, we move into TOPIC OVERVIEW how the system components interact with each other. Designs can be highly modular or highly There are eight perspectives that we consider in integrated, and there are positives and negatives Systems Engineering Design. for each approach. By describing the interactions between subsystems, the arrangement of the Needs and Opportunities (run by your tutor) design becomes explicit. The best engineers don’t solve problems, they find opportunities that build on the strengths of Testing, Validation and Evaluation users. They do this through mapping the problem Before moving to a complete design, testing space, and taking the time to understand the needs to be carried out to ensure that each needs of their users. In this topic we’ll cover how subsystem is performing correctly against the to discover the needs and opportunities. requirements. It’s at this point you can comparatively evaluate your design against other Problem Scoping options and the existing situation. Now that you have explored the problem space, it’s time to empathise; that is, to see the Design Communication (self-directed) problem from your client’s perspective. We’ll use At the end of the day, there’s no point creating a two tools that help you to understand other’s design if you can’t communicate it - this could be perspectives: journey mapping and stakeholder through a physical or digital prototype of the analysis. Finally, we’ll put the scope around the design, or through other methods that problem by defining the system boundary. communicate how the design works, and what opportunity the design meets. "4 1. NEEDS AND OPPORTUNITIES ‘Needs and opportunities’ is the first step of our design journey. In this stage of the design cycle, we are in a ‘Discover’ mode, looking for opportunities that can build on the strengths of the user, client or community, and can also address their needs. We will use three tools: Problem Framing, Desktop Research and Field Plan & Interviews. Problem Framing Desktop Research Field Plan & Interviews [Start] Needs & Opportunities 1 Discover Problem Scoping Design Communication 8 2 [Repeat] Testing, Validation Prototype & Evaluation Idea Generation 7 3 Ideate System Architecture 6 Requirements Analysis Describe 4 5 Logic & Functional Analysis At this stage of the process, your thinking should be diverging, ahead of refining your group’s thinking in the Problem Scoping stage. 2 Problem Scoping Requirements Analysis Convergent Thinking 4 Logic & Functional Analysis 5 Needs & Opportunities System Architecture Design Communication Idea Generation 3 Testing, Validation & Evaluation 1 6 8 Divergent Thinking 7 time Prototype Describe Ideate Discover "5 1.1 Problem Framing Framing your problem correctly turns it into an opportunity Framing your problem as an opportunity allows you to think in divergent ways. By putting a positive frame on your design thinking, you move from ‘helping’ your client to ‘empowering’ your user. A positive frame can inspire a virtuous cycle of good-will towards the project, and by looking for opportunities you are likely to come up with a better end result. Example applications Problem framing is used in a wide array of discipline areas, across the sciences and humanities. Framing a problem as an opportunity usually involves looking at the problem holistically. A classic example is the Great Horse Manure Crisis of 1894 in New York City, where the number of horses (and their excretions) were filling up the streets. The problem wasn’t solved by looking at the horse, but the introduction of the automobile ‘solved’ this problem. Another example is the accessibility features of an iPhone, which have revolutionised the way that people with vision or hearing disabilities interact with technology. Steps Framing a problem is best done individually at first, then bring together all your group’s ideas. Reframing problems is seen all the time in politics. George Lakoff 1. Write down your design problem in one sentence. (personal website) describes how