1. Procedures Software for People

2. Agenda Procedure: Definition Software for People Designing Procedures Procedures as Problem Solving Software: Procedures for Computers Some Important Lessons

3. Procedure: Definition From the textbook: “…include the strategies, policies, methods and rules for using the CBIS” (pg. 12) My definition: a step-by-step description of what a machine is to do to accomplish a goal. Implications: People are sometimes machine-like

4. Software for People Characteristics  Broken into steps  Involve information that has to be obtained  Steps are discrete  Elements of a step: Input Process Output  Procedures have a stopping point  Procedures produce products

5. Designing Procedures People make mistakes: expect them People get tired: people work imperfectly and inconsistently People need feedback: let people know how the procedure is working People have limited skills: people can’t do everything, can’t understand everything.

6. Procedures as Problem Solving Intelligence Design Choice Problem-solving Procedure Execution Gather information on the current environment Access a pre-designed Procedure embodying knowledge Execute the procedure, bringing the environmental knowledge to bear on the steps carried out

7. Procedures as Problem Solving This is the information or data the procedure user brings to the situation This is based on knowledge or a theory about the “best” way to get something accomplished; it’s the equivalent of expert opinion and hopefully has been tested. The execution depends on how well the procedure can be carried out by the procedure user. Gather information on the current environment Access a pre-designed Procedure embodying knowledge Execute the procedure, bringing the environmental knowledge to bear on the steps carried out Effectiveness depends on user’s research and observation skills as well as quality of environmental data Usefulness depends on how “expert” the model is and how well it matches the current environment Usability depends on user skills and the match with what the procedure is demanding from the user

8. Software: Procedures for Computers Software is exactly a procedure that a computer performs. Steps are accessed sequentially Activities are computer activities (addition, etc.) Feedback is less important and computers don’t have human failings (or capabilities)

9. Some Important Lessons Procedures are only as good as  Users’ ability to access and provide accurate and valid descriptions of the current situation and manipulate the procedural parameters  The knowledge embedded in the procedure; for software, this means that users and systems analysts have to know what process needs are and programmers have to program correctly and effectively  Users’ ability to carry out the procedure with respect to physical and cognitive limitations. Computers can usually execute software without problems, but not always.