Software Engineering

2. 
Functional analysis attempts to resolve complex tasks by decomposing each 
task until a set of simpler, less complex functions are perceived.
3. 
The comprehension achieved by applying the functional analysis methodology 
incites a natural need to iterate upward to reconsider the problem bolstered with 
a new appreciation of the problem and solution space.
4. 
The physical architecture is derived via design synthesis that strives to combine 
software elements into a new, larger, more complex software element that con-
tributes effectively and efficiently to the overall design solution.
5. 
The default methodology for applying design synthesis is to begin with the 
smallest parts and to progress toward a design solution by assembling and inte-
grating structural units and components into larger, more complex structural 
components. However, engineering analysis involves identifying the design 
challenges that entail the most risks and to seek a design resolution that involves 
less risk. Then, the remainder of the design can be worked out utilizing the less 
risky design solution as its centerpiece.
6. 
The desire to generate a suitable and competent design solution defies a strict 
top-down functional and bottom-up design synthesis practice. Design efficiency 
and effectiveness supersede the adherence to any design approach that dictates a 
strict architectural design stratagem.
7. 
Software engineering blends the top-down analytical and bottom-up synthesis 
techniques with an understanding that the structural design must evolve in an 
abstract top-down manner. However, the abstract structural design is only rep-
resentational until it is refined by the thorough application of the bottom-up 
design synthesis practice.
Software products are not bound by any scientific, technological, engineering, or 
mathematical principles that provide design reference models for other products. The 
vast majorities of products in the market today are based on existing products with 
only minor innovative variations. The architectural design of many software prod-
ucts does not have a conventional legacy from which to initiate their design. Software 
reference architectures may be established with a domain or software product line. 
However, stakeholder requirements and advancements in computer technology often 
render these reference architectures ineffective and inefficient. Therefore, most soft-
ware products begin the design effort with a clean slate from which to being deriving 

---