News Jan 20, 2020 4 mins 2105 Views 0 Comments 0 Likes What do you do when you're tasked with modifying a larger existing platform or when there is no time for a top-down or buttom-up design approach? The answer may just be Middle-Out Design also known as Inside-Out Design. "Most engineers and managers in the real world follow a middle-out or inside-out approach. As the name implies, the “middle-out" systems engineering method consists of concurrent bottom-up and top-down systems engineering activities. The bottom-up tasks are built on a detailed knowledge of component parts and subsystems. The concurrent top-down activities will preserve the customer-focused, requirements-driven emphasis that keeps the system development in a functional domain." John Blyler This approach to systems engineering is by no means new. It has been employed by project managers for many years and it is thought to have origiinated within the Model-Based Systems Engineering (MBSE) community by Dr. Steven H. Dam. "Models can be used in both the top-down, multiple domain architectural and requirements design as well as the bottom-up simulation and prototyping of preliminary system, subsystems and component evaluation and verification. Together, these models provide a platform that combines high-level system models with specific component and subsystem oriented executable models." Continue reading at Design News Login or Register to download Related Content New ways of working can actually accelerate your team’s productivity What are Product Requirements? Requirements Glossary from A to Z Did you like this article? 0 Upvote Requirements Analysis Systems Engineering 2020-01-20 Requirements.com All about Requirements 2020-01-20 Requirements.com Staff Middle-Out or Inside-Out Systems Engineering Comments / Discussions Please login or register to post comments.