SOFTWARE ENGINEERING & TESTING

METHODOLOGY
Course Code: BCSE3032

Practical File
For
BACHELOR OF

Engineering & Technology

SCHOOL OF COMPUTING SCIENCE AND

ENGINEERING GALGOTIAS UNIVERSITY,

GREATER NOIDA UTTAR PRADESH

Student Name: Aman Pratap Singh

Admission No: 18SCSE1140035

Batch : CNCS-1

Semester : V / FALL 2020/21

 Table of Contents
S.NO Date Experiment Title Remarks
1 09-07- Identify the project and prepare the SRS document for the
2020 project
2 23-07- Getting familiarized with the Unified Modeling Language
2020 (UML) Environment.
3 30-07- Modeling Data Flow Diagrams (at level 0, level 1 & level
2020 2) for the chosen project.
06-08-
4 2020 Modeling E-R diagram for the chosen project.
5 13-08- Working with the Use-case diagrams and capturing Use
2020 case scenarios.
6 20-08- Working with the Activity Diagrams for the chosen
2020 project.
27-08-
7 2020
Working with the Class Diagrams for the chosen project.
8 03-09- Working with the Sequence Diagrams for the chosen
2020 project.
9 10-09- Demonstration on Manual testing
2020
a. Write Programs in „C‟ Language to demonstrate the
working of the following constructs:
i)do…while ii) while…do iii)if…else iv)switch v)for
b. Write a program in ‟C‟ language to demonstrate the
working of palindrome using do…while.
10 17-09- Demonstration on Unit testing
2020
a. Create a test plan document for any application (e.g.
Library Management System).
b. Study of any testing tool (e.g. Win runner).
c. Create a test plan document for cellular phone.
11 24-09- Demonstration on Integration testing
2020
Take a mini project (e.g. University admission, Placem
and execute it. During the life cycle of the mini project
various testing documents and final test report document
12 01-10- Demonstration on System testing
2020
a. Take any system (e.g. ATM system) and study its system
specifications and report the various bugs.
b. Write down the test cases for any known applications
(e.g. Banking Application).
13
14
EXP.NO:1
DATE: 09-07-2020
TITLE: PREPARE SRS DOCUMENT FOR THE SMS PROJECT

OBJECTIVE: Identify the project and prepare the SRS document for the project

DESCRIPTION IF THEORY:
1.INTRODUCTION:
A Student Management System (SMS) is a System that manages the records of student
regarding admission and examination part. A Student Management System (SMS) is
designed to help collages for management of dental student. Extensive information is
available at your fingertips through this System. Viewing student data, managing admission
and reshuffling, managing seats, quota, board, semester, faculty, category and for
examination, block allocation, subject management, scheduling exam, result and related
issues are made simple and easy. There are custom search capabilities to aid in finding
student information and working on student records. This can make the system easier to
navigate and to use maximizing the effectiveness of time and other resources. SMS allows
the keeping of personnel data in a form that can be easily accessed and analysed in a
consistent way.

1.1 PURPOSE
This SRS Document contains the complete software requirements for the Online Student
Information Management System (OS I MS) and describes the design decisions, architectural
design and the detailed design needed to implement the system. It provides the visibility in
the design and provides information needed for software support. New reliable and fast
school management software with the great customers support. It'll help you with your daily
school management routines and deliver you from your paperwork.

1.2 SCOPE
Online Student Information Management System is developing for general purpose and used
to replace old paper work system and PUMS. OSIMS is to build upon the existing
information system PUMS in order to efficiently provide student information to teacher sand
school administration . This increase in efficiency of result making, provide result to
parents, give feedback to student, finally, publication and email student result. It provides a
mechanism to edit the student information form which makes the system flexible.

1.3 Definitions, Acronyms,abbreviations

The students management system is an automated version of manual student management
system. It can handle all the details about a student. The details includes college details,
subject details, student personnel details, academic details, exam details etc.
 Our system has two type of accessing modes, administrative and user. Student
management system is managed by an administrator. It is the job of the administrator to
insert update and monitor the whole process. When a user log in to the system. He would
only view details of the student. He can’t perform any changes.

Acronyms:
SMS: Student management system

LM: Log in module

RUM: Registered users module

NUM: Normal users module

AM: Administrator module

SM: Server module

DB: Database

1.4 REFERENCES
(a) https://www.scribd.com/doc/48111565/Software-Requirements-Specification-for-
online-student-management-system.
(b) ‘Software Engineering’ by K.K. Aggarwal & Yogesh Singh, New Age Publishing
nd
House, 2 Ed.
(c) IEEE Recommended Practice for Software Requirements Specifications – IEEE Std
830-1998.
(d) IEEE Standard for Software Test Documentation – IEEE Std. 829-1998.

1.5 Overview
Student management system (SMS) is a web-based application that tracks current student’s
academic information. It maintains academic information for ready access by office staff,
students their faculty advisors, and committee members, instead of tedious paper work,
students will be able to submit required information electronically, and the departments
will be able to evaluate the submission with a much quicker turnaround.

The student management system has been modularized into following modules.
LOGIN MODULE:
The purpose of this module is to provide entry to the system or website .based on the type of
login,the user is provided with various facilities and functionalities. The main function of
the module is to allow the user to use SMS .the module provide two types of login -Admin
login and student Login.

ADMINISTRATION MODULE:
In this module when the administrator will enter his/her user name and password ,then
he/she will enter in the administrator page and the page consists of two following sub
module. STUDENT ADDITION/UPDATION/DELETION: in SMS each student is
added ,updated or deleted according its branch.

Notice/Attendence/Result Generation: in SMS information about notice ,attendance and

internal result is generated.

FEE DETAIl and Schedules: fee information detail and schedule detail are manged

STUDENT MODULE:
In this module when user enter his student id and password,then he can visit all the
following pages.

Profile view: when the student click on this link he/she will get his /her information like
student id,student name,password ,father name,d.o.b,email id,mob no,if he/she can change
his profile.

NOTICE VIEW: when the student click on this he/she see the latest notice released
by administrator.

Attendence view: when the student click on this one ,the student can get overall
attendance percentage(present and absent).

Internal Result View: when the stuident click on this link he/she can get all the fees
structure semester wise and annual fee.

The Student Helpdesk: This helpdesk is staffedby faculty who are there to help
you.you may contact on(faculty phone no).
2.Overall Description
THE STUDENT MANAGEMENT SYSTEM ALLOWS AUTHORIZED MEMBERS TO
ACCESS THE RECORS OF ACADEMICALLYB REGISTERED STUDENTS. IT CAN
BE USED IN VARIOUS EDUCATIONAL INSTITUTES ACROSS THE GLOBE AND
SIMPLIFIES WORKING OF INSTITUTES.

2.1. Product Perspective

The proposed system shall be developed using client/server architecture and be compatible
with Microsoft Windows Operating System. The front end of the system will be developed
using Visual Basic 6.0 and backend will be developed using MS SQL Server 2000.

2.1.1. System Interfaces

None

2.1.2. User Interfaces

The ONSMS will have following user-friendly and menu driven interfaces

a) Login: to allow the entry of only authorized users through valid login Id and password.
b) School Details: to maintain school details.
c) Programme Details: to maintain programme details.
d) Scheme Details : to maintain scheme details of a programme.
Paper Details: to maintain paper details of a scheme for a particular programme
g) Faculty Details : to maintain the faculty details.

2.1.3. Hardware Interfaces

a) Screen resolution of at least 640 x 480 or above.
b) Support for printer (dot matrix, deskjet, laserjet)
c) Computer systems will be in the networked environment as it is a multi-user system.

2.1.4. Software Interfaces

a) MS-Windows Operating System

b) Microsoft Visual Basic 6.0 for designing front-end
c) MS SQL Server 2000 for backend
d) PLATEFORM : JAVA LANGUAGE
e) INTEGRATED DEVELOPMENT ENVIRONMENT(IDE):ECLIPSE

2.1.5. Communication Interfaces

None

2.1.6. Memory Constraints

At least 512 MB RAM and 500 MB space of hard disk will be required to run the software.

2.1.7. Operations
None

2.1.8. Site Adaptation Requirements

The terminal at client site will have to support the hardware and software interfaces specified
in the section 2.1.3 and 2.1.4 respectively.

2.2. Product Functions

The ONSMS will allow access only to authorized users with specific roles (System
administrator, Faculty and Student). Depending upon the user’s role, he/she will be able to
access only specific modules of the system. A summary of major functions that the URS will
perform

· A login facility for enabling only authorized access to the system.

· System administrator will be able to add, modify or delete programme, school,
scheme, paper and login information.
· Students will be able to add/modify his/her details and register for papers to be
studied in the current semester.
· System administrator/Faculty will be able to generate reports.

2.3. User Characteristics

· Qualification: At least matriculation and comfortable with English.
· Experience: Should be well versed/informed about the registration process of the
university.
· Technical Experience: Elementary knowledge of computers

2.4. Constraints
· There will only be one administrator.
· The delete operation is available only to the administrator. To reduce the complexity
of the system, there is no check on delete operation. Hence, administrator should be very
careful before deletion of any record and he/she will be responsible for data consistency.
2.5 Assumptions and Dependencies
· The login Id and password must be created by system administrator and communicated
to the concerned user confidentially to avoid unauthorized access to the system.
· It is assumed that a student registering for the subsequent semester has been promoted
to that semester by the university as per rules and has paid desired university fee.
· Registration process will be open only for specific duration.
EXP.NO:2
DATE: 23-07-2020
TITLE: Familiar with the Unified Modeling Language (UML)
Environment
OBJECTIVE: Getting familiarized with the Unified Modeling Language
(UML) Environment

DESCRIPTION IF THEORY:
Unified Modeling Language (UML) is a general purpose modelling language. The main
aim of UML is to define a standard way to visualize the way a system has been designed. It is
quite similar to blueprints used in other fields of engineering.

UML is not a programming language, it is rather a visual language. We use UML diagrams
to portray the behavior and structure of a system. UML helps software engineers,
businessmen and system architects with modelling, design and analysis. The Object
Management Group (OMG) adopted Unified Modelling Language as a standard in 1997.
Its been managed by OMG ever since. International Organization for Standardization (ISO)
published UML as an approved standard in 2005. UML has been revised over the years and
is reviewed periodically.

Do we really need UML?

Complex applications need collaboration and planning from multiple teams and
hence require a clear and concise way to communicate amongst them.
Businessmen do not understand code. So UML becomes essential to communicate with non
programmers essential requirements, functionalities and processes of the system.
A lot of time is saved down the line when teams are able to visualize processes, user
interactions and static structure of the system.
UML is linked with object oriented design and analysis. UML makes the use of elements and
forms associations between them to form diagrams. Diagrams in UML can be broadly
classified as:

Structural Diagrams – Capture static aspects or structure of a system. Structural Diagrams

include: Component Diagrams, Object Diagrams, Class Diagrams and Deployment
Diagrams.
Behavior Diagrams – Capture dynamic aspects or behavior of the system. Behavior
diagrams include: Use Case Diagrams, State Diagrams, Activity Diagrams and Interaction
Diagrams. The image below shows the hierarchy of diagrams according to UML 2.2
Object Oriented Concepts Used in UML –
Class – A class defines the blue print i.e. structure and functions of an object.

Objects – Objects help us to decompose large systems and help us to modularize our
system. Modularity helps to divide our system into understandable components so that we
can build our system piece by piece. An object is the fundamental unit (building block) of a
system which is used to depict an entity.

Inheritance – Inheritance is a mechanism by which child classes inherit the properties

of their parent classes.

Abstraction – Mechanism by which implementation details are hidden from user.

Encapsulation – Binding data together and protecting it from the outer world is referred
to as encapsulation.

Polymorphism – Mechanism by which functions or entities are able to exist in

different forms.

Additions in UML 2.0 –

Class Diagram – The most widely use UML diagram is the class diagram. It is the
building block of all object oriented software systems. We use class diagrams to depict the
static structure of a system by showing system’s classes,their methods and attributes. Class
diagrams also help us identify relationship between different classes or objects.
Composite Structure Diagram – We use composite structure diagrams to represent the
internal structure of a class and its interaction points with other parts of the system. A
composite structure diagram represents relationship between parts and their configuration
which determine how the classifier (class, a component, or a deployment node) behaves. They
represent internal structure of a structured classifier making the use of parts, ports, and
connectors. We can also model collaborations using composite structure diagrams. They
are similar to class diagrams except they represent individual parts in detail as compared to
the entire class.
Object Diagram – An Object Diagram can be referred to as a screenshot of the instances in
a system and the relationship that exists between them. Since object diagrams depict
behaviour when objects have been instantiated, we are able to study the behaviour of the
system at a particular instant. An object diagram is similar to a class diagram except it
shows the instances of classes in the system. We depict actual classifiers and their
relationships making the use of class diagrams. On the other hand, an Object Diagram
represents specific instances of classes and relationships between them at a point of time.
Component Diagram – Component diagrams are used to represent the how the physical
components in a system have been organized. We use them for modelling
implementation details. Component Diagrams depict the structural relationship between
software system elements and help us in understanding if functional requirements have
been covered by planned development. Component Diagrams become essential to use
when we design and build complex systems. Interfaces are used by components of the
system to communicate with each other.

Deployment Diagram – Deployment Diagrams are used to represent system hardware and
its software.It tells us what hardware components exist and what software components run
on them.We illustrate system architecture as distribution of software artifacts over distributed
targets. An artifact is the information that is generated by system software. They are
primarily used when a software is being used, distributed or deployed over multiple
machines with different configurations.
Package Diagram – We use Package Diagrams to depict how packages and their elements
have been organized. A package diagram simply shows us the dependencies between
different packages and internal composition of packages. Packages help us to organise
UML diagrams into meaningful groups and make the diagram easy to understand. They are
primarily used to organise class and use case diagrams.
Behavior Diagrams –

State Machine Diagrams – A state diagram is used to represent the condition of the system
or part of the system at finite instances of time. It’s a behavioral diagram and it represents
the behavior using finite state transitions. State diagrams are also referred to as State
machines and State-chart Diagrams . These terms are often used interchangeably.So simply,
a state diagram is used to model the dynamic behavior of a class in response to time and
changing external stimuli.

Activity Diagrams – We use Activity Diagrams to illustrate the flow of control in a system.
We can also use an activity diagram to refer to the steps involved in the execution of a use
case. We model sequential and concurrent activities using activity diagrams. So, we
basically depict workflows visually using an activity diagram.An activity diagram focuses on
condition of flow and the sequence in which it happens. We describe or depict what causes a
particular event using an activity diagram.

Use Case Diagrams – Use Case Diagrams are used to depict the functionality of a system or
a part of a system. They are widely used to illustrate the functional requirements of the
system and its interaction with external agents(actors). A use case is basically a diagram
representing different scenarios where the system can be used. A use case diagram gives us
a high level view of what the system or a part of the system does without going into
implementation details.
Sequence Diagram – A sequence diagram simply depicts interaction between objects in a
sequential order i.e. the order in which these interactions take place.We can also use the
terms event diagrams or event scenarios to refer to a sequence diagram. Sequence diagrams
describe how and in what order the objects in a system function. These diagrams are widely
used by businessmen and software developers to document and understand requirements
for new and existing systems.

Communication Diagram – A Communication Diagram(known as Collaboration

Diagram in UML 1.x) is used to show sequenced messages exchanged between objects. A
communication diagram focuses primarily on objects and their relationships. We can
represent similar information using Sequence diagrams,however, communication diagrams
represent objects and links in a free form.

Timing Diagram – Timing Diagram are a special form of Sequence diagrams which
are used to depict the behavior of objects over a time frame. We use them to show time
and duration constraints which govern changes in states and behavior of objects.

Interaction Overview Diagram – An Interaction Overview Diagram models a sequence of

actions and helps us simplify complex interactions into simpler occurrences. It is a mixture
of activity and sequence diagrams.
EXP.NO:3
DATE: 30-07-2020
TITLE: Modeling Data Flow Diagrams (at level 0 & level 1) for
the chosen project

OBJECTIVE: Data Flow Diagrams (at level 0 & level 1) for the SMS project.

DESCRIPTION IF THEORY:
A data flow diagram is a graphical view of how data is processed in a system in terms
of input and output.
The Data flow diagram (DFD) contains some symbol for drawing the data flow diagram.

0 Level DFD – Student Management System

The context level data flow diagram (dfd) is describe the whole system. The (o) level dfd
describe the all user modules who run the system. Below context level data flow diagram of
Student management system project shows the one Admin user can operate the system.

st
1 level DFD – Student Management System
The Admin side DFD describe the functionality of Admin. Admin is a responsible person
who run the project. After login to system admin can first Add Course Detail and Teacher
Detail and then add student detail by course wise. And admin can manage student reports
and fees payment detail.

OUTPUT:

O LEVEL DFD DIAGRAM FOR STUDENT MANGEMENT SYSTEM

 st
1 level DFD DIAGRAM FOR Student Management System

Result : Successfully drawn the dfd diagram with star uml for student management
system
EXP.NO:4
DATE: 06-08-2020
TITLE: Modeling E-R diagram for the chosen project

OBJECTIVE: Draw E-R diagram for the SMS project.

DESCRIPTION IF THEORY:

E-R (Entity-Relationship) Diagram is used to represents the relationship between

entities in a table. ER diagrams represent the logical structure of databases. ER Diagram
represent relationship between two database tables.

E-R diagram means Entity Relationship diagram. Entity is a object of system, generally we
refer entity as database table , the e-r diagram represent the relationship between each table
of database. E-R diagram represent entity with attributes, attributes is a properties of entity.
If we assume entity is a database table then all the columns of table are treat as attributes.

ER Diagram

Entity : Entities are represented by rectangle. All table of database are treat as entity.

Attributes : Attributes are represented by ellipses. Attributes are properties of entities.

OUTPUT:

Result: Successfully executed the ER diagram for student management

system
EXP.NO:5
DATE: 13-08-2020
TITLE: Working with the Use-case diagrams and capturing Use
case scenarios

OBJECTIVE: Use-case diagrams and capturing Use case scenarios

DESCRIPTION IF THEORY:

Use Case Diagram – Student Management System

The use case diagram are usually referred to as behavior diagram used to describe the
actions of all user in a system. All user describe in use case are actors and the functionality
as action of system.
The Use case diagram is a collection of diagram and text together that make action on goal
of a process.

Use case diagram for student information system project. In Student information
system there is a only one actor Admin can do all the activities to run the system.

Use case diagram elements:

The use case diagram consist of six graphics elements that represent whole system :
Systems
Actors
Use cases
Association
Dependencies
OUTPUT:

Result: Successfully executed use case diagram with star uml for student
management system
EXP.NO:6
DATE:20-08-2020
TITLE: Working with the Activity Diagrams for the SMS project

OBJECTIVE: Execute Activity Diagrams for the SMS project

DESCRIPTION IF THEORY:

Activity Diagram – Student Management System

The activity diagram used to describe flow of activity through a series of actions. Activity
diagram is a important diagram to describe the system. An activity diagram shows the overall
flow of control. Here, we learn how to draw activity diagram for student information system
or student management system project.
OUTPUT:

Result : Successfully executed Activity diagram with star uml for student
management system
 EXP.NO:7
DATE:27-08-2020
TITLE: Working with the Class Diagrams for the SMS project.

OBJECTIVE: EXECUTE CLASS DIAGRAM FOR SMS WITH STAR UML

DESCRIPTION IF THEORY:

Student Management System Class Diagram describes the structure of a Student

Management System classes, their attributes, operations (or methods), and the
relationships among objects. The main classes of the Student Management System are
Student, Fees, Logins, Profiles, Cources, Exams.

Classes of Student Management System Class Diagram:

Student Class : Manage all the operations of Student

Fees Class : Manage all the operations of Fees
Logins Class : Manage all the operations of Logins
Profiles Class : Manage all the operations of Profiles
Cources Class : Manage all the operations of Cources
Exams Class : Manage all the operations of Exams
Classes and their attributes of Student Management System Class Diagram:

Student Attributes : student_id, student_college_id, student_name, student_mobile,

student_email, student_username, student_password, student_address
Fees Attributes : fee_id, fee_course_id, fee_amount, fee_total, fee_payment,
fee_type, fee_description
Logins Attributes : login_id, login_user_id, login_role_id, login_username, login_password,
login_lastlogin
Profiles Attributes : profile_id, profile_name, profile_type, profile_description
Cources Attributes : course_id, course_student_id, course_registration, course_name,
course_type, course_year, course_description
Exams Attributes : exam_id, exam_student_id, exam_roll_number, exam_date
exam_name, exam_type, exam_description
Classes and their methods of Student Management System Class Diagram:

Student Methods : addStudent(), editStudent(), deleteStudent(),

updateStudent(), saveStudent(), searchStudent()

Fees Methods : addFees(), editFees(), deleteFees(), updateFees(), saveFees(), searchFees()

Logins Methods : addLogins(), editLogins(), deleteLogins(), updateLogins(),
saveLogins(), searchLogins()

Profiles Methods : addProfiles(), editProfiles(), deleteProfiles(), updateProfiles(),

saveProfiles(), searchProfiles()

Cources Methods : addCources(), editCources(), deleteCources(),

updateCources(), saveCources(), searchCources()
Exams Methods : addExams(), editExams(), deleteExams(), updateExams(),
saveExams(), searchExams()

OUTPUT:

Result : Successfully executed Class diagram with star uml for students
management system
EXP.NO:8
DATE:03-09-2020
TITLE: Working with the Sequence Diagrams for the SMS project.

OBJECTIVE: EXECUTE SEQUENCE DIAGRAM FOR SMS WITH STAR UML

DESCRIPTION IF THEORY:

This is the UML sequence diagram of Student Management System which shows the
interaction between the objects of Profiles, Exams, Fees, Student, Courses. The instance of
class objects involved in this UML Sequence Diagram of Student Management System are
as follows:

Profiles Object
Exams Object
Fees Object
Student Object
Courses Object
Login Sequence Diagram Of Student Management System:

This is the Login Sequence Diagram of Student Management System, where admin will be
able to login in their account using their credentials. After login user can manage all the
operations on Fees, Profiles, Exams, Courses, Student. All the pages such as Exams, Courses,
Student are secure and user can access these page after login. The diagram below helps
demonstrate how the login page works in a Student Management System. The various objects
in the Courses, Fees, Profiles, Exams, and Student page—interact over the course of the
sequence, and user will not be able to access this page without verifying their identity.
OUTPUT:

Result : Successfully executed SEQUENCE diagram with star uml for

student management system
EXP.NO:9
DATE: 10-09-2020
TITLE: Demonstration on Manual testing
a. Write Programs in “C” Language to demonstrate the working of the following
constructs:
I) do…while ii) while…do iii) if…else iv) switch v) for
b. Write a program in ‟C‟ language to demonstrate the working of palindrome using
do…while.

Objective:- To understand the working of do while with different range of values and
test cases.

#include <stdio.h>
void main ()
{
int i, n=5,j=0; clrscr();
printf(“enter a no”);
scanf(“%d”,&i);
do
{
if(i%2==0)
{
printf("%d", i);
printf("is a even no. \n");
i++;
j++;
}
else
{
printf("%d", i);
printf("is a odd no.\n");
i++;
j++;
}
}
while(i>0&&j<n);
getch();
}

Input Actual output

1 4 is even number
5 is odd number
6 is even number
7 is odd number
8 is even number
Test cases:

Test case no: 1

Test case name: Positive values within range

Input =2 Expected output Actual output Remarks

4 is even number 4 is even number
5 is odd number 5 is odd number success
6 is even number 6 is even number
7 is odd number 7 is odd number
8 is even number 8 is even number

Test case no:2

Test case name: Negative values within a range

Input = -2 Expected output Actual output Remarks

-4 is even number -4 is an even number
-5 is odd number fail
-6 is even number
-7 is odd number
-8 is even number

Test case no: 3

Test case name: Out of range values testing

Input Expected output Actual output Remarks

6789456788888888 678945678888888868 78945678888888869 fail
Program-2 WAP to demonstrate the working of do-while
with while construction.

Objective:- To understand the working of while with different range of values and test
cases

#include<stdio.h>
#include <conio.h>
void main (){
int i, n=5,j=1;
clrscr();
printf("enter a no");
scanf("%d",&i);
while (i>0 && j<n){
if(i%2==0){
printf("%d",i);
printf("is a even number \n");
i++;
j++;
}
else{
printf("%d",i);
printf("is a odd number \n"); i++;
j++;
}
}
getch();
}

Input Actual output

2 2 is even number
3 is odd number
4 is even number
5 is odd number
6 is even number

Test cases:

Test case no: 1s

Test case name: Positive values within range

Input =2 Expected output Actual output Remarks

2 is even number 2 is even number
3 is odd number 3 is odd number success
4 is even number 4 is even number
5 is odd number 5 is odd number
6 is even number 6 is even number
Test case no:2
Test case name: Negative values within a range

Input = -2 Expected output Actual output Remarks

-2 is even number -2 is an even number
-3 is odd number fail
-4 is even number
-5 is odd number
-6 is even number

Test case no: 3

Test case name: Out of range values testing

Input Expected output Actual output Remarks

1234567891222222222222 123456789122222222213 234567891222222215 fail
Program-3 WAP to demonstrate the working of IF ELSE construction.

Objective:- To understand the working of if else with different range of values and test cases

#include<stdio.h>
#include <conio.h>
void main (){
int i;
clrscr();
printf(“enter a number”);
scanf(“%d”,&i);
if(i%2==0){
printf(“%d”,i);
printf(“is a even number”);
}
else{
printf(“%d”,i);
printf(“is a odd number”);
}
getch();

Input Actual output

2 2 is even number
3 is odd number
4 is even number
5 is odd number
6 is even number

Test cases:

Test case no: 1

Test case name: Positive values within range

Input =2 Expected output Actual output Remarks

2 is even number 2 is even number
3 is odd number 3 is odd number success
4 is even number 4 is even number
5 is odd number 5 is odd number
6 is even number 6 is even number
Test case no:2
Test case name: Negative values within a range

Input = -2 Expected output Actual output Remarks

-2 is even number -2 is an even number
-3 is odd number fail
-4 is even number
-5 is odd number
-6 is even number
Test case no: 3

Test case name: Out of range values testing

Input Expected output Actual output Remarks

1234567891222222222222 123456789122222222213 234567891222222215 fail
 Program-4 WAP to demonstrate the working of
switch construction.

Objective:- To understand the working of switch with different range of values and
test cases

#include<stdio.h>
#include <conio.h>
void main() {

int
a,b,c;
clrscr()
;
printf(“1.Add/n 2.Sub /n 3.Mul /n 4.Div /n Enter
Your choice”); scanf(“%d”,&i);
printf(“Enter a,b values”);
scanf(“%d%d”,&a,&b);
switch(i){
case 1: c=a+b;
printf(“ The sum of a & b is:
%d”,c); break;
case 2: c=a-b;
printf(“ The Diff of a & b is:
%d”,c); break;
case 3: c=a*b;
printf(“ The Mul of a & b is:
%d”,c); break;
case 4: c=a/b;
printf(― The Div of a & b is:
%d‖,c); break;
default:
printf(― Enter your
choice‖); break;
}
getch();
}

Output:

Input Output

Enter Ur choice: 1
Enter a, b Values: 3, 2 The sum of a & b is:5

Enter Ur choice: 2
Enter a, b Values: 3, 2 The diff of a & b is: 1

Enter Ur choice: 3
Enter a, b Values: 3, 2 The Mul of a & b is: 6
Enter Ur choice: 4
Enter a, b Values: 3, 2 The Div of a & b is: 1

Test cases:

Test case no: 1

Test case name: Positive values within range

Input Expected output Actual output Remarks

Enter Ur choice: 1
Enter a, b Values: 3, 2 The sum of a & b is:5 5

Enter Ur choice: 2
Enter a, b Values: 3, 2 The diff of a & b is: 1 1 Success

Enter Ur choice: 3
Enter a, b Values: 3, 2 The Mul of a & b is: 6 6

Enter Ur choice: 4
Enter a, b Values: 3, 2 The Div of a & b is: 1 1

Test case no:2

Test case name: Out of range values testing

Input Expected output Actual output Remarks

Option: 1

a= 22222222222222

b=22222222222222 44444444444444 -2 fail

Test case no: 3

Test case name: Divide by zero

Input Expected output Actual output Remarks

Option: 4

a= 10 & b=0 Error fail

Program-5 WAP to demonstrate the working of FOR construct.

Objective:- To understand the working of for with different range of values and test cases

#include<stdio.h>
#include<conio.h>
void main ()
{
int i;
clrscr();
printf(“enter a no”);
scanf(“%d”,&i);
for(i=1;i<=5;i++)
{
if(i%2==0)
{
printf(“%d”,i);
printf(“ is a even no”);
i++;
}
else
{
printf(“%d”,i);
printf(“ is a odd no”);
i++;
}
}
getch();
}

Output:

Enter a no: 5

0 is a even no
1 is a odd no
2 is a even no
3 is a odd no
4 is a even no
5 is a odd no
Test cases:

Test case no: 1

Test case name: Positive values within range

Input =2 Expected output Actual output Remarks

0 is even number 0 is even number

1 is odd number 1 is odd number success

2 is even number 2 is even number
Test case no:2
Test case name: Negative values within a range
Input = -2 Expected output Actual output Remarks
0 is even number 0 is an even number
-1 is odd number -1 is even no Fail
-2 is even number -2 is odd no

Test case no: 3

Test case name: Out of range values testing

Input Expected output Actual output Remarks

1234567891222222222222 123456789122222222213 234567891222222215 fail
Program-6 WAP to check no is palindrome or not using do-while

OBJECTIVE: Write a program in ‘C‘language to demonstrate the working

of palindrome using do…while.

RESOURCES:

i). Server System configuration: 128 MB of RAM , 500 MB of free disk space, Win
NT server, Win 2K server, IIS 5.0, MS Access/Oracle 7.x,8.x,9/MS SQL.

ii). Server Client System configuration: 64 MB of RAM , 10 MB of free disk

space, Win95/98/NT/2K/XP, IE 5.

PROGRAM LOGIC:

1. do …while

declare n, reverse=0, rem,temp.

print ―Enter an integer‖.
Read n value.
Assign temp to n.
while( temp not equal to zero)
do

rem=temp%10.
reverse=reverse*10+rem.
temp/=10.
If reverse equal to n Print n is a palindrome.
else
print n is not a palindrome.

PROCEDURE:

a. Create: Open editor vi x.c write a program after that press ESC and: wq for save and Quit.
b. Compile: gcc x.c.
c. Execute:. / a.out.

SOURCE CODE:

#include <stdio.h>
int main()
{
int n, reverse=0, rem,temp;
printf("Enter an integer: ");
scanf("%d", &n);
temp=n;
while(temp!=0) { rem=temp%10;
reverse=reverse*10+rem;
temp/=10;
}
if(reverse==n)
printf("%d is a palindrome.",n);
else
printf("%d is not a palindrome.",n);

return 0;
}

INPUT AND OUTPUT:

i. do…while

Input Actual output

545 545is palindrome

Test cases:
Test case no: 1
Test case name : Positive values within range
Input Expected Output Actual Output Remarks
545 545 is palindrome 545 is palindrome Success
EXP.NO:10
DATE: 17-09-2020
TITLE: Demonstration on Unit testing

OBJECTIVE : Create a test plan document for students management system

RESOURCES: 1. Server System configuration: 128 MB of RAM , 500 MB of free disk

space, Win NT server, Win 2K server, IIS 5.0, MS Access/Oracle 7.x,8.x,9/MS SQL.
2. Server Client System configuration: 64 MB of RAM , 10 MB of free disk space,
Win 95/98/NT/2K/XP, IE 5.

TEST PLAN DOCUMENT FOR STUDENTS MANAGEMENT SYSTEM:

All the tests that are listed below were conducted on the system with the above
mentioned configuration. The test plan is given below:-
I have taken three test cases into consideration; the three different test cases were conducted
differently with different number of users. For test case-1 I have considered 200 users, for
test case-2 I have considered 90 users and lastly for test case-3 I have considered like 300
users. Evaluation of the results is based on two factors viz., throughput and response times.
There are several factors which made me to put a limit on number of users I was considering
and they are described in the future sections below. The following web pages of my
application are tested:-
1. Home(login) Page using HTTP protocol

2. Selection of the courses by student using HTTP protocol

3.Faculty main page, where a faculty member enters the student’s WID using HTTP protocol

Test Case 1
Firstly I have tested the home page to analyze its behavior and to get an idea about the
performance of the application. I plan to show the through put as well as response times of
the web page when like more number of users are accessing it in order to estimate the
performance of the application and how they are affected and thereby estimating the
maximum number of users accessing the application at same point of time.

Test Case 2
The second test case I have planned to estimate the performance is the courses page
where the student chooses the program option as well as core and non-core courses.
I plan to show to show the through put and response time when like many users are accessing
the application and how they are affected and also to estimate the maximum number of users
accessing the application simultaneously.

Test Case 3

Lastly, the third page I have tested is the faculty page. In this page, a member of faculty
enters the student WID in order to view the profile of that particular student having that ID. I
plan to show the performance of the application by showing the through put and response
time when like many users are trying to access the application and how they are affected and
also maximum number of users using the application at same point of time.
OBJECTIVE: Study of Any Testing Tool (Win Runner)

RESOURCES:
1. Server System configuration: 128 MB of RAM , 500 MB of free disk space, Win
NT server, Win 2K server, IIS 5.0, MS Access/Oracle 7.x,8.x,9/MS SQL.
2. Server Client System configuration: 64 MB of RAM, 10 MB of free disk space,
Win 95/98/NT/2K/XP, IE 5.

STUDY OF WIN RUNNER TESTING TOOL:

Win Runner is a program that is responsible for the automated testing of software. Win
Runner is a Mercury Interactive enterprise functional testing tool for Microsoft
windows applications.

Importance of Automated Testing:

Reduced testing time Consistent test procedures – ensure process repeatability and
resource independence. Eliminates errors of manual testing. Reduces QA cost – Upfront
cost of automated testing is easily recovered over the life-time of the product .Improved
testing productivity – test suites can be run earlier and more often Proof of adequate testing
.For doing Tedious work – test team members can focus on quality areas.

Win Runner Uses:

1. With Win Runner sophisticated automated tests can be created and run on an application.
A series of wizards will be provided to the user, and these wizards can create tests in an
automated manner.
2. Another impressive aspect of Win Runner is the ability to record various interactions, and
transform them into scripts. Win Runner is designed for testing graphical user interfaces.
When the user make an interaction with the GUI, this interaction can be recorded. Re-cording
the interactions allows determining various bugs that need to be fixed. When the test is
completed, Win Runner will provide with detailed information regarding the results. It will
show the errors that were found, and it will also give important information about them. The
good news about these tests is that they can be reused many times.
3. Win Runner will test the computer program in a way that is very similar to normal user
interactions. This is important, because it ensures a high level of accuracy and realism. Even
if an engineer is not physically present, the Recover manager will troubleshoot any problems
that may occur, and this will allow the tests to be completed without errors.
4. The Recover Manager is a powerful tool that can assist users with various scenarios. This
is important, especially when important data needs to be recovered.
5. The goal of Win Runner is to make sure business processes are properly carried out. Win
Runner uses TSL, or Test Script Language.

Win Runner Testing Modes

Context Sensitive:
Context Sensitive mode records your actions on the application being tested in terms of the
GUI objects you select (such as windows, lists, and buttons), while ignoring the physical
location of the object on the screen. Every time you perform an operation on the application
being tested, a TSL statement describing the object selected and the action performed is
generated in the test script. As you record, Win Runner writes a unique description of each
selected object to a GUI map. The GUI map consists of files maintained separately from your
test scripts. If the user interfaces of your application changes, you have to update only the
GUI map, instead of hundreds of tests. This allows you to easily reuse your Context Sensitive
test scripts on future versions of your application. To run a test, you simply play back the test
script. Win Runner emulates a user by moving the mouse pointer over your application,
selecting objects, and entering keyboard input. Win Runner reads the object descriptions in
the GUI map and then searches in the application being tested for objects matching these
descriptions. It can locate objects in a window even if their placement has changed.

Analog
Analog mode records mouse clicks, keyboard input, and the exact x and y coordinates
traveled by the mouse. When the test is run, Win Runner retraces the mouse tracks. Use
Analog mode when exact mouse coordinates are important to your test, such as when testing
a drawing application.
The Win Runner Testing Process Testing with Win Runner involves six main stages:

1. Create the GUI Map

The first stage is to create the GUI map so Win Runner can recognize the GUI objects in the
application being tested. Use the Rapid Test Script wizard to review the user interface of
your application and systematically add descriptions of every GUI object to the GUI map.
Alternatively, you can add descriptions of individual objects to the GUI map by clicking
objects while recording a test.

2. Create Tests
Next is creation of test scripts by recording, programming, or a combination of both. While
recording tests, insert checkpoints where we want to check the response of the application
being tested. We can insert checkpoints that check GUI objects, bitmaps, and databases.
During this process, Win Runner captures data and saves it as expected results the expected
response of the application being tested.

3. Debug Tests
Run tests in Debug mode to make sure they run smoothly. One can set breakpoints, monitor
variables, and control how tests are run to identify and isolate defects. Test results are saved
in the debug folder, which can be discarded once debugging is finished. When Win Runner
runs a test, it checks each script line for basic syntax errors, like incorrect syntax or missing
elements in If, While, Switch, and For statements.

We can use the Syntax Check options (Tools >Syntax Check) to check for these types of
syntax errors before running your test.

4. Run Tests
Tests can be run in Verify mode to test the application. Each time Win Runner encounters a
checkpoint in the test script, it compares the current data of the application being tested to the
expected data captured earlier. If any mismatches are found, Win Runner captures them as
actual results.
5. View Results
Following each test run, Win Runner displays the results in a report. The report details all the
major events that occurred during the run, such as checkpoints, error messages, system
messages, or user messages. If mismatches are detected at checkpoints during the test run, we
can view the expected results and the actual results from the Test Results window. In cases of
bitmap mismatches, one can also view a bitmap that displays only the difference between the
expected and actual results. We can view results in the standard Win Runner report view or in
the Unified report view. The Win Runner report view displays the test results in a Windows
style viewer. The Unified report view displays the results in an HTML style viewer (identical
to the style used for Quick Test Professional test results).

6. Report Defects
If a test run fails due to a defect in the application being tested, one can report information
about the defect directly from the Test Results window .This information is sent via e-mail to
the quality assurance manager, who tracks the defect until it is fixed.
Using Win runner Window
Before you begin creating tests, you should familiarize yourself with the Win Runner main
window.

To start Win Runner:

Choose Programs>Win Runner>Win Runner on the Start menu. The first time you start
Win Runner, the Welcome to Win Runner window and the What‗s New in Win Runner help
open. From the Welcome window you can create a new test, open an existing test, or view an
overview of Win Runner in your default browser. If you do not want this window to appear
the next time you start Win Runner, clear the Show on Startup check box. To show the
Welcome to Win Runner window upon startup from within Win Runner, choose Settings >
General Options, click the Environment tab, and select the Show Welcome screen check
box.

The Main Win Runner Window

The main Win Runner window contains the following key elements:

1. Win Runner title bar

2. Menu bar, with drop-down menus of Win Runner commands
3. Standard toolbar, with buttons of commands commonly used when running a test
4. User toolbar, with commands commonly used while creating a test
5. Status bar, with information on the current command, the line number of the insertion
point and the name of the current results folder

Standard Toolbar
The User toolbar displays the tools you frequently use to create test scripts. By default, the
User toolbar is hidden. To display the User toolbar, choose Window>User Toolbar. When
you create tests, you can minimize the Win Runner window and work exclusively from the
toolbar. The User toolbar is customizable. You choose to add or remove buttons using the
Settings > Customize User Toolbar menu option. When you reopen Win Runner, the User
toolbar appears as it was when you last closed it. The commands on the Standard toolbar and
the User toolbar are described in detail in subsequent lessons. Note that you can also execute
many commands using soft keys. Sof keys are keyboard shortcuts for carrying out menu
commands. You can configure the softkey combinations for your keyboard using the Softkey
Configuration utility in your Win Runner program group. For more information, see the Win
Runner at a Glance chapter in your Win Runner User‘s Guide. Now that you are familiar
with the main Win Runner window, take a few minutes to explore these window components
before proceeding to the next lesson.

The Test Window You create and run Win Runner tests in the test window. It contains the
following key elements:
1. Test window title bar, with the name of the open test
2. Test script, with statements generated by recording and/or programming in TSL, Mercury
Interactive Test Script Language.
3. Execution arrow, which indicates the line of the test script being executed during a test
run, or the line that will next run if you select the Run from arrow option
4. Insertion point, which indicates where you can insert or edit text.
Create a test plan document for cellular phone.

OBJECTIVE: Create a test plan document for cellular phone.

RESOURCES:
1. Server System configuration: 128 MB of RAM , 500 MB of free disk space, Win NT
server, Win 2K server, IIS 5.0, MS Access/Oracle 7.x,8.x,9/MS SQL.
2. Server Client System configuration: 64 MB of RAM , 10 MB of free disk space, Win
95/98/NT/2K/XP, IE 5.

TEST PLAN DOCUMENT FOR CELLULAR PHONE :

There are broadly 2 kinds of testing that take place on mobile devices:

1. Hardware testing: The device including the internal processors, internal hardware, screen
sizes, resolution, space or memory, camera, radio, Bluetooth, WIFI etc. This is sometimes
referred to as, simple ―Mobile Testing.

2. Software or Application testing: The applications that work on mobile devices and their
functionality is tested. It is called the ―Mobile Application Testing‖ to differentiate it from
the earlier method. Even in the mobile applications, there are few basic differences that are
important to understand:

a) Native apps: A native application is created for use on a platform like mobile and tablets.

b) Mobile web apps are server-side apps to access website/s on mobile using different
browsers like chrome, Firefox by connecting to a mobile network or wireless network like
WIFI.

c) Hybrid apps are combinations of native app and web app. They run on devices or offline
and are written using web technologies like HTML5 and CSS.There are few basic
differences that set these apart:

• Native apps have single platform affinity while mobile web apps have cross platform
affinity.
• Native apps are written in platforms like SDKs while Mobile web apps are written
with web technologies like html, css, asp.net, java, php.
• For a native app, installation is required but for mobile web apps, no installation is
required.
• Native app can be updated from play store or app store while mobile web apps are
centralized updates.
• Many native app don‘t require Internet connection but for mobile web apps it‘s a must.
• Native app works faster when compared to mobile web apps.
• Native apps are installed from app stores like Google play store or app store where
mobile web are websites and are only accessible through Internet.
EXP.NO:11
DATE:24-09-2020
TITLE: Demonstration on Integration testing

OBJECTIVE: Create a integration test plan document for Hospital Management System

RESOURCES:

Min 10 GB Hard Disk, Min 512mb RAM, Dual-Core Processor Monitor.

Hardware: Dual Core or above machines, Software: Microsoft Windows XP installed

INTEGRATION TESTING FOR STUDENTS

MANAGEMENT SYSTEM:

Integration test cases focus mainly on the interface between the modules, integrated links,
data transfer between the modules as modules/components that are already unit tested i.e.
the functionality and the other testing aspects have already been covered.
• Verifying the interface link between the login page and the home page i.e. when
a user enters the credentials and logs it should be directed to the homepage.
• Verifying the interface link between the home page and the profile page i.e.
profile page should open up.
• Verify the interface link between the network page and your connection pages i.e.
clicking accept button on Invitations of the network page should show the
accepted invitation in your connection page once clicked.
• Verify the interface link between the Notification pages and say congrats button
i.e. clicking say congrats button should direct towards the new message window.
EXP.NO:12
DATE:01-10-2020
TITLE: Demonstration on System testing

Take any system (e.g. ATM system) and study its system specifications and report the
various bugs.

OBJECTIVE: Take any system (e.g. ATM system) and study its system
specifications and report the various bugs.

RESOURCES:
a. Server System configuration: 128 MB of RAM , 500 MB of free disk space, Win
NT server, Win 2K server, IIS 5.0, MS Access/Oracle 7.x,8.x,9/MS SQL.
b. Server Client System configuration: 64 MB of RAM , 10 MB of free disk space,
Win 95/98/NT/2K/XP, IE 5.

BUGS IN ATM SYSTEM:

1. Machine is accepting ATM card.

2. Machine is rejecting expired card.
3. Successful entry of PIN number.
4. Unsuccessful operation due to enter wrong PIN number 3 times.
5. Successful selection of language.
6. Successful selection of account type.
7. Unsuccessful operation due to invalid account type.
8. Successful selection of amount to be withdrawn.
9. Successful withdrawal.
10. Expected message due to amount is greater than day limit.
11. Unsuccessful withdraw operation due to lack of money in ATM.
12. Expected message due to amount to withdraw is greater than possible balance.
13. Unsuccessful withdraw operation due to click cancel after insert card.
Write down the test cases for any known applications (e.g.
Banking Application).
OBJECTIVE:
Write the test cases for any known application (e.g. banking application)

RESOURCES:

1. Server System configuration: 128 MB of RAM , 500 MB of free disk space, Win
NT server, Win 2K server, IIS 5.0, MS Access/Oracle 7.x,8.x,9/MS SQL.
2. Server Client System configuration: 64 MB of RAM, 10 MB of free disk space,
Win 95/98/NT/2K/XP, IE 5.

TEST CASES FOR BANKING APPLICATION:

1. Checking mandatory input parameters.

2. Checking optional input parameters.
3. Check whether able to create account entity.
4. Check whether you are able to deposit an amount in the newly created account (and
thus updating the balance).
5. Check whether you are able to withdraw an amount in the newly created account
(after deposit) (and thus updating the balance).
6. Check whether company name and its pan number and other details are provided in case
of salary account.
7. Check whether primary account number is provided in case of secondary account.
8. Check whether company details are provided in cases of company's current account.
9. Check whether proofs for joint account are provided in case of joint account.
10. Check whether you are able deposit an account in the name of either of the person in
a joint account.
11. Check whether you are able withdraws an account in the name of either of the person in
a joint account.
12. Check whether you are able to maintain zero balance in salary account.
13. Check whether you are not able to maintain zero balance (or mini balance) in non-
salary account.