writing functional specifications n.
Skip this Video
Loading SlideShow in 5 Seconds..
Writing Functional Specifications PowerPoint Presentation
Download Presentation
Writing Functional Specifications

Writing Functional Specifications

200 Views Download Presentation
Download Presentation

Writing Functional Specifications

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Writing Functional Specifications JAMS Workshop Makerere University September, 2010

  2. Agenda • What is a Functional Spec? • Specification Template • Technical Goals Exercise • Specification Details • Sample Specification

  3. What is a Functional Spec? A functional specification is a document that describes the essential technical requirements of a system or feature, including the procedures by which it can be determined that requirements have been met. • Specs are helpful in a number of ways: • Enable teams to achieve consensus on what a program is to achieve before implementing it • Allow for accurate estimates for work and resources • Act as a negotiation and reference document for engineering changes • Help avoid duplication and inconsistencies

  4. Standard Spec Template Written by either program manager or business stakeholder – background on what the feature is and why we need it. Sometimes called a “one-page spec”. • Overview • Goals/Non-Goals • Scenarios • Functional Design • Add sections here as appropriate • Implementation Plan • Deployment Plan • Security • Performance • Implementation Details • Open Issues Written by program manager in collaboration with developer. Describes what will be built in enough detail to unblock the dev team, including user interface design, workflows, and system diagrams. Written by developer, discusses deeper technical aspects of system Written by spec owner, should be empty when spec is “done”

  5. Users of a Functional Spec

  6. Spec Lifecycle Spec may be updated at each stage of development

  7. Overview • What is the feature about and why do we care? • You only need a few paragraphs to describe it at a high level • But make them compelling, especially if the feature is large or expensive to build • Address the business need for the feature • Anyone (technical or otherwise) should be able to read this section and understand it Tic-tac-toe is a game for two players, X and O, who alternate marking spaces in a 3x3 grid with their symbol. The player who successfully places a set of three marks in a horizontal, vertical, or diagonal row wins the game. If no player can create a horizontal, vertical, or diagonal row then the game is a draw. Player X goes first. As it has a simple set of rules, tic tac toe provides leisure entertainment for people of all ages.

  8. Goals and Non-Goals • Goals and Non-Goals clearly articulate what you are and are not doing • Goals are the concrete outcomes you are trying to accomplish with the feature • They should be prioritized • Non-Goals help with scoping: they clearly identify things you are not trying to accomplish • Non-goals may (or may not) become goals at a later point in the project

  9. Technical Goal-Writing Exercise • Tic-Tac-Toe • A two-player game where players try to get three squares in a row • Beyond that high-level description, what is it and, more importantly, what isn’t it? Goals [P1] Support two human players in a game that is run as a client application [P2] Support custom player names … • Non-Goals • Support for any grids larger than 3x3 • …

  10. Tic-Tac-Toe Goals and Non-Goals • Goals • [P1] Support two human players in a game that is run as a client application • [P1] Use a graphical representation of the players and game board • [P1] Alternate turns between the players starting with X • [P1] Declare a winner when a player has successfully placed three marks in a row • [P1] Declare a tie when no player can make a winning move • [P1] Support for starting a new game after the initial game has completed • [P2] Allow the game to be run inside a web-browser • [P2] Use multi-colored graphics in the game visuals • [P2] Support custom player names • [P2] Tabulate, store, and display statistics on players’ performance • [P3] Add a timer to limit the amount of time a player is allowed to spend on a turn • [P3] Allow for the two players to be on separate machines and play through the network • [P3] Have one player be a computer-based (AI) player • Non-Goals • Support for any grids larger than 3x3 • Support for non-grid shaped game boards • Animation of game play • Allow player O to start a game

  11. Scenarios • A scenario is a narrative description of a user’s interaction with the system • There is usually at least one scenario for each type of user who interacts with the system Richard has an afternoon free. He calls up his friend Joseph and invites him over to play tic-tac-toe. Richard launches tic-tac-toe and a 3x3 grid appears on the screen. They play a game, Joseph connects three Os on the right-most column and is declared the winner.

  12. Functional Design • Describes the system in enough detail for testers to write test plans and developers to design the implementation • Description of major components • Application workflows/logic • User Interface mockups • Database schema • Protocols/wire formats for any client/server interactions • Diagrams are helpful • Does not cover details that are purely internal implementation • Focuses on what outside agents observe when interacting with the system

  13. Player clicks a square Is square available? Yes No Update Gameboard Switch Current Player and update UI 3 in a row? No Yes Start New Game Print winning message Tie? No Yes Print tie message Update Statistics

  14. Functional Design: Security • A spec for any security-sensitive feature needs to address security • Discuss concerns and mitigations

  15. Functional Design: Implementation & Deployment Plan • Implementation Plan • Gameboard and game-play logic • UI design and visuals for gameboard, players, and winner notifications • Hooking up the UI gestures to the game-play logic • Advanced features, such as customized player names, timing moves, and showing high scores • Implementation Plan • If applicable, what are the different phases involved in the development of the feature? • Especially important for complex features that will take more than a day or two • Deployment Plan • How will we deploy this new feature? Are there updates or patches that need to be installed on a server? Any database schema changes? • Does the order of steps matter? Deployment Plan Tic-tac-toe will be packaged as a single Windows executable. There are no features that require special setup tasks.

  16. Implementation Details • Further details on how the developer will implement the product • Algorithms • Class/method definitions • Data structures • Enables testers to perform deeper testing • For bigger features, allows for better collaboration among multiple developers

  17. Open Issues • Used to capture unanswered questions during the spec authoring and review process • This section should be empty when the feature is complete • Open Issues • Should we use Windows Forms or WPF for the UI? • Should we secure the high-score file, or at least obfuscate it?

  18. Sample Specification • The functional specification for Tic-Tac-Toe is included in your Student Packet •