ICT benefits realisation consultancy

Requirements definition

We scope and define the software and hardware user requirements of your proposed mobile system. Through working with your users we identify the system requirements that will enable them to do their jobs more efficiently and effectively. We align these user requirements with the organisational objectives to ensure all stakeholders benefit appropriately from the system implementation.

How you will benefit

Much of our research is conducted in the context where the new technology will be used. Our focus on context helps ensure users of the new system will be able to effectively carry out the specific work processes that have been identified. We provide:

• A user requirement definition that will save you development time and money
• An unbiased solution-independent view of user requirements and potential use in the field
• A clear understanding on the front line requirements and the variations involved in using systems across a number of job roles and locations
• An understanding of the existing work practices and what changes would actually be beneficial and solicited by users – rather than what the organisation perceives as useful
• Independent analysis of the usability of your existing systems and processes

What we do

We draw on a variety of quantitative and qualitative methodologies such as surveys, interviews, work shadowing, and process reviews and a range of methods from the field of Human Computer Interaction such as usability testing, expert reviews, and prototyping. We have considerable experience at working alongside people to gather a range of work practice and work process related data, whilst having minimum impact on their behaviour.

Things that may be on your mind about requirement definition

1. Every user comes up with a different set of requirements, how do I decide who is right?
Everybody will have a slightly different set of requirements because each user will have varying perceptions and behaviours. As you talk to more users, however, patterns will emerge and you will be able to identify which requirements are core and those that are secondary. A good rule of thumb is to talk to at least 5 users; this generally identifies the core requirements that will effectively support 80%+ of your user base.
2. Shouldn’t we iteratively develop the system rather than focus on a single requirement definition?
To get the most out of your system it is essential you follow an iterative development process. Repeatedly test and redesign with users throughout development – our requirement definition will ensure you set out on the right track, but it is the foundations rather than the finished product. If at all possible put into your development contract iterative development phases, to avoid prohibitively expensive changes further down the line.
3. Why can’t we rely on developers to advise us?
Developers can offer some guidance, but in general because they are removed from what actually happens out in the field, they will not know or fully understand the real needs and work practices of the users.