functional specifications template
TRANSCRIPT
-
7/29/2019 Functional Specifications Template
1/7
Functional Specification - FRS document
Enter Project Name HereSoftware Version
Sponsor: Enter sponsors name DMDC Lead: Enter leads name
Prepared By: Enter persons name Published: Enter date
Approved By: Enter persons name Project Officer: Enter persons nameCustomer: Enter customer name here Data Model Review Board: Enter name ofapproving review board member
QA Resource: Enter QA Tester name here Data Dictionary Manager: Enter name ofapproving data dictionary manager
Table of Contents
1.0 Introduction.........................................................................................................................................12.0 Business Context................................................................................................................................13.0 Functional Requirements...................................................................................................................24.0 Non-Functional Requirements...........................................................................................................4
5.0 Future Requirements..........................................................................................................................56.0 Resource Requirements.....................................................................................................................57.0 Revision History..................................................................................................................................6
To update the Table of Contents, click in the table then press F9
i
-
7/29/2019 Functional Specifications Template
2/7
Functional SpecificationElaboration Phase
1.0 Introduction
The introduction should give a summary of the system for which this functional specification is
being written. This summary may include as little or as much detail as necessary, but should
describe the purpose and approach of the system while also providing background and/or history
where appropriate.>
2.0 Business Context
The business context section should describe the system as it relates to business processes and
other systems.
2.1 Definitions
Business definitions go here
Term1 -
TermN -
2.2 Context Models
www.BusinessAnalystFAQ.com Page 1
-
7/29/2019 Functional Specifications Template
3/7
Functional SpecificationElaboration Phase
2.2.1
System X
System X Action
User
System Y
System Y Action
System Z ActionSystem Z
User Action
System Y Action
User Action
2.2.2
3.0 Functional Requirements
3.1 System Actor-Goal Listing
The following table depicts the systems primary actors and their goals in using the system.
3.2 System Use Case Model
The following use case diagram depicts the high-level functionality of . Details on
each of the specific uses are captured in the following use case narratives (Section 3.3) and
business rules (Section 3.4)
www.BusinessAnalystFAQ.com Page 2
Actor Goal Description
-
7/29/2019 Functional Specifications Template
4/7
Functional SpecificationElaboration Phase
System Name
Use Case 1
Use Case 3
Actor2
Actor1
Use Case 2
Secondary
Actor1
Use Case 4
3.3 System Use Case Narratives
The following use case narratives provide details on each of the specific uses of the system:
UC1.
Description: < In one or two sentences, describe the interaction that occurs in this use case. Try
not to regurgitate the basic course of events, rather summarize the events, actors, and goals,
providing context not included in other sections.>
Assumptions
Basic Course of Action
1. (See Alternate Actions A & B)2. (See Business Rule 3.4.2)
Alternate Course of Action A ()
A1.
A2.
Alternate Course of Action B ()
B1.
B2.
3.4 Business Rules
www.BusinessAnalystFAQ.com Page 3
-
7/29/2019 Functional Specifications Template
5/7
Functional SpecificationElaboration Phase
3.4.1
BR1
BR.1.1
BR.1.2
3.4.2
BR2
BR.2.1
BR.2.2
4.0 Non-Functional Requirements
4.1 Performance Requirements
P.1
P.2
4.2 Monitoring and Logging Requirements
M.1 M.2
4.3 Security Requirements
www.BusinessAnalystFAQ.com Page 4
Security Requirements Yes No N/A4.3.1 Does proposed project include COTS Products?
4.3.1.1 Are they security products or security enabled products?
4.3.2 Does proposed project include only standard ports?
4.3.2.1 If not, please identify the ports the product uses.
4.3.3 Does proposed project include hashing or encryption?
4.3.4 Will the application display a Privacy Act Statement?
4.3.5 Is there a valid or legal reason to display the Social Security
Number?
4.3.6 Is there a valid or legal reason for not requiring CAC/PIN
login?
-
7/29/2019 Functional Specifications Template
6/7
Functional SpecificationElaboration Phase
4.4 Privacy Requirements
Personally Identifiable Information (PII) is any form of information that can be used to identify,
locate, or contact an individual. This information includes, but is not limited to SSN, name, homeaddress/phone number, complete DOB, personal medical information, financial information,
religion, or national origin.
There are also indirect identifiers, which when used in combination, could help to narrow downthe identity of a specific individual. This information includes, but is not limited to gender, age,
race, geographic indicators, and job position.
Business Analyst Interview QuestionsBusiness Analyst Job Description
Business Analyst
4.5 Testability Requirements
T.1
T.2
4.6 General Constraints
C1
C2
5.0 Future Requirements
F.1
6.0 Resource Requirements
www.BusinessAnalystFAQ.com Page 5
Privacy Requirements Yes No Unknown
If any question is answered Yes or Unknown, see the DMDC Privacy Information Officer.4.4.1 Is Privacy Act data to be displayed?
4.4.2 Will the application collect, maintain, or disseminate
information in identifiable form?
4.4.3 Will this application change anonymous information into
information in identifiable form?
4.4.4 Will this application change how information in identifiableform is managed?
4.4.5. Will this application alter a business process that results insignificant new uses or disclosures of information?
4.4.6. Will this application alter a business process that willincorporate additional information items in identifiable form?
4.4.7 If new information in identifiable form is added to a
collection, will this application raise the risks to personal
privacy?
4.4.8 Based on all of Section 4.4 questions is a PIA (Privacy
Impact Assessment) required?
http://www.businessanalystfaq.com/blog/business-analyst-sample-interview-questions.htmlhttp://www.businessanalystfaq.com/blog/business-analyst-job-description-explained.htmlhttp://www.businessanalystfaq.com/http://www.businessanalystfaq.com/blog/business-analyst-sample-interview-questions.htmlhttp://www.businessanalystfaq.com/blog/business-analyst-job-description-explained.htmlhttp://www.businessanalystfaq.com/ -
7/29/2019 Functional Specifications Template
7/7
Functional SpecificationElaboration Phase
6.1 Human Resource Needs
Define the human resource needs. Complete the table as well as possible.
Need Resource Amount Status Comments
Project Officer N hoursRequirements/Design N hours
Technical Expert N hours
Systems Architect N hours
Database Administrator N hours
Development N hours
QA Testing N hours
Configuration
Management
N hours
Production Support N hours
Technical Writer
DSC
Systems
7.0 Revision History
Revision Revised By Date
www.BusinessAnalystFAQ.com Page 6