GUJARAT TECHNOLOGICAL UNIVERSITY (GTU)

Competency-focused Outcome-based Green Curriculum-2021 (COGC-2021) Semester-V

Course Title: Software Engineering

Course Code: 4353202

Diploma Programme in which this course is offered	Semester in which offered
Information & Communication Technology	Fifth

1. RATIONALE

Software engineering offers a structured framework for creating applications and software. Through this study, students gain the ability to develop and design software to specific needs. It encompasses analyzing and designing systems through various steps and teaches systematic project preparation. This course teaches you how to break down and plan out systems step by step. You learn how to organize projects in a smart way. By studying different parts of software engineering, you understand what it takes to design and make projects work smoothly.

2. COMPETENCY

The course content should be taught and implemented with the aim to develop various types of related skills leading to the achievement of the following competency:

Identify and analyze problems in the field of Software development.

3. COURSE OUTCOMES (COs)

The practical experiences and relevant soft skills associated with this course are to be taught and implemented, so that the student demonstrates the following industry-oriented COs associated with the above-mentioned competency:

a) Describe Generic framework activity and Umbrella activity.
b) Differentiate various software development process models.
c) Prepare SRS as well as draw DFD and object-oriented UML diagrams.
d) Create software development plan using project scheduling.
e) Prepare test-cases to test software functionalities.

4. TEACHING AND EXAMINATION SCHEME

Teaching Scheme (Hours)			Total Credits	Examination Scheme (Marks)				Total
L	T	P	(L+T/2+P/2)	Theory CA	Theory ESE	Practical CA	Practical ESE	Total Marks
3	0	2	4	30	70	25	25	150

Out of 30 marks under the theory CA, 10 marks are for assessment of the micro-project to facilitate integration of COs and the remaining 20 marks is the average of 2 tests to be taken during the semester for the assessing the attainment of the cognitive domain UOs required for the attainment of the COs.

Legends: CI-Classroom Instructions; T-Tutorial/Teacher Guided Theory Practice; P-Practical; C-Credit; CA-Continuous Assessment; ESE-End Semester Examination.

5. SUGGESTED PRACTICAL EXERCISES

The following practical outcomes (PrOs) are the sub-components of the COs. Some of the PrOs marked '*' are compulsory, as they are crucial for that particular CO. These PrOs need to be attained at least at the 'Precision Level' of Dave's Taxonomy related to 'Psychomotor Domain'.

Sr.No	Practical Outcomes (PrOs)	Unit No.	Approx. Hrs. Req
1	Discuss generic framework activity and Umbrella activity	I	02
2	Define the project's title and scope by outlining the problem statement	II	01
3	Select relevant process model to define activities and related tasks set for assigned project	II	01
4	Gather application specific requirements for assigned project - Requirement gathering	III	02
5	Prepare software requirement specification (SRS) for the above selected project	III	02
6	Develop data designs using data flow diagram (DFDs) and E-R (entity-relationship) diagram.	III	04
7	Prepare use-cases and draw use case diagram	III	02
8	Develop a class diagram for selected project	III	02
9	Develop Sequence diagram for selected project	III	02
10	Develop the activity diagram to represent flow from one activity to another for software development.	III	02
11	Evaluate size of the project using Function point metric for the assigned project.	IV	02
12	Estimate cost of the project using COCOMO (Constructive Cost Model) / COCOMO II approach for the assigned project.	IV	02
13	Use flow chart and Gantt charts to track progress of the assigned project. (Use Sprint burn down chart if agile model is selected).	IV	02
14	Prepare various test case for selected project.	V	02
	Total		28

Note

i. Faculty should ensure that students select different problem statement in a group for practical 2 to 14. Size of group should not be more than 3 students.
ii. More Practical Exercises can be designed and offered by the respective course teacher to develop the industry relevant skills/outcomes to match the COs. The above table is only a suggestive list .
iii. The following are some sample 'Process' and 'Product' related skills (more may be added/deleted depending on the course) that occur in the above listed Practical Exercises of this course required which are embedded in the COs and ultimately the competency.

S. No.	Sample Performance Indicators for the PrOs	Weightage in %
1	Problem selection and its feasibility study	30
2	Logical thinking to decompose problem into modules	20
3	Ability to estimate size and cost of the software	30
4	Presentation and Documentation Skills	10
5	Submission of reports within time	10
Total		100

6. MAJOR EQUIPMENT/ INSTRUMENTS AND SOFTWARE REQUIRED

These major equipment/instruments and Software required to develop PrOs are given below with broad specifications to facilitate procurement of them by the administrators/management of the institutes. This will ensure conduction of practical in all institutions across the state in proper way so that the desired skills are developed in students.

S. No.	Equipment Name with Broad Specifications	PrO. No.
1	Computer with latest configuration of windows or UNIX OS	All
2	Software tool: Any UML tool	All

7. AFFECTIVE DOMAIN OUTCOMES

a) Work as a leader/a team member.
b) Follow ethical practices.

8. UNDERPINNING THEORY

The major Underpinning Theory is formulated as given below and only higher level UOs of Revised Bloom's taxonomy are mentioned for development of the COs and competency in the students by the teachers. (Higher level UOs automatically includes lower level UOs in them). If required, more such higher level UOs could be included by the course teacher to focus on attainment of COs and competency.

Unit	Unit Outcomes (UOs)	Topics and Sub-topics
Unit-1: Introduction to Software Engineering	1a. Define Software Engineering 1b. Differentiate Programs and Software Products 1c. Describe Generic Framework Activity	1.1 Software, Software Application Domain 1.2 Software Engineering - A layered Approach 1.3 Programs vs. Software Products 1.4 Software process and software engineering methods 1.5 Generic Framework Activity & Umbrella activity
Unit-2: Software Development Life Cycle	2a. Select the relevant software process model for the given problem statement with justification 2b. Suggest the relevant activities in Agile Development Process in the given situation with justification	2.1 Introduction to software development life cycle (SDLC) 2.2 Software Development Models i. Waterfall Model ii. Incremental Process Model iii. Prototype Model iv. Spiral Model v. RAD Model vi. Agile Development Model 2.3 Agile Development Model i. Agility Principles ii. Types of Agile Models (Extreme Programming (XP), Scrum)
Unit-3: Software Requirement Analysis and Design	3a. Identify Software requirements for the given problem 3b. Prepare SRS from the requirement analysis 3c. Represent the specified problem in the given design notation - DFD	3.1 Requirement Gathering and Analysis 3.2 Software Requirement Specification (SRS) i. Functional Requirement ii. Non-Functional Requirement 3.3 Software Design i. Characteristics of good software design ii. Analysis v/s design 3.4 Classification of cohesion 3.5 Classification of coupling 3.6 Data Flow Diagram (DFD) i. Context Diagram ii. Level 1 DFD 3.7 Object Modeling with UML i. Use case Diagram ii. Class Diagram iii. Sequence Diagram iv. Activity Diagram
Unit-4: Software Project Management	4a. Estimate the size of the software product using the given method 4b. Evaluate the size of the given software using COCOMO model 4c. Prepare the Gantt chart/Sprint burn down chart to track progress of the given project	4.1 Responsibility of software project Manager 4.2 Metrics for Size Estimation i. Line of Code ii. Function Points 4.3 Project Estimation Technique i. Empirical Estimation Technique ii. Heuristic Technique iii. Analytical Estimation Technique 4.4 Project Scheduling i. Gantt Chart ii. Sprint burn down chart for agile model 4.5 Risk Management i. Risk Identification ii. Risk Assessment iii. Risk Control
Unit-5: Software Coding and Testing	5a. Describe different code review techniques 5b. Prepare test cases for the given module.	5.1 Code review i. Code Work through ii. Code Inspection 5.2Software Documentation i. Internal Documentation ii. External Documentation 5.3 Unit Testing 5.4 Black box Testing 5.5 White box testing 5.6 Test case templates

Note: The UOs need to be formulated at the 'Application Level' and above of Revised Bloom's Taxonomy to accelerate the attainment of the COs and the competency.

9. SUGGESTED SPECIFICATION TABLE FOR QUESTION PAPER DESIGN

Unit No.	Unit Title	Teaching Hours	R Level	U Level	A Level	Total Marks
I	Introduction to Software Engineering	04	04	04	00	08
II	Software Development Life Cycle	06	02	04	04	10
III	Software Requirement Analysis and Design	14	04	08	08	20
IV	Software Project Management	10	06	08	04	18
V	Software Coding and Testing	08	04	06	04	14
Total		42	20	30	20	70

Legends: R=Remember, U=Understand, A=Apply and above (Revised Bloom's taxonomy)

Note: This specification table provides general guidelines to assist students for their learning and to teachers to teach and question paper designers/setters to formulate test items/questions to assess the attainment of the UOs. The actual distribution of marks at different taxonomy levels (of R, U and A) in the question paper may vary from above table.

10. SUGGESTED STUDENT ACTIVITIES

Other than the classroom and laboratory learning, following are the suggested student-related co-curricular activities which can be undertaken to accelerate the attainment of the various outcomes in this course: Students should conduct following activities in group and prepare small reports (of 1 to 5 pages for each activity). For micro project report should be as per suggested format, for other activities students and teachers together can decide the format of the report. Students should also collect/record physical evidences such as photographs/videos of the activities for their (student's) portfolio which will be useful for their placement interviews:

a) Undertake micro-projects in teams.
b) Prepare charts for various models, SDLC life cycles, UML notations etc.
c) Prepare SRS documents based on case study.
d) Discuss various case studies available on internet.
e) An hour of problem solving for various case study topics may be organized and students are encouraged to participate
f) Students are encouraged to register themselves in various MOOCs such as: Swayam, edx, Coursera, Udemy etc to further enhance their learning.
g) Encourage students to interact with the industry person to discuss and gather information of current trends, models, documentation, testing methods and different tools used in industry.

11. SUGGESTED SPECIAL INSTRUCTIONAL STRATEGIES

These are sample strategies, which the teacher can use to accelerate the attainment of the various outcomes in this course:

a) Massive open online courses ( MOOCs ) may be used to teach various topics/sub topics.
b) Guide student(s) in undertaking micro-projects.
c) Managing Learning Environment
d) Diagnosing Essential Missed Learning concepts that will help for students.
e) Guide Students to do Personalized learning so that students can understand the course material at his or her pace.
f) Encourage students to do Group learning by sharing so that teaching can easily be enhanced.
g) 'CI' in section No. 4 means different types of teaching methods that are to be employed by teachers to develop the outcomes.
h) About 20% of the topics/sub-topics which are relatively simpler or descriptive in nature is to be given to the students for self-learning , but to be assessed using different assessment methods.
i) With respect to section No.10 , teachers need to ensure to create opportunities and provisions for co-curricular activities .
j) Guide students on how to address issues on environment and sustainability using the knowledge of this course

12. SUGGESTED MICRO-PROJECTS

Only one micro-project is planned to be undertaken by a student that needs to be assigned to him/her in the beginning of the semester. In the first four semesters, the micro-project are group-based (group of 3 to 5). However, in the fifth and sixth semesters , the number of students in the group should not exceed three.

The micro-project could be industry application based, internet-based, workshop-based, laboratory-based or field-based. Each micro-project should encompass two or more COs which are in fact, an integration of PrOs, UOs and ADOs. Each student will have to maintain dated work diary consisting of individual contribution in the project work and give a seminar presentation of it before submission. The total work load on each student due to the microproject should be about 16 (sixteen) student engagement hours (i.e., about one hour per week) during the course. The students ought to submit micro-project by the end of the semester (so that they develop the industry-oriented COs).

A suggestive list of micro-projects is given here. This should relate highly with competency of the course and the COs. Similar micro-projects could be added by the concerned course teacher:

a) Case study on attendance management system
b) Case study on vehicle rental system
c) Case study on hospital appointment booking
d) Case study on gym management system
e) Case study on Tours and Travel Management
f) Case study on hostel management system
g) Case study on student management system
h) Case study on library management system
i) Case study on hospital management system
j) Case study on banking system
k) Case study on college management system
l) Case study on movie ticket booking system
m) Case study on online food ordering application
n) Case study on online shopping
o) Case study on hotel management system
p) Case study on bus ticket reservation system
q) Case study on railway ticket reservation system
r) Case study on flight ticket reservation system

13. SUGGESTED LEARNING RESOURCES

Sr. No.	Title of Book	Author	Publication with place, year and ISBN
1	Software Engineering: A Practitioner's Approach	Roger S. Pressman	Tata McGraw Hill, 2010, ISBN :978-007-126782-3
2	Fundamentals of Software Engineering	Rajib Mall	PHI,2018, ISBN:978-93-88028-02-8
3	Object Oriented Modeling and design with UML	Michael R Blaha and James R Rambaugh	Pearson Prentice Hall, 2009 ISBN:978-81-317-1106-4

14. SUGGESTED LEARNING WEBSITES

15. PO-COMPETENCY-CO MAPPING

Competency & Course Outcomes	PO 1	PO 2	PO 3	PO 4	PO 5	PO 6	PO 7
	Basic & Discipline Specific Knowledge	Problem Analysis	Design/Development of Solutions	Engineering Tools, Experimentation & Testing	Engineering Practices for Society, Sustainability & Environment	Project Management	Life-long Learning
Competency: Identify and analyze problems in the field of Software development	3	3	3	3	3	3	3
CO a) Describe Generic framework activity and Umbrella activity	2	2	-	-	-	-	2
CO b) Differentiate various software development process models	2	-	-	-	-	-	2
CO c) Prepare SRS as well as draw DFD and object-oriented UML diagrams	2	3	2	2	2	2	2
CO d) Create software development plan using project scheduling	2	1	2	2	-	3	2
CO e) Prepare test-cases to test software functionalities	2	1	1	3	-	-	2

Legend: '3' for high, '2' for medium, '1' for low or '-' for the relevant correlation of each competency, CO, with PO/PSO

16. COURSE CURRICULUM DEVELOPMENT COMMITTEE

GTU Resource Persons

S. No.	Name and Designation	Institute	Email
1	Smt. Manisha P. Mehta, HOD	Government Polytechnic, Himatnagar	manishamehtain@gmail.com
2	Smt. Avani S. Galathiya, Lecturer	R C Technical Institute, Ahmedabad	asgalathiya@gmail.com