Department of Information Technology

University of Gujrat

ACADEMIC PROJECT
MANAGEMENT SYSTEM

Session: BSIT Fall 2020-2024

Project Advisor: Ms. IRUM SHAHZADI

Submitted By

AHMED ALI RAZA 20011556-035

SUBHAN RAZA 20011556-030

SAMI ULLAH 20011556-003

Department of Information Technology

University of Gujrat

Department of Information Technology

© University of Gujrat
1
 STATEMENT OF SUBMISSION

This is certify that Ahmed Ali Raza,Subhan Raza Roll No. 20011556-035,20011556-030
and Sami Ullah Roll No. 20011556-003 has successfully completed 30% the final year
project named as Academic Project Management System at the Department of
Information Technology, University of Gujrat, to fulfill the requirement of the degree of
BSIT in Information Technology.

______________________ _____________________
Project Supervisor Project Coordination Office
Faculty of C&IT -UOG

______________________
Head of the Department

Department of Information Technology

© University of Gujrat
2
 Acknowledgement

We truly acknowledge the cooperation and help make by Mam Rizwana and Mam Irum
Teachers, Department of Information Technology, University of Gujrat. He has been a
constant source of guidance throughout the course of this project. We would also like to
thank Mam Rizwana and Mam Irum for his help and guidance throughout this project.
We are also thankful to our friends and families whose silent support led us to complete
30% our project.

Date: 9-3-2024

Department of Information Technology

© University of Gujrat
3
 Abstract

The Academic Project Management System (APMS) is a application-based platform

designed to facilitate the seamless organization, coordination, and monitoring of
academic projects within educational institutions. Recognizing the challenges posed by
traditional project management methods in academic settings, APMS leverages modern
technology to provide an intuitive and collaborative environment.

Key functionalities of APMS include project creation, task assignment, progress tracking,
and resource management. Through a user-friendly interface, project stakeholders,
including students, faculty, and administrators, can easily collaborate and communicate
in real-time.

APMS incorporates features such as milestone tracking, palgrisim checking, and

analytics tools to assess project performance and resource utilization. This not only
enhances project outcomes but also facilitates data-driven decision-making for educators
and administrators. The system aims to streamline the academic project lifecycle,
reducing administrative overhead and providing a structured framework for successful
project completion.

Department of Information Technology

© University of Gujrat
4
TABLE OF CONTENTS
CHAPTER 1: PROJECT FEASIBILITY REPORT ................................................ 7,7
1.1. INTRODUCTION ...................................................................................................... 7
1.2. PROJECT/PRODUCT FEASIBILITY REPORT ................................................................ 7
1.2.1. Technical Feasibility ...................................................................................... 7
1.2.2. Operational Feasibility .................................................................................. 7
1.2.3. Economic Feasibility ...................................................................................... 8
1.2.4. Schedule Feasibility ....................................................................................... 8
1.2.5. Specification Feasibility ................................................................................. 8
1.2.6. Information Feasibility ................................................................................... 8
1.2.7. Motivational Feasibility ................................................................................. 9
1.2.8. Legal & Ethical Feasibility ............................................................................ 9
1.3. PROJECT/PRODUCT SCOPE...................................................................................... 9
1.4. PROJECT/PRODUCT COSTING .................................................................................. 9
1.4.1. Project Cost Estimation By Function Point Analysis ...................................... 9
1.4.2. Project Cost Estimation by using COCOMO’81 (Constructive Cost Model) . 11
1.4.3. Activity Based Costing ................................................................................. 11
1.5. TASK DEPENDENCY TABLE .................................................................................. 11
1.6. CPM - CRITICAL PATH METHOD .......................................................................... 12
1.7. GANTT CHART ..................................................................................................... 13
1.8. INTRODUCTION TO TEAM MEMBER AND THEIR SKILL SET ....................................... 13
1.9. TASK AND MEMBER ASSIGNMENT TABLE ............................................................. 14
1.10. TOOLS AND TECHNOLOGY WITH REASONING....................................................... 16
1.11. VISION DOCUMENT ............................................................................................ 16
1.12. RISK LIST .......................................................................................................... 16
1.13. PRODUCT FEATURES/ PRODUCT DECOMPOSITION ............................................... 17
CHAPTER 2: SOFTWARE REQUIREMENT SPECIFICATION (FOR OBJECT
ORIENTED APPROACH) .................................................................................... 19,19
2.1 INTRODUCTION: .................................................................................................... 19
2.1.1 Systems Specifications................................................................................... 19
3.1.2. Identifying External Entities ......................................................................... 20
2.1.3. Context Level Data Flow Diagram: ............................................................. 21
2.1.4. Capture "shall" Statements: ......................................................................... 22
2.1.5. Allocate Requirements: ................................................................................ 23
2.1.6. Prioritize Requirements: .............................................................................. 24
2.1.7. Requirements Trace-ability Matrix: ............................................................. 25
2.2.12. Usecase Description................................................................................... 28

CHAPTER 3: DESIGN DOCUMENT (FOR OBJECT ORIENTED APPROACH)

.................................................................................................................................... 344
Department of Information Technology
© University of Gujrat
5
 3.1. INTRODUCTION: .............................................................................................. 35,34
3.2. DOMAIN MODEL ............................................................................................. 36,34
3.3. SYSTEM SEQUENCE DIAGRAM ......................................................................... 37,35
3.4. SEQUENCE DIAGRAM ...................................................................................... 38,35
3.5. COLLABORATION DIAGRAM ............................................................................ 39,37
3.6. OPERATION CONTRACTS ............................. 40,ERROR! BOOKMARK NOT DEFINED.
3.7. DESIGN CLASS DIAGRAM ................................................................................ 40,39
3.8. STATE CHART DIAGRAM .................................................................................. 41,40
3.9. DATA MODEL ................................................................................................. 41,40

Department of Information Technology

© University of Gujrat
6
Chapter 1: Project Feasibility Report

1.1. Introduction
In the academic land scape, effective project management plays pivotal
ensuring successful collaboration between supervisors and students.
Recognizing the need for a streamlined and efficient system, our project
endeavors to create an "Academic Project Management System." This system is
tailored to enhance the coordination, communication, and oversight of academic
projects, fostering a collaborative environment that nurtures student growth and
academic excellence.

1.2. Project/Product Feasibility Report

When a project is started the first matter to establish is to assess the feasibility of a
project or product. Feasibility means the extent to which appropriate data and information
are readily available or can be obtained with available resources such as staff, expertise,
time, and equipment. It is basically used as a measure of how practical or beneficial the
development of a software system will be to you (or organization). This activity recurs
throughout the life cycle.
There are many types of feasibilities:

 Technical
 Operational
 Economic
 Schedule
 Specification
 Information
 Motivational
 Legal and Ethical

1.2.1. Technical Feasibility

In Technical point of view tools that are used to develop our project are available, so it is
possible to develop our REBEL (Customized Application) project and our team members
have skills to develop such system. Our system is practical due to the context of all
application always run-on Desktops/ laptops and smart phones.

1.2.2. Operational Feasibility

Operational feasibility refers to the practicality and viability of implementing a system
Department of Information Technology
© University of Gujrat
7
within an organization's existing infrastructure and processes. In the case of an Academic
Project Management System (APMS), assessing operational feasibility involves
evaluating whether the system can be effectively integrated into the academic
environment. Here are key considerations for evaluating the operational feasibility of an
APMS:
1. User Acceptance:
Assess the willingness of faculty, students, and administrators to adopt and use the
APMS. Gather feedback through surveys, interviews, or pilot programs to gauge user
acceptance.

2. Training Requirements:
Evaluate the training needs for users to effectively navigate and utilize the APMS.
Consider the ease of learning the system and the availability of training resources.
3. Integration with Existing Systems:
Examine the compatibility of the APMS with existing academic systems and tools.
Ensure seamless integration to avoid disruptions and data inconsistencies.

1.2.3. Economic Feasibility

Economically our Project has many benefits. Economic Feasibility has two types: Cost
Estimates:
In Cost Estimates Total Cost of a Project can be calculated Acquisition Cost= 80k
Maintenance and Operation Cost= 10k Per Year of website Services & Hosting and 5k
for every year testing and updating.
Benefit Estimates:
Benefit estimates enclose tangible benefits and intangible benefits. Tangible Benefits:
First year we provide our services for free and make our system easier to use then our
services are paid.
Intangible Benefits:
We try to provide best services to the users of our system and provide correct and useful
information and help.

1.2.4. Schedule Feasibility

Time is an important factor. The assessment and evaluation of the completion of a project
with the available staff and resources within time is very essential. Meeting deadlines and
milestones should always be kept in mind.

1.2.5. Specification Feasibility

Requirements Specification and Analysis is the main aspect of our project. We must have
proper requirements specification to make our project meaningful and useful according to
user requirements.

1.2.6. Information Feasibility

To complete our project, we divided the project into tasks and tasks are assigned to each
member according to their skill set. We make our project reliable by using website
development techniques.
Department of Information Technology
© University of Gujrat
8
1.2.7. Motivational Feasibility
Motivational feasibility assesses whether there is sufficient enthusiasm, support, and
motivation among stakeholders to adopt and implement a new system, in this case, the
Academic Project Management System (APMS). The success of any project often
depends on the level of motivation and commitment from key individuals and groups
within the academic institution.

1.2.8. Legal & Ethical Feasibility

• Legally and ethically, we have legal rights to use tools that are used to develop
our project.
• We use Visual Studio Code that is totally free.
• We use Microsoft Visio for project documentation designing.
• We use database.

1.3. Project/Product Scope

The scope of an Academic Project Management System (APMS) encompasses a wide
range of functionalities and benefits aimed at improving the planning, execution, and
monitoring of academic projects within educational institutions. Here are key aspects that
define the scope of an APMS:
Project Planning:
Facilitates the creation and organization of academic project plans, including defining
project objectives, milestones, tasks, and timelines.
Progress Monitoring and Reporting:
Allows real-time tracking of project progress, milestones, and deadlines. Generates
reports and analytics to assess project performance and identify areas for improvement.
Customization and Flexibility:
Offers customization options to adapt the system to the specific needs and workflows of
different academic departments and project types.
Scalability:
Adapts to the varying sizes and complexities of academic projects, accommodating
increased data, users, and project requirements over time.
Security and Data Privacy:
Implements robust security measures to protect sensitive academic information and ensures
compliance with data privacy regulations

1.4. Project/Product Costing

1.4.1. Project Cost Estimation By Function Point Analysis

Component Type complexity of Components

Department of Information Technology

© University of Gujrat
9
 External inputs 23 3 23*4= 96 6 96

External outputs 13 4 13*5= 65 7 65

External inquiries 3 3 3*4= 20 6 20

Internal Logical Files 3 7 3*10= 30 15 30

Internal Interface Files 3 5 3*7= 21 10 21

Gross Function Point (GFP)=232

To compute function points (FP), the following relationship is used: FP est. = Count
Total * [ 0.65 + 0.01 * (Fi)] The degree of influence on 0
= No influence The degree of influence on 1 = incidental The degree of influence on 2 =
Moderate The degree of influence on 3 = Average The degree of influence on 4 =
Significant
The degree of influence on 5 = High influence

Fi=44 (14 values average)

Value Adjustment Factor (VAF)= 0.65+0.01*(Fi)
FP est. = GFP * VAF
FP est. = 232* [ 0.65 + 0.01 * (42)] FP est.
= 232 * 1.07 = 248.24 FP est. = 248.24
Where count total is the sum of all FP entries obtained from above figure and (Fi) is
value adjustment factor (VAF) is based on 14 general system characteristics (GSC's) that
rate the general functionality of the application being counted. Each characteristic has
associated descriptions that help determine the degrees of influence of the characteristics.
The degrees of influence range on a scale of zero to five, from no influence on strong
influence.
• Data communications
• Distributed data processing
• Performance
• Heavily used configuration
• Transaction rate
• On-Line data entry
• End-user efficiency
• On-Line update
• Complex processing
• Reusability
• Installation ease
• Operational ease
• Multiple sites
• Facilitate change
Department of Information Technology
© University of Gujrat
10
Finally, Total Project Cost and Total Project Effort are calculated given the average
productivity parameter for the system.

The formulae are given as follows:

Productivity parameter=248.24/3
=82.74

Cost / FP = labor rate / productivity parameter

=10000/82.74 =120.86

Total Project Cost = FP est. * (cost / FP)

=248.24*120.86 =30,074.802

Total Estimated Effort = FP est. / productivity parameter =286.24/82.74 =3.007

1.4.2. Project Cost Estimation by using COCOMO’81 (Constructive Cost Model)

Basic COCMO
TYPE Effort Schedule
Semi Detached PM= 3.0 (8)1.12= 30.81 TD= 2.5(30.81)0.35=8.3

PM= person-month (effort) KLOC= lines of code, in thousands

TD= number of months estimated for software development (duration)
People Required = Effort / Duration
People Required =30.81/ 8.3=3.7

1.4.3. Activity Based Costing

Activity Resources Cost Rate Duration
A. Mobile visual Free 12 Weeks
App Design, studio
Structure, and code
Layout

B. Database Database Free 2Weeks design & Storages

Development

Department of Information Technology

© University of Gujrat
11
 C. Login and Database Free 3 Weeks
Registration Authentication
Process

2k

D. Testing Android Free 2 Weeks

system

1.5. Task Dependency Table

The following are the steps to develop a task dependency table:

Task Dependency Duration

A Mobile Design None 4 Weeks
B Registration, project A 2 Weeks
dashboard and basic
setting overall
C Mobile Components A,,B 8 Weeks
D MySQL Database A,B,C 1 Week
Development and
connectivity
E Testing the Mobile app A,B,C,D 2 weeks
F Any Updating A,B,C,D,E 1 week
G Deployment of Mobile A,B,C,D,E 1 week
app
H Testing on Server A,B,C,D,F,G 1week

Department of Information Technology

© University of Gujrat
12
1.6. CPM - Critical Path Method

1.7. Gantt chart

1.8. Introduction to Team member and their skill set

A brief but a concise introduction of the team members should be provided signifying
their skill set. This skill set would especially be representative of the tasks and activities
assigned to him.
Name Skill Set Tasks
Ahmed Ali Raza Back-end Development Working on backend
Testing, php implementation overall

Department of Information Technology

© University of Gujrat
13
 Subhan Raza Website Design Website Front-end
Implementation Design Structure
Planning Layout login and
Front-end Development Registration process
Testing Module
Testing Website
Modules
Sami ullah Database Development Database Design,
MYSQL Deployment, Testing

1.9. Task and Member Assignment Table

Task durations and dependencies

Task Duration(days) Dependencies Members

T1 28 M2

T2 14 T1 M1,M2

T3 56 T1,T2 M1,M2,M3

T4 7 T1,T2,T3 M1,M3

T5 14 T1,T2,T3,T4 M1,M2,M3

Department of Information Technology

© University of Gujrat
14
 Task Duration(days) Dependencies Members
T1 28 M2

T2 14 T1 M1,M2

T3 56 T1,T2 M1,M2,M3

T4 7 T1,T2,T3 M1,M3

T5 14 T1,T2,T3,T4 M1,M2,M3

Allocation of People to Activities:

Task Member
T1 Ahmed Ali Raza
T2 Subhan Raza
T3 Subhan Raza, Sami
ullah

T4 Sami ullah
, Subhan Raza
T5 Subhan Raza,
Ahmed Ali Raza,
Sami ullah

T6 Subhan Raza,
Ahmed Ali Raza ,
Sami ullah
T7 Subhan Raza,
Ahmed Ali Raza

T8 Subhan Raza,
Ahmed Ali Raza,
Sami ullah

Department of Information Technology

© University of Gujrat
15
1.10. Tools and Technology with reasoning

Technology Tools
Visual studio code, Browser and Notepad++
Reason
Overall, browsers, Notepad++, and Visual Studio Code are indispensable tools in app
development, providing essential features for testing, editing code, debugging,
collaboration, and productivity. Developers often use a combination of these tools to
create, test, and maintain web and mobile applications effectively.

Languages
Php Laravel, HTML, CSS and JavaScript
Reason
Overall, PHP Laravel is a powerful and feature-rich framework that offers rapid
development, code organization, database abstraction, authentication, extensibility,
testing support, community support, and scalability. These qualities make it an excellent
choice for building a wide range of web applications efficiently.
Overall, HTML, CSS, and JavaScript form the foundation of modern web development,
enabling developers to create visually appealing, interactive, and cross-platform web
applications.

JQuery, Bootstrap, plagiarism Api and Pusher for notification

Reason
Overall, jQuery and Bootstrap are valuable tools in app development, offering features
such as cross-browser compatibility, DOM manipulation, AJAX support, responsive
design, CSS framework, component reusability, browser compatibility, and community
support. These qualities make them popular choices for building modern and interactive
web applications efficiently.
By leveraging a plagiarism API and Pusher for notifications, app developers can enhance
the user experience, maintain content quality, and ensure the integrity of user-generated
content, ultimately leading to a more engaging and trustworthy app environment.

1.11. Vision Document

In a rapidly evolving educational landscape, where collaborative and innovative projects
play a pivotal role in shaping the future leaders of our society, the Academic Project
Management System (APMS) envisions a dynamic platform that empowers students,
faculty, and administrators to seamlessly navigate the intricate world of academic
projects. APMS aspires to be a catalyst for academic excellence, fostering a culture of
collaboration, transparency, and efficiency within educational institutions.
In conclusion, the vision of the Academic Project Management System is to be a
transformative force, redefining how academic projects are conceived, executed, and
celebrated. By fostering a culture of innovation, collaboration, and efficiency, APMS
Department of Information Technology
© University of Gujrat
16
aims to empower the academic community, paving the way for a future where every
student's potential is unlocked, and every project becomes a stepping stone towards a
brighter, knowledge-driven world.

1.12. Risk List

There are few risks of this projects.

 Resistance to Adoption

 Technical Challenges

 Data Security and Privacy Concerns

 Integration Challenges

 Lack of Stakeholder Engagement

 Scalability Issues

 Regulatory Compliance

 User Resistance to Change

1.13. Product Features/ Product Decomposition

User Authentication Module:
 Description: Ensures secure logins foramens, supervisors, and students.
 Functionality: Manages user credentials, authentication processes, and
authorization levels.
Admin Panel:
 Description: Interfaceforadministratorstomanageusers, projects,andassignments.
 Functionality: Allows admins to assign projects to supervisors,
associate students with projects, and over seethe overall project
allocation process.
Supervisor Dashboard:
 Description: Dedicated interface for supervisors to manage assigned
projects and tasks.
 Functionality: Displays a list of assigned projects, including project names
and associated student details. Allows supervisors to assign tasks to
students, monitor task progress, and mark tasks as completed.
Task Management Module:
 Description:Facilitates th ecreation,assignment,and tracking of
tasks within projects.
Department of Information Technology
© University of Gujrat
17
  Functionality: Allows supervisors to create tasks, assign them to specific
students, set deadlines, and track task completion progress.
Project Database:
 Description: Centralized repository for storing project details,
including assigned supervisors and students.
 Functionality:Enable sefficient storageandretrieval of project in
formation,ensuring supervisors and students areas sociated with the correct
projects.
Plagiarism Check Module/API Integration:
 Description:Ensures academic integrity by detecting and preventing plagiarism.
 Functionality:Integrates with aplagiarism detection serviceor API
,conducting thorough checks on project submissions.
Notification System:
 Description:Keep susers informed about project updates,task
assignments,and deadlines.
 Functionality:Send automated notification stosupervisors and students
regarding new projectas asignments,upcoming task deadlines,and task
completion updates.
Progress Monitoring Module:
 Description:Allows supervisors to monitor th eoverall progressof projects and tasks.
 Functionality: Provides visual representations of project timelines, task
completion rates,and overall project health.
User Profile Management:
 Description:Allows users to customize and manage their profiles.
 Functionality: Enables users to update personal information,
preferences, and notification settings.

Department of Information Technology

© University of Gujrat
18
Chapter 2: Software Requirement Specification (For Object Oriented
Approach)

2.1 Introduction:
Requirements engineering process provides the appropriate mechanism for
understanding what the customer wants, analyzing need, assessing
feasibility, negotiating a reasonable solution, specifying the solution
unambiguously, validating the specification and managing the requirements
as they are transformed into an operational system. The task of capturing,
structuring, and accurately representing the user's requirements so that they
can be correctly embodied in systems which meet those requirements (i.e.,
are of good quality).

• Requirements elicitation
• Requirements analysis and negotiation
• Requirements specification
• System modeling
• Requirements validation
• Requirements management

Here, requirements specification is to be discussed. Requirements specification

would lead to thefollowing four steps:

• Identify external interfaces

• Development of context diagram
• Capture “shall statements
• Allocate requirements
• Prioritize requirements
• Development of requirements traceability matrix

2.1.1 Systems Specifications

The following are the clauses that must be included while describing the system
specifications.
Introduction
This clause should contain brief “Introduction” of the system under discussion domain
knowledge. It can also contain company, its location, its historical background and its
current status in the market. The most important part of this clause is to give an overview
of the major business areas of the company. This overview must be very brief so that one
Department of Information Technology
© University of Gujrat
19
can get a bird’s eye view of the organization under study.
Existing System
This clause must be focusing on providing a comprehensive detail of main business areas
of the organizations that we have just mentioned in the previous clause. But here the
discussion should be more elaborative.
Organizational Chart
Organizational chart will be very much supportive to get a better overview of the
organization’s business areas and their decomposition into different departments.

Scope of the System

The Scope may include the boundaries of the system under study. To what domain you
want to restrict your project must be clearly mentioned in this clause.
Summary of Requirements: (Initial Requirements)
Visitors create account or login (if already have account)
Basic needs for account:
• Name
• Email
• Address
• Phone Number

User can manage their projects. Admin can manage the users, project progress, checking,
and plagiarism checking etc.
3.1.2. Identifying External Entities
The identification of the external entities will be based on the information contained in
your Abstract. This identification is done after two phases. We will map the “Green
Department of Information Technology
© University of Gujrat
20
wood” case study to make things more comprehensible.

The Identification of External Entities is done in two phases.

a. Over Specify Entities from Abstract:

On the basis of the Abstract, one might identify the entities from the problem.
Based on the Abstract, one might identify the entities from over project.

• Login and registration processes

• User can See the projects
• User can check percentage of plagiarism
• Admin create task project etc
• Supervisor check project performance
• User can update profile
• Checkout projects
b. Perform Refinement:
After over specifying the entities, you must refine them based on your business logic. For
example, in this example we found the following entities more related to our business
logic.
• Registration Module
• User module
• Main Admin Module
• Tracking Module
• Customize projects
• Checkout projects

2.1.3. Context Level Data Flow Diagram:

Context level data flow diagram contains only one process, representing the entire
system. The process is given the number zero and all external entities are shown on the
context diagram as well as major data flow to and from them. The diagram does not
contain any data stores.

Department of Information Technology

© University of Gujrat
21
2.1.4. Capture "shall" Statements:
Identify “shall” statements, as they would be all functional requirements.
Para # Initial Requirements

1 User Authentication Module

2 Admin Panel

3 Mobile app “shall” provide sign up or register page to user for sign up

4 User “shall” login to the system.

5 Mobile app “shall” provide new page to user for further working.

6 Supervisor Dashboard

7 Task Management Module

8 Project Database

9 Plagiarism Check Module/API Integration

10 Notification System

11 Progress Monitoring Module

12 User Profile Management

Department of Information Technology

© University of Gujrat
22
2.1.5. Allocate Requirements:
Allocate the requirements in the use cases.
1.0 A user “shall” search project. Search Project
1.1 A user “shall” register himself to the UC_ Register
Application.
1.2 Application “shall” provide sign up or UC_ Register
register page to user for sign up.
1.3 User “shall” login to the system. UC_Login
1.4 Application “shall” provide new page to UC_project Search
user for further working.
1.5 User “shall” enter the Project name for UC_Search Project
search.
1.7 User “shall” select desired project. UC_select Project
1.8 User “shall” also view pictures of projects. UC View project
1.9 User “shall” see all the projects. UC View Project
1.10 User “shall” open the project. UC Open Project
2.1 User “shall” select the project. UC_select Project
2.2 User “shall” get notified whenever a project UC Notification System
is modified.
2.3 User “shall” see the project detail. UC Project Details
2.4 User “shall” enter order number for track- UC Tracking
in.
2.5 Order checker “shall” login to system. UC Tracking
2.7 Suprivisor “shall” login to system. UC Login
2.9 Admin “shall” login to system. UC login
2.10 Suprivisor can put Plagrism and check the UC Project details
submission from the user
.
3.1 A user “shall” upload the project. UC Upload
3.2 System “shall” check the deadline of UC Deadline
submission.

Department of Information Technology

© University of Gujrat
23
2.1.6. Prioritize Requirements:
Requirements must be prioritized as this will help achieve tasks easily. Rank them as
“highest, medium, and lowest”.
Para # Rank Initial Requirements Use Case Use Case Name
ID
1.0 Highest User “shall” select UC_1 UC_ UC_Select Desired
project project

1.1 Highest User “shall” run UC_2 UC Run Query

query.

1.2 Highest User “shall” be UC_3 UC_Confirm Project

notified about the Submission
project upload
details.
1.3 Highest User must ON the UC_6 UC_Select project
Internet to Use
the web site
1.4 Highest Suprivisor update UC_7 UC_Enter project details
details.

1.6 Highest Admin or UC_8 UC add Projects

suprivisor add
project
2.0 Medium A user “shall” UC_9 UC_register
register himself to
the website.
2.1 Medium A user “shall” UC_10 UC_Login
login to the
website.
2.2 Medium Status checker UC_11 UC tracking
shall login to
system.
2.3 Medium Main admin UC_12 UC register Suprivisor
“shall” register
the suprivisor.

Department of Information Technology

© University of Gujrat
24
 2.4 Medium Suprivisor will make UC_13 Uc Projects details
complete project
specifications
3.0 Lowest A user “shall” search UC_14 Uc project search
project.
3.1 Lowest User “shall” also view UC_15 UC product details
pictures of project.
3.2 Lowest User “shall” see the UC_16 UC upload detail
upload detail.

2.1.7. Requirements Trace-ability Matrix:

The requirements trace-ability matrix is a table used to trace project life cycle activities
and work products to the project requirements. The matrix establishes a thread that traces
requirements from identification through implementation.
Para # Initial Requirements Build Use Case Name Category

1.0 A user “shall” search B1 Search Project Business

project.
1.1 A user “shall” B1 UC_ Register Business
register himself to
the mobile app.
1.2 Mobile app “shall” B1 UC_ Register Business
provide
sign up or register
page to
user for sign up
1.3 User “shall” login to B1 UC_Login Business
the system.
1.4 Mobile app “shall” B1 UC_project Search Business
provide new page to
user for fur- there
working.
1.5 User “shall” enter B1 UC_Search Project Business
the Project name for
search.
1.7 User “shall” select B1 UC_select Project Business
desired project.

Department of Information Technology

© University of Gujrat
25
 1.8 User “shall” also B1 UC View project Business
view details of
projects.
1.10 User “shall” select B1 Uc Select Project Business
the type of project he
wants
2.1 User “shall” select B1 UC_select Project Business
the project.
2.2 A user can check the B1 UC Deadline Check Business
deadline of
submission.
2.3 User “shall” see B1 UC upload Business
the upload
detail.
2.4 User “shall” enter B1 UC Tracking Business
project name or
number for tracking.
2.7 Suprivisor “shall” B1 UC Lgin Business
login to system.
2.9 Admin “shall” login B1 UC login Business
to system.
2.10 Suprivisor can check B1 UC Project details Business
the projects and can
modify them.

2.8 User must submit the B1 UC Submission Business

project in the given
time.
3.2 System “shall” B1 Uc Submission Business
generate the
submission report
and Plagirism for the
user

Department of Information Technology

© University of Gujrat
26
2.2.10. High Level Usecase Diagram:
A use case scenario is a visual description, typically written in structured English or point
form, of a potential business situation that a system may or may not be able to handle.
A use case defines a goal-oriented set of interactions between external actors and the
system under consideration.
A use case is initiated by a user with a particular goal in mind, and completes
successfully when that goal is satisfied. It describes the sequence of interactions between
actors and the system necessary to deliver the service that satisfies the goal. It also
includes possible variants of this sequence, e.g., alternative sequences that may also
satisfy the goal, as well as sequences that may lead to failure to complete the service
because of exceptional behavior, error handling, etc. The system is treated as a “black
box”, and the interactions with system, including system responses, are as perceived from
outside the system.
Thus, use cases capture who (actor) does what (interaction) with the system, for what
purpose (goal), without dealing with system internals. A complete set of use cases
specifies all the different ways to use the system, and therefore defines all behavior
required of the system, bounding the scope of the system.
Generally, use case steps are written in an easy-to-understand structured narrative using
the vocabulary of the domain. This is engaging for users who can easily follow and
validate the use cases, and the accessibility encourages users to be actively involved in
defining the requirements.

Department of Information Technology

© University of Gujrat
27
2.2.11. Analysis Level Use Case Diagram:
Analysis level use case diagram is actually the explanation of high level use case
diagram. In this diagram high level use cases are expanded in a way that exhibit how high
level use cases will reach to their functionality. Two types of relationships are used in this
diagram. Which are:
 Extend
 Include

2.2.12. Use case Description

Product Search
Description: In this process the user can search different product from the database.

Department of Information Technology

© University of Gujrat
28
Use Case ID: UC-02 Actor: User

Use Case ID: UC-01 Actor: User

Use Case Name: Search Project Date: 7-Mar-23

Pre-Conditions:
User must be connected to the internet & Search a project.

Actor Actions System Response

1- User will navigate to the landing page 1- User will see projects related to the
of the website. keywords.

2- User will enter keyword for searching

process.

3- User will see the list of projects.

Post-Condition:
User got the Project.

User Registration

Description: In this process user can register himself to the website

Use Case Name: User Registration Date: 7-Mar-23

Department of Information Technology

© University of Gujrat
29
Pre-Conditions:
System must be connected to the internet for registration process.

Actor Actions System Response

1- User will navigate to the registration 2- Registration page will open.

page of the website.

2- User will enter its email or username and

password for registration process.

3- User will register to the website. 2- System perform the registration process.

Post-Condition:
User got registration to the website.

User Login
Description: The process of login to enter in website for authorized users.
Use Case ID: UC-03 Actor: User

Use Case Name: User Login Date: 7-Mar-23

Pre-Conditions:
User must be registered to the website first.

Actor Actions System Response

Select Desired project

Description: user select projects and review it.
Use Case ID: UC-04 Actor: User

Department of Information Technology

© University of Gujrat
30
Use Case Name: Select Desired project Date: 7-Mar-23

1- User will navigate to the login page of 1- Login page will open.
the website.

2- User will enter its email address and

password for login process.

3- User will initiate login event. 2- System perform the login process.

Post-Condition:
User got login to the website.

Open Desired Project

Description: The user will select the desired project that is good
for him and he canalso view the project.
Pre-Conditions:
User must be login and enter project name.

Actor Actions System Response

1- User will enter the name of the project. 1- Website will shows the project
.

2- User can be view the project. 2.System will provide the available
number of related projects.

Department of Information Technology

© University of Gujrat
31
 2- User can upload his own project as well.
2.System will provide the show project on
user dashboard.

Post-Condition:
User will create his project

Post-Condition:
User will get the selected project.

Customize Project
Description: The user will customize the project with desired needs or requirements

Use Case ID: UC-05 Actor: User

Use Case Name: customize project Date: 7-Mar-23

Pre-Conditions:
User must be login.

Actor Actions System Response

1- User will navigate to the user dashboard and 2- Mobile app will shows the project with
select the project he wants to edit. user design
.

Tracking of project
Description: The process of tracking is to get the details of the uploaded project.
Use Case ID: UC-06 Actor: User

Use Case Name: User Login Date: 7-Mar 2023

Pre-Conditions:
User must be registered to the website first.

Department of Information Technology

© University of Gujrat
32
 Actor Actions System Response

4- User will navigate to the user dashboard 3- Dashboard will open.

of the website.

5- User will enter product name he has

uploaded to check the submission status and
plagrism details.

6- User will get the details. 4- System perform the tracking process.

Post-Condition:
User got tracking status of the project.
While technically not part of UML, use case documents are closely related to UML use
cases. A use case document is text that captures the detailed functionality of a use case.
Such documents typically contain the following parts:
Enter Project Detail
Description: The supervisor will enter the project details and add project
Use Case ID: UC-07 Actor: Sub-admin

Use Case Name: Enter Project Detail Date: 7- Mar 2023

Pre-Conditions:
Suprivisor must be login into the website through username and pass-
word then enter the details related to project or Add project.
Actor Actions System Response

1- Suprivisor will login to the system. 1-Website will provide login to the
Suprivisor.
2- Suprivisor will enter the details of project.
2-Detailed information will show to
Suprivisor.

3- He can check the past projects as

well as the projects uploaded recently.
4- Suprivisor can also add new projects.

Department of Information Technology

© University of Gujrat
33
 Post-Condition:
Suprivisor will successfully enter the details or add projects.

Chapter 3: Design Document (For Object Oriented Approach)

3.1. Introduction:
Third deliverable is all about the software design. In the previous deliverable, analysis of
the system is completed. So we understand the current situation of the problem domain.
Now we are ready to strive for a solution for the problem domain by using object-
oriented approach. Following artifacts must be included in the 3 rd deliverable.

1. Domain Model
2. System Sequence Diagram
3. Sequence Diagram
4. Collaboration Diagram
5. Operation Contracts
6. Design Class Diagram
7. State Transition Diagram
8. Data Model

Now we discuss these artifacts one by one as follows:

3.2. Domain Model

.A domain model using a UML Class diagram is crucial for representing the key elements
and relationships within the system. This model helps to illustrate the structure and
concepts involved in the project, providing a visual representation of the classes,
attributes, and associations.

Department of Information Technology

© University of Gujrat
34
3.3. System Sequence Diagram
Utilize a domain model to design a document management system, showcasing its use
cases and object relationships.
Enterprise Architect Support: Enterprise Architect offers extensive support for creating a
domain model using UML Class diagrams.
Stages of Domain Modeling: The domain model is integral in various stages of
development, including requirement gathering, designing, development, and testing.
Organizing with Models: Learn how to organize a project by creating a domain model
and transcribing it into an implementation model.

3.4. Sequence Diagram

A Sequence diagram depicts the sequence of actions that occur in a system. The
invocation of methods in each object, and the order in which the invocation occurs is
captured in a Sequence diagram. This makes the Sequence diagram a very useful tool to
easily represent the dynamic behavior of a system.
A Sequence diagram is two-dimensional in nature. On the horizontal axis, it shows the
life of the object that it represents, while on the vertical axis, it shows the sequence of the
creation or invocation of these objects.
Because it uses class name and object name references, the Sequence diagram is very
useful in elaborating and detailing the dynamic design and the sequence and origin of
invocation of objects. Hence, the Sequence diagram is one of the most widely used
Department of Information Technology
© University of Gujrat
35
dynamic diagrams in UML.

Department of Information Technology

© University of Gujrat
36
3.5. Collaboration Diagram
A collaboration diagram describes a pattern of interaction among objects; it shows the
objects participating in the interaction by their links to each other and the messages that
they send to each other.
Collaboration diagrams are used to show how objects interact to perform the behavior of
a particular use case, or a part of a use case. Along with sequence diagrams,
collaborations are used by designers to define and clarify the roles of the objects that
perform a particular flow of events of a use case. They are the primary source of
information used to determining class responsibilities and interfaces.
Unlike a sequence diagram, a collaboration diagram shows the relationships among the
objects. Sequence diagrams and collaboration diagrams express similar information, but
show it in different ways. Collaboration diagrams show the relationships among objects
and are better for understanding all the effects on a given object and for procedural
design.
Department of Information Technology
© University of Gujrat
37
Because of the format of the collaboration diagram, they tend to better suited for analysis
activities. Specifically, they tend to be better suited to depicting simpler interactions of
smaller numbers of objects. As the number of objects and messages grows, the diagram
becomes increasingly hard to read. In addition, it is difficult to show additional
descriptive information such as timing, decision points, or other unstructured information
that can be easily added to the notes in a sequence diagram.

Operation Contract Syntax

Name: appropriate Name

Responsibilities: Perform a function

Cross References: System functions and Use Cases

Exceptions: none

Department of Information Technology

© University of Gujrat
38
Preconditions: Something or some relationship exists

Postconditions: An association was formed

When making an operation contract, think of the state of the system before the action
(snapshot) and the state of the system after the action (a second snapshot). The conditions
both before and after the action should be described in the operation contract. Do not
describe how the action or state changes were done. The pre and post conditions describe
state, not actions.
Typical post condion changes:

 Object attributes were changed.

 An instance of an object was created.
 An association was formed or broken.
 Postconditions are described in the past tense. They declare state changes to the
system. Fill in the name, then responsibilities, then postconditions.

3.7. Design Class Diagram

Classes are the work-horses of the design effort—they actually perform the real work of
the system. The other design elements—subsystems, packages and collaborations simply
describe how classes are grouped or how they interoperate.
Capsules are also stereotyped classes, used to represent concurrent threads of execution
in real-time systems. In such cases, other design classes are 'passive' classes, used within
the execution context provided by the 'active' capsules. When the software architect and
designer choose not to use a design approach based on capsules, it is still possible to
model concurrent behavior using 'active' classes.
Active classes are design classes, which coordinate and drive the behavior of the passive
classes - an active class is a class whose instances are active objects, owning their own
thread of control.

Department of Information Technology

© University of Gujrat
39
3.8. State chart diagram
For some operations, the behavior of the operation depends upon the state the receiver
object is in. A state machine is a tool for describing the states the object can assume and
the events that cause the object to move from one state to another. State machines are
most useful for describing active classes. The use of state machines is particularly
important for defining the behavior.

3.9. Data Model

The data model is a subset of the implementation model, which describes the logical and
physical representation of persistent data in the system.

Department of Information Technology

© University of Gujrat
40
Department of Information Technology
© University of Gujrat
41
Department of Information Technology
© University of Gujrat
42