01-07-2013, 04:55 PM
E-Prescription on Mobile
E-Prescription.doc (Size: 1.52 MB / Downloads: 24)
INTRODUCTION
In the growing world of technology, cellular devices have quickly emerged as one of the fastest evolving fields. They have increased greatly in both popularity and complexity, requiring more advanced operating systems and applications to meet the demands of the consumer.
Android is a software stack for mobile devices that includes an operating system,a middleware and key applications. The Android SDK provides the tools and APIs necessary to begin developing applications that run on Android-powered devices.
PURPOSE OF THE PROJECT:
The project is basically designed to develop an electronic way of generating prescriptions through an automated data entry process. The patients can consult the doctor on mobile to describe their problem and the doctor views the previously given prescriptions of that particular patient and gives the prescription.
PROBLEMS IN EXISTING SYSTEM:
Here the existing system is a manual system using which the patient needs to go the clinic manually, he needs to check the doctor list, doctor availability and book the appointment. The doctor also needs to tell the clinic management to cancel his OP on a particular date. If the patient wants to contact the doctor for some confirmation then he needs to come to the clinic again. By following this approach the clinic management people needs to store the customer information, further consultations and payment details.
PROPOSED SYSTEM:
E-Prescription is a mobile based application which is used to interact with Doctor on mobile. Instead of going and meeting the doctor several times, by staying at home patient can consult the doctor on mobile, then doctor advises new prescription by looking at older one. Everyone busy with their daily activities so it is impossible to meet the doctor every time. Proposed system reduces these unnecessary efforts.
Usecase Diagram:
A use case illustrates a unit of functionality provided by the system. The main purpose of the use-case diagram is to help development teams visualize the functional requirements of a system, including the relationship of "actors" (human beings who will interact with the system) to essential processes, as well as the relationships among different use cases.
Use-case diagrams generally show groups of use cases — either all use cases for the complete system, or a breakout of a particular group of use cases with related functionality (e.g., all security administration-related use cases). A use-case diagram is typically used to communicate the high-level functions of the system and the system's scope.
Collaboration Diagram:
UML Collaboration diagrams (interaction diagrams) illustrate the relationship and interaction between software objects. They require use cases, system operation contracts, and domain model to already exist. The collaboration diagram illustrates messages being sent between classes and objects (instances). A diagram is created for each system operation that relates to the current development cycle (iteration).
TECNOLOGIES / PLATFORMS USED
Android is Google's operating system for mobile devices. It is a competitor to the Symbian platform, Apple's iOS for the iPhone and Microsoft's Windows Mobile for mobile devices. Technologically, Android includes middleware and key applications, and uses a modified version of the Linux kernel. It was initially developed by Android Inc., a firm later purchased by Google, and lately by the Open Handset Alliance. It allows developers to write managed code in the Java language, controlling the device via Google-developed Java libraries.
The Android operating system software stack consists of Java applications running on a Java based object oriented application framework on top of Java core libraries running on a Dalvik virtual machine featuring JIT compilation. Libraries written in C include the surface manager, OpenCore media framework, SQLite relational database management system, OpenGL ES 2.0 3D graphics API, WebKit layout engine, SGL graphics engine, SSL, and Bionic libc. The Android operating system consists of 12 million lines of code including 3 million lines ofXML, 2.8 million lines of C, and 2.1 million lines of Java.
Open Handset Alliance
The OpenHandsetAlliance, a consortium of several companies which include Texas Instruments, BroadcomCorporation, Google, HTC, Intel, LG, MarvellTechnologyGroup, Motorola, Nvidia, Qualcomm, Samsung Electronics, Sprint Nextel and T-Mobile was unveiled with the goal to develop open standards for mobile devices. Along with the formation of the Open Handset Alliance, the OHA also unveiled their first product, Android, a mobile device platform built on the Linux kernel version 2.6.
Software development kit
The Android SDK includes a comprehensive set of development tools. These include a debugger, libraries, a handset emulator (based on QEMU), documentation, sample code, and tutorials. Currently supported development platforms include x86-architecture computers running Linux (any modern desktop Linux distribution), Mac OS X10.4.8 or later, Windows XP or Vista. Requirements also include Java Development Kit, Apache Ant, and Python 2.2 or later. The officially supported integrated development environment (IDE) is Eclipse (3.2 or later) using the Android Development Tools (ADT) Plugin, though developers may use any text editor to edit Java and XML files then use command line tools to create, build and debug Android applications as well as control attached Android devices (e.g., triggering a reboot, installing software package(s) remotely).
A preview release of the Android software development kit (SDK) was released on 12 November 2007. On 15 July 2008, the Android Developer Challenge Team accidentally sent an email to all entrants in the Android Developer Challenge announcing that a new release of the SDK was available in a "private" download area. The email was intended for winners of the first round of the Android Developer Challenge. The revelation that Google was supplying new SDK releases to some developers and not others (and keeping this arrangement private) has led to widely reported frustration within the Android developer community.
Community-based firmware
There is a community of open-source enthusiasts that build and share Android-based firmware with a number of customizations and additional features, such as FLAC lossless audio support and the ability to store downloaded applications on the microSD card. This usually involves rooting the device. Rooting lets users load modified firmwares allowing users of older phones to use applications available only on newer releases.