.: Common Mistakes: Functional Web Specification
Category:Home / Internet / Web Design
Ineffective functional specification for Web projects such as Web sites, Intranets or Portals contribute largely to delays, higher costs or in applications that do not match the expectations. Independent if the Web site, Intranet or Portal is custom developed or built on packaged software such as Web-, enterprise content management or portal software, the functional specification sets the foundation for project delays and higher costs. To limit delays and unexpected investments during the development process, the following pitfalls should be avoided:
Too vague or incomplete functional specification: This is the most common mistake that companies do. Everything that is ambiguously or not specified at all, developers do not implement or implement in a different way of what site owners want. This relates primarily to Web features that are considered as common user expectations. For example, HTML title tags, which are used to bookmark Web pages. The Web steering committee may specify that each page contains a page title, but does not specify that HTML Title tags needs to be implemented as well. Web developers therefore may do not implement HTML Title tags or implement them in a way, which differs from site owners' visions. There are other examples such as error handling on online forms or the definition of ALT texts for images to comply with the disability act section 508. These examples look like details but in practice, if developers need to modify hundreds or even thousands of pages, it amounts to several man-days or even man-weeks. Especially, the corrections for images as business owners need first to define the image names prior that Web developers can implement the ATL texts. Ambiguous functional specification can result due to the lack of internal or external missing usability skills. In this case, a one-day usability best practice workshop transfers the necessary or at least basic usability skills to the Web team. It is recommended, even for companies that have usability skills or rely on the subcontractor's skill set, that an external and neutral consultant reviews the functional specification. Especially, as such reviews relate to marginal spending as compared to the total Web investments (e.g. about $10 K - $15 K dollars for a review).
Future site enhancement not identified or not communicated: It is crucial that the Web committee identifies at least the major future site enhancements and communicates them to the development team. In the best case, the development team knows the roadmap for the coming three years. Such an approach allows the development team to anticipate implementation choices to host future site enhancements. It is more cost effective on mid- or long-term to invest more in the beginning and to build a flexible solution. If Web teams do not know or even ignore future enhancements, the risk for higher investment increases (e.g. adding new functionality in the future results in partially or at worst in totally rebuilding existing functionality). Looking at the financial delta for a flexible solution versus a solution just satisfying the current requirements, the flexible solution has proven to be more cost-effective in practice from a mid- and long-term perspective.
Planned functionality not aligned with internal resources: Many companies look at site functionality only from a site visitor perspective (e.g. facilitation of searching information or performing transaction) and corporate benefits (e.g. financial benefits of self-service features). However, there is a third dimension the impact of site functionality on internal resources. Site functionality that can heavily impact internal resources are for example:
- Web sites: providing news, online recruitment, online support, etc.
- Intranets / portals: providing content maintenance functionality for business managers
It is crucial for the success of site functionality that the Web committee analyzes the impact and takes actions to ensure operations of the planned functionality. For example, providing the content maintenance functionality to business owners and product mangers with an associated workflow. This functionality is effective and can generate business benefits such as reduced time to market. However, in practice, business owners and product managers will need to write, validate, review, approve and retire content. This results in additional workload. If the Web committee has not defined in the Web governance (processes, policies, ownership and potentially enforcement), it may happen that this functionality is not used and hence becomes useless.
Wish lists versus actual needs and business requirements: The functional specification is not aligned with user's needs or business requirements. This is more common for internal applications such as Intranets or portals. In many cases, the project committee neglects to perform a sound internal survey and defines functionality by generalizing individual employees' wishes without any sound proves. Capturing the feedback of internal users across the organization allows determining the critical functionality. To effectively perform a survey a representative set of employees need to be questioned. Further these employees need to be categorized into profiles. The profiles need to be characterized by for example, frequency of usage of the Intranet, estimated duration by visit, usage of the Intranet to facilitate their daily tasks, contribution to the business, etc. Based on this information the Web team can then prioritize the functionality and choose the most effective and relevant functionality for the next release. Less critical or less important functionality may be part of future releases (roadmap) or dropped. If such a sound decision process is not performed, it may happen that functionality is developed but only used by few users and the return of investment is not achieved.
Not enough visual supports or purely text based: Textual description of Web applications can be interpreted subjectively and hence leading to wrong expectations. To avoid setting wrong expectations, which may are only discovered during development or at worst at launch time, functional specification need to be complemented by visual supports (e.g. screenshots or at best HTML prototypes for home pages or any major navigation pages like sub-home pages for the major sections of the site such as for human resources, business units, finance, etc.). This allows reducing subjective interpretation and taking into account the users' feedback prior development. Such an approach helps setting the right expectations and to avoid any disappointments at the end once the new application is online.
We have observed these common mistakes, independently if companies have developed their Web applications internally or subcontracted them to an external service provider.
Article keywords: Functional Specification, Web specification, design specification, prototyping, stripped pages
Article Source: http://www.articles32.com
Nicolas Bürki is the founder of effinfo.com, a European based usability and Strategic Web Marketing company providing you actionnable and pragmatic publications on online marketing, usability, Web strategy, Web Goverance. Our consulting engagements are delivered in English, French and German language.
- Benefit from our freely availabe Web publications
- Subscribe to our FREE monthly newsletter on Web design, usability and strategic Web marketing.
- Subscribe to our FREE Webinars providing you pragmatic advise on how to boost your Web sites.
.: New Web Design Articles
1). HTML Might Become Obsolete
Web designers are beginning to dump HTML in favor of more versatile web programming languages
2). Macromedia Dreamweaver: An Introduction
Getting started with your first web page can seem very daunting indeed. Macromedia Dreamweaver is the industry leader in web editors, but knowing where to start and what you need to know can be a little confusing at first.
3). Finding A Good Web Designer
Avoid the mistakes I made when I hired someone over the internet to design my web site
4). Top Tips for Getting Free Websites
There are millions of opportunities of earning money online, but for that you frequently need to have a web site and there are many people interested in how to build a web site online for free. So whether you want to build a free business web site or to build a Yahoo-like web site, you can be sure there are plenty of online guides, such as this, to take you step by step through the process.
5). Is Your Web Site Driving Away Visitors?
Much has been written about optimizing your web site for search engines, but less emphasis is placed on usability. Optimizing for usability and for search engines is not a contradiction.
6). Choosing a Web Designer
freelance web designers are rip-off artists
7). HTML Sitemaps Are Still Important
An html sitemap is one that humans and search engines both can read. Google sitemaps are important too, but they are specific to google and are read only by a search engine.
.: Top Web Design Articles
1). Advanced Joomla Templating (pt1) Using Module Class Suffix
an article from User Written Resources
1. duplicate the styles already used for the particular module, adding a suffix to each style name. this will definitely include some of the following;
1. .module {} 2. div.moduletable {} 3. div.moduletable h3 {} 4. table.moduletable {}/li> 5. table.moduletable th 6. table.moduletable td
and can include other styles used on the content in that section, such as;
1.
2). How To Make a MySpace Layout That Stand Out
If you are a MySpace user, you have learned what an easy to read and fun profile looks like. The only problem is, you may not know how to create or find out. Most of the time when you see an awful MySpace layout, it's because its sloppy, hard to read, or has annoying links you didn’t even see. That is because since MySpace has been growing so much, so have the layout sites.
3). Professional XOOPS theme design - What to look for
In general, prices for theme design work will range depending on a number of factors. If you don't mind the designer releasing the theme on their site for others to purchase, then you can expect anywhere from $20US to $50US for your theme. If the theme must be a one of a kind theme that only you use, you could expect to multipy the fee by at least 10x.
4). Adsense: The Smart Investment
Over the last 2 years, We have been building a Virtual Adsense Empire of over 500 websites and making some good money. We've also been building content sites for clients using the same system. The system we use is not something that produces 1000's of sites with a click of a button, our system does not build spam websites, nor does it produce the same sites you see over and over and over again.
5). Irish Graphic Design Industry
Graphic design is the use of color, light, balance, contrast, emphasis, proportion, proximity, repetition, texture and a plethora of other elements to create a work of digital art that is pleasing to the eye. Graphic design is about seamlessly molding image and text to convey a theme, message, or often advertise a product or service. Graphic design dates back to prehistoric times.
6). How to Create a Splash Page for Your Website?
These splash designs prove to be quite popular, especially among the designers as they allow the designer to show their skills in flash and any other technology on a single page. The splash page design involved in the splash page will be one that is very attractive to the eye of the viewer. Its main intention lies in captivating the viewer the moment he looks at it.
7). Does Your Web Design Include Background Music?
When you design your website, you may wonder whether or not you should include background music in your web design. The answer to this requires you to ask two additional questions: