Telecom Testing
Telecom lifecycle is different from the
software lifecycle and a testing strategy based on the telecom lifecycle is
required to address the issues of converged space. V, X and proactive testing
models do not address the challenges of telecom end-to-end business in the
converged world as it is non-standard and lacks a common industry acceptance.
Issues in telecom testing are taken up in more detail as challenges under each
view of telecom lifecycle.
The telecom testing lifecycle is based
on the NGOSS telecom lifecycle defined in GB927. The testing lifecycle consists
of four views. The business and deployment view is concerned with the service
provider while the System / Architecture and Implementation view correspond to
the Service Developer. As shown in figure 1, each view in the telecom testing
lifecycle generates a set of artifacts. The artifacts in each view serve as
input to the succeeding views. Any customer request or service development /
enhancement can be categorized as a business requirement. The testing lifecycle
starts once the business requirement is analyzed. Once a decision is made on developing
the requirement, testing then moves to the system / architecture view where the
service developer works on defining a technology- neutral method of
implementing the requirement. This is followed by the Implementation view where
the requirement is implemented. The implementation view in itself would involve
certain amount of integration of the component developed in stages. The major
view where a telecom-based testing pays off is in the deployment view where
multiple implementations are integrated during deployment. In a multi-service,
heterogeneous, multi-vendor environment, the test artifacts and their execution
results for the other views serve as input to generation of deployment
artifacts that result in providing new service offerings with a higher degree
of flexibility and a shorter time-to-market with minimal or zero failures
during operation
The test artifacts developed in
different views can be test plan, test case or even a test model for the
specific telecom scenario.
Figure 2 shows the items that make
up the test artifacts developed in each view.
|
5. Views in the Testing Lifecycle
5.1 Business View
This view handles investigation of
the requirements and Proof of Concept before taking up the requirements. The
investigation of the requirements
starts with elicitation and ends with specification. Based on requirement
specification artifacts, a proof of concept (PoC) is developed to assess the
feasibility of taking the requirement to service developers based on current
infrastructure and products.
List
of Companies Developing/Testing software for Telecom Products
SASKEN
WIPRO
TCS
ADVENTNET
HCL
SATYAM
TECH MAHINDRA
SASKEN
WIPRO
TCS
ADVENTNET
HCL
SATYAM
TECH MAHINDRA
No comments:
Post a Comment