|
Scenario:
There are two actors using the Moduel and
will switch UIs between Moduel C and MOdule B in ICU. One is physician and
another one is nurse.
Physician: ICU Patients are under extreme
health situation that means they need more duteous care services from physician.
So, a physician could not take care of more patients in his one day job. Assume
that a physician will take care of 30 patient a day (It seems a little
ridiculous but it is true in some China hospital). He/she will performs at least
60 UI switching between Patient List and Module plus 90 other operation which
also takes 90 UI switching. Totally 120 switches (30+90). And also assume there
is a factor with value of 5. We get a approximate number of 600 UI switch. If
physician's legal work time is 8 hours. That means he will perform at least one
time UI switching per minute. I am not sure whether it will make physician
exhaust or not if he keeps on staying before computer to switch UI once per
minutes. Thus the reasonable UI switching frequency is one time/3 minutes
averagely. And then we get the conclusion:
160 UI switching one
day.
Ttest scenario: 1 hour and 50 minutes to crash.
(6600 seconds). We could have 1320 switches in actual scenario. That means
system will go into crash 8.25 days later.
Because nurse will take no more than 3 patients in
ICU, then maybe 80 days later system will crash which could be acceptable by
customers because I think they will reboot computer at least one time due to
Windows' characteristic .
If so, maybe we need fix the issues
soon.
2. Action Plan (When
happen)
We are supposed to assign the mission to developers
who have abundant experience to resolve the issue and also have done some
research on that before the test report.
We need 3 weeks /2 manpower to do
that.
3. Resource leverage:
If the first build is not focusing on the issue, my
suggestion is that we could postpone the mission to sometime after M4 signoff
because we devote to Milestone. |