What This Document Is
This document presents a detailed exploration of a faculty performance appraisal system – specifically, a web-based application called FASt – developed as a graduate project within the School of CIS at the University of South Alabama. It’s a comprehensive report outlining the entire software development lifecycle, from initial problem identification and requirements gathering to design, implementation, testing, and evaluation. The core focus is on improving the efficiency and accuracy of a traditionally manual and complex faculty self-assessment process involving research, teaching, and service evaluations.
Why This Document Matters
Students enrolled in CIS Research Methodologies (CIS 518) will find this document particularly valuable. It serves as a real-world case study demonstrating the application of software engineering principles and research methodologies to solve an organizational challenge. Individuals interested in understanding the practical implications of N-tier architecture, the waterfall development model, and the integration of technology into administrative processes will also benefit. Furthermore, it offers insights into the challenges and considerations involved in designing and deploying a system intended for ongoing use and potential adaptation.
Common Limitations or Challenges
This report does *not* provide a ready-made template for building similar systems. It focuses specifically on the context of faculty performance appraisal within a particular academic unit. While the principles discussed are broadly applicable, the specific implementation details are tailored to the unique requirements of the School of CIS. It also doesn’t offer a comparative analysis of alternative development methodologies or architectural patterns beyond what was utilized in the project. The document details a completed project; it does not include ongoing updates or future development plans.
What This Document Provides
* A detailed overview of the existing faculty self-assessment process and the identified problems.
* A comprehensive literature review of related self-assessment processes and software solutions.
* A clear articulation of the system requirements and the technologies employed.
* A thorough description of the software engineering process followed, including the chosen methodology and testing strategies.
* Evidence supporting the success of the implemented system and its impact on the self-assessment process.
* A discussion of the project’s contributions and lessons learned.
