AfroCentric Helios IT

To whom it may concern, This letter makes recommendation of the Testing Services provided by Ubungcweti Management Services (Pty) LTD to AfroCentric Helios IT (Pty) LTD

Customer Name:
AfroCentric Helios IT
Team Size:
12-15 resources
Project Duration:
01/02 to Current
Oracle - Medscheme's (Nexus System)
Type of Testing:
Requirements Testing, Integration Testing, Regression testing and Performance testing.
UMS Role in Testing:
Life Cycle Phases - Initiation, Planning Analysis and Design, Execution readiness, Closeout, Handover
High Level Responsibilities:
Assess if the system can support day-to-day business and user scenarios and ensure the system is sufficient and correct for business usage. Verify the system’s behaviour is consistent with the requirements.
Metrics per release:
Test Cases executed, effort distribution, defect find rate, defect fix rate etc
Metrics daily:
The number of Defects, reviewed defects per day, Test Case Effectiveness - effectiveness of the test cases and the stability of the software, The number of test cases executed per person per day, The of test cases derived per day per person
Acceptance Testing::
UMS is AfroCentric's (Helios IT) preferred Supplier for Development and Testing. They also provide IT Executive placements. As a result of this contract, UMS has placed Test Managers, Test Leads as well as Test Analysts to execute the following:
  • Analysis of Business Requirements
  • Creation of UAT test plan
  • Identify Test Scenarios
  • Create UAT Test Cases
  • Preparation of Test Data(Production like Data)
  • Run the Test cases
  • Record the Results
  • Confirm business objectives
Lead Times:
UMS has proven that they are able to provide quality resources to AfroCentric with the shortest Lead times possible. They have a number of resources on the bench that are able to start within a week. Turnaround times are fast and efficient. If specialised skills are required, this could take a bit longer but nothing less than a more than a 2 month period for perm placements
Quality of Resources:
Provide an overview of the types of resources that were provided to you who have the necessary skills applicable to the specific project and functional subject areas being contracted, inclusive of software testing experience and proficiency, test tools and software applications under test (knowledge and experience in the specified test tools and software applications
UMS Account Model:
The UMS Sales and Services Model enables UMS to develop a strategic partnership with Helios IT. The Account Manager liaises once a month with the Line Manager to ensure that the Client is receiving quality deliverables by conducting monthly KPI sessions. UMS Service Delivery Manages are weekly on the floor ensuring UMS consultant are delivering. They are able to look at the staff performance and rectify issues
Commitment of Resources:
UMS has always been committed to delivering quality resources with the shortest turnaround times. Resources are bound into the system using the UMS MOU document ensuring that resources are committed and available once client is happy with the interviews.
UMS Flexibility of notice periods, etc:
UMS Client and Contract Notice periods are aligned to the BCEA, 1 Week for Resources who have worked for less than 6 months, 2 weeks for resources that have worked longer than months but under a year, 30 days for resources who have worked over a year. UMS is flexible in replacing resourcing as long as sufficient notice is provided or adequate planning carried out between the Client and UMS.
Business Continuity:
Backup Resources are readily available. Handover is managed by the UMS Sales Team and little impact is felt by the business with minimum impact to the business.
Work Breakdown structure and schedule is done in conjunction with the client and at a Test Analyst / Test Manager or Lead level.
Resource and Capacity Planning:
The Service Delivery Manager works with the Client Team leads to ensure that resource capacity is measure adequately for projects. UMS is flexible is sharing resources based at the same client across projects to ensure maximum delivery.
Since UMS offers Analysis, Project Management and Testing Resources to Helios IT, a number of the resources are involved in the planning and design phases of a number project deliverables. Since the inception of Helios IT as the IT company of AfroCentric , UMS resources have been involved in a number of initiatives to define the Testing Areas PPP's.
Areas of Testing:
UMS resources have conducted the following types of testing for Afrocentric- Acceptance Testing, Functional Testing, Integration Testing, Post - Implementation Support .
Data Clean-up:
Quality Center is the tool that testers are using to manage test plans and test cases as well as test execution.
Process Improvements:
UMS Resources are actively involved in test process improvements and using different testing methodologies.
Monthly KPI are done with their staff and performance is discussed on a monthly basis with clients. Resources provide weekly status reports to SDMS.
Testing Services:
There have been no breaches to date with UMS regarding the testing services provided by UMS to AfroCentric.
Testing Information:
Quality Center is the toolset used for test planning and test cases.
Acceptance Testing::
Before the User Acceptance testing can be done the application is fully developed. Various levels of testing (Unit, Integration and System) are already completed before User Acceptance Testing is done. As various levels of testing have been completed most of the technical bugs have already been fixed before UAT. Effective User Acceptance Testing Test cases are created. The following steps are carried out by the Testing team:
  1. User Acceptance Test (UAT) Planning
  2. Designing UA Test Cases
  3. Selecting a Team that would execute the (UAT) Test Cases
  4. Executing Test Cases
  5. Documenting the Defects found during UAT
  6. Resolving the issues/Bug Fixing
  7. Sign Off
Testing Tools
Quality Center is used to do all test planning
UMS resources are able to perform complex functional, application, regression, and performance tests, Design and maintain UAT test cases to be re-used for recurring and common implementations, Map business requirements into test cases and/or test scripts. Execute objectives and targets for internal UAT team, establishing baseline of results, milestones of achievement, Archive a process and review implementation requirements and specification, identifying all points of testing and expected outcomes, Document and report test results as well as identify and track issues and defects, Assist in the parallel running of the current system to ensure the new product results are validated against the existing application, Help analyse and improve test plans and results for each product, Work with implementation teams to ensure the quality of the product and timely bug resolution, Provide afterhours support during maintenance windows as needed.
Core Functions
Please provide detail around the involvement of UMS Resources delivering these core functions for your company
One of the most important activities in the UAT is to identify and develop test scenarios. These test scenarios are derived from the following documents:
  • Project Charter
  • Business Use Cases
  • Process Flow Diagrams
  • Business Requirements Document(BRD)
  • System Requirements Specification(SRS)
The UAT test plan outlines the strategy that will be used to verify and ensure an application meets its business requirements. It documents entry and exit criteria for UAT, Test scenarios and test cases approach and timelines of testing .Identify the test scenarios with respect to high level business process and create test cases with clear test steps. Test Cases should sufficiently cover most of the UAT scenarios. Business Use cases are input for creating the test cases.
Preparation of Test Data.
Confirm that business objectives are met.
  • Analysis of Business Requirements
  • Creation of UAT test plan
  • Identify Test Scenarios
  • Create UAT Test Cases
  • Preparation of Test Data(Production like Data)
  • Run the Test cases
  • Record the Results
  • Confirm business objectives
Business Analysts or UAT Testers needs to send a sign off mail after the UAT testing . After sign-off the product is good to go for production. Deliverables for UAT testing are Test Plan, UAT Scenarios and Test Cases, Test Results and Defect Log, Before moving into production, following needs to be considered:
  • No critical defects open
  • Business process works satisfactorily
  • UAT Sign off meeting with all stakeholders