Web-Based Application Accessibility Analysis

/in , , , /by

Web-Based Application Accessibility Analysis

(Web-Based Application Accessibility Analysis)

discussion using the web as a database contains unread posts

This week we learned how the web can be used as a database. We also learned how web applications can integrate with databases.

Summarize an application that your organization uses that is not currently on the web. What would be the advantages and disadvantages of accessing this application from the web? What steps can you take to determine whether the application could be available on the internet?

Also, discuss the security implications that would need to be reviewed and what type of database design would be needed to support it.

Refer to the Discussion Rubric for directions on completing these discussions.

 

Summary of Application Not Currently on the Web: One application that my organization uses, which is not currently available on the web, is an internal employee scheduling system. This system is currently hosted on a local server and is only accessible within the organization’s network. Employees and managers use it to view and create work schedules, track time-off requests, and manage shift assignments.

Advantages of Accessing This Application from the Web:

  1. Accessibility: By moving the application to the web, users could access it from any device with internet connectivity, whether they are in the office, working remotely, or traveling. This would make scheduling more flexible and efficient.
  2. Real-Time Updates: Web-based access would allow for real-time updates, so changes in the schedule would immediately reflect for all users. This would help minimize scheduling conflicts and ensure everyone is on the same page.
  3. Ease of Integration: A web-based system can easily integrate with other tools (e.g., payroll, HR systems) through APIs or web services, streamlining workflows.

Disadvantages of Accessing This Application from the Web:

  1. Security Risks: Exposing the application on the internet increases the risk of unauthorized access, hacking attempts, and data breaches, especially if sensitive employee information is stored in the system.
  2. Dependence on Internet Access: If the web-based system goes down or if there are connectivity issues, users might be unable to access the application, causing delays in scheduling.
  3. Complex Migration: Migrating the application from a local server to a web-based system can be technically challenging, requiring changes in architecture, software development, and testing.

Steps to Determine if the Application Could Be Available on the Internet:

  1. Assess the Current Architecture: Evaluate the current system’s technology stack to determine if it can be easily adapted to work in a web environment. This includes examining the programming languages, database, and server architecture used.
  2. Consult with IT and Development Teams: Discuss with the organization’s IT and development teams to understand the technical feasibility of creating a web-based version of the application, including possible costs, required time, and resources.
  3. Evaluate User Requirements: Understand if there are specific features or functionality needed for the web version. This would include considerations for mobile accessibility and cross-platform compatibility.
  4. Research Hosting Options: Determine the hosting environment (cloud or on-premises) that would best support the application once it is available online.

Security Implications:

  1. Authentication and Authorization: Ensuring strong user authentication (e.g., multi-factor authentication) is critical to prevent unauthorized access. Role-based access controls should be implemented to ensure only authorized personnel can make changes to sensitive data, such as employee schedules and personal information.
  2. Encryption: Data should be encrypted both in transit (using SSL/TLS) and at rest to protect sensitive information, such as employee names, schedules, and personal contact details.
  3. Backup and Disaster Recovery: Regular backups and a clear disaster recovery plan should be implemented to prevent data loss in case of a system failure or cyberattack.
  4. Audit Logs: The system should maintain detailed audit logs that track user activity, such as login attempts and changes to schedules, to help identify and respond to security incidents quickly.

Database Design: To support a web-based scheduling application, the database design needs to be scalable, secure, and efficient. Key considerations would include:

  1. Relational Database: A relational database (e.g., MySQL, PostgreSQL) could be used to store data on employees, schedules, and shift assignments. Proper normalization should be implemented to reduce redundancy and ensure data consistency.
  2. User Management Tables: Separate tables for user authentication (e.g., user login credentials) and authorization (e.g., roles and permissions) would be required to manage who can access and modify the system.
  3. Indexing and Performance Optimization: Indexes should be created on frequently queried fields, such as employee IDs or schedule dates, to improve performance. The database should also be designed to handle a large number of concurrent users efficiently.
 
Do you need a similar assignment done for you from scratch? Order now!
Use Discount Code "Newclient" for a 15% Discount!