A very short and compact introduction to the great field of Systems (Design and) Engineering. I gave this presentation on September 7th at the Opening of the Industry Academy at University College of Southeast Norway, in Kongsberg, Norway.
Systems engineering is an interdisciplinary approach that focuses on defining customer needs and system functionality early in development, then proceeding through design while considering the complete problem of operations, cost schedule, performance and more. As systems increase in complexity, multidisciplinarity and cost, the need for systems engineering has grown. Systems engineering differs from traditional engineering by taking a holistic view of the system and emphasizing interactions between system components and the environment. Effective practice of systems engineering requires consideration of both technical and social aspects through processes, methods and an emphasis on interdisciplinary teamwork.
status of INCOSE Systems Engineering Handbook 5th Edition - AISE Annual EventBernardo A. Delicado
The document provides an overview of the status of the Fifth Edition of the INCOSE Systems Engineering Handbook. It discusses the schedule, requirements, and architecture of the Fifth Edition. The Fifth Edition is on track to be published in July 2023 after a final review period in September/October 2022 and incorporating feedback. The Fifth Edition will continue to reflect best practices in systems engineering and be aligned with updated international standards.
The document summarizes a presentation on systems engineering and technical leadership given at the Escuela Técnica Superior de Ingenieros Industriales, Universidad Politécnica de Madrid on May 22, 2017. It discusses systems engineering as an interdisciplinary approach that requires technical leadership to integrate different skills and address increasingly complex problems. It also examines the skills and career path of systems engineers, including their roles in facilitating collaboration and enabling successful project outcomes through systems thinking.
The document is a presentation about the international standard ISO/IEC/IEEE 42010:2011, Systems and software engineering—Architecture description. It provides an overview of the standard's history, core concepts, use and application. The presentation covers topics such as the motivation for architecture standards, the development of IEEE 1471 and its internationalization, key terms and concepts defined in the standard, and how the standard can be applied.
This describes the concept of a Process Oriented Architecture. A Process Oriented Architecture is a way of linking process areas to actual (desired) interactions – customer (external interacting party) service journeys through the organisation. It allows two views of any process to be maintained and operated:
1. External view – that experienced by user
2. Internal view – that worked on by the organisational competency
An organisation will interact will multiple external parties. Each external party will have a number of interaction paths or journeys. These journeys are the routes of experience of external parties. These routes of experience need to be mapped (as) seamlessly (as possible) to internal organisational operational process competency groupings.
The interaction paths or journeys represent the Straight Through Processing that the customer (external party) wants to experience. The complexity of internal organisational operational process competency groupings needs to be masked from the customer (external party). Process Oriented Architecture is a key enabler of successful digital transformation.
This document discusses the relationship between enterprise architecture (EA) and project and portfolio management (PPM). It argues that EA and PPM have different but complementary perspectives in helping an organization translate strategy into realized value through portfolios and projects. The document provides examples of how EA and PPM can collaborate more effectively by having EA guide the enterprise towards its target state while PPM drives the enterprise strategically forward. It also provides a sample collaboration model where EA and the project manager work together on project architecture.
Enterprise Business Analysis Capability - Strategic Asset for Business Alignm...Alan McSweeney
This document discusses the role and importance of enterprise business analysis as a strategic capability for achieving business and IT alignment and driving innovation. Some key points:
- Enterprise business analysis can help translate business strategy into objectives, ensure IT solution delivery is aligned to strategy/objectives, and contribute to solution delivery governance.
- It involves analyzing business requirements and processes associated with changes, defining business solutions to deliver requirements/processes, and rebuilding the conversation between business and IT.
- Multiple levels of business analysis (enterprise, functional, IT) are needed to effectively prevent fragmentation across the organization and deliver solutions in response to business needs from strategy through delivery.
- Without this capability, IT risks delivering solutions that are not
Systems engineering is an interdisciplinary approach that focuses on defining customer needs and system functionality early in development, then proceeding through design while considering the complete problem of operations, cost schedule, performance and more. As systems increase in complexity, multidisciplinarity and cost, the need for systems engineering has grown. Systems engineering differs from traditional engineering by taking a holistic view of the system and emphasizing interactions between system components and the environment. Effective practice of systems engineering requires consideration of both technical and social aspects through processes, methods and an emphasis on interdisciplinary teamwork.
status of INCOSE Systems Engineering Handbook 5th Edition - AISE Annual EventBernardo A. Delicado
The document provides an overview of the status of the Fifth Edition of the INCOSE Systems Engineering Handbook. It discusses the schedule, requirements, and architecture of the Fifth Edition. The Fifth Edition is on track to be published in July 2023 after a final review period in September/October 2022 and incorporating feedback. The Fifth Edition will continue to reflect best practices in systems engineering and be aligned with updated international standards.
The document summarizes a presentation on systems engineering and technical leadership given at the Escuela Técnica Superior de Ingenieros Industriales, Universidad Politécnica de Madrid on May 22, 2017. It discusses systems engineering as an interdisciplinary approach that requires technical leadership to integrate different skills and address increasingly complex problems. It also examines the skills and career path of systems engineers, including their roles in facilitating collaboration and enabling successful project outcomes through systems thinking.
The document is a presentation about the international standard ISO/IEC/IEEE 42010:2011, Systems and software engineering—Architecture description. It provides an overview of the standard's history, core concepts, use and application. The presentation covers topics such as the motivation for architecture standards, the development of IEEE 1471 and its internationalization, key terms and concepts defined in the standard, and how the standard can be applied.
This describes the concept of a Process Oriented Architecture. A Process Oriented Architecture is a way of linking process areas to actual (desired) interactions – customer (external interacting party) service journeys through the organisation. It allows two views of any process to be maintained and operated:
1. External view – that experienced by user
2. Internal view – that worked on by the organisational competency
An organisation will interact will multiple external parties. Each external party will have a number of interaction paths or journeys. These journeys are the routes of experience of external parties. These routes of experience need to be mapped (as) seamlessly (as possible) to internal organisational operational process competency groupings.
The interaction paths or journeys represent the Straight Through Processing that the customer (external party) wants to experience. The complexity of internal organisational operational process competency groupings needs to be masked from the customer (external party). Process Oriented Architecture is a key enabler of successful digital transformation.
This document discusses the relationship between enterprise architecture (EA) and project and portfolio management (PPM). It argues that EA and PPM have different but complementary perspectives in helping an organization translate strategy into realized value through portfolios and projects. The document provides examples of how EA and PPM can collaborate more effectively by having EA guide the enterprise towards its target state while PPM drives the enterprise strategically forward. It also provides a sample collaboration model where EA and the project manager work together on project architecture.
Enterprise Business Analysis Capability - Strategic Asset for Business Alignm...Alan McSweeney
This document discusses the role and importance of enterprise business analysis as a strategic capability for achieving business and IT alignment and driving innovation. Some key points:
- Enterprise business analysis can help translate business strategy into objectives, ensure IT solution delivery is aligned to strategy/objectives, and contribute to solution delivery governance.
- It involves analyzing business requirements and processes associated with changes, defining business solutions to deliver requirements/processes, and rebuilding the conversation between business and IT.
- Multiple levels of business analysis (enterprise, functional, IT) are needed to effectively prevent fragmentation across the organization and deliver solutions in response to business needs from strategy through delivery.
- Without this capability, IT risks delivering solutions that are not
Patterns provide structure and clarity, enabling architects to establish their solutions across the enterprise. Moreover, these software patterns also help to link technology and business requirements in an effective and efficient manner. Patterns help to incorporate robust solutions for business problems due to it’s wide adoption as well as it’s reusability. In addition, patterns create a common method to communicate, document and describe solutions. This session will explain some of these patterns ranging from SOA (Service-Oriented Architecture), WOA (Web-Oriented Architecture), EDA (Event Driven Architecture), and IoT (Internet of Things)
This document provides an overview of systems engineering standards and processes. It discusses ISO/IEC/IEEE 15288, which provides a framework for managing systems throughout the lifecycle. The standard defines technical and technical management processes. It also discusses the Systems Engineering Body of Knowledge (SEBoK) and the INCOSE Systems Engineering Handbook, both of which are based on ISO/IEC/IEEE 15288. The document recommends following a systems engineering approach to aircraft development to help ensure safety and optimize costs over the lifecycle. It emphasizes integrating safety assessments into systems engineering processes from an early stage.
To tackle global and societal challenges like the SDG’s and Climate Change - we need collaborations at a scale beyond individual projects and organisations.
We need to invest in building our portfolio capabilities - so that we can have scalable impact and work across the whole system for transformation.
By orchestrating entire innovation ecosystems, we can bridge and create coherence between the adaptive and practical efforts that are at play. This session will focus on building an understanding of the capabilities and capacities that are needed in organisations to work in systems transformations.
In the Innovation Ecosystems for Transformation session of the States of Change Learning Festival 2020, Mikael Seppälä from Sitra Lab spoke about Orchestrating Innovation Ecosystems
(and Portfolios) for Transformation.
https://festival.states-of-change.org/event/orchestrating-innovation
Solution Architecture And (Robotic) Process Automation SolutionsAlan McSweeney
This document discusses solution architecture and robotic process automation solutions. It provides an overview of many approaches to automating business activities and processes, including tactical applications directly layered over existing systems. The document emphasizes that automation solutions should be subject to an architecture and design process. It also notes that the objective of all IT solutions is to automate manual business processes and activities to a certain extent. Finally, it states that confirming any process automation initiative happens within a sustainable long-term approach that maximizes value delivered.
Using Software Architecture Principles in PracticeEoin Woods
Architects have to balance providing clear guidance for important decisions with the need to let people get on and build their aspects of the system without interference. In this talk Eoin Woods explores how architecture principles can help achieve this by making constraints and priorities clear without being unnecessarily prescriptive about how they are to be implemented.
Presented at O'Reilly Software Architecture Conference in London during October 2016.
An introduction to fundamental architecture conceptswweinmeyer79
(Note: This is a very dated version of this popular deck, as SlideShare does not provide authors with a mechanism to update their documents. If interested in the latest version, feel free to message me on LinkedIn or at wweinmeyer@gmail.com. Also, feel free to ask SlideShare to bring back the ability to update posted documents.)
A discussion of the fundamentals you need to nail in your architecture practice:
- Architecture vs. Design
- Conceptual vs. Logical vs. Physical architecture
- Viewpoint Frameworks
- Architecture Domains
- Architecture Tiers
You are free to use/copy this information but if you do so, please include an acknowledgement
This document presents a vision for systems engineering in 2035. It discusses key trends that will influence systems engineering, including a changing global environment, evolving technology and systems, and increasing demands on enterprises. The document outlines four chapters that make up the vision:
1) The global context and trends that will drive changes in systems engineering
2) The current state of systems engineering practices, competencies, and challenges
3) The future state of systems engineering, including a model-based approach and skills needed for the future workforce
4) Steps to realize the vision, including collaboration and roadmaps to transition systems engineering
The document provides an overview of an IT operating model case study. It discusses building blocks for developing an IT operating model, including business context, business architecture, application architecture, technology architecture, IT organization structure, IT governance, IT valuation, IT budget plan, IT portfolio management, and IT roadmap. It also describes potential deliverables from an IT operating model project such as an enterprise architecture document, IT organization structure, IT governance framework, and IT investment analysis. The case study methodology involves assessing current IT effectiveness, developing an optimal IT organization structure, and aligning IT investment with business planning.
Insights on Procurement Data with Analytics Solutions from SAPSAP Ariba
This document discusses insights on procurement data analytics solutions from SAP. It introduces speakers from Vodafone and SAP and outlines an agenda covering executive dashboarding using Supply Watch at Vodafone, process mining using Celonis at Vodafone, and advanced analytics using SAP Fraud Management. The document provides details on each of these topics and opportunities for data mining in procurement organizations.
Application Rationalization with LeanIXLeanIX GmbH
In this presentation from EA Connect Days 2018 in Bonn you learn about the benefits of Application Rationalization and how to optimize your Application Portfolio with LeanIX.
Why New-age IT Operating Models are Necessary for Enhanced Operational AgilityCognizant
IT organizations need a new operating model consisting of automated tools, refined thinking around operating discipline, and more relevant talent acquisition and management strategies. This new model will not only help IT deliver tailored services to a new generation of users, but it will also unlock the vast potential of emerging digital business opportunities made possible by the quickly maturing SMAC Stack.
This Toolkit was created by ex-McKinsey, Deloitte and BCG Management Consultants after more than 3,000 hours of work. It shares our combined 100+ years of experience advising executive teams around the world. It includes all the Frameworks, Best Practices & Templates required to successfully implement an operating model and organization design initiative, and make your strategy happen.
The document discusses delivering enterprise architecture using TOGAF and ArchiMate. It introduces BiZZdesign, an experienced consultancy firm that provides tools and training for enterprise architecture. The proposed schedule covers topics like enterprise architecture, ArchiMate core language and extensions, TOGAF ADM process, and examples of modeling with ArchiMate. The case study involves applying TOGAF and ArchiMate to help a insurance company consolidate their fragmented IT systems by migrating to a single back-office system.
An overview of The Open Group IT4IT Reference Architecture. It is a vendor and product-agnostic value chain-based operating model for managing the business of IT. While providing guidance on the design, procurement and implementation of the functionality needed to run IT, it also enables the systematic tracking of the state of IT services across the service life-cycle using four value streams - Strategy to Portfolio, Request to Fulfill, Requirement to Deploy, and Detect to Correct.
Download presentation from http://opengroup.co.za/presentations
Bringing Architecture Thinking to the People - An introduction into the PEOPL...Craig Martin
The successful implementation of an architecture plan or blueprint is often challenged not in the efficacy of the design elements of the architecture, but in its implementation by people in business operations. Transformation programs will often struggle as a consequence of the failure to consider the issues impacting and the role of people in supporting the target operating state of the architecture once implemented, it is therefore imperative that when architects innovate, model and design to solve business problems, that they equally consider the people dimension. Capability based planning is incomplete unless we address the optimum mix of people, process and tools to drive out the target outcome of that capability. This presentation will look at a case study from within the Australian market in which Business Capability Based Planning was applied to assess people capabilities and organisation preparedness to support a target business model. It will also discuss some of the more effective people levers that can be applied to deliver more impactful and long lasting architectural change.
The document provides an overview of enterprise architecture foundations, including stakeholders, views and viewpoints, the enterprise continuum, and architecture repositories. It explains that the enterprise continuum classifies architecture and solution artifacts and consists of the architecture, solution, and enterprise continua. The architecture continuum shows the relationships between foundational, common, industry, and enterprise architectures, aiming to discover commonality and eliminate redundancy. It also establishes an architecture repository structure and tool standardization.
IT4IT and DevOps Tools Landscape (2020).Rob Akershoek
Complete overview of the IT management tooling landscape 2020. Key market players / vendors in the IT4IT and DevOps tooling ecosystem. Automate and streamline your end-to-end DevOps tool chain.
Business Value Measurements and the Solution Design FrameworkLeo Barella
The presentation covers a process and artifacts to establish better communication between business and IT and improve the quality and consistency of solutions. It also includes a tool to measure business value of the solutions that are being proposed and allows the business audience to make educated choices based on overall IT Business impact.
This document discusses various heuristics and principles for architecture design. It provides guidelines for creating simplified, evolvable systems using small modular components. Some key points discussed include using open architectures, building in options, and designing structures that are resilient to stress. The document also advocates for pattern-oriented, minimalist designs and evolutionary systems that can adapt over time without disrupting existing information. Overall, the document presents best practices for handling complexity, enabling flexibility, and ensuring architectures can withstand failures.
This document discusses the business and organizational implications of multi-speed IT. It begins by setting the stage on how information growth, disruptive innovations, and market speed are accelerating exponentially. It then discusses the concepts of multi-speed IT and how systems of innovation can operate differently than traditional systems of record. The document outlines some technical, business, and organizational challenges that multi-speed IT presents. It concludes that while multi-speed IT adds complexity, it allows organizations to embrace change while maintaining existing systems.
Patterns provide structure and clarity, enabling architects to establish their solutions across the enterprise. Moreover, these software patterns also help to link technology and business requirements in an effective and efficient manner. Patterns help to incorporate robust solutions for business problems due to it’s wide adoption as well as it’s reusability. In addition, patterns create a common method to communicate, document and describe solutions. This session will explain some of these patterns ranging from SOA (Service-Oriented Architecture), WOA (Web-Oriented Architecture), EDA (Event Driven Architecture), and IoT (Internet of Things)
This document provides an overview of systems engineering standards and processes. It discusses ISO/IEC/IEEE 15288, which provides a framework for managing systems throughout the lifecycle. The standard defines technical and technical management processes. It also discusses the Systems Engineering Body of Knowledge (SEBoK) and the INCOSE Systems Engineering Handbook, both of which are based on ISO/IEC/IEEE 15288. The document recommends following a systems engineering approach to aircraft development to help ensure safety and optimize costs over the lifecycle. It emphasizes integrating safety assessments into systems engineering processes from an early stage.
To tackle global and societal challenges like the SDG’s and Climate Change - we need collaborations at a scale beyond individual projects and organisations.
We need to invest in building our portfolio capabilities - so that we can have scalable impact and work across the whole system for transformation.
By orchestrating entire innovation ecosystems, we can bridge and create coherence between the adaptive and practical efforts that are at play. This session will focus on building an understanding of the capabilities and capacities that are needed in organisations to work in systems transformations.
In the Innovation Ecosystems for Transformation session of the States of Change Learning Festival 2020, Mikael Seppälä from Sitra Lab spoke about Orchestrating Innovation Ecosystems
(and Portfolios) for Transformation.
https://festival.states-of-change.org/event/orchestrating-innovation
Solution Architecture And (Robotic) Process Automation SolutionsAlan McSweeney
This document discusses solution architecture and robotic process automation solutions. It provides an overview of many approaches to automating business activities and processes, including tactical applications directly layered over existing systems. The document emphasizes that automation solutions should be subject to an architecture and design process. It also notes that the objective of all IT solutions is to automate manual business processes and activities to a certain extent. Finally, it states that confirming any process automation initiative happens within a sustainable long-term approach that maximizes value delivered.
Using Software Architecture Principles in PracticeEoin Woods
Architects have to balance providing clear guidance for important decisions with the need to let people get on and build their aspects of the system without interference. In this talk Eoin Woods explores how architecture principles can help achieve this by making constraints and priorities clear without being unnecessarily prescriptive about how they are to be implemented.
Presented at O'Reilly Software Architecture Conference in London during October 2016.
An introduction to fundamental architecture conceptswweinmeyer79
(Note: This is a very dated version of this popular deck, as SlideShare does not provide authors with a mechanism to update their documents. If interested in the latest version, feel free to message me on LinkedIn or at wweinmeyer@gmail.com. Also, feel free to ask SlideShare to bring back the ability to update posted documents.)
A discussion of the fundamentals you need to nail in your architecture practice:
- Architecture vs. Design
- Conceptual vs. Logical vs. Physical architecture
- Viewpoint Frameworks
- Architecture Domains
- Architecture Tiers
You are free to use/copy this information but if you do so, please include an acknowledgement
This document presents a vision for systems engineering in 2035. It discusses key trends that will influence systems engineering, including a changing global environment, evolving technology and systems, and increasing demands on enterprises. The document outlines four chapters that make up the vision:
1) The global context and trends that will drive changes in systems engineering
2) The current state of systems engineering practices, competencies, and challenges
3) The future state of systems engineering, including a model-based approach and skills needed for the future workforce
4) Steps to realize the vision, including collaboration and roadmaps to transition systems engineering
The document provides an overview of an IT operating model case study. It discusses building blocks for developing an IT operating model, including business context, business architecture, application architecture, technology architecture, IT organization structure, IT governance, IT valuation, IT budget plan, IT portfolio management, and IT roadmap. It also describes potential deliverables from an IT operating model project such as an enterprise architecture document, IT organization structure, IT governance framework, and IT investment analysis. The case study methodology involves assessing current IT effectiveness, developing an optimal IT organization structure, and aligning IT investment with business planning.
Insights on Procurement Data with Analytics Solutions from SAPSAP Ariba
This document discusses insights on procurement data analytics solutions from SAP. It introduces speakers from Vodafone and SAP and outlines an agenda covering executive dashboarding using Supply Watch at Vodafone, process mining using Celonis at Vodafone, and advanced analytics using SAP Fraud Management. The document provides details on each of these topics and opportunities for data mining in procurement organizations.
Application Rationalization with LeanIXLeanIX GmbH
In this presentation from EA Connect Days 2018 in Bonn you learn about the benefits of Application Rationalization and how to optimize your Application Portfolio with LeanIX.
Why New-age IT Operating Models are Necessary for Enhanced Operational AgilityCognizant
IT organizations need a new operating model consisting of automated tools, refined thinking around operating discipline, and more relevant talent acquisition and management strategies. This new model will not only help IT deliver tailored services to a new generation of users, but it will also unlock the vast potential of emerging digital business opportunities made possible by the quickly maturing SMAC Stack.
This Toolkit was created by ex-McKinsey, Deloitte and BCG Management Consultants after more than 3,000 hours of work. It shares our combined 100+ years of experience advising executive teams around the world. It includes all the Frameworks, Best Practices & Templates required to successfully implement an operating model and organization design initiative, and make your strategy happen.
The document discusses delivering enterprise architecture using TOGAF and ArchiMate. It introduces BiZZdesign, an experienced consultancy firm that provides tools and training for enterprise architecture. The proposed schedule covers topics like enterprise architecture, ArchiMate core language and extensions, TOGAF ADM process, and examples of modeling with ArchiMate. The case study involves applying TOGAF and ArchiMate to help a insurance company consolidate their fragmented IT systems by migrating to a single back-office system.
An overview of The Open Group IT4IT Reference Architecture. It is a vendor and product-agnostic value chain-based operating model for managing the business of IT. While providing guidance on the design, procurement and implementation of the functionality needed to run IT, it also enables the systematic tracking of the state of IT services across the service life-cycle using four value streams - Strategy to Portfolio, Request to Fulfill, Requirement to Deploy, and Detect to Correct.
Download presentation from http://opengroup.co.za/presentations
Bringing Architecture Thinking to the People - An introduction into the PEOPL...Craig Martin
The successful implementation of an architecture plan or blueprint is often challenged not in the efficacy of the design elements of the architecture, but in its implementation by people in business operations. Transformation programs will often struggle as a consequence of the failure to consider the issues impacting and the role of people in supporting the target operating state of the architecture once implemented, it is therefore imperative that when architects innovate, model and design to solve business problems, that they equally consider the people dimension. Capability based planning is incomplete unless we address the optimum mix of people, process and tools to drive out the target outcome of that capability. This presentation will look at a case study from within the Australian market in which Business Capability Based Planning was applied to assess people capabilities and organisation preparedness to support a target business model. It will also discuss some of the more effective people levers that can be applied to deliver more impactful and long lasting architectural change.
The document provides an overview of enterprise architecture foundations, including stakeholders, views and viewpoints, the enterprise continuum, and architecture repositories. It explains that the enterprise continuum classifies architecture and solution artifacts and consists of the architecture, solution, and enterprise continua. The architecture continuum shows the relationships between foundational, common, industry, and enterprise architectures, aiming to discover commonality and eliminate redundancy. It also establishes an architecture repository structure and tool standardization.
IT4IT and DevOps Tools Landscape (2020).Rob Akershoek
Complete overview of the IT management tooling landscape 2020. Key market players / vendors in the IT4IT and DevOps tooling ecosystem. Automate and streamline your end-to-end DevOps tool chain.
Business Value Measurements and the Solution Design FrameworkLeo Barella
The presentation covers a process and artifacts to establish better communication between business and IT and improve the quality and consistency of solutions. It also includes a tool to measure business value of the solutions that are being proposed and allows the business audience to make educated choices based on overall IT Business impact.
This document discusses various heuristics and principles for architecture design. It provides guidelines for creating simplified, evolvable systems using small modular components. Some key points discussed include using open architectures, building in options, and designing structures that are resilient to stress. The document also advocates for pattern-oriented, minimalist designs and evolutionary systems that can adapt over time without disrupting existing information. Overall, the document presents best practices for handling complexity, enabling flexibility, and ensuring architectures can withstand failures.
This document discusses the business and organizational implications of multi-speed IT. It begins by setting the stage on how information growth, disruptive innovations, and market speed are accelerating exponentially. It then discusses the concepts of multi-speed IT and how systems of innovation can operate differently than traditional systems of record. The document outlines some technical, business, and organizational challenges that multi-speed IT presents. It concludes that while multi-speed IT adds complexity, it allows organizations to embrace change while maintaining existing systems.
The document provides an overview of biomedical engineering design and related topics presented at Mbarara University of Science and Technology. It discusses what engineering design entails, the engineering design process, considerations for good design such as requirements and regulations. It also covers topics like prototyping, testing, human factors, intellectual property, and engineering ethics.
Based on my observations, in IT we suffer from continuous collective amnesia and we are even proud of it.
For at least 50 years meanwhile, we struggle how to build systems, that are easy to understand, to maintain, to change and to operate in a reliable way. Each time we hit the wall again, we start to look for a new silver bullet on the horizon, strongly believing that it will solve the problem for good.
The key word is "new": "New" is good in our community, while "old" is bad, worthless, crap. We suffer from youthism, not only in recruiting, but in all areas. This way we discard any "old" knowledge, no matter if it is valuable or not. We separate by age, not by value.
Additionally we continuously lose our collective memory with every new generation that leaves university as they are also taught not to value anything old and instead only look for the new, shiny stuff.
While not all old knowledge is worth being preserved, admittedly, there is still a lot of valuable old knowledge available, offering answers to the problems that we face today - creating maintainable and reliable systems, dealing with distribution and tackling complexity, just to name a few of the challenges.
This presentation is a journey through some (very) old computer science papers that contain a lot of very valuable knowledge regarding the problems we face today. For each of the papers, some of the key ideas are presented and how they address our current challenges.
Of course, the voice track is missing and there are a lot more papers that would be worth being mentioned in this presentation. Still, I hope that also the slides alone will be of some value for you - and convince you a bit that not everything "old" in IT is automatically worthless ... ;)
Annual address covering trends, emerging requirements, pain points and infrastructure issues in the "Bio-IT" aka life science informatics and HPC realm; Email me if you want a PDF of this talk - chris@bioteam.net
Chris Heilmann gave a talk at BTConf in Munich in January 2018 about machine learning, automation worries, and coding. He discussed how coding used to refer to creative programming within technical limitations but now often refers to programming for work. He addressed common worries about new technologies and dependencies, and argued that abstractions are not inherently bad and help more people build products together through consensus. The talk focused on using tools to be more productive and enabling rather than seeing them as dangers, and creating solutions for users rather than fighting old approaches.
Yiannis Kanellopoulos, Management Consultant for Sustainable Software, Software Improvement Group, at the Startup Founder 101 event that took place on Wednesday, February 12th, 2014 in the context of the"4th Infocom Mobiles & Apps 2014" conference.
Bim based process mining master thesis presentation Stijn van Schaijk
The document discusses using building information modeling (BIM) and process mining techniques to enable knowledge reassurance and problem discovery in construction and facility management. It describes case studies applying these methods, including analyzing a road design process with over 140,000 events and 1 specification with 1,904 process steps. Continuous on-site monitoring using drone scans and comparing as-built models to as-planned BIM models is also demonstrated. Process mining analytics can identify bottlenecks, social networks, and deviations to facilitate improved planning and risk identification for future projects.
CK: from ad hoc computer engineering to collaborative and reproducible data s...Grigori Fursin
Designing novel computer systems and optimizing their software is becoming too tedious, ad hoc, time consuming and error prone due to enormous number of available design and optimization choices. Empirical autotuning combined with run-time adaptation and machine learning has been demonstrating some potential to address above challenges for several decades but is still far from the widespread production. The main reasons include unbearably long exploration and training times, ever changing tools and their interfaces, lack of a common experimental methodology, lack of diverse and representative benchmarks, and lack of unified mechanisms for knowledge building and exchange apart from publications where reproducibility and reusability of results is often not even considered.
I will present our community-driven solution to above problems based on our open-source Collective Knowledge technology (CK) that can gradually organize, exchange and reuse knowledge and experience in computer engineering. CK helps share various artifacts (benchmarks, data sets, libraries, tools) as unified, reusable and Python-based components with JSON meta description via GITHUB. Researchers can then quickly prototype and crowdsource various experimental workflows such as performance and energy autotuning, design space exploration and run-time adaptation. At the same time, CK continuously analyzes and extrapolates all collected knowledge using powerful data science techniques to automatically model computer systems' behavior, predict better optimizations or hardware configurations, and eventually enable faster, more power efficient, reliable and self-tuning software and hardware. Furthermore, CK can record any unexpected behavior in a reproducible way and expose it to an interdisciplinary community to find missing features and improve models. Live demo of our approach is available at http://cknowledge.org/repo .
This document discusses software engineering concepts and the traditional waterfall development process. It notes that the waterfall process is not receptive to change and risks are not addressed until late in the project. The document then proposes an iterative development process that embraces change, identifies and resolves risks upfront, uses architecture and user involvement to improve outcomes. Overall it analyzes issues with the traditional approach and advocates for a better, more iterative software engineering process.
This document provides information about a computer organization and design course. It includes details about the instructor, tutors, grade determination, textbook, and course content. The course will cover major computer system components, CPU design, techniques for improving performance and energy efficiency, and multiprocessor architecture. It aims to teach how computer hardware and software interact and how design choices affect performance.
Research-Based Innovation with Industry: Project Experience and Lessons LearnedLionel Briand
The document discusses lessons learned from research projects conducted in collaboration with industry partners, focusing on defining problems, understanding context factors, developing domain models, and verifying requirements. It provides examples of projects in various domains like subsea systems, automotive, and satellite systems. The goal is to share success criteria and practical guidelines for performing industry-relevant engineering research.
Rapid prototyping is a technique used to quickly fabricate a scale model of a physical part or assembly using 3D computer-aided design (CAD) data and 3D printing technology. It originated in the late 1980s and allows for the production of models and prototype parts to test designs. Reverse engineering involves analyzing an existing system to recreate its components, while reengineering is a radical redesign not constrained by previous solutions. Concurrent engineering is an approach where design, manufacturing, and other functions integrate tasks concurrently to reduce time to market for new products.
2017 think - session 4085 - increase your agile velocity - integrate your d...M Kevin McHugh
This document discusses increasing development team velocity through continuous engineering using an Internet of Things (IoT) architecture. It notes that development complexity has increased as teams use many tools and repositories. An IoT approach pushes critical data and alerts to developers in real-time to make the right information available at the right time. The presentation demonstrates connecting an IBM tool to analyze and push event data to external services like Twitter to notify users. It aims to streamline continuous engineering processes using IoT concepts.
This document discusses scheduling and controls for project manufacturing. It begins by contrasting mass production, job shop manufacturing, and proposing project manufacturing as a third method. Project manufacturing schedules unique engineered products using critical path methodology (CPM). The document outlines automating schedule creation from routing and BOM data, integrating project schedules, resolving resource conflicts in an enterprise system, and concludes the approach provides benefits like improved project integration and controls for project manufacturing plants.
Develop, deploy, and operate services at reddit scale oscon 2018Gregory Taylor
The last few years have been a period of tremendous growth for Reddit. Process, tooling, and culture have all had to adapt to an organization that has tripled in size and ambition. Greg Taylor discusses Reddit's evolution and explains how one of the world’s busiest sites develops, deploys, and operates services at significant scale.
Presented at OSCON 2018 in Portland, Oregon
This document contains details about an engineering design and CAD modeling course taught by Dr. Vi Nguyen at the Vietnamese-German University. The course will cover topics like the engineering design process, CAD modeling, CAM, and CAE tools over 8 sessions from July 30th to August 27th. Sessions will be split between on-site and online meetings. Students will complete assignments, an exam, and a final project. The course will use textbooks on engineering design, technical drawing, CAD/CAM/CAE systems, and NX modeling software.
GENN001 Fall2013 Session #8 Problem SolvingEsmail Bialy
This document discusses the engineering approach to problem solving. It outlines the typical phases of the engineering design process, including identifying the problem, gathering data, searching for creative solutions, developing preliminary designs, evaluating solutions, preparing reports/plans, and implementing the design. It also discusses techniques like brainstorming, checklists, attribute listing and the use of models. Teamwork, failures, and a case study are also covered.
Simulation can help in both design and process optimization for additive manufacturing industry by getting the product right the first time. Cost saving by reducing print iterations can be tremendous. The presentation covers some overview of the AM industry and specifically discusses both metal and polymer AM simulation solutions.
This document discusses Building Information Modeling (BIM) and its implications for electrical engineers. It begins with an overview of BIM, explaining that BIM provides a digital representation of a facility and its physical and functional characteristics. It then discusses how BIM can benefit owners, design engineers, and contractors by improving coordination, reducing risks and costs, and streamlining processes. The remainder of the document focuses on a case study of a large hospital project where BIM was used, highlighting lessons learned around project setup, managing limitations, and the importance of communication and proper planning when adopting BIM.
A SYSTEMATIC RISK ASSESSMENT APPROACH FOR SECURING THE SMART IRRIGATION SYSTEMSIJNSA Journal
The smart irrigation system represents an innovative approach to optimize water usage in agricultural and landscaping practices. The integration of cutting-edge technologies, including sensors, actuators, and data analysis, empowers this system to provide accurate monitoring and control of irrigation processes by leveraging real-time environmental conditions. The main objective of a smart irrigation system is to optimize water efficiency, minimize expenses, and foster the adoption of sustainable water management methods. This paper conducts a systematic risk assessment by exploring the key components/assets and their functionalities in the smart irrigation system. The crucial role of sensors in gathering data on soil moisture, weather patterns, and plant well-being is emphasized in this system. These sensors enable intelligent decision-making in irrigation scheduling and water distribution, leading to enhanced water efficiency and sustainable water management practices. Actuators enable automated control of irrigation devices, ensuring precise and targeted water delivery to plants. Additionally, the paper addresses the potential threat and vulnerabilities associated with smart irrigation systems. It discusses limitations of the system, such as power constraints and computational capabilities, and calculates the potential security risks. The paper suggests possible risk treatment methods for effective secure system operation. In conclusion, the paper emphasizes the significant benefits of implementing smart irrigation systems, including improved water conservation, increased crop yield, and reduced environmental impact. Additionally, based on the security analysis conducted, the paper recommends the implementation of countermeasures and security approaches to address vulnerabilities and ensure the integrity and reliability of the system. By incorporating these measures, smart irrigation technology can revolutionize water management practices in agriculture, promoting sustainability, resource efficiency, and safeguarding against potential security threats.
A review on techniques and modelling methodologies used for checking electrom...nooriasukmaningtyas
The proper function of the integrated circuit (IC) in an inhibiting electromagnetic environment has always been a serious concern throughout the decades of revolution in the world of electronics, from disjunct devices to today’s integrated circuit technology, where billions of transistors are combined on a single chip. The automotive industry and smart vehicles in particular, are confronting design issues such as being prone to electromagnetic interference (EMI). Electronic control devices calculate incorrect outputs because of EMI and sensors give misleading values which can prove fatal in case of automotives. In this paper, the authors have non exhaustively tried to review research work concerned with the investigation of EMI in ICs and prediction of this EMI using various modelling methodologies and measurement setups.
KuberTENes Birthday Bash Guadalajara - K8sGPT first impressionsVictor Morales
K8sGPT is a tool that analyzes and diagnoses Kubernetes clusters. This presentation was used to share the requirements and dependencies to deploy K8sGPT in a local environment.
ACEP Magazine edition 4th launched on 05.06.2024Rahul
This document provides information about the third edition of the magazine "Sthapatya" published by the Association of Civil Engineers (Practicing) Aurangabad. It includes messages from current and past presidents of ACEP, memories and photos from past ACEP events, information on life time achievement awards given by ACEP, and a technical article on concrete maintenance, repairs and strengthening. The document highlights activities of ACEP and provides a technical educational article for members.
International Conference on NLP, Artificial Intelligence, Machine Learning an...gerogepatton
International Conference on NLP, Artificial Intelligence, Machine Learning and Applications (NLAIM 2024) offers a premier global platform for exchanging insights and findings in the theory, methodology, and applications of NLP, Artificial Intelligence, Machine Learning, and their applications. The conference seeks substantial contributions across all key domains of NLP, Artificial Intelligence, Machine Learning, and their practical applications, aiming to foster both theoretical advancements and real-world implementations. With a focus on facilitating collaboration between researchers and practitioners from academia and industry, the conference serves as a nexus for sharing the latest developments in the field.
Embedded machine learning-based road conditions and driving behavior monitoringIJECEIAES
Car accident rates have increased in recent years, resulting in losses in human lives, properties, and other financial costs. An embedded machine learning-based system is developed to address this critical issue. The system can monitor road conditions, detect driving patterns, and identify aggressive driving behaviors. The system is based on neural networks trained on a comprehensive dataset of driving events, driving styles, and road conditions. The system effectively detects potential risks and helps mitigate the frequency and impact of accidents. The primary goal is to ensure the safety of drivers and vehicles. Collecting data involved gathering information on three key road events: normal street and normal drive, speed bumps, circular yellow speed bumps, and three aggressive driving actions: sudden start, sudden stop, and sudden entry. The gathered data is processed and analyzed using a machine learning system designed for limited power and memory devices. The developed system resulted in 91.9% accuracy, 93.6% precision, and 92% recall. The achieved inference time on an Arduino Nano 33 BLE Sense with a 32-bit CPU running at 64 MHz is 34 ms and requires 2.6 kB peak RAM and 139.9 kB program flash memory, making it suitable for resource-constrained embedded systems.
Harnessing WebAssembly for Real-time Stateless Streaming PipelinesChristina Lin
Traditionally, dealing with real-time data pipelines has involved significant overhead, even for straightforward tasks like data transformation or masking. However, in this talk, we’ll venture into the dynamic realm of WebAssembly (WASM) and discover how it can revolutionize the creation of stateless streaming pipelines within a Kafka (Redpanda) broker. These pipelines are adept at managing low-latency, high-data-volume scenarios.
2. Who is presenting?
Maarten Bonnema (Dutch)
• With NISE and USN/HBV/HiBu since 2011
• Multidisciplinary Systems Design
• Systems Engineering in Electric Mobility
• Course owner Electric and Hybrid Vehicle
System Design
• Work experience as Systems Engineer at ASML
• Background:
– Electrical Engineering (UT)
– Post-master Design program (TUDelft)
– PhD on Systems Architecting (UT)
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 2
• Home institution:
3. Design versus Analysis
ANALYSIS
• Studying an existing situation/thing/effect
• In-depth
• Creating knowledge
• Single “correct” answer
• Descartian
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 3
DESIGN
• Creating something new
• Big picture
• Creating knowledge
• Many possible “correct” answers
• Holistic
Truths that are attained by reason are
broken down into elements that intuition
can grasp, which, through a purely
deductive process, will result in clear
truths about reality.
https://en.wikipedia.org/wiki/Rationalism
Holism (from Greek ὅλος
holos "all, whole, entire") is the
idea that systems (physical,
biological, hemical, social,
economic, mental, linguistic,
etc.) and their properties
should be viewed as wholes,
not just as a collection of parts.
https://en.wikipedia.org/wiki/Holism
4. How Design is often viewed
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 4
Problem Design
Complete
description of
the Solution
5. Questions that pop up immediately
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 5
• What is the problem?
– And how do I learn more about it?
– Is this the *real* problem, or a symptom
• What space do I have:
– To do the design
– For the solution
• Who has the need for a solution to this
problem?
• What will be the impact of the solution
• Etc.
Interestingly, development projects often start
from the solution…
SHOULD
7. Products versus Systems
in words
Products
• Mostly one-way influence
• Few users/stakeholders
• Optimization
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 7
Systems
• Two-way influence
• Multiple users
• Multiple stakeholders
• Trade-offs
• Large with multiple subsystems
• Multiple domains
8. Consequences
• We don’t create products, but systems
• These systems present an increasing impact
on the environment, and vice versa
• Most engineers are educated in creating
products
• Resulting in various problems and
unintended consequences*.
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 8
What happened?
• A fridge contains environmentally friendly
coolants that don’t work below 7 °C.
=> advice: put a heater next to it.
• Frequent use of autopilot improves
consistency, comfort, energy use.
But decreases the ability to handle non-
normal situations. [N.Carr, 201311]
*: http://www.econlib.org/library/Enc/UnintendedConsequences.html
9. 9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 9
• We are now the new product
definition team of an aircraft
manufacturer
Ways of looking at an airplane:
• Components:
– Engine(s)
– …
Ways of looking at an airplane:
• Aspects:
– what discerns this new
plane-type from another
– why would
KLM/SAS/Lufthansa/… buy
this type instead of
another
– …
A Small Exercise…
There are also functions, but these are mostly equal for all planes
11. 9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 11
System perspective Separate the what and
how-much from the how
Focus on interfaces
(in contrast to focus on
components)
This brings us to the Core of Systems Engineering
Uncertain and incomplete
information versus far-
reaching decisions
Multi-disciplinarity
Communication
12. System Perspective
• Put system central, instead of
focussing on details
• Zoom out to see the whole
• Zoom in on crucial issues only
• Holistic thinking
• Big picture; also time-wise
• Pitfall: stay too general or superficial.
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 12
• Tool: Nine window diagram (from TRIZ)
system of
interest
developing
organization
architect
super
system
customer
organization
subsystems
past system
of interest
past super
system
past
subsystems
past current future
future system
of interest
future super
system
future
subsystems
based on TRIZ
knowledge innovation
system of
interest
developing
organization
architect
super
system
customer
organization
subsystems
system of
interest
developing
organization
architect
Picture credit: Gerrit Muller www.gaudisite.nl
13. Example 9-window diagram
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 13
(Hybrid) Electric
Vehicle
Motor, air
conditioning, …
Personal Mobility,
including charging
stations
Internal Combustion
Engine Vehicle
Engine, drive train,
fuel tank, …
Personal Mobility,
including fuel services
Autonomous Electric
Vehicle
In car services,
mobility service
Future societal
mobility
Time
Pers-
pective
14. System perspective is a layered concept
• One person’s system is another person’s
subsystem
• Implication: Systems Engineering can be
applied on different levels:
– System
– Subsystem
– Assembly
– And:
• Supersystem
• Society
– …
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 14
Zooming in
Zooming out
Picture credit: Alberto Sols, USN
15. Separate the What and How much from the How
• “What” and “How much” relate to the
problem domain/the need
• “How” relates to the solution domain
• Instead of a linear flow, there is iteration
and feedback involved
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 15
Functional
Performance/
Quantification
Physical
Picture from: Bonnema, G. M., K. T. Veenvliet and J. F. Broenink
(2016). Systems Design and Engineering: facilitating
multidisciplinary development projects. Boca Raton, FL, CRC
Press.
16. Interfaces:
There are two types of systems engineers…
… Those that look at the interfaces
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 16
… And amateurs
Picture from: Bonnema, G. M., K. T. Veenvliet and J. F. Broenink
(2016). Systems Design and Engineering: facilitating
multidisciplinary development projects. Boca Raton, FL, CRC
Press.
17. Failures often occur at the interfaces
Interfaces are often not high on the attention
list of developers.
• Interfaces between tools:
Airbus 380: could not be built because the
cables were too short
• Interfaces between people and domains
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 17
… and failures of configuration
management and change control.[64][65] The
German and Spanish Airbus facilities
continued to use CATIA version 4, while
British and French sites migrated to
version 5.[66] This caused overall
configuration management problems, at
least in part because wire harnesses
manufactured using aluminium rather than
copper conductors necessitated special
design rules including non-standard
dimensions and bend radii; these were not
easily transferred between versions of the
software.[67]
https://en.wikipedia.org/wiki/Airbus_A380#Pro
duction_and_delivery_delays
18. Those … Interfaces
• Between Organizations…
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 18
Photo: Scania
19. How to avoid Interface problems?
• Address them explicitly
• Make people responsible for the system
coherence
• Draw the system structure
• Look at it from a functional and from a
physical point of view
• Agree on the specifications for the
interfaces
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 19
Function
1
Interface
F1 -> F2
Function
2
Interface
F3 -> F1
Function
3
Function
4
Interface
F4 -> F5
Function
5
Function
6
N2 diagram:
• Helps to address all possible Interfaces
• Outputs on row
• Inputs in colums
• Use to define modules/subsystems
20. Uncertain and Incomplete Information
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 20
• Donald Rumsfield said it all:
“[T]here are known knowns; there are things
we know we know.
We also know there are known unknowns;
that is to say we know there are some
things we do not know.
But there are also unknown unknowns –
there are things we do not know we don't
know.”
—United States Secretary of Defense
Donald Rumsfeld
http://en.wikipedia.org/wiki/There_are_known_knowns
Picture from: Bonnema, G. M., K. T. Veenvliet and J. F. Broenink
(2016). Systems Design and Engineering: facilitating
multidisciplinary development projects. Boca Raton, FL, CRC
Press.
21. Uncertain and Incomplete Information – How to deal with it?
• Systems thinking
• Reason about the system
• Scenario creation => focus on
exceptions/bad weather behavior
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 21
Use the Twelve Thinking Tracks:
1. Dynamic Thinking
2. Feedback Thinking
3. Specific-Generic Thinking
4. Operational Thinking
5. Scales Thinking
6. Scientific Thinking
7. Decomposition-Composition Thinking
8. Hierarchical Thinking
9. Organizational Thinking
10. Life-Cycle Thinking (Product life-cycle,
Resource life-cycle, Project life-cycle)
11. Safety Thinking
12. Risk Thinking
Bonnema, Gerrit Maarten and Broenink, Jan F. (2016) Thinking Tracks for
Multidisciplinary System Design. Systems, 4 (4). p. 36. ISSN 2079-8954
www.tinyurl.com/sde-book
22. 9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 22
System perspective Separate the what and
how-much from the how
Focus on interfaces
(in contrast to focus on
components)
Where are we now w.r.t. the Core of Systems Engineering
Uncertain and incomplete
information versus far-
reaching decisions
Multi-disciplinarity
Communication
23. Multidisciplinarity
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 23
• Mechanical engineers use CAD systems
• Software engineers use UML and class
diagrams
• Electrical engineers use circuit
schematics
• Ergonomists use percentiles and mock-
ups
etc
• But how to make sure we get ONE
system?
Successful
Systems
Mechanical
Engineering
Electrical
Engineering
Software
Engineering
Industrial
Design
Engineering
…
System
Design &
Engineering
An enormous
amount of
information
and data
24. Communication
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 24
Shannon, C. E. and W. Weaver (1949). The Mathematical Theory of Communication. Urbana, IL, University of Illinois Press.
Schramm, W. (1954). The Process and Effects of Mass Communication. Urbana, IL, University of Illinois Press.
Clark, H. H. and S. E. Brennan (1991). Grounding in communication. Perspectives on socially shared cognition. L. B. Resnick, J. M.
Levine and J. S. D. Teasley. Washington DC, American Psychological Association.
25. Back to the Airplane Case – how to move on?
• Investigate the problem domain:
– What is the need for an extra type of
plane in our line-up?
– What is the competition doing?
– What is the market pull?
– What are long-term developments?
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 25
• Investigate the solution domain:
– What new technologies have come up
that might improve our planes?
– What are strengths and weaknesses of
our current products?
– Describe the plane in three dimensions:
• Functional (what does it do)
• Physical (how does it do it)
• Quantification (how much)
26. Thinking pattern of a Systems Engineer/Architect
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 26
Picture credit: Gerrit Muller www.gaudisite.nl Picture from: Bonnema, G. M., K. T. Veenvliet and J. F. Broenink
(2016). Systems Design and Engineering: facilitating
multidisciplinary development projects. Boca Raton, FL, CRC
Press.
27. This all may sound somewhat chaotic
– Some chaos is inevitable
– A moderate level of chaos can be very
inspiring
In essence, SE is about managing this chaos
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 27
• Vee model
– Requirements
– Decomposition – Composition
• Trade-offs
• Various schemes and diagrams
• Model Based Systems Engineering
28. Vee-model
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 28
Shows:
• Requirements definition process
• Decomposition
• Composition (often called Integration)
• Link between these processes
Notes:
1. starting from requirements may result in
a verified result, but not validated.
2. Investigating and defining the problem at
hand constitutes a considerable part of
the SE effort
3. Another considerable part is integration:
putting it back together…
Customer
wish
Validated
system
29. Trade-offs
• In designing systems, answers tend to be
not clear-cut
• Very dissimilar properties have to be
compared
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 29
http://beingperfectlyhonest.blogspot.nl/2010/09/dare-to-not-compare.html
30. Various Useful Schemes and Diagrams
• To enable communication
• Create knowledge by looking at the system
under design from different angles
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 30
Diagram
• N2 diagram
• Functional Block
Diagram
• State Transition
Diagram
• System Budgets
• A3 Architecture
Overviews
Shows
Interfaces
Functions and flow
(material, information,
energy)
Different modes of
operation
Quantification of
performance
Bundles various views
(Functional, Physical,
Quantification)
31. Model Based Systems Engineering (MBSE)
• Transition from document-based to model-
based
• David Long (CEO Vitech corporation):
– “Models are inherent to the way engineers
think, reason, and communicate – and that
includes systems engineers.”
– “Fundamentally, MBSE is about making
system-descriptive and analytical models
explicit, coherent, and consistent. It is a
natural evolution from low-fidelity
representations in documents to higher-
fidelity, richer representations.“
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 31
Thomas Haduch, Director of Systems Engineering, RDECOM,
http://armytechnology.armylive.dodlive.mil/index.php/2015/07/01/15-3/
32. To Conclude
• Systems Engineering is a *very* broad
discipline
• While large portion of the SE Body of
Knowledge relies on common sense,
training *is* necessary
• NISE offers a thorough Master Program in
Systems Engineering
9/7/2017 Systems Engineering in 45 minutes - (c) G.Maarten Bonnema 32
Any comments and/or
questions?
Editor's Notes
Quite a linear process. “Waterfall” process. First complete problem definition, then do the design, then finalize…
Crucial issues: Alberto calls them the relevant few
What can we learn from this: Even if YOU have done your work properly, there might be an undesired, unforeseen effect…
And this is where the systems engineer adds value to your development organization!
RISK THINKING!
Is inherent and crucial part of SE.
Goal: identify risks and keep risks at a manageable level (=/=0)
Lefthand column: possible long-term developments: increased ratio of elderly, increased pressure on sustainability
Righthand column: So we need to organize:
Technology management
Portfolio management
Systems engineering and architecting
The vee-model is often mentioned as describing the SE process.
Comparing apples to oranges (appels met peren vergelijken)
Trade-offs are made using budgets and often with low-order models
SEs try to find the essential performance items (the relevant few) and optimize those within given constraints.