Describe design walk throughs and critical design review, Software Engineering

Q. Describe design walk throughs and critical design review.

Ans. A design walkthrough is a excellence practice that allows designers to acquire an early validation of design decisions related to the development and treatment of content and design of the graphical user interface as well as the elements of product functionality. Design walkthroughs offer designers with a way to identify and assess early on whether the proposed design meets the requirements as well as addresses the project's goal.

For a design walkthrough to be effective it requires to include specific components. The subsequent guidelines highlight these key components. Use these guidelines to conduct, plan and participate in design walkthroughs and increase their effectiveness.

1. Plan for a Design Walkthrough

2. Get the Right Participants

3. Understand Key Roles as well as Responsibilities

4. Prepare for a Design Walkthrough

5. Utilize a Well-Structured Process

6. Review as well as Critique the Product not the Designer

7. Review don't Solve Problems

The purpose of critical design review is to make sure that the detailed design satisfies the specifications laid down during system design. The critical design review process is similar as the inspection process in which a group of people gets together to discuss the design with the aim of revealing design errors or undesirable properties.

Posted Date: 7/26/2013 3:46:03 AM | Location : United States







Related Discussions:- Describe design walk throughs and critical design review, Assignment Help, Ask Question on Describe design walk throughs and critical design review, Get Answer, Expert's Help, Describe design walk throughs and critical design review Discussions

Write discussion on Describe design walk throughs and critical design review
Your posts are moderated
Related Questions
What is Up time? "Up time" is the time period when a method is operational and in service. Up time is the sum of idle time and busy time.

Which type of software must not be automated? Following types of software must not be automated: - Incomplete/Unstable software since they are still undergoing changes -

What is software engineering? Software engineering is a regulation in which theories, methods and tools are applied to make professional software.

Q. Differentiate between structured analysis and structured design? Ans. The aim of structured examination is to transform the textual description of a problem into a graphic

Consider a program for the purpose of the nature of roots of a quadratic equation. Its input is the triple of positive integers say a, b, c as well as values in the interval [0,100

FAN IN is simply a count of the number of other Components that can call, or pass control, to Component A.

what is COCOMO model and where it is used also say about COCOMO model when in use then how it act and its characteristtics details

Explain about the software testing strategies. A method approach to software testing. Verification and Validation. Verification refers to the set of activities that ma

What are the benefits of evolutionary prototyping? i. Fast delivery of the working system. ii. User is included while developing the system. iii. More useful system can b

When is RTM (Requirement traceability matrix) prepared - after or before test case designing? - RTM is prepared before test case designing. - Requirements must be traceable