Top Banner
Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442
16

Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Dec 31, 2015

Download

Documents

Florence Mills
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Business Objectives Functional Requirements

Non-Functional Requirements Interface Specifications Policies and Procedures

CPTE 442

Page 2: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Definitions

Page 3: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Business Objectives

• An organizational goal stated in business terms – We would like to reduce operational expenses

of mission control by 45%

Page 4: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Functional Requirements

• A statement of a service that the system must provide– The system must allow for payment by credit

card

Page 5: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Non-Functional Requirements(Quality Requirements)

• A statement of the environment, conditions or constraints under which the system will operate– The average time for validation of credit cards

shall be less than 1 minute, with the maximum time no more than 3 minutes.

– The system shall accept up to 1000 concurrent users

Page 6: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Interface Specifications

• A statement detailing how an external actor shall interact with the system– Swipe credit card through a card reader– Transmit credit card number using bluetooth– Type card number using a keyboard

Page 7: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Policies and Procedures

• A statement detailing necessary1 actions outside of the hardware/software– Connection to the intranet shall only be

through VPN– Expense reports shall be submitted monthly– Sales presentations shall not use Red/Green

color schemes

1. To achieve business objectives

Page 8: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Examples

Page 9: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Inventory tracking

Business Objective: To prevent loss of inventory due to theft or misplaced goods.Functional Requirement: For any scanned barcode, system must be able to report quantity on hand

Quality Requirement: Database must support a minimum of 80,000 different inventory items

Interface Specification: System must work with MS9520 Voyager Hand-Held Scanner Policies or Procedure: All inventory is scanned into the system before leaving the loading dock

Page 10: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Online Gradebook

Business Objective: To give students and parents immediate feedback on grades.Functional Requirement:Quality Requirement:Interface Specification:Policies or Procedure:

Page 11: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

HomeworkCreate a word document that for each of the four sample Business Objectives gives a corresponding:

• Functional Requirement• Quality Requirement• Interface Specification• Supporting Policy or procedure

Page 12: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Data RedundancyRAID

Business Objective: To be able to recover data and resume operations in a timelymanner after a hardware, software, or user failure

Page 13: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Media support

Business Objective: To be able to more effectively communicate ideas both internally amongst employees and externally to potential clients and business partners.

Page 14: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Security

Business Objective: To prevent disruption of business functions, and theft of business data by external individuals

Page 15: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.

Communications

Business Objective: To increase sales by enabling potential clients to more easily reach the sales staff.

Page 16: Business Objectives Functional Requirements Non-Functional Requirements Interface Specifications Policies and Procedures CPTE 442.