Thursday, September 27, 2018

Prototypes Reduce Risk In Selecting User Interfaces

›
To reach an agreement on a user interface prior to full-scale development, a prototype is your best choice for a low-risk, high-payoff ap...
Wednesday, September 26, 2018

Determine The Requirements Now

›
Requirements are hard to understand and harder to specify. The wrong solution to this problem is to do a slipshod job of requirements sp...
Tuesday, September 25, 2018

Determine The Problem Before Writing Requirements

›
When faced with what they believe is a problem, many engineers rush into offering solutions. I am guilty of this myself - finding soluti...
Monday, September 24, 2018

Poor Requirements Yield Poor Cost Estimates

›
Poor cost estimation can be traced back to these top five causes that all relate to the requirements process: Frequent requirements ch...

Take Responsibility

›
In all the [licensed] engineering disciples, when a design fails, the engineers are blamed. Thus, when a bridge collapses, we ask, ...
Thursday, September 20, 2018

Research-Then-Transfer Doesn't Work

›
The achievements of software engineering research laboratories have difficulties making it into practice. Some reasons would be: Softw...
Wednesday, September 19, 2018

Use The Same Name For The Same Concept

›
Technical documentation must always use the same words to refer to the same concept and the same sentence structure for similar messages...
Tuesday, September 18, 2018

Every Software Document Needs An Index

›
An index is a list of all terms and concepts used in the document, together with one or more page numbers where the term or concept is de...

Every Document Needs A Glossary

›
It is a frustrating experience to read a document and come across a term that is not familiar. The frustration is short-lived; however, ...
Monday, September 17, 2018

Use Documentation Standards

›
If your project requires that a documentation standard be followed, then, of course, follow it. However, never blame a standard for doing...