Project Management

Managing a Software-Tracking Database for a Higher Education Institution
Jean Micael Colon


Introduction

Institutions of higher education rely on hundreds of software applications to support instruction, research, administration, cybersecurity, and student services. Managing these systems requires accurate documentation of software types, licensing agreements, installation locations, and update cycles. Without centralized tracking, institutions face risks such as licensing violations, security vulnerabilities, version inconsistencies, and inefficient budgeting.

This project proposes the development of a centralized software-tracking database for a university similar in scale to the University of South Florida. The database will be developed and maintained by the institution’s Information Technology (IT) department and will provide real-time visibility into software usage across departments. The implementation plan follows the six project management steps outlined in Baars (2006): Definition Phase, Design Phase, Preparation Phase, Implementation Phase, Follow-Up Phase, and Completion Phase.

Definition Phase

The Definition Phase establishes the scope, objectives, constraints, and stakeholders of the project (Baars, 2006). The project team will conduct stakeholder interviews, define system requirements, create a project charter, identify risks, and establish a timeline and preliminary budget. Responsible personnel include the Project Manager, Systems Analyst, IT Director, and Cybersecurity Officer. Deliverables include the Project Charter, Scope Statement, and Risk Assessment.

Design Phase

During the Design Phase, requirements are translated into technical specifications (Baars, 2006). The team will develop Entity-Relationship diagrams, define database schemas, create access control structures, and establish data governance policies. Responsible personnel include the Database Architect, Systems Analyst, and Security Specialist. Deliverables include a System Design Document, ER diagrams, and a Security Plan.

Preparation Phase

The Preparation Phase ensures resources and environments are ready for development (Baars, 2006). Tasks include setting up development environments, assigning roles, creating a detailed project schedule, and preparing a data migration strategy. Deliverables include a finalized Gantt chart, resource allocation plan, and migration documentation.

Implementation Phase

The Implementation Phase involves building and deploying the system (Baars, 2006). Developers will create database tables, implement the user interface, conduct testing, and pilot the system within a selected department. Deliverables include the operational database, testing reports, and pilot evaluation results.

Follow-Up Phase

The Follow-Up Phase evaluates system performance and incorporates feedback (Baars, 2006). The team will monitor KPIs, conduct audits, provide training, and refine the system based on user feedback. Deliverables include a Post-Implementation Review Report and updated training materials.

Completion Phase

The Completion Phase formally closes the project (Baars, 2006). Final documentation is archived, stakeholders approve deliverables, and the system transitions fully to IT operations. A Lessons Learned document ensures institutional knowledge is preserved.

Conclusion

By following the six project management phases outlined by Baars (2006), the university ensures structured planning, controlled execution, and sustainable implementation. The centralized software-tracking database will improve compliance, enhance cybersecurity oversight, and support strategic IT governance across the institution.

References

Baars, W. (2006). Project management handbook. Stichting SURF.