Professional Documents
Culture Documents
Data Pirates Chapter1 3
Data Pirates Chapter1 3
Data Pirates:
INTRODUCTION
Specific Objectives:
M college.computerstudies@chmsc.edu.ph
(034) 434 8148
chmsc.edu.ph Excellence • Compassion • Environmentalism • Love aY Country • Social Responsibility • /n/‘eg’r/ • Openness • Resilience
CHAPTER II
A. Foreign Studies
B. Local Studies
Synthesis
Initialization
In the beginning phase, the team members engage in lively
discussions and brainstorming sessions to determine the initial
course of action. With a carefully selected project proposal,
which has been thoroughly researched and aligns with the desired
objectives, the groundwork is laid for the subsequent phases.
After carefully selecting the team members, consisting of a
project manager, technical writer, and programmer, the team
members will start planning the next steps.
Planning Phase
In this phase, the proponents research the possible related
studies that are relevant to our proposed title. The researchers
find a business organization that suits the proposed title.
Based on research, includes creating a project timeline,
allocating resources, and considering the budget. This detailed
planning provides a structured framework for the project's
development.
Requirement Gathering
This phase all possible requirements of the system
development are in this phase. Requirements are a set of
functions and constraints that the end user expects from the
system. The proponents conduct interviews and consultations with
key stakeholders from J-BEE Trucking Services such as business
owners and potential system users, to fully understand business
organization expectations and needs regarding the automated
transaction management system. Finally, a requirement
specification document was created which serves the purpose of a
guideline for the next phase of the model.
Design
The analysis phase includes the gathering of the data by
studying the current system. The process in the documentation of
the system project, the gathering of the sample billing sheet,
and customer and lineup information sheet. In the design phase,
the proponents generated a rough draft of the system. The data
flow diagram and the database structure (DFD) were the backbones
of the J-BEE Trucking Services Automated Transaction Management
System. The design helped in specifying the hardware and
the system
requirements and also helped define the overall system
architecture.
Testing
During this step, the system is tested against a set of
standards and norms. To ensure the reliability and effectiveness
of the J-BEE Trucking Services Automated Transaction Management
System, thorough testing is conducted. The proponent carries out
various tests to verify that the system performs as intended,
many sorts of testing are performed, including performance
testing, stress testing, security testing, and usability
testing. Any identified bugs or issues are promptly addressed
during this phase to ensure the system's functionality and user
satisfaction.
Coding
During this step, developers put the chosen design into
action by writing the necessary code according to predefined
coding standards and metrics for the J-BEE Trucking Services
Automated Transaction Management System. Based on the
requirements and design criteria, ensuring that the system meets
the desired functionality and user expectations.
Deployment
The deployment phase completes the project by making the
system operational. The research team meticulously installs and
configures the system in the intended setting, providing a
smooth transfer from development to production. Extensive
testing and verification are performed to ensure that the system
is completely functioning and meets the demands of the users.
After a successful
deployment, this allows users and stakeholders to access and
benefit from the system's automated transaction management
capabilities.
Operational Framework
The proponent’s system is designed to provide a in
automated transaction management system in J-BEE Trucking
Services use.
Table 1. billing
Table 3. customer
Field Name Data Size Description
Type
Table 4. lineup
Table 5. reminder
Table 6. user
Hardware Requirements
Software Requirements
Gantt Chart