I am happy to announce that my Master's thesis has been accepted and is available for all. While there is an official abstract within the thesis, in summary I was trying to find a way to help design engineers focus system modularization efforts. The goal would be to only create modules in areas of systems that are likely to need to change to be value robust. Further, I wanted to provide a way to check and make sure that the target system modularization had actually been achieved.
Feedback or thoughts on follow-up research are always welcome.
Monday, June 4, 2012
Monday, February 13, 2012
Prototypes, ambiguity, and tradespace exploration
I ran across an HBR story about how single prototypes that happen early in the system or product development cycle can project outcomes. This is reported to happen because the team becomes focused on the single prototype instead of remaining in the problem space for a longer period of time.
Tradespace exploration, and in particular tradespace exploration rooted in what is valuable to the acquirer or customer, could be one counter measure to this team dynamic. By exploring hundreds or thousands of designs parametrically is one way to avoid settling on optimizing one solution too early in the development process. Further, by mapping to stakeholder utility it keeps the development team focused in the customers problem domain.
May particular research in this area is two fold:
1. Use of multi-attribute tradespace exploration for systems solutions in the competitive commercial space with many sellers competing for many consumers (the current research has been primarily in the context of a monopsony, such as the U.S. Department of Defense or NASA).
2. The use of tradespace exploration to as a value centric approach to target system modularization efforts.
As I get articles out on each of these areas I'll provide additional pointers.
Tradespace exploration, and in particular tradespace exploration rooted in what is valuable to the acquirer or customer, could be one counter measure to this team dynamic. By exploring hundreds or thousands of designs parametrically is one way to avoid settling on optimizing one solution too early in the development process. Further, by mapping to stakeholder utility it keeps the development team focused in the customers problem domain.
May particular research in this area is two fold:
1. Use of multi-attribute tradespace exploration for systems solutions in the competitive commercial space with many sellers competing for many consumers (the current research has been primarily in the context of a monopsony, such as the U.S. Department of Defense or NASA).
2. The use of tradespace exploration to as a value centric approach to target system modularization efforts.
As I get articles out on each of these areas I'll provide additional pointers.
Subscribe to:
Posts (Atom)