Powered by Adaequare offers e-Way bill API's Try them FREE

Capturing Requirements

A Comprehensive Framework for Capturing Requirements

Executive Summary

Expectations cause misery is an old adage. However,in software product engineering , misstated or unstated requirements are the root cause of many failures and support issues.

The purpose of this document is to provide a framework and to discuss the details that need to be addressed for deriving requirements for a software product. This helps in ensuring that the product meets and exceeds the expectations of users, partners’ community and internal IT organizations.


High Level Requirements
The prime objective of this section to is to express concisely the high level requirements and understanding of the proposed system.

Given below are the types of information which need to be captured for better understanding the context and nature of the product.

  • Business goals and Objectives
  • Current Problems, Opportunities
  • Business Requirements
  • Business processes
    • Profile of Business Objects/Entities
    • Profile of Business Entities
    • Profile of data sources
  • Critical Success Factors
  • System Context Diagram
  • Data context diagram
  • Document Classification
  • Constraints,Risks and assumptions

Requirements relating to Business Process Model
Information should be gathered on the existing and proposed business process model with the following details. It is suggested that,as many inputs as possible ,relating to the following items,should be captured and documented.

  • Business process model hierarchy
    • Super process
    • Major process
    • Sub-processes
    • Elementary processes
  • High level/ Detailed process flow
  • Description of business objects and attributes
  • Description of each business process
  • Description of business events

Requirements relating to Business Data Model
Information should be gathered on the existing and proposed business data model with the following details. It is suggested that, as many inputs as possible , relating to the following items , should be captured and documented

  • High level entity descriptions
    • Outline for describing the entities
      • Entity name
      • Alias(es)
      • Definition
      • Existence constraints
      • Business rules
      • Volumetrics
      • Attributes
  • Entity Relationships
    • Outline for describing the relationships
      • Relationship name
      • Description
      • Cardinality classification
      • Existence constraints
      • Business rules

Software Engineering Solution/Technical Requirements
Information should be gathered with respect to the following items to understand the solution/technical requirements:

  • Candidate technologies (HW/SW/Networking)
  • Computing platform requirements
  • Technical component diagram
  • Interoperability requirements
  • Database selection/requirements
  • Interface requirements
  • Reliability requirements
  • Performance requirements

System Distribution Strategy Requirements
This section describes issues related to setting up and maintaining the proposed solution:

  • Data and process association matrices
    • System transaction matrix
    • Data entity/location matrix
    • Data entity/volume matrix
  • Data and process distribution technology

Security/Control/Administration Requirements
This section discusses a variety of security and control requirements that need to be addressed for the proposed solution.

  • Categories of users
  • Administration Requirements
  • Security Requirements
    • Application
    • Database
    • Network
    • Operating system
  • Integrity requirements
  • Audit requirements
  • Disaster Recovery

System Operational Requirements
This section addresses a variety of performance related requirements.

  • System response time requirements
  • Operational service level requirements
  • System accessibility requirements
  • System availability and reliability requirements
  • System throughput requirements
  • Batch report/user queries requirements
  • Miscellaneous batch job requirements (data archiving etc.)
  • System printing requirements

Capacity Planning
The prime objective of this section is to analyze and estimate the capacity requirements of the proposed solution

  • Online Usage
    • Geographical distribution of users
    • System transactions overview
    • Transaction usage frequency
  • Batch Usage
  • Initial disk space sizing
  • Extra capacity load
  • Network requirements (speed, bandwidth etc.)
  • Computers/LAN requirements

Capturing the above requirements and addressing them in product design will go a long way towards creating a robust and stable product that becomes a stakeholder’s delight.

Requirements Traceability Matrix

Project Name

Current Version: current version number
Date Last Updated: last update date
Last Updated By: update author name
Author: author name
Date Created: creation date
Approved By: approving body
Approval Date: date of approva
Seq. # Document Requirement Type Category Priority Use Case Test Script Analysis Model(s)/ Business Objects Development Cycle
Assign a unique sequence number. Reference the source document, where the requirement is defined. Restate the requirement definition. Constraint , Hardware, Software, Performance, Other Link to System Scope Statement Category. Select from:Functionality, Data, Interface,Architecture Assign a priority – classification may be dependenton project. Provide the use case name Reference the Test Script to test this requirement Reference the containing analysis model(s) and associated business objects Provide the iteration of the development cycle this requirement will be implemented in when that becomes available
About Adaequare

Adaequare is a pioneer in cutting edge Data, Product and Test Engineering Solutions. Established in 2001, Adaequare is a CMMi Level 3 Certified company and has global presence across 3 different locations. Our thrust to be creative is our key to success in this contemporary world.

Data drives Performance! At Adaequare, we are committed to deliver state-of-the-art business solutions through engineering excellence. We enable organizations to improve business performance and realize higher returns on investments through the potential of our business solutions. With innovative, data-driven services and products, we ensure that our customers stay ahead of their competitors through rapid and effective decision making.

Our Data, Product and Engineering capabilities, along with our expertise and experience help organizations improve their business processes continually. We deliver value with cost-effective, high value-based and quality solutions that can precisely address your business challenges

Adaequare means ‘equal to requirement’ and it signifies our focus on providing precise, cost-effective solutions with outstanding quality. We deliver what it takes to turn your ideas into value – to your customers and employees alike!

Get in touch

For more details about our services and solutions, contact us now

Your Name *

Your Email *

Your Message

Download (PDF)

This White Paper is for informational purposes only. ADAEQUARE MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS WHITE PAPER.

Adaequare software Engineering is a trademark of Adaequare.

©Copyright 2014 Adaequare. All rights reserved. Reproduction in any manner whatsoever without the express written permission of Adaequare is strictly forbidden. For more information, contact Adaequare.

information in this document is subject to change without notice.