HICET – Department of Computer Science and Engineering
Programme Course Code Name of the Course L T P C
B.E 22CS4203 SOFTWARE DESIGN WITH UML 3 0 0 3
[Link] understand the basic concepts of software engineering, life cycle models and project
management concepts
[Link] understand in detail about the requirement analysis and requirement engineering processes
Course
3. Learn the basics of OO analysis and design skills..
Objective
4. Learn the UML design diagrams.
5. Learn to map design to code.
Instructional
Unit Description
Hours
SOFTWARE PROCESS AND PROJECT MANAGEMENT
Introduction to Software Engineering, Software Process, Perspective and
Specialized Process Models – Software Project Management: Estimation –
I 9
LOC and FP Based Estimation, COCOMO Model – Project Scheduling –
Scheduling, Earned Value Analysis - Risk Management.
REQUIREMENTS ANALYSIS AND SPECIFICATION
Software Requirements: Functional and Non-Functional, User requirements,
System requirements, Software Requirements Document – Requirement
II 9
Engineering Process: Feasibility Studies, Requirements elicitation and analysis,
requirements validation, requirements management-Classical analysis:
Structured system Analysis, Petri Nets- Data Dictionary
UML DIAGRAMS
Introduction to OOAD – Unified Process – UML diagrams – Use Case – Class
III 9
Diagrams– Interaction Diagrams – State Diagrams – Activity Diagrams –
Package, component and Deployment Diagrams
DESIGN PATTERNS
GRASP: Designing objects with responsibilities – Creator – Information expert
IV – Low Coupling – High Cohesion – Controller – Design Patterns – creational – 9
factory method – structural – Bridge – Adapter – behavioral – Strategy –
observer.
CASE STUDY
Case study – the Next Gen POS system, Inception -Use case Modeling –
Relating Use cases – include, extend and generalization – Elaboration – Domain
V 9
Models – Finding conceptual classes and description classes – Associations –
Attributes – Domain model refinement – Finding conceptual class Hierarchies
– Aggregation and Composition.
Total Instructional Hours 45
CO1: Understand and gain knowledge to implement projects using OO concepts.
Course CO2: Understand the functional requirements of UML analysis and design diagrams.
Outcome CO3: Apply the UML diagrams to understand the conceptual classes and class hierarchies
CO4: Apply appropriate design patterns.
CO5: Understand the concepts of use case modeling.
TEXT BOOKS:
T1 Roger S. Pressman, ―Software Engineering – A Practitioner‟s Approach‖, Seventh Edition, Mc Graw-Hill
International Edition, 2010.
HICET – Department of Computer Science and Engineering
T2 Craig Larman, “Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative
Development”, Third Edition, Pearson Education, 2005.
REFERENCE BOOKS:
R1: Ian Sommerville, “Software Engineering”, 9th Edition, Pearson Education Asia, 2011.
R2: Simon Bennett, Steve Mc Robb and Ray Farmer, “Object Oriented Systems Analysis and Design Using
UML”, Fourth Edition, Mc-Graw Hill Education, 2010.
R3: Erich Gamma, and Richard Helm, Ralph Johnson, John Glissades, “Design patterns-Addison-Wesley, 1995.
R4: Stephen [Link], ―Software Engineering‖, Tata McGraw-Hill Publishing Company Limited,2007.
PO
& PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 PO11 PO12 PSO1 PSO2
PSO
CO1 3 3 3 2 2
CO2 3 3 3 3 2 2
CO3 3 3 3 2 2
CO4 3 3 3 2 -
CO5 3 3 3 2 2
AVG 3 3 3 3 3 3 2 2