You are on page 1of 20

Pimpri Chinchwad Education Trust’s CO-R-46

Pimpri Chinchwad Polytechnic


Revision : Date :
Computer Department
:00
(NBA Accredited and ISO 9001:2015Certified Department)
Academic Year: 2023-2024 Page : 01/01

MICRO-PROJECT REPORT
PART - A and PART – B

Name of Program: Diploma in Computer


Engineering

Semester: 5th Semester

Name of Course and Code: Software Testing (22518)

Title of the Micro-Project: “Medical store


management system”
Name of Team Members: 2. Rahul Kalunke

3. Akshay Patil

4. Gopal Chinchole

5. Rishikesh Dharunde

Name and Sign of the Project


Guide:
Mrs. S .P. Chattar

Department Of Computer Engineering, PC Polytechnic


MaharashtrBoard of
Technical Education, Mumbai
(Autonomous) (ISO-9001-2015) (ISO/IEC 27001:2013)

CERTIFICATE

This is to certify that Mr. Rahul kalunke, Akshay patil, Gopal Chinchole,
Rishikesh Dharunde of Diploma In Computer Engineering of Pimpri- Chinchwad
Polytechnic has completed Micro projects of the course Software Testing (22518)
as prescribed in the curriculum for the academic year 2023-24.

Place: Nigdi,Pune-44 Date:

Course Incharge Head of Department


Mrs. S .P. Chattar Prof.M.S.Malkar

Seal of institute
PART-A Micro Project Proposal
“Medical store management
system”

1.0 Aim/Benefits of the Micro-Project:


• The aim of Microproject is to prepare report on Medical store management
System.

2.0 Intended Course Outcomes:


• Prepare the test cases for different types and levels of testing.

3.0 Proposed methodology -


The project aims is to is to prepare report on Medical store management system
in the following format:

Step I :- Searched and Selected the topic for micro project.

Step II:- Discussed about the microproject.

Step III:- Distributed the work accordingly.

Step IV :- Collected and gathered the required data.

Step V :- Prepared the test cases.

Step VI :- We Process information in one document

Step VII :- We Consulted with our subject teacher.


4.0 Resources Used-

SR. NAME OF
NO. RESOURCE/MATERIAL SPECIFICATION QTY REMARKS

1. Operating System Microsoft Windows 1 Used

2. Visual Studio code Version 5.2.2 1 Used

3. Eclipse Version 4.24 1 Used

4. Search Engine Chrome 1 Used

5.0 Action Plan:-

SR. Details of Activity Planned start Planned finished Name of


NO. Date Date Responsible
Team Member
Topics given by subject
1. teacher and discussed on All members
given topic with all
members.
Collection of information
2. related to topic Gopal Chinchole

3. Planning of project Rahul Kalunke

Analyses the collected data


4. and finalize structure of Akshay Patil
project
Distribution of task and
5. discussion of roles and Rishikesh
responsibilities of each Dharunde
member
6. Design of project Gopal Chinchole
6.0 List of team member

Enrollment No. Names


Roll No.

2000560359 2. Rahul kalunke

3. Akshay patil

2000560411 4. Gopal chinchole

5. Rishikesh
dharunde
PART-B Micro Project Proposal
“Medical store management
system”

1.0 Rationale:
Medical shop management requires user entry of container and product
dimensions, together with information on weight and orientation constraints. It
implements the storage and retrieval system of day-to-day activities which
involves daily transaction report, monthly wise report on goods delivered,
enquires which enables us to provide efficient and accurate methods of
organizing and accessing different types of information. In-built database
facilities for up to 50 containers and 4000 products are provided so that input into
these screens can be carried out with minimal effort. If information for a
particular product code is already held in the 4000 product database then this is
automatically entered into the appropriate fields. The first option will attempt to
pack as much of the medicines using any of the packing methods available to
medical shop management. This may be a loading from the floor or from the end
of the container. The second and third options are self explanatory and the one
most appropriate t o the practical circumstances should be selected.

2.0 Aim/Benefits of the Micro-Project:


The aim of Microproject is to prepare report on Medical store management
System.

3.0 Intended Course Outcomes:


Prepare the test cases for different types and levels of testing.

4.0 Literature Review


In this system, the management needs not to keep any type of registers, which
they use to keep in old one. They have work only with one computer. All the
details are stored in computer files. The dual entries are done very quickly as
entry in one file only, affects the other file where it has to record. In the way there
is no need to record the computer operator.
• Objectives
• Accuracy
• Security
• Time Saving
• Perform Repetitive Task Very Well
• Low Cost
• Easy Maintenance
• Easy Modification
• Attractive and Status
4.0.1 Module Description
1. Purchase Item -The medicines been purchased by the medical shop, the
details are recorded in the Purchase Item. Some of the details been recorded by
the Medical shop agent is the agency from which the medicines are bought, item
details such as item type, item name, quantity, manufacturing date, expiry date
etc. The operations that are been performed here: To add new records into the
database, to modify an already existing record in the database , to search a record
and delete a record from the database.

2. Sales Item- The medicines been sold out by the medical shop, the details are
recorded in the Sales Item. Some of the details been recorded by the Medical
shop agent is the agency or the customer and their respective address to whom the
medicines are sold, item details such as item type, item name, quantity,
manufacturing date, expiry date etc. The operations that are been performed here:
To search a record in the database and delete a record from the database.

3. Item Details -The medicine details such as name of the medicine, bill number,
manufacturing date, expiry date, price and the quantity of the medicines etc are
been recorded in the Item Details.

4. Customer Billing -The bill for the medicines been purchased, is issued to the
Customer by the medical shop. The Customer bill contains the bill number,
purchase date, details of the item such as medicine type, name, price, quantity,
manufacturing date, expiry date etc. The operations that are been performed here:
To print the record ,to modify an already existing record in the database ,to search
a record and delete a record from the database.

5. Stock Details- The Stock details deals with the details of the agency as well as
the stock item such as the item type, item name, price and quantity. The
operations that are been performed here: To display the sales details of the stock
as recorded in the database ,to search a record in the database

4.0.2 Data Flow Diagram

Data flow oriented techniques advocate that the major data items handled by a
system must be first identified and then the processing required on these data
items to produce the desired outputs should be determined. The DFD (also called
as bubble chart) is a simple graphical formalism that can be used to represent a
system in terms of input data to the system, various processing carried out on
these data, and the output generated by the system. It was introduced by De
Macro (1978), Gane and Sarson (1979).The primitive symbols used for
constructing DFD's are:
5.0 Actual Methodology Followed:

Waterfall Model is used to develop medical Store management system.


• Reason For choosing WaterFall Model

1. This is Small Project and Requirements Are Well understood.


2. This model is simple and easy to understand and use.
3. Waterfall model is simple to implement and also the amount of resources
required for it are minimal.
4. It is easy to manage due to the rigidity of the model - each phase has
specific deliverables and a review process.
5. In this model, output is generated after each stage (as seen before),
Therefore it has high visibility. The client and project manager gets a
feel that there is considerable progress. Here it is important to note that
in any project psychological factors also play an important role .
6. In this model phases are processed and completed one at a time. Phases
do not overlap. This Project Is Conversion From Manual To Automatic.

• Advantages and Disadvantages

• Advantages –

1. This system provides an easy way for the casher to determine whether the
customer is a valid member so that he can provide them with discount.

2. This system is also provides great help to the casher to add or update
new or existing members respectively

• Disadvantage –

1. As every coin has a two side this system also suffers from disadvantage.

2. Multiple medicines can not be checked for a customer

6.0 System Testing

Testing is an activity to verify that a correct system is being build and if perform with
the intention of results once gathered and evaluated provide a qualitative indication
of software quality and reliability and serve as a basis for design modification. A
project is said to be incomplete without proper testing
• Testing Levels

System testing is the stage of implementation that is aimed at ensuring that the
system works accurately and efficiently before live operation commences. Testing is
vital for the success of the system. System testing makes a logical assumption that
if all parts of the system are correct, the goal will be successfully achieved. A series
of tests are performed for the proposed system is ready for User Acceptance
Testing. The testing steps are
• Unit Testing
• Integration Testin
• Validation Testing
• Output Testing
• User Acceptance Testing

1. Unit Testing - Unit testing focuses verification efforts on the smallest unit of
software design, the machine module. This is also known as "MODULE TESTING".
The modules are tested separately is carried out during programming stage itself. In
this step, each module is found to be working satisfactory. So the expected output
from the module is arrived.

2.Integration Testing - Data can be lost across and interface, one module can
have an adverse effect on others, and sub-functions when combined may not
produce the desired major functions. Integration Testing is a Systematic Structure,
while at the same time conducting to uncover errors

associated within the interfaces. The objective is to take unit-tested modules


and to combine them and test it as a whole. Here correction is difficult because the
vast expenses of the entire program complicate the isolation of
causes. This is the integration testing step. All the errors encountered will be carried
over to the next testing step.

3. Validation Testing - Validation testing is performed in order to find whether there


is any flow and deficiency in requirements of the system. Each and every module is
tested independently. The input and output process are validated effectively. The
input of the user for each field is validated to check if value entered is null (or) valid.
After field level validation, the module level is made such that they are integrated
and a validation is performed for the whole system
4. Output Testing - After performing the validation, the next is output testing of the
proposed system. Since no system could be useful. If it does not produce the
required output in the special format asking the user about the requirement, test the
output generated (or) displayed by the system. Hence the output format is
considered in two ways. On is on of the screen and other is printed format.

5. User-Acceptance Testing - User-Acceptance of a system is the key factors for


the success of any system. The system under consideration is tested for user
acceptance by constantly keeping in touch with the perspective system users at the
tim

7.0 Action Plan

Sr. Work Done by Team name of Student

No. Member
1 Topic given by subject teacherand 2.Rahul kalunke
3.Akshay patil
. discussed on given members. 4.Gopal chinchole
5.Rishikesh dharunde

2 Collection of information
4.Gopal chinchole
. related to the topic.

3 Planning of project.
.
2.Rahul kalunke

4 Analyze the collected data and


3.Akshay patil
. finalize structure of data.
5. Distribution of task and
5.Rishikesh dharunde
discussion of role and
responsibilities of each other

6. Design of Project
4.Gopal chinchole

7. Implementation 2.Rahul kalunke


3.Akshay patil
4.Gopal chinchole
5.Rishikesh dharunde

8. Finalization of project 2.Rahul kalunke


3.Akshay patil
4.Gopal chinchole
5.Rishikesh dharunde

8.0 Resources Required:

Sr. Name of Re- Specifications


No. source/material

1 Operating System Windows 10

2 Computer System Processor i7


RAM-8GB
3 Software Microsoft word,
Microsoft Excel.
9.0 Outputs of the Micro Project:
10.0 Skill Developed/Learning outcome of this Micro-project:

1.After working on the allotted microproject topic, I gained various d skills


like working in team, making coordination between team members.
2.This project also made me increase my various skills.
3. Such project work increases our knowledge other from the regular
course work

11.0 Applications of this Micro Project:

The Proposed medical management is the completely computerized.


1.In proposed system there is no need to maintain data about medicine
because all process of that data done in computerized.
2. The modern age the age of computer is an electronic device, which
trade line as it as many advantages such as speed, accuracy, security
3.In this proposed system all the add, edit, delete, search in project of
computer are done through computerized system.
4.Easy and fast retrieval of information.
5.Better storage capability. More efficient operation.
6.Well Designed report.
7. Eliminate the repeated data entry effort and errors.
Name of program: Software Testing.
Semester: 5th
Course Title: Software Testing (22518).
Title of Microproject: “Medical store management system”
Name of subject teacher: Mrs. Shital. P. Chattar

You might also like