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 prepare a requirements specification
to enabling 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. Fundamentally, the requirements specification functions as a blueprint for completing a project with as little (and ideally no) cost growth as possible.
How Kiandra delivers requirements & functional specifications
Kiandra's requirements specifications accomplish four goals:
They provides 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 decomposes 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 – none of which is good for the client or the development company.
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.
Requirements & functional specification experience and certifications
Kiandra has been awarded the Microsoft Worldwide Partner of the Year
2009 for our software, web, and requirement specification skill, design and quality. Kiandra's requirements specification team are highly skilled and
experienced with business analysis, articulation of business processes
and working with clients directly to determine appropriate solutions.
We have been engaged by everyone from the Victorian Government through
to small businesses to develop requirements specifications as
required. Our industry development certifications combine with our
business process management experience to ensure you set your solution
along the correct path right from the start. All have had satisfactory
state and federal police checks – National Names Check and/or Police
and Fingerprint Search (Australian).