Users Requirements Statement specifies the work that will be performed, completion deadlines, cost structure and additional terms. Every part of Users Requirements Statement describes the application or the development process from a different angle and every part of it, including input/output model, is just a written description of either certain aspect of the application or the development process.
For the optimum outcome, the project development stages and steps can and should be modified in accordance with the project's nature. Similarly, Users Requirements Statement's parts can be modified, so that it is in accordance with the project's nature.
Most Users Requirements Statements specify the following application development aspects:
| • | Application's Purpose and Description - description of what the application is about and what it has to accomplish and description of all the application's parts as they relate to subject matters and information flow elements |
| • | Subject Matters and Information Flow Elements - information entities that the application will track and their characteristics, and parts of the application that will be used for that purpose (forms and reports) and these parts' characteristics |
| • | Input/Output Model - specifies what information will be entered and what results should be displayed |
| • | Business Rules - specifications and limitations that apply to input/output model |
| • | Additional Development - information about possible additional development or additional services provided |
| • | Definitions - explanation of terms used |
| • | Cost Structure - agreement on pricing and billing structure and how much and when will be paid for the work performed |
| • | Timetable - description of project-related mutually acceptable time frame |
| • | Additional information pertaining to application's development process - contact information, agreement's acceptance information and additional terms |
This company's representative puts the Users Requirements Statement together during the application development Analysis Stage's Contract Development Process sub-stage, after gathering sufficient information for this purpose. Users Requirements Statement will also form a contract between the customer and this company.
Even if the application is simple, we prefer to use a written document that specifies the work that will be performed and the development process' details, and is signed by both the customer and this company's representative before and after the application production process. Signing this document before the application production process indicates that we have agreed on what needs to be delivered. Signing this document after the application production process indicates that this company has delivered precisely what we did agree to do.
This approach increases efficiency by helping to verify that all the necessary elements have been developed and that all the elements that were developed do indeed belong into the project. It also helps to minimize the probability of having misunderstandings or disagreements between the developer and the customer about the application after it has been built.
After testing and usage the application users may find additional features that should be added to the application, and modifications and changes that should be made. Minor modifications can often be handled without cost overruns. (Our project planning and management structure allocates development time for that purpose.)
If the modifications are not so minor and additional cost is acceptable to the customer, any additional features, modifications and changes needed can be added to the application's current version. Otherwise, any additional features, modifications and changes can be added to the application's next, updated version. That is, applications can, and often should be, developed in versions, so that each version is fully usable, but builds on the previous work. In such case each version should have its own Users Requirements Statement.
We do a very thorough and detailed users needs and wants analysis and verify the results with the users before we start building the application. This approach helps to minimize the need for making changes to an already signed Users Requirements Statement. If changes need to be made, the Users Requirements Statement's new version should be signed again by this company's and the customer's representatives.
You can download an example of a Users Requirements Statement as a PDF file from here. If you are an application developer and would like to use this file as a template for creating your own similar document, feel free to do so. (Per request, if you submit an inquiry, we can also send out the same document as a MS Word file, so that you can use it as a template for creating your own similar document.)
Legal Disclaimer: Please note that, depending on the nature of the contract and your location, you may need to consult with an attorney for putting together your own contract, just like you would need to do so for putting together any other type of legal document. Project Developer, Inc. will not assume any responsibility whatsoever for your usage of this or any other material or information obtained from this website or in any other way or manner from Project Developer, Inc.
