Professional Documents
Culture Documents
Specification Document
1.0
PURPOSE
[Provide an overall description of the FRD, its purpose. Reference the system name and identifying information about the
system to be implemented.]
SCOPE
[Discuss the scope of the document and how it accomplishes its purpose.]
BACKGROUND
[Describe the organization and its overall responsibilities. Describe who is producing the document and why.]
REFERENCES
[List references and controlling documents, including: meeting summaries, white papers, other deliverables, etc.]
A. Assumptions
Examples of assumptions include: availability of a technical platform, legal changes and policy decisions.
Section/
Requirement ID Requirement Definition
ASSUM-1 The system shall [parent requirement group 1].
ASSUM-1 The system shall [child/parent requirement].
ASSUM-1.1.1 The system shall [child requirement].
ASSUM-1.2 The system shall [child requirement].
B. Constraints
Constraints are boundary conditions on how the system must be designed and constructed. Examples include: legal
requirements, technical standards, strategic decisions.
• Constraints exist because of real business conditions. For example, a delivery date is a constraint only if there are real
business consequences that will happen as a result of not meeting the date. If failing to have the subject application
operational by the specified date places the organization in legal default, the date is a constraint.
• Preferences are arbitrary. For example, a date chosen arbitrarily is a preference. Preferences, if included in the FRD,
should be noted as such.]
Section/
Requirement ID Requirement Definition
CONS-1 The system shall [parent requirement group 1].
CONS -1 The system shall [child/parent requirement].
CONS -1.1.1 The system shall [child requirement].
CONS -1.2 The system shall [child requirement].
WEBSITE REQUIREMENTS
Example: The user interface should intuitively guide the visitor to the information they seek, including web accessibility. The site
should include the following navigation strategies:
- Menu System as the primary navigation method of the site that is always displayed on each page.
- A hierarchical menu content divided into related functional areas based on the current Organization site map.
Please refer to site map in Appendix A.
- Each section must have a main page where visitors can navigate to the sub items under the sections, but still
be able to get back to any of the other main section home pages.
- Full site search, with administrator control.
- Navigation, category, section, and link names and link design.
Example: The web site content must easily be able to manage dynamically by non-technical department staff in as simple a
method as possible. The staff will be able to add, change and delete site content without manipulating any HTML or scripting
code. Personnel should be able to access designated templates and easily update information in pre-designed formats,
including the use of databases to hold and change dynamic information. This includes formatted text, hyper-links, digital
pictures, as well as providing downloadable documents in Word, Excel, PDF, and other formats. Most documents will age and
lose relevancy over time, and need to be routinely updated or removed.
Example: In order to maintain a quality site that continues to meet organization needs, a quality web site reporting system that
provides types and features of management reports, including traffic counts, orgin or domain names sources of visitors, or other
useful information regarding the website is required.
D. Video/Audio Streaming
[Discuss whether the site will need to support on-demand, live streaming, podcasts (or all types) as well the encode format the
server will need to support (Real, Windows Media, Quicktime, etc.]
Example: Organization product demonstrations will be available for demand-access by users of the website through video/audio
streaming or a similar technology. The website shall address this capability and shall specify any requirements to enable V/A.
1. The title of each page should be unique to each page and not be longer than 70 characters.
2. Each content author must have the ability to customize the META-DESCRIPTION and META-KEYWORDS in the CMS
3. All page URLs , especially dynamically generated ones, must have friendly URL aliases so that they are picked up by
search engines.
4. The CMS must employ semantic HTML (h1, h2, p, etc.)
5. The CMS should allow the content author to specify ALT text for all images
E. Website Elements:
Section/
Requirement ID Requirement Definition
BREQ-1 Home Page The company logo will be located at the top left hand corner of the page
A global navigation bar will be located below the logo
Rollovers will be used for the global links to the other web pages
- Reservations
- Facilities
- Directions
- About Us
- Events
- Online Store
- Contact
- Employment
- Site/Map
- Legal/ Privacy
The bottom of the page will contain links to information regarding copyright and
privacy statement.
- Store Locator
- Event Page
- Contact
- Careers
- Site Map