Software Engineering Lab December 30, 1899

Experiment No. 3

Title: Application of two traditional

Process models

Name of Student:

Roll No. :

Date : ____ / ____ / ________

Subject In-charge Sign:

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

| Department of Computer Engineering | Sem-V

RIZVI COLLEGE OF Engineering
1
 Software Engineering Lab December 30, 1899

Experiment No. 3
Aim: Application of two traditional Process models on selected Project

Software: Following software’s are required to perform this experiment:-

1. Wordpad or Microsoft Word
2. Any window-based operating system

Theory:
A software process model is an abstraction of the software development process. The models
specify the stages and order of a process.

Diffrenet types of Process Models are:

• Waterfall model
• Incremental model
• V model
• RAD model
• Agile model
• Spiral model

Waterfall Model
 The Waterfall Model was the first Process Model to be introduced.
 It is also referred to as a linear-sequential model” or “Classic life cycle model”
 It is very simple to understand and use.
 In a waterfall model, each phase must be completed before the next phase can begin
and there is no overlapping in the phases.
 This model is used for the small projects.
 In this model, feedback is taken after each phase to ensure that the project is on the
right path
 Testing part starts only after the development is complete.
 It is used when user requirements are fixed and clear that may not change

| Department of Computer Engineering | Sem-V

RIZVI COLLEGE OF Engineering 2
 Software Engineering Lab December 30, 1899

• Communication:
• The software development process starts with communication between
customer and developer
• According to waterfall model customer must state all requirements at the
beginning of project
• Planning:
• It includes complete estimation(e.g. cost estimation of project) and scheduling
(complete timeline chart for project development) and testing
• Modelling:
• It includes detailed requirement analysis and project design(algorithm,
flowchart etc)
• Flowchart shows complete pictorial flow of program whereas algorithm is
step-by-step solution of problem
• Construction: It includes coding and testing steps:
• Coding: Design details are implemented using appropriate programming
language
• Testing: Testing is carried out to check whether flow of coding is correct, to
check out the errors of program
• Deployment:
• If customer suggest some corrections, or demands additional capabilities then
changes are required for such corrections or enhancement
• It includes software delivery, support and feedback from customer

Incremental Process Model

• The Incremental model combines the elements of waterfall model applied in an

interactive & iterative fashion. The first increment is generally a core product.
• Incremental Model is a process of software development where requirements divided
into multiple standalone modules of the software development cycle.
• Each Increment produces the product which is submitted to the customer. The
customer suggests some modifications.
• The next increment implements customer’s suggestions and some additional
requirements

| Department of Computer Engineering | Sem-V

RIZVI COLLEGE OF Engineering 3
 Software Engineering Lab December 30, 1899

• In this model, each module goes through the requirements, design, implementation
and testing phases.

Waterfall Model for Library Management System

1)Communication:Requirements are gathered from Customer

 Requirements given by customer are:( For Staff/Student)

o Registration
o Login
o Search Book(By Author,Book Title,Frequently Referred etc)
o Issue Book
 Check Limit
 Check if valid member
 Check Availabilty
o Return Book
 Check if valid member
 Check for Fine
o Renew Book
 Check if valid member

 Requirements given by customer are:( For Librarian/Admin)

o Registration
o Login
o Search Book(By Author,Book Title,Frequently Referred etc)
o Monitor Request(Issue Book,Renew Book,Return Book)
o Add New Book
o Remove Book
o Update Record

2)Planning:

a)Cost Estimation:

 Hardware: Computer/Laptop,Bar code Scanner,server

 Software: Operating system
 Manpower cost/month

b)Schedule:

 Implementation of all the requirements must completed in two months.

(Date:01/10/2021)
 Testing must be completed in next 15 days of development.(Date:16/10/2021)
Delivery to the customer-20/10/2021

| Department of Computer Engineering | Sem-V

RIZVI COLLEGE OF Engineering 4
 Software Engineering Lab December 30, 1899

c)Tracking Progress:

 Checks that whether the Implemetation and Testing progressing as per the
schedule.

3)Modelling:

 FUNCTIONAL REQUIREMENTS

 NORMAL USER

 USER LOGIN

Description of feature

This feature used by the user to login into system. They are required to enter user id and
password before they are allowed to enter the system .The user id and password will be
verified and if invalid id is there user is allowed to not enter the system.

Functional requirements

-user id is provided when they register

-The system must only allow user with valid id and password to enter the system

-The system performs authorization process which decides what user level can acess to.

-The user must be able to logout after they finished using system.

REGISTER NEW USER

Description of feature

This feature can be performed by all users to register new user to create account.

Functional requirements

System must be able to verify information -System must be able to delete information if
information is wrong.

REGISTER NEW BOOK

Description of feature

This feature allows to add new books to the library

Functional requirements

-System must be able to verify information

| Department of Computer Engineering | Sem-V
RIZVI COLLEGE OF Engineering 5
 Software Engineering Lab December 30, 1899

-System must be able to enter number of copies into table.

- System must be able to not allow two books having same book id.

SEARCH BOOK

Description of feature

This feature is found in book maintenance part . we can search book based on book id , book
name , publication or by author name.

Functional requirements

- System must be able to search the database based on select search type

- System must be able to filter book based on keyword entered

- System must be able to show the filtered book in table view

SOFTWARE AND HARDWARE REQUIREMENTS

This section describes the software and hardware requirements of the system

SOFTWARE REQUIREMENTS

 Operating system- Windows 7 is used as the operating system as it is stable and supports
more features and is more user friendly

 Database MYSQL-MYSQL is used as database as it easy to maintain and retrieve records

by simple queries which are in English language which are easy to understand and easy to
write.

 Development tools and Programming language- HTML is used to write the whole code and
develop webpages with css, java script for styling work and php for server side scripting.

HARDWARE REQUIREMENTS

 Intel core i5 2nd generation is used as a processor because it is fast than other processors
and provide reliable and stable performance and we can run our pc for longtime. By using
this processor we can keep on developing our project without any worries.

 Ram 1 gb is used as it will provide fast reading and writing capabilities and will in turn
support in processing.

SOFTWARE TOOLS USED

The whole Project is divided in two parts the front end and the back end.

Front end The front end is designed using of html , Php ,css, Java script

| Department of Computer Engineering | Sem-V

RIZVI COLLEGE OF Engineering 6
 Software Engineering Lab December 30, 1899

4)Construction: It includes coding and testing steps:

• Coding: Design details are implemented using appropriate programming language
• Testing: Testing is carried out to check whether flow of coding is correct, to check
out the errors of program

The aim of the system testing process was to determine all defects in our project .The
program was subjected to a set of test inputs and various observations were made and based
on these observations it will be decided whether the program behaves as expected or not. Our
Project went through two levels of testing

1.Unit testing

2.Integration testing

UNIT TESTING

Unit testing is undertaken when a module has been created and succesfully reviewed .In order
to test a single module we need to provide a complete environment ie besides the module we
would require

 The procedures belonging to other modules that the module under test calls

 Non local data structures that module accesses

 A procedure to call the functions of the module under test with appropriate parameters

Test For the admin module

 Testing admin login form-This form is used for log in of administrator of the system.In this
we enter the username and password if both are correct administration page will open other
wise if any of data is wrong it will get redirected back to the login page and again ask for
username and password

| Department of Computer Engineering | Sem-V

RIZVI COLLEGE OF Engineering 7
 Software Engineering Lab December 30, 1899

 Student account addition- In this section the admin can verify student details from student
academinc info and then only add student details to main library database it contains add and
delete buttons if user click add button data will be added to student database and if he clicks
delete button the student data will be deleted

Book Addition

- Admin can enter details of book and can add the details to the main book table also he can
view the books requests .

Test for Student login module

 Test for Student login Form-This form is used for log in of Student .In this we enter
thelibraryid, username and password if all these are correct student login page will open other
wise if any of data is wrong it will get redirected back to the login page and again ask for
libraryid, username and password.

 Test for account creation- This form is used for new account creation when student does not
fill the form completely it asks again to fill the whole form when he fill the form fully it gets
redirected to page which show waiting for conformation message as his data will be only
added by administrator after verification.

 Test for teacher login

This form is used for logg in of teacher .In this we enter the username and password if all
these are correct teacher login page will open other wise if any of data is wrong it will get
redirected back to the login page and again ask for username and password.

INTEGRATION TESTING
In this type of testing we test various integration of the project module by providing the
input.The primary objective is to test the module interfaces in order to ensure that no errors
are occurring when one module invokes the other module.

5) Deployment:
• If customer suggest some corrections, or demands additional capabilities then
changes are required for such corrections or enhancement
• It includes software delivery, support and feedback from customer

Incremental Model for Library Management System

1)Communication:Requirements are gathered from Customer

 Requirements given by customer are:( For Staff/Student)

o Registration
o Login

| Department of Computer Engineering | Sem-V

RIZVI COLLEGE OF Engineering 8
 Software Engineering Lab December 30, 1899

o Search Book(By Author,Book Title,Frequently Referred etc)

o Issue Book
 Check Limit
 Check if valid member
 Check Availabilty
o Return Book
 Check if valid member
 Check for Fine
o Renew Book
 Check if valid member

 Requirements given by customer are:( For Librarian/Admin)

o Registration
o Login
o Search Book(By Author,Book Title,Frequently Referred etc)
o Monitor Request(Issue Book,Renew Book,Return Book)
o Add New Book
o Remove Book
o Update Record

2)Planning

a)Cost Estimation:

 Hardware: Computer/Laptop,Scanner,server
 Software: Operating system
 Manpower cost/month

b)Schedule:
Firstly, All the requirements are divided in groups
Group 1: To be implemented in 1st Increment
 Requirements:( For Staff/Student)
o Registration
o Login
o Search Book(By Author,Book Title,Frequently Referred etc)
 Requirements:( For Librarian/Admin)
o Registration
o Login
o Search Book(By Author,Book Title,Frequently Referred etc)

Group 2: To be implemented in 2nd Increment

 Requirements:( For Staff/Student)
o Issue Book
 Check Limit

| Department of Computer Engineering | Sem-V

RIZVI COLLEGE OF Engineering 9
 Software Engineering Lab December 30, 1899

 Check if valid member

 Check Availabilty
o Return Book
 Check if valid member
 Check for Fine
o Renew Book
 Check if valid member
 Requirements:( For Librarian/Admin)
o Monitor Request(Issue Book,Renew Book,Return Book)
o Add New Book
o Remove Book
o Update Record

 Group 1 -Requirements must be completed in 15 days (Date:15/08/2021)

 Group 2 - Requirements must be completed in next 20 days (Date:10/09/2021)

c)Tracking:

 Checks that whether the Implemetation and Testing progressing as per the schedule.

FUNCTIONAL REQUIREMENTS

NORMAL USER

USER LOGIN

Description of feature

This feature used by the user to login into system. They are required to enter user id and
password before they are allowed to enter the system .The user id and password will be
verified and if invalid id is there user is allowed to not enter the system.

Functional requirements

-user id is provided when they register

-The system must only allow user with valid id and password to enter the system

-The system performs authorization process which decides what user level can acess to.

-The user must be able to logout after they finished using system.

REGISTER NEW USER

Description of feature

This feature can be performed by all users to register new user to create account.

| Department of Computer Engineering | Sem-V

RIZVI COLLEGE OF Engineering 10
 Software Engineering Lab December 30, 1899

Functional requirements

-System must be able to verify information -System must be able to delete information if
information is wrong

REGISTER NEW BOOK

Description of feature

This feature allows to add new books to the library

Functional requirements

-System must be able to verify information

-System must be able to enter number of copies into table.

- System must be able to not allow two books having same book id.

SEARCH BOOK

Description of feature

This feature is found in book maintenance part . we can search book based on book id , book
name , publication or by author name.

Functional requirements

- System must be able to search the database based on select search type

- System must be able to filter book based on keyword enterd

- System must be able to show the filtered book in table view

Functional requirements

-System should be able to add detailed information about events .

-System should be able to display information on notice board available in the homepage of
site

SOFTWARE AND HARDWARE REQUIREMENTS

This section describes the software and hardware requirements of the system

SOFTWARE REQUIREMENTS

 Operating system- Windows 7 is used as the operating system as it is stable and supports
more features and is more user friendly

| Department of Computer Engineering | Sem-V

RIZVI COLLEGE OF Engineering 11
 Software Engineering Lab December 30, 1899

 Database MYSQL-MYSQL is used as database as it easy to maintain and retrieve records

by simple queries which are in English language which are easy to understand and easy to
write.

 Development tools and Programming language- HTML is used to write the whole code and
develop webpages with css, java script for styling work and php for sever side scripting.

HARDWARE REQUIREMENTS

 Intel core i5 2nd generation is used as a processor because it is fast than other processors an
provide reliable and stable and we can run our pc for longtime. By using this processor we
can keep on developing our project without any worries.

 Ram 1 gb is used as it will provide fast reading and writing capabilities and will in turn
support in processing.

SOFTWARE TOOLS USED

The whole Project is divided in two parts the front end and the back end.

Front end The front end is designed using of html , Php ,css, Java script

4)Construction: It includes coding and testing steps:

Coding: Design details are implemented using appropriate programming language

 Here, Each group will implement it’s own group of requirements in given scheduled time

Testing: Testing is carried out to check whether flow of coding is correct, to check out the
errors of program

The aim of the system testing process was to determine all defects in our project .The
program was subjected to a set of test inputs and various observations were made and based
| Department of Computer Engineering | Sem-V
RIZVI COLLEGE OF Engineering 12
 Software Engineering Lab December 30, 1899

on these observations it will be decided whether the program behaves as expected or not. Our
Project went through two levels of testing

1.Unit testing

2.Integration testing

UNIT TESTING

Unit testing is undertaken when a module has been created and succesfully reviewed .In order
to test a single module we need to provide a complete environment ie besides the module we
would require

 The procedures belonging to other modules that the module under test calls

 Non local data structures that module accesses

 A procedure to call the functions of the module under test with appropriate parameters

Test For the admin module

 Testing admin login form-This form is used for log in of administrator of the system.In this
we enter the username and password if both are correct administration page will open other
wise if any of data is wrong it will get redirected back to the login page and again ask for
username and password

 Student account addition- In this section the admin can verify student details from student
academic info and then only add student details to main library database it contains add and
delete buttons if user click add button data will be added to student database and if he clicks
delete button the student data will be deleted

Book Addition

- Admin can enter details of book and can add the details to the main book table also he can
view the books requests .

Test for Student login module

 Test for Student login Form-

This form is used for log in of Student .In this we enter thelibraryid, username and password
if all these are correct, student login page will open other wise if any of data is wrong it will
get redirected back to the login page and again ask for libraryid, username and password.

 Test for account creation-

| Department of Computer Engineering | Sem-V

RIZVI COLLEGE OF Engineering 13
 Software Engineering Lab December 30, 1899

This form is used for new account creation when student does not fill the form completely it
asks again to fill the whole form when he fill the form fully it gets redirected to page which
show waiting for confirmation message as his data will be only added by administrator after
verification.

 Test for teacher login -

This form is used for log in of teacher .In this we enter the username and password if all these
are correct teacher login page will open other wise if any of data is wrong it will get
redirected back to the login page and again ask for username and password.

INTEGRATION TESTING
In this type of testing we test various integration of the project module by providing the
input.The primary objective is to test the module interfaces in order to ensure that no errors
are occurring when one module invokes the other module.

5) Deployment:
• If customer suggest some corrections, or demands additional capabilities then
changes are required for such corrections or enhancement
• It includes software delivery, support and feedback from customer

Pre Lab Questions:

1. What is Software Process Model?
2. What are different types of Process models?
Post Lab Questions:
1. Which Process Model is best suitable for your case study/Project?
2. Why do you think so?

Lab Outcome: Identify requirements and apply software process model to selected case
study.

Conclusion: Thus, we have studied Traditional Process models i.e. Waterfall and
Incremental Process model and its application to the selected project.

| Department of Computer Engineering | Sem-V

RIZVI COLLEGE OF Engineering 14