Problem Based Learning
Software Design and Architecture-(SESD-242)
BSSE-IV
CLO Description Blooms Taxon- PLOs Assessment
omy Level
CLO-2 Apply UML C-3 3 Software Design
knowledge to Document (SDD)
Comprehend the
design challenges
as well as to doc-
ument the design
of software sys-
tems.
Objective:
Problem-based learning (PBL) is a student-centered instructional strategy that emphasizes active in-
volvement in solving real-world design problems. In the context of the Software Design and Archi-
tecture course, where students are introduced to modeling techniques and architectural design pat-
terns, the goals of using PBL are:
Objective 1: To enable students to actively engage in identifying and modeling system requirements
using UML diagrams such as Use Case, Class, Sequence, and Activity diagrams.
Objective 2: To develop students’ analytical and design thinking by involving them in scenarios
where they must select and apply appropriate architectural styles and design patterns.
Objective 3: To help students gain hands-on experience in modeling the software structure and be-
havior of real-world systems, preparing them to effectively contribute to software design tasks in
industry settings.
Group Size:
Groups of 3-4 students will be formed.
Problem Statement:
In the Requirements Engineering course, students worked on different real-world systems and created
their Requirements Specification documents. In this project, they will work on the same projects and
create their UML models and architectural styles and patterns.
Tasks to be Performed:
Each student must choose 5 functional requirements from the SRS and prepare the following.
1. Develop a Domain Model to identify and represent key domain concepts and their relation-
ships in the target software system. This will be created for the whole system.
(10 marks)
2. Design a Class Diagram to represent the static structure of the system. Include major clas-
ses, their attributes, operations, relationships (associations, aggregations, compositions),
and inheritance where applicable. This will be created for the whole system.
(10 marks)
3. Create Use Case Models that capture and clearly document system interactions from the
perspective of different user roles (actors). Ensure each use case includes a brief description
and its scope. This will be created for the individual use cases.
(10 marks)
4. Perform CRC (Class-Responsibility-Collaboration) Modeling for key classes. Define the
responsibilities of each class and identify how they collaborate with others. Present CRC
cards or tables. This will be created for the whole system.
(10 marks)
5. Develop Sequence Diagrams for at least two key use cases, showing object interactions
and message flows over time. Ensure diagrams reflect object lifelines, activation bars, and
clear communication flow. This will be created for the individual use cases.
(10 marks)
6. Model Business or System Workflows using Activity Diagrams, capturing parallelism,
decision branches, and object flows where applicable. Focus on a real-life scenario from
the system. (10 marks)
7. Construct State Machine Diagrams for critical system entities that undergo complex state
transitions (e.g., order lifecycle, user authentication session). Capture events, transitions,
and actions. This will be created for the individual use cases.
(10 marks)
8. Construct the deployment and component diagrams for the whole system.
(10 marks)
9. Identify and Justify Suitable Architectural Patterns/Styles (e.g., Layered, Client-Server,
Microservices, MVC) for the system. Explain the rationale for selection and provide a high-
level architectural view. This will be created for the whole system.
(10 marks)
10. Prepare a Consolidated Software Design Document (SDD) that integrates all the models
developed above. Ensure the document is logically structured, technically sound, and suita-
ble for guiding development. (10 marks)
