County of San Luis Obispo

General Services Agency - Information Technology

Business and Technical Requirements

<Department Name>

<Project Title>

<Date>

<Author>, <Title>

<Department Name>

Document Overview

The purpose of this document is to delineate the design goals and functional requirements for the <Project Title> application. The document is divided into the following sections:

Project Scope

Responsibilities

Business & Technical Requirements

Project Scope

<Brief scope statement>

Responsibilities

The following table provides a list of significant project milestones and the role of the responsible parties.

Category	Information Technology	Customer
Requirements Gathering Sessions	Facilitate requirements gathering meetings.	Participate in requirements gathering meetings.
Business and Technical Requirements Documentation	Document business and technical requirements.	Review and accept requirements document.
Solution Development Estimate	Estimate effort with customer (business and technical effort requires estimate).	Review for project approval (sponsors).
Solution Development	Develop and test solution.	Participate in application reviews, testing, and acceptance.
Data Warehouse	Migrate, convert, or replicate data as needed.	Provide electronic copies of or access to data files for migration or conversion. Responsible for acquiring additional data if needed and entering it into the new application.
Deployment	Deploy solution. Assist with training as determined by customer.	Test deployment to ensure access and appropriate functionality. Accept final product.

Business & Technical Requirements

The following table represents the complete set of Business and Technical Requirements for this project. The last two columns are to be used when the requirements are to be included as part of a Request for Proposal vendor response, and will be completed by the vendors.

Note: The Vendor Response column should include responses using codes as defined below:

Response Codes:
F = Fully provided “out of the box”
P = Partially provided “out of the box”

3 = Provided via third party product

CU = Custom Development Required (requiring programming changes to source code)
CF = Configuration (Easily changed by the user without any changes to underlying source code)
NA = Not available/unable to support

Item	Title	Description	Must Have (MH)/Nice to Have (NH)	Vendor Response

Code	Vendor Comments
1.0	User Interface Functionality
1.1	Function	<description: include expected input, output; error and event messages; how the form is navigated to and what navigational or functional items should appear on the form itself; which role or application actor may / may not access this form; design constraints>
1.2	Function	<description>
2.0	Business Services – Business Application Layer
2.1	Calculate account balance (for example)	<description: include expected input, output; error, event, or state messages; which role or application actor may / may not access this functionality; dependencies on other functionality or conditions; interfaces; how this functionality is accessed; scenarios, states, and results of function behavior>
2.2	<business service>	<description>
3.0	Business Services – Integration
3.1	Input SAP Real Internal Orders (for example)	<description: include the type and value of information to be integrated; frequency; filtering (if applicable); specific security settings; which external systems are affected; protocol (web service, for example); which application layer is integrated (data, business, user interface)>
3.2	<integration service>	<description>
4.0	Data Services – Data Access Layer & Warehousing Requirements
4.1	Generic data access method (for example)	<description: include information such as auditing required; any known databases or database server systems; specific security settings; data conversion; data transformation; data warehousing; data transfer; data transfer scheduling requirement>
4.2	<data service>	<description>
5.0	Scaling, Performance and Availability
5.1	Scaling	<description: include information on how many users or instances of the application need to be able to run simultaneously; describe how conflicts will be handled (concurrency issue)>

5.2	Performance	<description: include information related to acceptable response thresholds; mitigations for infrastructure latency if applicable>
5.3	Availability	<description: include information pertaining to infrastructure redundancy; server failover; how outages and component failures are handled; critical uptime requirements; acceptable downtime; maintenance approach>
6.0	Conformance and Compliance
6.1	Known compliance requirements	<description: include information on type of compliance or conformity required, for example: ADA/Section 508, HIPAA, and indicate which part of the application must comply if applicable>
7.0	Reporting
7.1	Report: Auditing (for example)	<description: include type of report needed; data; frequency; publisher (data source); subscriber and subscribing method>
7.2	Report:	<description>
8.0	Host Server and Desktop Environment
8.1	Host and Integration Servers Required (Hardware)	<description>
8.2	Host Server Software and Operating Systems Required (Server Software)	<description>
8.3	Desktop Environment (hardware and any external desktop software required to support this application)	<description>
9.0	Documentation and Training
9.1	Application Documentation	Information Technology will provide the application fact sheet and necessary technical documentation.

9.2	User Training	<description>
9.3	User Training Media	<description>

Document Action History (Revised, Reviewed, Approved)
Date	Action	Staff Name	Comments

<Project Title>

Business and Technical Requirements

County of San Luis Obispo	Page 2 of 5

v. 2.0 - August 17, 2009

County of San Luis Obispo	Page 1 of 5

Requirements Document

Shawn Shurick

2009-08-17

County of San Luis Obispo