Web Application Development Process

No Comments

PoLR employ a simple but effective development process for web application development.

Stage 1: Requirements Gathering
The initial stage is requirements gathering which may involve:

  1. Discussion with clients to distinguish between needs and desires
  2. Investigation of applicable laws and standards
  3. Analysis of existing systems for replacement or integration
  4. Interviews with key stakeholders such as management and the employees who will use the system
  5. Observation of existing business processes

The main deliverable of the requirements gathering stage is a System Requirements Specification (SRS) document which is based on the IEEE 830 standard. In short the SRS details the functions the web application should provide and any constraints such as specific software components it should use.

The SRS will be delivered along with a schedule of cost and time estimations for the project.

Stage 2: Iterations
Depending on the scale and complexity of the individual web application a number of iterations will be devised. An iteration is a set of steps that produce a partial working functionality specified in the SRS. A typical iteration would involve:

  1. Architecture: A design of how the specific part of the application will function and integrate with the system as a whole.
  2. Test Specification: All tests required to validate the functionality within the iteration will be defined.
  3. Implementation: Creation of relevant software modules, database elements and integration with existing software elements.
  4. Testing: The test specifications will be used to test the implementation to ensure it is functionally correct.

Stage 3: Testing
When iterations are complete the software as a whole is tested both at the module level and as a complete system. With web applications it is typical to simulate users carrying out common tasks to ensure that the system functions as expected.

Stage 4 Delivery & Training
Delivery of web applications most often involves sourcing suitable hosting, installation and a repeat of testing procedures to ensure that the hosting environment has not introduced any unexpected behaviours due to changes in system configuration. PoLR can advise on hosting requirements and providers from very simple shared hosting to complex load balanced clusters for large applications.

Together with the working application installed and functioning PoLR will supply a backup of all software, databases and materials on permanent media.

PoLR can provide training and manuals on the use of web applications from day to day tasks to how to perform backups.

Stage 5: Maintenance
Depending upon the specific project the amount of maintenance advised can vary significantly. However, most clients are advised to schedule maintenance time for the first three months after delivery.

What is scheduled maintenance time? In short, we schedule a set number of hours per month specifically for your applications maintenance and will rearrange daily schedules where possible. This ensures that we can respond to issues promptly.

Unscheduled maintenance can not receive the same level of priority due to the number of development projects managed. However, we are proactive in managing all maintenance requests and tracking waiting times.

Types of Maintenance
There are three main types of maintenance: corrective, adaptive and perfective.

Corrective maintenance is when a bug or malfunction is discovered in the software after delivery and must be fixed. This is perhaps what most individuals think of as maintenance.

Adaptive maintenance is when an application must be partially re-engineered due to changes in your business environment. A typical example would be wishing to expand payment processing options to include a new system or integration with new stock control systems.

Perfective maintenance is often requested by clients after a medium period of using their application and usually involves changing the flow of existing modules are the addition of new modules to make the system easier to use or more maintainable. Typical examples include realising that a common task requires entering on screen to check some details then entering them manually in another screen, perfective maintenance would be changing the application to remove the need to navigate multiple screens for the common task.

PoLR are committed to the ongoing maintenance and development of delivered applications and can help grow your software with your company.

This is author biographical info, that can be used to tell more about you, your iterests, background and experience. You can change it on Admin > Users > Your Profile > Biographical Info page."

About us and this blog

We are a digital marketing company with a focus on helping our customers achieve great results across several key areas.

Request a free quote

We offer professional SEO services that help websites increase their organic search score drastically in order to compete for the highest rankings even when it comes to highly competitive keywords.

Subscribe to our newsletter!

Fields marked with an * are required

More from our blog

See all posts