Dept.

of Information Technology
VASAVI COLLEGE OF ENGINEERING
III Yr. IT- Software Engineering
Vision
To be a center of Excellence in Multi disciplinary learning and Research, where
students get acquainted with latest technologies and apply them for self and societal
growth.
Mission
To enable the students acquire outstanding competence and skills in latest
technologies through practice- oriented teaching and training.

1. Programme Educational Objectives

The Programme will produce graduates
1. With necessary theoretical and practical knowledge to gain employment
and advanced education and deal with problems in Information
Technology.
2. With effective written and oral communication skills that will help them to
work in a multidisciplinary and dynamic working environment.
3. Who have explored and developed their self, which enables them to
conduct themselves as good professionals and good citizens of the country.

2. Program Outcomes
At the end of the program, the graduates will demonstrate
a. Knowledge of required Mathematical, Electronic and Information Technology
Skills required in analyzing and solving real life problems.
b. Active participation in attempting and succeeding in competitive exams like
GATE, GRE, CAT etc.
c. An ability to identify, analyze and solve problems in the area of Information
Technology and Computer Science.
d. An ability to develop software programs using various programming languages to
solve problems.
e. An ability to develop software applications for different real time problems.
f. Skills in handling the different Engineering tools, software tools and Equipment in
analyzing and solving problems.
g. Good written and oral communication skills
h. An ability to work in laboratories and in a multi disciplinary environment.
i. An aptitude for continuous self education and ability for lifelong learning.
j. Good professional and Ethical responsibilities.
k. An understanding of the impact of Engineering solutions on the society at large
and will be aware of the contemporary issues.
l. Knowledge and understanding of the management principles as a team
player/leader while handling projects of multidisciplinary nature.

Graduate Attributes (based on OBE)

i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.

Engineering knowledge
Problem analysis
Design and development of solutions
Investigation of complex problem
Modern tool usage
Engineer and society
Environment and sustainability
Ethics
Individual and team work
Communication
Lifelong learning + project management and finance
Project management and finance
Programme
Educational
Objectives
1
2
3

PROGRAM
OUTCOMES
a
b
c
d
e
f
g
h
i
j
K
l

Programme Outcomes
a

X
X

X
X

ii

iii

x
x

x
x

x
x

x
x

X
X

GRADUATE ATTRIBUTES
iv
v
vi
vii viii ix

x
x
x
x

x
x
x
x

x
x
x
x
x

x
x

xi

xii

x
x
x
x
x
x
x

x
x

x
x

x
x

x
x
x
x

x
x
x

x
x
x
x
x

x
x
x
x
x

x
x

x
x
x

Prerequisites:
Programming Concepts
Objective:
Software Engineering study areas include software processes and management, and
modeling complex software systems and focuses on team-based projects, in which students
must conceive, design, implement and operate software engineering solutions. Students
develop skills and the ability to apply engineering principles to solving real world problems.
Learning Outcomes

1. Outcome1: The student will be able to select the most suitable software process
model out of several, for the development of a given software project.
[(a),(c),(e)]

2. Outcome2: The student will be able to develop the ability to elicit, analyze and
specify software requirements through a productive working relationship with various
stakeholders of the project.
[(a),(c),(e), (f),(g),(j)]

3. Outcome3: The student will be able to learn the software design principles and
understand how to apply them towards implementation.
[(a),(c),(e), (f)]
4. Outcome4: The student will be able to

compare different ways and techniques of

ensuring software quality and apply various test processes and techniques on
conventional applications. [(c),(e),(g)]

5. Outcome5: The student will be able to use various estimation methods to estimate
the effort required for a given project, develop an understanding of risks inherent to
software development, and provide continuous quality improvement.
[(c),(e),(g),(k)]

Course outcomes
1
2
3
4
5

Program Outcomes
a
b
c
d
X
X
X
X
X
X
X
X

e
X
X
X
X
X

X
X

X
X
X

l
X

Key Performance Indicators:

Outcome 1:
1.
List the general principles of software engineering.
2.
Can you distinguish between different process models by assessing them against a
particular project.
3.
Can you say that requirements model represents a snapshot of a system in time.
Outcome 2:
1.
How many different points of view can be used to describe the requirements
model? What are they?
2.
Develop a checklist for requirement gathering meeting.
3.
Will you interpret in your own words the scenario based requirement modeling with
an example.
4.
Develop a complete use-case for one of the following activities:
a) Making a withdrawal at an ATM.
b) Searching for books (on a specific topic) using an online bookstore.
Outcome 3:
1.
How would you elaborate on separation of concerns in your own words? Is there a
case when a divide-and-conquer strategy may not be appropriate? How might such
a case effect the argument for modularity?
2.
Suggest a design pattern that you encounter in a category of everyday things(e.g.,
consumer electronics, automobiles, appliances). Also, describe the patterns.
3.
Briefly describe each of the four elements of design model.
4.
How are the concepts of coupling and cohesion related to software module size?

Outcome 4:
1.
Garvin describes 5 different views of quality. Identify an example of each case
using one or more well known electronic products with which you are familiar.
2.
Compare and contrast verification and validation.
3.
Is it possible to assess the quality of software if the customer keeps changing what
it is supposed to do?
4.
Can you identify the different parts of a testing strategy for your mini-project.
5.
Test a user manual for an application that you use frequently. Find at least one
error in the documentation.
Outcome 5:
1.
Can you describe the difference between process and project metrics in your own
words.
2.
Justify with examples why some of the software metrics should be private and
some are public.
3.
Identify and list different known and unknown risks in general.
4.
Assume that you are the project manager for the team building that is your mini
project, create a project plan by considering the planning activity "estimation".
5.
Create a risk table that focuses the risks associate with the SPI process for your
own mini project developed.

Correlation of course with Program Outcomes:

Program Outcomes

Course Name &

Course Code

SE (BIT 302)

l
2

Strong Correlated 4- (If greater than 70% Course outcomes are matching with POs)
Moderately Correlated 3 (If greater than 40% and less than 70% Course outcomes
are matching with POs)
Weakly Correlated 2 (If less than 40% Course outcomes are matching with POs)
No Correlated 1 (If the Course outcomes do not match any of the POs)