Software Specification for Accurate Medicine Recognition

Software Requirements
Specification

For

Accurate Medicine Recognition

Supervisor: Mm Um-e-Habiba, Lecturer

Sana Farooq 04 sm580016@gmail.com

Sohail Akram 05 sohailmm3@gmail.com

Kiran Ajaib 14 km93683@gmail.com

Dated: 02-07-2018

Copyright © 2015 by Sohail akram. Permission is granted to use, modify, and distribute this document.
Software Specification for Accurate Medicine Recognition Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................... Error! Bookmark not defined.
1. Introduction ..............................................................................................................................1
1.1 Purpose............................................................................................................................................. 1
1.2 Document Conventions .................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions .................................................................................. 1
1.4 Product Scope .................................................................................................................................. 1
1.5 References ........................................................................................................................................ 2
2. Overall Description ..................................................................................................................2
2.1 Product Perspective.......................................................................................................................... 3
2.2 Product Functions ............................................................................................................................ 3
2.3 User Classes and Characteristics ..................................................................................................... 3
2.4 Operating Environment .................................................................................................................... 3
2.5 Design and Implementation Constraints .......................................................................................... 4
2.6 User Documentation ........................................................................................................................ 4
2.7 Assumptions and Dependencies ...................................................................................................... 4
3. External Interface Requirements ...........................................................................................4
3.1 User Interfaces ................................................................................................................................. 4
3.2 Hardware Interfaces ......................................................................................................................... 4
3.3 Software Interfaces .......................................................................................................................... 4
3.4 Communications Interfaces ............................................................................................................. 5
4. System Features .......................................................................................................................5
4.1 System Feature 1 .............................................................................................................................. 5
4.2 System Feature 2 (and so on) ..........................................................Error! Bookmark not defined.
5. Other Nonfunctional Requirements .......................................................................................5
5.1 Performance Requirements .............................................................................................................. 5
5.2 Safety Requirements ........................................................................................................................ 5
5.3 Security Requirements ..................................................................................................................... 5
5.4 Software Quality Attributes ............................................................................................................. 6
5.5 Business Rules ................................................................................................................................. 6
6. Other Requirements ................................................................................................................6
Appendix A: Glossary....................................................................................................................6
Appendix B: Analysis Models .......................................................................................................6
Appendix C: To Be Determined List ............................................................................................6
 Page 1
Software Specification for Accurate Medicine Recognition

1. Introduction
This document outlines the software requirement for accurate medicine recognition system. it will
cover the overall description of the system, specific requirements and a description of a prototype
to be build to demonstrate the system’s functionality.

1.1 Purpose

The Purpose of this document is to describe in detail the accurate medicines recognition system. It
will explain the purpose and features of the system, what the system will do and constraints under
which it must operate .it will explain thoroughly the complete description of medicine and different
companies of medicines (National or International) in Pakistan and It will give detail of registered
and unregistered companies information and highlighted the narcotics included drugs and is
intended for the general public for the better selection of medicines.

1.2 Document Conventions

This document is created based on the IEEE template for system requirement specification
documents.

1.3 Intended Audience and Reading Suggestions

Typical users, such as common people who want to get complete information of the medicines
available in market.
Doctors who wants to get knowledge about different companies of medicines to prescribe better
one.
Health organizations use for better health advices to people.
Health officers and drug inspectors to check the illegal medicine companies.

1.4 Product Scope

It is the system that people will use to analyze the best medicine of their choice .it will recognize
the medicines by company wise differences. People will understand about medicines in better way
and discover hidden aspects about it.

1.5 Glossary

Term Definition
 Page 2
Software Specification for Accurate Medicine Recognition

Active Article The document that is tracked by the system; it is a narrative

that is planned to be posted to the public website.
Author Person submitting an article to be reviewed. In case of
multiple authors, this term refers to the principal author,
with whom all communication is made.
Database Collection of all the information monitored by this system.
Editor Person who receives articles, sends articles for review, and
makes final judgments for publications.
Field A cell within a form.
Historical Society Database The existing membership database (also HS database).
Member A member of the Historical Society listed in the HS
database.
Reader Anyone visiting the site to read articles.
Review A written recommendation about the appropriateness of an
article for publication; may include suggestions for
improvement.
Reviewer A person that examines an article and has the ability to
recommend approval of the article for publication or to
request that changes be made in the article.
Software Requirements A document that completely describes all of the functions
Specification of a proposed system and the constraints under which it
must operate. For example, this document.
Stakeholder Any person with an interest in the project who is not a
developer.
User Reviewer or Author.

1.6 References

IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications.
IEEE Computer Society, 1998.

2. Overall Description
This section contains the complete description of our project. It states the perspective of the
system. This section also shows the constraints faced by the system, and the assumptions we
made about the system it will be interacting with, and the people who will be using the system.
 Page 3
Software Specification for Accurate Medicine Recognition

2.1 Product Perspective

It is self-contained product using new approaches for achieving the old goal but rather more
efficiently. Its main purpose is to differentiate between national and international companies in
Pakistan. In Pakistan several local and unregistered companies are working as well, these
companies make their agreements with doctors to publicized and prescribe their products in
prescriptions these companies pay the doctors on monthly basis and there is commission system
as well. Many companies make their products which contain low quality ingredients which is prove
by their wholesale total price. People are totally unaware of these agreements and product quality.
our system will give detail description of medicines detail such like (level, ingredients, price,
registration information, unregistered companies, stride included medicines and banned medicines
in Pakistan).

2.2 Product Functions

 The system shall be able to chose the best medicine from number of companies.

 The system shall provide complete information of medicines

(ex: company, price, salt, Indications, warnings, side effects and high risk groups)

 The system shall provide Registration and license number information of medicines.

 The system shall provide Time to Time updates.

 The system shall provide information about Stride included medicines.

 The system shall provide information about Unregistered medicines

2.3 User Classes and Characteristics

It is intended for by common people for better selection of medicines according to their choice. The
user must be able to properly put medicine name in medicine search engine, as if any incorrect
input is put into the system, the medicine search option provided by the system would not be valid
in any way. Also the user needs to have some kind of medicines information. Doctor will prescribe
the medicine and people will select the best one according to their choice and user needs to be
able to act upon the same medicine as prescribe by the doctor.

2.4 Operating Environment

The software will work on windows as well as Linux distributions. It requires 1GB of RAM, 900 MB
of HDD with minimum Core i5 system, Core i7 is recommended.
 Page 4
Software Specification for Accurate Medicine Recognition

2.5 Design and Implementation Constraints

This product is made to work in harsh environments yet low memory may cause the system to
freeze. The system must have access to database which contain medicine records of different
companies.
The system will only work for medicines which are in record. If someone search medicine name
that our database do not have record of, our system will not accurately be able to provide useful
information.

2.6 User Documentation

User manual describing complete functioning and configuration of software is included. On-line
help can also be found at www.Accuratemedicinerecognition.com

2.7 Assumptions and Dependencies

The system assumes that there is database set up which holds medicine name, company name,
price, registration number, medicine included stride, banned companies and that our system as
access to these piece of information .as without this information, our system has no information
about any other medicine information.

3. External Interface Requirements

3.1 User Interfaces

The interface of the system is extremely simple providing only useful features while omitting all
irrelevant features to avoid cluttering.

3.2 Hardware Interfaces

No special requirement in hardware is required since this software is a database processing

software at most levels.

3.3 Software Interfaces

The system needs a few other components which are included in package like Dot Net Framework.
The system can be connected with a MYSQL or SQL database to import searching list of
medicines.
 Page 5
Software Specification for Accurate Medicine Recognition

3.4 Communications Interfaces

Fast internet connection is required for communication and update some components of the
system.

4. System Features
The system includes the following features:
 Search engine.
 Complete information (such as price, indications, side effects, over dosage, warnings, overview
etc).
 Registration information.
 Stride included medicines.
 Banned companies and medicines.

4.1 Login

4.1.1 Stimulus/Response Sequences

It contains the input fields for submission of username and password of the administrator of
the system.
4.1.2 Functional Requirements
Cache Memory is required for its features.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

Moderate RAM memory is required for loading of the system into the memory.

5.2 Safety Requirements

To ensure that no one of system user loses any data while using the system (due to crush or a bug
of some kind) The developer team updates system regularly. There is a bug tracer or comment
section available where user can report any bugs they have encountered so that the developer can
fix it in next update.

5.3 Security Requirements

The system does not have any security requirements and thus any type of user can use it without
any additional privileges. There is no restriction on read access.
 Page 6
Software Specification for Accurate Medicine Recognition

5.4 Software Quality Attributes

System provides the user many simple features. Due to its well design and easy to use interface it
can be used by both expert and typical users. However, user must already have a basic knowledge
of medicines before use.

5.5 Business Rules

This product is designed for multiple users but gives complete access to admin only.

6. Other Requirements
The product can use existing databases. It does not require but can work with a number of
software.

Appendix A: Glossary
UoK University of kotli
www.UoKERP.edu.ajk Web Site Address of UoKERP

Appendix B: Analysis Models

Entity-relationship diagrams etc are attached in SQL with the document.

Appendix C: To Be Determined List

 IEEE.com
 www.UMSITERP.edu.ajk