Design review
In-game article clicks load inline without leaving the challenge.
A design review is a milestone within a product development process whereby a design is evaluated against its requirements in order to verify the outcomes of previous activities and identify issues before committing to—and, if need be, to re-prioritise—further work. The ultimate design review, if successful, therefore triggers the product launch or product release.
The conduct of design reviews is compulsory as part of design controls, when developing products in certain regulated contexts such as medical devices.
By definition, a review must include persons who are external to the design team.
Contents of a design review
In order to evaluate a design against its requirements, a number of means may be considered, such as:
- Physical tests.
- Engineering simulations.
- Examinations (Walk-through).
Timing of design reviews
Most formalised systems engineering processes recognise that the cost of correcting a fault increases as it progresses through the development process. Additional effort spent in the early stages of development to discover and correct errors is therefore likely to be worthwhile. Design reviews are example of such an effort. Therefore, a number of design reviews may be carried out, for example to evaluate the design against different sets of criteria (consistency, usability, ease of localisation, environmental) or during various stages of the design process.
See also
Navbox |name = Systems engineering |title = Systems engineering |state = state |bodyclass = hlist
|group1 = Subfields |list1 =
- Aerospace engineering
- Biological systems engineering
- Cognitive systems engineering
- Configuration management
- Earth systems engineering and management
- Electrical engineering
- Enterprise systems engineering
- Health systems engineering
- Performance engineering
- Reliability engineering
- Safety engineering
- Stanford torus|Sociocultural Systems Engineering
|group2 = Processes |list2 =
- Requirements engineering
- Functional Analysis and Allocation
- System integration
- Verification and validation
- Design review
- System of systems engineering
|group3 = Concepts |list3 =
- Business process
- Fault tolerance
- System
- System lifecycle
- V-model
- Systems development life cycle
|group4 = Tools |list4 =
- Decision-making
- Function modelling
- IDEF
- Mathematical optimization
- Quality function deployment
- Spare part
- System dynamics
- Systems Modeling English Language
- Systems analysis
- Systems modeling
- Work breakdown structure
|group5 = People |list5 =
- James S. Albus
- Ruzena Bajcsy
- Benjamin S. Blanchard
- Wernher von Braun
- Kathleen Carley
- Harold Chestnut
- Wolt Fabrycky
- Barbara Grosz
- Arthur David Hall III
- Derek Hitchins
- Robert E. Machol
- Radhika Nagpal
- Simon Ramo
- Joseph Francis Shea
- Katia Sycara
- Manuela M. Veloso
- John N. Warfield
|group7 = Related field |list7 =
- Security engineering
- Computer engineering
- Industrial engineering
- Operations research
- Project management
- Quality management
- Risk management
- Software engineering
|below =
- Category:Systems engineering
}}<include>
Parameters
This template's initial visibility currently defaults to autocollapse, meaning that if there is another collapsible item on the page (a navbox, sidebar, or table with the collapsible attribute), it is hidden apart from its title bar; if not, it is fully visible.
To change this template's initial visibility, the |state= parameter may be used:
{{Design review|state=collapsed}}will show the template collapsed, i.e. hidden apart from its title bar.{{Design review|state=expanded}}will show the template expanded, i.e. fully visible.
See also
- tl
</include>