MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

VIVEKANAND EDUCATION SOCIETY POLYTECHNIC

MICRO PROJECT
Academic year: 2024-25

TITLE OF PROJECT
Prepare test plan and Design test cases for MS Paint application to
perform testing using an Automation Tool

Program: Computer Engineering

Program code: CO-5I (B)
Course: Software Testing (STE)
Course code: 22518
 MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION
Certificate
This is to certify that Mr./Miss. Akshay Parab, Rushikesh Pawar, Jayesh Nainwani
Roll No. 22, 23, 24 of Fifth Semester of Diploma in Computer Engineering Of
Institute, V.E.S. POLYTECHNIC (Code: 0004) has Completed the Micro Project
satisfactorily in Software Testing (22518) for the academic year 2024 - 2025 as
prescribed in the curriculum.

Place: Mumbai Enrollment No: 2200040404, 2200040405, 2200040406

Date: ……/……/2024 Exam Seat No:

Subject Teacher Head of the Department Principal

Shubhra Tonge

Seal of
Institution
 INDEX

Academic year: 2022-23 Name of the faculty: Mrs. Shubhra Tonge

Program code: CO-5I Course & Course code: Software Testing (STE)

Roll No:22, 23, 24 Enrollment No. : 2200040404, 2200040405, 2200040406

Semester: 5th
Name of the Students: Akshay Parab, Rushikesh Pawar, Jayesh Nainwani

SR.NO. CONTENT PAGE NO.

1 Brief Introduction 1-3

2 Aim of the Micro-Project 4

3 Action Plan and Resources Required 5

4 Brief Description 6-9

5 Implementation & Result 10-18

6 Skill Developed / learning out of this Micro-Project 19

7 Teacher Evaluation Sheet 20-23

 Annexure-1

Micro Project Proposal

Prepare test plan and Design test cases for MS Paint application to
perform testing using an Automation Tool

1.0 Aim of Micro Project :

The Aim of this microproject is to design test cases and test plan for MS Paint so that we
can cover all critical features and functionalities of MS Paint to identify issues and to
perform automation testing of MS Paint using ZAPTEST Tool to works across different
versions and configurations.

2.0 Course Outcomes Addressed:

 CO2: Prepare test cases for different types and levels of testing
 CO3: Prepare test plan for the application
 CO5: Test software for performance measures using automated testing tool

3.0 Proposed Methodology

• Define the Research Problem: Clearly state the problem or research question you want
to address. Provide context and background information to explain the significance of
the problem.
• Review of Literature: Conduct a thorough literature review to understand existing
research and theories related to your problem. Identify gaps in the literature that your
study can fill.
• Research Design: Choose a research approach (qualitative, quantitative, mixed-
methods, experimental, observational, etc.) based on the nature of your research
question. Specify the research methods and tools you'll use to collect and analyze data.
• Data Collection: Describe the data collection process, including the population or
sample you will study. Explain the data collection tools and techniques (surveys,
interviews, observations, experiments) you'll use.
• Results and Findings: Present the results of your analysis in a clear and organized
manner. Use tables, charts, and graphs to visualize the data. Interpret the results and
relate them back to your research question. Report Preparation
• Discussion: Discuss the implications of your findings and their relevance to the
research problem
4.0 Action Plan

Name of
Planned Planned
Sr. Responsible Team
Activity performed Finish date
no. Start date Members
1
Discussion and finalization of topic 06/02/2023 20/02/2023
2 Preparation and submission of
Abstract
3 Literature Review
4 Collection of Data
5 Compilation of Report And
Presentation

Actual Presentation & Final

6
submission of Micro Project

5.0 Resources required:

Name of
S. No. Specifications Qty
Resource/material
1. Desktop Dell, Windows 10, i5 4410(u) 1

2. Reference book: Software Author’s name : Roger 1

engineering - A practitioner’s Pressman
approach

Group Details:

Sr.No Roll No Name of Student

1 68 Shreya Shukla
2 67 Aditya Garje
3 70 Shahid Sarnobat

Name of Guide:

Mrs. Sangita Bhoyar

 Micro Project Report
Annexure-II

Choose a problem EMAIL CLEARING SYSTEM, create UML Diagrams and

estimate the cost of the project

1.0 Rationale:
The significance behind project work is to make sure that the students does their own
research and comes up with practical solutions to the concept they are trying to learn or
the problem that they are trying to solve.
Email Clearing System is a free anti-spam tool to get rid of newsletters/spam/advertising
emails with just one click. Email Clearing System works with all emails providers (gmail,
outlook, yahoo mail, hotmail), mails accounts and email apps. It provides an interface
with subscription models according to the user requirements too.

2.0Aim of Micro Project:

This Micro-Project aims: to explain us how to estimate cost of the project using appropriate cost
estimation method such as Function point (FP) and COCOMO.

3.0 Course Outcomes Addressed:

• (CO1) Select a suitable Software Process model for software
development.
• (CO2) Prepare software requirement specifications.  (CO3) Use
Software modeling to create data designs  (CO4) Estimate size and
cost of software product.

Annexure-II

4.0 Literature Review:

Introduction :
Consistent users of general email system face exertion in deletion of loads of emails
which demands individual selection of emails. Also visiting every website for the
objective of unsubscribing sponsored emails increases complexity and labor.
Email clearing system allows minimization of time requirement of a general email system
to expunge immense number of either spam or sponsored emails. It also assists in
 lessening the complexity of unsubscribing from the sponsored platforms promoted to the
users via email systems.
UML DIAGRAMS:

UML (Unified Modeling Language) a way to visually represent the architecture, design, and
implementation of complex software systems. It's a rich language to model software
solutions, application structures, system behavior and business processes.

 Use case:

A use case diagram is used to represent the dynamic behavior of a system. It encapsulates
the system's functionality by incorporating use cases, actors, and their relationships. It models the tasks,
services, and functions required by a system/subsystem of an application. It depicts the
high-level functionality of a system and also tells how the user handles a system.

Use case diagram components:

• Actors: The users that interact with a system. An actor can be a person, an
organization, or an outside system that interacts with your application or system.
They must be external objects that produce or consume data.
• System: A specific sequence of actions and interactions between actors and the
system. A system may also be referred to as a scenario.
• Goals: The end result of most use cases. A successful diagram should describe
the activities and variants used to reach the goal.
 DFD:

A Data Flow Diagram (DFD) is a traditional visual representation of the information

flows within a system. A neat and clear DFD can depict the right amount of the system
requirement graphically. It can be manual, automated, or a combination of both.
• Circle: A circle (bubble) shows a process that transforms data inputs into data
outputs.
• Data Flow: A curved line shows the flow of data into or out of a process or data
store.
• Data Store: A set of parallel lines shows a place for the collection of data items
• Source or Sink: Source or Sink is an external entity and acts as a source of
system inputs or sink of system outputs.

Levels in Data Flow Diagrams (DFD):

• 0-level DFD
• 1-level DFD  2-Level DFD  ER:

ER model stands for an Entity-Relationship model. It is a high-level data model. This

model is used to define the data elements and relationship for a specified system. It
develops a conceptual design for the database. It also develops a very simple and easy to
 design view of data. In ER modeling, the database structure is portrayed as a diagram
called an entityrelationship diagram.
 Activity diagram:

Activity diagram is basically a flowchart to represent the flow from one activity to another
activity. The activity can be described as an operation of the system.
The control flow is drawn from one operation to another. This flow can be sequential,
branched, or concurrent. Activity diagrams deal with all type of flow control by using
different elements such as fork, join.

 State diagram:

A state diagram, also known as a state machine diagram or state chart diagram, is an
illustration of the states an object can attain as well as the transitions between those states
in the Unified Modeling Language (UML). In this context, a state defines a stage in the
evolution or behavior of an object, which is a specific entity in a program or the unit of
code representing that entity.

5.0 Actual Methodology Followed:

• The project group would be formed according to the roll number and the topic for
micro project would be allotted by the subject teacher in consultation with our group.
 The topic allotted to our group was to prepare a report & make an Email Clearing
System. According to the topic allotted by the subject teacher for the micro-project,
we all the members of group would have a brain storming session among ourselves
After receiving the approval for the submitted action plan of project activities
(Annexure I) from the subject teacher, we would prepare a To-Do- List with
responsibilities and according the work would be distributed among the group
members.
• After making the program code we search and discuss information and take photo of
code output that would be required for the micro - project, we would prepare some
information of assigned micro-project topic and would execute as aimed. Finally the
information of the project gathered micro-project topic would be presented to the
subject teacher for evaluation. We will also prepare Micro-project Final Report and
would submit it to subject teacher before the term end.
 Annexure-II

6.0 Actual Resources Used:

Sr. Name of
Specifications Qty
No. Resource/material

1 Laptop Windows 10 1

2 Printer hp 1

3 Printer paper A4 size As required

Annexure-II
7.0 Outputs of micro-projects
USE-CASE DIAGRAM

LEVEL 0 DFD

LEVEL 1 DFD
 LEVEL 2 DFD

ACTIVITY DIAGRAM
ER DIAGRAM
STATE DIAGRAM
 FUNCTION POINT
Weighting Factor Count
Measurement
Count
parameter * Simple Average Complex

9 * 4 6 27
Number of 3
user inputs

8 * 5 7 32
Number of 4
user outputs

1 * 4 6 3
Number of 3
user inquiries

1 * 10 15 7
Number of 7
files

2 * 7 10 10
Number of 5
user interface

COUNT TOTAL 79

FP = Count total *[0.65+0.01*£ (Fi)]

= 79*[0.65+0.01*(46)]
= 54.51

Function Point of Email Clearing System is : 54.51

 USER INPUTS:
1. Request for clearing emails.
2. Request for unsubscribing emails.
3. Request for Login.
4. Request for apply for subscription plan.
5. Request for Logout.
6. Request to cancel the plan.
7. Request to delete emails from trash bin.
8. Request for recover emails.
9. Request for access the customer service.

 USER OUTPUTS:
1. Response for clearing emails.
 2. Response for unsubscribing emails.
3. Response for Login.
4. Response for apply for subscription plan.
5. Response to cancel the plan.
6. Response to delete emails from trash bin.
7. Response for recover emails.
8. Response for access the customer service

 FILES:
1. SRS (System specific requirements).

 EXTERNAL INTERFACES:
1. User interface
2. Administrator interface

COST ESTIMATION USING COCOMO:

Boehm proposed COCOMO (Constructive Cost Estimation Model) in 1981.COCOMO is one of

the most generally used software estimation models in the world. COCOMO predicts the efforts
and schedule of a software product based on the size of the software.
In COCOMO, projects are categorized into three types:
1. Organic
2. Semidetached
3. Embedded

Project ai bi ci di

Organic 2.4 1.05 2.5 0.38

Semidetached 3.0 1.12 2.5 0.35

Embedded 3.6 1.20 2.5 0.32

The Email Clearing System is concluded to be Organic System as the team size required is
adequately small, the problem is well understood and has been solved in the past and also the
team members have a nominal experience regarding the problem.

 Organic Type of Software:

 LOC = 23000
Salary of engineer = 10000/-
E (Efforts) = 2.4 * (KLOC) ^1.05
= 2.4 * (23) ^1.05
= 64 Person-Month
TDEV (Development Time) = 2.5 * (E) ^ 0.38
= 2.5 * (64) ^ 0.38
= 12 months
Cost = TDEV * Salary of engineer
= 12 * 10000
= 120000 /-

The estimated cost for the Email Clearing System is 120000 /-

Annexure-II

8.0 Skill Developed / learning out of this Micro-Project

The following skills were developed-
1 Designing: Designing of micro project with minimum required resources and
at low cost.
2 Teamwork: Learned to work in a team and boost individual confidence.
3 Time Management: Timely completion of micro project as scheduled.
4 Data Analysis: Interpretation of data: drawing and analysis of graphs,
laboratory calculations, etc.
5 Problem-solving: Develop good problem-solving habits.
6 Technical writing: Preparing a report of the proposed plan and final report.
7 Presentation: Giving working model presentation of the micro project.

9.0 Applications of this Micro – Project.

References:
 https://blog.teachmint.com/importance-of-project-work-inschool/#:~:text=Gives%20Them
%20Practical%20Experience,they%20are%20trying%20t o%20solve.
 https://www.geeksforgeeks.org/
 https://www.cleanfox.io/en/

Sign of the faculty

Mrs. Sangita Bhoyar

Annexure-III

Suggested Rubric for Assessment of Micro-Project

S. Characteristic to be Poor ( Marks Average Good Excellent

No. assessed 1-3) ( Marks 4 - ( Marks 6 - ( Marks 9- 10 )
5) 8)
Relevance to the course Relate to very few Related to some LOs Take care of at-least one Take care of more than
1
LOs CO one CO
Not more than two
sources At-least 5 relevant
Literature Survey At –least 7 relevant About 10 relevant
2 (primary and sources, at least 2
/information collection secondary), very old sources, most latest sources, most latest
latest
reference
3 Completion of the Completed less than Completed 50 to Completed 60 to 80% Completed more than
 Target as per project
50% 60% 80 %
proposal
Enough data collected
Sufficient and
by sufficient and
appropriate Sufficient and appropriate
Sample Size appropriate sample size.
sample, enough sample, enough data
small, data Proper
Analysis of Data and data generated but generated
4 neither organized inferences drawn
representation not organized and which is organized and
nor presented well by organising and
not presented well. presented well but poor
presenting data
No or poor inferences drawn through tables, charts
inferences drawn
and graphs.
Just Well
Well
assembled/fabricated assembled/fabricated
and parts are not assembled/fabricated
with proper
functioning with proper functioning
functioning parts. In
Quality of well. Not in proper parts. In proper shape,
Incomplete proper shape, within
5 Prototype/Model shape, dimensions within tolerance
fabrication/assembly. tolerance dimensions
beyond tolerance dimensions and good
and good
limit. finish/appearance. But
finish/appearance.
Appearance/finish is no creativity in design and
Creativity in design and
shabby. use of material
use of material
Nearly sufficient
Very short, poor
and correct details Very detailed, correct,
quality sketches, about methods, Detailed, correct and clear clear description of
Details about
material, description of methods, materials,
methods, precautions and methods, materials, precautions and
6 Report Preparation material,
conclusion. but precautions and conclusions.
precaution and clarity is not there in Conclusions. Sufficient Enough tables,
conclusions presentation. charts and
Graphic Description.
omitted, some details But not enough sketches
are wrong graphic description.
Major information is Includes major
Includes major Well organized, includes
not included, information but
Presentation of Micro information and well major
7 information is not not well organized
Project organized but not presented information ,well
well organized . and not presented
well presented
well
Replied to
Could not reply considerable Replied properly to
Replied most of the
8 Viva to considerable number of considerable number of
questions but not questions properly
of question. question.
very properly

Annexure – IV

Micro-Project Evaluation Sheet

Academic year: 2021-22 Name of the faculty: Mrs. Sangita Bhoyar
Program code: CO-4I (A) Course & Course code: Software Engineering
(SEN)

Roll No: 67, 68, 70 Enrollment No. 220004220, 220004222,

220004214
Semester: 4th Name of the Students: Shreya Shukla, Shahid
 Sarnobat, Aditya Garje
Title of the Micro-Project: Choose a problem EMAIL CLEARING SYSTEM, create UML
Diagrams and estimate the cost of the project

Course Outcomes Achieved:

 (CO1) Select a suitable Software Process model for software development.
 (CO2) Prepare software requirement specifications.  (CO3) Use Software
modeling to create data designs  (CO4) Estimate size and cost of software
product.

Evaluation as per Suggested Rubric for Assessment of Micro Project

Sr. Characteristic to be assessed Poor Average Good Excellent Sub Total
No. Marks 1- Marks Marks 6- Marks 9-10
3 4-5 8
(A)Process and product assessment Out Of 6

1 Relevance to the course

2 Literature Survey .
Information Collection

3 Completion of the Target as

per project proposal

4 Analysis of Data and

representation

5 Quality of
Prototype/Model/Content

6 Report Preparation

(B)Individual Presentation/Viva Out of 4

7 Presentation .

8 Viva

Micro-Project Evaluation Sheet

 Process and Product Individual Total
Roll
Name Assessment Presentation/Viva Marks
No.
(6 marks) (4 marks) 10

1 Shreya Shukla

2 Aditya Garje

3 Shahid Sarnobat

Comments/Suggestions about teamwork/leadership/interpersonal communication (if any)

……………………………………………………………………………………………..

……………………………………………………………………………………………..

Name and designation of the Faculty Member: Mrs. SANGITA BHOYAR (Lecturer)

Signature________________