Case Study 3: Security CIS 524 – Computer Interaction And De

Case Study 3: Security CIS 524 – Computer Interaction and Design

Analyze the new system and determine the design issues with this new system.

Describe how you would correct the design issues with the system to make the restaurant managers happy.

Create a design plan that: 1. Lists and explains the tasks associated with improving this interface. 2. Contains at least six (6) tasks. 3. Includes realistic time estimates for each task to be completed. 4. Analyzes the development of the system in your plan. 5. Analyzes the testing of the system in your plan. 6. Analyzes the implementation of the system in your plan.

Examine how this system balanced security and usability, and explain the challenges of incorporating system security and system usability into a design.

Suggest changes that could be made to the security of this system to still meet security objectives but make the system more usable.

Use Microsoft Visio or an open source alternative, Dia, to create a graphical representation of your proposed interface.

Paper For Above instruction

In the rapidly evolving landscape of retail and hospitality technology, the deployment of secure yet user-friendly interfaces remains paramount. The recent introduction of a touchscreen cash register system at a major fast-food chain was intended to streamline operations and enhance security. However, the initial implementation revealed significant design flaws that compromised both usability and security. Analyzing these issues and proposing a comprehensive redesign is essential to optimize performance, satisfy managerial expectations, and ensure system integrity.

Analysis of System and Identification of Design Issues

The implemented system incorporated several security measures, including user IDs and passwords for cashier login, automatic lockout after multiple failed login attempts, and automatic screen locking after a period of inactivity. Despite these features, the system's design presented multiple challenges that hindered daily operations. Notably, the need for cashiers to remember complex passwords caused frequent forgotten credentials, leading to other cashiers logging in for them—a practice that compromises security and accountability. The button layout for password entry was prone to user errors, resulting in incorrect entries and lockouts, which further delayed transactions.

The system's reliance on static passwords and physical tokens such as key cards introduced vulnerabilities and inefficiencies. For instance, if a cashier left the system unlocked unintentionally, the only recourse was a system reboot, a process that could take three to five minutes, disrupting workflow and increasing customer wait times. Additionally, grease accumulation on touchscreens diminished responsiveness, compounding usability issues. The environmental factors—grease, dust, and fingerprints—detracted from interface clarity and efficiency.

Proposed Corrections to System Design

Addressing these issues requires a user-centric approach that balances security with usability. A primary correction involves replacing static passwords with proximity or magnetic swipe cards to authenticate users. This transition eliminates the need for cashiers to memorize passwords, reduces login errors, and streamlines the login process. Implementing smart cards or RFID badges enhances swift access and minimizes physical contact with terminal surfaces, directly countering environmental factors affecting touchscreens.

Secondly, reevaluating the lockout and timeout policies is crucial. Extending automatic logout time from three to five or eight minutes provides greater flexibility, reducing frequent resign-ins and restarting workflows. Introducing a "force unlock" feature accessible by designated power users or managers via secure credentials allows authorized personnel to unlock and reset login statuses swiftly, without necessitating full system reboots, thus maintaining operational continuity.

Thirdly, touchscreen sanitation and maintenance protocols are vital. Regular cleaning schedules, use of screen protectors, and anti-fingerprint coatings can mitigate responsiveness issues. While environmental cleaning cannot be entirely eliminated, establishing routine maintenance procedures will preserve interface integrity and user satisfaction.

Implementing these corrections demands synchronizing hardware upgrades with software modifications. Clear, consistent training for staff on new procedures and the importance of security protocols further ensures adoption and compliance. Such reengineering efforts will likely encompass a phased rollout, allowing feedback collection and iterative improvements.

Design Plan for Interface Improvements

1. Stakeholder Feedback Collection: Conduct surveys and interviews with cashiers and managers over a two-week period to gather insights about usability issues and safety concerns. Data from system logs will complement subjective feedback.
2. Resource and Requirements Gathering: Hold stakeholder meetings to define project scope, team roles, budget, and timeline within one day. Collect hardware specifications, security standards, and training needs.
3. Research and Prototype Development: Allocate ten days for resource consumption analysis and design exploration. Create multiple interface prototypes featuring swipe card authentication, redesigned button layout, and streamlined workflows. Develop and test these prototypes over twelve days, focusing on minimizing input errors and reducing lockout procedures.
4. System Implementation: Deploy the approved prototype into the operational environment within three days. This includes installing hardware, configuring authentication systems, and integrating the new interface with existing infrastructure.
5. Monitoring and Control: Monitor system performance, user interaction, and security logs for ten days post-implementation. Address unforeseen issues promptly and refine features as necessary.
6. System Testing and Validation: Conduct functional and usability testing for two days to ensure compliance with specifications, security standards, and user satisfaction.
7. Final Training and Handover: Over two days, train staff on the new system protocols, security practices, and troubleshooting procedures. Document best practices and provide user manuals.

Development, Testing, and Implementation Analysis

The development phase focuses on creating a user-friendly authentication mechanism that maintains robust security. This involves hardware integration of RFID or magnetic stripe card readers, along with software updates for login processes. The testing phase assesses efficiency gains, error reduction, and system resilience under typical operational conditions. It verifies that increased timeout intervals do not compromise security while enhancing usability.

The implementation emphasizes phased deployment, allowing staff adaptation and feedback incorporation. Continuous monitoring ensures that security protocols are enforced without obstructing workflow. The success of this phase relies on comprehensive training to ensure staff competence and confidence with the new system features.

Balancing Security and Usability: Challenges and Insights

Designing systems that harmonize security with usability remains a complex challenge. Enhanced security measures, such as password complexity and lockouts, often hinder ease of access, frustrating users and potentially leading to risky workarounds. Conversely, overly simplified interfaces or relaxed security protocols expose vulnerabilities. Woods (2013) underscores that security without usability leads to failures, emphasizing the importance of incremental security enhancements aligned with user workflows. Achieving this equilibrium involves iterative testing, user feedback, and appropriate technological solutions that maintain a seamless user experience without compromising security.

Recommended System Security Enhancements for Better Usability

Transitioning from static passwords to hardware tokens or RFID badges significantly improves usability by reducing cognitive load on cashiers. Extending inactivity logout times, combined with a "force unlock" feature for authorized personnel, balances operational efficiency with security oversight. Regular electronic audits and logs will help monitor access patterns and detect anomalies without impeding daily operations.

Employing biometric authentication, such as fingerprint or facial recognition, presents future opportunities for enhanced security with minimal inconvenience. Furthermore, instituting routine touchscreen cleaning and maintenance protocols will sustain interface responsiveness, indirectly fostering higher user satisfaction and system reliability.

Graphical Representation of the Proposed Interface

(Note: A diagram would be created using Microsoft Visio or Dia, illustrating the new login screen featuring RFID badge authentication, a streamlined keypad with designed error reduction features, and a control panel for managers to unlock or reset sessions efficiently. Due to the text format, the visual diagram is not included here but should be integrated into the final submitted document.)

Conclusion

Integrating security with usability in retail systems necessitates a nuanced approach that considers user behavior, environmental factors, and technological capabilities. The initial flaws of the cash register system, driven by password-based authentication and rigid lockout policies, underscored the need for a revision emphasizing server hardware tokens, flexible timeout settings, and environmental maintenance. These refinements not only enhance operational efficiency but also reinforce security standards. A balanced, user-centered design fosters an environment of trust, accountability, and productivity, ultimately contributing to the franchise's success in a competitive market.

References

• Microsoft. (2016). Clean and care for your Surface. Retrieved from https://support.microsoft.com
• Perrin, C. (2008). Interface design is security design. TechRepublic. Retrieved from https://www.techrepublic.com
• Vogt, T. (n.d.). User Interface vs. Security. Lemuria. Retrieved November 2016, from https://www.lemuria.com
• Woods, D. (2013). Why security without usability leads to failure. Forbes. Retrieved from https://www.forbes.com
• Gartner. (2015). User authentication best practices. Gartner Research.
• ISO/IEC 27001. (2013). Information Security Management Systems standard.
• Microsoft Docs. (2018). Implementing secure sign-in methods. Microsoft Documentation.
• Kim, D. (2017). Human factors in security system design. Journal of Security Studies, 29(3), 45-59.
• Johnson, P., & Smith, R. (2019). Human-computer interaction principles for system design. HCI Journal, 34(2), 123-135.
• Zeigler, R. (2012). Environmental considerations in HCI system maintenance. International Journal of Human-Computer Interaction, 28(1), 75-89.