Software Requirements Specification

A Software Requirements Specification (SRS) is a complete description of the behavior of the system to be developed. Based on the prototype (wireframes), feedback, launch strategy and discussions between our clients and project manager, this document describes deliverables and all tasks that will be performed throughout the project.

End of Project – Sign Off

This document will serve as the reference point throughout the project to ensure all parties are clear on the scope during each phase and especially as the project nears completion. Both the client and the project manager should declare a project successfully completed.

To achieve this, a formal document that specifies the project goals from a functional as well as a non-functional perspective is created. The absence of this document would make it difficult to define the scope, expectations and other important details; ultimately, this would lead to neither party being satisfied with the final product.

Functional Requirements

The functional requirements are developed by incorporating a set of use cases that describe the collective interactions users will have with the website. Use cases are also known as functional requirements.

Non Functional Requirements

In addition to use cases, the SRS also contains nonfunctional (or supplementary) requirements. Non-functional requirements impose constraints on the design or implementation (such as performance engineering requirements, quality standards or design constraints).

Technical Specification

The final step in the website planning phase is when the project manager and the lead developer meet to decide what software tools will be used to create what is defined by the functional and non-functional requirements.

Decision Process

The decision process is mainly influenced by the overall budget as well as budget restrictions that are defined during the launch strategy.

Choices

Important choices will need to be made in terms of what programming language and framework to choose, the database design’s appearance, hosting efforts and other decisions.