This document describes a final year project management and tracking system. It includes sections on functional requirements, use cases, prototypes, and test cases. The functional requirements allow students to upload artifacts, coordinators to manage terms and supervisors, and supervisors to view projects. Use cases describe how a coordinator can create a term. Prototypes demonstrate the user interface. Test cases validate creating, editing, and deleting terms in the system.

1. FINAL YEAR PROJECT MANAGEMENT
AND TRACKING SYSTEM
(Final Year Project part-1 Fall 2019)
Supervised by: Mr. Samir Obaid
Hina Mahmood Qureshi (BCS163008)
Muhammad Haroon Qureshi (BCS163009)

2. Introduction
 Project Management and Tracking System are collaboration tools that helps group
of people in a project to collaborate for smooth execution of project.
 There can be different roles in project.
 Students
 Project Coordinator.
 Supervisors
 The tracking part of these system helps to track different artifacts such as
 Requirements with Design
 Requirement with Code.
 Code with Design
 Design with Implementation and Testing

3. Functional Requirements:
S. No. Functional Requirement
1 User (Student, Supervisor and Coordinator) can login to the system
2 User (Student, Supervisor and Coordinator) can sign up to the system
3 Student can create profile
4 Student can upload artifacts
5 Student can resolve comments
6 Coordinator can manage supervisor’s panel
7 Coordinator can manage term
8 Coordinator can manage PLOs
9 Coordinator can manage CLOs
10 Coordinator can manage Exam
11 Coordinator can manage Questions
12 Coordinator can manage Supervisors
13 Supervisor can view projects
14 Supervisor can approve groups
15 Supervisor can respond to comments

4. Selected Functional Requirements:
S. No. Functional Requirement
1 Coordinator can manage term
2 Coordinator can manage PLOs
3 Coordinator can manage CLOs
4 Coordinator can manage Exam
5 Coordinator can manage Questions
6 Coordinator can manage supervisor’s panel
7 Coordinator can manage Supervisors

5. Use Case Diagram

6. Use Case Description
Actors: Coordinator
Description: Coordinator shall be adding, updating and deleting terms
Trigger: Create term Button
Preconditions: Coordinator must have click the create term button.
Post
conditions:
Coordinator have created term and will manage it
Normal Flow: Actor
1) Coordinator shall click on
create term button
3) Coordinator shall click on save
button
System
2) System shall provide a forum for
adding credentials.
4) System shall notifies the term has
created successfully
5) System will display created term
with edit and delete option.

7. System Sequence Diagram
( )
( )

8. Domain Model

9. Architecture Diagram

10. Class Diagram

11. Sequence Diagram
Create (id)

12. Data Base Schema

13. Prototypes:

14. Prototypes:

15. Prototypes:

16. Prototypes:

17. Prototypes:

18. Prototypes:

19. Prototypes:

20. Test Case 1: CreateTerm
Test: Create term with all valid inputs
Date: 23 January 2020
System: Final Year Project Management & Tracking System
Objective: Create term with valid inputs Test ID:1
Version:1 Test Type: System
Input:
Term Name= 201
Date From= 17 Feb, 2020
Date To= 20 June, 2020
Working Term= True
Expected Result: Data will be added to the database and will be shown by system in a table
Actual Result: passed

21. Test Case 2: CreateTerm
Test: Create term with all invalid inputs
Date: 23 January 2020
System: Final Year Project Management & Tracking System
Objective: Create term with invalid inputs Test ID:2
Version:1.1 Test Type: System
Input:
Term Name= 201
Date From= 20 June, 2020
Date To=17 Feb, 2020
Working Term= Working
Expected Result: Data will not be added to the database and will not be shown by system in a table
Actual Result: passed

22. Test Case 3: EditTerm
Test: Edit term by changing DateTo field
Date: 23 January 2020
System: Final Year Project Management & Tracking System
Objective: Edit term by changing Date To field Test ID:3
Version:1.2 Test Type: System
Input:
Date To=18 Feb, 2020
Expected Result: Data will be edited to the database and will be shown by system in a table
Actual Result: passed

23. Test Case 4: DeleteTerm
Test: Delete term
Date: 23 January 2020
System: Final Year Project Management & Tracking System
Objective: Delete term Test ID:4
Version:1.3 Test Type: System
Input:
Remove Button Clicked
Expected Result: Data will be deleted from the database and will not be shown by system
in a table
Actual Result: passed

24. Thank You!