DEPARTMENT OF COMPUTER SCIENCE
UNIVERSITY OF ENGINEERING & TECHNOLOGY LAHORE
Dated: March 25, 2025
CSC104 Term Project
1. Term Project will be done in group of two to three members.
2. Groups will be made within sections.
3. Working on project will be started from March 29, 2025. Github Repositories should be
created from March 28, 2025. and add [Link]@[Link] as Collaborator.
4. Progress on project will be tracked from Github accounts.
5. Name of repository should be as follows: DBS25F001 where 001 is the project ID which
will be given from eduko.
6. Project will be evaluated based on rubrics described in the document(all the rubrics are
based on basic requirement).
7. Deadlines will be as followed:
Milestone Deadline
Selection of Project March 27, 2025
Repositories Submission March 28, 2025
Detailed requirement document April 4, 2025
ERD Design April 10, 2025
GUI of project April 13, 2025
Object Oriented Design April 15, 2025
Database Design April 17, 2025
Implementation of Design April 28, 2025
Project Documentation May 2, 2025
Project Testing May 4, 2025
Resolution of Issues May 6, 2025
Project Viva Any time after May 2, 2025
(One member can be chosen only)
• Basic requirement are being shared, you are required to add more features on your own
and write detailed requirements to remove any ambiguity. Detailed requirement should
mention the UI design using pencil tool.
• In all of these projects, basic requirement to save data in database.
• Any frontend framework could be used except Mobile Application, for backend, only C#
and Java can be used.
• Students can use Entity frameworks of any language in addition to queries
Basic Requirements to be implemented in the project.
1. Minimum 8 domain classes
2. Minimum 5 software classes
3. Entities in ERD(Minimum 10)
4. Database tables(Minimum 15)
5. Validators
6. Handle exceptions
7. UI should contain text boxes, password fields, radio button, check boxes, dropdowns,
date selector fields, text areas, scroll bar, tables, buttons inside table, use of panels for at
least 3 forms, file menu on each screen, use of same form for add and edit.
8. Logging in case of errors
9. Use of transaction wherever required (at least 3 examples)
10. Use of views (at least 5 examples)
11. Use of Stored procedure(minimum three)
12. Use of Triggers (at least 2 examples)
13. Use of constraints (at least 10)
14. PDF reports (minimum 10 business level reports)
15. Responsive UI
16. Reports generation based on parameters