Testing of the System User Interface – Case Study Example

Download full paperFile format: .doc, available for editing

The paper "Testing of the System User Interface "  is an outstanding example of a case study on information technology. Task 1 Executive summary Testing is an important method and need of every system development and implementation. Without testing, we can not achieve an effectively working system. There are a lot of areas of the system testing that are incorporated to assess the system's best performance and error-free working and operations. In our system for MyPress Publishing Ltd, we have to deploy an effectively working and operational system that can manage and handle the Publishing tasks, human activities, and other associated activities.

The importance of testing for this system is really vital. For the error-free working of the MyPress Publishing System, we need to test the system in all the aspects and functionalities. Here we need to find out all errors that can stop or halt the overall smooth working. Implementation of different testing techniques will outline the main working problems that make the overall system non-functional. The unit testing for the MyPress Publishing System will outline the main systems errors in each functional component.

This will ensure better working for each system area. Then we need to test the overall system for its working this type of testing will make certain regarding the best system coordination, mutual data sharing, and record management. Testing of the system user interface will ensure the best and more user-friendly working environment for the working personnel. Here we will ensure that system does not make the user distracting because the user's interest in system working makes the best user performance. Here we also need to test the system for the quality of working and best performance.

This can comprise the system response time, working delay, speed, resources used, and accuracy of the results. In this way, we can ensure the best and appropriate system response. Task 3 Test domains that could be tested but cannot reasonably be tested 1- Environment The working environment is a vital factor in every system implementation. The analysis and implementation of an enhanced working environment make people happy regarding working on the systems (Pressman, 2001). The analysis and testing of this domain are really essential. This provides us valuable information about people's behavior, their working areas, interest, and habits.

Through this analysis, we can develop a better working environment. The testing of the environment is difficult because every working person has different habits, likes, and dislikes. The generic working environment is difficult to build and implement. The testing for the environment requires extensive hard work for the analysis of the user working at the workplace, and then we have figured out the main problems and difficulties. The mitigation of these problems is also the main issue in such type of testing.

Another main factor that makes this area harder to test is the strategy or policy for the testing. To choose such a testing strategy or policy we have to analyze the main working style, user needs, basic requirements, and handling policy. In this way, we can make the system better to implement for the workers and operational people. So the main difficulties regarding MyPress Publishing System testing are:

References

Adams B., B. E. (2004). Applying Strategies to Overcome User Resistance in a Group of Managers to a Business Software Application: A Case Study. Journal of Organizational and End User Computing; 55, 10.

Alavi. (1984). An Assessment of the Prototyping Approach to Information System Development. Communications of the ACM, (p. 27).

Anderson, S. D. (2004). Project quality and project managers. International Journal of Project Management, 10, 138-144.

Baskerville, & Stage. (1996). Controlling Prototype Development through Risk Analysis. MIS Quarterly, (p. 20).

Burke, R. (1999). Project Management: Planning and Control Techniques. Chichester: Wiley.

Cadle, J., & Yeates, D. (2001). Project Management for Information Systems, the 3rd Edition. Harlow: Prentice-Hall.

Chaffey, D., & Wood, S. (2004). Business Information Management: Improving Performance Using Information Systems. Essex: Prentice-Hall.

Dhillon, G., & Backhose, J. (2001). Current directions in IS security research: towards socio-organizational perspectives. Information Systems Journal, 127-153.

Dix, A., Finlay, J., Abowd, G., & Beale, R. (1998). Human-Computer Interaction. Hillsdale: Prentice-Hall.

Field, M., & Keller, L. (2007). Project Management. Thomson Learning.

Gray, C., & Larson, E. (2006). Project Management, The Managerial Process. New York: McGraw-Hill.

Helander, M., Landauer, T., & Prabhu, P. (1997). Handbook of Human-Computer Interaction. Amsterdam: Elsevier Science Pub Co.

Jawadekar, W. S. (2004). Software Engineering: Principles and Practice. New York: McGraw Hill.

Kerzner, H. (2006). Project management: A systems approach to planning, scheduling, and controlling. New Jersey: John Wiley & Sons.

Kietzman, S. (2009). What is Quality Assurance? Retrieved September 06, 2009, from WiseGeek: http://www.wisegeek.com/what-is-quality-assurance.htm

Laudon, K. C., & Laudon, J. P. (1999). Management Information Systems, Sixth Edition. New Jersey: Prentice-Hall.

Laudon, K. C., & Laudon, J. P. (2006). Management Information Systems: Managing the Digital Firm--9th Ed. New Jersey: Pearson.

Lewis, J. P. (2006). Fundamentals of Project Management. New York: AMACOM.

Lock, D. (1996). Project Management, 6th edition. New York: Wiley.

Lockyer, K., & Gordon, J. (1996). Project Management and Project Network Techniques, 6th edition. Harlow: Prentice-Hall.

Maylor, H. (2003). Project Management, 3rd edition. Harlow: Pearson Education.

Meredith, J., & Mantel. (2006). Project Management: A Managerial Approach, . Asia: John Wiley & Sons.

Monk, E., & Wagner, B. (2009). Concepts in Enterprise Resource Planning, 3rd.ed. Boston: Course Technology Cengage Learning.

Nagen N. Nagarur, T.-s. H. (1994). A Computer-based Inventory Management System for Spare Parts. Industrial Management & Data Systems, 22-28.

Pressman, R. S. (2001). Software Engineering: A Practitioner's Approach, 5th Edition. London: McGraw Hill.

Sage, P., Andrew, & & Palmer, J. D. (1990). Software Systems Engineering. New York: John Wiley & Sons.

Selic, B. (1999). UML-RT: A profile for modeling complex real-time architectures. New York: ObjecTime Limited.

Sock Hwa Chung, C. A. (2000). ERP adoption: a technological evolution approach. International Journal of Agile Management Systems, 1465-4652.

Sommerville, I. (2004). Software Engineering, 7th Edition, New York: Pearson Education (Addison Wesley).

Download full paperFile format: .doc, available for editing
Contact Us