Semester-IV: Introduction To Software Engineering Course Code: 4340702
Semester-IV: Introduction To Software Engineering Course Code: 4340702
1. RATIONALE
The Software engineering provides platform to develop Application or software in a systematic way.
After studying the subject the students will be able to develop and design the software according to
given requirements. It involves various steps in analysis and design of the system. It includes the
knowledge of preparing project systematically. This course helps to know about various aspects of the
software engineering so that the students will be able to understand the responsibilities while
designing and implementing the project.
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
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:
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. PrO. No.
Equipment Name with Broad Specifications
No.
1 Computer with latest configuration of windows or UNIX OS All
2 Software tool : Any UML tool All
The ADOs are best developed through the laboratory/field-based exercises. Moreover, the
level of achievement of the ADOs according to Krathwohl’s ‘Affective Domain Taxonomy’
should gradually increase as planned below:
i. ‘Valuing Level’ in 1st year
ii. ‘Organization Level’ in 2nd year.
iii. ‘Characterization Level’ in 3rd year.
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.
Total 42 22 32 16 70
Legends: R=Remember, U=Understand, A=Apply and above (Revised Bloom’s taxonomy)
Note: This specification table provides general guidelines to assist student for their learning
and to teachers to teach and question paper designers/setters to formulate test
items/questions 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.
g) ‘CI” in section No. 4means 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 micro-
project 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 student management system
b) Case study on library management system
c) Case study on hospital management system
d) Case study on banking system
e) Case study on collage management system
f) Case study on movie ticket booking system
g) Case study on online food ordering application
h) Case study on online shopping
i) Case study on hotel management system
j) Case study on bus ticket reservation system
k) Case study on railway ticket reservation system
l) Case study on flight ticket reservation system
m) Case study on leave management system in large organization
n) Case study on stock management system in mall
o) Case study on attendance management system
p) Case study on vehicle rental system
q) Case study on hospital appointment booking
r) Case study on gym management system
s) Case study on Tours and Travel Management
t) Case study on hostel management system
u) Case study on employee management system
3 Object Oriented Modeling and Michael R Blaha and Pearson Prentice Hall, 2009
design with UML James R Rambaugh ISBN:978-81-317-1106-4
Course Outcomes
CO a) Compare various
2 - - - - - -
software development process
models.
CO b) Prepare software
analysis and design using SRS,
2 3 2 2 - 2 2
DFD and object oriented UML
diagrams.
CO c) Prepare software
development plan using project 2 1 2 2 - 3 2
scheduling.
CO d) Prepare test-cases to test
2 - - - - - -
software functionalities
Legend: ‘3’ for high, ‘2’ for medium, ‘1’ for low or ‘-’ for the relevant correlation of each competency, CO, with PO/ PSO
Name and
S. No. Institute Contact No. Email
Designation
Shri P. P. Kotak S S Gandhi Polytechnic, [email protected]
1 9825469617
Principal Surat om
Government
Smt. M. P. Mehta manishamehtain@gm
2 Polytechnic, 9879578273
HOD, Computer ail.com
Himmatnagar
Smt. Avani S R C Technical Institute,
3 9904126016 [email protected]
Galathiya Ahmedabad
Smt. Soniya S R C Technical Institute, soniyasdadhania@gmail
4 9974006746
Dadhania Ahmedabad .com