How we assure Quality in Software Development at Rebaca
Software Development as a Service
Today, almost everything is moving towards a service-oriented model. From software to enterprise, the shift is towards service orientation. Software is delivered through SaaS, infrastructure through IaaS, and tools through PaaS. Even enterprise APIs follow a service-oriented architecture. From telecom to hospitality, industries everywhere are shifting products into services.
At its core, the service model is simple: a consumer makes a request, and a provider fulfils it. In the SAAS model, users raise service requests to Google and Office 360 by using a web browser and the software running at the data center fulfils these requests by returning relevant data. At Rebaca, we were early adopters of the Software Development as a Service (SDAAS) model.
Quality of Service
For us, quality is defined by the experience of the user. A car that offers good consumer experience, such as nice handling, sharp breaking, quick acceleration and low fuel consumption rates higher in the quality index. A software deployed at a data center, offering bad consumer experiences, such as slow response, wrong calculations and frequent crashes under increased load conditions rates lower in the quality index. In the world of Software Development As A Service, the product owners are the consumers of the service. The product owners expect the service to be fast, accurate, cost-bound and time-bound. A development team meeting these parameters rates higher in the quality index. At Rebaca, quality of service is our top priority.
Assuring The Quality of Service
| Qos Parameter | Rebaca Process Assuring The QOS Parameter | HOW The Process Assures QOS |
|---|---|---|
| FAST | Requirement Management | This process breaks each customer requirement into 1 or many implementation items or OUTPUTs in such a way that the outputs as VALUABLE, INDEPENDENT, SMALL and DEMONSTRABLE. The OUTPUT(s) are later associated with the corresponding artifacts such as code changes and document changes. This enables us to deliver quickly and consistently. |
| ACCURATE | Validation Management | We test and review the artifacts linked to each output, fixing any defects before release. 2 levels of tests and reviews are done – DUT and DIT. DUT is done by developers while DIT is done by testers. This ensures accuracy and reliability in every delivery. |
| COST BOUND & TIME BOUND | Schedule Management | This process loads the outputs into short schedules of a few weeks, called DEADLINE(s). Then it breaks them into micro-tasks which are less than 24h of effort estimates. These tasks are assigned to the appropriate team members and loaded into the ITERATION(s). Each iteration is limited to 40 hours of effort across a week. The team is expected to complete the loaded ITERATION(s) and DEADLINE(s). This structure keeps our work both time-bound and cost-effective. |
