Displaying items by tag: requirements repository
RIC MDG Technology - Better Functional Requirements for Information System-based Solutions
The Problem
A project chartered to deliver an IT-based solution typically begins with establishing high-level functional requirements (HLRs) which are eventually followed up with detailed functional requirements (DTRs). The problem is that there have never been clear guidelines for what constitutes ‘high-level’. And when it comes to DTRs, there are no guidelines for how much detail there should be in a given requirement statement, making it difficult to check for overall completeness and/or redundancy.
The Solution
The solution to the HLR problem is to recognize that there are five fundamental capability types for adding domain-specific functionality on top of a data management capability. A given high-level functional capability should be viewed as one of the following:
- A Report
- A User Interface
- A Data Import
- A Data Export
- An Automated Function (e.g. ‘batch job’)
A given HLR should only identify who it is that needs a specific one of those types. A properly high-level HLR should contain no ‘field-level’ details.
The solution to the DTR problem is to recognize that for each of the above five types, the necessary detail can be captured in a ‘structured’ format rather than in textual requirement statements. A single DTR, containing no more detail than its corresponding HLR, should be sufficient as an aggregation point for the capability’s structured details.
The RIC MDG Technology provides that structure. It extends the Enterprise Architecture concept of Requirement, and adds additional stereotypes to capture the detail.
The Trips-R-You Web-Based Flight Reservation System case study shows examples of HLRs, DTRs, and spreadsheet-based templates structuring the example details for each of the five capability types. The RIC extensions are described in the article Tool Support for Requirements [In Context]. Documenting functional requirements for an information system-based solution using Requirements In Context format is described in detail in the Requirements In Context Series of Articles.
NOTE: Any questions or problems with the RIC MDG Technology please contact the author.
Enterprise Architect for Business Analysis - Requirements Management
Capturing and communicating business needs as requirements is a critical task of a Business Analyst.
Requirements Repositories allows capturing those requirements once, then have them available to you and your team for the projects lifetime and beyond. Using Requirements Management tools like Enterprise Architect, the captured business requirements can then be transformed to a formal requirements specification according to the business information needs and views of every relevant stakeholder. Also validating these specifications by tracing from the requirement specification and solution components at every level directly back to the business requirements helps you create the most accurate solutions imaginable. This webinar shows how to use Enterprise Architect for building and managing a requirements repository. You will also learn how to establish requirements traceability in Enterprise Architect thereby documenting the lineage of the requirement to its solutions.
We encourage you to register for the webinar using the link below:
https://sparxsystems.com/resources/webinar/businessanalysis/requirementsmanagement/index.html