1.

0 Rational
Medical store management system is a very simple micro project in software
engineering. That help you to understand the basic concept of software engineering.. This
project is used mainly for medical stores to maintain the details of medical stores such as stock
and account.

This medical store management system is designed as to ease work load of medical
store professionals. The main feature includes inventory and stack control, accounting, client
management. This system organize their daily activities like billing, tablets information, stock
details and more. In present trend this application is used in every medical shop. This system will
save time and increase work efficiency This software helps you to track all the products of
medical shop more over it’s a medical shop accounting software .Flexible and adaptive software
suited to medical shops or stores or pharmacies of any size.

2.0 Course Outcomes

1. Select appropriate process models.
2. Prepare SRS.
3. Modeling for different data designs
4. Estimate project size and cost.
5. Project management and quality assurance.

3.0 Literature Review

Medical store management system project in software engineering is simple
application. In this project user can perform typical management functions like adding a new
medical record and displaying, modifying, editing and deleting it.

We collected the information about our project medical store management system from
Google and reference book of software engineering.

4.0 Proposed methodology

Collection of collected information from various medium.

 First we select the topic for micro project.

 We collected all the information about project.
 We studied about subject of the project.
 We made a report on project.
  Planning

Activity Description Duration Roles

A Requirement Gathering 10-2-20 to 11-2-20 Poonam
Masti,
Pratiksha
patil.

B Hardware selection 11-2-20 to 15-2-20 Poonam

Masti,
Saroja
Gaikwad.
C Designing 16-2-20 to 21-2-20 Pratiksha
Patil, Pallavi
patil.
D Coding 21-2-20 to 24-2-20 Poonam
Masti.
Pratiksha
patil
E Debugging/Testing 24-2-20 to 4-3-20 Pratiksha
Patil, Saroja
Gaikwad
F Deployment 4-3-20 to 16-3-20 Poonam
Masti,
Pratiksha
patil, Saroja
Gaikwad,
Pallavi patil.

5.0 Resources Required

Sr. No Name of Specification Quantity

Resources
1. Computer Computer(i3- 1
System i5preferable)RAM
minimum 2GB
2. Operating Windows 7 1
System
3. Application MS word 2010 1
Software
6.0 Output Of The Micro Project

 Model implementation

Waterfall model is used to develop this project

This is small project and requirements are well understood. This model is simple
and easy to understand and use. waterfall model is simple to implement and also the amount of
resources required for it are minimum. It is easy to manage due to the rigidity of the model. Each
phase has specific deliverable and a review process.

In this model output is generated after each stage therefore it has high visibility.
The client and project manager gets a fill the there is considerable progress. Here it is important
to note that in any project psychological factors also play and important role. This project is
conversion from manual to automatic.
  Software Requirement Specifications(SRS)

Functional requirements
1. The software must allow input of products data from administrator and secure access at
and from the data streaming real time monitoring equipment.
2. The project must request user name and password for access to data .only after
authentication will allow access to the system.
3. The project must require high level of error correction and input validation.
4. Project must allow browsing by the directors and staff to access and update information
products and customer vendors
5. The project must identify the products and customers by a unique numeric identifier
derived from a function performed on the customers birth date of products.

Non Functional Requirements

1. The software interface must follow design conventions which allow for familiar
location of menus etc.
2. Input errors will be returned in red with appropriate message box.
3. More the three attempts of login and failure will produce a red flag to system
administrator.
4. Response time should be minimum.

 Designing

Data Flow Diagram Of Medical Store Management System

Data flow diagrams (DFDs) reveal relationships among and between the various
components in a program or system. DFDs are an important technique for modeling a system’s
high-level detail by showing how input data is transformed to output results through a sequence
of functional transformations.
Example of DFD for Medical store management system shows the Data Flow
Diagram for medical store and interactions between the Visitors, Customers and Sellers, as well
as Website Information and User databases.
ER Diagram
 This ER (Entity Relationship) Diagram represents the model of Medical Store Management
System Entity. The entity-relationship diagram of Medical Store Management System shows all
the visual instrument of database tables and the relations between Medicines, Company, Medical
Shop, Sells etc.

 Coding
  Front end coding using visual studio in vb.net
The coding is the process of transforming the design of a system into a computer
language format. This coding phase of software development is concerned
with software translating design specification into the source code.
The coding of the software will be carried out in the vb.net .The code should be
well tested and should optimized. The coding structure of the software should have the
proper exception handling so that if any error to be understood if encounterd by the
user .The database should be also linked properly to the vb.net code in development
environment
 Back end coding using SQL file server
The vb.net is used to the easy of its coding and easy to learn syntax. The visual
studio is used since it has one of most easy to design user interface offering a quick to
construct software .The back end is designed in SQL file server since the SQL file server
offers a easy to built table structure and also it is more easy to connect to the front end
that also data can be easily stored in columns in the SQL file server .

Reason For Selecting This Language

Because of the simplicity of the syntax, but VB.NET has the ability to create
very powerful and sophisticated applications. VB.NET is a great place to start because of
how easy and straight forward it is. The syntax is easy and you will not find yourself
writing hundreds of lines of code as there are many shortcuts that make coding so much
easier in this language.
WE selected SQL file server for back end because of its availability, security,
managing tools, database manageability development tools.

 Testing
Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding. The purpose of
product testing is to verify and validate the various work product viz. units, integrated
unit, final product to ensure that they meet their respective requirements.
This process has two parts
1. Planning – This involves writing and reviewing units, integration, functional,
validation and acceptance test plans.
2. Execution-This involves executing these plans, measuring, collecting data and
verifying if it meets the quality criteria. Data collected is used to make appropriate
changes in the plans related to the development and testing.

The Techniques followed throughout the testing of the system are as under

1. Top Down Testing

 In Top to down approach, testing takes place from top to down following the
control flow of the software system.

2. Bottom Up Testing
In the bottom-up strategy, each module at lower levels is tested with higher
modules until all modules are tested. It takes help of Drivers for testing

Modules
1. Login: Using this module user enters user name and
password and the system checks whether it is valid. If it is valid user can log in,
otherwise invalid user name and password message is displayed.
2. Purchase: This module allows purchasing medicines from
the supplier. It contains fields such as batch number, manufacture date, expiry date,
company name, etc.
3. Sales module: This module consists of customer sales
information. When sale is made proper fields in the sale form should be filled such
as patient name, address, doctor’s name, medicine details etc.
4. Stock module: This module manages the inventory. Stock
is updated when purchase, sale or replace is made.
5. Medicine: This module consists of information of
medicines available in the Medical.
6. Employee: Using this module the user can add employee
name, update his details and generate payrolls with great ease.

1. Black box testing

1. All the software functions are operational.
2. Input is properly accepted.
3. Output is correctly produced

2. White box testing

1. It is predicated on close examination of procedural details.

2. Providing test cases that exercise specific sets of conditions and/or loops
tests logical path through the software.
3. The state of the program may be examined at various points to determine if
the expected of asserted status corresponding to the actual status.
  Deployment
The software will be deployed after testing.
Deployment includes all the process required for preparing a software
application to run and operate in a specific environment. It involves installation,
configuration, testing and making changes to optimize the performance of the
software. It can either be carried out manually or through automated systems.
In deployment we want to manage customer expectations and we want
to provide essential manual, instructions and documentation. Customer must get all
supporting and essential help from developer.
1. Instruction manual will be provided to the customer.
2. proper training will be given to the customer.
3. Frequent updates will be given to the software.
4. Frequent security patch will be provided to the customer.
5. All the executable will be given to the customer with all the documents.

 System Features
1. Order processing and taking.
2. Staff information.
3. Customer bill detail.
4. Product detail.
5. Searching of product.
6. Reminder about product expiry.

7.0 Skill Development

1. Analyzing the information.
2. Software design.
3. Software Testing.
4. Problem solving and team work.

8.0 Applications Of Project

In all medical stores, different inventories as well as milk dairy.
9.0 Area Of Future Improvement
1. There will be only one data base for the two or more stores Messaging service to inform
customers. As this is a generic software it can be used by wide variety of outlets(Retailers
and Wholesalers) to automate the process of manually maintaining the records related to
the subject of maintaining the stock and cash flows.
2. This project is basically updating the manual chemist inventory to Automate Inventory
system. So that organization can manage their record in efficient and organized form.
3. It also includes automatic validation of data during it sale and purchase. It is able to
detect the medicines that are near to expiry date or expired.

 Conclusion
By using “Medical shop management system”, the orders can be easily tracked and
the report acts as a proof. The order will be taken systematically and will be saved safely in the
database rather than manually through paper work. It requires less time and space to save the
order details. Database can be cleared yearly or monthly according to the company.

 Reference
1. WWW.Google.com
2. Reference book of software engineering.