EXTRA

Question 1

Name benefits of a highly modular architecture

Answer 1

A highly modular design opens up the following benefits:
Each module can be designed by a separate team that becomes entirely responsible for a particular function.
Modifications of individual modules can be independent of each other.
If a particular function fails it is often clear which module needs redesign.
Product ranges typically cost less because of possible use of common components.
A modular design enables better product variety, enabling variations in size, performance, etc.

Question 2

Name advantages and disadvantages of a highly integral architecture

Answer 2

A highly integrated design provides more opportunities to optimise size, mass, material usage however it also the following disadvantages:
 Assigning modules to different teams is difficult because of inherent interdependencies in the integral design.
 Changing one module is likely to require a review and quite possibly a redesign of other modules.
 Similarly, modules that fail to perform their function will necessitate the review, and possibly the redesign, of other modules.
 There is an increased cost in maintaining product ranges as many components are unique.

Question 3

Describe 7 elements of good risk management practice:

Answer 3

Shortened:

1. Identify and prioritise high risk areas
2. Define project requirements while considering risks
3. Pilot the product/service to give evidence of safety/performance
4. Define system performance metrics + associated risk monitoring methods
5. Reference to rework model (maximise quality, minimise rework discovery time)
6. Use V+V led approach/compare against existing solutions
7. Good communication with stakeholders

Risk management refers to the entire process of identifying hazards, analysing risks and controlling them. A number of strategies were raised during the lectures, including:
1. Reference to risk management as a means to drive the design process by identifying areas of high risk (show stoppers) which should be investigated in preference to low risk areas;
2. The careful definition of the project requirements, with reference to active risk assessment to identify potential hazards, evaluate risks, and to define risk reduction priorities;
3. Application of a formal approach to risk control during the development of the project, and across all three technology stages;
4. Clear definition of the system performance metrics and associated risk monitoring methods;
5. Reference to the rework model and the resulting need to maximise design quality and reduce delays in the discovery of rework.
6. Use of the waterfall model as an example of a verification/validation led approach. Importance of validation of requirements as a precursor to design and the timely use of verification to identify problems early;
7. Good communication and involvement of the stakeholders in the design and implementation.
Page

Question 4

Name some main headings for the requirements specification of a product?

Answer 4

Geometry
Materials 
Safety 
Ergonomics 
Operation 
Environmental impact
Maintenance
Cost