1.1 Gantt Chart
One of the
top used methods for monitoring web projects is the utilization of a Gantt
chart. A Gantt chart frames all larger-scale procedures and additionally the
tasks linked with each activity as well as dates of beginning and end. The
Gantt chart acts as a visual note, illustrating the timeframes of each stage
and the connections between these stages.
and Site Architecture
architecture consists of the sitemap and the page wireframes. The generation of
a sitemap guarantees that all the main website pages have been taken into
account, illustrating their connection with each other and determining the
sites general navigation arrangement. Wireframes offer a thorough outlook of
the content that will be shown on each page. Despite the fact that wireframes
don’t illustrate any design aspects, they offer a guide for determining the
content structure appearing on the page. This results of these processes will
be used during the production of application initial prototype, prepared in
Graphic aspects that have been designed during the earlier
stage should be used for building the actual website. The homepage is developed
first and then all the other pages, based on the website structure created
earlier as a sitemap. All of the planned elements that were designed in previous
phases should be added accordingly and then checked. Next, required
functionality, interactivity and other features of the application should be
incorporated and entire system carefully tested.
The Prototyping Model is used to describe a Systems
Development Method (SDM) that involves building a prototype (a close
representation of what a final product would look like). This prototype goes
through series of tests and modifications till all parties are satisfied with
it and this prototype can now serve as the basis for the development of the
final product. This model is ideal for scenarios where some of the project
requirements are unknown ahead of time. It is usually a trial-and-error process
that occurs between the developers and the users.
The steps involved in the Prototyping Model include:
The new system requirements are spelled out in
clear detail, as it often involves interviewing users who represent every
aspect of the existing system.
The programmer come up with a preliminary design
for the new system
The preliminary design is used to create the
first prototype of the new system. The system is usually scaled-down and
possesses the qualities of the expected final product.
The users are allowed to evaluate the first
prototype, identifying its weaknesses, strengths, as well as what can be
improved upon. The programmer collates and analyses the feedback from the
Based on users’ feedback, the first prototype is
modified, and the programmer comes up with a upgraded prototype of the new
The second prototype goes through the same
evaluation path as the first prototype.
There’s iteration of the preceding steps several
times until the users are convinced that the prototype is an ideal
representation of the expected final product.
The final system or product is created, based on
the final prototype.
The final product then goes through thorough
evaluation and testing. Also, routine maintenance is done periodically to avert
monumental failures and to reduce downtime.
the website is crucial as there may be problems that need to be tackled prior
the website goes live. The role of the testing is to make sure that everything
runs smoothly, there are no mistakes and broken code or elements. During this
phase, the website should be checked on various web browsers (i.e. Google Chrome,
Safari, Firefox) and on different devices (i.e. laptops, smartphones, tablets)
to check whether breaks and mistakes appear.
types of test for various aspects of the application should be performed:
This is done to check if the product conforms to the
characteristics and specifications spelled out in your developmental
2.2.2 Usability Testing
Usability testing is now a critical aspect of any web-based
project. The test can be done by testers or a small target group similar to the
web application’s target audience.
The three focus areas here are: Web Server, Application and
Application – test requests are accurately
sent to the database and output is shown correctly at the client side. If there
are any errors, they are captured and shown only to the administrator, not the
Web Server – test web server handles every
application request in real time without any service denial.
Database Server – ensuring that all queries
sent to the database return the expected outcome.
The importance of database to any web application cannot be
overemphasized, and it must be subjected to thorough testing.
Compatibility tests are done to ensure that web application is
shown correctly across a range of devices.
This is to ensure that the application is at optimum performance
level under all loads.
2.2.7 Security Testing
For a website that handles sensitive information, security testing
is highly crucial.
The final step is to perform an evaluation to determine the extent
to which the project was successful and record any lessons learned for future
projects. Evaluation allows to identify the level of success of the project by
reviewing its execution to determine whether the project delivered the
benefits, met the requirements and produced the deliverables on time.
Because Prototyping Model has been selected as system
development method for this project, mix of two different types of evaluation
will take place.
Formative Evaluation – this evaluation takes
place during the project to direct further development.
Summative Evaluation – this evaluation takes
place after realisation of a project to assess its success.