User involvement is key to designing an effective application and a good user interface. Give the business users a template of standards and procedures to follow so that they can describe how they do their work, including workflow, and thus how the application should work for them.
You searched for: ∨derBy=RANK∨derBy=RANK (∨DERBY=RANK∨DERBY=RANK)
20901 items found
Ever been confused by technical jargon when you access an application's online help? Don't let your users feel that way! Define standards, as in this example, to ensure that your documentation writers develop clear, direct help files that appropriately support your application.
Why build a data warehouse? Be sure you have good justification in the form of a solid business case before taking the plunge.
Oops! isn't what your client wants to hear at the eleventh hour in the delivery cycle. Use this sample QA plan to verify that the data warehouse (or data mart) has been designed and built correctly before it undergoes user acceptance testing.
Even though you've built the perfect data warehouse, it's better to be safe than sorry if something goes wrong during its operation and you need to restore the original data files. Take the time to document your backup and recovery procedures, as in this example.
This example will help you put in place logical as well as physical database design standards for building data warehouses using Business Objects.
Does your project involve building an automated system based on individual business areas that are designed and implemented separately? Here's an example of a planning strategy for integrating business areas into a single system.
What is a data warehouse, how do I use it, and what's in it for me? How should you instruct and inform your data warehouse users on these subjects? Here is an informative paper on the inner workings of a data warehouse that was built to perform category management analysis for a retail grocery chain.
Reduce, Reuse, Recycle! It's not just an environmental slogan, it's a project manager's dream. Document standards as to how to reuse development objects and approaches on your project, as in this IEF-based client/server example.
How do changes get recorded, analyzed and approved on your project? This document contains guidelines for these procedures and more.