Course Handout Software Engineering
Course Handout Software Engineering
NO TOPIC PAGE NO
1 Course Description
2 Vision and Mission of the Institute
3 Vision and Mission of the department
4 PEOs
5 POs
6 PSOs
7 Academic calendar
8 Class Timetable (for A, B, C, D Sections)
9 Individual Work load of course teachers
10 Student Nominal Rolls
11 Prerequisites
12 Course Objective
13 Course Outcomes
14 Syllabus
15 Course plan with Teaching Methodology adopted
16 Mapping delivery methodology with course outcomes
17 Students Reference Notes
18 References/ E-Links
19 Question papers of Previous Years
20 Unit Wise quiz Question Bank
21 Unit wise Short and Long Questions
22 Revised Bloom’s Taxonomy Levels
23 Course Mapping with PO’s, PSO’s and PEO’s
24 Course Articulation Matrix with justification
25 Evaluation Scheme
26 Assessment Methodology: Direct
i)Internal Question Papers
ii) Internal Award List
iii)External Question Paper
iv) External Award List/T-Sheet
27 Assessment Methodology: Indirect
i) Course End Survey Questionnaire
ii) Feedback report
28 CO-PO-PSO Attainment Matrix
Year: II
Semester: II
Course Type: Regular
Regulation: R22
Course Structure:
Theory:
Lecture Tutorials Credits
3 0 3
Vision: The institute endeavors towards imparting quality education with ethical values and
strives to make students technically competent to reach high level of achievements an make our
nation self-reliant and globally recognized.
Mission: The institute is committed and dedicated to mould the students into quality engineers
and technologists with aplomb by providing world class scientific and technical education
through:
Ensuring excellent branch wise infrastructure facilities, with eminent and qualified
faculty.
Making the institute a research/resource centre to enhance scope for consultancy and
R&D.
Vision:
Department envisages the development of global professionals with a strong computational
background, entrepreneurial qualities and technical knowledge to meet the industry and societal
needs, sustaining ethical and moral values.
Mission:
Evolving competitive and technical knowledge through innovative ICT based teaching-
learning process.
Developing academic as well as industry-oriented skill sets.
Inculcating, ethical and moral values with leadership qualities and lifelong learning
appetite.
4. Program Educational Objectives:
The Programme Educational Objectives of the programme offered by the department are listed
below:
PEO-1: The Graduates will be able to design and develop solutions for real life technical
problems using modern engineering tools.
PEO-2: Ability to analyze and interpret experimental results in frontier areas of Computer
Science and Engineering and appetite for higher learning and research in multidisciplinary areas.
5. Program Outcomes:
Upon completion of 4 year under graduate program, the student will be able to possess the
following outcomes
PO1: Engineering Knowledge: Apply the knowledge of mathematics, science, engineering
fundamentals, and an engineering specialization to the solution of complex engineering problems.
PO2: Problem Analysis: Identify, formulate, review research literature, and analyse complex
engineering problems reaching substantiated conclusions using first principles of mathematics,
natural sciences, and engineering sciences.
PO3: Design/Development of solutions: Design solutions for complex engineering problems and
design system components or processes that meet the specified needs with appropriate
consideration for the public health and safety, and the cultural, societal, and environment
considerations.
PO4: Conduct investigations of Complex Problems: Use research-based knowledge and
research methods including design of experiments analysis and interpretation of data, and
synthesis of the information to provide valid conclusions for complex problems.
PO5: Modern Tool Usage: create, select, and apply appropriate techniques, resources, and
modern engineering and IT tools including prediction and modelling to complex engineering
activities with an understanding of the limitations.
PO6: The Engineer and Society: Apply reasoning informed by the contextual knowledge to
assess societal, health, safety, legal and cultural issues and the consequent responsibilities relevant
to the professional engineering practice.
PO7: Environment and sustainability: Understand the impact of the professional engineering
solutions in societal and environmental contexts, demonstrate the knowledge of, and need for
sustainable development.
PO8: Ethics: Apply ethical principles and commit to professional ethics, responsibilities and
norms of the engineering practice.
PO9: Individual Teamwork: Function effectively as an individual, and as a member or leader in
diverse teams, and in multi-disciplinary settings.
PO10: Communication: Communicate effectively on complex engineering activities with the
engineering community and with society, such as, being able to comprehend and write effective
reports and design documentation, make effective presentations, and give and receive clear
instructions.
PO11: Project Management and Finance: Demonstrate knowledge and understanding of the
engineering and management principles and apply these to ones own work, as a member and
leader in a team, to manage projects and in multi-disciplinary environments.
PO12: Life-long Learning: Recognize the need for, and have the preparation and ability to
engage in independent and life-long learning in the broadest context of technological change.
PSO1: Developing software applications with key focus on privacy, cost and utility.
PSO2: Storing, processing, analysing, communicating the data for effective decision-making
while finding solutions for problems.
Academic calendar:
LIBRAR
MON WT DAA OOPS SE ES
Y
TUE AECS LAB DAA DBMS ES
WED DBMS SE WT DBMS LAB
MENTO
THU SE DBMS
OOPS WT DAA RING
FRI DAA OOPS DBMS OOPS LAB
SAT SE WT OOPS WT LAB
PRINCIP
HOD CSE (AI & IML) AL
LIBRAR
MON DBMS OOPS SE
DAA WT Y
TUE SE DBMS DAA OOPS LAB
WED WT DBMS DAA SE OOPS ES
MENTO
THU OOPS ES
WT LAB RING
FRI AECS LAB OOPS WT DBMS
SAT DAA WT SE DBMS LAB
Phone
S.No Mentees Roll No's Mentors Name
No
22k91A6666 TO 9347809
1
22K91A6687,23K95A6605,606 Mrs.CH.Shilpa 244
22K91A6688 TO 9063092
2
22K91A66A8,23K95A6607,608,609 Mrs.M.Swetha 083
6303097
3 22K91A66A9 TO 22K91A66D0 Mrs.K.Teja Reddy
287
PR
HOD CSE (AI & IML) INCIPAL
Mrs.CH.Shilpa
9.40- 12.40- 2.20-
Period/Day 10.40-11.40 11.40-12.40 1.20-2.20 3.20-4.20
10.40 1.20 3.20
MON SE-B SE-A
TUE SE-B
WED SE-A SE-B
LUNCH
THU SE-A
FRI
SAT SE-A SE-B WT LAB-A
Mrs.G.Srivani
9.40-
Period/Day 10.40-11.40 11.40-12.40 12.40-1.20 1.20-2.20 2.20-3.20 3.20-4.20
10.40
MON SE-C
TUE SE-C
WED DBMS LAB-A
LUNCH
THU SE-C
FRI OOPS LAB-A
SAT SE-C
Software engineering skills, such as programming languages, software development tools, software
design, testing, and debugging.
1. Ability to translate end-user requirements into system and software requirements, using e.g.
UML, and structure the requirements in a Software Requirements Document (SRD).
2. Identify and apply appropriate software architectures and patterns to carry out high level design
of a system and be able to critically compare alternative choices.
3. Will have experience and/or awareness of testing problems and will be able to develop a simple
testing report
12. Syllabus:
UNIT I
Introduction to Software Engineering:
The evolving role of software, changing nature of software, software myths. A Generic view of
process: Software engineering- a layered technology, a process frame work, the capability
maturity model integration (CMMI). Process models: The waterfall model, Incremental process
models, Spiral model, prototyping and unified process. Agile view of process: Agile process, agile
process models.
UNIT II
Software Requirements: Functional and non-functional requirements, user requirements, system
requirements, interface specification, the software requirements document. Requirements
engineering process: Feasibility studies, requirements elicitation and analysis, requirements
validation, requirements management.
UNIT III
Design Engineering: Design process and design quality, design concepts, the design model.
Creating an architectural design: software architecture, data design, architectural styles and
patterns, architectural design. Conceptual model of UML: SDLC, Basic structural modeling- class
diagrams, Interaction diagrams- sequence diagrams, collaboration diagrams, use case diagrams,
activity diagrams component diagrams, deployment diagrams.
UNIT IV
Testing Strategies: A strategic approach to software testing, test strategies for conventional
software, black-box and white-box testing, validation testing, system testing, the art of debugging.
Metrics for Process and Products: Software measurement, metrics for software quality.
UNIT- V Risk management: Reactive Vs proactive risk strategies, software risks, risk
identification, risk projection, risk refinement, RMMM. Quality Management: Quality concepts,
software quality assurance, software reviews, formal technical reviews, statistical software quality
assurance, software reliability, the ISO 9000 quality standards.
TEXT BOOKS:
1. Software Engineering, A practitioner’s Approach- Roger S. Pressman, 6th edition, McGraw Hill
International Edition.
2. Software Engineering- Sommerville, 7th edition, Pearson Education.
3. The unified modeling language user guide Grady Booch, James Rambaugh, Ivar Jacobson,
Pearson Education.
REFERENCE BOOKS:
1. Software Engineering, an Engineering approach- James F. Peters, WitoldPedrycz, John Wiley.
2. Software Engineering principles and practice- Waman S Jawadekar, The McGraw-Hill
Companies.
3. Fundamentals of object-oriented design using UML Meiler page-Jones: Pearson Education
Section A:
UNIT - I
1 Introduction to Software Engineering
2 29/2/2024 The evolving role of software, changing nature of software
3 2/3/2024 software myths.
4 4/3/2024 Software engineering- a layered technology
5 7/3/2024 a process frame work
6 11/3/2024 the capability maturity model integration (CMMI)
7 12/3/2024 Process models: The waterfall model,
8 14/3/2024 Incremental process models, Spiral model,
9 16/3/2024 proto typing and unified process.
10 18/3/2024 Agile process,
11 19/3/2024 agile process models
12 21/3/2024 Revision on Unit-I
Total number of Lecture hours for Unit -I
UNIT - II
13 23/3/2024 Software Requirements: Functional and non-functional requirem
14 26/3/2024 user requirements, system requirements, interface specification
15 28/3/2024 the software requirements document
16 30/3/2024 Requirements engineering process: Feasibility studies,
17 1/4/2024 requirements elicitation and analysis, requirements validation
18 2/4/2024 requirements management.
19 4/4/2024 SEMINARS
20 6/4/2024 TEST
Total number of Lecture hours for Unit -II
UNIT - III
21 8/4/2024 Design Engineering: Design process and design quality
22 15/4/2024 design concepts
23 16/4/2024 the design model
24 18/4/2024 Creating an architectural design: software architecture
25 20/4/2024 architectural styles and patterns
26 22/4/2024 architectural design,data design
27 23/4/2024 Revision for UNIT-I,II,III
28 29/4/2024 Conceptual model of UML: SDLC
29 30/4/2024 Basic structural modeling- class diagrams
30 2/5/2024 Interaction diagrams,sequence diagrams,
31 4/5/2024 collaboration diagrams, use case diagrams,
32 6/5/2024 activity diagrams component diagrams
33 7/5/2024 deployment diagrams.
Total number of Lecture hours for Unit -III
UNIT - IV
34 9/5/2024 Testing Strategies: A strategic approach to software testing
35 13/5/2024 test strategies for conventional software
36 14/5/2024 black-box testing
37 16/5/2024 white-box testing
38 18/5/2024 validation testing
39 3/6/2024 system testing
40 4/6/2024 the art of debugging
41 6/6/2024 Metrics for Process and Products: Software measurement
42 10/6/2024 metrics for software quality
43 11/6/2024 Revision Unit-IV
Total number of Lecture hours for Unit -IV
UNIT -V
44 13/6/2024 Risk management: Reactive Vs proactive risk strategies
45 15/6/2024 software risks, risk identification
46 18/6/2024 risk projection, risk refinement
47 20/6/2024 RMMM.
48 22/6/2024 Quality Management: Quality concepts
49 24/6/2024 software quality assurance
50 25/6/2024 Software reviews, formal technical reviews,
51 27/6/2024 Statistical software quality assurance
52 29/6/2024 software reliability,
53 1/7/2024 the ISO 9000 quality standards.
54 2/7/2024 SEMINARS
55 4/7/2024 Revision
Total number of Lecture hours for Unit -V
Total No. of Classes
Section B:
S.NO EXPECTED ACTUAL
. DATE DATE Topic(s) to be covered
UNIT - I
1 Introduction to Software Engineering
2 1/3/2024 The evolving role of software, changing nature of software
3 2/3/2024 software myths.
4 4/3/2024 Software engineering- a layered technology
5 7/3/2024 a process frame work
6 11/3/2024 the capability maturity model integration (CMMI)
7 12/3/2024 Process models: The waterfall model,
8 13/3/2024 Incremental process models, Spiral model,
9 16/3/2024 proto typing and unified process.
10 18/3/2024 Agile process,
11 12/3/2024 agile process models
12 21/3/2024 Revision on Unit-I
Total number of Lecture hours for Unit -I
UNIT - II
13 24/3/2024 Software Requirements: Functional and non-functional requirem
14 26/3/2024 user requirements, system requirements, interface specification
15 28/3/2024 the software requirements document
16 30/3/2024 Requirements engineering process: Feasibility studies,
17 1/4/2024 requirements elicitation and analysis, requirements validation
18 3/4/2024 requirements management.
19 4/4/2024 SEMINARS
20 6/4/2024 TEST
Total number of Lecture hours for Unit -II
UNIT - III
21 9/4/2024 Design Engineering: Design process and design quality
22 15/4/2024 design concepts
23 16/4/2024 the design model
24 17/4/2024 Creating an architectural design: software architecture
25 20/4/2024 architectural styles and patterns
26 22/4/2024 architectural design,data design
27 23/4/2024 Revision for UNIT-I,II,III
28 29/4/2024 Conceptual model of UML: SDLC
29 30/4/2024 Basic structural modeling- class diagrams
30 4/5/2024 Interaction diagrams,sequence diagrams,
31 5/5/2024 collaboration diagrams, use case diagrams,
32 6/5/2024 activity diagrams component diagrams
33 7/5/2024 deployment diagrams.
Total number of Lecture hours for Unit -III
UNIT - IV
34 10/5/2024 Testing Strategies: A strategic approach to software testing
35 13/5/2024 test strategies for conventional software
36 14/5/2024 black-box testing
37 16/5/2024 white-box testing
38 18/5/2024 validation testing
39 3/6/2024 system testing
40 4/6/2024 the art of debugging
41 5/6/2024 Metrics for Process and Products: Software measurement
42 10/6/2024 metrics for software quality
43 11/6/2024 Revision Unit-IV
Total number of Lecture hours for Unit -IV
UNIT -V
44 14/6/2024 Risk management: Reactive Vs proactive risk strategies
45 16/6/2024 software risks, risk identification
46 18/6/2024 risk projection, risk refinement
47 20/6/2024 RMMM.
48 22/6/2024 Quality Management: Quality concepts
49 24/6/2024 software quality assurance
50 25/6/2024 Software reviews, formal technical reviews,
51 27/6/2024 Statistical software quality assurance
52 29/6/2024 software reliability,
53 1/7/2024 the ISO 9000 quality standards.
54 2/7/2024 SEMINARS
55 4/7/2024 Revision
Total number of Lecture hours for Unit -V
Total No. of Classes
Section C:
UNIT - II
13 26//3/24 Software Requirements: Functional and non-functional requirem
14 28/3/24 user requirements, system requirements, interface specification
15 30/3/24 the software requirements document
16 04-01-2024 Requirements engineering process: Feasibility studies,
17 04-02-2024 requirements elicitation and analysis, requirements validation
18 04-04-2024 requirements management.
19 04-06-2024 SEMINARS
20 04-08-2024 TEST
Total number of Lecture hours for Unit -II
UNIT - III
21 15/4/2024 Design Engineering: Design process and design quality
22 16/4/2024 design concepts
23 18/4/2024 the design model
24 20/4/2024 Creating an architectural design: software architecture
25 22/4/2024 architectural styles and patterns
26 23/4/2024 architectural design,data design
27 23/4/2024 Revision for UNIT-I,II,III
28 29/4/2024 Conceptual model of UML: SDLC
29 30/4/2024 Basic structural modeling- class diagrams
30 05-02-2024 Interaction diagrams,sequence diagrams,
31 05-04-2024 collaboration diagrams, use case diagrams,
32 05-06-2024 activity diagrams component diagrams
33 05-07-2024 deployment diagrams.
Total number of Lecture hours for Unit -III
UNIT - IV
34 05-09-2024 Testing Strategies: A strategic approach to software testing
35 13/5/2024 test strategies for conventional software
36 14/5/2024 black-box testing
37 16/5/2024 white-box testing
38 18/5/2024 validation testing
39 06-03-2024 system testing
40 06-04-2024 the art of debugging
41 06-06-2024 Metrics for Process and Products: Software measurement
42 06-10-2024 metrics for software quality
43 06-11-2024 Revision Unit-IV
Total number of Lecture hours for Unit -IV
UNIT -V
44 13/6/2024 Risk management: Reactive Vs proactive risk strategies
45 15/6/2024 software risks, risk identification
46 18/6/2024 risk projection, risk refinement
47 20/6/2024 RMMM.
48 22/6/2024 Quality Management: Quality concepts
49 24/6/2024 software quality assurance
50 25/6/2024 Software reviews, formal technical reviews,
51 27/6/2024 Statistical software quality assurance
52 29/6/2024 software reliability,
53 07-01-2024 the ISO 9000 quality standards.
54 07-02-2024 SEMINARS
55 07-04-2024 Revision
Total number of Lecture hours for Unit -V
Total No. of Classes
14. Mapping delivery methodology with course outcomes:
Presentations √ √ √ √ √
Laboratory sessions √
Assignments √
E-Learning resources √ √ √ √ √
Model Paper √ √ √ √ √
https://drive.google.com/drive/folders/1SkR63Gxa4P3lHEzs2dk3vb9swP4L8Ol_?usp=sharing
https://drive.google.com/drive/folders/1SkR63Gxa4P3lHEzs2dk3vb9swP4L8Ol_?usp=sharing
UNIT-1
9.Which software development model requires thorough planning before any development
begins?
A) Waterfall model
B) Agile methodology
C) Incremental model
D) RAD (Rapid Application Development)
Answer: A) Waterfall model
UNIT-II
A)Inspections
B)Prototyping
C)Pair programming
D)Code refactoring
A) Use case
B)Functional requirement
C)Non-functional requirement
D)Coding standard
6.What is the purpose of a use case diagram in requirements engineering?
A) Mo Scow method
B)Bubble sort
C)Fibonacci sequence
D) Binary search
UNIT-III
1.Which of the following is NOT a primary consideration in design engineering?
a) Functionality
b) Aesthetics
c) Cost-effectiveness
d) Manufacturing process
6.Which software is commonly used for finite element analysis (FEA) in design engineering?
a) MATLAB
b) AutoCAD
c) SolidWorks
d) ANSYS
7.What does DFM stand for in design engineering?
a) Design for Manufacturability
b) Detailed Functional Modeling
c) Direct Fabrication Method
d) Digital Feedback Mechanism
UNIT-IV
5.Which testing technique is also known as "glass box" or "clear box" testing?
a) Black box testing
b) System testing
c) White box testing
d) Regression testing
6.Which testing technique focuses on ensuring that changes in one part of the software do not
adversely affect other parts?
a) Integration testing
b) System testing
c) Regression testing
d) Acceptance testing
8.Which type of testing is typically performed by end-users to ensure that the software meets their
business requirements?
a) Unit testing
b) Integration testing
c) System testing
d) Acceptance testing
UNIT-V
2. Which of the following risk is the failure of a purchased component to perform as expected?
a) Product risk
b) Project risk
c) Business risk
d) Programming risk
3.Which of the following term is best defined by the statement: “There will be a change of
organizational management with different priorities.”?
a) Staff turnover
b) Technology change
c) Management change
d) Product competition
A)Risk identification
B)Risk analysis
C)Risk celebration
D)Risk mitigation
A)Risk identification
B)Risk analysis
C)Risk celebration
D)Risk mitigation
8.What does the acronym "SWOT" stand for in the context of risk analysis?
a)Software Workflow and Optimization Techniques
b)Strengths, Weaknesses, Opportunities, Threats
c)Software Workbench for Optimization and Testing
d)Systematic Workflow and Organizational Techniques
Part-A
1. What is software engineering activity?
2. Compare waterfall model and spiral model.
3. What is software development life cycle?
4. What are the advantages of waterfall model?
5. What are the five framework activities?
6. Define CMMI.
7. Define legacy software.
8. What is incremental model?
Part-B
1. Define software engineering. What are the challenges of software engineering? 2. a. Explain
spiral model with metrics and demerits.
b. Discuss different software myths and their consequences.
3. Explain about specialized process models
4. Explain the following process models a. The incremental model. b. The RAD model.
5. Explain CMMI with a neat diagram.
6. a. Explain about the waterfall model with neat diagram. b. Explain integrity constraints over
relations
UNIT II
Part-A
1.Explain the kinds of system requirements.
2. Explain context model.
3. What is meant by requirement management?
4. What are functional requirements for software?
5. Define functional requirements.
6. Define software requirements documentation.
7. What is meant system requirements? 8. What are non-functional requirements?
Part-B
1. Which model in system modeling depicts the static nature of the system? Explain in detail.
2. What are the characteristics of software requirement documentation (SRD)?
3. Explain about requirements validation.
4. Describe five desirable characteristics of a good software requirement specification document.
5. Differentiate between functional and non-functional requirements.
6. Explain adaptive software development with neat diagram. B. List and explain the object model in brief.
7. Which model in system modeling depicts the static nature of the system? Explain in detail.
8. What are the characteristics of software requirement documentation.
9. Show how we represent a. Data models. b. Explain behavioral models and object models.
10. What are the characteristic of software requirement documentation (SRD).
UNIT-III
Part-A
1. What is design?
2. What is interface design?
3. Define software architecture.
4. What is data design?
5. List the principles of software design. 6. Write about interface design evaluation.
Part-B
1.Write about design quality.
2. Describe mapping data flow into software architecture.
3. a. How do you assess the quality of a software design?
b. Explain clearly architectural styles and patterns.
4. Explain the process of mapping data flow into software architecture.
5. What is coupling? How it differs from cohesion. Describe the types of coupling.
UNIT-IV
Part-A
1. What is testing?
2. Elaborate on metrics of software quality.
3. Compare between alpha testing and beta testing.
4. What are the metrics used for software maintenance.
5. Define alpha testing.
6. Define software process metrics.
7. Define system testing. 8.
8. What is meant by software reliability?
Part-B
1.Discuss black box testing in a detailed view.
2.Demonstrate art of debugging. Demonstrate metrics for analysis model.
3. a. What is the need of software testing? What are its main objectives and principles?
b. Explain testing strategies for conventional software.
4. Explain the usage of metrics for design model, metrics for source code, metrics for
testing, metrics for maintenance of process and products.
5. Evaluate the art of debugging as a strategic approach to software testing of
conventional software.
6. Explain in detail about metrics for process and products.
7. What is black box testing? What is boundary value analysis? Explain the technique
specifying rules and its usage with the help of an example.
8. What is meant by software quality? Explain the metrics for design model.
UNIT-V
Part-A
1. What is javascript? Write the advantages of javascript.
2. Write the limitation of javascript.
3. Discuss with an example about internal and external java scripts.
4. How do you convert numbers to strings in javascript.
5. What is the function of the === operators
6. Write any 3 properties of the window object
7. Write a javascript program to display the time and date on popup window
8. Write a javascript program to close the window
9. What are the limitations of ajax technology
10. What is the XMLHttpRequest Object in AJAX.
Part-B
1. Discuss about Advantages and limitations of Javascript.
2. Explain internal and external javascript with an example.
3. Explain about javascript variables scope with an example
4. Write a JavaScript program for arithmetic operations.
5. Explain about Function definition, Function calling,
6. Function parameters, the return statement with a suitable example.
7. Define what is DOM and explain javascript HTML Object Hierarchy.
8. Explain Form validation types with a suitable example.
9. What are the properties of the XMLHttpRequest Object?
10. What are the different values of ready State in AJAX?
11. Write a javascript to design a simple calculator to perform the all
12. basic arithmetic operations
13. Explain about Asynchronous and Synchronous request in AJAX with neat diagram
Subjective 20
Assignment Assignment-2 5
Subjective 20
CO2 3 3
CO3 3 3
CO4 3 2
CO5 3 2
Weightag 100.00 66.67 100.00 0.00 0.0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 100.00 75
e 0 0
3- 3.00 2.00 3.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3.00
Scaling 2.25
*to be rated with 1- slightly, 2 – moderately, 3- substantial
Delivery Methodology
Course Delivery Methods / Modes:
1. Class room lectures: 53
2. Presentations:
3. Laboratory sessions:
4. Demos:
5. Assignments:1
6. Case studies:
7. Seminars:
8. Projects:
9. E-Learning Resources:
5
Software Engineering (R22) A.Y.-2023-2024
280
iii)Mentoring report:
Feedback of the students who need specific care is collected from the student’s mentors and
identified the following list of students as slow learners.
SNo Roll No Remarks
iv) Test
prepare 1m questions from the first 50%syllabus of unit 1.
Date: Test 1 for identification of weak/bright students
v) Marks of test 1 :
S TEST-1
Roll No Student Name
No Marks
1
2
3
.
.
.
.
.
28
0
i) Students List:
S No Roll No Student Name
1
2
3
.
.
.
ii) Assignments or open end questions for life long learning or introducing advanced topics
that maps to PEOs
iii) Impact Analysis of Bright students:
Students performance is Improved in Semester end examinations.
Improvement is observed in programming skills.
Improvement in inter-institute event participation.
Positive attitude and Confidence levels are improved to take participation in
presenting seminars, in doing quality projects, in participating inter institute events, in
facing the competitive exams (GATE/GRE/TOFEL)
To the below table Add the names of the students who secured O grade in this subject (from T
Sheet)