Hang tight while we fetch the video data and transcripts. This only takes a moment.
Connecting to YouTube player…
Fetching transcript data…
We’ll display the transcript, summary, and all view options as soon as everything loads.
Next steps
Loading transcript tools…
BCS1033 Software Engineering Project | BusOnlineTicket.com | Incremental Development Model | MUHAMMAD IRSYAD ILHAM BIN SHAIFUL BAHARIN | YouTubeToText
YouTube Transcript: BCS1033 Software Engineering Project | BusOnlineTicket.com | Incremental Development Model
Skip watching entire videos - get the full transcript, search for keywords, and copy with one click.
Share:
Video Transcript
Video Summary
Summary
Core Theme
This case study presents the development of "Bus Online Ticket.com," a web-based platform designed to offer a convenient, user-friendly, and affordable online bus ticketing experience in Malaysia, emphasizing software engineering principles and an incremental development model.
Mind Map
Click to expand
Click to explore the full interactive mind map • Zoom, pan, and navigate
Uh
today I'm going to present about our
case study which is uh our website is
pass online ticket.com. Um
without without further ado I'm going uh
introduce myself as a project manager
which is mama and these are my fellow
teams. First uh I'm going to begin with
our system analyst which is Aisha alumi
and then uh the other one is uh Mohammed
Ishad bin
this our this is our programmer and also
the third one is uh our tester which is time
all right I'm going to begin by our
details about our case study the name of
our website is bus online ticket and it
is founded during 2006. The type of
website is web based online bus
ticketing platform. This website is
based in Malaysia. As as you can see
here is this is our uh main interface
website. The key features that I'm going
to highlight during this presentation is
uh search bus routes, compare ticket
prices, view departure schedules, select
seats, make sure online payments and
also receive electronic ticket
confirmation. With these uh key
features, it helps uh travelers to
travel more convenient and also makes
them uh easier for them to view their
schedule uh and also pricing about the
This is our main interface where people
uh select their routes and also
departure time.
And this is the login interface.
And this is also the sign up office.
Uh we we already uh list out six of our
objectives for the websites which is
enable convenient online booking
tickets, provide multiple travel, ensure
user friendly, offer exclusive deals,
reduce skills and improve travel
planning and also make travel hasslefree
and also affordable. Next the first one
is enable convenient booking. Uh what I
mean by enable convenient booking is uh
allows booking from everywhere and
anywhere. Next uh the third one is
provide multiple travel options. Uh what
does it mean by provide multiple travel
option is by providing uh different type
of operator like as you can see here.
Next, the third one is ensure user
friendly and also accessible experience.
What I mean by user friendly is uh
people get user gets to choose their
type of language they want to see on
their website
and also offer deals
uh discounts and also loyalty programs.
And this is these are the example of our
discount deals and also loyalty programs.
programs. Next
Next
uh the fifth one is reduce skills and
also improve travel comfort. What we
what we meant by reduce and improve
travel comfort is by travelers gets to
choose their seat according to their uh preference.
preference.
The sixth one is our make travel hassle.
The sixth objective is make travel
hazard free and also affordable. What we
meant by affordable is that travelers or
users get to choose their own price and
their own
operators according to their budget and preference.
preference.
Okay. First search and road information
service. Our service offer uh our
service offer a ticket search and root
information service. Users can search
for a bus, bus, ferry and train uh by
choosing the departure time,
destination, travel date and number of
passengers. The system then shows real
uh shows travel time, duration and
ticket prices so users can compare
option and plan their journey easily.
Next, real time seat availability. Our
system also shows realtime seat availability.
availability.
Users can see which seats are available
and choose their preferred seat which
help prevent over. After selecting the route
route
and seats, user can book their ticket
online without going to a physical
counter and they will receive the
confirmation immediately. Next, this is
the online ticket. So, no need to go to
physical counter. Next for secure
payment they offer multiple payment
method which is online banking, credit
card, debit card, wallet and more. Next
so booking management service. Booking
management service uh we also provide
view booking history. So users can
manage existing reservation or they can
ask for ref refine if they want uh back
based on operator policies. Next uh
customer service, customer support and
information service. Our website also
provide customer support service such as
frequently asked questions, contact form
and customer service channel. So these
features help users solve booking or
payment problem and improve overall user satisfaction.
satisfaction.
Uh basically we are going to explain why
software engineering is important to uh
develop our website. So um we use
software engineering because software
engineering provides um a systematic
approach to develop and to maintain the
website. Um it also ensures um important
quality attributes such as
maintainability, dependability,
efficiency and usability. The next one,
it helps the system remain secure, user
friendly and also makes it easier for
online transactions. The last one is
that um
it considers um oh I'm sorry the last
one it improves productivity through
>> Okay. uh for the software process model
chosen from this project is increment
incremental software development model.
So next okay for the spec specification
ensure flexibility and clear system
objective uh for the fibility techn
technically physible cost effective user
user ready ID requirement online booking
seat management payment confirmation for
the specification input process output
document and update each increment for
validation review to ensure requirement
meet schedule needs and for the design
and imple implementation convert
specification into working software
incrementally. So for the architecture
we choose a layer architecture. So for
the daily architecture present
presentation application data uh for
interface user friendly responsibility
multi- general for component modular
feature like search booking payment
account for database secure and storage
for user booking payment. So next
uh for validation and verification
ensure the system work correctly uh
before each release. So component
testing, individual module test, system
testing, full booking process tested,
exception testing, user and schedule
approval for evaluation, continuous
improvement after deployment,
business change, new operation and
service, new technologies, update,
payment and security system. So does
platform change support new device and browser?
browser?
>> Okay, while developing our website there
are three deliverables um that are
important. The first one is
specification. Basically for the
specification it defines um the system
requirements for each increment for each
increment through documented and
feasible requirements before development
begins. And the next one is development.
In this deliverable um we basically
translates the requirement into an
executable system covering both design
and implementation. The last one is
validation. For the validation we
basically just um check whether the
newly developed increment matches the
specification and meets the user needs.
Okay. This uh slide show the 12week
project schedule of uh busonline.com
using the incremental development model.
So the project is divided into several
phases which is starting with planning
and design and then followed by the
development in stages testing user
acceptance testing and finally system
deployment. So this schedule helps the
team to stay organized and complete the
project in time.
>> Uh all right I'm going to talk about
four main things which is problem
overview impact on project relationship
to incremental development model and
also mitigation strategies. This is
about in topic incomplete knowledge
transfer. The first one is problem of
view. problem of view is uh our problem
of view is knowledge transfer between
development increments may be
incomplete. The second one is uh impact
on project addition uh the impact on
project is additional time spent reverse
engineering existing code. Uh and the
third one is relation to incremental
development model. uh incremental uh
development model uh strength is
flexibility and also early delivery of
working software and our weak uh and
weakness is if handover is body manage
benefits of incremental delivery reduce.
Uh the fourth one is mitigation
strategies. Our mitigation strategies is
enforce standard standardized
documentation for each increment. uh
conduct formal handover meetings and
also record design uh decision and also
assumptions early.
Uh as a system analyst one medal
handover problem is unclear or
incomplete requirements for this happen
when requirements are not explained
clearly or important details are
missing. For example, dur the
requirement users can only search for
tickets but may mean searching across
all operator but developer might
understand it as searching within only
one operator. So next
the impact on incremental development uh
there may be error in early increment
where it will excite the later stages.
So it can uh it can be project delay,
rework and high cost or user is dissatisfaction.
dissatisfaction.
Uh main issue is uh inconsistent in
system interface API contract between
contract between improvement. For the
example year increasement may include
working selection and payment module
where later increasement introduced
feature such as promotion loyalty
program or new payment gateway. If API
then API data structure are changed
without proper communation or docu
document mutation.
This issue increase debug time cause rework
rework
and slow down development to maint
programmer should enforce strict
interface specification. FBI
versian maintain up to date techn
technical document and conduct regular
technical review.
>> My perspective as um as the our handover
problem is that receiving new system
equipment without proper updates. So
basically um if the if the developers do
not clearly hand the updated environment
details tester may attempt to use new
feature on
using the outdated uh configurations. So
this handover problem could also cause
in delay testing for for for
us. Basically developers also may waste
time trying to reconigure reconigure the configuration
configuration
error. Tester also will be unable to
verify the new increments. And the last
one um we as a tester I come with um
solution. Um basically in order to
overcome this problem developers should
provide clear and updated documentation
The system architecture model that we
chose is the layered architecture
pattern because it is suitable for a
large scale web- based um bus online bus
ticketing system. So this is the block
diagram that we have made next.
Okay. Why we choose um layer
architecture pattern? We chose this um
architecture pattern because the first
reason is clear separation. Um
Um
in this case it allows changes to be
made in one layer um without affecting
the entire system which which improves
the maintenability and reduce the risk
of error. The next one is support
scalability and team based development.
system will be able to handle high user
traffic while enabling different teams
to um work on the per to work on
enhancing the performance or feature
without disrupting the existing
fundamental fun oh I'm sorry without um
first I'm going to begin with the
benefits as a project manage manager the benefits
benefits
uh improve communication with
stakeholder and also uh more accurate
risk management. Um
what I meant by improves communication
is engage user early to get feedback on
ticket search booking and also payments.
Uh besides that uh it's also clarifies
user expectation and align features with
stakeholders needs. Uh the second one is
more accurate risk management. Uh use
more accurate risk management is user
help to support to spot functional
usability or security issues early for
example like payment errors. Uh it
corrects availability and also unclear
messages. Uh besides that uh early
identification allow fix allow fixes in
upcoming increment and also ensure high
quality final system.
Next is disadvantages
about the early user testing. Uh as a
project manager risk the dis the
advantage the the disadvantage
is risk of exposing confidential
information. Uh what I mean by risk of
exposing confidential information is
early testing may reveal personal data
of user such as booking history and also
payment. Besides that it also can cause
breaches or legal issues. Um besides
that our m our mitigation is to control
access anonymize uh test data and also
authorize testers only.
>> So early user involvement in release
testing is very important as my role as
system. So the benefits we got it helps
make sure the system meets real user
needs uh by finding missing features or
usability problem early. Uh second we
can improve user acceptance and
satisfaction because user can give
feedback on things like booking flow
payment process or timetable display.
However, the disadvantage
uh it's it when this one disadvantage
that it it takes more time and effort to
organize testing testing session and an
analyze feedback which can increase
project cost if we not manage it properly.
properly.
>> Okay. From the programmer's perspective,
read user help reporting and logic error
such as incorrect fail population see available
available
or booking failure after payment.
Uh this issue may not be detecting
during internal testing. Daily feedback
allow programmer to fix problem before
full de deployment. Uh next user
involvement also help evaluate system
for performance under real usage
condition improvement system stability
and re realability especially during
peak working period. Uh however one
disadvantage is that user may have limit
technical understanding. Their feedback
can be subjective requirement additional
time for programmer to analyze and
identify the actual system defect.
All right. Right now we are going to
talk about the
benefits of early user involvement in
release testing in my perspective as a
tester. The first one is it ensures the
system meets actual user requirement and
the second one is it increases
um confidence in usability and
readiness. Um
which means um early user testing helps
identify user usability and performance
issues. Um
for the disadvantage is that additional
effort may be required to manage and
interpret user feedback. That's all from
Click on any text or timestamp to jump to that moment in the video
Share:
Most transcripts ready in under 5 seconds
One-Click Copy125+ LanguagesSearch ContentJump to Timestamps
Paste YouTube URL
Enter any YouTube video link to get the full transcript
Transcript Extraction Form
Most transcripts ready in under 5 seconds
Get Our Chrome Extension
Get transcripts instantly without leaving YouTube. Install our Chrome extension for one-click access to any video's transcript directly on the watch page.
