Name:
Maham Fayaz
Roll No:
22101001-110
Assignment:
Software Project Management
Section:
Grey
Submitted To:
Ma’am Aysha Saddiqa
______________________________________________________________________________
Faculty of Computing & IT
University of Sialkot
______________________________________________________________________________
Risk Analysis in University Management System
Risks:
1. Changing Requirements
2. Data Security Issues
3. Integration Problems
4. User Resistance
5. Poor Internet Connectivity
6. Budget Overrun
7. System Slowness Under Load
8. Insufficient Testing
9. Inconsistent Data Entry
10. Legal Compliance
Risk 1: Changing Requirements:
In many UMS projects, requirements often change after development has started. Stakeholders
may add new features or ask for adjustments, leading to confusion and inefficiencies. These
frequent changes result in scope creep, extended timelines, and budget overruns.
➢ Solution:
To handle this risk, the team should adopt an Agile development model that
accommodates change through iterative cycles. A proper change request process should
be established to evaluate and approve any modifications. Frequent stakeholder meetings
will also help align expectations and reduce sudden requirement shifts.
Risk 2: Data Security Issues
University systems handle sensitive data such as personal information, academic records, and
payroll details. If this data is not adequately protected, it could be stolen, leaked, or misused. A
data breach would damage the institution's reputation and possibly lead to legal penalties.
➢ Solution:
The system should employ end-to-end encryption and secure authentication mechanisms
to protect sensitive information. Role-based access should be implemented so only
authorized users can view or modify specific data. Regular security testing and audits will
help identify vulnerabilities before attackers can exploit them.
Risk 3: Integration Problems
Integrating the new system with legacy modules like library management, hostel systems, or
examination portals can be challenging. Compatibility issues, differing data formats, or
undocumented APIs often cause delays. Failed integration results in incomplete functionality and
inconsistent data.
➢ Solution:
The development team should use standard, well-documented APIs and data formats like
JSON or XML. Integration should be planned early and tested frequently to detect issues
sooner. Middleware solutions can also help bridge communication between incompatible
systems.
Risk 4: User Resistance
Staff and faculty members may resist the adoption of the new system due to a lack of familiarity
or fear of technological change. This resistance can result in underutilization of the system and
reduced overall productivity.
➢ Solution:
Training programs, tutorials, and user manuals should be provided to make the transition
easier for staff. Engaging users during the design phase can build trust and improve
acceptance. The interface should be designed to be intuitive and user-friendly to
minimize confusion.
Risk 5: Poor Internet Connectivity
In many regions, especially rural areas, internet access may be unstable or slow. Users facing
connectivity issues may struggle to use the system during critical tasks like admissions or
registration.
➢ Solution:
The system should offer offline capabilities that allow users to work without an internet
connection and sync later. It should be optimized for low-bandwidth environments
through lightweight design. Additionally, deploying the application on CDN-backed
cloud servers ensures better regional performance.
Risk 6: Budget Overrun
As development progresses, additional features or delays can cause costs to exceed the allocated
budget. Budget overruns may force compromises in quality or halt development altogether.
➢ Solution:
A detailed scope and timeline should be defined at the beginning and approved by all
stakeholders. A contingency fund should be included to handle unexpected expenses. The
use of open-source tools and cost-effective platforms will help manage financial
constraints.
Risk 7: System Slowness Under Load
During peak periods such as course registration or results announcement, the system may
become slow or even crash. This can cause frustration among users and disrupt university
operations.
➢ Solution:
Performance testing tools should be used to simulate high-load conditions and identify
bottlenecks. The application should be hosted on scalable cloud infrastructure to handle
spikes in traffic. Database queries should be optimized, and caching techniques used to
reduce load times.
Risk 8: Insufficient Testing
If the system is not thoroughly tested, it may contain critical bugs that affect its functionality.
Undetected issues such as calculation errors or failed transactions can result in serious user
dissatisfaction.
➢ Solution:
A comprehensive testing plan should be followed, covering unit testing, integration
testing, and user acceptance testing. Automated testing tools can reduce manual effort
and improve accuracy. End-users should also participate in testing to ensure real-world
usability.
Risk 9: Inconsistent Data Entry
Manual data entry by different users can lead to inconsistent formats, duplicates, or missing
information. This inconsistency affects reporting accuracy and system reliability.
➢ Solution:
The system should implement validation rules, input masks, and dropdown menus to
ensure uniform data entry. Duplicate detection algorithms should be added to flag
repeated records. Regular audits should be scheduled to clean and standardize the
database.
Risk 10: Legal Compliance
Handling personal and academic data comes with strict legal obligations under data protection
laws such as GDPR or FERPA. If the system fails to meet these requirements, it may expose the
university to legal action.
➢ Solution:
Legal experts should be consulted during the design of data storage and sharing features.
Consent mechanisms must be built into the system for data collection. Audit trails and
clear privacy policies should be integrated to ensure transparency and accountability.
Risk Probability-Impact Table
Risk Probability Impact Risk Level Explanation
Changes happen
Changing
High Moderate High often (High) and
Requirements
they slow down
the work
(Moderate).
Hacks are
Changing
High High High common (High)
Requirements
and can cause
big data loss and
legal issues
(High).
Sometimes
Integration Moderate Moderate Moderate systems don’t
Problems work well
together
(Moderate),
causing delays
(Moderate).
Staff often resist
User Resistance High Low Moderate new systems
(High), but it’s
usually not
serious (Low).
Internet may be
Poor Internet
Moderate Low Low weak in some
Connectivity
areas Moderate,
but system still
works offline
(Low).
Costs may rise
Budget Moderate High High unexpectedly
Overrun (Moderate), and
this affects the
whole project
(High).
System slows
System High Moderate High during busy
Slowness Under times (High),
Load which delays
important tasks
(Moderate).
Testing is
Insufficient
Moderate High High sometimes
Testing
skipped
(Moderate), and
bugs can cause
serious issues
(High).
Manual entry
Inconsistent High Moderate High errors are
Data Entry common (High)
and affect
reports and
accuracy
(Moderate).
Legal issues are
Legal
Low High Moderate rare (Low), but
Compliance
very serious if
they happen
(High).