Requirements Specification Group Name :

For : 117942 ‫ محمد رمضان الرمحي‬-1

121584 ‫ يوسف خالد حمد‬-2
**(Electronic Doctor)** 110805 ‫ صايل محمد ابو عليقة‬-3
118256 ‫ محمد فالح الطويل‬-4

Version <1.0>

Instructor : ‫نة‬
‫صـ‬
‫خـواـ‬ ‫وسف‬
‫يـ‬
Course :
fundamentals of
software
engineer.
TABLE OF CONTENTS
• 1 INTRODUCTION
• 1.1 DOCUMENT PURPOSE
• 1.2 PRODUCT SCOPE
• 1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
• 1.4 REFERENCES AND ACKNOWLEDGMENTS
• 15 state diagram
• OVERALL DESCRIPTION
• 2.1 PRODUCT FUNCTIONALITY
• 2.2 END USERS AND CHARACTERISTICS
TABLE OF CONTENTS
• 2.3 SYSTEM STAKEHOLDERS
• 2.4 OPERATING ENVIRONMENT
• SPECIFIC REQUIREMENTS
• 3.1 USER INTERFACE
• 3.2 FUNCTIONAL REQUIREMENTS
• 3.3 USE CASE DIAGRAM
• NON-FUNCTIONAL REQUIREMENTS
• 4.1 SOFTWARE QUALITY ATTRIBUTES
• OTHER REQUIREMENTS
 Purpose and Scope of
“E-Doctor”
The electronic doctor is very useful for people , provide most
functions of doctor such as Diagnosis of disease , give the
necessary medication and save health record for all patients .

Online (electronic) doctor system is designed for all people,

The system offers a question (simple test), then finally provide
result then recorded .

1
Definitions, Acronyms and
Abbreviations
1- E-Doctor On-line Dcotor

2- Electronic Dcotor Is a expert system working as a doctor can be ACCESS

at any time

3-
References and
Acknowledgments
• Webkidia : HYPERLINK "http://www.webkidia.com"
www.webkidia.com
User Interface
State diagram
 Negatives of E-Doctor
Risks and disadvantages may affect the project :
- E-Doctor must have internet connection so it is not useful for people
who don’t use internet devices.
- Bad instructions affect the using of E-Doctor ,so good using
instructions should included by the designer or the stakeholder.
- Inaccuracy of entered patient information, so we will have wrong
medical results of patient case.
- Bad design of the app will decrease the rate , cost and number of
users .
 Project Functionality
When patients enter the system, the system provides a
question about the symptoms to the user, the patient
chooses symptoms, All the answers are recorded , then
the system performs some calculations based on the
answer, and then displays the result (disease) and
medicine based on the process. 
This improved in the following context model :
 5

Context diagram
 FUNCTIONAL REQUIREMENTS
(1)
n1 : the software provide list of symptoms .
n2 : the software accept the selected as record list .
n3 : the software perform sum calculate for the record .
n4 :the software provide disease .
n5 :the software provide medication for the disease .
n6 : the software save each patients disease and
medication .
 FUNCTIONAL REQUIREMENTS
(2)
• User RR :
• R1: the patients/user login to the software .
• R2: the patients/user chooses symptoms .
• R3 : the patients/user got medication and disease(result) .
• Admin FR :
• FR1 :insert to database .
• FR2 :update the database .
• FR3:delete from database .
 Non Functional
Requirements
n1 : The software should be available.

n2 : The software should be scure .

n3 : The software save medication in the database.

 End user and characteristics

User Who login to software and chooses symptoms .

Admin who design, maintain and enter information to the database.

PhCompany Who provide the medication for the disease .
*Operating environments for E-doctor :
• Java .
• HTML & PHP .
*Software Quality Attributes for E-doctor :
• Privacy .
• Availability .
• Flexibility .
 11

Use case diagram of logging system

 12

Class Diagram
 13

Sequence diagram
 14

Activity diagram
PHASE 2

Testing
 15

Development Testing
• Unit testing:
Test the functionality of E-Doctor system, When patients enter the
system, the system provides a question about the symptoms to the
user and the patient chooses symptoms .. Etc .
• Components testing:
Test the components interface .
• System testing :
The interaction and connection between E-Doctor components.
• System and components testing (FULL Test):
E-Doctor is a flexible system so we can edit and add new parts.
 16

Use Case Testing

• Release testing:
Test the version of E-Doctor (1.0) and this project have
a lot of actors and entities .
• User testing:
E-Doctor have specific users that we make tests of their
using , so after that we have made the test of our
version(1.0).