- Make sure that the team is ready.
- Record preparation time and issues ready to be raised.
- Take notes.
- Summarize the work done page by page.
- Record assumptions, questions and dissent.
- Record minority views.
- Record quality issues and their conflict with standards.
- Take care over sudden agreement over correctness.
- Summarize total effort.
- Make sure that the team does not get bogged down in discussions or correction activities.
- Focus on internal and external interfaces.
- Make sure to review the final product instead of the person.
This site provide software developers on the Software Development Life Cycle.
Showing posts with label Design Phase. Show all posts
Showing posts with label Design Phase. Show all posts
Monday, January 7, 2008
Structured Walkthough Tips
When conducting Structured Walkthough, I have the following tips:
Saturday, January 5, 2008
Conducting Structure Walkthrough in SDLC
Structure Walkthrough can be conducted:
- at any point in time during SDLC.
- to review users requirements in the feasibility study stage or the external design stage, system design during the internal design stage or source coding duirng the development stage.
What is Structured Walkthrough
Structured Walkthrough is:
- a tool for analysing the design of a system to ensure it addresses all requirements.
- a mean of ensuring conformity to standard.
- a mean to make reviewees more conscious of the way the product looks.
- used as a learning experience for the team.
Prototyping in SDLC
A prototype is:
- a demonstration system.
- a partially or fully working system waiting for idea testing and modification to meet requirements.
- an intermediate state that exhibits the essential features of a later generation.
- technique for clarifying user requirements (especially on user interface).
- can also verify the feasibility of a design.
Subscribe to:
Posts (Atom)