Welcome to our Seilevel Photo Op.
Posts about documenting requirements and different document types
The Business Data Diagram is a powerful, high-level RML model that can help bound the scope of data for your project. It can also be used to visually convey a sophisticated strategy for bounding your requirements objects and their traceability. I was recently working on a project where we had …
In the world of software development, especially the Agile part of it, it is easy to live in the now and the current development effort. The Agile Manifesto values “Working software over comprehensive documentation.” Some people interpret this to mean that they do not need to worry about documentation as …
We all have our reasons for using a piece of software. Maybe it makes staying in touch easier, maybe it helps organize, or for that matter, make us money, maybe it’s just fun to interact with…whatever those reasons may be, the drive to get things done is not, and cannot …
A large part of working on software projects at Fortune 1000 companies is the documentation mountain that can sometimes arise. This can be a necessity in order to provide information for future support staff and accountability, or it can be a time intensive and largely senseless endeavor. Often times, as …
There are several ways that we document our requirements, and one of them is by using Microsoft Word to create a document complete with requirements, explanations, approvers, pictures of our models, and other important information. Since there are usually many people making changes to the document, we often use Track …
Have you ever clicked the submit button on a project and immediately afterward noticed a glaring, stomach-dropping, panic-inducing typo in your work? The consequences of delivering sloppy work can be dire, especially in the world of requirements where attention to detail is so important! If your stakeholders find errors, the …
At Seilevel, on our Agile projects we have introduced a project artifact called the Agile Requirements Document or ARD that we create during the planning phase of a project. We have done this on several projects and have had good success with it. An ARD is conceptually similar in some …
I’ve been working on a program that has certain been a challenge, both from the subject matter, the extremely short timeframes given (imposed governmental regulations that must be met), to the stakeholders (who have day jobs to perform as well). Everyone is under pressure, which can make for some short …
I still remember my first project at Seilevel, more than 9 years ago. I struggled with the information flood and came out of that project with at least one clear goal: to get better at acquiring new information. In October, I started on a new project with a new client …
This blog post was written with Karl Wiegers based on our Software Requirements, 3rd Edition book. No matter how thorough a job you do on requirements elicitation, there is no way to be certain that you have found them all. No little green light comes on to announce “You’re done!” You …
