0% found this document useful (0 votes)
5 views6 pages

Event-Driven Course Project

The Mini-DARMAS project is a capstone course assignment to develop a WinForms-based application for managing meeting documentation workflows in government and corporate settings. It involves four user roles: Admin, Operator, Transcriber, and Editor/Approver, each with specific functionalities for managing meetings, agendas, recordings, and final document approval. The project emphasizes event-driven programming, GUI development, object-oriented principles, and database integration, with a structured approach to deliverables across five phases culminating in a complete application and technical documentation.
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
0% found this document useful (0 votes)
5 views6 pages

Event-Driven Course Project

The Mini-DARMAS project is a capstone course assignment to develop a WinForms-based application for managing meeting documentation workflows in government and corporate settings. It involves four user roles: Admin, Operator, Transcriber, and Editor/Approver, each with specific functionalities for managing meetings, agendas, recordings, and final document approval. The project emphasizes event-driven programming, GUI development, object-oriented principles, and database integration, with a structured approach to deliverables across five phases culminating in a complete application and technical documentation.
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

Event Driven Course Project (Max group members Six)

Mini-DARMAS: Digital Meeting Recording and Transcript Management


System

Course Capstone Project

1. Project Overview
Government institutions, parliaments, and corporate boards often conduct meetings that require
formal documentation, including agenda preparation, audio recording, transcription, editing, and
final approval. Your task is to design and implement a WinForms-based desktop application
that manages this workflow digitally. This system will be a simplified version of the real-world
DARMAS (Digital Audio Recording and Meeting Archiving System) used in parliamentary
settings.

The capstone project brings together all the key concepts learned throughout the course-event-
driven programming, delegates and handlers, GUI development, OOP principles, dynamic
controls, file handling, and database integration-into one comprehensive system.

2. System Concept
You will develop a desktop application called Mini-DARMAS, which supports a simplified end-
to-end meeting documentation workflow involving four primary user roles:

1. Admin - manages user accounts and roles


2. Operator - creates meetings, adds agendas, attaches recordings, assigns transcribers
3. Transcriber - transcribes assigned audio into text and submits to editor
4. Editor/Approver - reviews, corrects, approves, and produces the final meeting
document

The final system must allow a meeting to progress from creation → recording → transcription →
editing → approval → generation of final meeting document.

3. Learning Objectives
This course project is designed to assess and reinforce the following course outcomes:

Event-Driven Programming

 Use events, event handlers, delegates, and UI triggers


 Implement multi-form interactions and control events (button, selection, form load)

GUI Development
 Build a multi-form WinForms application
 Use advanced controls: ListBox, ComboBox, DataGridView, TabControl, MenuStrip,
Dialogs
 Handle keyboard/mouse events where appropriate

Object-Oriented Programming

 Implement domain classes (Meeting, Agenda, Recording, User, Transcription)


 Practice encapsulation, inheritance, and data model design
 Use reusable methods and classes

Data & File Handling

 Apply [Link] for CRUD operations


 Save/load transcription files
 Export final meeting documents

Software Design Skills

 Design database schema


 Use multi-layer architecture (UI layer + Logic layer + Data layer)
 Prepare documentation and present system design

4. System Requirements
The system must support four key user modules.

4.1 Admin Module

Features:

 Login authentication
 Manage user accounts
 Create new users with:
o Full name
o Username
o Password
o Role (Admin, Operator, Transcriber, Editor, Approver)
 Activate/deactivate users
 List all users in a DataGridView with:
o Search
o Sorting
o Filtering

4.2 Operator Module


Key responsibilities:

A. Meeting Management

 Create new meeting:


o Meeting No
o Date
o Location
o Chairperson
 List, edit, and delete meetings

B. Agenda Management

 For each meeting:


o Add agendas (Agenda Title, Office, Supporting Document filename)
o Edit and delete agendas
o Display agenda list

C. Recording Management

 Attach audio file(s) to a specific agenda


 Store audio file path
 Provide list of recordings per agenda

D. Assignment to Transcriber

 Assign recordings to a transcriber using a ComboBox


 Change assignment status to:
o Assigned
o In Progress
o Completed
 Store assignment info in database

4.3 Transcriber Module

Features:

 List all recordings assigned to current transcriber


 Display:
o Meeting No
o Agenda Title
o Audio File Name
o Assignment status

Transcription Form
 Large TextBox (multi-line) for text transcription
 Playback option (bonus)
 Buttons:
o Save Draft
o Submit to Editor
 Status should update in database

4.4 Editor / Approver Module

A. Editor

 View submissions awaiting review


 Edit transcription text in editable TextBox
 Provide comments
 Approve or return for correction

Statuses:

 Submitted
 Under Review
 Approved
 Returned

B. Approver (Secretary/Chairperson)

 View fully approved agenda transcriptions


 Combine all approved agendas into final meeting text
 Display combined text in read-only RichTextBox
 Optionally export final document to:
o .txt
o .rtf
 Mark entire meeting as Final Approved

5. Technical Requirements
5.1 Technology Stack

 C# WinForms
 .NET Framework 4.8 or .NET 6
 SQL Server Express (localdb acceptable)
 [Link] for database operations
 [Link] for file handling

5.2 Database Schema (Minimum Tables)

1. Users
2. Meetings
3. Agendas
4. Recordings
5. Assignments
6. Transcriptions

Students must design and submit a .sql script that creates all tables and inserts sample data.

6. Project Phases & Deliverables


Phase 1: Requirements & Design (Week 1)

Deliverables:

 System workflow diagram


 UML Use Case diagram
 Database ERD
 UI mockups of all forms

Phase 2: Admin + Login (Week 2)

Deliverables:

 Authentication working
 User management screens

Phase 3: Operator Module (Week 3)

Deliverables:

 Meeting & agenda management


 Recording attachment
 Assignment to transcriber

Phase 4: Transcriber + Editor Modules (Week 4)

Deliverables:

 Transcription UI
 Editorial review UI
 Status flow implemented

Phase 5: Approver + Final Integration (Week 5)

Deliverables:
 Final meeting document generator
 Export feature
 Complete testing

Final Deliverables (End of Project)

1. Complete WinForms Application


2. SQL Database Script (.sql)
3. Technical Report
o Introduction
o Class diagrams
o ERD
o Screen mockups
o Code design decisions
4. User Manual (short version)
5. Presentation & Demonstration

7. Assessment Rubric
Component Weight
Functional Implementation 30%
GUI Design and Usability 15%
OOP & Architecture Quality 15%
Database Design & Integration 15%
Documentation 10%
Presentation/Demo 15%

8. Bonus Features
 Audio playback integration
 Logging system (activity log)
 Multi-language UI (Amharic/English)
 Administrator dashboard with statistics
 Digital signature placeholder
 Export final document as PDF

9. Academic Integrity
All code must be written by the group.
Copy-paste or using AI-generated full projects without understanding will be penalized.
Students must explain their code during the evaluation.

You might also like