JS Tip 572: Designing the Project
Design is identifying how our project will work for those who use it.
Design has two sub-discussions:
What elements—areas, components—are involved?
Three:
The people: Who will be affected by and who will use our project? The two are not the same.
The processes: What steps will the people who use the project have to take for it to work correctly? No surprises. No dead ends. No “Oops. 404: Page not found.”
The tools: What resources or equipment will they need? Make a list. Make sure those using the project have—or can get—the necessary tools.
Recognizing each of these elements, how do we put the project together?
Three (again):
Document the design. Identify each step of running (operating) the finished project. (Think of this as writing an instruction manual.) One of the best tools we’ve found is using sticky notes on a white board. Write each step. Put them in order. Identify branches. Move notes around.
Test the design. Go practical. Go hands-on. Try it out yourself. Make sure it works. Be rigorous. (The tougher your testing, the more certain your success.)
Train the design. Make sure those who will use the project can use the project. Make sure they know what to do. (“We’ll start here. See this switch? Turn it to ‘On.’ [Click] See all the lights? That’s good.”) Teach them.
That’s design.
Next week: Develop. Crunch time.
Let us know your questions. We love this stuff. Hey. Stay safe. Stay well.