“Testing as a Service (TaaS) – People, process, accelerators, tools, technologies delivered in a consumable as-a-service model”
Ahmed Adel in this Slideshare pack
Testing as a Service has its merits for performing quality control on an OSS product set. It certainly provides greater resourcing flexibility and the swarm engineering model allows a faster time to revenue for product or project development.
The following three variants support a TaaS model:
There’s only one down-side. Almost all OSS products are very data-driven. Data models are almost always unique with no customer having identical networks, topologies, services, vendors, technologies, naming conventions, etc.
TaaS can handle the volume, but it is still essential to perform tests with the customer’s own data as this is the only way to provide contextual accuracy to your testing.
Earlier this week, I was lucky enough to be introduced to a talented RAN automation expert. He’s one of Australia’s foremost, hands-on, experts on SON
I was listening to a group of telco experts on a podcast the other day. As they were talking, I kept picturing the image of
Earlier in the year, we wrote a series of articles about the chasm that exists between OSS/BSS buyers and sellers (pt1, pt2, pt3, pt4, pt5, pt6). “The chasm” is
Actually, maybe a few related questions. As you’ve seen from recent articles such as this, I’m increasingly interested in the cross-over worlds of comms and
Here at Passionate About OSS, we are exactly that – Passionate About OSS (Operational Support Systems). We’re also passionate about BSS, NMS, or any other names you call the tools that help to operationalise your network.
