A

MICRO PROJECT REPORT

ON
“DEFECT REPORT ON MALWARE DETECTION ON
ANDROID SMARTPHONE”

Program & Program code :

CO5I Course name : STE
Course code : 22518

Submitted by,

NAME OF STUDENT ENROLLEMENT NO PROGRAM

Ghungarde Rutuja Shivaji 2214640024 CO5I

Jadhav Payal Bhausaheb 2214640038 CO5I
Karle Nita Satish 2214640041 CO5I

Under the Guidance of

Prof. Mhaske.B.B.

In partial fulfillment of requirement for the award

of Diploma in Computer Engineering
MSBTE, Mumbai.

Academic Year: 2024-25

DEPARTMENT OF COMPUTER ENGINEERING

S.S.M. ADSUL POLYTECHNIC COLLEGE
CHAS, AHMEDNAGAR-414 005(M.S)

1
 DEPARTMENT OF COMPUTER ENGINEERING
S.S.M. ADSUL POLYTECHNIC
COLLEGE,CHAS, AHMEDNAGAR-414
005(M.S)

CERTIFICATE
This is to certify that the micro project report entitled

Submitted by,

NAME OF STUDENT ENROLLEMENT NO PROGRAM

Ghungarde Rutuja Shivaji 2214640024 CO5I

Jadhav Payal Bhausaheb 2214640038 CO5I
Karle Nita Satish 2214640041 CO5I

Of semester I institute, Sau. Sundarabai Manik Adsul Polytechnic, Chas, Ahmednagar

(code: 1464) has completed the micro project satisfactorily in course (22518) for the
Academic year 2024-25 as prescribed in the MSBTE curriculum.

Place: Ahmednagar
Date: / /2024

Prof. Mhaske.B.B. Prof.Hole.P.P. Prof.Gadakh.R.S.

(Micro Project guide) (Head of Dept.) (Principal)

2
 ACKNOWLEDGEMENT

We take this opportunity to acknowledge the constant encouragement and continuous help given
to me by my guide Prof. Mhaske.B.B. convey my sincere thanks to his valuable timely suggestion.

We would also like to thanks principal Prof. Gadakh R.S and Head of Computer Department
Prof. .Hole P.P We would also like to thank teaching staff of Computer Department for helping us to
achieve this goal.

We are also thankful to those who directly or indirectly helped me for completing this micro
project. we would like to thank my parents without whose supports; the completion of the micro project
would not have been possible.

Ghungarde Rutuja Shivaji

Jadhav Payal Bhausaheb
Karle Nita Satish

3
 INDEX

Sr. No Name of Topic Page

No
PART A- PLAN

1.0 Introduction 5

2.0 Aim of Micro-Project 5

3.0 Action plan 5

4.0 Resources required 6

PART B- (OUTCOMES AFTER EXECUTION)

1.0 Brief Introduction 7-8

2.0 Aim of Micro-Project 8

3.0 Course Outcomes 8

4.0 Actual Methodology Followed 9

5.0 Actual Resources Used 10

6.0 Conclusion 11

7.0 Skill developed / learning out of this micro- 11

project

4
 PART –A
(PLAN)

1.0 INTRODUCTION

What is Defect?
A defect in a software product is also known as a bug, error or fault which makes the software produce
an unexpected result as per the software requirements. For example; incorrect data, system hangs,
unexpected errors, missing or incorrect requirements.

What is Defect Report?

A defect report is a document that has concise details about what defects are identified, what action steps
make the defects show up, and what are the expected results instead of the application showing error
(defect) while taking particular step by step actions.
Defect reports are usually created by the Quality Assurance team and also by the end-users (customers).
Often customers detect more defects and report them to the support team of the software development
since the majority of the customers curiously tries out every feature in the application.

2.0Aim of Micro-Project:
Prepare Defect Report on Malware Detection on Android Smartphone.

3.0 Action Plan

Sr.No. Details of Activity Planned Start Planned Finish Name of Responsible
Date Date Team Members

1. Formation of group and selection of 11-09-2024 13-09-2024 Rutuja Ghungarde

topic

2. Submission of proposed plan 19-09-2024 24-09-2024 Payal Bhausaheb

3. Project definition, design 26-09-2024 30-09-2024 Rutuja Ghungarde

structure, testing

4. Demonstration of project 04-10-2024 07-10-2024 Nita Karle

5. Submission of micro project 10-11-2024 18-11-2024 ALL MEMBERS

5
 4.0 Resources Required
Sr.No. Name of Resources/Material Specification Qty.

1. Computer system with broad i3-i5, 2GB Ram, HDD 4GB 1

Specifications

2. Software Windows 1

3. Any other resource used MS Word 1

6
 PART-B
(OUTCOME FROM THIS PROJECT)

1.0 Brief Introduction:

We can find the defect from our project “Malware Detection on Android Smartphone” and
make a defect report on the basis of defects. Using the above parameters we prepare the defect
report:
1. Defect ID:
Nothing but a serial number of defects in the report.
2. Defect Description:
A short and clear description of the defect detected.
3. Action Steps:
What the client or QA did in an application that results in the defect. Step by step actions they
took.
4. Expected Result:
What results are expected as per the requirements when performing the action steps mentioned.
5. Actual Result:
What results are actually showing up when performing the action steps.
6.Severity:
(A small bug that doesn’t affect the software product usage).

a. Low
A small bug that needs to be fixed and again it’s not going to affect the performance of
the software.
b. Medium
This bug does affect the performance. Such as being an obstacle to do a certain action.
Yet there is another way to do the same thing.
c. High
It highly impacts the software though there is a way around to successfully do what the
bug cease to do.
d. Critical
These bugs heavily impact the performance of the application. Like crashing the
system, freezes the system or requires the system to restart for working properly.
7. Attachments:
A sequence of screenshots of performing the step by step actions and getting the
unexpected result. One can also attach a short screen recording of performing the steps
and encountering defects. Short videos help developers and/or QA to understand the
bugs easily and quickly.

7
A Defect Report, also known as a Bug Report, is a document created during the
software testing process to identify, describe, and track any issues or defects found in
a software application.
It provides detailed information about the defect, including how it was discovered,
the environment in which it occurred, and steps to reproduce it. A defect
report includes
complete details about the application/software defects, sources, what are the actions
needed to resolve them, and the expected result.

i. Developers can check this defect report, understand the problem & its
solution and make improvements accordingly.

ii. QA testers create a defect report to test & analyze each functionality and note
it in the report.

iii. It
requires lots of effort and information to write a detailed defect
report and deliver It to developers.

so the primary purpose of a good defect report is to identify the anomalies in the project and
inform developers with a well-organized structure.

2.0 Aim of Micro-Project:

Prepare Defect Report on Malware Detection on Android Smartphone.

3.0 Course Outcomes:

Identify bugs to create defect report on given application.

8
4.0 Actual Methodology Followed:

Module 1: Feature Extraction.

Defect_ID FE_01

Project Malware Detection on android Smartphone

Release Version 1.0

Module Feature Extraction

Detected Build version Fe.001

Summary Feature extraction not functioning properly.

Description The module should extract features from installed apps to analyze
potential malware.
Steps to replicate _

Actual Result Error

Expected Result The module should extract relevant features for analyze accurately.

Attachments Extraction_issue_screenshot.jpg

Remark The feature extraction must be precise and consistent for the
detection system to function effectively.
Defect Severity Major

Defect Priority Fe_01

Reported by Ghungarde Rutuja S.

Jadhav Payal
B.
Karle Nita S.
Assigned to Mr. Mhaske B.B.

Fixed Build Version 1.A

9
 Module2: Selection of Keyword.

Defect_ID ADS_01

Project Malware Detection on android Smartphone

Release Version 1.1

Module Keyword Selection for Malware Detection

Detected Build version Ad.01

Summary The module fails to accurately detect keywords indicative of Malware.

Description The application is intended to scane and identify keywords that could
indicate potential malware threats.
Steps to replicate _

Actual Result Error

Expected Result The module should identify and flag keywords that suggest malware
presence.
Attachments Keyword_detection_error.jpg

Remark The module should enhance detection accuracy for keywords to identify
malware.
Defect Severity Major

Defect Priority Dt_01

Reported by Ghungarde Rutuja S.

Jadhav Payal B.
Karle Nita S.

Assigned to Mr. Mhaske B.B.

Fixed Build Version 1.1A

10
5.0 Actual Resources Used:
S. No. Name of Resources/Material Specification Qty.

1. Computer system with broad i3-i5, 2GB Ram, HDD 1

specifications 4GB

2. Software Windows 1

3. Any other resource used MS Word 1

6.0 CONCLUSION:
A defect report is a crucial instrument for efficient communication, defect management and
general quality control in the software development industry. Its significance goes beyond
problem discovery and includes defect resolution throughout its whole lifecycle and supports
continuous development process improvement.
Hence here we have successfully prepare defect report on the topic of
Malware Detection on Android Smartphone.

7.0 Skill developed / learning out of this micro-project:

 Analytical skills
 Logical thinking
 Multitasking

 Project management skills

 Attention to detail
 Timemanagement
 Communication skills.

11
 ANNEXURE II
Evaluation Sheet for the Micro Project
Academic Year :2024-25

Name of Faculty: Prof. Mhaske B.B.

Course: STE
Course Code: 22518 Semester: 5th

Title of the Project: Defect Report on Malware Detection on Android Smartphone.

COs addressed by the Micro Project:

A: Prepare defect report on defect report on Malware Detection on Android Smartphone.

Major learning outcomes achieved by students by doing the Project:

(a)Practical outcomes:
Prepare defect report on given topic.
(b) Unit outcomes in Cognitive domain:
Identify bugs to create defect report on given application.
(c) Outcomes in Affective Domain----------------------------------------------------------------------

---------------------------------------------------------------------------------------
Comments/Suggestion about team work/leadership/inter-personal communication (if
any)

Marks out of 6 for Marks out of 4 for

performance in performance in Total
Sr.
Student Name group activity (D5 oral/ presentation out of
No.
Col. 8) (D5 Col.9) 10

1 Rutuja Ghungarde
2 Payal Jadhav
3 Nita Karle

(Name & Signature of

Faculty) Prof. Mhaske

B.B.
12