2. One of the factors that kept in mind during systems evaluation was “raising users’ skill level and confidence”. Suggest one type of test that could be used to know if the users feel confident and skillful with the systems. Explain when should this test be best performed and why.
Many information technology professionals think of testing as a stage that comes near the end of information technology product development. Instead of putting serious effort into proper planning, analysis, and design of information technology projects, some organizations rely on testing just before a product ships to ensure some degree of quality.
Depend on our article; I think user acceptance testing could be user to know if the users fell confident and skillful with the systems. User acceptance testing is an independent test performed by end users prior to accepting the delivered system. It focuses on the business fit of the system to the organization, rather than technical issues.
In fact, testing need to be done during almost every phase of the systems development life cycle, not just before the organization ships or hands over a product to the customer. To help improve the quality of software development projects, it is important for organization to follow a through and disciplined testing methodology. System developers and testers must also establish a partnership with all project stakeholders to make sure the system meets their needs and expectations and the tests are done properly. [1]
[1]Schwalbe, Information Technology Project Management, 2007, pg. 328
3. According to the article, there were more problems discovered during the whole project implementation. Do you think this project was successfully managed? In you own opinion, what caused these discoveries to occur (in other words,” what went wrong?”), and what do you think should be done to avoid these?
Actually, in my opinion, this project was not successful managed.
Because the corrupted data was making it difficult to demonstrate correct processes in the PRMS class, the same was true of the live system. During the consolidated pilot phase, real-time data was used in the final days of testing, which revealed some timing and procedural issues that were easily corrected, but would have had significant impact on planning in a live environment. As do most projects of this nature, the UGC project changed its design, but not its scope as it progressed. The goal from the beginning was to enhance the users’ knowledge of the software and to begin using more of its functionality. Real time data was used in the final days of testing, which revealed some timing and procedural issues that were easily corrected, but had significant impact on planning.
The causes of the data corruption were found, corrective action was taken and documented and additional training was developed as needed. The power users would then make the necessary corrections to the data in the training environment.
When the changes proved successful, the process was repeated in production. As the project developed, this became a key to success. Systems Conversion Ltd’s flexibility and extra effort to develop an improvement plan “on the fly” and yield the desired results. The negative impact potential of projected business volume growth has been greatly reduced and the overall knowledge of UGC’s users has significantly improved.
http://www.systemsconversion.com/casestudies/unisiafinalP2.htm
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment