Stay in touch
-
Latest posts
- Drop-down and flyout menus – when are they appropriate?
- Making a good information architect – empathy
- Functional specification – getting down to business
- Open issues
- Functional specification – important top-level information
- Functional specification – document audience and introduction
- Product data requirements
- Product detail page
- Teasing out data/information requirements
- Team involvement
Archives
Author Archives: Jacqueline
Making a good information architect – empathy
I’m diverging from my normal factual posts today to touch, ever so slightly, on the almost esoteric. I’ve spent a lot of time working with companies to make websites that cater for their users and their information requirements. It also … Continue reading
Posted in Project planning
Leave a comment
Functional specification – getting down to business
After writing the top-level information about the project we get to the project functionality itself. I include an example on the payment confirmation/ receipt page as it’s such a common requirement. Sitemap and/or logic diagrams Then I list all the … Continue reading
Posted in Project planning
Leave a comment
Open issues
Logically this section links to risk analysis. I find this section very useful over the project life-cycle. During planning I list all the questions I’ve come across while planning that the requirement interviews and analysis did not reveal I put … Continue reading
Posted in Project planning, Uncategorized
Leave a comment
Functional specification – important top-level information
Project environment If the project consists of many online and offline discrete elements and/or operational aspects I include a diagram to show the overall environment. The basis for this is my little mental map diagram. Technical environment Specify the programming … Continue reading
Posted in Project planning
Tagged documentation, functional specification, living document, tracking
Leave a comment
Functional specification – document audience and introduction
The document and format you use depends on the company you work for (following their internal process and formats) and the project. Document audience Business stakeholders – one person would be responsible to sign the functionality, budget, timeline etc off. … Continue reading
Posted in Project planning
Leave a comment
Product data requirements
When you plan the data requirements of a project you’ll sit down with the lead programmer (or the person responsible for planning the database) while you’re planning the project data requirements. While you go through the public and admin page … Continue reading
Posted in Project planning
Leave a comment
Product detail page
We looked at the administrative page for managing product details last time. Let’s look at the Product detail page wireframe.
Posted in Uncategorized
Leave a comment
Teasing out data/information requirements
Administrating information On large technical projects you’ll be lucky enough to have a business analyst working on the data requirements and/or the system architect (head developer) will write a technical specification that runs alongside the functional specification. In our case … Continue reading
Posted in Uncategorized
Leave a comment
Team involvement
When reading my posts, this planning malarky, can sound like a solitary activity. It isn’t. The way you approach a project is always dependant on the requirements of the project. In general I like to have the following at hand … Continue reading
Posted in Project planning
Leave a comment