237
Integration in Systems Engineering Context
searching for financing, the conceptualizer’s risk increases for not
being able to realize a return on investment. However, failing to
attract needed capital may or may not increase the risk of success.
Conceptualization is often presented as a case that justifies the
product (e.g., business case, business plan, or proposal).
• Financing: The second stage focuses on financing—determining
which financing source has sufficient interest, capital, and expertise
to consider and possibly fund the effort to accept or amend the pro
posed solution to satisfy market demands. Financing is secured to
reduce the risk of not having sufficient resources to complete and
sell the product. Outside money is exchanged for a say in decisions
and a part of the results of all activities (make equivalent to other
areas, including process decomposition to first level).
If financed, the project begins work to prepare a design that captures the
preliminary set of top-level (most general) requirements. These require
ments derive from the various stakeholders and represent their cardinal
interests and is responsive to the various delineations that bound the
solution(s) as well as the conditions under which the boundaries impact on
the design. Additionally, a CONSOLS (describe how it reduces risk) and a
CONOPS (describe how it mitigates risk) are prepared that relate the design,
the operational environment, and the key performance parameters that
d istinguish the solution from other existing and proposed solutions.
Preliminary design reduces the risk of failure by (1) providing confidence to
the developers and financiers; (2) showing transparency in the work and the
design, so that “independent” analysis and evaluation can be accomplished
before additional money is spent; (3) uncovering areas of work that necessitate
further study; and (4) addressing specific issues that were identified earlier
as items of risk.
• Preliminary design: The third stage transforms the revised CONSOLS
and CONOPS into requirements at appropriate levels of detail to
produce a design that can be evaluated for risk, utility, and market
acceptance (or mission dominance). Planning is performed.
• Detailed design and architecting: The fourth stage completes the design
by inductive reasoning, innovation, creativity, reductionist logic,
modeling and simulation, and prototyping. Alternative architec
tures are formulated. The detailed design and architecting follows
from the preliminary designs to provide additional detail, derive
requirements from the stated requirements, and further specify
tasks and their outcomes. Sometimes protoproducts or protoser
vices are developed to verify the stakeholder requirements and
needs are met (but as important, to validate that the team can in fact
build a model of something that represents a key function that is
Integration in Systems Engineering Context
searching for financing, the conceptualizer’s risk increases for not
being able to realize a return on investment. However, failing to
attract needed capital may or may not increase the risk of success.
Conceptualization is often presented as a case that justifies the
product (e.g., business case, business plan, or proposal).
• Financing: The second stage focuses on financing—determining
which financing source has sufficient interest, capital, and expertise
to consider and possibly fund the effort to accept or amend the pro
posed solution to satisfy market demands. Financing is secured to
reduce the risk of not having sufficient resources to complete and
sell the product. Outside money is exchanged for a say in decisions
and a part of the results of all activities (make equivalent to other
areas, including process decomposition to first level).
If financed, the project begins work to prepare a design that captures the
preliminary set of top-level (most general) requirements. These require
ments derive from the various stakeholders and represent their cardinal
interests and is responsive to the various delineations that bound the
solution(s) as well as the conditions under which the boundaries impact on
the design. Additionally, a CONSOLS (describe how it reduces risk) and a
CONOPS (describe how it mitigates risk) are prepared that relate the design,
the operational environment, and the key performance parameters that
d istinguish the solution from other existing and proposed solutions.
Preliminary design reduces the risk of failure by (1) providing confidence to
the developers and financiers; (2) showing transparency in the work and the
design, so that “independent” analysis and evaluation can be accomplished
before additional money is spent; (3) uncovering areas of work that necessitate
further study; and (4) addressing specific issues that were identified earlier
as items of risk.
• Preliminary design: The third stage transforms the revised CONSOLS
and CONOPS into requirements at appropriate levels of detail to
produce a design that can be evaluated for risk, utility, and market
acceptance (or mission dominance). Planning is performed.
• Detailed design and architecting: The fourth stage completes the design
by inductive reasoning, innovation, creativity, reductionist logic,
modeling and simulation, and prototyping. Alternative architec
tures are formulated. The detailed design and architecting follows
from the preliminary designs to provide additional detail, derive
requirements from the stated requirements, and further specify
tasks and their outcomes. Sometimes protoproducts or protoser
vices are developed to verify the stakeholder requirements and
needs are met (but as important, to validate that the team can in fact
build a model of something that represents a key function that is