CRTIFICATE

THIS IS CERTIFIED THAT THE SEMISTER REPORT ENTITLED

“Examination and Result Management System”

IS BENEFITED WORK AND IT IS SUBMITED TO THE
GOVERNMENT POLYTECHNIC, YAVATMAL
SUBMITED BY:

 Riya Godse (21)

 Tejaswini Rathod (46)
 Saloni Pawar (58)
 Aditi Chaudhari (68)

FIFTH SEMISTER OF DIPLOMA IN COMPUTER ENGINEERING, MAHARASHTRA

STATEBOARD OF TECHNICAL EDUCATION, MUMBAI
SUBMITTED IN A PARTIAL FULFIMENT OF THE DIPLOMA IN COMPUTER
ENGINEERING DURING THE ACADEMIC YEAR 2023-2024

GUIDE HOD PRINCIPLE

PROF. R. MESHRAM PROF. S S.METE DR. R.P. MOGRE

INSTITUE
SEAL

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

 ACKNOWLEDGEMENT

It is pride to present project on Examination and Result Management System. Within

the deep sense of gratitude and profound respect, I acknowledged my oblivion to my guide
Prof. R. Meshram Mam, for the valuable guidance and timely inspiration.

Our sincere and whole hearted thanks to our HOD Prof. S.S. Mete Computer Engineering
for providing all facilities needed for successful completion of project.

We are also thankful to Principal DR. R.P. Mogre, for inspiring us to achieve highest goal.

Last but not least, we are thankful to our parents, all faculty members and friends who have
directly and indirectly helped us in completing our project.

Students Names:

RIYA GODSE
TEJASWINI RATHOD
SALONI PAWAR
ADITI CHAUDHARI

Index
Chapters No. Annexure No. & Chapter Title
1. Annexure I 1.1 Title
1.2 Aim/Benefits of the Micro-Project
1.3 Course Outcomes
1.4 Proposed Methodology
1.5 Action Plan
1.6 Resource Required
2. Annexure II 2.1 Title
2.2 Rationale
2.3Amis/Benefits of the Micro-Projects
2.4 Course Outcomes Archived

3. 2.5 Literature Review Case Study

Current System
Introduction
Purpose
Problem Statement
Scope
4. Prototyping Model
5. Cost Estimation
6. Code
7. Note
8. Testing Methodologies Testing
Example of GUI Test Cases
Positive and Negative Test Cases
9. Test Cases Test Cases for Login Module

10. Risk Management Plan Risk Table

11. Timeline Chart

12. Gantt Chart
13. SQA Plan Software Quality Assurance Plan, Audit, and
Revives.
Why do we need SQA in Test Management Process
Benefits of SQA
Steps to implement the Quality Assurance
14. Defect/ Bug What is a Bug in Software Testing
Basic terminology of Defect/Bug
 Why Defect/Bug occurs
15. Bug Report
2.6 Actual Methodology Followed
2.7 Actual Resources Required
2.8 Outputs of the Micro-Project
2.9 Skill Developed/ Learning outcomes of this
Micro-Project
2.10 Application of Micro-Project
16. Annexure IV
 Annexure-1

PART-A Micro-project Proposal TITLE:

“Examination and Result Management System”.

1.0 Aims/benefits of the Micro-Project:

The goal of this project is to provide a mobile application for all the students and teachers and Institute’s
administrator, to build an online system to manage all the records related to examination and result of students
and teachers to ease the service of examination and result management.
• Our aim is for the automation of Result Management.
• To help the student/teachers associated with managing of the examination and results.
• To make the day to day work easier.
• It can be used in any Schools, Colleges or tuitions for maintaining exam or results details.

2.0 Course Outcomes Addressed:

• Apply various software testing methods.
• Prepare test cases for different types and levels of testing.
• Prepare test plan for an application.
• Identify bugs to create defect report of given application.

3.0 Proposed Methodology:

Firstly, we will select the topic with the help of subject teacher. Then all group members will start to collect the
information related to topic. Firstly we need to get the knowledge about how to build a program. Also we will
need a brief study on the requirements of project. After that we will collect of the information together and
make a plan on it. After that we will discuss that how to build a program. Then we will start building a program.
Then we will show the resultant output to teacher. Then finally we will show it to the teacher for final correction.
Then after collecting all the necessary information we will start to combine it together and arrange it in a proper
way then we will make word document by using all the information for making it more effective we will add
some picture related to the topic. Then we will show it to subject teacher and ask for the changes if any. Then
finally we will make report on the project and submit to the teacher.

4.0ACTION PLAN:
Sr. No. DETAILS PLANNED START PLANNED NAME OF
OFACTIVITY DATE FINISH DATE RESPONSIBLE
TEAM MEMBERS

1. Confirmation of topic 07-09-2023 08-09-2023 Riya Godse

Tejaswini Rathod
and collection of [1 hour]
Saloni Pawar
information Aditi Chaudhari

2. Requirement 11-09-2023 16-09-2023

gathering, [3 hours] Riya Godse
Tejaswini Rathod
confirmation Saloni Pawar
of process Aditi Chaudhari
model, etc.

3. Preparing broad SRS, 16-09-2023 20-09-2023 Riya Godse

Tejaswini Rathod
Developing Diagrams [2:30 hours]
Saloni Pawar
Aditi Chaudhari

4. Preparing risk 20-09-2023 25-09-2023

management plan, Size [3 hours] Riya Godse
Tejaswini Rathod
and cost
Saloni Pawar
estimation Aditi Chaudhari

5. Creating 25-09-2023 5-10-2023 Riya Godse

code, execution [2 hours] Tejaswini Rathod

Saloni Pawar
and error solving Aditi Chaudhari

6. Making Test Cases, 5-10-2023 15-10-2023 Riya Godse

Tejaswini Rathod
Time line chart and [2 hours] Saloni Pawar
Gantt chart Aditi Chaudhari

7. Making SQA Plan, and 16-10-2023 29-10-2023 Riya Godse

bug report Tejaswini Rathod
Saloni Pawar
[1 hour] Aditi Chaudhari

8. Making 29-10-2023 05-11-2023 Riya Godse

project Tejaswini Rathod
[1 hour]
Saloni Pawar
document file, User Aditi Chaudhari
Manuals, etc.
9. Submitting To The 06-11-2023 07-11-2023 Riya Godse
Tejaswini Rathod
Teacher [30 Minutes]
Saloni Pawar
Aditi Chaudhari
5.0 Resource Required:
Sr. No. Name of Specification Quantity
Resources/material
1 Computer Specification with Operating System: Windows 11 1
broad based specifications Processor: AMD Ryzen 5 3550H
RAM: 8GB
System type: 64-bit Operating System

2 Software Microsoft Word 2010 1

3 Mobile Phone Processor: Qualcomm Snapdragon 665 1

RAM: 4 GB
Model: RMX 1911
MINIMUM SOFTWARE AND HARDWARE SPECIFICATIONS

Software requirements

Operating System : Windows 11

User interface : Java, Servlets, JSP

Database : My SQL

Documentation Tool : MS. Office

Hardware requirements

Processor : Standard processor with a speed of 1.6 GHz or more

RAM : 256 MB RAM or more

Hard Disk : 20 GB or more

Monitor : Standard color monitor

Keyboard : Standard keyboard

Mouse : Standard mouse

Annexure II
Part-B Micro-Project Report

TITLE: "Examination and Result Management System”.

1.0 Rationale: Thus document lays out a project plan for the development of “Examination and Result
Management System”. The plan will include, but is not restricted to a summary of the system functionality,
the scope of the project from the perspective of the “Result Management System” team (me and my
mentors), project risks and how those risks will be mitigated, the process approach to develop the project,
 and metrics and measurements that will be recorded throughout the project. This document will cover
each of the system’s intended features, as well as offer a preliminary glimpse of the software application’s
User Interface (UI). The document will also cover hardware, software, and various other technical
dependencies.

2.0 Aims/Benefits of the Micro-Project:

The goal of this project is to provide a mobile application for all the students and teachers and
Institute’s administrator, to build an online system to manage all the records related to
examination and result of students and teachers to ease the service of examination and result
management.
• Our aim is for the automation of Examination and Result System.
• To help the people associated with managing of the Exams, Results.
• To make the day to day work easier.
• This Code/ Program includes:Making online results.
Students name, School/College name, Marks, etc.
• It can be used in any School, Colleges or Tuitions for maintaining student results.
• The main aim of our project is to provide a paper-less college up to 30%. It also aims at providing low-
cost reliable automation of the existing systems. The system also provides excellent security of data at
every level of user system interaction and also provides robust & reliable storage and backup facilities.

3.0 Course Outcomes Achieved:

• Apply various software testing methods.
• Prepare test cases for different types and levels of testing.
• Prepare test plan for an application.
• Identify bugs to create defect report of given application.
4.0 Literature Review:-
Sites Used:

• www.code-project.org
• www.slideshare.net
• www.studyttonight.com
• www.qeeksforqeeks.org
• www.TutorialsDuniya.pdf

Books Used:
• Software Engineering: A practitioner’s approach (Pressman, Roger S.)
• Software Engineering Concepts (Fairly, Richard)
Case Study
Current System: The current system in use is a paper-based system. It is too slow and cannot provide
updated lists of students or exams within a reasonable timeframe. The intentions of the system are to reduce
over-time pay. Requirements statements in this document are both functional and non-functional.

Introduction:
Thus document lays out a project plan for the development of “Examination and Result Management System”.
The plan will include, but is not restricted to a summary of the system functionality, the scope of the project
from the perspective of the “Result Management System” team (me and my mentors), project risks and how
those risks will be recorded throughout the project. This document will cover each of the system’s intended
features, as well as offer a preliminary glimpse of the software application’s User Interface (UI). The document
will also cover hardware, software, and various other technical dependencies.

Purpose
The goal of this project is to provide a mobile application for all the students and teachers and Institute’s
administrator, to build an online system to manage all the records related to examination and result of students
and teachers to ease the service of examination and result management. Problem Statement:
In our current examination conduction of exam and computation of result.
It becomes very difficult to manage record of all students manually which results in heap of files.
So, there is always a risk of loss of information due to various reasons.
Also, there is imbalance between the man power availability and magnitude of the examination work which
results in inaccuracy and delay in declaration of result.
Our software is designed to efficiently manage all the records of the students, automatically calculate the
percentage and grade point of the students.
With the use of our software, the span required for declaration of result and use of man power will be reduced
Scope:
to great extent.
The “Examination and Result Management System” is a mobile application, which helps students and teachers
to find all the up-to-date information related to examination and result.

The Examination and Result Management System is composed of two main components: a client-side
application which will run on Android handsets and a server-side verifies logins as Student, Teacher of
Administrator and manages user information. The data will be held in an Access database on the server. The
administrator logins to upload information about creating/updating a record of a student or a teacher, or handle
the complaints and queries put forward by students/teachers.

Prototyping Model:
Often, customer defines a set of general objectives for software but does not identify detailed input, processing,
or output requirements. In other cases, the developer may be unsure of the efficiency of an algorithm, the
adaptability of an operating system, or the form that human/machine interaction should take. In these, and
many other situations, prototyping paradigms offer the best approach.
• The prototyping paradigm begins with requirements gathering. Developer and customer meet and
definethe overall objectives for the software.
• A "quick design" then occurs. The quick design focuses on a representation of those aspects of the
softwarethat will be visible to the customer/user (e.g., input approaches and output formats).
• The quick design leads to the construction of a prototype. The prototype is evaluated by the customer
andused to refine requirements for the software to be developed.
• Iteration occurs as the prototype is tuned to satisfy the needs of the customer, while at the same
timeenabling the developer to better understand what needs to be done.
• Ideally, the prototype serves as a mechanism for identifying software requirements. If a working
prototype isbuilt, the developer attempts to use existing program fragments or applies tools that enable working
programs to be generated quickly.

Advantages:
1. Customers can see the prototype earlier, so customer knows what actually he/she is getting.
2. Unexpected requirements can be accommodated.
3. Allows for flexible design and development.
4. Interaction with the prototype stimulates awareness of additional needed functionality.
5. Steady, visible signs of progress produced.

Disadvantages:
1. The customer just views the appearance of working version of the software. But due to rush to
get it done quickly affects overall quality or long-term maintainability of software product.
2. Product may need to rebuild to maintain high quality.
3. The developer often makes implementation compromises in order to get a prototype working
quickly. An inappropriate operating system or programming language may be used; an inefficient
algorithm may be implemented simply to demonstrate capability.
4. Chances of getting less-than-ideal system are too high.
 Cost Estimation
We have used COCOMO2 model for the cost estimation of our project.

• COCOMO2 (COnstructive COst MOdel 2) is an algorithmic cost estimation technique proposed by

Boehm, which works in a bottom-up manner.
• It is designed to provide some mathematical equations to estimate software projects.
• These mathematical equations are based on historical data and use project size in the form of KLOC.
• The COCOMO model uses a multivariable size estimation model for effort estimation.

Object Point = ∑3 i=1 ∑3 i=j Cij * Wij

SIMPLE MEDIUM COMPLEX

SCREENS 1 3 2
REPORT 1 3 1
3GL 0 0 1
 = (1*1 + 3*2 + 2*3) + (1*2 + 3*5 + 1*8) + (1*10)
= 13 + 25 + 10
= 48

 NOP = Object Point * (1 - %reuse/100)

= 48 * (1-0)
= 48

 Efforts = NOP/PROD
= 48/13
= 3.7
NOP= New Object Point
PROD= Productivity
We have assumed nominal developer experience.

Code
// Mark sheet Generation Using Array
#include<iostream>
#include<stdlib.h> using
namespace std; int
main()
{
int rollno,sem,java,se,gad,dccn,mic,total;
char name[70],school_name[30];
cout<<"Enter your Roll No:"; cin>>rollno;
cout<<"Marksheet of Semester:";
cin>>sem; cout<<"Enter your
Name:";
cin>>name; //gets(name);
cout<<"Enter your School Name:";
cin>>school_name; //gets(school_name);
cout<<"Enter your Semester:"; cin>>std; cout<<"Enter marks
of JAVA:"; cin>>java;
cout<<"Enter marks of Software Engineering:"; cin>>se;
cout<<"Enter marks of GUI Application:"; cin>>gad;
cout<<"Enter marks of Data Communication and Network:"; cin>>dccn;
cout<<"Enter marks of Microprocessor:";
cin>>mic;
cout<<"==================================================="<<endl;
cout<<"MARKSHEET OF SEMESTER:"<<sem<<endl;
cout<<"---------------------------------------------------"<<endl;
cout<<"School Name:"<<school_name<<endl;
cout<<"==================================================="<<endl;
cout<<"Roll No:"<<rollno<<endl; cout<<"Name:"<<name<<endl;
cout<<"---------------------------------------------------"<<endl; cout<<"SUBJECT
\t\t\tMARKS\n";
cout<<"---------------------------------------------------"<<endl;
cout<<"JAVA \t\t\t"<<java<<endl; cout<<"Software
Engineering\t\t\t"<<se<<endl; cout<<"GUI Application
\t\t\t"<<gad<<endl;
cout<<"Data Communication and Network\t\t"<<dccn<<endl;
cout<<"Microprocessor \t\t"<<mic<<endl; cout<<"--------
-------------------------------------------\n"; cout<<"Total";
total=java+se+gad+dccn+mic; cout<<"\t
\t\t\t"<<total<<endl;
cout<<"===================================================\n"<<endl;
cout<<"Percentage \t\t"<<total/5.0<<" %"<<endl;
cout<<"===================================================\n";
}

Note: Every system needs some modification after an interval of time because as the time passes every
current system becomes less and less effective. This project gives small information. This project has further
scope by doing some modifications in it.
Write test case to validate requirements of assigned project from SRS document. Testing

Testing:
Methodologies
Black box Testing.
White box Testing.
Gray Box Testing.

The process of executing a system with the intent of finding an error.

Testing is defined as the process in which defects are identified, isolated, subjected for rectification and
ensured that product is defect free in order to produce the quality product and hence customer
satisfaction.
Quality is defined as justification of the requirements
Defect is nothing but deviation from the requirements
Defect is nothing but bug.
Testing --- The presence of bugs
Testing can demonstrate the presence of bugs, but not their absence Debugging
and Testing is not the same thing!
Testing is a systematic attempt to break a program or the AUT
Debugging is the art or method of uncovering why the script /program did not execute properly.

Testing Methodologies:

Black box Testing: is the testing process in which tester can perform testing on an application without
having any internal structural knowledge of application.
• Usually Test Engineers are involved in the black box testing.
White box Testing: is the testing process in which tester can perform testing on an application with
having internal structural knowledge.
• Usually The Developers are involved in white box testing.
Gray Box Testing: is the process in which the combination of black box and white box techniques are
used.
 Example for GUI Test cases:
T.C. No Description Expected value Actual value Result

Check for all the features in the The screen must contain all the
1 screen features

Check for the alignment of the The alignment should be

2 objects as per the validations in proper way

Positive Test Cases:

The positive flow of the functionality must be considered

Valid inputs must be used for testing

Must have the positive perception to verify whether the requirements are justified.

Example for Positive Test cases:

T.C. No Description Expected value Actual value Result

Check for the date Time The date and time of the system Correct date and Pass
1 must be displayed time displaying
Auto Display

Enter the valid Roll no into the It should accept Accepting Pass
2 student roll no field

Negative Test Cases:

Must have negative perception.

Invalid inputs must be used for test.

 Example for Negative Test cases:
T.C. No Description Expected value Actual value Result

Try to modify the information in Modification should not Not allowing Pass
1 date and time be allow

Enter invalid data in to the It should not accept invalid Not Pass
data, save should not allow accepting
2 student details form, click on
Save

Test Cases
Test Cases for Login Module
Test Test Case Input Expected Actual Status
Case ID Description Data Result Result
TC01 Verify Valid full name Full Name Full Name was Pass
registering user- should be accepted
Full Name accepted
TC02 Validate name String data Raise an Display a Pass
field exception when message when
the we don’t enter
Input field is any name
empty.
TC03 Register by If username is Error message Register by Pass
entering not unique then “This username entering
username message already exists” username
“This username was prompted.
already exists”
must be
prompted else
username
should be
accepted

TC04 Validate mobile Successfully Successfully Number Pass

number input if mobile input if mobile Accepted
no = no =
10 digits 10 digits
Successfully Successfully
TC05 Verify Valid mobile Mobile Mobile number Pass
registering number number must was accepted
userValid be accepted
mobile number
TC06 Verify Email Error message Error message Verify Email Pass
Address “Incorrect email was displayed Address
format” must be
displayed
TC07 Verify Valid Email Email must be Email was Pass
registering user- accepted accepted
Valid Email
TC08 Verify Invalid Email Error message Error message Pass
registering user- (abc@pqr) “Incorrect email was displayed
Invalid Email format”

must be
displayed
TC09 Verify login 4 digit valid 4 digit Login pin Login pin was Pass
pin(password) login pin should be accepted
functionality accepted
during
registering
TC10 Validate String data Raise an Display a Pass
Password field exception message when
when the we don’t enter
input field is any name
empty.
TC11 Validate confirm Password System should Displayed Pass
password should be same display a message when
as you enter in message that password is not
the password “password matching.
field. doesn’t match”
TC12 Validate address String data Should not be Prompts to Pass
field empty enter the
location
TC13 Delete product Message “Are Message was Delete product Pass
you sure you prompted
want to delete correctly
product ID: id?”
should be
prompted
TC14 Verify search Enter Item List of items List of items was Pass
item Name must be displayed
functionality displayed to the
user
TC15 Check register Button Should redirect Redirecting to Pass
button to home page the homepage.
TC16 Verify Invalid mobile Error message Error message Pass
registering number “Mobile was displayed
userInvalid (12343253) number must
mobile number be of 10 digits”
must be
displayed
TC16 Check admin Login id & pass Successfully Successfully Pass
login login login
 Risk Management Plan
Risk always involves two characteristics:
• Uncertainty- The risk may not happen. There are no 100% probable risks.
• Loss- If a risk becomes a reality, unwanted consequences or losses will occur.

The goal of the risk mitigation, monitoring and management plan is to identify as many potential risks as possible.
The project will be analyzed to determine any project-specific risks.

• When all risks have been identified, they will be evaluated to determine their probability of occurrence.
Plans will be made to avoid each risk, to track each risk to determine if it is more or less likely to occur,
and to plan for those risks should they occur.
• It is the organization’s responsibility to perform risk mitigation, monitoring, and management in order to
produce a quality product.
• The quicker the risks can be identified and avoided, the smaller the chances of having to face that
particular risk’s consequence. The fewer consequences suffered as a result of good RMMM plan, the
better the product and the smoother the development process.

Risk Table:
Risks Category Probability Impact
Computer Crash Technical Risk 70% 1
Late Delivery Project Risk 30% 1
End Users Resist System Project Risk 20% 1
Changes in Requirements Project Risk 20% 2
 Timeline Chart:
Task Name/ Steps Start Date End Date

Preliminary Investigation 15-09-2021 20-09-2021

Designing 22-09-2021 01-10-2021
Size and Cost Estimation 03-10-2021 07-10-2021
Creating Code 09-10-2021 18-10-2021
Implementation 20-10-2021 22-10-2021
Testing 24-10-2021 26-10-2021
User Manual 24-10-2021 26-10-2021
Final Report 29-10-2021 02-11-2021
Training 04-11-2021 08-11-2021

Gantt Chart:
Task Name/ Steps 11 to 30-04-2021 02 to 31-05-2021 01 to 08-
06-2021
Preliminary 15-20
Investigation
Designing 22-
01
Size and Cost Estimation 03-07

Creating Code 09-18

Implementation 20-
22
Testing 24-
26
User Manual 24-
26
Final Report 29-
02
Training 04-08

Prepare SQA plan that facilitates various attributes of quality of process of project.
Software Quality Assurance (SQA) Plan, Audit and Review:
After completion of the seven phases of testing, the results looking good, no significant issues occurred
in the project. You managed the project well, and you were proud of the success of this project.
Unfortunately, the management Board thinks different. You don’t have any evidence to show that you
managed this project well. You asked an advisor for a solution, here is the answer:-
This answer is start, but you still have following questions:

What
What is the Test Management Reviews and Audit?

Why
Why do wee need the SQA in Test Managemt process?

How
How to implement the quality assurance?

What is the Test Management Reviews and Audit?

Management Review: Management Review is known as software Quality Assurance or (SQA). It
focuses more on the software process rather than the software work products. Quality Assurance is a
set of activities designed to ensure that the project manager follows the standard process which is
already pre-defined. In other words, Quality Assurance makes sure the Test Manager is doing the right
things in the right way.
Audit: An audit is the examination of the work products and related information to assesses whether
the standard process was followed or not.

Why do we need SQA in Test Management Process?

To understand this, consider the following scenario:-
In the project various test phase’s like-

Report
Issue
Management
Monitoring
Organization and control

Planning
Estimation
Risk
Analysis

As a Test Manager, you are the person who takes in charge these activities. However, you are at the highest
position in the project team. Who will review your tasks and check the project management activities are
executed to the highest standard?
Well, SQA auditor is the person who reviews and checks the project management activities are executed to
the highest possible standard. Only through the result of this review, the Management Board can evaluate the
quality of your project handling.
This is the reason why we do need Management Review or SQA in Test Management process.
The SQA interviews you, the Test Manager to benchmark the project against set standards.
Benefits of SQA are:

Monitoring and improving the process.

Make sure that the standards and procedure are followed.
Preventing the quality problems from accruing.
How to implement the quality assurance?
Steps:-

Develop SQA plan.

Preparation
Review the process.
Step 1: Develop SQA plan .
 Testing activity needs Test Plan likewise SQA activity also needs a plan which is called SQA plan.
The goal of SQA plan is to craft planning process and procedures to ensure products manufactured or
the service delivered by the organization are of exceptional quality.
During project planning, Test Manager makes on SQA plan where SQA audit is scheduled periodically.
Step 1.1: Identify the role and responsibilities of SQA team

In a project team, every member must have responsibility for the quality of his or her work. Each person
has to make sure their work meet the SQA criteria.
The SQA team is the group of person who plays the major role in the project. Without SQA, no business
will run successfully. Therefore, the Test Manager has to make clear the responsibility of each SQA member in
SQA plan as below:

• Review and evaluate the quality of project activities to meet the SQA criteria.
• Co-ordinate with management board and project teams to assess requirements and engage in project
review and status meetings.
• Design track and collect metrics to monitor project quality.
• Measure the quality of product; ensure the product meet the customer expectations.
Step 1.2: List of the work products that the SQA auditor will review and audit.

The Test Manager should

• List out all the work products of each Test Manager Process.
• Define which facilities or equipment the SQA auditor can access to perform SQA tasks such as process
evaluation and audits.
Step 1.3: Create the schedule to perform the SQA tasks.

In this step, the Test Manager should describe the tasks to be performed by SQA auditor with special
emphasis on SQA activities as well as the work product for each task.
Test Manager also creates the scheduling of those SQA tasks. Normally the SQA schedule is driven by the project
development schedule. Therefore an SQA task is performed in relationship to what software development
activities are taking place.

Step 2: Define the standards/ methodology

To review the Management activities against the standards process, you should do the following steps:
Define the policies and procedures intended to prevent defects from accruing in the management process.
• Document the policies and procedures.
• Inform and train the staff to use it.
Step 3: Review the process
Review project activities to verify compliance with the defined management process. In the management
review, the SQA members have management review, the SQA members have to perform 5 SQA reviews as
following.
In each SQA phase, the SQA members provide consultation and review of the project plans, work product and
procedures regarding compliance to defined organizational policy and standard procedures.

During audit, the SQA members should use SQA review checklist.
After you walk through the step 3 of software assurance implementation you have the result of Test
Management Review and Audit. This is the evidence to show to your stakeholders about your management
quality.
Software quality assurance best practice:

Continuous Improvement: All the standard process in SQA must be improved frequently and made official so
that the other can follow. This process should be certified by popular organization such as ISO, CMMI, etc.
Documentation: All the SQA Policies and methods, which are defined by SQA team, should be documented for
training and reuse for future projects.
Experience: Choosing the members who are seasoned SQA auditors is a good way to ensure the quality of
management review.
Tool Usage: Utilizing tool such as the tracking tool, management tool for SQA process reduces SQA effort and
project cost.
Metrics: Developing and creating metrics to track the software quality in its current state, as well as to current
state, as well as to compare the improvement with previous versions, will help increase the value and maturity
of the Testing the value and maturity of the Testing process.
Responsibility: The SQA process is not the SQA member’s task, but everyone’s task. Everybody in the team is
responsible for quality of product, not just the tester, leader or manager.

What is a bug in software testing?

The Bug is the informal name of defects, which means that software or application is not working as per the
requirement.

In Software Testing
A software bug can also be issue, error, fault, or failure. The bug occurred when developers made any mistake
or error while developing the product.

While testing the application or executing the test cases, the test engineer may not get the expected result as
per the requirement. And the bug had various names in different companies such as error, issues, problem,
fault, and mistake, etc.
Basic terminology of defect
Let see the different terminology of defect:

• Defect
• Bug
• Error Issue
• Mistake
• Failure
Terms Description Raised by
Defect When the application is not working Test Engineer
as per the requirement.
Bug Informal name of defect Test Engineer

Error Problem in code leads to the Developer, Automation Test

errors. Engineer
Issue When the application is not Customer
meeting the business requirement.
Mistake Problem in the document is known --
as a mistake.
Failure Lots of defect leads to failure of the --
software.
Why Defect/bug occur?
In software testing, the bug can occur for the following reasons:

• Wrong coding
• Missing coding
• Extra coding
Wrong coding
Wrong coding means improper implementation.
For example: Suppose if we take the Gmail application where we click on the "Inbox" link, and it navigates to
the "Draft" page, this is happening because of the wrong coding which is done by the developer, that's why it is
a bug.
Missing coding
Here, missing coding means that the developer may not have developed the code only for that particular
feature.

For example: if we take the above example and open the inbox link, we see that it is not there only, which
means the feature is not developed only.
Extra coding
Here, extra coding means that the developers develop the extra features, which are not required according to
the client's requirements.
For example:
Suppose we have one application form wherein the Name field , the First name , and Last name textbox are
needed to develop according to the client's requirement.
But, the developers also develop the "Middle name" textbox, which is not needed according to the client's
requirements as we can see in, the below image:

If we develop an extra feature that is not needed in the requirement, it leads to unnecessary extra effort. And
it might also happen that adding up the extra feature affects the other elements too.
 Bug Report
Here is a sample Bug Report for the above mentioned example
(Note that some ‘Bug Report’ fields might differ depending on your bug tracking system) Bug
Name: Application crashes upon clicking the SAVE button while creating a new user.
Bug ID: (It will be automatically created by the BUG Tracking tool once you save this bug).
Area Path: USERS menu -> New Users
Build Number: Version Number 5.0.1
Severity: HIGH (High/ Medium/ Low) or 1
Priority: HIGH (High/ Medium/ Low) or 1
Assigned to: Developer
Reported By: Jay Pardakhe
Reported On: 27-10-2021
Reason: Defect
Status: New/Open/Active (Depends on the Tool you are using)
Environment: Windows 2003/SQL Server 2005
Description: Application crashes upon clicking the SAVE button while creating a new the user, hence unable to
create a new user in the application.

Steps to Reproduce:
1) Login into the Application.
2) Navigate to the Users Menu -> New User
3) Filled out all the user information fields.
4) Clicked on the ‘Save’ button.
5) Seen an error page “ORA1090 Exception: Insert values Error…”
6) See the attached logs for more information (Attach more logs related to the bug if any)
7) Also see the attached screenshot of the error page.

Expected Result: On clicking the SAVE button, you should be prompted to a successful message “New User
has been created successfully” (Attach ‘application crash’ screenshot if any)

Save the Defect/Bug in the BUG TRACKING TOOL. You will get a Bug ID that you can use for further bug
reference.
Default ‘New Bug’ mail will go to the respective developer and the default module owner (Team leader or
manager) for further action.
5.0 Actual Methodology Followed:
Firstly, we select the topic with the help of subject teacher. Then all group members started to collect the
information related to topic. Then after collecting all the necessary information we started to combine it
together and arrange it in a proper way then we made word document by using all the information for making
it more effective we will add some picture related to the topic. Then we showed it to subject teacher and ask
for the changes if any. Then finally we made report on the project and submit to the teacher.

6.0 Actual Resources Required:

Sr. No. NAME OF RESOURCES SPECIFICATION Quantity
1 Computer Specification with Operating System: Windows 10
broad based specifications Processor: AMD Ryzen 5 3550H
RAM: 8GB 1
ROM: 1TB
System type: 64-bit Operating System
2 Software Microsoft Word 2010,
4
Code blocks, Turbo C++, DEV C++
3. Mobile Phone Processor: Qualcomm Snapdragon 665
RAM: 4 GB 1
Model: RMX 1911
4 Books • Software Engineering: A
practitioner’s approach (Pressman,
Roger S.)
• Software Engineering Concepts
(Fairly, Richard)
4
• Object Oriented Programming with
C++ (Balgurusamy,E.)
• Software Testing Principles,
Techniques and Tools (Chauhan
Naresh), etc.
5 Websites • www.code-project.org
• www.slideshare.net 5
www.studyttonight.com,
• www.selenium.com , etc.
7.0 Outputs of the Micro-Project:
8.0 Skill Developed/ Learning outcomes of this Micro-Project:
Gain knowledge of how to handle Code blocks, DEV C++ and Turbo C++ software.
We learned how to actively work in group.
We learned how to collect information and create report.
Presentation skills are developed after completing Micro-project.
Gain knowledge of how to prepare Test Plans, Test Cases, Gantt chart, Timeline Chart, etc.

9.0 Application of Micro-project :

It can be used in any Hospital, Clinic and Dispensary of Pathology labs for maintaining patient details. The
existing project is user friendly and helps in fields of management also. We made this project for the
automation of Hospital Application Form and its management. In this project we add patient details like its
date of admission, name of disease, discharge date, etc. This project just gives a simple idea how a record of
various doctors and patients can be kept in hospital. With better knowledge of C++ and the use of more
functions, the program can be made more users friendly and practically applicable.
 Annexure IV
Micro Project Evaluation Sheet
Name of Student: Enrollment No:
Name of Programme: Semester: 5 th

Jay Surendra Pardakhe 1901350034

Sr. Characteristic to be assessed Poor Average Good Excellent Sub

No. (Marks 1-3) (Marks 4-5) (Marks 6-8) (Marks 9-10) Total
(A) Process and Product Assessmen t (Convert above total marks out of 6 Marks)
1 Relevance to the course
2 Literature Review/information
collection
3 Completion of the Target as per
project proposal
4 Analysis of Data and
representation
5 Quality of Prototype/Model
6 Report Preparation
(B) Individual Presentation / Viva (Convert above total marks out of 4 Marks)
7 Presentation
8 Viva

…………………………………………………………………………………………………………………….
(A) (B) Total Marks
.
Process and Product Assessment Individual Presentation/Viva 10
…………………………………………………………………………………………………………………….
. (6 marks) (4 marks)

Name and designation of the Teacher ………………………………………………

Dated Signature…………………………………………………………………….....
 Annexure IV
Micro Project Evaluation Sheet
Name of Student: Enrollment No:
Name of Programme: Semester: 5 th

Computer Engineering
Course Title: Software Testing Code: 22518

Title of the Micro-Project: Examination and Result Management System.

Course Outcomes Achieved:-
a) Apply various software testing methods.
b) Prepare test cases for different types an levels of testing.
c) Prepare test plan for an application.
d) Identify bugs to create defect report of given application.
e) …………………………………………………………………………………………………….

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

Name and designation of the Teacher ………………………………………………

Dated Signature…………………………………………………………………….....
 Annexure IV
Micro Project Evaluation Sheet
Name of Student: Enrollment No:
Name of Programme: Semester: 5 th

Comments/Suggestions about team work/leadership/inter-personal Communication (if any)

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

Name and designation of the Teacher ………………………………………………

Dated Signature…………………………………………………………………….....
 Annexure IV
Micro Project Evaluation Sheet
Name of Student: Enrollment No:
Name of Programme: Semester: 5 th

Devesh Anand Pande 1901350068

Sr. Characteristic to be assessed Poor Average Good Excellent Sub

No. (Marks 1-3) (Marks 4-5) (Marks 6-8) (Marks 9-10) Total
(C) Process and Product Assessmen t (Convert above total marks out of 6 Marks)
1 Relevance to the course
2 Literature Review/information
collection
3 Completion of the Target as per
project proposal
4 Analysis of Data and
representation
5 Quality of Prototype/Model
6 Report Preparation
(D) Individual Presentation / Viva (Convert above total marks out of 4 Marks)
7 Presentation
8 Viva

…………………………………………………………………………………………………………………….
(A) (B) Total Marks
.
Process and Product Assessment Individual Presentation/Viva 10
…………………………………………………………………………………………………………………….
. (6 marks) (4 marks)

Name and designation of the Teacher ………………………………………………

Dated Signature…………………………………………………………………….....
 Annexure IV
Micro Project Evaluation Sheet
Name of Student: Enrollment No:
Name of Programme: Semester: 5 th

Computer Engineering
Course Title: Software Testing Code: 22518

Title of the Micro-Project: Examination and Result Management System.

Course Outcomes Achieved:-
a) Apply various software testing methods.
b) Prepare test cases for different types an levels of testing.
c) Prepare test plan for an application.
d) Identify bugs to create defect report of given application.
e) …………………………………………………………………………………………………….

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

Name and designation of the Teacher ………………………………………………

Dated Signature…………………………………………………………………….....
 Annexure IV
Micro Project Evaluation Sheet
Name of Student: Enrollment No:
Name of Programme: Semester: 5 th

Comments/Suggestions about team work/leadership/inter-personal Communication (if any)

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

Name and designation of the Teacher ………………………………………………

Dated Signature…………………………………………………………………….....
 Annexure IV
Micro Project Evaluation Sheet
Name of Student: Enrollment No:
Name of Programme: Semester: 5 th

Pavan Tolaram Rathod 1901350069

Sr. Characteristic to be assessed Poor Average Good Excellent Sub

No. (Marks 1-3) (Marks 4-5) (Marks 6-8) (Marks 9-10) Total
(E) Process and Product Assessmen t (Convert above total marks out of 6 Marks)
1 Relevance to the course
2 Literature Review/information
collection
3 Completion of the Target as per
project proposal
4 Analysis of Data and
representation
5 Quality of Prototype/Model
6 Report Preparation
(F) Individual Presentation / Viva (Convert above total marks out of 4 Marks)
7 Presentation
8 Viva

…………………………………………………………………………………………………………………….
(A) (B) Total Marks
.
Process and Product Assessment Individual Presentation/Viva 10
…………………………………………………………………………………………………………………….
. (6 marks) (4 marks)

Name and designation of the Teacher ………………………………………………

Dated Signature…………………………………………………………………….....
 Annexure IV
Micro Project Evaluation Sheet
Name of Student: Enrollment No:
Name of Programme: Semester: 5 th

Computer Engineering
Course Title: Software Testing Code: 22518

Title of the Micro-Project: Examination and Result Management System.

Course Outcomes Achieved:-
a) Apply various software testing methods.
b) Prepare test cases for different types an levels of testing.
c) Prepare test plan for an application.
d) Identify bugs to create defect report of given application.
e) …………………………………………………………………………………………………….

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

Name and designation of the Teacher ………………………………………………

Dated Signature…………………………………………………………………….....
 Annexure IV
Micro Project Evaluation Sheet
Name of Student: Enrollment No:
Name of Programme: Semester: 5 th

Comments/Suggestions about team work/leadership/inter-personal Communication (if any)

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

Name and designation of the Teacher ………………………………………………

Dated Signature…………………………………………………………………….....