Академический Документы
Профессиональный Документы
Культура Документы
PROJECT REPORT
ON
BY
(INFORMATION TECNOLOGY)
UNIVERSITY OF MUMBAI
(2015 2016)
MALAD KANDIVALI EDUCATION SOCIETYS
CERTIFICATE
(B.Sc.IT/C
ACKNOWLEDGEMENT
I take this opportunity to express my gratitude to our Co-ordinator Mrs. Sindhu P.M.
for giving me this opportunity to accomplish my project work.
I am very thankful to our Principal Dr. (Mrs.) Ancy Jose, for her kind co-operation
during the completion of the project.
A special thanks to our project guide Ms. Sweety Garg for her most sincere efforts,
support and encouraging contribution throughout the project.
Last but not the least, I would like to thank all our friends & our family for their support,
motivation and encouragement.
5 ANNEXURE 68
5.1 References 68
5.2 Bibliography 68
ANALYSIS PHASE
1. ANALYSIS PHASE
1.1 Requirement Gathering Phase
Q. How much of time and efforts goes into maintaining and retrieving records?
Approximately 55% of time goes into maintaining and retrieving records.
DocPad Page | 1
1.1.3 Objective and scope of the project
Docpad is an Android app which sets up online communication between a doctor and a
patient. Docpad allows doctors to prescribe the medicines online via email. This will
help doctors in not maintaining the records/history physically which will save the time.
Doctor and patient both can access the records anytime from anywhere.
DocPad Page | 2
1.2 Feasibility Study
Assessing technical feasibility is to evaluate whether the new system will perform
adequately and whether an organization has ability to construct a proposed system
or not. The technical assessment help answer the question such as whether the
technology needed for the system exists, how difficult it will be to build, and
whether the firm has enough experience using that technology.
In case of technical feasibility, we have made a system that match accord to the
requirements of the doctors and patient.
We have made the project in a language in which we are familiar. The entire project
and website is made in Java and Couchbase. We have chosen these to as the project
is small and also we are familiar with the technologies.
The next area where have concentrated is the operating system architecture. At
presently the users are using jellybean, KitKat and lollipop and very soon it will be
available for marshmallow. So in order to solve this problem we have made the
software operating system and architecture friendly.
DocPad Page | 3
1.2.3 Economic feasibility
Economic evaluation is a vital part of investment appraisal, dealing with factors that
can be quantified, measured, and compared in monetary terms (Chen 1996). The results
of an economic evaluation are considered with other aspects to make the project
investment decision as the proper investment appraisal helps to ensure that the right
project is undertaken in a manner that gives it the best chances of success.
The system according to us is cost effective as this a small group which is containing
little members and only two members are working on this project.
Since the time given to us almost 10 months we are more time and therefore less man
power is required to develop the project.
DocPad Page | 4
1.2.4 Cost Benefit Analysis:
The coefficients a, b and c depend on the mode of the development. There are three modes
of development:
Basic COCOMO
The basic COCOMO applies the parameterized equation without much detailed
consideration of project characteristics.
Basic COCOMO a b C
Organic 2.4 1.05 0.38
Semi-detached 3.0 1.12 0.32
Embedded 3.6 1.20 0.32
MM = a * KDSIb
DocPad Page | 5
Intermediate COCOMO
Basic equation for the model is used, but fifteen cost drivers are rated on a scale of 'very
low' to 'very high' to calculate the specific effort multiplier and each of them returns an
adjustment factor which multiplied yields in the total EAF (Effort Adjustment Factor).
EAF
Category Cost Driver Very Low Nominal High Very Extra
Low High High
Product RELY Required Software 0.75 0.88 1.00 1.15 1.40 -
Attributes Reliability
DATA Database Size - 0.94 1.00 1.08 1.16 -
CPLX Product Complexity 0.70 0.85 1.00 1.15 1.30 1.65
Computer TIME Execution Time - - 1.00 1.11 1.30 1.66
Attributes Constraint
STOR Main Storage - - 1.00 1.06 1.21 1.56
Constraint
VIRT Virtual Machine - 0.87 1.00 1.15 1.30 -
Volatility
TURN Computer - 0.87 1.00 1.07 1.15 -
Turnaround Time
Personnel ACAP Analyst Capability 1.46 1.19 1.00 0.96 0.71 -
Attributes AEXP Applications 1.29 1.13 1.00 0.91 0.82 -
Experience
PCAP Programmer 1.42 1.17 1.00 0.86 0.70 -
Capability
VEXP Virtual Machine 1.21 1.10 1.00 0.90 - -
Experience
LEXP Language 1.14 1.07 1.00 0.95 - -
Experience
Project MODP Modern 1.24 1.10 1.00 0.91 0.82 -
Attributes Programming Practices
TOOL Use of Software 1.24 1.10 1.00 0.91 0.83 -
Tools
SCED Required 1.23 1.08 1.00 1.04 1.10 -
Development Schedule
DocPad Page | 6
Basic COCOMO A b C
Organic 2.4 1.05 0.38
Semi-detached 3.0 1.12 0.32
Embedded 3.6 1.20 0.32
EAF = 1*1.08*1.15*1*1.07*1.0*0.91*0.86*0.95
= 0.988
MM = 3*5.51.12*0.988
= 20.00
TDEV = 2.5*20.000.35
= 2.5*2.85
= 7.125
DocPad Page | 7
1.2.4.2 Function points:
User Output 4 4 16 1 5 5 2 7 14 35
User 23 3 69 - 4 - - 6 - 69
Online
Queries
Logical Files 1 7 7 2 10 20 2 15 30 57
External - 5 - - 7 - - 10 - -
Files
Total 107 85 44 236
CFP
CALCULATION OF RCAF
RCAF=
The RCAF determines the technical complexity factor TCF = 0.65+0.01*RCAF
FP = CFP*TCF
DocPad Page | 8
Sr. No Subject Grade
1 Requirement for reliable backup and recovery 3
2 Requirement for data communication 3
3 Extent of distributed processing 3
4 Performance requirements 5
5 Expected operational environment 4
6 Extent of online data entries 3
7 Extent of multi-screen or multi-operation online data input 1
8 Extent of online updating of master files 0
9 Extent of complex inputs, outputs, online queries and files 3
10 Extent of complex data processing 3
11 Extent that currently developed code can be designed for reuse 4
12 Extent of conversion and installation included in the design 4
13 Extent of multiple installations in an organization and variety of 0
customer organizations
14 Extent of change and focus on ease of use 4
Total = RCAF 40
Calculating FP
FP = CFP*TCF
TCF = 0.65+0.01*40
TCF= 1.05
FP = 236*1.05
= 247.8
DocPad Page | 9
1.2.4 Gantt Chart
DocPad Page | 10
1.3 Requirement Specification
Doctor Functionality:
Add patient.
Add, view and mail prescription.
View patient history and number of visits.
Backup and Restore data.
Patient Functionality:
View Prescription and history.
For running software there are some specification and only if it satisfies the specified
requirement it will get installed and works as it is designed for.
A technical requirement pertains to the technical aspects that your system must fulfil,
such as performance-related issues, reliability issues, and availability issues. These types
of requirements are often called quality of service (QoS) requirements, service level
requirements or non-functional requirements.
For our software also there are some specification there are as follows:
DocPad Page | 11
The system will work properly as intended and smoothly only if the requirements are
met or else the software will work but it may lag.
Doctor Functionality:
Add patient.
Add, view and mail prescription.
View patient history and number of visits.
Backup and Restore data.
Patient Functionality:
View Prescription and history.
The software also has backup and recovery options to protect the data. This would
help to recover from any type of software or OS or any other failures.
As per the requirement and guidelines that you have given we have formulated this document
and by signing this document you accept that all the requirements are met. Any change
request hereafter will be chargeable as per the requirement
DocPad Page | 12
1.4 Tools and Technology
DocPad Page | 13
Graphical User Interface: Android
Studio
DocPad Page | 14
CouchBase
DocPad Page | 15
Graphical User Interface: Cochbase console
DocPad Page | 16
Languages that we have used in our project are as follows:
JAVA
XML
JSON
JAVA
XML
Extensible Markup Language (XML) is a markup language that defines a set of rules for
encoding documents in a format which is both human-readable and machine-readable. It
is defined by the W3C's XML 1.0 Specification and by several other related
specifications, all of which are free open standards
JSON
JSON (JavaScript Object Notation) is an open-standard format that uses human-
readable text to transmit data objects consisting of attributevalue pairs. It is the most
common data format used for asynchronous browser/server communication (AJAJ),
largely replacing XML which is used by AJAX.
JSON is a language-independent data format. It derives from JavaScript, but as of 2016,
code to generate and parse JSON-format data is available in many programming
languages. The official Internet media type for JSON is application/json. The JSON
filename extension is .json.
DocPad Page | 17
DESIGN PHASE
2. DESIGN PHASE
2.1 Detailed life cycle of project
2.1.1 Event table
DocPad Page | 18
2.1.2 ER diagram
DocPad Page | 19
Figure: Docpad ER diagram (Patient)
DocPad Page | 20
2.1.3 Use Case Diagram
DocPad Page | 21
2.1.4 Class Diagram
DocPad Page | 22
2.1.5 Activity Diagram
DocPad Page | 23
Figure: Activity Diagram (Patient)
DocPad Page | 24
2.1.6 Sequence Diagram
DocPad Page | 25
Figure: Sequence Diagram (Patient)
DocPad Page | 26
2.1.7 State Machine Diagram
DocPad Page | 27
Figure: State Machine Diagram (Patient)
DocPad Page | 28
2.1.8 Component Diagram
DocPad Page | 29
2.1.9 Deployment Chart
DocPad Page | 30
2.1.10 Site Map
Figure: Sitemap
DocPad Page | 31
2.2 Physical design
START
LOGIN
NO
If Valid
YES
Add/Search
Patient
Create/View
Prescription
Mail Prescription
END
DocPad Page | 32
START
LOGIN
NO
If Valid
YES
View
Prescription
END
DocPad Page | 33
IMPLEMENTATION
PHASE
3. IMPLEMENTATION PHASE
3.1 Screen Layout
Main Page & Login Options
DocPad Page | 34
Doctor Sign Up
DocPad Page | 35
Doctor Log in
DocPad Page | 36
Doctor Homepage
DocPad Page | 37
Doctor Profile & Update
DocPad Page | 38
Add Patient
DocPad Page | 39
Search Patient
DocPad Page | 40
Prescription
DocPad Page | 41
Send Prescription via Gmail
DocPad Page | 42
Password Change
DocPad Page | 43
Patient Login
DocPad Page | 44
Patient Home
DocPad Page | 45
Patient Profile & Update
DocPad Page | 46
Prescription History
DocPad Page | 47
Prescription (in Gmail)
DocPad Page | 48
Medicine Search & Online Medicine Purchase
DocPad Page | 49
Password change
DocPad Page | 50
About us (Doctor & Patient)
DocPad Page | 51
3.2 Report Layout
Prescription History
DocPad Page | 52
Prescription History (Patients Email Account)
DocPad Page | 53
3.3 Validations
DocPad Page | 54
Validations (Doctor Sign Up)
DocPad Page | 55
Validations (Adding Patient)
DocPad Page | 56
Validations (Adding Patient)
DocPad Page | 57
Validations (Login Page)
DocPad Page | 58
Validations (Doctor Password change)
DocPad Page | 59
Validations (Patient Password change)
DocPad Page | 60
3.4 Test Cases
DocPad Page | 61
Doctor Module:
DocPad Page | 62
Patient Module:
DocPad Page | 63
White Box Testing:
Cyclomatic Complexity=E-N+P
Where,
E=number of edges in the flow graph.
N=number of nodes in the flow graph.
P=number of nodes that have exit points.
Cyclomatic Complexity for user validate function.
Here, E=36, N=35, p=2
Therefore, cyclomatic complexity = 36-35+2 = 3
Complexity=3
DocPad Page | 64
Figure: Control Flow Diagram/Graph
DocPad Page | 65
MAINTENANCE AND
EVALUATION
4. MAINTENANCE AND EVALUATION
4.1 System maintenance and future enhancement
The major goal of this application is to create online interaction between doctors
and patients, to fulfill the basic needs/problems of the patients. Patients can update their
problem to doctors by messaging and get advice from the doctor. DocPad serves as the
platform for easy and quick treatment, with extended support from doctors to patients.
DocPad has unique features such as issuing online prescription to patients, referring patients
to a specialist, sending health tips to patients, and finally, reducing the cost of customer
service and providing a vital communication link between doctors and patients.
System Maintenance:
Once the application is deployed, then maintenance phase starts. Application requires
maintenance because there are some residual errors remaining in the system that must be
removed as they are discovered.
In Maintenance we will be doing the following:
Future Enhancement:
Nothing can be ended in a single step. It is the fact that nothing is permanent in this world.
So this project also has some future enhancements in the evergreen and booming IT industry.
This app can be improved in the future by adding the following functionalities:
DocPad Page | 66
4.2 User Manual
1. User (doctor) can register his or her self by filling registration form.
2. User (doctor) can send prescription by login into application.
3. User (patient) can view their all prescription history.
4. User (patient & doctor) can view his or her profile and update also.
5. User (doctor) can register patients.
6. User (doctor) can view patient profile.
DocPad Page | 67
ANNEXURE
5. ANNEXURE
5.1 References
Programming Guide:
Mr. Bhavik Nitin Mer
Videos:
Android Programming Tutorial 2015 | The Complete Tutorial to Learn Android
Developing with Couchbase Lite Android
Websites:
Developer.android.com
www.tutorialspoint.com
Stackoverflow.com
www.couchbase.com
Books:
Programming Android (By: Zigurd Mednieks, Laird Dornin, G. Blake Meike &
Masumi Nakamura)
5.2 Bibliography
http://www.google.co.in
https://en.wikipedia.org/wiki/Couchbase_Server/
http://www.couchbase.com/
http://stackoverflow.com/questions/tagged/android
http://developer.android.com/guide
http://www.tutorialspoint.com/android
https://www.youtube.com/
DocPad Page | 68