Welcome
We have created this Quality Link Directory and built thousands of links to share the quality websites with others. We suggest those with great websites, large or small, to submit your sites and articles today!

ARTICLES

Career Change - Become a Truck Driver

Are you unemployed? Or have you worked in an office for years and want something different to do to earn a living?

My Reflections

I am no one special. I am a simple guy that gives advice on a forum for free because I care. I care because I learned so much from alot of you out there and I want to give back just as much as I learned.

SuperDave71's Guide to Reconciliation

Taken from http://www.theLoveLogic.com/forum Enjoy

So You Think Truck Driving Is Easy?

I know all of you, whether in the USA or not have seen truck drivers. They are what make the world go around. If it were not for a truck driver, driving all night and day then people would not have anything.

Has Cobra Electronics opened pandoras box?

With the development of the new radio that Cobra plans to display at MATS in March 2008. Is it going to be good for the trucking industry, or will it just be another way for “Big Brother” to stick his hand in the pockets of Truckers?

Submit Link -Submit Article -Latest Links -Latest Articles -Top Hits -Contact -Advance Search

And then came the acceptance test.
Date Added: February 17, 2008 01:53:11 PM
Author: M Trellis
Category: Computer: Software
Acceptance Testing is typically viewed as marking the change in a system’s ownership from the developers of the system to the�system commissioners or users.�It is a distinct phase of testing prior to the final sign-off and delivery of a system to the customers or business users.�The responsibility for acceptance testing may reside with the customer (CAT) and/or end users (UAT - user acceptance testing) themselves.The primary objectives of preceding test phases (unit, integration and systems testing) are those of defect identification and ensuring that each step in the process of building the software delivers working products (verification). The objective of Acceptance Testing is to give confidence that the software being developed, or changed, satisfies the specified requirements, meets customer/user expectations and is fit for business purpose (validation).�Unlike the other test phases, an objective of acceptance testing is not to actively look for faults.�The expectation should be that the preceding stages of testing have identified and resolved software faults and that the system is ready for operational use.Clear entry criteria may need to be put in place to ensure that the expectation of a system being ‘production ready’ has been met.�This is an opportunity to review the effectiveness, completeness and outcome of previous test phases and to declare any known problems that remain prior to acceptance test commencing.As a testing phase with it’s own objectives, acceptance should not duplicate other test phases, such as system testing or integration testing.�However, it may repeat previously run test scenarios to provide confidence that preceding test phases have been completed�appropriately.�Those�responsible for system acceptance should dictate the objectives and coverage of the test phase.�In doing so they are likely to consider the following: Have the acceptance test conditions been demonstrated? Do the test conditions model realistic business scenarios? Is there appropriate coverage of each business function? Is there appropriate coverage of system reports and screens Is there appropriate coverage of application menu options? Are updated training materials and system documentation subject to test?It is important to minimise the number of changes taking place to the system during the acceptance test phase.�The cost of rework, to change software or system operation, at this stage of development is high.�Implemented changes may invalidate testing that has been already conducted and require greater levels of regression testing to be carried out.�Ideally, the software under test should mot be�enhanced during the business acceptance testing with the obvious�exception of defect resolutions.Where faults are uncovered during acceptance, ‘work-arounds’ should first be investigated before attempting to make changes to the software.�However, it may be necessary to agree the correction of high severity/priority problems and to defer/timetable the correction of others before acceptance can occur.�These steps of investigation, review, agreement and/or deferral may need to be repeated until the point where the system is considered as acceptable.�Users involved in the acceptance activities are typically end users rather than specialists and therefore are rarely involved in this activity. To increase their overall productivity it helps if they attend an acceptance testing training course or that their team includes an experienced user who can coach the rest of the team.�The type of project or software under test may allow for parts/modules of the system that meet their acceptance criteria to be signed off in advance of others that don’t.�For projects of this type acceptance can be an ongoing and evolving process that allows earlier or the phased implementation of a system into production�In order to minimise the risk of software faults and system changes, acceptance should not just start at software delivery.�It needs to be a function of the earliest design and development stages.�Early involvement of users in the system requirements and design stages can minimise the risk of gaps and misinterpretations occurring in end system functionality.�The benefits reaped at later stages can be the avoidance of re-work and the reduced cost of system delivery.�These, in turn, will help complete�the�acceptance test faster, which is� a substantial benefit�with the current�trends for ever shorter development cycles.About the AuthorM Trellis is an experienced consultant who works�in testing software�performance and acceptance testing. His assignments are�mainly with end user organisations ensuring that what is delivered from their system suppliers is fit for its �purpose. He is a consultant with independent software testing consultancy Acutest and is based in UK (London). For further information visit: http://www.acutest.co.uk

Ratings:

You must be logged in to leave a rating.

Average rating: ( votes)

Comments:

No Comments Yet.

You must be logged in to leave a comment.