1. 6-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 6 Systems Development Steps, Tools, and Techniques

2. 6-2 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Presentation Overview Seven Phases In The Systems Development Life Cycle Seven Phases In The Systems Development Life Cycle Knowledge Workers and Their Roles In The Systems Development Life Cycle Knowledge Workers and Their Roles In The Systems Development Life Cycle Why Systems Fail Why Systems Fail Selfsourcing Selfsourcing Outsourcing Outsourcing Prototyping Prototyping

3. 6-3 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Opening Case Study Building The Unbelievable – The Hoberman Arch Many information systems are developed and brought to life by following the systems development life cycle. Many information systems are developed and brought to life by following the systems development life cycle. Why is knowledge worker involvement in each phase of the SDLC critical for successful system development? Why is knowledge worker involvement in each phase of the SDLC critical for successful system development?

4. 6-4 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Introduction Systems development life cycle (SDLC) - a structured step-by-step approach for developing information systems. Systems development life cycle (SDLC) - a structured step-by-step approach for developing information systems.

5. 6-5 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 1: Plan Define the system to be developed. Define the system to be developed. Set the project scope. Set the project scope. Develop the project plan including tasks, resources, and timeframes. Develop the project plan including tasks, resources, and timeframes.

6. 6-6 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 1: Plan Planning phase - involves determining a solid plan for developing your information system. Planning phase - involves determining a solid plan for developing your information system. Critical success factor (CSF) - a factor simply critical to your organization’s success. Critical success factor (CSF) - a factor simply critical to your organization’s success. Project scope - clearly defines the high-level system requirements. Project scope - clearly defines the high-level system requirements.

7. 6-7 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 1: Plan Project scope document - a written definition of the project scope and is usually no longer than a paragraph. Project scope document - a written definition of the project scope and is usually no longer than a paragraph. Project plan - defines the what, when, and who questions of system development including all activities to be performed, the individuals, or resources, who will perform the activities, and the time required to complete each activity. Project plan - defines the what, when, and who questions of system development including all activities to be performed, the individuals, or resources, who will perform the activities, and the time required to complete each activity.

8. 6-8 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 1: Plan Project milestones - represent key dates for which you need a certain group of activities performed. Project milestones - represent key dates for which you need a certain group of activities performed. Project manager - an individual who is an expert in project planning and management, defines and develops the project plan and tracks the plan to ensure all key project milestones are completed on time. Project manager - an individual who is an expert in project planning and management, defines and develops the project plan and tracks the plan to ensure all key project milestones are completed on time.

9. 6-9 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 2: Analysis Gather the business requirements for the system. Gather the business requirements for the system.

10. 6-10 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 2: Analysis Analysis phase - involves end users and IT specialists working together to gather, understand, and document the business requirements for the proposed system. Analysis phase - involves end users and IT specialists working together to gather, understand, and document the business requirements for the proposed system. Business requirements - the detailed set of knowledge worker requests that the system must meet in order to be successful. Business requirements - the detailed set of knowledge worker requests that the system must meet in order to be successful.

11. 6-11 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 2: Analysis Joint application development (JAD) - knowledge workers and IT specialists meet, sometimes for several days, to define or review the business requirements for the system. Joint application development (JAD) - knowledge workers and IT specialists meet, sometimes for several days, to define or review the business requirements for the system. Requirements definition document – prioritizes the business requirements and places them in a formal comprehensive document. Requirements definition document – prioritizes the business requirements and places them in a formal comprehensive document. Sign-off - the knowledge workers’ actual signatures indicating they approve all of the business requirements. Sign-off - the knowledge workers’ actual signatures indicating they approve all of the business requirements.

12. 6-12 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 3: Design Design the technical architecture required to support the system. Design the technical architecture required to support the system. Design system models. Design system models.

13. 6-13 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 3: Design Design phase - build a technical blueprint of how the proposed system will work. Design phase - build a technical blueprint of how the proposed system will work. Technical architecture - defines the hardware, software, and telecommunications equipment required to run the system. Technical architecture - defines the hardware, software, and telecommunications equipment required to run the system.

14. 6-14 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 3: Design Modeling - the activity of drawing a graphical representation of a design. Modeling - the activity of drawing a graphical representation of a design. Graphical user interface (GUI) - the interface to an information system. Graphical user interface (GUI) - the interface to an information system. GUI screen design - the ability to model the information system screens for an entire system. GUI screen design - the ability to model the information system screens for an entire system.

15. 6-15 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 3: Design

16. 6-16 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 4: Development Build the technical architecture. Build the technical architecture. Build the database and programs. Build the database and programs.

17. 6-17 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 4: Development Development phase - take all of your detailed design documents from the design phase and transform them into an actual system. Development phase - take all of your detailed design documents from the design phase and transform them into an actual system.

18. 6-18 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 5: Test Write the test conditions. Write the test conditions. Perform the testing of the system. Perform the testing of the system.

19. 6-19 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 5: Test Testing phase - verifies that the system works and meets all of the business requirements defined in the analysis phase. Testing phase - verifies that the system works and meets all of the business requirements defined in the analysis phase. Test conditions - the detailed steps the system must perform along with the expected results of each step. Test conditions - the detailed steps the system must perform along with the expected results of each step.

20. 6-20 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 6: Implement Write detailed user documentation. Write detailed user documentation. Provide training for the system users. Provide training for the system users.

21. 6-21 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 6: Implement Implementation phase - distribute the system to all of the knowledge workers and they begin using the system to perform their everyday jobs. Implementation phase - distribute the system to all of the knowledge workers and they begin using the system to perform their everyday jobs. User documentation - highlights how to use the system. User documentation - highlights how to use the system.

22. 6-22 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 6: Implement Online training - runs over the Internet or off a CD-ROM. Online training - runs over the Internet or off a CD-ROM. Workshop training - is held in a classroom environment and lead by an instructor. Workshop training - is held in a classroom environment and lead by an instructor.

23. 6-23 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 7: Maintain Build a help desk to support the system users. Build a help desk to support the system users. Provide an environment to support system changes. Provide an environment to support system changes.

24. 6-24 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 7: Maintain Maintenance phase - monitor and support the new system to ensure it continues to meet the business goals. Maintenance phase - monitor and support the new system to ensure it continues to meet the business goals. Help desk - a group of people who responds to knowledge workers’ questions. Help desk - a group of people who responds to knowledge workers’ questions.

25. 6-25 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Knowledge Workers and Their Roles in the SDLC Your participation in the systems development process is vitally important because you are (or will be) a: Your participation in the systems development process is vitally important because you are (or will be) a: 1. Business process expert 2. Liaison to the customer 3. Quality control analyst 4. Manager of other people

26. 6-26 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Knowledge Workers and Their Roles in the SDLC Plan Define which systems are to be developed. Define which systems are to be developed. Define the project scope, project plan, and project milestones. Define the project scope, project plan, and project milestones. Allocate individuals to work on the different activities. Allocate individuals to work on the different activities.

27. 6-27 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Knowledge Workers and Their Roles in the SDLC Analysis Review all business requirements. Review all business requirements. It’s far cheaper to find an error during the planning or analysis phase than it is to find the same error during the implementation or maintenance phase. It’s far cheaper to find an error during the planning or analysis phase than it is to find the same error during the implementation or maintenance phase.

28. 6-28 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Knowledge Workers and Their Roles in the SDLC Analysis

29. 6-29 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Knowledge Workers and Their Roles in the SDLC Design IT specialists perform most of the activities during the design phase. IT specialists perform most of the activities during the design phase.

30. 6-30 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Knowledge Workers and Their Roles in the SDLC Develop Confirm any changes to business requirements. Confirm any changes to business requirements. Track the progress of tasks on the project plan to ensure timely delivery of the system. Track the progress of tasks on the project plan to ensure timely delivery of the system. IT specialists complete many of the activities in the development phase. IT specialists complete many of the activities in the development phase.

31. 6-31 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Knowledge Workers and Their Roles in the SDLC Test Review the test conditions to ensure the IT specialists have tested all of the system functionality and that every single test condition has passed. Review the test conditions to ensure the IT specialists have tested all of the system functionality and that every single test condition has passed. User acceptance testing (UAT) - determines if the system satisfies the business requirements and enables the knowledge workers to perform their jobs correctly. User acceptance testing (UAT) - determines if the system satisfies the business requirements and enables the knowledge workers to perform their jobs correctly.

32. 6-32 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Knowledge Workers and Their Roles in the SDLC Implement Attend training. Attend training. Ensure all of the knowledge workers have the required training in order to use the system correctly. Ensure all of the knowledge workers have the required training in order to use the system correctly.

33. 6-33 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Knowledge Workers and Their Roles in the SDLC Maintain Ensure all of the knowledge workers have the support they require in order to use the system. Ensure all of the knowledge workers have the support they require in order to use the system. Develop a help desk. Develop a help desk. Develop change request forms for your users to fill out if they require a change to the system. Develop change request forms for your users to fill out if they require a change to the system.

34. 6-34 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Knowledge Workers and Their Roles in the SDLC IT Specialists and Knowledge Workers Working Together Team Work Your Responsibilities During Each Phase of the Systems Development Life Cycle (p. 298)

35. 6-35 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Why Systems Fail 20% of systems are successful, 80% of systems fail. 20% of systems are successful, 80% of systems fail. Five primary reasons why systems fail include: Five primary reasons why systems fail include: 1. Unclear or missing requirements 2. Skipping SDLC phases 3. Failure to manage project scope 4. Failure to manage project plan 5. Changing technology

36. 6-36 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Why Systems Fail Unclear or Missing Requirements The business requirements drive the entire system. The business requirements drive the entire system. If they are not accurate or complete there is no way the system will be successful. If they are not accurate or complete there is no way the system will be successful.

37. 6-37 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Why Systems Fail Skipping SDLC Phases The first thing individuals tend to do when a project falls behind schedule is to start skipping phases in the SDLC. The first thing individuals tend to do when a project falls behind schedule is to start skipping phases in the SDLC. Skipping any of the phases is sure to lead to system failure. Skipping any of the phases is sure to lead to system failure.

38. 6-38 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Why Systems Fail Failure To Manage Project Scope The project manager must track the status of each activity and adjust the project plan if a activity is added or taking longer than expected. The project manager must track the status of each activity and adjust the project plan if a activity is added or taking longer than expected. Scope creep - occurs when the scope of the project increases. Scope creep - occurs when the scope of the project increases. Feature creep - occurs when developers add extra features that were not part of the initial requirements. Feature creep - occurs when developers add extra features that were not part of the initial requirements.

39. 6-39 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Why Systems Fail Failure To Manage Project Plan The project plan is the road map you follow during the development of the system. The project plan is the road map you follow during the development of the system. Developing the initial project plan is the easy. Developing the initial project plan is the easy. Managing, revising, and updating the project plan is the hard part. Managing, revising, and updating the project plan is the hard part.

40. 6-40 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Why Systems Fail Changing Technology Technology changes so fast that it’s almost impossible to deliver an information system without feeling the pain of changing technology. Technology changes so fast that it’s almost impossible to deliver an information system without feeling the pain of changing technology.

41. 6-41 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Insourcing Three choices for building a system include: Three choices for building a system include: 1. IT specialists within your organization - Insourcing 2. Knowledge workers such as yourself – Selfsourcing 3. Another organization – Outsourcing Insourcing - IT specialists within your organization will develop the system. Insourcing - IT specialists within your organization will develop the system.

42. 6-42 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Selfsourcing Selfsourcing (also called knowledge worker development or end user development) - the development and support of IT systems by knowledge workers with little or no help from IT specialists. Selfsourcing (also called knowledge worker development or end user development) - the development and support of IT systems by knowledge workers with little or no help from IT specialists. On Your Own How Have You Selfsourced? (p. 303)

43. 6-43 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Selfsourcing The Selfsourcing Process

44. 6-44 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Selfsourcing The Advantages of Selfsourcing Improves requirements determination. Improves requirements determination. Increases knowledge worker participation and sense of ownership. Increases knowledge worker participation and sense of ownership. Increases speed of systems development. Increases speed of systems development.

45. 6-45 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Selfsourcing Potential Pitfalls and Risks of Selfsourcing Inadequate knowledge worker expertise leads to inadequately developed systems. Inadequate knowledge worker expertise leads to inadequately developed systems. Lack of organizational focus creates “privatized” IT systems. Lack of organizational focus creates “privatized” IT systems. Insufficient analysis of design alternatives leads to subpar IT systems. Insufficient analysis of design alternatives leads to subpar IT systems. Lack of documentation and external support leads to short-lived systems. Lack of documentation and external support leads to short-lived systems.

46. 6-46 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing Developing Strategic Partnerships Outsourcing - the delegation of specific work to a third party for a specified length of time, at a specified cost, and at a specified level of service. Outsourcing - the delegation of specific work to a third party for a specified length of time, at a specified cost, and at a specified level of service.

47. 6-47 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing Developing Strategic Partnerships IT outsourcing takes on 1 of 4 forms: IT outsourcing takes on 1 of 4 forms: 1. Purchasing existing software. 2. Purchasing existing software and pay the publisher to make certain modifications. 3. Purchasing existing software and pay the publisher for the right to make modifications yourself. 4. Outsourcing the development of an entirely new and unique system for which no software exists.

48. 6-48 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing Developing Strategic Partnerships Team Work How Many Outsourcing Companies Are There? (p. 306)

49. 6-49 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing The Outsourcing Process

50. 6-50 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing The Outsourcing Process Steps of the outsourcing process Steps of the outsourcing process 1. Plan 2. Define project scope 3. Select a target system 4. Establish logical requirements

51. 6-51 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing The Outsourcing Process 5. Develop a request for proposal  Request for proposal (RFP) - a formal document that describes in detail your logical requirements for a proposed system and invites outsourcing organizations to submit bids for its development. 6. Evaluate request for proposal returns and choose a vendor 7. Test and accept solution 8. Monitor and reevaluate

52. 6-52 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing The Advantages and Disadvantages of Outsourcing Advantages of outsourcing include: Advantages of outsourcing include:  Focus on unique core competencies.  Exploit the intellect of another organization.  Better predict future costs.  Acquire leading-edge technology.  Reduce costs.  Improve performance accountability.

53. 6-53 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing The Advantages and Disadvantages of Outsourcing Disadvantages of outsourcing include: Disadvantages of outsourcing include:  Reduces technical know-how for future innovation.  Reduces degree of control.  Increases vulnerability of strategic information.  Increases dependency on other organizations.

54. 6-54 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing The Advantages and Disadvantages of Outsourcing On Your Own A Request for Proposal and the Systems Development Life Cycle (p. 311)

55. 6-55 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Prototyping Prototyping - the process of building a model that demonstrates the features of a proposed product, service, or system. Prototyping - the process of building a model that demonstrates the features of a proposed product, service, or system. Prototype - a model of a proposed product, service, or system. Prototype - a model of a proposed product, service, or system. Proof-of-concept prototype - used to prove the technical feasibility of a proposed system. Proof-of-concept prototype - used to prove the technical feasibility of a proposed system. Selling prototype - used to convince people of the worth of a proposed system. Selling prototype - used to convince people of the worth of a proposed system.

56. 6-56 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Prototyping The Prototyping Process

57. 6-57 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Prototyping The Prototyping Process The prototyping process involves four steps: The prototyping process involves four steps: 1. Identify basic requirements 2. Develop initial prototype 3. Knowledge worker review 4. Revise and enhance the prototype

58. 6-58 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Prototyping The Advantages of Prototyping  Encourages active knowledge worker participation.  Encourages active knowledge worker participation.  Helps resolve discrepancies among knowledge workers.  Helps resolve discrepancies among knowledge workers.  Gives knowledge workers a feel for the final system.  Gives knowledge workers a feel for the final system.  Helps determine technical feasibility.  Helps sell the idea of a proposed system.  Helps sell the idea of a proposed system.

59. 6-59 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Prototyping The Disadvantages of Prototyping  Leads people to believe the final system will follow shortly.  Gives no indication of performance under operational conditions.  Leads the project team to forgo proper testing and documentation.

60. 6-60 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Closing Case Study One Some Prototypes Hit, Some Miss, and Some We Are Just Not Sure About There are many hilarious prototypes that failed such as garlic cake and toaster eggs. There are many hilarious prototypes that failed such as garlic cake and toaster eggs. How can prototyping help you develop a successful system? How can prototyping help you develop a successful system?

61. 6-61 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Closing Case Study Two Al’s Barbeque Restaurant Automating a manual business is an extremely difficult task. Automating a manual business is an extremely difficult task. How can the systems development life cycle help you implement a new system? How can the systems development life cycle help you implement a new system?

62. 6-62 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Summary Student Learning Outcomes 1. List the seven steps in the systems development life cycle and an associated activity for each step. 2. List four reasons why your participation during the systems development life cycle is critical. 3. Describe three of the five reasons why projects fail.

63. 6-63 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Summary Student Learning Outcomes 4. Define the three different ways you can staff a system development project. 5. List two of the three advantages of selfsourcing. 6. Describe prototyping and profile an example of a prototype. 7. Describe two of the five advantages of prototyping.

64. 6-64 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Summary Assignments & Exercises 1.SDLC and the real world 2.How creative are you? 3.Request for proposal 4.Understanding insourcing 5.Managing the project plan 6.Why prototype? 7.Business requirements 8.Why projects fail 9.Construction and the SDLC

65. 6-65 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Visit the Web to Learn More www.mhhe.com/haag Using your computer for more than work Using your computer for more than work Animating your computer screen Animating your computer screen Protecting your computer investment Protecting your computer investment Searching for freeware and shareware Searching for freeware and shareware Project planning and project management Project planning and project management