You are a new project manager working on a large project that has completed requ
ID: 3787733 • Letter: Y
Question
You are a new project manager working on a large project that has completed requirements gathering and is in the middle of the design stage of the SDLC. Your understanding is that design reviews are only successful when they are well structured. Develop a design review plan for the design review activity.
Write a 2 to 3 page paper, including at least one reference to support your research. Include the following in your design review plan:
The overall purpose of the design review.
The structure that you will use (e.g., directed meeting, informal meeting, written response in lieu of a meeting, et cetera).
The participants.
Identify the logistics of the meeting: when, where, and how will it take place? Will there be one or more meetings? Will it be conducted formally or informally?
Participant preparation: Should participants prepare ahead of time? If so, what do they need to do?
Create a check-off list of items you will evaluate. List at least six items that you will specifically consider during the design review process. (These can be expressed as statements, or questions to be asked.)
Explanation / Answer
I will provide the key points below, and it can be expanded further by googling.
Having a proper Design is important for a correct software to be developed.
Design Structure can make or break a team performance.
The team structure consists of consists of few directors at the top,
senior designers in the middle and junior designers forming the foundation.
Design directors will always have the question Why ? this is to encourage the desingers
to clearly and effectively articulate their ideas and rationale.
It forces designers to view their solutions from different perspectives and
truly understand the user stories that underpin a successful design.
Senior designers should be well versed in the design being discussed and should defend their work.
Designers become senior when they understand why their designs work.
Their positions are founded in facts, not opinions
Junior Designers are the people who actually prepare the design with numerous discussions with the
Senior designers
Design review meeting:
This meeting is very crucial one as it gives the correct idea about the software being developed.
Any wrong here can screw up the entire product and in some cases the companies itself. Therefore,
this should be s formal meeting with clear agendas in place to discuss each items in depth.
There can be multiple meetings to discuss each module of the product and that's how it is done.
The participants here could vary, as said earlier it can be design directors, Senior designers, Junior designers involved.
Normally Junior designers are also the people who actually code. Having them as part of the meeting will be of great help to them
as they will understand the product as a whole.
Since the time is crucial to everyone, the participants should be well prepared.
They should be ready with any questions being asked in the meeting. They should have done an overall research about the product
being developed,any similar products already in the market, about the technologies being planned to use here and the reason for the same.
Few of the points which is of high priority are -
1. Project Definition - Changes to the project since last review (if any).
2. Concept Approach Changes Since Last Review (if any)
3. Product Design
- Review of design concept for each product
- Assembly drawing/model review
- Product structure walk-through
- Schematic and functional design review (if applicable)
- Component drawing/model review.
4. Product Testing and Verification
- Test requirements and plan
- Test results
5. Quality Planning - Quality issues on similar components and counter-measures taken.
6. Product Cost and Profitability
7. Review of Issues and Follow-up Actions
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.