Dramatic Growth Demands Spur Unisia PRMS™ V. 8.4 Support(pan xia 1000819055)

Q1. Based on the article, there was a problem of corrupted data in the midst of project implementation, which affected the demonstration of correct processes in the PRMS class and the live system. How was this problem solved? Explain your points.

The data errors were ferreted out by the efforts of the SCL team. These data errors occurred during the planning. It was quickly agreed to frequently review and adjust the production company concurrent with training. 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. [1] In my point of view, Concurrent piloting, training reinforcement and a correct process were developed by SCL to solve this problem and help the staff became better at planning.

Q2. 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.

User acceptance testing could be used to know if the users feel confident and skillful with the systems. User acceptance testing is an independent test performed by end users prior to accepting the delivered system.

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. In fact, testing needs 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. [2] So user acceptance testing should be best performed after the system developed and before implementation.


References:
[1] Dramatic Growth Demands Spur Unisia PRMS™ V. 8.4 Support. Systems Conversion, Ltd. 2001
Available at: http://www.systemsconversion.com/casestudies/unisiafinal.htm
[2] Schwalbe, Information Technology Project Management, 2007, pg. 328