DSS Services for Clients
Definition of Your Requirements
Building a website or database without a definition of requirements is like building a house without blueprints.
In the end, you may indeed get a house, but the odds of your getting the house you'd envisioned are slim to none...
What Are "Requirements"?
In software development projects, "requirements"* consist of whatever documentation is necessary for a client to fully communicate what they want from the final product. Developers rely on this communication to define their development objectives.
Requirements can consist of:
- Mockups of prospective web pages or screen displays
- Your logo and other desired graphics
- Marketing copy and other desired content
- Flowcharts defining your related business processes
- Flowcharts indicating your preferred user navigation
- Anything else that clearly communicates to the developer the look, feel, and functionality of the website or database to be developed.
* In a building-construction project, this information would be called "specifications". In software development projects, requirements are sometimes referred to as "technical specifications".
Why Are Requirements So Important?
Building a website or database without a written definition of requirements is like building a house without blueprints.
In the end, you may indeed get a house, but the odds of your getting the house you'd envisioned are slim to none...
Defining and clearly communicating your product requirements is the most critical step in the development of any software product. Unfortunately, it is rarely given the attention and allocation of resources required to perform this step properly.
Too often neither the client nor the developer is fully aware that the lack of a clear definition of requirements guarantees — for both parties — budget overruns, project delays, highly-stressed staff, and at best, the creation of a mediocre product.
The truth is that developers create their solutions based on their understanding of their clients' needs, an understanding that often involves too few facts and way too many assumptions. The best developers are well aware of this pitfall and are wise enough to put the onus on the client to fully communicate their needs before development begins.
Beware the developer who doesn't have this professional maturity and begins to build your solution right out of the starting gate. If this occurs, I advise you to stop the project immediately and seriously consider moving on to a more seasoned professional.
Who's Responsible for Defining Your Requirements?
Since only the client knows what their website or database needs to accomplish,
the responsibility for defining requirements falls primarily on the client.
A seasoned developer will be skilled at extracting requirements from their clients, but a
wise client takes their communication responsibility in this regard very seriously.
That said, taking on this responsibility creates a huge problem for most small businesses because they rarely have the expertise in-house to do this effort justice.
Since only the client knows what their website or database needs to accomplish,
the responsibility for defining requirements falls primarily on the client.
A seasoned developer will be skilled at extracting requirements from their clients, but a
wise client takes their communication responsibility in this regard very seriously.
That said, taking on this responsibility creates a huge problem for most small businesses because they rarely have the expertise in-house to do this effort justice.
The end result is that most small business clients perceive the task of defining requirements as overwhelming because it requires extra time, personnel, and money they generally hadn't budgeted for. In some cases, unfortunately, the unexpected burden of defining detailed requirements forces the client to abandon the project altogether.
Don't allow this concern to sabotage your project...
Don't allow this concern to sabotage your project...
Who Can Help?
Development Support Services. I specialize in helping my small business clients define — and permanently document — their system requirements, business processes and other related information. I have done this type of work for 30 years, and the documentation methods I've developed are focused on communicating an abundance of information in as succinct a manner as possible. Since, when it comes to technical communication, a picture is worth far more than a thousand words, I utilize flowcharts and other diagramming tools like the ones shown below. Using this method allows me to convey a vast amount of technical information in the most time-efficient and cost-effective manner possible. It's worth noting, too, that if English is not your developer's native language, this type of communication is all the more effective. Many of us know how often critical details get lost in translation - especially in technology projects. DSS is here to do the the translating so your needs are fully understood by your international developer. |
|
No matter how simple or how complex your needs are, flowcharts like the samples below quickly, clearly, and effectively communicate what your developer needs to know. Please contact me today to assist you in defining your company's requirements so the end result of your project complies with your vision.