Micro Project report on

STUDENTS INFORMATION SYSTEM APPLICATION

Academic Year: 2022-2023 Institute Code: 0563

Program: Computer Engineering [First Shift] Semester: V

Course: Software Testing Code: 22518

Group No: 16

Maharashtra State Board of Technical Education, Mumbai

(Autonomous) (ISO-9001-2008) (ISO/IEC 27001:20013
 Maharashtra State Board of Technical Education,
Mumbai

CERTIFICATE
This is to certify that,
Roll Student Name Seat No Enroll No.
No

4 Shubham Khaladkar 2005630053

5 Tejas Patil 2005630089

6 Subrato Mandal 2005630108

Of Fifth semester of Diploma in Computer Engineering (First

Shift) of Institute Pravin Patil College of Diploma Engineering
and Technology, Bhayandar E (Code: 0563) has completed the
Micro Project satisfactorily in subject Software Testing (STE-
22518) for the academic year2021-2022 as prescribed in the
curriculum

Place: Bhayandar (E)

Date: _______________

__________________ __________________ __________________

Mr. Nilesh Vispute Mr. Hitesh Mhatre Mrs. Ranjana Patil
 PART A – Plan
STUDENTS INFORMATION SYSTEM APPLICATION
1.0 Rationale:
This software design specification is made with the purpose of outlining the software
architecture and design of the Student Registration System in detail. The document
will provide developers an insight in meeting client’s needs efficiently and effectively.
Moreover, the document facilitates communication and understanding of the system
by providing several views of the system design.
It has described architectural design of the Student Registration System. The high-
level components and their interactions, suitable architectural patterns, physical
arrangement of components and design decisions applied to the whole system. The
and chapter of the System Design Specification is on Component and detailed design.
Includes design patterns, sequence diagrams, class diagrams, database design in detail
and user in-terface design with screen shots of the interfaces.

2.0 Literature Review

It is in this regard that this research looks at the student registration system at Methodist 2
Literature Review 2.1 Introduction In a rapidly emerging world of group of online students
to be women, over 25 years of age, who worked more. Comments from the literature
attribute this to the fact that everyone's point is. best system to the honor code was where
the faculty took control of proctoring. Important...! About online student registration
system literature review is Not Asked Yet?. Please ASK FOR online student registration
system literature review BY Technical College, Wisconsin. Study procedures included the
following: a literature review, criteria identification, drawing a sample of students,
organization and Online Student Registration System

Online Registration. An online student registration system streamlines the application,

registration, and monitoring of students in a Literature Review .. electronic student's
records, course catalogue, online career development, . registration system) student records
store in mainframe. availability and consistency required by the student registration system
without are well-known in the research literature.

3.0 Proposed Methodology

• Identification of bugs
• Analysis of buys
• Estimation by metrics
• Apply Manual and Automation Testing method
• Selection of method preferred by purpose, estimation and analysis
3.0 Action Plan
Sr. No Details of Activity Planned Planned Name of
Start Date Finish Date Responsible
Members
1 Understand the Work 20-08-22 27-8-22 Shubham

2 Information Gathering 27-8-22 3-9-22 Tejas

3 Analyzing the Activity Subrato

3-9-22 10-9-22
4 Project Schedule 10-9-22 17-9-22 Shubham

5 Confusion Cleared 17-9-22 24-9-22 Subrato

6 Editing and Proofreading Tejas

24-9-22 1-10-22
7 Report Making 24-9-22 1-10-22 Shubham

8 Report Print out & Mailing 9-12-22 9-12-22 Shubham

4.0Resources Required
Sr.N Name of Resource Specification Qty Remarks
o
1 Microsoft Excel 2018 1 Available

2 Microsoft Word 2016 1 Available

3 Selenium IDE Version 1 Available

3.141.59
 PART B – Plan
STUDENTS INFORMATION SYSTEM APPLICATION

1.0 Rationale
This software design specification is made with the purpose of outlining the software
architecture and design of the Student Registration System in detail. The document
will provide developers an insight in meeting client’s needs efficiently and effectively.
Moreover, the document facilitates communication and understanding of the system
by providing several views of the system design.
It has described architectural design of the Student Registration System. The high-
level components and their interactions, suitable architectural patterns, physical
arrangement of components and design decisions applied to the whole system. The
and chapter of the System Design Specification is on Component and detailed design.
Includes design patterns, sequence diagrams, class diagrams, database design in detail
and user in-terface design with screen shots of the interfaces.

2.0 Course Outcomes Integrated

a) Apply various software testing methods.
b) Prepare test cases for different types and levels of testing.
c) Prepare test plan for an application.
d) Identify bugs to create defect report of given application.
e) Test software for performance measures using automated testing tools.

3.0 Literature Review:

It is in this regard that this research looks at the student registration system at Methodist
2 Literature Review 2.1 Introduction In a rapidly emerging world of group of online
students to be women, over 25 years of age, who worked more. Comments from the
literature attribute this to the fact that everyone's point is. best system to the honor code
was where the faculty took control of proctoring. Important...! About online student
registration system literature review is Not Asked Yet?. Please ASK FOR online
student registration system literature review BY Technical College, Wisconsin. Study
procedures included the following: a literature review, criteria identification, drawing
a sample of students, organization and Online Student Registration System
Online Registration. An online student registration system streamlines the application,
registration, and monitoring of students in a Literature Review .. electronic student's
records, course catalogue, online career development, . registration system) student
records store in mainframe. availability and consistency required by the student
registration system without are well-known in the research literature.
4.0 Actual Procedure Followed
- Information Gathering
- Understand the Project/Application Scope, Objective, Features
- Prepare Test Case
- Prepare Test Planning
- Perform Manual Testing and Prepare Bug Report
- Prepare Defect Report for identified Defects
- Test Application using Automation Testing Tool and Generate Test Summary
Report
- Prepare Final Report, Take Print-out

5.0 Actual Resources Used

Sr. No Name of Resource Specification Qty Remarks

1 Microsoft Excel 2018 1 Available

2 Microsoft Word 2016 1 Available

3 Selenium IDE Version 3.141.59 1 Available

6.0 Outputs of the Micro-Project

• Output of the web site:
 ❖ Test Cases of Web Site:
TEST CASES FOR STUDENTS INFORMATION SYSTEM APPLICATION
TEST CASE
TEST CASE DESCRIPTION
ID
NAME and SURNAME
Name and Surname of the Student should not be in numbers
TC_001

TC_002 Name and Surname of the student canot be kept blank

TC_003
Name and Surname of the student cannot be in symbols
Session
TC_004 Student should be able to pick one session
TC_005 Student should make a valid session
TC_006 Student cannot keep the session blank
ROLL NO.
TC_008 Roll no. should be in primary numbers
Branch and Year
TC_009 Student should Pick Current Branch And Year
TC_010 Student cannot pick the invalid year or Branch
TC_011 Shudent cannot keep the branch column blank
TC_012 Student cannot keep the year column blank
TC_013 Student must check if there branch is available or not
Semester
TC_014 Student should Enter valid semester
TC_015
Student cannot keep the column blank

Birth Date
TC_016 Birth should be in numbers
TC_017 Birth cannot be kept blank
Update
TC_018 Student should update its information
TC_019 Student shold check whether if its information is updated or not
 ❖ Test Planning Report:
SAMPLE TEST PLAN TEMPLATE

Name of the Product: STUDENTS INFORMATION SYSTEM APPLICATION

Prepared by:
- Shubham Khaladkar
- Subrato Mandal
- Tejas Patil
TABLE OF CONTENTS
1.0 INTRODUCTION
Student online admissions are vital part of any university’s running because students are
what university alive. The Student admission is one of the most important activities within
a university as one cannot survive without students. A poor admission system can mean
fever students being admitted into a university because of mistakes or an overly response
time. Online Students Registration is the web site which helpful for students as well as the
department. Int his project, the students facilitated by the online system for registering
students details, as well as subjects and fees structure.
OBJECTIVES AND TASKS
2.0 Objectives
• Provide management information for decision making
• Provide easy accessible information for all appropriate
• Provide information that is accurate, secure, consistent, timely, reliable and
complete
2.2 Tasks
1) Click Start, search Net Beans IDE 8.2 and double click to open.
2) To open a project, go to the up left corner of IDE and select projects.
3) All projects in Net Beans will now appear. Navigate to the folder containing
Student registration form .
4) Extend web and select index.html
3.0 Scope
General
Student Registration Form is a login form created by using servlets in Net Beans
through using apache tomcat 8.5 server runtime
Tactics
The HTTP site is including a frame reference to an HTTPS site. Again, the register
form submission is still correct. However, it is possible that the attacker from the
previous scenario could intercept the containing page and change the reference for
the login frame. In this case, the attacker would most likely create a page that is
identical to the real login form and point the frame to that one. The user would have
no idea that the authentication page was incorrect, because it would look like the
original. When the user submits their credentials, they would then be submitted to
the malicious user instead of the real site.
4.0 Testing Strategy
There are many test cases for login form but some following test cases for the testing
purpose.
1. Firstname and Lastname should contain not contain numbers and special
characters.
2. Firstname and Lastname should not be more than 30 characters.
3. Address field must accept proper address and should not contain special characters.
4. Phone no. should contain only integer values.
5. Username should accept 10 characters.
6. Username should not accept special characters.
7. Password must be atleast of 6 Characters.
8. Password should not contain spaces and period.
9. If all fields are filled correctly then it should display Registration Accepted.
4.1 Unit Testing
Definition: Unit testing is a software testing method by which individual units of source
code sets of one or more computer program modules together with associated control data,
usage procedures, and operating procedures are tested to determine whether they are fit for
use.
Participants:
- Shubham Khaladkar
- Subrato Mandal
- Tejas Patil
Methodology:
1. Black Box Testing - Using which the user interface, input and output
are tested.
2. 2. White Box Testing - used to test each one of those functions behaviour
is tested.
4.2 System and Integration Testing
Definition: When two or more modules are combined and tested, it is called integration
testing. After all the modules are combined and the complete system is made, testing of
the whole system is known as System Testing.
Participants:
- Shubham Khaladkar
- Subrato Mandal
- Tejas Patil
Methodology:
1. Big Bang is an approach to Integration Testing where all or most of the units are
combined together and tested at one go.
2. Top Down is an approach to Integration Testing where top-level units
are tested first and lower level units are tested step by step after that.
4.3 Performance and Stress Testing
Definition: Performance testing is the process of determining the speed, responsiveness
and stability of a computer, network, software program or device under a
workload. Performance testing can involve quantitative tests done in a lab, or occur in the
production environment in limited scenarios.
Participants:
- Shubham Khaladkar
- Subrato Mandal
- Tejas Patil
Methodology:
Check the performance quality is different across high-end and low-end devices. Apart
from ensuring the app performs consistently across devices with a lower capacity, a
developer has to ensure the product is capable of handling high server loads as well as
being immune to bandwidth and latency changes. This stage also includes load testing –
increasing the number of incoming traffic to ensure the stability of the application’s
response. As a rule, the approach to such tests is either modular or integrative.
4.4 User Acceptance Testing
Definition: Acceptance testing, a testing technique performed to determine whether or not
the software system has met the requirement specifications. The main purpose of this test is
to evaluate the system's compliance with the business requirements and verify if it is has
met the required criteria for delivery to end users.
Participants:
- Shubham Khaladkar
- Subrato Mandal
- Tejas Patil
Methodology:
• Verify that users can write/type alphabets from a standard keyboard.
• Verify that the user can type numeric from a standard keyboard.
4.5 Batch Testing
Definition: A laboratory testing procedure in which one test is done simultaneously on multiple
specimens
Participants:
- Shubham Khaladkar
- Subrato Mandal
- Tejas Patil
Methodology:
- Batch testing on – login from
4.6 Automated Regression Testing
Definition: Regression testing is the selective retesting of a system or component to verify
that modifications have not caused unintended effects and that the system or component
still works as specified in the requirements.
Participants:
- Shubham Khaladkar
- Subrato Mandal
- Tejas Patil
Methodology:
1. creating test cases in selenium.
2. Recording test cases through selenium
3. Running the recorded test cases
4.7 Beta Testing
Definition: Beta testing is the final round of testing before a product is finally released
to a wide audience. The objective is to uncover as many bugs or usability issues as possible
in this controlled setting.
Participants:
- Shubham Khaladkar
- Subrato Mandal
- Tejas Patil
Methodology:
1. Beta Test Plan.
2. Testing approach to be followed by the participants.
3. Tools used to log bugs, measure productivity, collect feedback – either through
surveys or ratings.
5.0 Hardware Requirements
- At least 4 GB Ram
- Dual core processor with x64 support
- Min 3 GB of HDD free space for JDK, tomcat & Net Beans.
6.0 Environment Requirements
6.1 Main Frame
Testing the application will occur on the following operating systems: Windows 7 /8/10;
6.2 Workstation
• Desktop
• Windows OS
7.0 TEST SCHEDULE
Testing of the Library Issue Book management system form on 03 December 2021.
8.0 CONTROL PROCEDURES
Problem Reporting
Some following problems occurs while testing application:
• Host port is already used when double runed the program.
• Net beans need to running in background for not closing
servlets template of tomcat
• Net Beans lags at starting while opening the IDE due to
Heavy CPU utilization
Change Requests
Using the different details to register with new student in servlet database
9.0 Features To Be Tested
Some features login form
• Verify if the registration form having correct fields with a submit button.
• Verify if the registration form screen having option to enter firstname and lastname.
• Verify if the registration screen having register button.
• Verify if the user is able to register with proper details of him.
• Verify if the user is unable to register with invalid details.
10.0 Features Not To Be Tested
• Working with Help
• Security testing
11.0 Resources/Roles & Responsibilities
Some responsibilities of login form are as follow:
1. Running a registration form in browser
2. Accepting all details of user.
3. Letting user be successfully register when all fields are correctly filled.
4. Don’t let user to register with invalid details.
12.0 Schedules
Major Deliverables
- Test Plan
- Working with the browser and local host
- Logging with registration form.
- Test Cases
• Check the efficiency of the program.
• Check the functionality for the Register button.
• Check if the register form accepts the info of same user.
• Check if the edits to the file are saved.
• Check the functionality of the close, maximize, and minimize buttons.
- Test Incident Reports
- The deadline for completion of all works and delivery of the project is 03/11/2020
24:00:00
- Test Summary Reports
- Testing is done on the web login form application. This login form application was
developed by Microsoft Corporation. While testing test cases some risk, bugs are
identified and some missing functionality also identified.
13.0 Significantly Impacted Departments (SIDs)
• Local File System
• Search History
• Browser URL
• Local hosting
14.0 Dependencies
• Web browsers
15.0 Risks/Assumptions
Possible risks during testing:
• Insufficient human resources for testing the application in deadlines.
• Changing the requirements for the product
16.0 Tools
Following tools are used to test application:
• Net Beans IDE
• Selenium IDE
17.0 Approvals

MR. NILESH VISPUTE

Name Signature Date
 ❖ Bug Report Of Website:
BUG REPORT FOR GOOGLE LOGIN PA

SR TEST CASE TEST TEST

TEST DESCRIPTION TEST DAT
NO ID OBJECT STEPS

1 TC_001.01 shubham***
CHECK WHETHER THE FIELDS
CONTAIN SPECIAL CHARACTER
OR NOT
2 TC_001.02 khalad***
Name
and
Surname CHECK WHETHER THE FIELDS IS
3 TC_001.03 man@@
LEFT BLANK OR NOT

CHECK WHETHER THE FIELD name: njnajnscn

4 TC_002.01
SHOULD NOT EXCEED THE LIMIT
CHECK WHETHER THE TITLE
5 TC_003.01 SHOULD NOT CONTAINS : €¢THE SE
SYMBOL
CHECK WHETHER THE AUTHOR
6 TC_004.01 NAME FIELD CONTAINS surname : 233
INTEGER VALUES OR NOT
CHECK WHETHER THE AUTHOR
7 TC_004.02 FIELD CONTAINS SPECIAL S :¥$€
CHARACTER OR NOT
CHECK WHETHER THE AUTHOR AUTHOR
8 TC_005.01
Session FIELD DON'T EXCEED THE LIMIT
DKFKSLALALSDNCNHSHTOOEEOJFVNN
CHECK WHETHER THE AUTHOR
9 TC_006.01 AUTHOR : THE O
FIELD IS VALID OR NOT
CHECK WHETHER THE ISSUED
10 TC_007.01 TO FIELD SHOULD BE A VALID ISSUED TO : Omkar
NAME
CHECK WHETHER THE ISSUED
TO FIELD CONTAINS INTEGER
11 TC_008.01 ISSUED TO : OMKA
AND SPECIAL CHARACTERS OR
NOT
CHECK WHETHER ISSUED DATE
12 TC_009.01 ISSUED DATE: 25
IS CURRENT DATE OR NOT
roll no.
CHECK WHETHER THE ISSUED
13 TC_010.01 ISSUED DATE: 25
DATE IS IN CORRECT FORMAT
CHECK WHETHER THE FIELD
14 TC_011.01 CONTAINS SPECIAL ISSUED DATE: 25-@
CHARACTERS OR NOT
 CHECK WHETHER THE FIELD
15 TC_012.01 CONTAINS DATE AFTER 30 DAYS RETURN DATE : 2
OF ISSUE DATE
CHECK WHETHER RETURN DATE
16 TC_013.01 RETURN DATE: 2
IS IN CORRECT FORMAT OR NOT

17 TC_014.01 FINE : 1238

CHECK WHETHER THE FINE
FIELD CONTAINS INTEGER
VALUES ONLY
18 TC_014.02 FINE FINE : SJAKA©©

CHECK WHETHER THE FINE

19 TC_015.01 RETURN DATE : 2
FIELD WORKS OR NOT
CHECK WHETHER THE FIELD
20 TC_016.01 CONTAINS ONLY INTEGER PHONE NO: 99203
VALUE OR NOT
CONTACT
21 TC_017.01 FIELD PHONE NO:9920
CHECK WHETHER THE FIELD
EXCEED THE LIMIT OR NOT
22 TC_017.02 PHONE NO: 920012

CHECK WHETHER ALL FIELDS

23 TC_018.01 CHECK ALL FIELDS ARE FI
ARE FILLED CORRECTLY
 ❖ Defect Report:

Defect Report Template 1

ID TC_002.01

Project STUDENTS INFORMATION SYSTEM APPLICATION

Product STUDENTS INFORMATION SYSTEM APPLICATION

Release Version NA

Module STUDENTS INFORMATION SYSTEM APPLICATION

Detected Build NA
Version

Summary Title field exceeded limit of input data i.e 30.

Description While executing test case on Title field when wrong

test input is passed then that field accepted the given
input.
Steps to Replicate NA

Actual Result Title field accepted the Character input data more
than its limit i.e 30 " TITLE : HARRY POTTER AND
THE CHAMBARS OF THE SECRET JSKDKDDKKSKS
"
Expected Results Title field must accept characters less than or equal
30. It must show error when input data is exceeds.
Attachments NA

Remarks Validation for Title field must be done

Defect Probability Probability of defect occurrence is HIGH

Defect Severity HIGH

Defect Priority HIGH

Reported By Shubham Khaladakar, Subrato Mandal, Tejas patil

Assigned To Shubham Khaladakar, Subrato Mandal, Tejas patil

Status FAIL

Fixed Build Version NA

Defect Report Template 2
ID TC_008.01

Project STUDENTS INFORMATION SYSTEM APPLICATION

Product STUDENTS INFORMATION SYSTEM APPLICATION

Release Version NA

Module STUDENTS INFORMATION SYSTEM APPLICATION

Detected Build NA
Version

Summary Issued to field should not accept Integer and special

character .
Description While executing test case on Issued to field when
wrong test input is passed then that field accepted
the given input.
Steps to Replicate NA

Actual Result Issued to field accepted the input i.e 10 "

OMKAR123$¥©"
Expected Results Issued to field must not accept Integer and special
characters. It must show error when special
characters are pass .
Attachments NA

Remarks Validation for Issued to field must be done

Defect Probability Probability of defect occurance is HIGH

Defect Severity HIGH

Defect Priority HIGH

Reported By Shubham Khaladakar, Subrato Mandal, Tejas patil

Assigned To Shubham Khaladakar, Subrato Mandal, Tejas patil

Status FAIL

Fixed Build Version NA

Defect Report Template 3
ID TC_011.01

Project STUDENTS INFORMATION SYSTEM APPLICATION

Product STUDENTS INFORMATION SYSTEM APPLICATION

Release Version NA

Module STUDENTS INFORMATION SYSTEM APPLICATION

Detected Build NA
Version

Summary Issued date field should not accept the special

character .
Description While executing test case on Issued date field when
wrong test input is passed then that field accepted
the given input.
Steps to Replicate NA

Actual Result Issued date field accepted the input i.e " Birth
DATE: 25-@@-263© "
Expected Results Issued date field must not accept special characters.
It must show error when special characters are pass
.
Attachments NA

Remarks Validation for Issued date field must be done

Defect Probability Probability of defect occurrence is HIGH

Defect Severity HIGH

Defect Priority HIGH

Reported By Shubham Khaladakar, Subrato Mandal, Tejas patil

Assigned To Shubham Khaladakar, Subrato Mandal, Tejas patil

Status FAIL

Fixed Build Version NA

Defect Report Template 4
ID TC_017.02

Project STUDENTS INFORMATION SYSTEM APPLICATION

Product STUDENTS INFORMATION SYSTEM APPLICATION

Release Version NA

Module STUDENTS INFORMATION SYSTEM APPLICATION

Detected Build NA
Version

Summary Contact field exceeded limit of input data i.e 10.

Description While executing test case on Contact field when

wrong test input is passed then that field accepted
the given input.
Steps to Replicate NA

Actual Result Contact field accepted the Character input data more
than its limit i.e 10 "Roll no.2005630053"
Expected Results Contact field must accept characters less than or
equal 10. It must show error when input data is
exceeds.
Attachments NA

Remarks Validation for Contact field must be done

Defect Probability Probablity of defect occurance is HIGH

Defect Severity HIGH

Defect Priority HIGH

Reported By Shubham Khaladakar, Subrato Mandal, Tejas patil

Assigned To Shubham Khaladakar, Subrato Mandal, Tejas patil

Status pass

Fixed Build Version NA

❖ Testing Web Site Using Automation Tool:
7.0Skill Developed/Learning out of this Micro-Project
- Gain the Knowledge about testing methods, planning.
- We work as a team.

8.0Applications of this micro project

• Application Software development

• Embedded low end device software’s
• Performance improvement for high scalable software’s
9.0 Area of Future Improvement

• Servlets are portable. You can develop the servlets on one platform and deploy it
on a different platform.
• Session Management is very powerful reason that we can create Using servlets and
for maintain or set we can set the session.
• Servlets are server-independent and do not tie you into a proprietary API like the
Netscape Server API.
 Teacher Evaluation Sheet
Name of Student: Shubham Khaladakar Enrollment No: 2005630053
Name of Program: COMPUTER ENGINEERING Semester: FIFTH
Course Title: SOTFWARE TESTING Code: 224477

Title of the Micro Project: STUDENTS INFORMATION SYSTEM APPLICATION

Course Outcomes Achieved:
a) Apply various software testing methods.
b) Prepare test cases for different types and levels of testing.
c) Prepare test plan for an application.
d) Identify bugs to create defect report of given application.
e) Test software for performance measures using automated testing tools.
Evaluation as per Suggested Rubric for Assessment of Micro-Project
Sr Characteristic to be Assessed Poor Average Good Excellent Sub
. (Marks 1- (Marks 4-5) (Marks 6- (Marks 9- Tota
N 3) 8) 10) l
o
(A) Process and Product Assessment (Covert above total marks out of 6 Marks)
1 Relevance to the course
Literature Survey / Information
2
Collection
Completion of the Target as per
3
project proposal
Analysis of Data and
4
Representation
5 Quality of Prototype/Model

6 Report Preparation
(B) Individual Presentation / Viva (Convert above total marks out of 4 Marks)
7 Presentation
8 Defense

Micro-Project Evaluation Sheet

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

Comments / Suggestions about teamwork / leadership / interpersonal communication:

………………………………………………………………………………………………………………………
Name & Designation of the Teacher: Mr. Nilesh Vispute (Sr. Lecturer-0563)
Dated Signature: ……………………….
 Teacher Evaluation Sheet
Name of Student: Subrato Mandal Enrollment No:2005630108
Name of Program: COMPUTER ENGINEERING Semester: FIFTH
Course Title: SOTFWARE TESTING Code: 224477

Title of the Micro Project: STUDENTS INFORMATION SYSTEM APPLICATION

Course Outcomes Achieved:
a) Apply various software testing methods.
b) Prepare test cases for different types and levels of testing.
c) Prepare test plan for an application.
d) Identify bugs to create defect report of given application.
e) Test software for performance measures using automated testing tools.
Evaluation as per Suggested Rubric for Assessment of Micro-Project
Sr Characteristic to be Assessed Poor Average Good Excellent Sub
. (Marks 1- (Marks 4-5) (Marks 6- (Marks 9- Tota
N 3) 8) 10) l
o
(A) Process and Product Assessment (Covert above total marks out of 6 Marks)
1 Relevance to the course
Literature Survey / Information
2
Collection
Completion of the Target as per
3
project proposal
Analysis of Data and
4
Representation
5 Quality of Prototype/Model

6 Report Preparation
(B) Individual Presentation / Viva (Convert above total marks out of 4 Marks)
7 Presentation
8 Defense

Micro-Project Evaluation Sheet

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

Comments / Suggestions about teamwork / leadership / interpersonal communication:

………………………………………………………………………………………………………………………
…
Name & Designation of the Teacher: Mr. Nilesh Vispute (Sr. Lecturer-0563)
Dated Signature: ……………………….
 Teacher Evaluation Sheet
Name of Student: Tejas Patil Enrollment No:2005630089
Name of Program: COMPUTER ENGINEERING Semester: FIFTH
Course Title: SOTFWARE TESTING Code: 224477

Title of the Micro Project:STUDENTS INFORMATION SYSTEM APPLICATION

Course Outcomes Achieved:
a) Apply various software testing methods.
b) Prepare test cases for different types and levels of testing.
c) Prepare test plan for an application.
d) Identify bugs to create defect report of given application.
e) Test software for performance measures using automated testing tools.
Evaluation as per Suggested Rubric for Assessment of Micro-Project
Sr Characteristic to be Assessed Poor Average Good Excellent Sub
. (Marks 1- (Marks 4-5) (Marks 6- (Marks 9- Tota
N 3) 8) 10) l
o
(A) Process and Product Assessment (Covert above total marks out of 6 Marks)
1 Relevance to the course
Literature Survey / Information
2
Collection
Completion of the Target as per
3
project proposal
Analysis of Data and
4
Representation
5 Quality of Prototype/Model

6 Report Preparation
(B) Individual Presentation / Viva (Convert above total marks out of 4 Marks)
7 Presentation
8 Defense

Micro-Project Evaluation Sheet

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

Comments / Suggestions about teamwork / leadership / interpersonal communication:

………………………………………………………………………………………………………………………
…
Name & Designation of the Teacher: Mr. Nilesh Vispute (Sr. Lecturer-0563)
Dated Signature: ………………………