Scribd
Upload
7 views

3. 0 Group Activity-ISE2-Q

The document outlines a group activity for evaluating students' understanding of software design principles through the design of a modular software system. Students will work in groups to create a software system based on a given scenario, focusing on design principles, modular design, cohesion, coupling, and architectural design. Deliverables include a design document and a presentation, with evaluation based on specific rubrics for each aspect of the design process.

Uploaded by

crce.10398.ce
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
7 views

3. 0 Group Activity-ISE2-Q

The document outlines a group activity for evaluating students' understanding of software design principles through the design of a modular software system. Students will work in groups to create a software system based on a given scenario, focusing on design principles, modular design, cohesion, coupling, and architectural design. Deliverables include a design document and a presentation, with evaluation based on specific rubrics for each aspect of the design process.

Uploaded by

crce.10398.ce
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

ISE-2

Group Activity for Evaluating Students on Software Design

Activity Title: Design a Modular Software System

Objective:

To evaluate students' understanding and application of software design principles, effective


modular design, cohesion and coupling, and architectural design.

This activity will help students apply theoretical knowledge to practical scenarios, demonstrating
their ability to design and document a software system while adhering to design principles and
practices.

Instructions:

1. Form Groups:
o Divide the students into groups of 3 members each.
2. Scenario:
o Each group will design a software system for a given scenario (e.g., a library
management system, an online shopping platform, or a hotel reservation system).
3. Task:
o Design Principles & Concepts:
▪ Define and document the overall design principles your team will use.
▪ Justify your design choices based on principles
o Effective Modular Design:
▪ Create a modular design for the system, breaking it down into distinct
modules or components.
▪ Describe each module’s functionality, interfaces, and responsibilities.
o Cohesion and Coupling:
▪ Ensure high cohesion within each module. Explain how each module is
responsible for a single aspect of the system.
▪ Describe the coupling between modules, aiming for loose coupling. Justify
your decisions to minimize dependencies.
o Architectural Design:
▪ Develop a high-level architectural design of the system, including
diagrams such as component diagrams, class diagrams, and system
architecture diagrams.
▪ Explain the architectural patterns used (e.g., MVC, layered architecture)
and how they support the design goals.
4. Deliverables:
o Design Document:
▪ A written document detailing the design principles, modular design,
cohesion and coupling analysis, and architectural design.
o Presentation:
▪ Prepare a 15-minute presentation summarizing your design. Include visual
aids like diagrams and charts.
5. Presentation and Evaluation:
o Each group will present their design to the class.
o After each presentation, there will be a Q&A session where other students and
instructors can ask questions about the design choices.

Rubrics for Evaluation:

1. Design Principles & Concepts (30%): 6 marks


o Understanding of Principles: Demonstrates a clear understanding of design
principles.
o Justification: Provides well-reasoned justifications for design choices.
o Application: Effectively applies design principles to the system.
2. Effective Modular Design (30%): 6 marks
o Modularity: Clearly defines and structures modules with well-defined
responsibilities.
o Documentation: Provides comprehensive documentation of module
functionalities and interfaces.
3. Cohesion and Coupling (20%): 4 marks
o Cohesion: Modules show high cohesion with well-defined responsibilities.
o Coupling: Achieves low coupling with minimal dependencies between modules.
o Justification: Justifies choices for cohesion and coupling.
4. Architectural Design (20%): 4 marks
o Diagram Quality: Provides clear and accurate architectural diagrams.
o Pattern Application: Effectively uses architectural patterns to support design
goals.
o Explanation: Clearly explains the architectural design and its benefits.

You might also like