Project Management

Newport, NC, North Carolina, Web Conferencing

Project Requirements Specification

You may view a well-written Software Requirements Specification as a user guide produced before creating the software. Like a guide, the requirements specification should clearly convey exactly how the software should work, in non-technical language. It's not necessary to spell out exactly how the software implements the features in this document. The requirements specification concerns only what the software will do.

High-Level Document, Detailed Functionality

A good software requirements specification will contain all known requirements and describes them clearly. Usually, the document need not state why the requirement exists; that important information is usually reserved for the discussions surrounding the business case for the software. Likewise, the requirements document does not concern implementation costs. Because usually a direct relationship exists between functionality and project costs, this important topic will often be supplied as an estimate accompanying the requirements specification.

Specific Requirements

If an important requirement is the artistic design, screen shot of the design prototype, storyboard, or mock-up will serve as a compelling requirement. If the graphic design requirement is not specified, state that the specific design choice is left to the discretion of the development team.

Also important: ensure all project stakeholders read, understand, and approve of the specification. The best way to accomplish this is often to host a meeting where the specification is dissected. Often, these meetings reveal incorrect assumptions, lead to the removal of unnecessary or costly features, or identify important missing requirements.

Involve the Team

The best requirements specifications consider the viewpoints of the project stakeholders, end users, and technical staff. Often, substantial cost savings are achieved by tweaking the requirements a bit, when possible.

An ideal person to write the requirements specification would be someone having technical writing skills, a developer background, and also well-honed business skills to draw out all of the detailed requirements from somewhat foggy beginnings. Not every organization has such a person available. Consider engaging a consultant when needed to ensure this vital task is done in a professional manner.

Discovering the Requirements

A functional specification documents the requirements. However, first the project stakeholders must find, discuss, and agree upon the requirements. A meeting is often an ideal way to accomplish a great deal in a short time. Large software projects may need large groups to meet over multiple days. It can be a big investment in time; however,  a well-orchestrated brainstorming and requirements-gathering session will be the most valuable time you will likely have during the entire project.

Get Started

Kick off your project with an experienced leader. Be sure your effort has  a well-written, clear, and accurate specification before you commit to developing it. Productive Technology's professional project management consultant has the expertise and skills necessary to produce your function specification. Contact us today for additional information on this and our many other services.