Business Objectives

Front-End Engineering Design for Software Development

In my last blog post, I discussed how including larger factors of safety in our requirements estimation and design might help give business analysts the breathing room they need when unexpected scope/features pop up in a project. Another interesting aspect of engineering design that could be incorporated in some way …

Read More

Requirements Deliverables: Target Your Audience

At Seilevel, we consistently tout the invaluable benefit of using models in your requirements process.  In many cases, models are more than enough to communicate the intended functionality to all stakeholders.  This is especially true if you have been using models in your process for some time and stakeholders know …

Read More

Telling a Story Through Your Requirements, Part II

In my previous post, I talked about how business analysts and product managers who are putting together requirements documentation can and should think of themselves as storytellers. By thinking of a Business Requirements Document (BRD) or a System Requirements Specification (SRS) as a narrative, with a beginning, middle and end, …

Read More

Tell a Story Through Your Requirements, Part I

Most of the projects that we work on here at Seilevel involve producing some sort of coherent documentation to describe what a given piece of software needs to be able to do and how it will work. Of course, software requirements are a crucial part of this documentation, but by …

Read More

In Action – the Business Objective Model

I was working with one of our newer clients today, talking with one of their newest developers. He had never heard of Seilevel before, but had seen a number of artifacts that some of his peers had created with our templates. His peers have taken our classes, and are trying …

Read More