Robert Rose-Coutré

Many companies use knowledge management (KM) but miss one of the key KM ingredients: employee/knowledge-into-workflow. Most companies send staff to training or cross train to give the person in the workflow the knowledge they need to do the job. The most interesting twist in true Knowledge Management is finding creative ways of looping employees who already have the knowledge into the workflow. That often-missing part of KM is the topic of this article.

Sometimes the user, project sponsor, and other key stakeholders haven't provided in the requirements documentation all the expectations of the software you're building. Instead, these expectations are only implied. In a perfect requirements-gathering process, there would be no such thing as an "implied requirement" because every requirement would be captured in the document. But no process is perfect, in theory or in practice. This article should help you look for and recognize the presence of implied requirements and learn how to capture them and convert them to documented requirements.

"Our Take" is a regular column from the editors at Software Quality Engineering. It appears in the twice-monthly StickyLetter since its inception in September 2000 (originally "STQe-Letter"). From jazz music, to car troubles, to the Lewis and Clark expedition, Robert Rose-Coutré, former StickyMinds.com Editor, will use anything to make a point about building better software. The editors at Software Quality Engineering have compiled a collection of some of these pieces. Musings from StickyLetter's "Our Take" are presented here.