SYSTEMS ANALYSIS AND DESIGN (CSC 302)

PROJECT

LECTURER IN CHARGE: DR. MRS. OLADEJO

GROUP 4 MEMBERS

1. AROWOLO AYOMIDE 214865

2. ANIMASHAUN AHMAD 214863
3. ANJORIN ADEDAPO 214864
4. ADELOWO SAMUEL 214850
INTRODUCTION
ABOUT THE ANDROID LOCAL TRAIN TICKETING SYSTEM

An Android local train ticketing system is smartphone software that enables

college students to buy train tickets for local transit. It may also have features like
schedules, fare information, and real-time train monitoring. Students will find it more
convenient to buy tickets this way, and they will be able to plan their transportation more
quickly and avoid long queues.

Phase 1: SYSTEM PLANNING AND SELECTION

1. ORGANIZATIONAL HIERARCHY OF THE ANDROID LOCAL

TRAIN TICKETING SYSTEM
1. Board of Directors: The highest level of the organization, in charge of the system's
overall strategy and direction.
2. Executive Management Team: The Executive Management Team would be in
charge of managing the system's daily operations and carrying out the strategy
decided upon by the Board of Directors.
3. Operation Teams: The operations team would be in charge of overseeing the daily
operations of the system, including ticket sales, customer support, and system
upkeep.
4. IT Team: This group would be in charge of the system's technical components,
including network infrastructure, database management, and software
development.
5. Marketing Team: This team would be in charge of educating clients about the
system and its features and developing marketing efforts to promote system usage.
6. Customer Service Team: This group would be responsible for responding to
customer queries and grievances and supporting users.

There would be a team leader for each team, who would answer questions from
the executive management team. The teams would collaborate closely to ensure the
system runs smoothly and satisfies client expectations.
 1.1. PROBLEM OF THE SYSTEM

With an Android local train ticketing system, there could be a number of possible
problems, some of which include the following:

a. Technical issues: The system could be plagued by errors or faults that

prohibit correct operation.
b. Network connectivity: If the system depends on internet connectivity, poor
reception areas may prevent it from functioning effectively.
c. User interface: Users may find it challenging to use the system, which
makes it challenging for them to buy tickets.
d. Problems with the payment gateway could hinder users from completing
their transactions due to payment-related issues.
e. The system could not have enough security safeguards in place, leaving it
open to hacking or data leaks.
f. Limited help and training: The system's users may not receive enough
support or training, which makes it difficult for them to use it efficiently.
g. Excessive traffic: If the system cannot manage high traffic, delays or
crashes may occur.
h. Lack of integration: If the system isn't integrated with other systems, it may
lead to inconsistent data or effort duplication.
 1.2. SOLUTIONS TO THE PROBLEMS

The issues mentioned above for an Android local train ticketing system can be
resolved in a number of ways:

a. Technical issues: Test and upgrade the system frequently to address faults
and anomalies.
b. Improving the system's ability to function offline or in places with poor
network connectivity.
c. User interface: By Performing user testing to find and fix any interface
problems.
d. Use a trusted and secure payment channel to avoid payment difficulties.
e. Concerns about security? Put encryption, two-factor authentication, and
regular security audits into action.
f. Inadequate support and training: Create user guides and tutorials, offer
customer service, and provide user training.
g. Large traffic: Scale the system to manage high traffic, and/or leverage cloud
infrastructure or load balancing.
h. Lack of integration: To guarantee data consistency, we need to integrate the
system with other pertinent systems.

It is also crucial to keep in mind that, depending on the complexity of the issue, a
combination of technical, operational, and management solutions may be necessary to
address a given issue.
1.3. SYSTEM OBJECTIVES

The goal of an Android local railway ticketing system is to give users a quick and
easy way to buy train tickets using their mobile devices. In order to accomplish this,
the system would:

a. Make it simple for consumers to find and display train schedules and ticket
availability
b. Using a user-friendly UI and a reputable payment gateway to enable users
to buy tickets swiftly and securely.
c. Providing users with up-to-the-minute information on the condition of their
tickets and their travels.
d. enabling consumers to manage and view their past purchases.
e. Giving customers a quick and simple way to exchange or refund their
tickets.
f. Putting security measures in place to safeguard users' money and personal
information.
g. Integrating with other pertinent systems to give users accurate and current
information.
h. Having a user-friendly interface that is simple to use and requires a few
steps to purchase a train ticket.
i. The system should be created to offer a simple and seamless user
experience that makes it simple for customers to buy train tickets and
schedule their trips.

1.4. SYSTEM SERVICE REQUEST

A system service request is a form that is used to formally request the

installation of a new system, an update to an existing system, or a modification
to an existing system.
System Service Request

Requested By: Date: January 26th, 2023

Contact Information:

Email:

Service Request:

I am requesting the development of an Android-based local train ticketing system that will
allow users to purchase train tickets through their mobile devices. The system should enable
users to search for and view train schedules, check ticket availability, purchase tickets, view
their purchase history, and receive real-time updates on the status of their tickets and journeys.
This system will improve the convenience and efficiency of purchasing train tickets and will
help increase the number of people using public transportation.

Specific Requirements:
The software ought to be created for Android-powered smartphones.
Users should be able to utilize the system to look up train schedules and see what tickets are
still available.
Through the use of a responsive mobile interface and a dependable payment gateway, the
system should enable customers to buy tickets swiftly and securely.
Users should be able to access real-time updates on the status of their tickets and journeys
through the system.
Users should be able to access and manage their purchase history through the system.
If necessary, the system needs to offer a quick and simple way to replace or refund tickets.
To safeguard the personal and financial information of users, the system should include
security measures.
To give consumers accurate and current information, the system should interface with other
pertinent systems.

Priority Level: High Due Date: May 16, 2023

Approval: Approved by:

IT Manager:

Project Sponsor: Date:

PROJECT CHARTER PREPARED:

Project Title: Android Local Train Ticketing System

Project Overview:

The goal of this project is to create a local train ticketing system based on Android that allows users
to purchase train tickets using their mobile devices. The system will enable users to search for and
view train schedules, check ticket availability, purchase tickets, view their purchase histories, and
receive real-time updates on the status of their tickets and journeys.

Project Scope:

The system will provide users with real-time updates on the status of their tickets and their journeys.

The system will provide a fast and easy way to refund or exchange tickets if needed.

The system will implement security measures to protect users' personal and payment information.

Project Timeline: Project initiation:

System design: Development:

Testing: Deployment:

Maintenance and support: Ongoing

Project Team:

Project Manager: Systems Analyst:

Developers: Testers:

Deployment and Support: Approval and Sign-Off:

Approved by: Project Sponsor:

Stakeholder:

Project Manager: Date:

 2.2. FEASIBILITY STUDY

A feasibility study evaluates how feasible a proposed system is. It is used to assess the
viability of a project and to spot any potential problems that might occur during
development or implementation.

2.2.1. ECONOMIC FEASIBILITY

This involves evaluating the costs and benefits of the system, including
development costs, maintenance costs, and potential revenue to the organization.

The project costs that would be taken into account in a study of the economic
viability of the system are as follows:

1. Development Costs:
a. Software development costs: $50,000
b. Hardware costs: $5,000
c. Third-party API costs: $2,500
d. Project management and testing costs: $10,000
2. Maintenance Costs:
a. Server hosting costs: $1,500/month
b. Software and hardware upgrades: $5,000/year
c. Customer support costs: $20,000/year
3. Operating Costs:
a. Internet and communication costs: $1,000/month
b. Electricity costs: $500/month
4. Revenue Generation:
a. Ticket sales: $50,000/month
b. Advertising revenue: $5,000/month
c. Other revenue streams: $2,000/month
2.2.2. TANGIBLE BENEFITS

Here are some examples of tangible benefits of an Android local train ticketing
system that could be considered in an economic feasibility study:

1. Increased convenience for users: The system allows users to purchase train
tickets through their mobile devices, increasing convenience and reducing
the need to visit a physical ticket office.
2. Increased revenue for train operators: The system allows for faster and
more secure ticket sales, increasing revenue for train operators.
3. Increased use of public transportation: The system can help increase the
number of people using public transportation by making it more
convenient and efficient to purchase tickets.
4. Reduced labor costs: Automating the ticketing process can reduce the
labor costs associated with staffing physical ticket offices.
5. Increased efficiency: The system can provide real-time updates on ticket
availability and journey status, increasing efficiency and reducing delays.
6. Increased security: The system can implement security measures to protect
users' personal and payment information, reducing the risk of data
breaches or fraud.
7. Increased customer satisfaction: The system can provide a user-friendly
and easy-to-use interface, increasing customer satisfaction.
8. Reduced paper usage: The system can help reduce the amount of paper
used in the ticketing process, which is more environmentally friendly.
 2.2.3. INTANGIBLE BENEFITS

Here are some examples of intangible benefits of the system that could be considered in
an economic feasibility study:

1. Improved brand reputation: The system can help to improve the reputation of the
train operator by providing a more convenient, efficient and modern service to
customers.
2. Increased customer loyalty: The system can increase customer loyalty by
providing a better user experience, which can lead to repeat customers and
increased revenue.
3. Improved decision-making: The system can provide valuable data and insights on
customer behavior, which can be used to improve decision-making and optimize
service offerings.
4. Improved employee satisfaction: The system can automate repetitive tasks and
reduce workload, which can lead to increased employee satisfaction and reduced
turnover.
5. Improved regulatory compliance: The system can help the train operator to
comply with any relevant laws, regulations, and standards, reducing the risk of
penalties or fines.
6. Improved community engagement: The system can help to improve community
engagement by providing a more convenient and efficient service to customers,
and by promoting the use of public transportation
7. Increased flexibility: The system can be easily adapted to changing market
conditions or new business requirements, which can help to increase the
long-term viability of the system.

2.3. FUNCTIONAL REQUIREMENTS

Functional requirements are the particular attributes and capabilities that the
system must possess in order to satisfy users' and stakeholders' needs.

The following functional specifications apply to an Android local train ticketing

system:
1. Search and view train schedules: Users should be able to search for and view train
schedules, including departure and arrival times, train numbers, and ticket
availability.
2. Purchase tickets: Users should be able to purchase tickets quickly and securely
through the use of a mobile-friendly interface and a reliable payment gateway.
3. Real-time updates: Users should receive real-time updates on the status of their
tickets and journeys.
4. Purchase history: Users should be able to view and manage their purchase history.
5. Refund and exchange: Users should be able to easily refund or exchange tickets.
6. Secure payment: The system should implement security measures to protect users'
personal and payment information.
7. User-friendly interface: The system should have a user-friendly and easy-to-use
interface, with minimal steps to purchase a train ticket.
8. Push notifications: Users should receive push notifications for updates, such as
delays or other important information.
9. Offline functionality: The system should be able to work offline if the user has no
internet connectivity, and should allow them to purchase the tickets and check
their journey status.
10. Multi-language support: The system should support multiple languages, to cater to
a diverse user base.
11. QR code scanning: Users should be able to scan QR codes at the station for quick
and easy entry to the train.

2.4. NON-FUNCTIONAL REQUIREMENTS

Non-functional requirements are those that outline a system's qualitative

characteristics, such as its performance, security, and usability. Non-functional needs
for the system include:

1. Performance: There should be no delays or mistakes when handling a large

number of users and transactions.
2. Security: The system must be able to prevent unauthorized access to and theft of
users' personal and payment information.
3. Usability: It should be simple to use, with a user-friendly interface and only a few
steps needed to buy a rail ticket.
4. Scalability: The system must be able to handle an increasing volume of users and
transactions without deteriorating in efficiency.
5. Reliability: There should be no downtime or interruptions to the system's
operation.

2.5. OPERATIONAL FEASIBILITY

Operational feasibility is the analysis of a proposed system's ability to meet the

needs of the users and stakeholders, as well as its ability to integrate with existing
systems and meet regulatory requirements.

The following elements would normally be included in a thorough operational

feasibility analysis for the ticketing system:

1. User Needs: This involves assessing the system's suitability for serving
users' demands, such as offering an intuitive user interface and real-time
updates on ticket availability and route status. These are:
a. User research and testing: $15,000
b. User interface design: $10,000
2. Integration with existing systems: This involves assessing the system's
compatibility with other important systems, such a payment gateway, a
database of railway schedules, and a customer management system. These
cost are:
a. Integration costs: $20,000
b. Testing and validation costs: $10,000
3. Regulatory Compliance: This includes evaluating the system's compliance
with any relevant laws, regulations, and standards, such as Health Insurance
Portability and Accountability Act (HIPAA), the General Data Protection
Regulation (GDPR), and the Payment Card Industry Data Security Standard
(PCI DSS).
a. Compliance assessment: $5,000
b. Compliance monitoring: $3,000/month
4. Training and Support:
a. Training materials development: $5,000
b. Employee training costs: $10,000
c. Support costs: $5,000/month
5. Operational Constraints:
 a. Data storage costs: $1,000/month
b. Security costs: $5,000/month
c. Privacy compliance costs: $3,000/month
6. Adoption rate:
a. User acceptance testing: $5,000
b. Marketing and promotion costs: $10,000
7. Impact on Business Processes:
a. Business process re-engineering costs: $20,000
b. Impact analysis and assessment costs: $5,000
8. Implementation and Deployment:
a. Deployment and implementation costs: $30,000
b. Testing and validation costs: $10,000

2.6. TECHNICAL FEASIBILITY

Technical feasibility is the assessment of how practical it is to implement a proposed

system or project. It is an analysis of the resources required to develop and maintain
the system, the cost of the software and hardware required, and the time it will take
to build the system. Evaluating technical feasibility entails determining the technical
capabilities and resources required to install and operate the system.

Some specific factors to consider when evaluating the technical feasibility include:

1. Hardware requirements: The system must run on the Android platform and will
require devices such as smartphones or tablets with sufficient processing power,
memory, and storage to run the app.
2. Software requirements: To store and retrieve information such as ticketing
information, user profiles, and payment information, the system will require a
database. Software for the user interface, database management, and security
will also be required.
3. Network infrastructure: The system will require a reliable network infrastructure
to support the transmission of data between the app, the database and the
payment gateway.
4. Integration with existing systems:To execute transactions and have access to
user data, the system will need to interact with other systems already in place,
such as the payment gateway.
5. Scalability: An expanding user base, volume of transactions, and data processing
should be accommodated by the system.

2.7. SCHEDULE FEASIBILITY

The term "schedule feasibility" describes a system's capacity to be designed and put
into operation within a given time frame. The time needed to design, build, test, and
deploy the system, as well as the ongoing time needed to maintain and run the
system, are all taken into consideration when evaluating schedule feasibility.

Some specific factors to consider when evaluating the schedule feasibility of the
ticketing system are:

1. Development time: The time required to design, develop, and test the system,
including the time required to integrate the system with existing systems.The
development time for an android local train ticketing system will depend on
several factors, including the complexity of the system, the availability of
resources, and the efficiency of the project management approach.
It's difficult to give an exact time frame for the development of the system
without a clear understanding of the requirements and specific features of the
system. However, a rough estimate can be made based on the following factors:
a. Size and complexity of the system: A simple system with basic features
will take less time to develop than a complex system with multiple features
and integrations.
b. Experience and expertise of the development team: A team with more
experience and expertise in developing android apps and systems will be
able to develop the system in a shorter time frame.
c. Resources availability: The availability of the necessary resources,
including personnel, hardware, and software, will impact the development
time.
d. Development methodology: The development methodology adopted can
have a significant impact on the development time, for example, Agile
methodologies tend to be faster than traditional methodologies.
e. Quality assurance: The time required for quality assurance and testing will
also impact the development time.
2. Deployment time: The time required to implement the system, including the time
required to train personnel, test the system, and roll out the system to users. It
can include several stages such as:
 a. User acceptance testing: This phase would involve testing the system with
a small group of users to ensure that the system meets their needs and is
easy to use.
b. Training: This phase would involve training personnel, including system
administrators and customer support staff, on how to use and maintain the
system.
c. Deployment: This phase would involve installing the system on the
necessary devices, such as smartphones or tablets, and making it
available to users.
d. Go-live support: This phase would involve providing support to users
during the initial launch of the system, addressing any issues that arise
and providing assistance with system usage.
e. Monitoring and maintenance: This phase would involve monitoring the
system to ensure that it is operating as expected and making any
necessary updates or changes.
3. Maintenance and updates: The time required to maintain and update the system
to fix bugs, improve performance, and add new features. Some specific factors to
consider when evaluating maintenance and updates include:
a. Bug fixes: The time required to fix bugs that are discovered after the
system is deployed.
b. Performance improvements: The time required to make performance
improvements to the system, such as optimizing database queries or
reducing load times.
c. Adding new features: The time required to add new features to the
system, such as new payment methods or user account management
features.
d. Security updates: The time required to implement security updates and
patches to protect the system from potential vulnerabilities.
e. Compliance: The time required to ensure that the system remains
compliant with data privacy and protection laws
4. Resources availability: The availability of the necessary resources, including
personnel, hardware, and software, to design, develop, and implement the
system. Some of those resources include:
a. Personnel: The availability of personnel with the necessary skills and
experience to design, develop, and maintain the system, such as android
developers, system administrators, and customer support staff.
b. Hardware: The availability of necessary hardware, such as servers,
smartphones, or tablets, to host and run the system.
 c. Software: The availability of necessary software, such as development
tools, databases, and operating systems, to design and develop the
system.
d. Budget: The budget allocated for the project, including the cost of
necessary hardware, software, and personnel, will impact the resources
availability.
5. Dependencies: The dependency of the project on other systems or projects,
which can impact the schedule. Some of the dependencies that could be
considered when developing an android local train ticketing system include:
a. Network connectivity: The system may rely on a stable and reliable
internet connection in order to function properly.
b. Third-party services: The system may rely on third-party services, such as
payment gateway providers or map APIs, in order to provide certain
features or functionality.
c. Backend systems: The system may rely on backend systems, such as a
database or a ticket reservation system, in order to provide up-to-date
information and process transactions.
d. Hardware compatibility: The system may require specific types of
hardware, such as smartphones or tablets, in order to function properly.
e. Software compatibility: The system may require specific software, such as
a particular version of Android, in order to function properly.
6. Project management: The effectiveness of the project management approach,
which can impact the schedule.Some specific tasks that a project management
approach may include are:
a. Defining project scope and objectives: This will involve defining the
requirements and features of the system and setting clear goals for the
project.
b. Establishing a project plan: This will involve creating a detailed plan for the
development, deployment, and maintenance of the system, including
timelines and resource allocation.
c. Managing the project team: This will involve managing the personnel
working on the project, including developers, system administrators, and
customer support staff.
d. Tracking progress and performance: This will involve monitoring the
progress of the project and identifying and addressing any issues or
delays that arise.
e. Managing risks: This will involve identifying potential risks to the project
and implementing measures to mitigate them.
 f. Communicating with stakeholders: This will involve keeping stakeholders,
such as customers and clients, informed of the progress and status of the
project.
g. Managing budget and resources: This will involve managing the budget
and resources allocated for the project and ensuring that they are used
efficiently and effectively.
h. Quality assurance: This will involve ensuring that the system meets the
necessary quality standards and ensuring that it is free of bugs and errors
before deployment.

2.7.1. PRELIMINARY SCHEDULE

A preliminary schedule for the train ticketing system would include the major
milestones and tasks that need to be completed during the development and
implementation of the system. The schedule would likely include the following
phases:

1. Planning: This phase would involve gathering requirements, analyzing

the current system, and developing a project plan.

2. Design: This phase would involve designing the system, including the
user interface and database design.

3. Development: This phase would involve developing the system, including

the app, database, and integration with other systems.

4. Testing: This phase would involve testing the system, including functional
testing

2.7.2. ACTIVITY TABLE

2.7.3. GANTT CHART

2.7.4. NETWORK DIAGRAM

2.7.5. PROGRAM EVALUATION REVIEW TECHNIQUE

2.7.6. RISK

2.8. PROJECT SCOPE STATEMENT

2.9. BASELINE PROJECT PLAN REPORT

3.0. USE CASE DIAGRAM

3.1. DATA FLOW DIAGRAM (DFD)