Opposition Report for Fast Point

Tracking System
Project by
Alina Hassan,
Urooj Anwar,
Anjiya Nawaz Nathani
Aiman

Report by
Talha Malik 16K-3694
Minhaj Siddiqui K16-3657
Issam Ahmed K16-3654
Haamiz Ahmed K16-3653
Varisha Jabbar K16-3663

Software Engineering, FAST-NUCES

May 6, 2019

Page | 1
This report aims to identify some loopholes in project process of FAST POINT
TRACKING SYSTEM developed by our fellow classmates. Note that most of the
oppositions and corrections are a matter of personal opinion yet provided with the
justifications. They are by no means absolutes.

The Methodology
Methodologies such as agile software development promises increased user
satisfaction, lower error rates, faster development times, and a solution to rapidly
changing requirements. Whereas, Plan-driven approaches or methods promise
stability and high confirmation.
However, both agile and plan-driven approaches have situation-subordinate
shortcomings that, if left unaddressed, can prompt to project failure.
Hence, the challenge is to pick the most suitable strategy between these two ways
to take advantage of their strengths in a given situation while making up for their
exploited shortcomings.

Applied to the "FAST Point Tracking System", they have utilized plan-driven
methodologies, whereas we recommend the Agile Approach to extend the
undertaking’s needs because Plan Driven Approach cannot cater the change in
requirements. Whereas, Agile Project planning saves overheads such as detailed
plan and minimal documentation etc.
Also because, Agile focuses more on its stakeholders’ interests.

DB blocking (I/O blocking)

The FAST Point Tracking System is developed using RAW PHP. Though raw PHP
has its obvious advantages that is they have full control over styling and making
components in their own way, however advantages of using PHP frameworks
overshadows this and are therefore a better option to use when dealing with
development in php.

Framework introduces an extra layer to wrap your business code which in turn provides
better manageability and easily workability in teams. It gives you some tools and
function to make it easier for yourself and usually have security classes in the core. With
raw php you need to write lots of code that may already be written and there is more to
consider about, like security (SQL Injection, XSS), organization of code, separation of
business logic, view etc. Moreover, Database blocking(I/O blocking has been used) in
this project.

A better approach would have been MongoDB (non relational DB)

The Architecture
They have used client-server architecture system, client-server architecture is a computing
model in which the server hosts, delivers and manages most of the resources and services
to be consumed by the client. This type of architecture has one or more client computers
connected to a central server over a network or internet connection. This system shares
computing resources.

Page | 2
The main drawbacks of using client-server architecture are:

 Overloaded Servers:

When there are frequent simultaneous client requests, server severely get overloaded,
forming traffic congestion.

 Impact of Centralized Architecture:

Since it is centralized, if a critical server failed, client requests are not accomplished.
Therefore, client-server lacks the robustness of a good network.

As we suggest them earlier to use PHP frameworks (laravel) they should use MVC
architecture in which there is separate presentation of each class as model
component manages data, view component defines how data is displayed to user
and controller components manages user interaction and pass the interaction to
other components the main advantage of this architecture is it supports the
presentation of the same data in different ways thus leading to a good and
manageable software.

Test Cases
They have used traditional scripted test cases approach in which they designed the
component and script the test case and then use these test cases as input to see
and to compare the functionality generated outcome with the actual outcome.

They could have used exploratory testing as it is type of testing in which test cases
are not created in advance but the tester creates test case and check the system on
the fly. It totally depends on personal freedom and responsibility of the tester and
with experience the creativity of the tester allows him/her to generate good test
cases to run on the system.

Miscellaneous Drawbacks
Driver profile is incomplete.

They haven’t included a reservation system.

General Review
Some plus points about this FAST Point Tracking System is that they have developed
an aesthetically pleasing interactive GUI which is easy to use and very responsive. This
makes it easier for users to track the point.

In addition to this their admin, passenger and point driver are independent of each
other adding better manageability in coding!

Page | 3