Web Development Business Requirements Template Introduction Purpose: Provide synopsis of workflow/problem/opportunity analysis. Describe how this system fits into the overall strategic and tactical objectives of the business. Give a brief description of what the system does. Intended Users: Who will be using the system? Are there specific characteristics about users that should be kept in mind? Who contributes to the upstream processes? Who relies on this process downstream? External System Interaction: What other systems does this Web Application interact with (e.g. PeopleSoft)? Does this application need a link to My One Stop? To other Web Sites? Glossary Term Definition List all the terms that are meaningful to the Business. Insert rows as necessary. Define the terms as known to the Business and to the Customer List all the terms that are technically meaningful. Insert rows as necessary Define the terms as known to Web Development and to the Business System Model Introduction: This section provides the overall view of how this system fits into a physical system or business environment. Include diagrams as necessary for clarification. Refer to the workflow/problem/opportunity analysis document as necessary. System Structure: How does this proposed system interact with other systems? Probably a diagram. Communication and Data-Flow: How does information flow into the process? Who provides the input, what processing occurs, what is the output? This is very high level; detail will be required in the functional requirements section. This is probably another diagram. Assumptions: Document any assumptions you make about the user community, system interaction, etc. Functional Requirements Requirement 1 Definition: What specifically should the user be able to do? Why is this important? Owner: Who originated this requirement? Data Elements: A list of data elements present for this requirement. Indicate whether the data is retrieved from a database, input by the user, display only, or available for user manipulation. Inputs: A description of the inputs needed to perform the function defined above Processing: A description of the transformation of data or effect of the system the requirement will perform Output: A description of the output produced after the processing is complete Testing Strategy: How will this requirement be tested? Cross Reference: Are there other requirements that are related to or impacted by this requirement? Repeat requirements section as many times as necessary. Requirement 2 Definition: Owner: Data Elements: Inputs: Processing: Output: Testing Strategy: Cross Reference: Sign-off Role Date Signature Author Sponsor Project Manager E-Business Manager