Author Marc Talbot

Borland SDK from .NET

I spent some time this month working on a requirements modeling application based on a connection to the Borland CaliberRM database using the Caliber SDK. This was a lot of fun, since I don’t usually get a chance to write a lot of code, and I wanted to share some …

Read More

Are your requirements smarter than a 5th grader?

There was a neat article in the July 13 Dr Dobbs Agile Modeling Newsletter. http://www.ddj.com/dept/architect/201001273 It basically argued that you could evaluate the quality of a document based on a set of criteria: C = The percentage of the document that is currently “correct”.R = Thechance that the document will …

Read More

Design is a poor substitute for nonfunctional requirements

I’ve traditionally been somewhat neutral on what amount of design gets slipped into a requirements document. I’m a consultant, and to a certain extent, I’m willing to accept that the things that are important to a customer ARE the requirements, whether they are true “business requirements” or a design that …

Read More

Templates for Requirements Documents

Most organizations have come to a realization that they need to apply more process to their requirements gathering efforts. One of the common first steps in support of this is to develop common templates to be used for each document. The templates contain subheadings that are associated with many common …

Read More

Views of Requirements

There is an architectural pattern in software engineering known as Model-View-Controller. This pattern suggests (among other things) the separation of data (Model) from the display of that data (View). The reason for this distinction is that there may be many different ways to display data in a way that is …

Read More

Requirements for the Easter Bunny

When I was a teenager, I cut grass for the Tooth Fairy. Quite frankly, she was unpleasant to work for, and she was very slow to pay. I resolved to never work for anthropomorphic representations of mythological creatures again. To my dismay, I found myself rolling off a project a …

Read More

Policy as an influence on requirements

One source of requirements for a software system is business rules. Business rules are usually defined as rules and constraints that affect how a company achieves its goals. These rules are typically independent of the software system being designed or deployed. But what about the collection of rules and constraints …

Read More

Getting by without requirements

I travel a lot for work. Travel, despite the implications of movement, actually involves a lot of waiting around, either in lines or in airline lounges. Waiting around with a bunch of business travellers often leads to some interesting conversations. I spend a lot of time talking about software requirements …

Read More

Why won’t they help themselves?

It’s a requirements analyst’s worst nightmare. You’ve been assigned to capture requirements for an insanely complex system. Your customer is suffering with their existing system. You’re excited, because you know you’re going to make a big difference in the next generation of the customer’s software.And then you hit the wall: …

Read More

Requirements Gathering without Software Development

There’s been a lot written about software requirements gathering as a component of the software development life cycle. Proper requirements are critical to being able to build the right piece of software for the right cost on the right schedule. But what about software that you are going to buy? …

Read More