Requirement Document Template

Requirement Definition Document

For

ITS-E-T026 I1.4

CONTENTS

1 INTRODUCTION 3

2 REQUIREMENTS 3

2.1 Low Level Functional Requirements 3

2.2 Operational and Environmental Requirements 3

2.3 Reliability Requirements/ Expectations 3

2.4 Volumetric and performance requirements 3

2.5 Security Requirements 3

2.6 Delivery Requirements 3

2.7 Documentation Requirements 3

2.8 Maintainability and Support Requirements 4

2.9 Look and Feel Requirements 4

2.10 Usability Requirements 4

2.11 Legal Requirements 4

2.12 Constraints (as stated by the customer) 4

2.13 Acceptance Criteria 4

3 REQUIREMENTS LIST FORMAT 4

INTRODUCTION

1. Purpose

This plan is to be used as a ‘Project Management Tool ’ for the project Mediation System to be executed for Mr.Bhushan Bhupta (Customer).

The purpose of this plan is to identify and define all project activities, organizational responsibilities for these activities, resources and monitoring mechanisms required to execute these activities for the entire project.

2. The system accepts input from network elements in the form of CDR file and outputs the required data in the format as expected by respective downstream system.

Scope of the project is restricted to offline processing.

3. Definitions

Audit Trail – Input from switch to output from mediation

NW1 – input directory

NW2 – input directory

Acronyms

CDR – Call Detail Record

REQUIREMENTS

1 Low Level Functional Requirements

• Handling heterogeneous CDR formats from NW1 and NW2

• Invalid file format or CDR format check

• Duplicate CDR file checking and its processing

• Filtration of CDR based on business logic agreed

• Distribution of CDRs to respective downstream system in the format they expect...