COURSE PLAN

Department of Information Technology

2023 - 2024 (ODD SEMESTER)
Year : III IT Course Code : VIT321
Faculty Name : P.Mahalakshmi Course Name : Software Architecture and UML
Design
Course Code : 21ITC312 Regulation : 2021
( As Per NBA)

Objectives:
This course is designed to understand software architectural requirements. Be exposed to architectural
styles and views. Be familiar with architectures for emerging technologies. To design with static
UML diagrams. To design with the UML dynamic and implementation diagrams.

Text Books:
T1 Hong Zhu, Software Design Methodology from Principles to Architectural Styles, Elsevier,
2005.
T2 Craig Larman, Applying UML and Patterns: An Introduction to Object Oriented Analysis and
Design and Iterative Development, Third Edition, Pearson Education, 2012.

References:
R1 David Budgen, Software Design, Second Edition, Pearson Education, 2004.
R2 Mary Shaw David Garlan, Software Architectural Perspectives on an Emerging Discipline,
EEE, PHI 1996.
R3 Mike O’Docherty, Object-Oriented Analysis & Design: Understanding System Development
with UML 2.0, John Wiley & Sons, 2005.

Web Resources:
WR1 https://www.geeksforgeeks.org/software-engineering-user-interface-design [User Interface
Design]
WR2 https://www.educative.io/answers/what-is-a-unified-process-model [Unified Process Model]
WR3 https://www.redhat.com/architect/dynamic-UML-diagramming#: [Dynamic Diagram]
WR4 https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-uml-
collaboration-diagram/ [Collaboration Diagram]

F.4/ Rev.2 Page 1 of 6

 Theory Component (45 Hrs)

Reference Book

Page Numbers

Teaching Aid

No. of periods
Cumulative
Number
Teaching Outline
Sl. No.

Periods
Topic name

No. of
Pre-assessment and Introduction about the
1. 1 1
Introduction about the subject Architecture
UNIT I INTRODUCTION TO SOFTWARE ARCHITECTURE (9)
Discussion about the Notion
2. Notion of Architecture T1 74 - 83 PPT 2 3
of Architecture
Notion of Software Explanation about the Notion
3. T1 84 - 93 PPT 2 5
Architecture of Software Architecture
Architectural Styles: Pipes and Demonstrate the architectural
4. T1 141 - 143 PPT 1 6
Filters Styles: Pipes and Filters
Self- Explanation on Layered
5. Layered Systems T1 158 - 159 1 7
Study Systems.
Self-
6. Repositories T1 162 - 163 1 8 Discussion on Repositories
Study
Description of Software Self- Lecture on Agent structure
7. T1 111 - 116 2 10
Architecture - Visual Notation Study and Review of Unit I
8.
UNIT II DESIGN FUNDAMENTALS (9)
The Basic Concepts of Design Discussion on Characteristics
9. - Characteristics of Design T1 2-6 PPT 1 11 of Design Activities.
Activities.
Lecture on Essential
10. Essential Elements of Design T1 7 - 15 PPT 2 13
Elements of Design
The Factors that affect the Explanation about the
11. T1 16 - 20 PPT 2 15
Design Factors that affect the Design
Design Principles - Basic Self- Discussion about the rules of
12. T1 47 - 54 2 17
Rules of Software Design Study Software Design
Elaborating the Design
Self-
13. Design Processes T1 55 - 65 2 19 Processes and Review of
Study
Unit II
UNIT III DESIGN METHODOLOGIES (9)
Structured Design - Design Elaborating Structured
14. Practices - Stepwise R1 233 - 238 PPT 1 20 design and design practices.
Refinement
Explanation about the
15. Incremental Design R1 241 - 254 PPT 1 21
incremental design
Structured System Analysis Lecture on structured system
16. R1 257 - 286 PPT 2 23
and Design analysis and design.
Jackson Structured Self- Discussion on Jackson
17. R1 289 - 312 1 24
Programming Study Structured Programming
Self- Explanation on Jackson
18. Jackson System Development R1 315 - 338 1 25
Study System Development
Self- Demonstrating the designing
19. Designing with Objects R1 341 - 398 2 27
Study with objects.
Lecture on User interface
Self-
20. User Interface Design WR1 1 28 design and Review of Unit
Study
III

F.4/ Rev.2 Page 2 of 6

 UNIT IV USE CASE AND STATIC DIAGRAMS (9)
Lecture on Unified Process
21. Unified Process Model WR2 PPT 1 29
Model
22. Inception T2 96-103 PPT 1 30 Demonstrating the inception.
Explanation about the use
23. Use Case Modelling T2 115-134 PPT 1 31
case modelling.
Relating Use Cases - Include, Self- Demonstrate the Relating use
24. T2 670-682 1 32
Extend and Generalization Study cases
Self-
25. Class Diagram T2 378-408 2 34 Lecture on class diagram
Study
Self- Discussion about the
26. Elaboration T2 214-216 1 35
Study elaboration
Domain Model - Finding
Conceptual Classes and Self- Lecture on domain model
27. T2 218-267 2 37
Description Classes - Study and Review of Unit IV
Associations – Attributes.
UNIT V DYNAMIC AND IMPLEMENTATION DIAGRAMS (9)
Discussion on dynamic
28. Dynamic Diagrams WR3 PPT 1 38
diagrams
Lecture on UML Interaction
29. UML Interaction Diagrams T2 346-377 PPT 2 40
Diagrams
Explanation about the
30. System Sequence Diagram T2 272-283 PPT 1 41
System Sequence Diagram
Lecture on Collaboration
31. Collaboration Diagram WR4 PPT 1 42
Diagram
State Machine Diagram and Self- Discussion on State Machine
32. T2 657-668 1 43
Modelling Study Diagram and Modelling
Self- Lecture on Activity Diagram
33. Activity Diagram T2 645-655 1 44
Study
Self- Explanation on UML
34. UML Package Diagram T2 320-333 1 45
Study package diagram
Discussion on Component
Component and Deployment Self-
35. T2 828-832 1 46 and Deployment Diagrams
Diagrams. Study
and Review of Unit V
Overall Review 1 47

Number of hours Allotted : 45 + 2 hours (Introduction – 1h and Overall Review – 1h)

Number of hours Needed : 47
Portions for Cycle Test:

Cycle Test Syllabus

I Unit I & Unit II

II Unit III & 50% of Unit IV

III 50% of Unit IV & Unit V

F.4/ Rev.2 Page 3 of 6

 Assignment Topics:
S.N K CO Tentative Date of
Topic
o. Level Mapped Submission
21ITC312.
1 1, 1st week of
Online MCQ from Unit I and II K2
21ITC312. September, 2023
2
Object based design and Object Oriented 21ITC312. 3rd week of September,
2 K2
Design 3 2023
21ITC312.
4, 3rd week of October,
3 Case Study Presentation for Unit IV and V K3
21ITC312. 2023
5

Rubrics for Assignment I Assessment:

Assignment Type Category Mark Allocation Maximum Marks
Number of Correct Each Question 1 Mark 20
Quiz 20
Answer x 1 = 20

Rubrics for Assignment II Assessment:

Mark
s
Category – Theory Oriented Assignment
allott
ed
Submissio
Submission Submission Submission
Submission Submission n with 1
with 2 day's with 3 day's with 4 day’s 10
on time on date-10 days
delay-6 delay-4 delay-2
delay-8
Entire Few
Entire topic All No
Content topic with highlighted
with highlighted highlighted
Preparation few key points
highlighted key points key points 10
and highlighte with few
key points- with few with few
Presentation d key description-
10 description - 6 description-2
points-8 4
Total Marks 20

Rubrics for Assignment III Assessment:

Rambling,
Presenting: Tightly focused; Less focused;
Mostly focused; Unfocussed;
Content is very Content is less
Clarity of Content is mostly Content is unclear;
clear; Good clear; Keeps very
Presentation clear; Keeps almost Runs over time or
timing – 10 almost to time –
[10 Marks] to time – 7.5 Marks too brief – 2.5
Marks 5 Marks
Marks

Engage Audience not

audience: Audience fully Audience mostly Audience slightly
engaged; Inability
Keeps engaged; Invokes engaged; Invoke engaged; Invoke
to invoke
audience useful discussion some discussion – 3 some discussion
discussion - 1
Attention – 5 Marks Marks – 2 Marks
Marks
[5 Mark]
Clarifying Convincing Adequate responses Few responses to Inability to answer

F.4/ Rev.2 Page 4 of 6

 responses to
Doubts to questions – 3 questions – 2 questions – 1
questions – 5
Marks Marks Marks
[5 Marks] Marks

*Assignment marks should be converted for 40% of Internal marks for R2021

COURSE OUTCOMES (COs):

On successful completion of this course, the students will be able to:

CO. No. CO Statements Knowledge Level
Summarize the software architecture that can be used for an
21ITC312.1 application. K2 – Understand
21ITC312.2 Illustrate the design fundamentals of the software. K2 – Understand
21ITC312.3 Demonstrate the design methodologies to create good software. K2 – Understand
Construct appropriate use case and class diagrams for real world
21ITC312.4 scenarios. K3 – Apply
Apply the dynamic and implementation diagrams for the given
21ITC312.5 software system K3 – Apply

DEPARTMENT OF INFORMATION TECHNOLOGY

PSO1: Demonstrate technical and interpersonal skills to design and develop IT enabled solutions to
meet the real time industrial and societal needs

PSO2: Exhibit an ability to adapt to the evolutionary changes in computing

CO - PO MAPPING:

POs PSOs
CO. No.
1 2 3 4 5 6 7 8 9 10 11 12 1 2
21ITC302.1 M L L - - - - - - - - L M L
21ITC302.2 M L L - - - - - - - - L M L
21ITC302.3 M L L - - - - - - - - L M L
21ITC302.4 M M M - - - - - - - - L M L
21ITC302.5 M M M - - - - - - - - L M L

H (for high), M (for moderate), L (for low)

Faculty In-charge Subject Expert Chairperson

Name: Mrs.P.Mahalakshmi Name: Mrs.P.Mahalakshmi Name: Ms.P.Kaviya

F.4/ Rev.2 Page 5 of 6

 Head of the Department

F.4/ Rev.2 Page 6 of 6