Professional Documents
Culture Documents
Handout - SE IS F341
Handout - SE IS F341
Goa Campus
COURSE HANDOUT
Credit 4
E-mail rizwanp@goa.bits-pilani.ac.in
Chamber D-159
Course Description
Software development outside of the classroom is a very complex process, mostly because
real-world software is much larger and more complex. The purpose of this course is to present
software engineering as a body of knowledge. The course is designed to present software
engineering concepts, various process models (such as Evolutionary, Agile) and principles in
parallel with the software development life cycle.
The basics of SE start with Software Development Life Cycle (SDLC) which has five major
phases: requirements gathering, requirements analysis, design, coding/ implementation, and
testing. There is will learning on software modelling using design languages and tools such as
Unified Modelling Language (UML), Simulink, UPPAAL, Ptolemy-II. UML is a standardized
general-purpose modelling language used to create visual models of object-oriented software.
You will be studying design process which includes Architectural Styles and Design Patterns.
You will also learn about project management for the purpose of delivering high-quality software
that satisfies customer needs and is within budget.
By the time the course is complete, you will learn software engineering concepts, principles, and
essential processes of the SDLC; Agile Process; you will demonstrate this knowledge by
creating UML artifacts for requirements gathering, analysis as well as design phases using an
object-oriented methodology.
Course Objectives
No
CO1 Practical Life aspect of the course- Introduction to Software Engineering; Process Models; An Agile View of
Process; Software Engineering Practices;
CO2 Understanding and Building business model with Software Engineering Practices and understanding good
practices to be followed for developing high quality software product
Understanding and usage of various Design Aspects - Creating an Architectural Design; Component-Level
Design; User Interface Design;
CO3 Maintaining the Quality of the Software Product - Testing Approaches; OO & Web Application Testing;
At the end of the course, the students would be able to understand and apply Object Oriented Analysis and
Design methods for development of good quality software systems, using the Unified Modeling Language
(UML) and the Unified Process.
Text Book(s)
T1 Roger S. Pressman,, Software Engineering: A Practitioner's Approach, MGHISE, 7th Ed., 2010
T2 Grady Booch et.al., Unified Modeling Language User Guide, Pearson Education, 1999.
Reference Book(s) & other resources
R2 Pankaj Jalote , An Integrated Approach to Software Engineering, Third Edition Springer © 2005
R4 Richard H. Thayer and Mark J. Christensen, Software Engineering, Volume 1: The Development Process, Third
Edition John Wiley & Sons © 2005
R5 Timothy Lethbridge (Author), Robert Laganiere (Author), Object-Oriented Software Engineering: Practical
Software Development using UML and Java McGrawHill 1st Edition
R6 Erich Gamma et. al., Design Patterns : Elements of Reusable Object-Oriented Software, Pearson Education, 2000
Course Topics
Chapter
Sr.No Topics/Activity
References/Remarks
1 Software Characteristics T1 – Ch1
Challenges of Software Engineering
Process, frameworks, methods
and tools
2 Software Engineering Definitions T1 - Ch 2
Challenges of Software Engineering
Process, frameworks, methods
and tools
3 Process Models R1 - Sommerville, I., Software
Engineering, Pearson Education, 9 th
Various Process Models and their Ed., 2010
usage in industry
Iterative Process Development Chapter 3
Unified Processes
4 Prescriptive Process Variants R1- Sommerville, I., Software
Component-based model Engineering, Pearson Education, 9 th
Ed., 2010
Chapter 2,3
5 Software Engineering Practice and T1: Chapter 4,5
Principles
Software Engineering and Feasibility
Study
6 Agile Process Models T1: Chapter 3
How to relate a process models to a e-Book (Books 24X7)
particular type of industry or system Richard H. Thayer and Mark J.
Christensen, Software
Software Engineering Practices Engineering, Volume 1: The
Development Process, Third
Edition John Wiley & Sons ©
2005
Section 1.3 (Recommended Skills and
Knowledge for Software Engineers)
7 ANALYSIS T1: Chapter 6,7
Requirement Gathering Process R1 (Sommerville) Chapter 4,5
Sommerville, I., Software Engineering,
Pearson Education, 9 th Ed., 2010
o Chapter 4,5
e-Book (Books 24X7)
Pankaj Jalote , An
Integrated Approach to
Software Engineering, Third
Edition Springer © 2005
Chapter 4 Section 3 (SRS structure
and contents)
8 Requirement Modelling -1 T1: Chapter 7
(Requirement Analysis and Modelling) R1 (Sommerville) Chapter 4,5
Evaluation Component
No Name Type Duration Weight Day, Date, Session, Time
1 Classroom discussion, Closed Continuous 25% To be announced in class.
Quiz, assignments and Book Activity
Projects
2 Mid-sem Exam Closed 1.5 hour 25% To be announced in class.
Book
3 Comprehensive Exam Open Book 3 hours 50% 14/05/20 (FN)
Evaluation Guidelines:
1. Though attendance does not have any marks BUT all your exam will be based on the topics covered in class.
Hence, it shall be the responsibility of the individual student to be attending the regular lectures, and take all
the prescribed evaluation components such as Assignment/Quiz, mid-sem and Comprehensive Exam
according to the evaluation scheme provided in the handout.
2. For Closed Book tests: No books or reference material of any kind will be permitted.
3. For Open Book exams: Use of books and any printed / written reference material (filed or bound) is permitted.
However, loose sheets of paper will not be allowed. There is no use of Calculator. Laptops/Mobiles of any
kind are not allowed. Exchange of any material is not allowed.
4. Avoid Make-up Exams; try to appear in all regular examination.
5. Please keep in your mind that only genuine Recheck request will be entertain. When a student
applies for the recheck, entire answer sheet will be re-evaluated again; this procedure may increase
or decrease (as well) the marks. Non-genuine request may lead to minus marking sometimes. Be
careful.
6. Chamber consultation hour: After class, Chamber NO: D-159 or take prior appointment via email.