LESSON PLAN

Faculty Name PROF. V. D. MISHRA

Semester: 1ST Session: 2021-2022 Contact Hours per week: 3
Subject: COMPUTER SYSTEM Branch: MCA Total Credit:3 (40 hrs)
ARCHITECTURE
Period NOVEMBER 2021 -APRIL 2022 Subject Code: MCA03001
Text Books: T1. Carl Hamacher, Zvonko Vranesic and Safwat
Zaky, “Computer Organization”, Fifth Edition, Tata
McGraw Hill, 2002.

T2. William Stallings, “Computer Organization and

Architecture– Designingfor Performance”,Sixth Edition,
Pearson Education, 2003.
.

Reference R1. John P Hayes, “Computer Organization”, McGraw Hill

books: .
R2 Morris Mano,” Computer System Architecture”, PHI
.

COURSE 1. To enable the student to know the basic concept of the software
OBJECTIVE engineering discipline, its evolution, impact and emergence of
S: software engineering and explain the development and use of
different software life cycle models for real-life industrial applications.
2. To enable the student to study different aspects of software project
management, risk management and configuration management and
explain various requirement elicitation, analysis and specification
techniques.

COURSE OUTCOME:

CO 1 The learner should be able to Understand the minimum requirements for the
development of application
CO2 The learner should be able to Know about the basic Software life cycle

CO 3 The learner should be able to develop, maintain, efficient, reliable and cost effective
software solutions
CO 4 The learner should be able to evaluate assumptions and arguments by using variant
software architectural styles & software process model
CO 5 The learner should be able to Understand software testing approaches such as unit
testing and integration testing
CO 6 The learner should be able to plan and analyze how to ensure good quality software .
Sl. No. Date Topics to be covered 60 Min Mode Link COs
propose Class of s
d Distrib Teachin
ution g
L ICT IM
M
Module – I Introduction)
1 30 30 GB CO-
Introduction
1
2 Review of basic computer GB CO-
architecture 2
3 Tutorial
class
4 Quantitative techniques in PPT CO-
computer design, 2
5 GB CO-
Measuring performance. 2

6 PPT CO-
reporting performance
2
7 Revision and question answer GB CO-
discussion(BPUT & Interview 2
Module – II ( Pipelining )

8 GB CO-
Basic concepts 2

9 Instruction and Arithmetic GB CO-

pipeline 2
10 GB CO-
Data hazards, 2
11 PPT CO-
Control hazards 2
13
Structural hazards
14 Techniques for handling hazards CO-
2

15 PPT CO-
Exception handling 2
16 CO-
Pipeline optimization
2
17 Revision and question answer
discussion(BPUT & Interview
18 Revision and question answer
discussion(BPUT & Interview
Module – III( Hierarchical memory technology )

19 GB CO-
Inclusion, Coherence and locality 3
properties,
20 GB CO-
Cache memory organizations 3
21 Techniques for reducing cache PPT CO-
misses 3
22 Virtual memory organization, PPT CO-
3
23 Mapping and Management GB CO-
techniques 3
24 PPT CO-
Tutorial class 3
25 PPT CO-
3
Memory replacement policies
26 Revision and question answer GB CO-
discussion(BPUT & Interview 3
27 Revision and question answer PPT CO-
discussion(BPUT & Interview 3
MODULE- IV ( Instruction-level Parallelism )

28 GB CO-
(08 Hours) 4
Basic
concept of
ILP
29 GB CO-
Techniques for increasing ILP, 4
30 GB CO-
Superscalar 6
31 Super pipelined and VLIW PPT CO-
Processor 6
32 PPT CO-
Array and Vector processors 6
33 Revision and question answer
discussion(BPUT & Interview
34 Revision and question answer
discussion(BPUT & Interview
35
MODULE- V ( Multiprocessor architecture )

39
(08 Hours)
Taxonomy
of Parallel
Architectur
es,
40 Centralized shared- memory
architecture
41 Synchronization,
42 Memory consistency,
43 Interconnection networks
44 Distributed shared memory
architecture
45 Cluster computers
46 Revision and question answer
discussion(BPUT & Interview
47 Revision and question answer
discussion(BPUT & Interview

Signature of the faculty

Date:

NOTE:

GB:-GREEN BOARD

LM:-LECTURE METHOD (THROUGH WHITE OR GREEN BOARD)

IM:- INTERACTIVE METHOD (THROUGH CASE STUDY, PPT, GD)

ICT:-INFORMATION AND COMMUNICATION TECHNOLOG

CO(COURSE OUTCOME) & COURSE OBJECTIVE IS DONE BY INDIVIDUAL

Ability to identify the minimum requirements for the

development of application
Ability to develop, maintain, efficient, reliable and cost effective
software solutions
Ability to critically thinking and evaluate assumptions and
arguments by using variant software architectural styles &
software process models
Understanding of software testing approaches such as unit
testing and integration testing
Understanding on quality control and how to ensure good
quality software.

Course title: ELECTIVE 2 - OBJECT ORIENTED SOFTWARE

ENGINEERING
 Course Code : Credits 03
L:T:P:S : 4:0:0:0 CIA Marks : 40
Exam Hours : 03 ESE Marks : 60
LEARNING OBJECTIVES:
On taking the course, the students will be able to
Develop the knowledge and practical skills needed to successfully
participate in the analysis, design and development of large
software systems, using object-oriented approaches, they can Apply
team dynamics by working in teams, focus on object-oriented
approaches and project management techniques Communicate the
science and Development of graphical user interfaces, and quality
assurance.

Course outcome: the end of course, the student will be able to

CO1 Knows the reason about the basic Software life cycle models
Importance of various kinds of Project Management methods, Tracking Software Quality,
Quality Standards and Metrics.
CO2 Develop System Concepts for Object Modelling Design and implement a software desig
concept to meet desired needs and Requirements.
Design the UML concepts like sequential, Use cases and Activity diagram

CO3 Concepts of Use cases, actors, and common modelling techniques.

Implementing the concept use cases, business actors, Significance of identifying the subsystem
and business requirements
CO4 Explain Design Workflow and System Design Concept Create Mapping Object Model to
Database Schema Testing and verification process Creation.

CO5 Usage of Software Configuration Management Definition and Types of maintenance

Life Build Reverse and re-engineering process.

Mapping of Course outcomes to program outcomes:

C0/PO/PSO PO PSO
1 2 3 4 5 6 7 8 1 2 3 4 5
CO1 3 3 3 3 3 3 3 3 2 2 2 3 2
CO2 3 3 2 3 3 3 3 3 2 3 3 3 3
CO3 3 3 2 3 3 3 3 3 2 3 3 3 3
CO4 3 3 2 3 3 3 3 3 2 3 3 3 3
CO5 3 3 2 2 2 2 3 3 2 3 2 3 2
CO6 3 3 2 3 3 2 3 3 2 3 2 3 2
3- Strong Correlation 2- Medium Correlation 1- Low Correlation
 1. To discuss the software engineering discipline, its evolution, impact
and emergence of software engineering and explain the development
and use of different software life cycle models for real-life industrial
applications.
2. To discuss different aspects of software project management, risk
management and configuration management and explain various
requirement elicitation, analysis and specification techniques.
3. To discuss various software design methodologies, the impact of
cohesion and coupling measures on the goodness of the software
design.
4. To discuss the importance of practicing different coding standards,
guidelines and different testing strategies along with software
reliability metrics and software quality management techniques and
standards.

On taking the course, the students will be able to

Develop the knowledge and practical skills needed to successfully
participate in the analysis, design and development of large
software systems, using object-oriented approaches, they can Apply
team dynamics by working in teams, focus on object-oriented
approaches and project management techniques Communicate the
science and Development of graphical user interfaces, and quality
assurance.

Course outcome: the end of course, the student will be able to

CO1 Knows the reason about the basic Software life cycle models
Importance of various kinds of Project Management methods, Tracking Software Quality,
Quality Standards and Metrics.
CO2 Develop System Concepts for Object Modelling Design and implement a software desig
concept to meet desired needs and Requirements.
Design the UML concepts like sequential, Use cases and Activity diagram

CO3 Concepts of Use cases, actors, and common modelling techniques.

Implementing the concept use cases, business actors, Significance of identifying the subsystem
and business requirements
CO4 Explain Design Workflow and System Design Concept Create Mapping Object Model to
Database Schema Testing and verification process Creation.
CO5 Usage of Software Configuration Management Definition and Types of maintenance
Life Build Reverse and re-engineering process.