Docstoc

Use Case Diagrams

Document Sample
Use Case Diagrams Powered By Docstoc
					 Project Definition Document

“A PDA based Management system for Diabetics”

        Group: Karl Linnane, Daniel Fay
               4th BSC IT
PDA-based Management System for Diabetics


Table of contents


1. Document Description                                                2
2. Aims and Objectives                                                 2
   2.1 Project Goal                                                    2
   2.2 Project Scope                                                   2
   2.3 Project Objectives                                              4
   2.4 Project Deadlines                                               4
3. Project Requirements                                                5
   3.1 User Requirements                                               5
   3.2 Doctor’s Requirements                                           5
4. Project Management                                                  7
   4.1 Work Breakdown Structure                                        7
   4.2 Use Case Diagrams                                               8
   4.3 Use Case Descriptions                                           9
   4.4 Gantt Chart                                                     10
   4.5 Roles and Responsibilities                                      11
   4.6 Risk Analysis                                                   13
   4.7 Risk Management                                                 14
5. Technology Options                                                  17
   5.1 Software Explore d                                              17
   5.2 Hardware Explored                                               20
6. References                                                          23




                                     2      Written By: Daniel Fay 4thBSC IT
                                                     Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


Document Description:
This Project Definition Document is for the B.Sc. IT Final Year Project entitled
“PDA based Management System for Diabetics”. This document sets out the Aims
and Objectives of the project, its functionality, the Use Case design proposal, the
available technologies, the required department resources and Project management
which explores the possible risks to the project and preventative measures we will
take to minimize their effects.



Aims and Objectives:

Project Goal:
The goal of this project is to:
“Design and develop a PDA based application that supports diabetics to manage
their dietary habits. A spreadsheet-like GUI will be developed to accommodate a user
to enter relevant data like medication intake, blood sugar levels, carbohydrate units
etc, and to keep track of these parameters. A PC-based data backup and patient
management application will be implemented as well as a simple statistics and data
visualisation package. ”

Project Scope:
There are various functions that the system will include to help diabetics manage their
diabetes easier and with more accuracy. One of the main result preferences of this
project would be to replace the traditional paper logbook procedures used by the
majority of diabetic patients today with this new PDA Management System.
       The PDA will include a spreadsheet-like GUI that will allow the user to record
        glucose measurements, insulin intake and other notes.
       The PDA will include a database which will be used to store the information
        entered by the user. Information may also be retrieved from this database,
        where the user may wish to query past results. A GUI interface will be
        prepared to allow the user to carry out such tasks.
       The project will include a PC-based data backup system available for both
        patient and doctor and a patient management application for use by the doctor
        in analysing the patient‟s results from their PDA. This management

                                            3    Written By: Daniel Fay 4thBSC IT
                                                          Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


       application will allow the doctor to manage his/her diabetic patient‟s records
       and query their results. Using the Microsoft ActiveSync 3.8 software (already
       installed on the PDA), the patient and doctor will be allowed to transfer the
       data to their PC data backup application for further analysis and better
       visualisation of the data.
      The PDA itself will include interactive charts and diagrams that will be
       created based on the patient‟s queried records. To facilitate this, the project
       will also include a data visualisation application for the doctor‟s desktop. Any
       graph created will automatically have set levels clearly shown on them i.e. a
       yellow range showing where the patient‟s blood sugar level was too low, a
       green range showing where the patient‟s blood sugar level was in the
       acceptable range, and a red range showing where the patient‟s blood sugar
       level was too high. This will help doctors to see trends in the patient‟s blood
       sugar levels. The main reason for this feature is to improve the doc tor‟s/GP‟s
       analysing and viewing of the patient‟s results.
      The PDA will also contain a simple food database that will store the
       carbohydrate, calories, fat, protein, sugar content and fibre of common foods.


   Despite all of the functions the PDA will perform, there are a number of functions
   the system will not include.
      The PDA will not read data from blood glucose meters.
      The system will not include an email wizard which would allow the user to
       send their data to their doctor or diabetic nurse via e- mails.
      The system will not include automated sending of SMS messages from the
       patient‟s PDA to his/her doctor if a critical blood glucose level is detected.
      Training will not be provided to the patient or doctor by the system
       developers, but could be considered an option in the future. Another future
       consideration would be to develop a special GUI for users who may not be
       very experienced working with technology devices. It is assumed here that the
       patient has a bit of experience with using technology devices e.g. mobile
       phone.




                                            4    Written By: Daniel Fay 4thBSC IT
                                                          Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


Project Objectives:
      The main objective of this project is to design, develop and complete a PDA
       management system for diabetics that will make the control of diabetes easier.
      To complete and deliver all project deliverables before their deadline dates.
      To meet the project requirements specified by ourselves and the supervisor by
       tracing back to this document.
      To improve the levels of consultations between patient and doctor by
       providing a PC based data backup application that will allow the doctor to
       store information from the patients PDA onto his/her desktop. This way a
       better analysis can be achieved by the doctor through the help of graphical
       representations of the patient‟s records.


Project Deadlines:
      Project Definition Document:                    Due Date: 28th October 2005
       This report outlines a description of the project, the project aims and
       objectives to be achieved, the technologies explored and the risks that may
       affect the completion of the project as well as strategies to prevent them from
       occurring.


      Web Page Summarising Project:                   Due Date: 11th November 2005
       This is basically a web page that will contain up to date information on our
       project for interested parties. It will be accessible as a link from the main
       Department website.


      Final Project Report:                           Due Date: 24th March 2006
       The final report will be a detailed and comprehensive report of all aspects of
       the project including the research, design, implementation and testing phases,
       as well as problems encountered, reasoning on software selections etc.




      Project bench Demonstration:                    Due Date: 27th March 2006




                                            5      Written By: Daniel Fay 4thBSC IT
                                                            Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


       Involves demonstrating the system from the user point of view, displaying all
       features and functionality of the PDA to a number of board members who will
       critique the project and its functionality.
      Project Viva Voce:                                Due Date: 3rd April 2006
       Once the project is completed, both group members enter the viva voce, where
       both members will be questioned and tested on their knowledge and
       understanding of the Project.




Project Requirements:
User Requirements:
There are various requirements that the Project must meet. Since there are two users
of the system, these requirements can be split into the requirements of the user
(diabetic) and the requirements of the medical staff (GP \Diabetic nurse). However,
there are some requirements that will apply to both users.
      The patient will require a login GUI. For this process, the patient will require a
       password to login to their PDA application.
      The patient will require a spreadsheet like GUI on their PDA application that
       will allow them to enter their dietary habits and save them to a database.
      Both users will require a data visualisation package that will allow them to
       create graphs and store them. They will also be allowed to view these graphs.
      In order to have a backup of this information, the patient will require a data
       backup system that will allow him/her to upload the data from their PDA onto
       their desktop for storage and in order to free memory on their PDA.
      The patient will also be given the option to logout of the PDA application.




Doctor’s Requirements:
The other side of this project is to develop a patient management application that the
diabetic doctor/nurse will use to manage his/her diabetic patient‟s records.
      The doctor will require a password to login to his/her patient management
       application on his/her desktop.


                                            6        Written By: Daniel Fay 4thBSC IT
                                                              Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


      Again the doctor will require an option to be able to select the patient‟s
       records he/she wants to view. Once the patient is selected, the doctor will be
       given the option to view the patient‟s past records, enter new data on the
       patient‟s record and save it, print reports, or view trends in the patient‟s blood
       glucose levels via graphs.
      The doctor will also require an option to add a new diabetic patient to his/her
       application or remove an existing diabetic patient from his/her application.
      In order to store the patient‟s blood glucose levels, the doctor will be given the
       option to download this information from the diabetic‟s PDA onto his/her
       patient management application.
      Again the doctor will require the option to logout of the patient management
       application.


It is assumed that both patient and doctor have a bit of experience at working with
technology devices and will not require training in using the applications.




                                            7    Written By: Daniel Fay 4thBSC IT
                                                          Karl Linnane 4thBSC IT
             PDA-based Management System for Diabetics



             Project Management:
             Work Breakdown System:
                                        PDA Diabetic Management system



                                                                           Design                         Implement
      Research          Project                                                                           System
                                                                           System
                        Plan

                                               PDA APP                              PC APP

Research
PDA                                     Database          GUI                       Database      GUI
Research
Diabetes
Research
Software                                                 Spreadsheet                            Spreadsheet

Research
existing                                                                                       Execute
systems                                                                                        Code



                        PDD                    Draw                                  GUI Code            SQL Code
                        Document               Tables



                                               Select
                                               Queries                      Test Code                         Test Code




                                                                            Write Code                        Write Code
    W.B.S        Req.Spec      ID Fun      ID Non-
                 Document
                               Req.        Fun Req.

           Use Case     ID             ID
           Diagram      Goal           Scope
                 ID            ID
                 Stakeholder
                               Users




                                                                8      Written By: Daniel Fay 4thBSC IT
                                                                                Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics



Use Case Diagrams:



                                      Log -IN
     PDA SYSTEM



                                    Enter Data

                            <<i nclude >>

                                    Save Data


                                    Vi ew Data

                                                          Add Notes
                                                                            Medical Staff
            Patie nt             Compose Graphs
                             <<i nclude >>

                                    Save Graphs

                                Upl oad to PC Backup



                                       Log Out

   PC BACK UP
   SYSTEM

                                       Log -IN


                                  Browse Data Hi story

                                                        Add Patie nt

                                                        Remove Patient

                             Vi ew Patient Information                             Medical
         Patie nt
                                                                                   Staff
                                   Enter New Data
                               <<i nclude >>                Print reports
                                        Save Data


                                        Vi ew Graphs

                                       Download to PDA




                                            Log Off


FIG 1.




                                             9        Written By: Daniel Fay 4thBSC IT
                                                               Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics



Use Case Descriptions (FIG 1):

We have decided to illustrate two use case diagrams to show the process that the
actors will have with the system. They have been labelled „PDA System‟ and „PC
Back-Up System‟ to make it to understand.

PDA System:

The patient will be interacting with the PDA as well as the medical staff and will
share some common functions that can be carried out. After logging in and starting
the application, the user will be able to enter, save and manipulate data so that they
graph their results for their own use. The medical staff will also have these functions
as well as extra visualisation capabilities and also can add notes for the patients use.
The upload function to the PC will be available for both the doctor‟s pc as well as a
patient‟s home pc, if applicable.

PC Back-Up System:

We have decided that the user will only use their home pc system for data storage so
as to keep records or history of their previous results which they can browse if
required. As regards the medical staff, they will be operating a patient management
system to which it will contain data from a range of diabetic patients. They will have
a lot of extra functionality, to allow them to search through patients, retrieving records
and data history, adding or removing patients and data visualisations. Information can
be downloaded to the PDA for the user and also reports can be printed out at the
office. Hopefully it will be similar to existing medical PC-based applications and easy
to use and integrate with the user.




                                           10    Written By: Daniel Fay 4thBSC IT
                                                          Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics




GANTT CHART:




This Gantt Chart shows a brief outline of the timeline of development of the project. It
is subject to change as we proceed through the project.




                                          11    Written By: Daniel Fay 4thBSC IT
                                                         Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics




Roles And Responsibilities:
The following table outlines different components of the Work Breakdown Structure
and who will be responsible for each section in order to complete the project.
Considering that there are only two team members, each task will be a shared
responsibility.

Roles And              Description of Task                                 Team
Responsibilities                                                           Member
1.2                    This will involve getting a clear picture of the          Both
Project Plan           exact outcome we want the project to achieve.
                       It will involve completing an intensive PDD
                       document which will outline the scope and
                       definition of the project.
1.2.1                  This document will describe what the objective            Both
Completing the         of the project will be and the areas that need to
Project Definition     be examined in order to achieve this. This will
Document               contain the WBS, Requirements Spec., use
                       case diagrams, scope descriptions as well as
                       functional and non- functional requirements
                       and aims and objectives.
1.3                    This is the actual design aspect of the                   Both
Design System          applications required for this system. The PDA
                       and PC applications. Assembling these areas
                       together will result in meeting our project
                       goals.
1.3.1                  It will include design of required databases,             Both
PDA Application        spreadsheets and GUI environments which will
                       set the boundaries on what the user can do with
                       the PDA.



1.3.2                  It will include design of required databases,             Both
PC Management          spreadsheets and GUI environments which will


                                           12       Written By: Daniel Fay 4thBSC IT
                                                             Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


Application            set the boundaries on what the users can do
                       with the PC. This will be implemented as a
                       back-up system and a patient management
                       system for doctors to store multiple patient
                       records.


1.4                    The system will be implemented once all code           Both
Implement System       is written and tested and when the design
                       phases of the PDA and PC Applications has
                       been completed.


1.4.1                  The GUI and SQL code will be done in tandem            Both
Execute Code           with the design phase and will be examined
                       and tested before being executed.




Above is a broad overview of the roles and responsibilities that must be considered
when carrying out the project. The research task will be an ongoing task as the project
progresses. We hope to learn as much as we can about the technology as we continue
to develop our Final Year Project and hopefully the continuous research will allow for
learning and a successful result. Some of the tasks have been broken down into
subtasks which have to be completed prior to the main tasks. The idea being, once the
major task has been completed, it will result in a working system and completing our
final year project.




                                          13    Written By: Daniel Fay 4thBSC IT
                                                         Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


Risk analysis:



No. Risk Area                                   Potential          Probability of
                                                Impact             occurrence
1    Error in choosing development              Critical           30%
     environment.

2    Other college work pressures               Critical           50%

3    Developers unable to meet                  Critical           30%
     requirements

4    College Systems failure                    Catastrophic       15%

5    Time spent on extra functionality          Minimal            20%

6    Communication failure between group        Minimal            5%
     members

7    Team members new to technology,            Minimal            30%
     takes time to get acquainted

8    Requirement overlooked                     Serious            20%

9    Database tables not designed correctly     Serious            20%

10   Code not tested fully                      Serious            10%

11   Error in choosing PDA device               Critical           30%

12   Notification of add-ons late on in         Serious            30%
     project time cycle
13   Project Failure at demo stage              Serious            5%




                                          14   Written By: Daniel Fay 4thBSC IT
                                                        Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


Risk Management Plan:


The above table is a listing of some possible risks that could be encountered during
project development. Included are the resultant potential impact and the probability of
occurrence of these risks. We will just briefly describe these risks and what can be
done to limit their impact on the project should they occur.


   1. Error in Choosing Development Environment:
It is vital that we settled on a development environment and a suitable programming
language at the early stages of the project plan. Any previous work carried out will
have been made redundant and time will be lost reworking the previous tasks. If it is
to occur, the earlier we find out the better, giving us more time to rectify the situation.


   2. Other College Work Pressures:
Due to other assignments and exam preparation, time, which would have been spent
on the Final Year Project, is lost. This could lead to missing deadlines or requirements
of the project to be omitted. If we can monitor the project effectively and implement a
time management system to help us consider the other college work, this problem can
be limited.


   3.   Developers unable to meet requirements:
If it were a case, that we were not able to meet the requirements of the project, for
whatever reasons (software, hardware, coding prob lems), it would mean that our Final
Year Project would not be successfully completed, resulting in a penalty. We both
agree that due to the timeframe set and educational tools at our disposal, this should
not be too much of a problem.


   4. College Systems Failure:
This would entirely depend on when this could occur. If it occurred during the later
stages of the project, then all previous work will be lost and extensions would have to
be applied for. If it occurred during the early stages, there should be enough time to
recoup our losses. To combat this, saving information on alternative sources




                                            15    Written By: Daniel Fay 4thBSC IT
                                                           Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


frequently would help to alleviate the problem. At least there will be one or two
copies made of work done.


   5. Time Spent on Extra Functionality:
If we were to take on extra functionality, it could result in missing deadlines and
ultimately an unsuccessful project. Any extra functionality would have to be
considered at an early stage and determined if the timescale allows for it. If it cannot
be accommodated for whatever reason, it will not be considered.


    6. Communication Failure between Group Members:
If there is a communication breakdown between the team members, this could have
dire consequences on the outcome of the project. A clear goal agreed upon by each
member will take the whole group in the one direction and hopefully to a successful
conclusion. Monitoring of this, through meetings and discussion, will help to
minimise the chances of communication breakdown occurring.


   7. Team members new to technology, takes time to get acquainted:
As the technology is new to us it will take some time to get used to working with the
software/hardware. Taking too long to get acquainted could have an impact on the
submission of requirements and project deadlines. We will try to familiarize ourselves
with the new technology beforehand in order to put us in a position to learn more as
we proceed.


   8. Requirement overlooked:
When working with our project it could be possible to overlook essential
requirements. Depending on the time at which this error is detected, the results could
be disastrous. Time will have to be taken out of the project to rectify the error and
rework the requirement into the project. This will result in lost development time and
could end up stalling the project indefinitely. With careful monitoring and weekly
discussions between group members, measures can be taken to make sure that this
won‟t occur.




                                           16    Written By: Daniel Fay 4thBSC IT
                                                          Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


   9. Database tables not designed correctly:
If the database tables are not designed correctly then the implementation of the system
will suffer, as they play an integral role in the system‟s operations. This will mean
taking attention from other areas of the project in order to rectify the situation, hence
falling behind overall. We will need to constantly check that we are following the
development plan and that any new developments are implemented immediately. This
will include intensive testing of the databases and revealing and rectifying problems
as soon as possible.


   10. Code not tested fully:
Code may not get tested efficiently enough before implementation or earlier untested
code could cause errors in larger code blocks. The result could be malfunctioning
applications leading to project failure. Code will be tested frequently as it is being
composed so as to eliminate any potential errors that might occur at a later stage.


   11. Error in choosing a PDA Device:
There are so many PDA devices on the market but there are also compatibility issues
between them and any new software to be implemented. If we discover that the PDA
we have chosen does not support the applications being designed it will certainly
result in failure. Research will be carried out to explore the different options available
and checks can be made to guarantee that the PDA we choose will support the
software that we are devising.


   12. Notification of add-ons late on in project time cycle:
It could happen that the project requirements could change due to new ideas or the
need to update functionality. A review of what has been done might result in changes
to previous work carried out and result in reworking of some elements. This will
affect the schedule and could result in deadlines being missed and possible project
failure. It is up to the team and the supervisor to ensure that all requirements are
decided upon during the early stages of project development so that this issue will not
occur and the project will not be interrupted.




                                            17    Written By: Daniel Fay 4thBSC IT
                                                           Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


   13. Project Failure at Demo Stage:
This would be the ultimate disaster. If for some reason the system failed to work
during the demonstration, there is not a lot that can be done. Perhaps, another demo
opportunity can be applied for no later than needs be. It cannot be stressed enough
that the entire team will have to be in synch throughout the project and thorough
testing is implemented at each stage.


Above are some of the main risks that can occur while the project is being undertaken.
The consequences are different for some but identical in all. Project failure could
result in all if they are not managed efficiently throughout the lifecycle of the project.
We will adopt a risk management strategy as well as effective risk response control in
order to combat the aforementioned possible scenarios.


Technology Options:

Software Explored:
There are various different software options that we have explored that we can use to
develop our final year project. Below is an overview of each of them.
      MS Visual Studio.NET: Visual Studio .NET 2003 is the comprehensive tool
       for rapidly building Microsoft .NET–connected applications for Microsoft
       Windows® and the Web, dramatically increasing developer productivity. One
       of the programming languages we have in mind for the development of our
       project is C# (C-sharp). We will require the Visual Studio.NET compiler to
       run the applications.
      SQL: SQL is a standard computer language for accessing and manipulating
       databases. For our project, we will be developing databases for storing data
       entered by the user and other information. We will be using SQL in order to
       send and retrieve information to our database tables.
      ADO.NET: Since we are using C# to develop our project applications, we
       were wondering how we would create our database connection with the C#
       code. From our research on this matter, it is likely that we will use ADO.NET
       to create our database connection with C#.



                                            18    Written By: Daniel Fay 4thBSC IT
                                                           Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


      C#: C# is a new language for Windows applications, intended as an alternative
       to the main previous languages, C++ and VB. Its purpose is twofold:
       It gives access to many of the facilities previously available only in C++,
       while retaining some of the simplicity to learn of VB.
       It has been designed specifically with the .NET framework in mind, and hence
       is very well structured for writing code that will be compiled for .NET.
       Since our project is based on a windows environment, we believe that C# is
       the programming language we will choose to develop our PDA and PC
       applications. Its features suit everything our project requires including the
       .NET framework and windows based PDA system.
      Java: A high- level programming language developed by Sun Microsystems. It
       is used for many types of applications that are compatible with most operating
       systems including Windows, UNIX and Macintosh.
       However, because we aim to use a Windows CE based PDA, we believe that
       using java may not be the best choice of programming language to choose
       because it is said that java does not support all Windows based PDAs, unlike
       C# which is said to support almost all Windows based PDAs.
      MS ActiveSync 3.8: Microsoft ActiveSync 3.8 is the latest synchronization
       software for Windows Mobile-based Pocket PCs and Smart phones.
       ActiveSync 3.8 contains a set of security enhancements that provide a more
       secure syncing experience with a Windows PC, specifically:
       Windows XP SP2 security pop- up warnings that appear the first time a
       Windows Mobile device is docked have been eliminated. This is the
       synchronisation software we intend to use for the uploading and downloading
       of data between the PC and the PDA.
      Windows CE Operating System: A version of the Windows operating system
       designed for small devices such as personal digital assistants (PDAs) (or
       Handheld PCs in the Microsoft vernacular). The Windows CE graphical user
       interface (GUI) is very similar to Windows 95 so devices running Windows
       CE should be easy to operate for anyone familiar with Windows 95.
       This is the operating system we are focused on using for our PDA. The
       reasons rely on the facts that:




                                           19   Written By: Daniel Fay 4thBSC IT
                                                         Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


       - We and other users are more familiar with the Windows GUI rather than the
       Palm GUI.
       - Programming applications for Windows operating systems (OS) seems that
       little bit easier and understandable than programming applications for Palm
       OS.
       - We want to program our PC and PDA applications using the C#
       programming language, which will only support a Windows based PC and
       PDA.
      Palm OS: Since the introduction of the first Palm Pilot in 1996, the Palm OS
       platform has defined the trends and expectations for mobile computing - from
       the way people use handhelds as personal organizers to the use of mobile
       information devices as essential business tools, and even the ability to access
       the Internet or a central corporate database via a wireless connection.
       Palm OS 5, which has been available to customers for years, supports ARM®-
       compliant processors. Palm OS Garnet is an enhanced version of Palm OS 5
       and provides features such as dynamic input area, improved network
       communication, and support for a broad range of screen reso lutions including
       QVGA. The reasons for not choosing this type of PDA operating system are
       mentioned above (see Windows CE OS paragraph above)




                                          20    Written By: Daniel Fay 4thBSC IT
                                                         Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


Hardware Explored:
We have explored a number of hardware options that could be used for our Final Year
Project. There is such a wide range of pocket pcs and palm systems that we could
choose from but the trick is to select one that will be compatible to meet our project
goals. Here are just a few of the options that we considered.


           1. Palm Tungsten T5:
This runs a Palm OS with 256mb of memory with the
Intel 416MHz X-scale processor providing the power to
allow the user to run any business application. It is very
easy to transfer files from the handheld to the PC using
the simple „drag-and-drop‟ technique and the fact that
this handheld can be used as a USB drive. It is also possible to create and edit
word/excel documents which would be a requirement for our project. Our reason for
not choosing this is the fact that the OS would not be compatible with the application
development language we will use(C#).


           2. CASSIOPEIA E-200:

This runs Pocket PC2002 with strong arm 206 Processor and with capabilities to
allow users to connect to a variety of network products and accessories to create a
complete mobile office environment. A key feature on the E-200 is USB connectivity,
available through the provided cradle or an optional PC card unit/host converter. This
gives users access to devices such as printers, keyboards or PC cameras already in use
in their offices, allowing users to print documents, input long sentences using a
keyboard and hold video conferences. Applications to enable such access are expected
to be developed shortly.




                                           21    Written By: Daniel Fay 4thBSC IT
                                                          Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


              3. Dell AximX5:

The Dell Axim X5 is a fairly bulky but feature-rich Pocket PC handheld with a smart
docking cradle that will recharge a spare Li- ion battery.
Equipped with a 400MHz XScale processor, 48MB of ROM and 64MB of RAM, the
Axim X5 has plenty of processing power and storage available. It possesses a cradle
which recharges the handheld and connects to a PC via a USB cable, just as you'd
expect. A separate USB cable is also provided for syncing the unit independently of
the cradle. You can navigate the Axim X5's menus via the five-way button below the
screen or using a scroll dial on the unit's side. One of the main disadvantages would
be the fact that this handheld is too large to slip easily into most pockets, especially
when stored in its protective case.




              4. Garmin iQue™ 3600 PDA with Integrated GPS :
The iQue 3600 is the first PDA to include integrated GPS technology. With the power
of Palm OS 5 and the dependability of Garmin GPS technology, this "Super PDA"
redefines multi-tasking.
One of the key benefits of combining the PDA & GPS features on the iQue is the
contact- locator feature. Enabled by Garmin's Que technology, this feature connects
the Palm Address Book and Date Book to the GPS electronic map to give the user the
ability to navigate directly to a specific address within the user‟s contact database.
This PDA is mainly used for travel and plus it runs a Palm OS which we will be
avoiding. For these reasons it is clear that it will not be suitable for our project.




                                             22    Written By: Daniel Fay 4thBSC IT
                                                            Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


            5. IPAQ Pocket PC:

   The iPAQ Pocket PCs are likely the most popular and well know n of all Pocket
   PC handhelds. The iPAQ 3600 series was introduced as one of the first Pocket
   PCs in April of 2000. Compaq, and now HP, have updated the iPAQ line with
   the follow-up 3700, 3800 and 3900 series and now with the new 1000, 2000
   and 4000 & 6000 series, which all ship w ith Windows Mobile 2003 or Windows
   Mobile 5.0 installed. There is quite a number of IPAQ products so it will be
   difficult to narrow down to choose one. Each one runs a windows OS which is
   one of the requirements for this project. Cradles w ill be available so we can
   utilise the USB connection when transferring files from PDA to PC. It will be
   compatible with the software that be will be writing. Most IPAQ include Active
   Synch which is software to allow for the easy transfer of files from PDA to PC.
   An example of one that could be used is the iPAQ 5555.




   Above is an example of the IPAQ5555, which hopefully will be similar to one
   of the IPAQ products that we could use for our Final Year Project.


   These are just some of the hardware technologies that we explored for our
   Final Year Project. We had to make sure that the PDA will be in synch for the
   software we will be writing and developing and that it can be made easier to
   use for patients who wouldn’t necessarily be used to the technology
   environment.




                                        23    Written By: Daniel Fay 4thBSC IT
                                                       Karl Linnane 4thBSC IT
PDA-based Management System for Diabetics


   References:


    www.utracksys.com
    www.ciadvertising.org
    www.csharphelp.com
    www.dell.ie
    www.programmersheaven.com
    www.uml.org
    www.criticaltools.com
    www.4pm.com
    www.google.ie
    www.hp.com/uk/ipaq
    www.codeproject.com
    Lecture Notes from CT417




                                    24      Written By: Daniel Fay 4thBSC IT
                                                     Karl Linnane 4thBSC IT

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:8
posted:11/1/2010
language:English
pages:24