CS 349 Software Engineering Syllabus VER 1.0

COURSE SYLLABI
(2019 - 2023)
SCHOOL OF COMPUTER ENGINEERING & 2021-2022

W.E.F. :
TECHNOLOGY
COURSE NAME : Software Engineering
THIRD YEAR BTECH IN COMPUTER COURSE CODE : CS 349
ENGINEERING
COURSE CREDITS : 4
RELEASE DATE : 1/12/2021 REVISION NO. : 0.0
TEACHING SCHEME: EVALUATION SCHEME:
THEORY
PRESENTATION/
LECTURE PRACTICAL PRACTICAL TOTAL
ICE ECE IA DEMONSTRATION
3 2 35 35 30 -- 50 150
PRE-REQUISITE:
1. ET206 : Prototyping
COURSE OBJECTIVES:
1. CS349.CEO.1: To identify the software process model.
2. CS349.CEO.2: To process requirement engineering for product development.
3. CS349.CEO.3: To learn design concepts and modelling for software development.
4. CS349.CEO.4: To comprehend the estimation and management of software metrics.
5. CS349.CEO.5: To Understand test driven environment in software development.
COURSE OUTCOMES:
Students successfully completing the course will be able to
1. CS349.CO.1: Classify process models.

2. CS349.CO.2: Analyze conformance of the requirement related to project development.
Format No. : MITAOE/ACAD/ 002 Rev. No. : 1.0 Rev. Date : 01/06/2018
3. CS349.CO.3: Develop design models using UML diagram
4. CS349.CO.4: Mitigate the risk associated with project development.
5. CS349.CO.5: Evaluate the schedule, cost and staff associated with project.
6. CS349.CO.6: Review quality assurance through test driven development.
THEORY:
Unit I Basics of Software Engineering 8 Hours

App/System/Case study:
Learning Game Design and Software Engineering through a Game Prototyping Experience.
Content:
Generic process model: Process framework, umbrella activities, Process Adaptation, Perspective
Process Models - Waterfall Model, Prototyping, Incremental, and Agile Process Model: XP and Scrum,
introduction to Principles of framework Activities, DevOps concepts and process: continuous development,
continuous integration, continuous testing, continuous deployment, and continuous monitoring.
Self-Study: Component based development process model.

Further Reading: Dynamic System Development Method
Unit II Understanding Requirements and Modelling 8 Hours
Online Marketing Software Platform
Content:
Requirement Engineering: Elicitation, Analysis, Specification and verification; Scenario based requirement
modelling: Creating a Preliminary Use Case, Refining a Preliminary Use Case, Writing a Formal Use
Case, Requirement modeling class based: Identifying Analysis Classes, Specifying Attributes, Defining
Operations, Class-Responsibility-Collaborator Modelling, Associations and Dependencies, Requirement
modelling Behavior, patterns and web/mobile apps: Creating a Behavioural Model, Identifying Events with
the Use Case, State Representations, Discovering Analysis Patterns, Web and Mobile Apps;
Requirements Modelling Input/output, Content and Navigation modelling;
Self-Study: Interaction Model for Web and Mobile Apps

Further Reading: Configuration Models for Web Apps
Unit III Design Concepts 8 Hours

Banking software user interaction and dependencies
Content:
Design Concepts, Design models, Architectural design: Representing the System in Context, Defining
Archetypes, Refining the Architecture into Components, Describing Instantiations of the System,
Architectural Reviews, Static and Dynamic UML Diagrams: Class diagram, object diagram, Use case,
activity, sequence, block diagram, architectural diagrams and deployment diagram.
Self-Study: Pattern based Design
Further Reading: Mobile application design models
Unit IV Process Management and Estimation 8 Hours

Successful Application of Software Reliability By Norman F. Chneidewind
Content:
Software Configuration Management. Software Project Planning: Project Planning objectives. Software
Metrics: Size, Function Point, Staffing, Project Estimation Methods Decomposition Techniques; Empirical
Estimation Models COCOMO Model. Risk Management: Risk Identification, Analysis, mitigation
methods.
Self-Study: Software Quality ISO Standards
Further Reading: ISO/IEC 9126 Software engineering
Unit V Test Driven development 8 Hours

Manual Testing (Online Marketing Software Platform)
Contents:
System Testing - System Integration Techniques-Incremental, Top-Down Bottom, White box Testing,
Black box Testing, Performance Testing, Security Testing, Acceptance testing.
Self-Study: Automated Testing life cycle
Further Reading: Software Reliability
PRACTICAL: Perform following experiments using Open source tools

Note: Following are the reference case studies, can be changed with other appropriate examples with same
level.
Practical
Title Hours
No. 1
Students are required to take a real-life scenario for software development
(ERP, Mobile app, IOT project) and apply a correct Development paradigm for
it with justification.
OR
1 4
Students can take Mini or Minor project/ DBMS project / DSF Project and
explain which software development paradigm was used, what were the
Limitations of that paradigm. Students should propose a revised paradigm to
Overcome the limitations of existing one with justification.
Take your Project statement and make a SRS in IEEE format.
2 IEEE SRS must have preliminary as well as detailed design. 4
3 Take your problem statement and design modelling using UML Diagrams 4
Prepare a suitable cost estimation model, WBS, Gantt chart (using MS
4 4
project tool) and all necessary estimation for your project.
5 Prepare the Risk mitigation plan for the selected project. 4
Design test driven process for project based on associated risk and possible
6 4
threats.
7 Final presentation: Report and PPT 4
TEXT BOOK:
1. Roger Pressman, “Software Engineering: A Practitioner's Approach”, McGraw-Hill Education; 8th
edition ISBN 13: 9789339212087
2. Ian Somerville, “Software Engineering” Pearson Publication; 9th Edition, ISBN-13: 978-0-13-
703515-1
3. Srinivasan Desikan,” Software Testing Principals and practices”, Pearson Publication ISBN-13 978-
8-17-758295-6
REFERENCES:
1. Software Testing And Quality Assurance-Theory and Practice, Kshirasagar Nak Priyadarshi Tripathy,
John Wiley & Sons Inc,2008
2. Software Quality Engineering: Testing, Quality Assurance, and Quantifiable Improvement, Jeff Tian,
John Wiley & Sons, Inc., Hoboken, New Jersey. 2005.
3. Software Quality Assurance - From Theory to Implementation, Daniel Galin, Pearson Education Ltd
UK, 2004
4. Software Quality Assurance, MilindLimaye, TMH ,New Delhi, 2011.
5. The Art of Software Testing, by Glenford J. Myers , Corey Sandler, Tom Badgett, 3rd Edition, Wiley;
3 edition, ISBN-13: 978-1118031964.
6. Selenium Testing Tools Cookbook - Second Edition, UnmeshGundecha , Publisher: Packt
Publishing, ISBN:13 -9781784392512
https://www.geeksforgeeks.org/software-engineering/

CS 349 Software Engineering Syllabus VER 1.0

Uploaded by

Copyright:

Available Formats

CS 349 Software Engineering Syllabus VER 1.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CS 349 Software Engineering Syllabus VER 1.0

Uploaded by

Copyright:

Available Formats

COURSE SYLLABI

SCHOOL OF COMPUTER ENGINEERING & 2021-2022

RELEASE DATE : 1/12/2021 REVISION NO. : 0.0

TEACHING SCHEME: EVALUATION SCHEME:

1. CS349.CO.1: Classify process models.

Unit I Basics of Software Engineering 8 Hours

Self-Study: Component based development process model.

Self-Study: Interaction Model for Web and Mobile Apps

Unit III Design Concepts 8 Hours

Unit IV Process Management and Estimation 8 Hours

Self-Study: Software Quality ISO Standards

Further Reading: ISO/IEC 9126 Software engineering

Unit V Test Driven development 8 Hours

Self-Study: Automated Testing life cycle

Further Reading: Software Reliability

PRACTICAL: Perform following experiments using Open source tools

You might also like