Professional Services

TMSA announces new Professional Services Capabilities!

TMSA is pleased to announce that after years of working collaboratively on large scale project deployments with world class integrators, we have developed the capabilities to deliver these services to our clients directly through our CMAS contracts. Our key areas of specialization include; Application Development, Quality Assurance and Testing, and Independent Verification and Validation.

TMSA SDLC Application Development Services;

Our software development life cycle (SDLC) is the entire process of formal, logical steps taken to develop a software product. The phases of SDLC we can provide are services related to;

Project planning, feasibility study: Establishes a high-level view of the intended project and determines its goals.

Systems analysis, requirements definition: Refines project goals into defined functions and operation of the intended application. Analyzes end-user information needs.

Systems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.

Implementation: The real code is written here. TMSA professionals are proficient in a variety of languages from COBOL to JAVA, TMSA has the talent.

Integration and testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability.

Acceptance, installation, deployment: The final stage of initial development, where the software is put into production and runs actual business.

Maintenance: What happens during the rest of the software's life: changes, correction, additions, and moves to a different computing platform and more.

TMSA Quality Assurance and Testing Services

We have developed a range of services that reflects our all-round experience, in-depth understanding and total commitment to client satisfaction. With TMSA, you'll get experienced management of professionals who specialize in QA. Our services range from;

Load testing
Reality-check your systems before going live.

Automated testing
Free your test team to troubleshoot defects by automating repetitive tasks. Fast, efficient and consistently accurate, automation delivers maximum gain for minimal resources.

Training
We pride ourselves on the outstanding quality of our training. Delivered in-house or at our purpose-built training facility, our courses focus our unmatched practical know-how on your own business needs.

Enterprise applications
Testing technology built in partnership with the creators of the applications themselves. Achieve deep diagnostics and seamless scripting support with protocols and specific monitors.

TMSA IV&V Services

At TMSA, we believe that understanding the nature of the work is as important as the outcomes. As such we first define our services,

VALIDATION
"Confirmation by examination and provisions of objective evidence that the particular requirements for a specific intended use are fulfilled."

VERIFICATION
"Confirmation by examination and provisions of objective evidence that specified requirements have been fulfilled."

Using the above definitions in software development Validation, in its simplest terms, is the demonstration that the software implements each of the software requirements correctly and completely. In other words, the "right product was built." Verification is the activity, which ensures the work products of a given phase fully implement the inputs to that phase, or "the product was built right."

Component Testing
Testing conducted to verify the implementation of the design for one software element (unit, module) or a collection of software elements.

Integration Testing
An orderly progression of testing in which various software elements and/or hardware elements are integrated together and tested. This testing proceeds until the entire system has been integrated.

System Testing
The process of testing an integrated hardware and software system to verify that the system meets its specified requirements.

Acceptance Testing
Formal testing conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system.

Types of Verification

There are four types of verification that can be applied to the various levels outlined above:

1. Inspection
Typical techniques include desk checking, walkthroughs, software reviews, technical reviews, and formal inspections (e.g., Fagan approach).

2. Analysis
Mathematical verification of the test item, which can include estimation of execution times and estimation of system resources.

3. Testing
Also known as "white box" or "logic driven" testing. Given input values are traced through the test item to assure that they generate the expected output values, with the expected intermediate values along the way. Typical techniques include statement coverage, condition coverage, and decision coverage.

4. Demonstration
Also known as "black box" or "input/output driven" testing. Given input values are entered and the resulting output values are compared against the expected output values. Typical techniques include error guessing, boundary-value analysis, and equivalence partitioning.

Explanation
The four methods for verification can be used at any of the levels although some work better than others for a given level of verification. As an example, the most effective way to find anomalies at the component level is inspection. On the other hand, inspection is not applicable at the system level (you don't look at the details of code when performing system level testing). A logical approach to testing is to utilize techniques and methods that are most effective at a given level.

TMSA utilizes V&V as the primary way of proving your system does what you intended and also meets the needs of the people using it. The resulting V&V effort becomes a significant part of the software development effort. One of the key pieces to demonstrate that the system is implemented completely is a Requirements Traceability Matrix (RTM), which documents each of the requirements traced to design items, code, unit, integration and system test cases. The RTM is an easy and effective way for documenting your implementation, e.g. what are the requirements, where are they implemented, and how have you tested them.