Tag: ROM

Business Objectives in Requirements Engineering

Business Objectives in Requirements Engineering ArgonDigital - enterprise automation experts

I have recently started working on a new project, and we recently held our kick off meeting for the effort.  One of the standard items to review is the project summary, which is usually a couple of short statements on what the project is all about. Since I was aware that most of the subject […]

Five New Year’s Resolutions for Requirements

Five New Year’s Resolutions for Requirements ArgonDigital - enterprise automation experts

It’s that time of year, where our thoughts turn to the holidays…the holiday parties, the shopping, the lights, visiting with family!  For many organizations, the end of the year tends to be quiet on the IT front, for no organization wants to risk introducing problems into their production environment at year end. So as I […]

Thanks to everyone who attended BA Vancouver

Thanks to everyone who attended BA Vancouver ArgonDigital - enterprise automation experts

Thanks to everyone who attended our presentation on business objectives at PS& BA World in Vancouver. For those of you who missed the handout.  Here it is, ArgonDigital’s ROM Defined Guide. For those of you who missed out on our lanyards with handy models, requirements gathering and use case cheat sheets– catch us at Casino […]

Live from RE’10: Keynote on Missing the Goals in Requirements

Live from RE’10: Keynote on Missing the Goals in Requirements ArgonDigital - enterprise automation experts

Al Davis spoke as a keynote at RE’10 (www.re10.org) titled “Requirements: A Textbook Example of Goals Displacement”. He started by giving us a definition of Goals Displacement: the process by which the means used to achieve a goal become more important than the goal itself. What I love about Al’s talks is that he is […]

Building Trust with Users – Be An Advocate

Building Trust with Users – Be An Advocate ArgonDigital - enterprise automation experts

One of the key Roles that a Requirements Analyst plays is defining and managing the scope of a project.  Of all the tasks we perform, this is one that is fraught with all manner of complications and one that is most often mismanaged.  The ArgonDigital ROM Framework provides excellent tools and methodology for ensuring that […]

When is IT the business stakeholder?

When is IT the business stakeholder? ArgonDigital - enterprise automation experts

We use a well established model for looking at the relationship between business requirements and the software requirements that are derived from them. Using the Requirements Object Model (ROM), we typically examine the business problem, the business objective, and the business strategy. We use these to derive a product concept and from there a set […]

BRD vs. Functional Requirements

BRD vs. Functional Requirements ArgonDigital - enterprise automation experts

Business requirements vs Functional requirements We often get the question asking “what is the difference between business requirements and functional requirements?” In prior posts I have discussed that these distinctions are actually artificial and are artifacts of an organization structure that requires people in “the business” to produce a “business requirements document (BRD)” vs. some […]

Live from RESFQ: The Requirements Object Model (ROM), part 3

Live from RESFQ: The Requirements Object Model (ROM), part 3 ArgonDigital - enterprise automation experts

Today we have an example to illustrate what I’ve said in the past two posts from Tuesday’s setup for the ROM and Wednesday’s definition of the ROM. Let’s say in this scenario we have an online gaming company that historically has only built complex role-playing games. Now let’s say the head of product management wants […]

Live from REFSQ: The Requirements Object Model (ROM), part 2

Live from REFSQ: The Requirements Object Model (ROM), part 2 ArgonDigital - enterprise automation experts

What follows is our ROM defined. For context, you can see yesterday’s post on why we have a ROM now at ArgonDigital.   Definitions for the items in the ROM hierarchy: Business Problem: Describes a problem to be solved. Business Objectives: Desired metrics the business seeks to meet in order to solve the problem. Business […]

Live from REFSQ’09: The ROM, Experiences with a Requirements Object Model

Live from REFSQ’09: The ROM, Experiences with a Requirements Object Model ArgonDigital - enterprise automation experts

What follows is a summary of the paper I wrote with James Hulgan (also from ArgonDigital) and presented at REFSQ’09 last week. The paper is titled “Experiences with a Requirements Object Model”. You can get the actual paper here. Most software projects we’ve seen develop features that don’t add value or they don’t build what […]