3rd Generation Partnership Project (3GPP) standardized Next Generation Network (NGN) architecture which intends to integrate the services provided by the existing IP network with the mobility of portable digital devices like 3G cellular phone. IMS defines a complete architecture and framework that enables the convergence of voice, video, data and mobile network technology over an IP-based infrastructure. It bridges the gap between the two most successful communication paradigms, cellular and Internet technology.
Similarly one cannot imagine shaping any telecom apps to be developed without SIP at all. Combined with the power and simplicity of Java technology in the form of the SIP Servlet API, an application developer can create and deploy new services to users in a fraction of the time it previously took.
Standardizing forums are coming up with strategies in design to cater to the changing telecom needs but it looks like "Testing Methodologies" being used are still relying on legendary models which is not
suited for converged world.
The high degree of complexity associated with the telecom
technology necessitates testing strategies that can create and deploy new service offerings. This intends to be with a higher degree of flexibility and a shorter time-to-market, without loosing the competitive edge in rolling out new, compelling service with improved customer satisfaction.
Need to Evolve Testing Strategy:
Testing strategy are not evolving based on the pace of operator adding new or expanding existing networks to support new technologies and products.
With convergence and multi service, multi vendor and heterogeneous networks arena; testing of interface and components become more difficult and complicated.
We also shouldn't forget that we have seen few important M&A (merger & acquisitions) in telco domains which undoubtly influences the requirement for proper telecom testing. Ease of integration requires a holistic view of telecom testing and can be the key to the success for real interop. These requirements trigger the need for new
strategies in telecom testing.
Existing Model -
Currently we have few popular generic testing model which are legendry and being blindly followed by Telecos for testing.
SDLC models are
1. Waterfall model
2.Prototype Model
3. Spiral Model
TLC Models are
1. Fish Model and
2. V-Model
V-Model is used for tester's where as SDLC we have developers and testers. V-Model is a Testing Life Cycle Model which is entirely different from Software Development Life Cycle.
In V-Model the strategy goes like this
Gathering phase -- User Acceptance Testing.
Analysing phase --- System Testing
Design Phase (HLD andLLD) ---Integration Testing
Coding phase --- Unit Testing
build
Here unit testing is done related to Coding
Integration testing is based on Design phase
System Testing is done related to Requirements (Analysing phase)
User acceptance is done based on Gathering phase.
In Waterfall Model the tester role will take place only in the test phase but in V-Model role will take place in the requirement phase itself. Waterfall model is a fixed process and we can't make any changes in the requirement or in any phase but in V-Model u can make any changes in the requirements. V-model is the simultaneous process but it is not in case of water fall model. Waterfall model used only the requirements are fixed but V-model can be used for the any type of requirement (Uncertain requirement)
Here below table helps us to understand how different SDLC phases are linked with differnet testing activities and available tools.
==========================================================
In my next blog; I would like to talk about: What is the Telecom testing lifecycle? Why above models are not so efficient? Business/System/Architecture/Implementation/ Deployment View in the Testing Lifecycle. Their challenges and possible resolutions. Best Testing model for Teleco products or Management software.
No comments:
Post a Comment