Requirement Specifications
A requirements specification is a detailed document that outlines Kiandra's understanding, in writing, of a client's current and/or target system. It is typically used as a precursor to the Kiandra development phase, however we can also prepare a requirements specification to enable a client to take the development stage to tender.
The requirements specification document states in precise and explicit language those functions and capabilities a software system must provide, as well as stating any required constraints by which the system must abide.
The requirements specification functions as a blueprint for completing a project with as little (and ideally no) cost growth as possible.
Martin Cooperwaite, Director - Software Development
How Kiandra delivers
Kiandra's requirement specifications accomplish four goals:
- They provide feedback to the client. A requirements specification is the client's assurance that Kiandra understands the issues or problems to be solved and the software behaviour necessary to address those problems.
- They also decompose the problem into component parts. It organises information, places borders around problems, solidifies ideas, and helps break down problems into their component parts in an orderly fashion.
- Kiandra's requirements specifications serve as an input to the design. Therefore, the requirements specification must contain sufficient detail in the functional system requirements so that a solution can be devised.
- It serves as a product validation check. The requirements specification also serves as the parent document for testing and validation strategies that will be applied to the requirements for verification.
The requirements specification is as much a part of the software build as the programming itself.
Software development companies that jump too early into programming without proper requirements specifications and other supporting documentation will almost always build a product which is poorly matched to the client, is delivered potentially overtime (and therefore rushed, poorly tested and 'buggy') and also over budget.
Therefore it is important to view the requirements specification as a core part of the software project, and not an optional and extravagant item that can be skipped. The cost of a requirements specification is directly related to the following:
- How complex your solution is
- How defined your processes are
- How well you have identified the problems you wish to address
Once a requirements specification is complete, Kiandra will be able to provide a fixed price quotation for the project build components.
Experience and certifications
Kiandra has been awarded the Microsoft Partner of the Year 2012 for our software, web, and requirement specification skill, design and quality.
Kiandra's requirements specification team are highly skilled and experienced in business analysis, articulation of business processes and working with clients directly to determine appropriate solutions. We have been engaged by a range of organisations from the Victorian Government through to small businesses to develop requirements specifications. Our industry development certifications combined with our business process management experience ensure you set your solution along the correct path right from the start.