Skip to content

Assignment 3

lsancer99 edited this page Mar 26, 2023 · 32 revisions

Root Cause Analysis

Analysis 1: Lack of Emergency Wait Time Support

Our previous proposed solution was only supporting the displaying of wait times for non-emergency services and the number of people that are waiting in queue at hospitals. Our clients requested to display the wait times for emergency services as well in our system. The cause of this request change was to provide more information to the patients who requires urgent care. Once we added this feature to our system, we were able to provide more information about the estimated time for patients who needed emergency.

Analysis 2: Not Enough Features

Our clients wanted to display the wait times for emergency services in our system, and the cause of this request was to our application was not offering lots of features for the users. Displaying the wait times for emergency services feature to our application, increased the functionality of our application.

Analysis 3: No Mobile Functionality

Our clients requested to make the website compatible with mobile devices, and the cause of this request was many of the users were not able to use our application through their mobile devices. We are currently modifying the existing application to make it compatible for mobile devices as well, and once it is done, we believe that the effects will increase accessibility for our users, and provide a better user experience.

Analysis 4: Unfriendly Mobile UI

With regards to our clients' requests to make our program compatible with mobile devices, one of the problems that can be explored is in our program's unfriendliness for a mobile user interface. The fishbone diagram below explores some causes for the lack of mobile support. Fishbone Diagram 1 for Analysis 4 Our lack of mobile experience can be resolved relatively simply by going through tutorials and reading on documentation online. While desktop computers have more capabilities compared to mobile devices, it is untrue that mobile devices do not have the capability to run a website such as ours. It is also untrue that this requirement was unconsidered because it was a possibility that we thought about while forming our earlier documents. The identified cause of the problem lies in our lack of created and presented UI design of our program for mobile devices. This lack of UI for mobile is explored even further in the second fishbone diagram below. Fishbone Diagram 2 for Analysis 4 While our UI Design was built around desktop computers and a direct translation of the current UI might be difficult to port to mobile, there is most likely a way to design the UI such that it suits mobile devices. Similarly above, any gap of knowledge regarding the design of mobile UI can be filled in through online resources. As for demand regarding mobile, there is clearly interest for mobile support as it was a change that was requested in the first place. Therefore, the reason of a lack of UI design for mobile devices can be pinpointed as the difficulty in designing, testing, and implementing such functionality within the given time and current scope of the project.

Goal Quality Metric (GQM)

GQM 1:

Define Goal:

We want to define the goal in terms of accommodating clients' request about adding the feature to display wait times for emergency services in your system. The client and developers should be involved and probed for their thoughts, but also the instructional team should be consulted for advice regarding the issue as well.

Therefore, the goal can be described as follows:

"Analyze the project scope to identify whether or not there is enough time to include this display of emergence queue in our system from the viewpoint of developers. clients, and the instructional team in the context of the course's time and scope constraints."

Quantify Goal with a Question:

When asking questions to tackle this goal, each perspective should be considered: the course (and instructional team), the developers, and the clients. It is also essential to consider which aspects of the goal are associated with each perspective: the time left in the course, the development time, and the client demand.

Therefore, the questions can be defined as follows:

  • What was the impact of adding the feature to display wait times for emergency services in addition to non-emergency services and queue length in hospitals?
  • Did this change improve the system's ability to provide more accurate and helpful information to patients who require urgent care?
  • Did this change expand the system's capabilities beyond non-emergency services and hospital queue length?

Metric:

When deciding the metrics to determine which data needs to be gathered, it is essential to ask how each question can be answered with a quantity. The course length must be considered concerning the due date of the project's last milestone, the semester's end date, and the date of when the instructional team is willing to accept submissions. In terms of development time, it can be measured with man-hours, and the developers can be asked about how long they think it will take to implement. Client demand is a bit tricky to quantify. Still, they can be surveyed using a survey to gauge their interest in the effectiveness of this change in providing more accurate and helpful information to patients who require urgent care and expanding the system's capabilities.

The metrics to provide possible answers are:

  • Number of customer support requests received per day/week/month.
  • Average time is taken to resolve customer support requests.
  • Customer satisfaction ratings based on feedback surveys.
  • Number of unresolved customer support requests.
  • Number of unresolved customer support requests.

Overall, the GQM for the RCA on lack of Emergency Wait Time Support can be summarized as follows. GQM for Lack of Emergency Wait Time Support

GQM 2:

Define Goal:

We want to define the goal by providing a wait time estimate to help users make informed decisions in emergencies. The client and developers should be involved and probed for their thoughts, but also the instructional team should be consulted for advice regarding the issue as well.

Therefore, the goal can be described as follows:

"Analyze the project scope to identify whether or not there is enough time to include this, providing an estimate time of emergence queue in our system from the viewpoint of developers. clients, and the instructional team in the context of the course's time and scope constraints."

Quantify Goal with a Question:

When asking questions to tackle this goal, each perspective should be considered: the course (and instructional team), the developers, and the clients. It is also essential to consider which aspects of the goal are associated with each perspective: the time left in the course, the development time, and the client demand.

Therefore, the questions can be defined as follows:

  • What was the impact of adding the feature to display wait times for emergency services in addition to non-emergency services and queue length in hospitals?
  • How will implementing these features increase the functionality of our application?
  • What benefits will our clients and our business gain from these additional features?

Metric:

When deciding the metrics to determine which data needs to be gathered, it is essential to ask how each question can be answered with a quantity. The course length must be considered concerning the due date of the project's last milestone, the semester's end date, and the date the instructional team is willing to accept submissions. In terms of development time, it can be measured with man-hours, and the developers can be asked about how long they think it will take to implement. Client demand is a bit tricky to quantify. Still, they can be surveyed using a survey to gauge their interest in providing a comprehensive system that displays both the emergence and non-emergency wait time, expanding the system's capabilities.

The metrics to provide possible answers are: *Number of feature requests made by clients

  • Days left in terms of date to the last milestone submission
  • Man-hours for programming the implementation
  • User satisfaction.
  • Revenue

Overall, the GQM for the RCA on Not Enough Features can be summarized as follows. GQM for Lack of Emergency Wait Time Support

GQM 3:

To-do...

GQM 4: Unfriendly Mobile UI

Define Goal:

We want to define the goal in terms of determining if mobile support is viable with respect to the time needed for such an implementation and and the time left in the course. The client and developers should be involved and probed for their thoughts, but also the instructional team should be consulted for advice regarding the issue as well.

Therefore, the goal can be described as follows:

"Analyze the scope of the project to identify whether or not there is enough time to design, test, and implement mobile support from the viewpoint of developers, clients, and the instructional team in the context of course's time and scope constraints."

Quantify Goal with a Question:

When asking questions to tackle this goal, each perspective should be considered: the course (and instructional team), the developers, and the clients. It is also important to consider which aspects of the goal is associated to each perspective: the time left in the course, the development time, and the client demand.

Therefore, the questions can be defined as follows:

  • How much time do we have left in the course?
  • How long would it take for the developers to learn and implement a mobile UI for their program?
  • How much client demand is there for this functionality?

Metric:

When deciding the metrics to determine which data needs to be gathered, it is important to ask how each question can be answered with a quantity. The course length must be considered with respect to the due date of the project's last milestone, the semester's end date, and the date of when the instructional team is willing to accept submissions. In terms of development time, it can be measured with man-hours and the developers can be asked about their experiences with mobile development and how long they think it will take to implement. Client demand is a bit tricky to quantify but they can perhaps be surveyed using a Likert scale to gauge their interest in mobile support.

Therefore, the metrics to provide possible answers are:

  • How much time do we have left in the course?
    • Days left in terms of the date of the last milestone submission
    • The semester's end date
    • The instructional team's date for accepting submissions
  • How long would it take for the developers to learn and implement a mobile UI for their program?
    • Hours to design a mobile UI
    • Hours to learn mobile development
    • Man-hours for programming the implementation
  • How much client demand is there for this functionality?
    • Survey scores for functionality demand from the client
    • Survey scores for UI preferences
    • Researching current systems and seeing the amount of demand and/or praise for mobile support

Overall, the GQM for the RCA on Unfriendly Mobile UI can be summarized with the following: GQM for Unfriendly Mobile UI

Implement a Fully Functional App

Clone this wiki locally