Requirements Manager
Requirements and IT
A set of requirements outlines the functionality of an IT system. Capturing requirements as closely as possible is an essential part of designing, building and understanding IT systems.
In a traditional IT approach, the requirements are usually communicated through documentation compiled by domain experts and business analysts to the architects and developers writing system code.
Traditional IT design processes devote large amounts of time at the start of projects to elicit exact requirements from experts and reduce the number of expensive, high-impact requirements that arise later. Unfortunately, this strategy does not take into account the ways humans recall information, particularly domain experts. This failure often leads to disruptive additions as some requirements are inevitably overlooked at the beginning of projects.
The Erudine approach to capturing requirements for complex IT systems focuses on one of the main mechanisms humans use for recalling information: association. Using Erudine’s technology, a domain expert is presented with specific situations as the system is built. Instead of being faced with possibilities before the system is even constructed, the domain expert can associate specific situations with the relevant requirements as the system grows - meaning no omissions and no expensive requirement additions later in the project.
The Erudine software itself handles any changes that need to be incorporated into the system. Adding high-impact requirements later in a project is no different from adding requirements that were known at a project’s inception.
Erudine's process for capturing system requirements and building IT systems is centred on human mental processes. Erudine uses a Case Based Reasoning approach to allow experts to define the system behaviour and build up a requirements document at the same time.