COMSATS University Islamabad, Lahore Campus

Department of Computer Science

Software Project Management

Assignment no. 2

Submitted By

Umer Nadeem (SP19-BSE-151)

Shanzee (SP19-BSE-022)
Project Charter

Campus Management System

Project Charter
Project Purpose
Due to popular demand for automated systems for everyday tasks that were previously handled
manually by Teachers, Students, and Administrations in Educational Institutes, Web Based
Campus Management Systems (CMS) have started to grow in Universities and some Schools
and Colleges over the last few years. The focus is similar to those of other systems or portals
used in Pakistani universities. A web application to help with student attendance, course
registration, task assignment, and receiving feedback from students on their assigned work.

Measurable Project Objectives

The Campus Management System will have to provide the following functionalities.

For administration
• Seeing and modifying personal data.
• Creating and uploading course catalogues so that they can be accessed by the teacher who
is teaching the course for the semester.
• Assigning a certain course to a specific teacher for the semester.
• Adding or removing students from a course.
• Employee/Teacher and Student Profiles Creation and Editing
• Notification of Important Announcements to Teachers or Students.

For Teachers
• It will list the courses and classes they are teaching, as well as the students who are enroll
ed in those classes, their contact information, and their attendance.
•  It will include the ability to track class attendance, assign tasks to students in a class, and 
a gateway for collecting completed assignments and delivering educational resources to s
tudents..
 • It will provide a platform for teachers to post educational resources such as books, article
s, and research papers so that they may access them whenever and wherever they 
login in to their accounts.
• They will receive notifications from the administration.
• It will display the list of Courses being offered in a semester by the university.

For Students
• Will provide list of the university's courses offered in a semester.
• A list of the courses in which the student is enrolled, as well as the ability to register for
classes.
• Viewing the performance or results from previous semesters and generating a result card.
• A portal for uploading completed assignments and viewing which tasks have been
assigned by an instructor.
• Keeping track of their attendance and performance in a course they are currently enrolled
in.
• Course-related Important Announcements
• At the end of the semester, reviewing and giving rating to the professors who taught a
certain course
• Students can also download their fee voucher thru student portal
• They can generate a query on the portal to issue challan slip, examination fee etc

High-level Requirements
A convenient and efficient Web Application must be designed and deployed on the Comsats
University Campus Main Server to assure the project's success. The application must be
compatible with the existing technologies used on Comsats University's official website. To run
the newly developed CMS, the Main Server must meet the basic technical requirements. To
function with the CMS, all employee, administrator, and student profiles and data must be
computerized. To complete the CMS workflow, all three interfaces (Admin, Employee, and
Student) must be interlinked.
Assumptions and Constraints
Assumptions in this project are as following.
• The CMS can be hosted on the Comsats University Campus Server
• The existing database and website are compatible with the newly built CMS.
• CMS can be operated by the Administration, Faculty, and Students;
• The CMS can be accessed by the majority of students who have access to a
working Internet connection outside of Comsats University; and
Constraints of this project will be as follows.
• There is no database, or the database previously utilized by the University is incompatible with
the CMS, and the University committee charged with overseeing the project's development does
not collaborate with the Project Manager.

High Level Description & Boundaries

Description
The goal of implementing an integrated system is to increase the efficiency and the effectiveness
of the entire organization. The focus is similar to other systems or portals being used in
Universities in Pakistan. An integrated Web Application to aid in attendance of students,
Registering of Courses, Assigning Tasks and getting feedback from the students on their
assigned tasks.

Boundaries
• Financial and Accounts information will not be integrated in the CMS.
• University Transport information will not be integrated.

High-level Risks
Communication Risk
When you are in control of a project, you must adhere to a tight work ethic of effective and
timely communication. Setting up meetings with stakeholders, such as project donors, allows
you to keep track of any changes, reassign duties, and develop a cohesive team. This may be the
most significant risk for our CMS, as we would require a large database as well as reliable data
from many departments on campus.

Technology Risk
The technological side of administering a project is becoming more complex as new and
improved technologies emerge. Technological risks are more difficult to manage since they
necessitate people training and the purchase of software. The validity of the HTTP/HTTPs
certificate expiring and needing to be renewed is one such risk that might be created in our
Campus Management system. Another technological issue could be DDoS or other malware-
related website attacks, which have become all too common, even among the larger companies.

Cost Risk
A project's completion is endangered if there is a shortfall or mishandling of project finances as a
result of an inflated budget or other constraints. When a project's cost exceeds the money
allocated, the risk may be transferred to other operations and labour divisions. A reduction in
funds could potentially lead to the occurrence of a scope risk. We'll require operating funding
because we're running a CMS. This will ensure that the servers are up and running, and that a
person or many staff are adequately funded. If the project's cost surpasses its utility, it will have
to be abandoned.

Operational Risk
A project may stall or terminate if there is a poor implementation of critical operations and core
processes such as production or procurement. The risks could result in a direct or indirect loss
owing to inadequacy or failed qualitative, quantitative or strategies. We might run into the
following operational risks:
• IT system risk – the IT department may not be able to properly support and run the
website on the server.
• Human and process direct implementation risk – the students and facility involved is
unable to understand how the website works.
• Human and process indirect implementation risk – the employee that is supposed to
maintain the project is unable to do so, for any reason.
• Financial capacity risk – the cost of maintenance is exceeding the effectiveness of the
project or the university is unable to further finance the maintenance of the website.

Summary Budget & Milestones

When the following milestones are met, the project will be finished.
1. The Application's Prototypes and Initial Workflow have been authorized.
2. The database is created
3. The backend has been created.
4. Each user's (Administrator/Employee/Student) frontend is created.
5. The database has been integrated.
6. The Application Has Been Deployed
The University Committee and the Project Manager have agreed a budget of Rs.1,000,000. The
Abc Software Company will get Rs.600,000 as an advance payment, with the remaining
Rs.50,000 due upon completion of the project.

Initial Stakeholders
• Comsats University
• Shareholders of Comsats University
• Committee overlooking project
• Company Abc delivering the project

Assigned Project Manager

Umer nadeem of the company Abc will be the assigned as a project manager for the campus
management system for university Comsats and he will be responsible to deliver fully functional
and errorless project.
WBS

Gantt Chart
 Name Role Responsibilities

Ali Sponsor -Approve or deny scope change requests as appropriate

-Evaluate need for scope change requests
-Accept project deliverables

Awais Project Manager - Measure and verify project scope

- Facilitate scope change requests
- Facilitate impact assessments of scope change requests
- Organize and facilitate scheduled change control meetings
- Communicate outcomes of scope change requests
- Update project documents upon approval of all scope changes
Sadia Team Lead - Measure and verify project scope
- Validate scope change requests
- Participate in impact assessments of scope change requests
- Communicate outcomes of scope change requests to team
- Facilitate team level change review process
Shaanze Team Member - Participate in defining change resolutions
- Evaluate the need for scope changes and communicate them to t
- project manager as necessary

Umer Team Member - Participate in defining change resolutions

- Evaluate the need for scope changes and communicate them to t
- project manager

Stakeholder Register

Requirement Traceability Matrix

Project Name Campus Management System
Project Number 12
Project Manager Umer

ID Requirem WBS Assig Accept Tes

Nu ent Name Deliver ned ance ted
mbe and able To Criteria By
r Descriptio an
n d
Dat
e
01 Log in 1.1 Umer Accepte Pas
d s
02 Sign up 2.1 Shaa Accepte Pas
nze d s
03 Password/ 3.1 Umer Accepte Pas
forgot d s
Password
04 Add to cart 4.1 Shaa Accepte Pas
nze d s
05 Search 5.1 Umer Accepte Pas
d s
06 Payment 6.1 Shaa Accepte Pas
nze d s
07 Cancel 7.1 Umer Accepte Pas
order d s
08 Delivery 8.1 Shaa Accepte Pas
nze d s
09 Review 9.1 Umer Accepte Pas
d s
10 Suggestio 10.1 Shaa Accepte Pas
n nze d s