Three Stage Process

[Vance Shipley]

This project sees folks coming together from inside and outside the telecom industry. Both will benefit from the knowledge, insight and experience of the other. Allow me to offer a telecom perspective on the development of specifications.

The ITU-T, ETSI and 3GPP follow a three staged approach which I'll summarize as follows:

Stage 1:  Requirements

Stage 2:  Logical Architecture

Stage 3:  Interfaces and APIs

Stage 1 is a specification of functional and non-functional requirements. Stakeholder concerns shall cover the entire operational lifecycle (i.e. Day 0,1,2) as well as supporting business goals.

Stage 2 specifies the logical (not physical) architecture and the information (not data) model including behaviour and procedures.

Stage 3 specifications describe one or more protocols and data models.

User stories are input to Stage 1, but are not requirements in and of themselves which are to be derived from them.

In our case Stage 3 should define KRM objects (CRD). It is important however to first define an information model, in Stage 2, which the data model shall represent. This is imperative when there are multiple Stage 3 data models, which we shall see is the case. 

--

Vance Shipley

CEO, SigScale