|
Task Completed
|
Onging Task
|
|
Project Schedule Document Sign off |
Requirements Gathering form rest homes not fully completed |
|
Project Briedf Document Sign off |
Start on the Functional Design Specification Document |
|
Project Schedule Presentation |
|
|
Contacted rest homes adn established relationship |
|
|
Identify critical/main processes |
|
Issues On April
1.Establishing RestHome Contacts
MedTech provided a few rest homes contacts, but for the others we had to call various rest homes around Auckland.
We introduced ourselves and enquired if they were interested in participationg in our project.This Process took a decent
amount of effort and time. We want to create more contacts so more information from a wider range of rest homes could
be gathered which will aid our design. The problem with this is time contraint.The information-gathering phase will be
ending and we will be starting on our Functional Design Specification Document soon.
2. Meeting with Rest Homes
Most of the rest homes are busy, they have other meetings and their flexibility in making
a meeting day and time with us is poor. The next available time they can meet us is normally one
or two weeks away from the day we ask them. Now this is compounded when we have several rest
homes to visit and having to visit each rest home several times to gain an in-depth
understanding of their core processes. In some cases, we cannot start other tasks without
the information we require from these rest homes. The only way of addressing this problem
is to do concurrently and to try scheduling as many meetings in a short space of time without
clashing with one another and to schedule meetings with the rest homes as early as possible.
3. Lack of Previous Document
There is very little documentation of REScare. This posed a substantial problem during our
analysis of the current software, but it will be a bigger during the Design phase. This is
because we are only improving certain aspects of the software and knowledge of the structure of the
software will be required if we want to implememt changes without affecting other aspects of the
software that we want to remain unchanged. There is no time to document the whole software.
To resolve this, we will have to document as much of the current software as we need. Even though
we are documenting only part of the software it will be a time consuming process that does not
directly help our objective of improving the software.
Monthly report for May.doc