0% found this document useful (0 votes)
16 views9 pages

CSharp Project Brief

The document outlines a project for developing a C# desktop application using N-tier architecture, focusing on addressing real-world challenges in community engagement or education. Students must select a relevant problem, design a GUI-based solution, and implement core services while adhering to technical requirements. Assessment criteria include problem definition, UI design, input validation, SQL Server integration, and functionality of the application.

Uploaded by

siwesapepa02
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
16 views9 pages

CSharp Project Brief

The document outlines a project for developing a C# desktop application using N-tier architecture, focusing on addressing real-world challenges in community engagement or education. Students must select a relevant problem, design a GUI-based solution, and implement core services while adhering to technical requirements. Assessment criteria include problem definition, UI design, input validation, SQL Server integration, and functionality of the application.

Uploaded by

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

Development Software Two Project Brief 2025

Development of a C# Desktop Application Using a N-Tier Architecture

Background and Rationale


Information and Communication Technologies (ICTs)—including computers, software applications, and
networking tools—have emerged as essential enablers in addressing societal challenges. Developers are
increasingly contributing to social innovation through the creation of desktop or web-based applications
that improve service delivery, streamline institutional processes, and enhance user engagement.

For the purposes of this project, students will develop a desktop application using C# Windows Forms and
implement a 3-tier (N-tier) architecture, consisting of:
1. Presentation Layer (Windows Forms for the user interface)
2. Application Logic Layer (business rules and logic)
3. Data Layer (SQL Server for data management).

Project Objectives
You are expected to select a real-world challenge that aligns with your interests and contributes to the
wellbeing of your community, educational institution, or fellow students. Your task is to develop a GUI-
based desktop application that addresses the identified problem.

Project Theme Options: Choose ONE


Theme A: Community Engagement and Public Services
Develop a C# Windows Forms application that improves public service delivery in a targeted community
(e.g., health services, waste management, water supply, etc).

Theme B: Education and Student Services


Build a system to improve campus services such as residence allocation, grade access, learning material
distribution, class registers, etc.

NOTE:
YOU DO NOT HAVE TO CHOOSE ANY OF THESE EXAMPLES BUT YOUR
IDENTIFIED PROBLEM MUST FALL WITHIN ONE OF THE ABOVE
THEMES.

1
Project Tasks and Deliverables
1. Clearly identify the real-world problem and the target group affected.
2. Provide justification for why the problem is significant and warrants a solution.
3. Formulate a clear problem statement that can be addressed using a GUI-based desktop application.
4. Assess the feasibility of your proposed solution and describe the anticipated benefits for users.
5. Identify and describe at least three core services the application will offer.
6. List the key design requirements and draft the layout of the application's user interface.
7. Design and build the Windows Forms application using C# and implement a N-tier architecture.
8. Include user authentication (register, login, update details, delete account).
9. Implement the three core services you identified.
10. Use SQL Server as the relational database for data storage.
11. Apply input validation and necessary control mechanisms for usability and data integrity.
12. Ensure all layers—presentation, application logic, and data—are properly connected.
13. Develop a class to handle interaction between the UI and the database.

Minimum Technical Requirements


 User Registration, Login, Account Management (update/delete)
 GUI Forms with appropriate input validations
 SQL Server Database with query functionality
 Three functional services directly addressing the identified problem
 Structured in N-Tier Architecture (UI, Logic, Data)

2
Assessment Rubric
Task # Criteria Assessment Weight Due Date
Method
1 Problem Presentation 15 Marks 20 June 2025
Definition and
Proposed
Solution
2 UI Design and Presentation 20 Marks 18 July 2025
3 Input Validation Presentation 15 Marks 25 July 2025
4 SQL Server Presentation 15 Marks 15 August 2025
connection User
registration,
login, Password
reset
5 Functionality of Presentation 25 Marks 29 August 2025
the Three Core
Services
6 Project Essay 10 Marks 12 September 2025
documentation
Total 100 Marks

3
Student Guide:
Task 1: create a PowerPoint presentation
Slide 1: Group name and member details
Slide 2: Clearly identify the real-world problem and the target group affected.
Respond to these:
 What is the problem that you have identified?
 Where is the problem that you have identified?
 Who is affected by the problem that you have identified?
 What is currently being done to solve the problem that you have identified?
 What are the drawbacks of the current way the problem is being solved?
Slide 3: What is your proposed solution:
Respond to these:
 State the proposed solution: e.g. a windows form application that does abcde……….
 State the benefits of the proposed solution to those affected by the problem stated in the previous
slide
Slide 4: Target group
Respond to these:
 State clearly who you are creating the application for (who will use it)
Slide 5: Key Functional Requirements:
Respond to these:
 User roles: State each user and actions they can perform on the proposed application.
Slide 5: Three core services to implement:
Respond to these:
 State clearly Three key services to implement

4
POWERPOINT PRESENTATION RUBRIC
Total: 15 Marks

Criteria Excellent (Full Good (Partial Needs Improvement Marks


Marks) Marks) (Low/No Marks)
Slide 1: Group Info Group name and all Minor detail Missing group name or /0
(1 mark) member details missing (e.g., multiple member details.
clearly listed. incomplete names
or unclear group
names).
Slide 2: Problem Clearly identifies Covers most Few details provided or /4
Identification (4 the problem, aspects but lacks significant information
marks) location, affected clarity/detail in missing.
group, current one or two areas.
solutions, and
drawbacks.
Slide 3: Proposed Clear proposed Solution and Vague or generic solution /3
Solution (3 marks) solution and all benefits stated but and unclear/no benefits
benefits explained lacks depth or mentioned.
in the context of the clarity in some
target group. areas.
Slide 4: Target Clearly identifies a General target No clear identification of /2
Group (2 marks) specific target user group stated, target group.
group. lacks specificity.
Slide 5: Key User roles and Roles stated, but Missing or vague user /2
Functional corresponding actions not fully roles and actions.
Requirements (2 actions clearly clear or only
marks) defined. partially
described.
Slide 6: Three Core Three key services Only two services Less than two services or /3
Services (3 marks) clearly and listed or vague descriptions missing or
appropriately descriptions. unclear.
described.
Presentation Slides are clear, Minor layout or Poor organization, /1
Quality (1 mark) well-organized, and formatting issues. spelling/grammar issues,
visually appealing. or unreadable content.

5
Task 2: UI DESIGN Presentation:
Total: 20 Marks

Inadequate (Low/No
Criteria Excellent (Full Marks) Satisfactory (Partial Marks) Marks
Marks)

Logical and consistent layout; Usable layout with minor Poorly organized or
Layout and
well-organized interface with inconsistencies or some confusing layout; difficult /5
Structure (4)
clear grouping and spacing. clutter. to navigate.

Easy to use; intuitive Moderately usable with Difficult to use; unclear


Usability and
navigation with helpful labels minor issues in labelling or labelling, poor navigation /5
UX (3)
and clear call-to-actions. navigation. or lacks basic guidance.

Controls are missing,


Appropriate use of controls Mostly appropriate controls;
Use of excessive, or misused;
(buttons, textboxes, etc.); all some redundancy or /5
Controls (3) doesn't meet functional
controls relevant to the task. misused controls.
needs.

Visually appealing; consistent Acceptable appearance; Cluttered, inconsistent, or


Aesthetic
fonts, colours, and sizes used minor inconsistencies in visually unappealing /5
Design (2)
appropriately. design elements. design.

Some validation
Includes proper input Little or no validation;
Error implemented; may miss
validation and user feedback poor user feedback or /2
Handling (2) edge cases or feedback is
for incorrect actions. error handling.
limited.

6
Task 3: Input Validation
Total: 15 Marks

Satisfactory (Partial Inadequate (Low/No


Criteria Excellent (Full Marks) Marks
Marks) Marks)

All input fields include


Most fields validated Few or no input
Field-Level proper validation (text,
correctly; minor issues in validations implemented; /4
Validation (4) numbers, email, etc.) with
logic or feedback. major fields unprotected.
clear feedback.

Error messages are clear, Messages exist but may No or very generic
Error Handling and
user-friendly, and specific lack clarity or messages; not helpful to /3
Feedback (3)
to the input issue. consistency. the user.

Proper use of try-catch for Try-catch used but not


Use of Try- No try-catch blocks or
handling input exceptions optimally (e.g., overly /2
Catch (2) incorrect usage.
where appropriate. broad or unnecessary).

UI prevents submission or
UI Behavior on UI allows action but UI allows invalid input
highlights errors before /2
Invalid Input (2) highlights issues after. with no feedback.
proceeding.

Validation logic is clean, Code works but includes Messy, repeated, or


Code Structure &
modular, and reusable (e.g., duplication or lacks hard-to-maintain /2
Reusability (2)
via helper methods). structure. validation logic.

All possible input scenarios Most cases handled; Major gaps in validation;
Overall Validation
and edge cases are handled edge cases may be several cases not /2
Coverage (2)
effectively. missed. considered.

7
Task 4: SQL Server connection User registration, login, Password reset
15 Marks

Inadequate (Low/No
Criteria Excellent (Full Marks) Satisfactory (Partial Marks) Marks
Marks)

Secure and efficient


SQL Server Connection established but Connection not
connection established
Connection (2 lacks error handling or working, insecure, or /2
with error handling and
marks) shows minor inefficiencies. poorly implemented.
tested successfully.

User Fully functional form with Form inserts to database but Form does not insert to
Registration(5 validation, database insert, lacks validation or clear database or major /5
marks) and user feedback. feedback. functionality is broken.

Valid credentials are Login does not


Login works but lacks
User Login (4 authenticated correctly; function correctly or
proper error handling or /5
marks) errors are handled bypasses security
validation.
gracefully. checks.

Secure reset implemented Reset works with limited Reset broken, insecure,
Password Reset(3
with identity verification validation or minor issues or does not update /3
marks)
and database update. in implementation. password.

8
Task 5: Functionality of the Three Core Services
15 Marks

Satisfactory (3 marks Needs Improvement (0-2


Criteria Excellent (5 marks each) Marks
each) marks each)

Fully implemented service Mostly works with minor Service incomplete, major
Service 1
works as specified, no bugs, bugs or small missing bugs, or does not work at /5
Functionality
intuitive UI features all

Fully implemented service Mostly works with minor Service incomplete, major
Service 2
works as specified, no bugs, bugs or small missing bugs, or does not work at /5
Functionality
intuitive UI features all

Fully implemented service Mostly works with minor Service incomplete, major
Service 3
works as specified, no bugs, bugs or small missing bugs, or does not work at /5
Functionality
intuitive UI features all

You might also like