• Seilevel Team

    Here’s the Team

    Welcome to our Seilevel Photo Op.

Author mmurphy

The Business Use Case

Use cases are an indispensible tool for capturing the behavioral requirements of a software product and many analysts employ them exclusively for that purpose. But use cases can also help describe the interaction between external entities and a business. And, there are some very good reasons to develop the business …

Read More

Three simple but powerful techniques for modeling Data

We often spend the majority of our modeling time on use cases, process flow diagrams, and other tools that model behavior. These behavior models are great tools for driving out functional requirements but they don’t explicitly address all of the data objects, attributes, and relationships associated with the behavior. For …

Read More

Is your software a project or a product?

One of the most common mistakes made by software development teams and others in thinking about software is the confusion between the concept of software as a project and the concept of software as a product. When asked, most people would agree that software is a product, not a project. …

Read More

Positive Random Reinforcement

As requirements consultants we sometimes find ourselves working with people who have learned through painful experience that requirements are not fun. We like to think the process we use is actually pretty interesting and engaging but it is not uncommon for us to start a new project and find people …

Read More

Three keys to success in Agile Modeling

For Agile development teams, there are three key modeling concepts that are critical for successful requirements modeling. First, create model artifacts “just in time” and make them “just good enough”. Creating model artifacts just in time means not trying to produce detailed models too far in advance of when they …

Read More

Agile Requirements – The use case narrative

Last month I wrote about Agile Requirements and a concept called GRIT or Great Requirements in Total. The idea behind GRIT is that it is important to deliver great requirements models along with great working software. GRIT recognizes that software is a product, not a project, and should be managed …

Read More

Structure in requirements writing

One of the quickest ways to improve your requirements documentation is to have someone else review your work and provide feedback. Of course, the flip side of asking someone to review your work is offering to review their work in return. And, entire project teams can dramatically raise the quality …

Read More

The use and misuse of includes and extends

Any sizeable collection of use cases will have relationships between use cases that can be modeled using the UML includes and extends stereotypes. Used properly these model constructs help make the model more readable and maintainable. Used improperly they can make the model incomprehensible and this happens all too often. …

Read More

Agile Requirements – no BRUF just GRIT

The first principal of agile software development is that the highest priority is to satisfy the customer through early and continuous delivery of valuable software. This is a significant departure from traditional waterfall methods in which delivery of working software happens not early, but very late in the process. In …

Read More