Concepts Development : How To Create Products Customers Love
1 like166 views
The document discusses concepts development and creating products that customers love. It emphasizes that concept development is important for being creative in solving problems and addressing customer needs. A good concept explains what it is, why it is needed, and how it might be done. The document also stresses that systems engineers need to think holistically and take a big picture view of problems. It promotes the idea of being a "T-shaped professional" with both broad and deep skills to effectively develop concepts for complex systems.
Concepts Development : How To Create Products Customers Love
- 1. Concepts Development How To Create Products Customers Love Escuela Politécnica Superior Universidad Carlos III de Madrid Leganés ( Madrid) , Spain, 4th December 2017 Bernardo A. Delicado [email protected]
- 2. 2 About me
- 3. Content 3 SW a Game Changer Concept Development T-Shaped Professional Conclusions Introduction
- 4. Content 4 SW a Game Changer Concept Development T-Shaped Professional Conclusions Introduction
- 5. Progress in Technology has been Astonishing
- 6. Complex Global Trends 6 SE Vision 2025. Copyright © 2014 by INCOSE. All rights reserved. Human Needs translate to… Societal Needs that are satisfied by… System Solutions
- 8. 8 10 Principles Next Revolution
- 9. 9 Core technologies make up next industrial revolution Source : IoT Analytics
- 10. 10 Cyber-physical systems has a complex combination of computational and physical dimensions. Pyster et al ( 2015 )
- 11. Systems Engineering needed due to product complexity is increasing • High Complexity • Multidisciplinary • Cost • Time
- 12. 12 DIGITAL WORLD
- 13. Content 13 SW a Game Changer Concept Development T-Shaped Professional Conclusions Introduction
- 14. 14 “in the future, all companies will be software companies” – in other words, fulfilling the high expectations of tomorrow’s consumers will require a seamless, coherent approach, centered on big data, and that this “software” will be the ultimate source of competitive advantage”. George Colony, CEO Forrester Research
- 15. Software vs Systems 15 Software is fundamental to the performance, features, and value of most modern systems. Software often shapes the system architecture; drives much of its complexity and emergent behavior; strains its verification; and drives much of the cost and schedule of its development. Pyster et al ( 2015 )
- 16. Source Lines of SW code 16 Software is in everything now, and people who code are among the highest in-demand employees not only in tech but every industry you can imagine.
- 17. Source Lines of SW code 17
- 18. Creating Systems that work : Principles 1. Debate, define, revise and pursue the purpose / need 2. Think holistically 3. Follow a systematic procedure 4. Be creative 5. Take account of the people 6. Manage the project and the relationships 18 ( UK Royal Academy of Engineering , 2007)
- 19. Think Holistically means 19 It refers to the holistic appreciation of the problem ( big picture ), considering its context, stakeholders, and the interrelationships and interconnections.
- 20. Need vs Systematic Procedure 20 Arrichiello ( 2014 ) All design begins with a clearly defined need All designs result in a system, product or service which meets the need All designs arise from a creative response to a need
- 21. People 21 Conceive Design Implement Operate Need Vision Delivery Creating Systems = Multidisciplinary Battle
- 22. Jumping to Solutions 22 It is very difficult for people describing requirements to avoid jumping to solutions instead of describing needs. This constrains the team in realizing the optimal solution and fails to employ the full creativity of the team. The difficulty lies not so much in developing new ideas as in escaping from old ones
- 23. Problem Space vs Solution Space : Keeping Separate is Critical 23 Problem Space Systems QUESTIONS Solution Space Technologies & Products ANSWERS It is all about needs It is all about the offerings that satisfy needs
- 24. Introduction to INCOSE 24 The problemProblem
- 25. Introduction to INCOSE 25
- 26. Introduction to INCOSE 26
- 27. Introduction to INCOSE 27
- 28. Introduction to INCOSE 28
- 29. Introduction to INCOSE 29
- 30. Introduction to INCOSE 30
- 31. Introduction to INCOSE 31
- 32. 32 No comments
- 33. Example 33 Problem Space QUESTIONS Problem/Need : Transport from Madrid to Leganés Solution Space ANSWERS
- 34. 34 Keeping separate Problem Space from Solution Space is critical to produce new unknown disruptive concepts addressing the need
- 36. Addressed Customer’s or Users' Real Needs ? Introduction to INCOSE 36 Selected CONCEPT
- 37. Perspectives 37
- 38. Procesosde Ingeniería de Sistemas Personas con competencias Organización Different views of the same Problem ( System ) @bernardo
- 39. 39 Copyright © 2014 Jeff Patton. All rights reserved.
- 40. Problem 40 HAVING a problem IS NOT a problem. PAYING a problem IS a problem. ( Salado, 2013 )
- 41. Introduction to INCOSE 41 Solved the Problem ?
- 43. 43
- 44. 44
- 45. 45
- 46. 46
- 48. Concept 48 A concept is an idea…….. It is the way people see and understand something Wikipedia, the free encyclopedia
- 49. Concept 49 A concept is when the idea has been considered and a clear understanding of how , what, why, where and who has been identified
- 50. Concept is Needed 50 Why ?
- 51. Debilidad Procesosde Ingeniería de Sistemas Personas con competencias Organización Help you To be creative in the Problem Space
- 52. Be Creative 52 Adopting a new technology or system is about innovation. It’s about finding the use cases where the new technology/system adds real, tangible value for customers.
- 53. A Concept Should 53 • Explain “What it is” • Explain “Why it is needed” • Imagine “How it might be done”
- 54. Concept Development 54 • Needs Analysis : Defines the need for a new system and determines if there is a practical approach to satisfying such a need • Concept Exploration : Examines potential system concepts and identifies required performance and feasibility of possible approaches • Concept Definition : Analyses a number of alternative concepts in order to select a preferred concept that will be developed Conceive Design Implement Operate
- 55. Be Creative 55 Adopting a new technology or system is about innovation. It’s about finding the use cases where the new technology/system adds real, tangible value for customers.
- 56. Concept Development : Methodology 56 Source : Central Office of Design UK
- 57. 57 Processes Technical Processes Project Management Processes Business & Organization OtherOrganizations V Manage the project and the relationships
- 58. Content 58 SW a Game Changer Concept Development T-Shaped Professional Conclusions Introduction
- 59. 59 If we want to make great software, we have to have great people
- 60. 60 Your Thinking ? Do you see the System ?
- 61. 61 I see the System
- 62. 62 I see the Big Picture
- 63. T-Shaped Professional 63 Breath Deep Ability to work outside of core area Specialty or core area of expertise
- 64. 64 IT Sector promoting T-Shaped
- 65. Top 10 Skills in 2020 65 Complex Problem Solving Critical Thinking Creativity People Management Coordinating with Others Emotional Intelligence Judgment and Decision Making Service Orientation Negotiation Cognitive Flexibility
- 66. Content 66 SW a Game Changer Concept Development T-Shaped Professional Conclusions Introduction
- 67. Conclusions • Concept development is the vehicle of collaboration and reinventing the systems. • Concept development is about creativity and innovation. • Computer Science/ Software Engineering fundamental in the future systems concepts • A software engineer thinking big needed for developing successful systems concepts. 67
- 68. 68 Thank You
- 69. References • Arrichiello, Vincenzo ( 2014 ), “Introduction to Systems Engineering”, INCOSE Italian Chapter Conference on Systems Engineering (CIISE2014), Rome, Italy, November 24 – 25, 2014 • Patton, Jeff (2014), “User Story Mapping”, Published by O’Reilly Media, Inc., ISBN: 978-1-491-90490-9 • Pyster, Art; Adcock , Rick; Ardis, Mark ; Cloutier, Rob ; Henry,Devanandham; Laird, Linda; Lawson, Harold ‘Bud’; Pennotti, Michael ; Sullivan, Kevin ; Wade, Jon ( 2015 ), “Exploring the Relationship between Systems Engineering and Software Engineering”, 2015 Conference on Systems Engineering Research, Procedia Computer Science 44 ( 2015 ) 708 – 717, doi: 10.1016/j.procs.2015.03.016 • Salado, Alejandro ( 2013) , “Problems during system integration: When architecture and contracts meet”, KSEE 2013 - Kongsberg systems engineering event. • UK Royal Academy of Engineering ( 2007), “Creating systems that work: Principles of engineering systems for the 21st century”, ISBN: 1-903496-34-9 69