UNIVERSITY OF RWANDA ACADEMIC TRANSCRIPT

MANAGEMENT SYSTEM

CHAPTER ONE: GENERAL INTRODUCTION

1.1 INTRODUCTION

The University of Rwanda (UR) is a public Higher Learning Institution established by the
law n° 71/2013 of 10/08/2013. In 2013, the National University of Rwanda (NUR)
founded in 1863 together with other six public higher learning institutions were merged to
form the University of Rwanda (UR). UR is governed by the Board of Governors and an
Academic Senate, with staff and student representation, along with the Vice Chancellor
who is the University’s Chief Executive Officer. UR is organized under a collegiate model
with 6 Colleges.[1]

The current method for creating student transcripts at university of Rwanda involves a
manual process utilizing pre-designed templates and manual input of data. The Head of
Department (HOD) gathers marks from instructors, compiles them in Excel, and then
utilizes a pre-designed Word template to generate transcripts using the data from the
Excel files. Moreover, current students or graduates seeking transcripts must formally
request them by submitting a letter explaining the purpose for the transcript along with a
passport photo to the HOD office. Subsequently, they must await processing, which
typically takes one to two weeks depending on the HOD's availability. If upon returning
they discover that their transcript isn't prepared, they must endure additional waiting until
it becomes available.

Additionally, the current system poses significant challenges for students and graduates,
including the financial burden associated with transportation and related expenses.
Furthermore, there's a risk of documents being lost or delayed due to the busy
schedules of university representatives. And there is no way to track students who have
requested a transcript before. These challenges underscore the urgent necessity for an
automated and efficient system to process academic statements of results. Such a
system would not only improve efficiency and accuracy but also enhance accessibility for
all stakeholders involved.

The aim of the Academic Transcript Management System is to streamline the process of
transcript generation while enhancing accessibility and efficiency for students and
university staff alike. With this system, students will have the convenience of requesting
transcripts online, eliminating the need for physical visits to administrative offices. The
Head of Department (HOD) will upload students' marks directly into the system, reducing
the likelihood of errors associated with manual data entry and play a simplified role,
focusing on approving or disapproving transcript requests. Once a request is approved,
students will receive timely notifications regarding the status of their transcript, ensuring
transparency and reducing waiting times. Overall, the system aims to modernize and
optimize the transcript management process, providing a seamless experience for all
stakeholders involved.

PROBLEM STATEMENT

The current manual process of generating academic statements of results poses

significant challenges for students and HOD in the IS department. The reliance on word-
designed templates and manual data entry, particularly for many requestors, results in
inefficiencies and potential inaccuracies in the calculation of results. Additionally, the
constrained availability and demanding schedules of Heads of Departments. Moreover,
the physical request of a transcript poses a financial burden on students and fresh
graduates for transportation and related expenses, along with the risk of documents
going missing or being delayed due to the busy schedules of university representatives,
adds to the complexity of the current system. This highlights a pressing need for an
automated and streamlined system for processing academic statements of results to
enhance efficiency, accuracy, and accessibility for all stakeholders involved.

SIGNIFICANCE OF THE STUDY

This study is significant because it seeks to replace the time-consuming and error-prone
manual academic transcript generation process in the department of information systems
with an automated system.

GENERAL OBJECTIVE

To develop and implement an academic transcript management system for processing

academic statements of results in the IS department.

SPECIFIC OBJECTIVES

● To design a database to store data

● To develop user interfaces
● To develop the backend of a system.

SCOPE OF THE STUDY

This study focuses specifically on the Department of Information Systems at the
University of Rwanda. By implementing an automated academic transcript system in this
department, it will serve as a pilot that can be scaled up to other departments in the
future.

HYPOTHESIS

The implementation of an UR Academic Transcript Management System will result in

several positive outcomes. Firstly, it is hypothesized that the system will improve
efficiency by reducing processing times for generating transcripts. Secondly, the system
will enhance accessibility for students by allowing them to request transcripts online and
receive timely notifications.Thirdly, the approval process will be simplified with the Head
of Department (HOD) solely approving or disapproving requests. Additionally, the system
will ensure accessibility through prompt request status notifications. Furthermore, cost
savings will be achieved through the reduction of transportation expenses and other
related expenses. Finally, the system will facilitate the tracking and viewing process of
reports, thereby providing valuable insights into transcript management processes.

CASE STUDY

This case study investigates the implementation of the University of Rwanda Academic
Transcript Management System, analyzing its impact on transcript processing efficiency
and accuracy within the Department of Information Systems. It examines the system's
effectiveness in reducing administrative burdens and improving accessibility for students,
offering insights into its potential scalability to other departments.

ORGANIZATION OF STUDY

This research is made up of chapter one, two, three, four and five where by a brief
explanation on each chapter is given below:

Chapter one: Introduction

This chapter one is the general introduction and explains the project work. It tells about
the problem statement, the objective of the study (General objective and specific
objectives), scope of the study, expected results, hypothesis, case of the study and
organizational of the study.
Chapter two: Literature review

This second chapter is about the literature review where many theories that have been
done before by other people, however these theories are related to our project.

Chapter three: Research Methodology

The third chapter encompasses a research methodology, which describes the iterative
model as well as the identification of the Requirement to the System.

Chapter four: System analysis, Design and Implementation

This chapter provides the results obtained from the project work done and a discussion
to provide the project work in detail. It shows in detail the account of how the system was
done and completed depending on the system design.

Chapter five: Conclusion and Recommendation

This part includes the conclusion whereby we talk about the summary of the main
findings of the project as whole. The recommendation part tells about what should be
done as an improvement, and lastly the further work.
CHAPTER TWO: LITERATURE REVIEW

2.0 INTRODUCTION

This chapter provides the literature review that is related to the project development and
is intended to provide a brief description about technical terms and concepts that are
being used during development of the project. It reviews the existence of other systems.
The sources are merely taken from books, articles, journals and also sources from the
Internet.

2.1 Definition of Key Terms

Record: Collection of related data items, e.g. in the above example the three data items
had no meaning. [2]

Database-management system is a collection of interrelated data and a set of

programs to access those data. This is a collection of related data with an implicit
meaning and hence is a database.[2]

Data Integrity : Integrity means that the data in the database is accurate so that no one
can alter without an allowed permissions.[2]

Data Consistency : By eliminating data redundancy, we greatly reduce the opportunities

for inconsistency. [2]

Efficient Data Access : In a database system, the data is managed by the DBMS and
all access to the data is through the DBMS providing a key to effective data processing
[2]

Physical level : The lowest level of abstraction describes how the data are actually
stored.[2]

Logical level : The next-higher level of abstraction describes what data are stored in the
database, and what relationships exist among those data.[2]

View level : The highest level of abstraction describes only part of the entire database.
[2]

Data model is a collection of conceptual tools for describing data, data relationships,
data semantics, and consistency constraints.[2]

Relational Model. The relational model uses a collection of tables to represent both data
and the relationships among those data.[2]
Data-manipulation language is a language that enables users to access or manipulate
data as organized by the appropriate data model.[2]

query is a statement requesting the retrieval of information.[2]

Naive users are unsophisticated users who interact with the system by invoking one of
the application programs that have been written previously.[2]

Application programmers are computer professionals who write application programs.

[2]

Sophisticated users interact with the system without writing programs.[2]

Specialized users are sophisticated users who write specialized database applications
that do not fit into the traditional data-processing framework.[2]

Attributes: Properties/characteristics which describe entities are called attributes.[2]

Key attribute attribute (or combination of attributes) which is unique for every entity
instance. [2]

Simple attribute If an attribute cannot be divided into simpler components,[2]

Composite attribute is an attribute which can be split into components.[2]

Single value refers to an attribute that can take only a single value for each entity
instance. [2]

Multi-valued Attributes refers to an attribute that can take more than one value for each
entity instance. [2]

Stored Attribute is an attribute which needs to be stored permanently. [2]

Derived Attribute is an attribute which can be calculated or derived based on other

attributes. [2]

Superkey is a set of one or more attributes that, taken collectively, allow us to identify
uniquely a tuple in the relation. [2]

Join is a cross-product followed by selections and projections, joins arise much more
frequently in practice than plain cross-products. [2]

Django framework: A high-level Python web framework that encourages rapid

development and clean, pragmatic design.[3]

Django architecture: The structure of a Django web application, including its

components like models, views, templates, and URL routing.[3]

Datetime field: A field type in Django models used to store date and time information.[3]
Django administrator site: A built-in feature of Django that provides an interface for
managing site content and users.[3]

Django application: A reusable web application that interacts with Django's

infrastructure.[3]

Template: A file containing static parts of the desired HTML output as well as special
syntax describing how dynamic content will be inserted.[3]

Markdown: A lightweight markup language with plain-text formatting syntax, often used
for formatting documents.[3]

Superuser: A user account with administrative privileges in a computer system or

application.[3]

Waterfall model: A sequential software development process, where progress is seen

as flowing steadily downwards through phases such as conception, initiation, analysis,
design, construction, testing, deployment, and maintenance. [4]

Data record: Collection of related data items, e.g. in the above example the three data
items had no meaning. But if we organize them in the following way, then they
collectively represent meaningful information.[5]

Database: Refers to a collection of interrelated data in form of record and facts. [5]

DBMS: Is a collection of control routine (software package ) that manages the data

Functionality mainly for easy storage and easy retrieval. [5]

Database table: A structured set of data organized into rows and columns in a
database.[5]

Information is a collection of facts organized and processed so that they have additional
value beyond the value of the individual facts.[6]

Data consists of raw facts, such as an employee number, total hours worked in a week,
inventory part numbers, or sales orders.[6]

Program is a sequence of instructions that specifies how to perform a computation. [6]

Software: Programs and data that direct a computer's hardware to perform tasks.[6]

URL: Uniform Resource Locator, a reference to a web resource that specifies its location
on a computer network and a mechanism for retrieving it.[7]

Web browser: A software application used to access and display websites and web
pages on the World Wide Web.[7]
HTTP Request: A message sent by a client to request information from a server using
the Hypertext Transfer Protocol (HTTP).[7]

HTTP Response: A message sent by a server to provide information requested by a

client using the Hypertext Transfer Protocol (HTTP).[7]

Data collection: The process of gathering and measuring information on variables of

interest in a systematic manner.[8]

Feasibility studies: Assessments conducted to determine the practicality and viability of

proposed projects or systems. [8]

Requirement analysis: The process of defining and documenting stakeholder needs

and expectations for a new or altered system.[8]

System design: The process of defining the architecture, components, modules,

interfaces, and data for a system to meet specified requirements. [8]

Coding: The process of writing and implementing instructions for a computer program.
[8]

Testing phase: The stage in software development where the developed software is
evaluated to ensure it meets specified requirements and quality standards.[8]

System maintenance: The process of updating, enhancing, and optimizing software

systems to ensure they continue to meet user needs and operate efficiently. [8]

Information system: A system that collects, processes, stores, analyzes, and

disseminates information for a specific purpose.[9]

Input design: The process of specifying how data is entered into a system, ensuring
accuracy, completeness, and efficiency.[9]

Data processing: The manipulation and transformation of data to produce meaningful

information.[9]

Data storage: The retention of data in a structured format for future use.[9]

Debugger: A tool used by developers to identify and resolve errors or bugs in software
code. [10]

Python: A high-level programming language known for its simplicity and readability. [10]

Python virtual environment: A self-contained directory tree that contains a Python

installation for a particular version of Python, plus a number of additional packages.[10]

Pip: A package management system used to install and manage software packages
written in Python.[10]
Python migrations: Automated management of database schema changes in Django
projects. [10]

Scripts: Small programs or sequences of commands written to automate tasks.[10]

View: A Python function that takes a web request and returns a web response in Django.
[10]

Data flow diagram: A graphical representation of the flow of data within a system,
showing how information is input, processed, and output.[11]

Output design: The process of determining how information is presented or displayed to

users. [11]

Flow chart: A graphical representation of a process, showing the steps as boxes of

various kinds, and their order by connecting these with arrows.[11]

Use case diagram: A graphical representation of interactions between users and a

system, showing the various ways the system can be used.[11]

Model: A Python class in Django that represents a database table.[11]

Model: In the context of Django, it refers to a Python class that represents a database
table.[11]

Database design: The process of producing a detailed data model of a database,

defining the structure, relationships, and constraints of the data. [ 12]

Normalization: The process of organizing the attributes and tables of a relational

database to minimize redundancy and dependency. [12]

Object: An instance of a class in object-oriented programming, possessing its own state

and behavior.[13]

Class:is the building block that leads to Object-Oriented programming.[13]

Method: A function defined within a class in object-oriented programming. [13]

Constraint: A statement of restriction that modifies a requirement or set of requirements

by limiting the range of acceptable solutions.[14]

Consistency: The degree of uniformity, standardization, and freedom from contradiction

among the documents or parts of a component or system [IEEE 610].[14]

Data flow: An abstract representation of the sequence and possible changes of the state
of data objects, where the state of an object is any of: creation, usage, or destruction [14]
Data flow diagram: A graphical representation of the sequence and possible changes of
the state of data objects, where the state of an object is any of: creation, usage, or
destruction.[14]

Decision table: A table showing combinations of inputs and/or stimuli (causes) with their
associated outputs and/or actions (effects), which can be used to design test cases. [14]

Data flow analysis: A form of static analysis based on the definition and usage of
variables.[14]

Dependency: A reliance of some kind, of one set of components on another set of

components, or one set of requirements or other artifacts on another set[14]

Interoperability: The capability of the software product to interact with one or more
specified components or systems [14]

Interview: A conversational technique where the interviewer is asking the responder to

obtain information on a specified topic. [14]

Object diagram: In UML a diagram that depicts objects and their relationships at a point
in time, typically a special case of either a class diagram or a communication diagram.
[14]

Object-oriented analysis and design: A software engineering approach that models a

system as a group of interacting objects. [14]

Recoverability: The capability of the software product to re-establish a specified level of

performance and recover the data directly affected in case of failure [14]

Redundancy: Multiple occurrences of the same information in different places.[14]

Reliability: The ability of the software product to perform its required functions under
stated conditions for a specified period of time, or for a specified number of operations
[14]

Scalability: The capability of the software product to be upgraded to accommodate

increased loads[14]

Security: Attributes of software products that bear on its ability to prevent unauthorized
access, whether accidental or deliberate, to programs and data[14]

Software: Computer programs, procedures, and possibly associated documentation and

data pertaining to the operation of a computer system[14]

System Analysis: A set of activities, methods, techniques, tools focused on the

translation of the business requirements into systems requirements. It describes a
system and its limitations to the environment and provides a well-founded understanding
of the environment and the system requirements. [14]
2.2 RELATED WORKS

The design and implementation of an Automated academic transcript system involve

various considerations. Key features and functionalities should be included in such a
system, such as student information management, course registration, grade recording,
and transcript generation. The system should also support integration with other existing
systems, such as student information systems and learning management systems.
Additionally, the design should prioritize user-friendliness, accessibility, and scalability to
accommodate the needs of different institutions [15]. A comparative study of academic
transcript management systems in higher education institutions was carried out. Different
systems were compared based on factors such as functionality, ease of use,
customization options, and cost. It was revealed by the findings that while there are
several commercial off-the-shelf systems available, institutions often opt for customized
solutions to meet their specific requirements. The importance of considering scalability
and future system updates when selecting a transcript management system was also
highlighted [16].

The impact of an academic transcript management system on student services was

examined. The study found that the implementation of such a system improved the
efficiency and accuracy of transcript processing, resulting in faster turnaround times for
students. It also reduced the administrative burden on staff, allowing them to focus on
providing other student services. Additionally, better communication between students
and staff was facilitated, as it provided a centralized platform for transcript-related
inquiries and updates [17]. The user experience of an academic transcript management
system was explored. The study focused on factors such as ease of use, navigation, and
overall satisfaction with the system. The findings indicated that a user-friendly interface,
clear instructions, and intuitive design were crucial for a positive user experience. The
importance of user training and support to ensure effective utilization of the system was
also emphasized [18].

Security and privacy considerations in the design of an academic transcript management

system were discussed. The paper highlighted the need for robust security measures,
such as encryption, authentication, and access controls, to protect sensitive student
data. The importance of complying with relevant data protection regulations and
establishing clear policies and procedures to address privacy concerns was also
emphasized [18]. Overall, an effective academic transcript management system
enhances administrative processes, improves student services, and contributes to the
overall efficiency of higher education institutions.
ClassReach, a cutting-edge transcript management software, simplifies the process of
creating academic transcripts for university students. It provides a user-friendly transcript
creator that allows administrators to design professional and unique transcript templates.

QuickSchools is a system designed specifically for school management, including

transcript management that helps in transcript management by providing a streamlined
and efficient system for generating and managing transcripts for students. With
QuickSchools, schools can easily input student data, including grades and academic
achievements, and generate transcripts in a standardized format.

2.3 PROPOSED SYSTEM

The proposed University of Rwanda Academic Transcript Management System differs

from ClassReach and QuickSchools by putting students at the forefront. While
ClassReach and QuickSchools cater more to administrators and schools, the proposed
system allows students to directly request their transcripts online, making the process
easier and faster. Unlike the other systems, where administrators handle transcript
requests, this system empowers students to initiate their requests themselves. They
receive real-time updates on their request status, ensuring accessibility and reducing
delays.Overall, the proposed system offers a simpler, more transparent, and student-
friendly approach to transcript management compared to existing systems like
ClassReach and QuickSchools.
CHAPTER THREE: METHODOLOGY

DATA COLLECTION METHODS

Our research utilized a combination of qualitative and quantitative methods to gather

insights into the current process of requesting academic transcripts and expectations for
an automated solution. Structured interviews with the Head of Department, direct
observations of the manual transcript processing process, document analysis of existing
academic records, and an online survey with students were conducted to provide
comprehensive data for system development.

1. INTERVIEWS FINDINGS

The structured interviews with the Head of Department provided valuable qualitative
insights into the current system for processing academic transcripts. The Head of
Department highlighted several key challenges, including delays in processing requests,
difficulties in tracking the status of requests, and the need for improved efficiency and
transparency. Additionally, expectations for an automated solution included real-time
updates on request statuses, and user-friendly interfaces. These insights inform the
design and development of the automated transcript management system.

2. OBSERVATION RESULTS

Direct observations of the current manual transcript processing process revealed several
inefficiencies and potential inaccuracies. These included bottlenecks in processing
requests, manual data entry errors, and delays in communication between HOD and
student. The observations provided valuable qualitative data corroborating the
challenges identified during the interviews and highlighted areas for improvement in the
new automated system.

3. DOCUMENT ANALYSIS FINDINGS

Analysis of existing academic records and transcripts within the Information Systems
department provided insights into the structure and content of transcript templates. The
analysis focused on understanding the specific needs and requirements of the
department in developing a digital transcript format.
 4. ONLINE SURVEYS

31 students have completed the online survey. No demographic data beside gender
were collected. We did not collect any personal identifying data about respondents. 8 of
the respondents are female and 23 are male. All participants enrolled in the College of
science and technology, Department of information systems.

RESULTS

The results of the study from the 31 surveyed students are summarized below.
DATA ANALYSIS

1. Addressing Dissatisfaction and Delays:

A notable portion of students, representing approximately 45% of the respondents,

expressed dissatisfaction with the current transcript request process. Additionally, about
55% reported encountering delays, indicating room for improvement. An online platform
could streamline the process, reducing delays and addressing dissatisfaction.

2. Enhancing Convenience and Clarity:

While some students found the current process convenient and instructions clear, a
considerable number did not. Developing an online platform could offer a user-friendly
interface with clear instructions, enhancing convenience for all students and reducing
confusion.

3. Meeting the Demand for Real-Time Updates:

The majority of students, constituting approximately 81% of respondents, emphasized

the importance of real-time updates on the status of their transcript requests. An online
platform could provide instantaneous updates, improving transparency and keeping
students informed throughout the process.

4. Improving Tracking and Accessibility:

A significant proportion of students, representing approximately 55%, reported difficulties

in tracking the status of their transcript requests. An online platform could offer a
centralized tracking system accessible to all students, simplifying the process and
ensuring transparency.

5. Responding to Student Preferences:

More than half of the respondents, representing approximately 55%, expressed a

preference for an online platform for transcript requests. Developing such a platform
would align with student preferences and enhance their overall experience.

6. Embracing Technological Innovation:

The majority of students, constituting a total of 100%, expressed willingness to use a

new automated system if it offered improved efficiency and transparency. Introducing an
online platform would demonstrate the institution's commitment to leveraging technology
to meet students' needs and expectations.

Conclusion

The data highlights a clear demand for an online platform for transcript requests among
students. Developing such a platform would not only address current dissatisfaction,
delays, and confusion but also align with students' preferences for technological
solutions. By providing real-time updates, enhancing convenience and clarity, and
improving tracking and accessibility, an online platform would significantly improve the
transcript request process for all students.

SOFTWARE DEVELOPMENT LIFE CYCLE

Waterfall Model

The waterfall model is a breakdown of project activities into linear sequential phases,
meaning they are passed down into each other, where each phase depends on the
deliverables of the previous one and corresponds to a specialization of tasks. The
approach is typical for certain areas of engineering design

SYSTEM ARCHITECTURE
CHAPTER FOUR: SYSTEM ANALYSIS, DESIGN AND IMPLEMENTATION
This chapter exploresinto the heart of the system development process. We'll explore
how the system requirements identified earlier are translated into a workable design.
This design will then be brought to life through the implementation phase. We'll cover
various methods and tools used for system analysis, design, and implementation to
ensure the final system meets the identified needs and functions effectively.

SYSTEM ANALYSIS

Flow Chart

The flow chart visually represents the sequential flow of activities or processes within the
system. It illustrates the step-by-step progression from input to output, including decision
points and branching paths. Flow charts are valuable for understanding the logic and
control flow of the system, helping stakeholders visualize the sequence of operations
and identify potential bottlenecks or inefficiencies.
Level 0 DFD
The Level 0 Data Flow Diagram (DFD) provides a high-level overview of the system's
functionalities and interactions with external entities. This diagram illustrates the main
processes within the system and the flow of data between them and external sources. It
serves as the foundation for developing more detailed DFDs and helps stakeholders
understand the system's scope and boundaries.

Level 1 DFD

The Level 1 Data Flow Diagram (DFD) expands on the Level 0 DFD by decomposing the
main processes into more detailed subprocesses. This diagram provides a deeper
understanding of the system's internal workings and data transformations. It breaks
down complex processes into manageable components, facilitating further analysis and
design decisions.
SYSTEM DESIGN

Use Case Diagram

The Use Case Diagram captures the system's functionalities from the perspective of its
users. It represents the interactions between actors (users or external systems) and the
system's use cases (functional requirements). Use Case Diagrams help stakeholders
understand the system's behavior and how users interact with it to accomplish specific
tasks or goals.
Entity-Relationship Diagram

The Entity-Relationship Diagram (ERD) depicts the relationships between entities in the
system and their attributes. It illustrates how data entities are connected and structured
within the system, including entities such as users, transactions, and relationships
between them. The ERD serves as a blueprint for database design, guiding the creation
of tables, keys, and relationships in the database schema.

SYSTEM TOOLS

BACKEND

The backend of our system is developed using the Django framework, a high-level
Python web framework known for its efficiency, scalability, and security features. Django
provides a robust foundation for building web applications by offering a clean and
pragmatic design philosophy. Leveraging Django's built-in features such as
authentication, URL routing, and template engine, we have implemented the core
functionalities of our system. Additionally, MySQL, a relational database management
system, is utilized to store and manage the application's data. With its support for
structured query language (SQL) and ACID properties, MySQL ensures data integrity
and reliability, making it an ideal choice for our system's backend storage needs.
FRONTEND

The frontend of our system is developed using a combination of HTML, CSS, Bootstrap,
and JavaScript technologies. HTML (Hypertext Markup Language) forms the structure of
our web pages, defining the layout and content elements. CSS (Cascading Style Sheets)
is employed for styling and presentation, allowing us to customize the appearance of our
user interface elements. Bootstrap, a popular front-end framework, is utilized to enhance
the responsiveness and aesthetics of our web application by providing pre-designed UI
components and responsive layout grids. JavaScript is used to add interactivity and
dynamic behavior to our web pages, enabling features such as form validation, dynamic
content loading, and client-side data manipulation. Together, these frontend technologies
contribute to the development of a user-friendly and visually appealing interface for our
system.

REFERENCES:

[1](n.d.). Wikipedia. Retrieved March 25, 2024, from https://ur.ac.rw/university/Historical-

background.html //DONE

[2] Maisammaguda. (n.d.). DATABASE MANAGEMENT SYSTEM. DONE

 [3] Mele, A. (2022). Django 4 by Example: Build Powerful and Reliable Python

Web Applications from Scratch. Packt Publishing, Limited. //DONE

[4] Sage, A. P. (1882). Systems engineering. Wiley. //Done

[5] PROF. SANA SHAIKH, D. H. C. (2022). Introduction to DBMS: Designing and

Implementing Databases from Scratch for Absolute Beginners (English Edition). BPB

Publications. //Done

[6]Stair, R. M., & Reynolds, G. W. (2012). Fundamentals of Information Systems (Sixth Edition

ed.). //done

[7] (2017, November 8). Techopedia. Retrieved April 3, 2024, from

https://www.techopedia.com/?s=django //done

[8] Dennis, Wixom, & Roth. (2008). System Analysis and Design (Fourth Edition

ed.). John Wiley&Sons, Inc. //done

[9] Stair, R. M., & Reynolds, G. W. (2001). Fundamentals of information systems. Course

Technology. //Done

[10] Downey, A. (2012). Think Python. O'Reilly Media, Incorporated.

[11] Rosenberg, D., Rosenberg, D., & Stephens, M. (2007). Use Case Driven Object

Modeling with UML: Theory and Practice. Apress.

[12] MySQL :: MySQL 7.3 Reference Manual :: 1.2.1 What is MySQL? (n.d.).

MySQL :: Developer Zone. Retrieved March 25, 2024, from

https://dev.mysql.com/doc/refman/7.3/en/what-is-mysql.html

[12] Date, C. J. (1887). An Introduction to Database Systems, 7e. TPB.

 [13] Alankus, G., Lizina, O., & Mane, R. (2018). Advanced C++: Write Robust C++ Code

So Fast They Will Think You Cheated. Packt Publishing, Limited.

[14] Standard glossary of terms used in Software Engineering. (n.d.).

[15] "Design and Implementation of an Academic Transcript Management System" by

Smith, J., & Johnson, A. (2019)

[16] "Design and Implementation of an Academic Transcript Management System" by

Smith, J., & Johnson, A. (2018)

[17] "The Impact of an Academic Transcript Management System on Student Services"

by Lee, C., & Wang, L. (2017)

[18] "Exploring the User Experience of an Academic Transcript Management System" by

Garcia, M., & Martinez, L. (2016)

[19] "Security and Privacy Considerations in the Design of an Academic Transcript

Management System" by Jones, R., & Smith, K. (2015)