Business requirements are a tool for documenting your business solutions for driving higher value in your company. In Elements Catalyst you can raise and manage business requirements independently as well as in the context of the process diagrams, Salesforce org and ref models.
By default any user (including free viewers) can raise requirements and collaborate on them using comments in a PRO space. However, in order to manage requirements through the full lifecycle, prioritise them in the release schedules and enrich them with user stories, you will need a requirement manager permission.
Article outline :
- Raising & submitting requirements
- Requirement grid behaviour
- Managing requirements
Raising & submitting a requirement
By default anyone can "raise" a requirement. In the main application select the "Changes" menu item and then click on "Add new" on the toolbar (all the way to the left).
A new row will appear at the top of the grid. Specify your business requirement, i.e. the problem being solved, the proposed solution as well as target release, priority, impact, risk etc. Once you're done just click "Add" in the command column on the left.
The command button is always present on the screen even if you scroll right to other columns.
At this point a requirement is in "Being raised' status and this allows you to add any additional information, like notes, links, data tables, images, or even change the requirement details, in the right panel.
The right panel can be closed/open using a blue arrow button on the right side of your screen.
Once you feel the requirement is ready you can click "Edit" in the command button and change it to "Submitted". From this point only a requirement manager can manage the submitted requirement.
Change grid behaviour
The change grid allows you to filter and sort requirements by any standard and custom field. You can also resize the column widths. The system will save set filters and column widths so when you visit the change grid next time it will be exactly how you left it !
In order to edit items in the grid you need to use the command column on the left. The reason is that when you start editing a requirement we 'lock' it from being changed by anyone else in the system.
You can also use the context menu (right-mouse click) to delete an item in the grid or copy a link to that item (more on that later in this article).
You can also import and export all requirements visible in the grid (based on applied filers) either in a csv file (which only includes the standard fields) or an excel file (which also includes the custom fields). Read this article to learn more about importing and exporting requirements and stories.
A requirement manager is responsible for assessing, consulting, and implementing the submitted requirements. They can edit it at any point during the cycle, specify actionable user stories for a requirement and link it with process activities or model nodes.
The image below outlines the default business requirement lifecycle. The requirements with statuses: "Implemented", "Deleted", "Will not implement" and "Duplicate" will be put in the "Closed" category list so you can concentrate on the ones requiring action.
The closed requirements end up in the closed section of the grid which you can access at the top of the page.
You might also find these articles helpful: