Workin with devs
- Started
- Last post
- 7 Responses
- jox
I'm writing a function specification for a CMS. I have it all in my head from a designer's P O V but having a hard time describing it to a developer. Any tips or suggestions how to approach this?
A bit of a longshot but I would love you forever if you have done something similar and could show me bits and pieces how a spec is built up for the logical side of the brain to understand as opposed to the creative one...
thank yawu!
- joyride0
Here's a basic outline of 1:
Table of Contents
PROJECT OVERVIEW
PURPOSE OF DOCUMENT
PROJECT NAME
PROJECT DESCRIPTION
E1 - REQUIREMENTS
PROBLEM STATEMENT
BUSINESS JUSTIFICATION / BENEFIT. SUCCESS METRICS
IDENTIFY CUSTOMERS / USERS
REQUIRED WEB METRICS / REPORTS
COMMUNICATION PLAN
OUT OF SCOPE ITEMS
COMMERCIALIZATION PLAN
SYSTEM REQUIREMENTS
RISKS / MITIGATION PLAN
E2 – DESIGN
SUMMARY OF SYSTEM FUNCTIONALITY
REQUIREMENTS FOR HARDWARE
OVERALL REQUIREMENTS
TOUCH SCREEN
LABEL PRINTER
BARCODE SCANNER
INTERNET CONNECTION
PROJECT USE CASE SCENARIOS
1.0 FUNCTIONALITY – xxxxxx &xxxxxxx
Screen #1 – Main Menu
Screen #2 – xxxxxx
Screen #3 – xxxxxxxxxxxx
2.0...etc
DATA RETENTION REQUIREMENTS
USER ACCESS AND AUTHORITY REQUIREMENTS
USABILITY TEST PLAN
ROLLOUT PLAN / COMMUNICATION PLAN
SECURITY
APPROVALBasically, the functional part is screenshots and a description of each action for the screen.
Make any sense?
PS. Sorry bout the all caps! copy/pasted it
- jox0
Wahey, perfect! Thanks!
- winter0
don't forget a map! they'll ask you for it when in sight of your 400pp. brochure.
- joyride0
don't forget a map! they'll ask you for it when in sight of your 400pp. brochure.
winter
(Jun 15 06, 07:49)true, as much as i hate visio its pretty handy for that. you can do it in excel too. i usually do it on paper anyway. but corps need it all official n shit. helps to map out complex apps
- invisiblecity0
This is a pretty good wireframe documentation technique. More visual than excel and word docs.
- invisiblecity0
oh yeah, the link:
http://www.boxesandarrows.com/vi…
- Fariska0
For a CMS i use to draw a map of how it works, write all the specs
and, the most useful thing, prepare , also on paper, a mockup of the screens. Just to let them understand what input fields, what radio buttons etc, you want.In this moment of the project visualizing is important. At least you have a common base to doodle on.