Modularity and Black-Boxing
From apppm
(Difference between revisions)
Line 10: | Line 10: | ||
− | + | =Introduction= | |
+ | =Modularity in different fields= | ||
+ | ==Modularity in product architecture== | ||
+ | ==Modularity in portfolio management== | ||
+ | ==Modularity in Project management== | ||
+ | =Techniques= | ||
+ | ==Blackboxing== | ||
+ | ==Modular Function deployment== | ||
+ | =References= | ||
+ | |||
Revision as of 11:24, 21 September 2015
Abstract
This article is part from the course 42433 – Advanced Engineering Project, Program and Portfolio Management E15 at DTU. This is an individual assignment and the reason why this topic has been selected is because of the personal interest of the author on it. To allow success in a company, project or program it is important to learn how to transform complex systems (meaning processes, concepts, architectures, etc.), in small boxes that can be easily handled. The structure of this article is defined by the following sections:
- Modularity in different areas: Within the field of engineering modularity can be used in many different areas, this article will focus on three main areas of interest: product architecture, portfolio management and project management, and how they build each other.
- Techniques: Here it will be addressed how to take to due modularity and two techniques will be described (black-boxing and MFD)
- Limitations: This final section will discuss the limitations of this concept applied to the areas described in the article
Contents |
Introduction
Modularity in different fields
Modularity in product architecture
Modularity in portfolio management
Modularity in Project management
Techniques
Blackboxing
Modular Function deployment
References
Module Drivers
Module Function Development
Referencess
Oehmen, J. et al 2015
Developing productc families based on architecture, Ulf Harlou