0% found this document useful (0 votes)
43 views6 pages

Online Medical Shop 1st Report

Uploaded by

Asif Koujaganur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
43 views6 pages

Online Medical Shop 1st Report

Uploaded by

Asif Koujaganur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Zero Level DFD:

Admin User
PMS

FIRST LEVEL DFD:

ADMIN:

Admin
PMS
Database
USER:

User
PMS
Database

SECOND LEVEL DFD:


DMIN: Add View

Edit
Username&
Admin Pwd Login Valid Products
Delete

Invalid Delete

Add
Vendor
Edit

View

Customer Add

Bill
View
View
Add
Delete
Order Reorder
View

Delete

ENTITY RELATIONSHIP DIAGRAM (ER)


ADMIN

Add View
Add View

Medicine Vendor

medicine_name View vendor_name

company_name
vendor_contact
Add
contetnt
vendor_address

m_date, e_date

Bill
price

Customer bill_id medicine_id

bill_date
customer_name

customer_contact customer_id

customer_addres
Functional Requirements:
Functional requirements are statements of the services that the system must
provide or are descriptions of how some computations must be carried out.The
plan for implementing functional requirements is detailed in the system design.
 Admin is provided with Username and Password to avoid unauthorized access.
 Basic and advance admin facilities like add/update/delete Product details are
provided.
 Sends the quotations to the customer generated by the Admin.
 Manages details about the vendors.
 Manages customer details.
 Back up /recovery of data such as product details.
 Role based System functions access.

5.6 Non-Functional Requirements


A non-functional requirement is a requirement that specifies criteria that can be
used to judge the operation of a system, rather than specific behaviors. This should
be contrasted with functional requirements that define specific behavior or
functions. The plan for implementing non-functional requirements is detailed in the
system architecture.

 The code is easily understood and read because of the structure and coding
style of the application.
 Various components are provided in order to improve the performance at peak
time.

You might also like