I really like The Business Data Diagram (BDD), described in RML™ Requirements Model 6 – The Business Data Diagram (BDD), because it gives me a big-picture understanding of the data […]
Tag: requirement models
A Panegyric on the Number Seven (plus or minus two) for Software Requirements
“…what about the magical number seven? What about the seven wonders of the world, the seven seas, the seven deadly sins, the seven daughters of Atlas in the Pleiades, the […]
Business Analysts: Org Charts Does a Project Good!
I know that we have written a lot regarding the value of an organization chart. It’s one of those models that we use where everyone tends to nod their head […]
Fear of the Unknown for Business Analysts
I’ve been working on a project recently, where we introduced one of our models as a planned deliverable. For the first phase of the project, this model worked fairly well, […]
Acceptance Testing: Cross-tracing to Avoid Crossed Fingers
It is the end of your project and your tests are passing. Are you ready to confidently release your project? Or, are you secretly crossing your fingers like a young […]
Behind the scences at our video shoot: Requirements Visualization Training- A guide to RML
This week was our first video shoot in our video training series, Requirements Visualization Training- A guide to RML. This is a training series that we have presented to clients […]
The Importance of the Org Chart Model
When we train people in the use of different requirements models, we typically mention three models as being distinct by virtue of the fact that you can know they are complete: […]
How to Shoot Yourself in the Foot: Conclusion
Conclusion to the series, “How to Shoot Yourself in the Foot: 7 ways to do software requirements poorly to set your project up for failure and what to do instead.” […]
RML Model: Business Data Instance Diagram
As many of you who are familiar with RML know, the models are organized into 3 categories: people, systems and data. People models are models that relate to who is using the […]
Don’t do Requirements Traceability
Number 7 in the series, “How to Shoot Yourself in the Foot: 7 ways to do software requirements poorly to set your project up for failure and what to do […]
Another Reason to Create an Org Chart: Navigating Project Politics
My fellow ArgonDigital bloggers have written about the many virtues of Org Charts and their relationship to requirements elicitation and management. In case you missed it, here is a good […]
Tips for modeling large system migrations
It seems like many of the projects that we are implementing these days are large system migrations. Typically they are 20 year old mainframe systems that are being converted into […]