Escolar Documentos
Profissional Documentos
Cultura Documentos
Introduction:
How to Ride Trains on the Philippine General Railway
constraints and other form of perils and incidences that can affect the
performance of the train and the personnel of the company.
B. Entity-Relationship Model showing transaction on how to ride the
trains of the Philippine General Railway
1:1
1:1
M:1
1:M
M:1
1:M
As per the current system, a passenger can buy a ticket for himself or
several tickets for him and his companions. Once the passengers go
inside the train, the inspectors will check their ticket for an assurance that
those inside the train are the once who has made their payment. These
inspectors are assigned by the company to stay on their respective train
designations for their entire shift.
II. Mission
Company:
The PGR shall provide safe, reliable and affordable railway services as a
socio-economic development tool within the framework of the
metropolitan infrastructure system, while ensuring sustainable operations
so that optimum service can be rendered at a minimum passenger and
freight prices.
Information Technology:
We aim to improve the current system of Philippine General Railway
Company in order to give their client secured and comfortable trip. On its
financial aspect, we would like to assure that every resource is being
utilized and used optimally in order to save finances in the long run.
III. Vision
Company:
Philippine General Railway envisions an improved, sustainable railway
system running from Caloocan to Alabang City. The company will be the
name when it comes to transactional organization. The clients will be
accommodated at their best by giving them secured trip and ease of
access to the transportation system.
Information Technology:
Philippine General Railway will have an effective tool that it can use to
manage the passengers in order for both parties to save time and effort.
The scope of project define the project feasibility, the technology , finance
, time and resources best define in technology whether the defects can be
reduced in the project and up which level financially, whether the overall
project cost is affordable. Time describe the whether the projection
finishing point will be achieve on time or before time resources required
should be available at the rate of cost and time.
V. User
To see the different types of agents on responsible in running the current
ticketing system in PGR, please check the Use-Case Diagram Below:
Conductor
/ Inspector
2. Design constraint:
3. Hardware requirements:
For the hardware requirements the SRS specifies the logical
characteristics of each interface b/w the software product and the
hardware components. It specifies the hardware requirements like
memory restrictions, cache size, the processor, RAM size etc... those
are required for the software to run.
Minimum Hardware Requirements
RAM 128 MB
Cache 512 kb
Processor Pentium IV
RAM 256 MB
Cache 512 kb
4. Software requirements:
Any window based operating system with DOS support are primary
requirements for software development. Windows XP, FrontPage and
dumps are required. The systems must be connected via LAN and
connection to internet is mandatory.
Non-Functional Requirements:
1. Security:
The system use passwords in order to avoid unauthorized users have
access on the database they are not intended to use or even see. The
systems back-end servers shall only be accessible to authenticated
management.
2. Reliability:
The reliability of the overall project depends on the reliability of the
separate components. The main pillar of reliability of the system is the
backup of the database which is continuously maintained and updated to
reflect the most recent changes. Also the system will be functioning inside
a container. Thus the overall stability of the system depends on the
stability of container and its underlying operating system.
3. Availability:
The system should be available at all times, meaning the user can access
it using a web browser, only restricted by the down time of the server on
which the system runs. A customer friendly system which is in access of
people around the world should work 24 hours. In case of a of a hardware
failure or database corruption, a replacement page will be shown. Also in
case of a hardware failure or database corruption, backups of the
database should be retrieved from the server and saved by the Organizer.
Then the service will be restarted. It means 24/7 availability.
4. Maintainability:
A commercial database is used for maintaining the database and the
application server takes care of the site. In case of a failure, a reinitialization of the project will be done. Also the software design is being
done with modularity in mind so that maintainability can be done
efficiently.
5. Supportability:
The code and supporting modules of the system will be well documented
and easy to understand.
implemented
II.
Use
Diagram
Case
To see the
types of users
utilize
the
once
it
is
implemented,
check
the
Diagram
different
who
can
project
please
Use-Case
Below: