IFS 231 Business Analysis LECTURE 3 Functional Specification

IFS 231 Business Analysis LECTURE 3 Functional Specification Documents

Contents § § What is a functional specification? Contect of functional specification Business Analysis 2

Introduction § § What is a functional specification? Why write a functional spec? • • § Streamlines the development process Manage expectations Who writes a functional spec? Business Analysis 3

Define the application This section should answer questions like: § § § What is the application supposed to be? What is the application supposed to do? Who will be using the application? What are the performance metrics? Is there a precedent for this application? • Learn from previous/similar systems and their mistakes Business Analysis 4

Develop Models § Business Process Models • § Conceptual Models • § Input Output (IO) Models and “Swimming lanes” ERD’s Programmer’s Models • Internal (SQL) models Business Analysis 5

Write the FS content § § Create a design document if necessary Write the spec for each page/screen • • Use lots of screenshots and visual prsentations of how screens should look / work Detail! Nothing should be left for the developers to deside Write concisely, correctly, and consistently Use writing / drawing / formatting tools most comfortable for you Business Analysis 6

Requirements Spec § § § Defines WHAT must be delivered Functional Requirements: relate to functions that the solution/system must be able to perform. Informational Requirements: identify reports and enquiries that the system must be able to supply (gather this information from stakeholders) Business Analysis 7

Requirements Spec (2) § Non-functional requirements: relates to quality /qualitative requirements • Operational requirements • Technology requirements • Help files, technical documentation Reliability of the system • Response time, transactions per second Documentation requirements • Usernames, passwords, security levels (security models ) Performance requirements • User interface standards, level of help Security requirements • Operating system, hardware, protocols Usability requirements • Demographics / Environments / Context (Currency) Maximum bugs per 1000 lines of code Archiving requirements Business Analysis 8

Example § Web Tutorial document • This document use Web Design terminology § Wireframes Navigation information, etc. Example of a flowchart • This is not a Cross-functional Flowchart for a Business Process Business Analysis 9