8/6/2019 Functional Specification Template(2)

1/3

8/6/2019 Functional Specification Template(2)

2/3

Non-goal 2

ScenariosScenarios are narrative descriptions that indicate how different users will interact

with and use the new feature or system that we are creating. If you have multiplepersonae who will interact with the system, you will need at least one scenario

involving each of them.

Each scenario should be tied to a Goal from the section above.

:Bob has just gotten home and cant wait to show his young brother Jim acomputerized form ofNkusibidde awo(Interceptor) game. Bob launches the

game and a 4- diagonal square appears. Bob then lets his brother choose on which

side he wants to play, given that Bob starts. After alternating turns Jim has his

members lined up with one in the center. He is declared the winner and Bob in

disbelief clicks to have another go.

Functional Design

The sub-sections that are required for this section of the document will vary widelywith the type of feature/system being described. In general though, you should

include things like:

The database schemas you are using..no database

Any client-server protocols such as the details of your HTTP GET and POST

request/responses

User Interface mockups

User-facing control-flow/application workflows

There are a few sub-sections that should be thought through for most applications

and are included below.

SecurityIs this a security-sensitive feature, and if so, what are the particular security

concerns?

8/6/2019 Functional Specification Template(2)

3/3

What provisions are in place to mitigate the concerns?

Implementation Plan

If applicable, what are the different phases involved in the development of this new

feature/system? This is especially important for complex features that will require

more than a day or two to implement.

Deployment PlanWhat needs to be done in order to deploy this new feature? Include any necessary

steps involved around updating databases, deploying server components, and

installing client components (if any). Indicate if there is a particular order in which

deployment steps need to be followed.

Implementation DetailsThis section is intended to be completed by the developer, with further details

about algorithms, data structures, and other implementation details of the design.

Feel free to add any sub-sections you need.

Open IssuesList any open issues here. By the time the feature is complete, this section should

be empty.