E-mail Me
Syllabus
Schedule
Handouts
Assignments
All My Webs
Dept Home
|
Applications
Jim Walkenbach defines a spreadsheet application as:
A spreadsheet file (or a group of related files) designed
so that someone other than the developer can perform useful work without
extensive training.
This could be a good definition for applications designed in
Word, Excel, or Access. Two key things stand out:
-
It has to function for someone other than the developer.
-
The user must find it useful without a lot of training.
Walkenbach gives a good list of what he thinks makes a good
design:
-
Enables user to perform tasks they couldn't do otherwise.
-
Provides an appropriate solution to the problem.
-
Does what its supposed to do.
-
Produces accurate results and is bug-free.
-
Performs its job using appropriate, efficient methods.
-
Traps errors and helps users correct them.
-
Does not allow the user to delete or modify important
components.
-
Offers the user a clear, consistent user interface.
-
Formulas and macros are well-documented
-
Designed so other developers can make simple modifications
easily.
-
Easily accessible help system.
-
Portable design - runs on any machine with the right
software.
He offers these steps for developing applications:
-
Determine the needs of the user.
-
Ask the user for specifics - what inputs, what outputs?
-
Offer what you think they need - they'll correct
you.
-
Talk to the end user.
-
Find out what they do now.
-
Watch out for "needs" that contain solutions.
-
Plan applications that meet those needs.
-
Structure - worksheets, modules, data files
-
Formulas or VBA?
-
Delivery - will you give the user modules?
Add-ins? Workbooks?
-
Stand alone or networked?
-
Version of Excel
-
Error handling
-
Determine the most appropriate user interface.
-
Spreadsheet template?
-
Custom forms?
-
Standard Dialog Boxes?
-
Create the spreadsheet, formulas, interface, and macros.
-
Test and Debug.
-
Make it bulletproof.
-
Make it aesthetically pleasing and intuitive.
-
Document your work.
-
Create user documentation and help files.
- Assume a level of competence
- Walk the user through the operation
- Test with someone who doesn't know the program
- Lay out documentation to let the user jump ahead
- Address potenetial errors
- Help files need to be brief, clear, helpful
-
Distribute it to the user.
-
Update when necessary.
|