Chapter 1 Information Technology Principles, Practices, and

1、1Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallJames A. SennsInformation Technology, 3rd EditionChapter 10Launching Information Technology Applications Projects2Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallObjectives Describe the origin of IT applications

2、 in business and understand why they have become so prominent. Identify the distinguishing characteristics of an IT application. Explain the benefits of IT applications to users and enterprise.3Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallObjectives (Continued) Explain how a s

3、ystems project begins and how its desirability is determined. Describe the six phases of the systems development life cycle. Explain the importance of continual evaluation and evolution in IT systems.4Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallWhat Is an IT Application?Defin

4、ition Single-user System/Personal System: An IT system used by only one person. A system that stands alone and is not interconnected with other companies or shared by other people. Enterprise System: Usually involves the same types of components as a personal system, plus server or mainframe, databa

5、se, and network. It is generally a shared system.5Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallWhat Is an IT Application?Characteristics of Personal Systems Designed for Hands-On Usage Hands-on System: A system in which a user enters data and information, directs processing, a

6、nd determines the types of output to be generated. Tailored to Personal Requirements and Preferences Used to Improve Personal Performance6Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallWhat Is an IT Application? Characteristics of Enterprise Systems (Continued) Designed for Shar

7、ed Use Designed for Sharing Data Resources Designed to Connect a Variety of Users Designed for Larger Size and Scope7Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallWhat Is an IT Application? Characteristics of Personal and Enterprise Systems8Senn, Information Technology, 3rd Edi

8、tion 2004 Pearson Prentice HallWhat Is an IT Application? Impact of IT Applications Improved Productivity Productivity: The relationship between the results of an activity (output) and the resources used to create those results (inputs). Personal Productivity Software: Software packages that permit

9、activities to be completed more quickly, allow more activities to be completed in a particular period of time, or allow a task to be completed with fewer resources.9Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallWhat Is an IT Application? Impact of IT Applications (Continued)10S

10、enn, Information Technology, 3rd Edition 2004 Pearson Prentice HallWhat Is an IT Application? Impact of IT Applications (Continued) Greater Effectiveness Effectiveness: The extent to which desirable results are achieved. Increased Creativity and Innovation11Senn, Information Technology, 3rd Edition

11、2004 Pearson Prentice HallThe Origin of Enterprise System ProjectsDefinitionSystems Development: The process of examining a business situation, designing a system solution to improve that situation, and acquiring the human, financial, and information technology resources needed to develop and implem

12、ent the solution.Project Management: The process of planning, organizing, integrating, and overseeing the development of an IT application to ensure that the projects objectives are achieved and the system is implemented according to expectations.12Senn, Information Technology, 3rd Edition 2004 Pear

13、son Prentice HallThe Origin of Enterprise System ProjectsProject Proposal Project Proposal: A proposal for a systems projects prepared by users or systems analysts and submitted to a steering committee for approval. Steering Committee Review Steering Committee: A group of people from various functio

14、nal areas of a business that determines whether a systems development project proposal is desirable and should be pursued.13Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Origin of Enterprise System ProjectsThe Systems AnalystThe System Analyst Systems Analyst: The IT profes

15、sional responsible for working with users to determine a systems requirements and for describing the features needed in the system. System Designer: The IT professional responsible for doing the technical work of designing the system and its software. Programmer/Analyst: A person who has joint respo

16、nsibility for determining system requirements and developing and implementing the systems.14Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Origin of Enterprise System ProjectsThe Systems Analyst (Continued) The System Analyst Web Developer: Expected to have additional capabi

17、lities that enable him or her to use expertise in creating IT applications that will involve the Internet or company intranets and extranets, Web browsers, and the display of information using browsers.15Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life

18、 CycleDefinition Systems Development Life Cycle (SDLC): The six-phased set of activities that brings about a new IT application. Problem Recognition/Preliminary Investigation Requirements Determination Systems Design Development and Construction Implementation Evaluation and Continuing Evolution16Se

19、nn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life CycleDefinition (Continued)17Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life CycleProblem Recognition/Preliminary Investigation Preliminary Investigation: T

20、he first phase of the systems development life cycle, in which the merits and feasibility of a project proposal are determined. Three types of feasibility Operational Financial/Economic Technical18Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life CycleR

21、equirements Determination Requirement: A feature that must be included in a system. Requirements Determination: The second phase of the systems development life cycle, in which the current business situation is studied to determine who is involved, what data and information are needed, and how the c

22、urrent system can be improved.19Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life CycleRequirements Determination (Continued) Two types of Improvement Process Improvement: An improvement in the way a business works. Process: A structured activity that l

23、eads to a set of results (output). Business Improvement Offering New Products and Services Speeding Up Business Processes Reducing the Cost of Products and Services Entering New Regions or Markets20Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life Cycle

24、Requirements Determination (Continued)21Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life CycleRequirements Determination (Continued)22Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life CycleSystems DesignSy

25、stems Design: The third phase of the systems development life cycle, in which requirements are translated into design specifications.Three steps Preliminary (Conceptual) Design Prototyping: A working model of an IT application. Detailed (Physical) Design Output: Information and Results Layout Descri

26、ption: A chart that shows the exact location of data and information on a computer screen or in a printed report.23Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life CycleSystems Design (Continued)24Senn, Information Technology, 3rd Edition 2004 Pearson

27、Prentice HallThe Systems Development Life CycleSystems Design (Continued)25Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life CycleSystems Design (Continued) Three steps Detailed (Physical) Design Input: Data and Information for Processing Stored Data: D

28、atabases and Files Processing and Procedures Controls26Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life CycleSystems Design (Continued)27Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life CycleSystems Desig

29、n28Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life CycleDevelopment and ConstructionPrincipal Activities Acquisition of Software and Services Programming Testing Software Testing: The testing of software programs to ensure that the software will not p

30、roduce unexpected or incorrect results or interruptions during processing. Test Data: Experimental files used to test software. System Testing: The testing of a complete system software, procedures, and guidelines.29Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Deve

31、lopment Life CycleDevelopment and Construction (Continued)30Senn, Information Technology, 3rd Edition 2004 Pearson Prentice HallThe Systems Development Life CycleImplementationThree important aspects of Implementation Training: The process by which people are taught how to use a system. Site Prepara

32、tion: The activities involved in preparing for the installation of a new system. Conversion Strategies Conversion Plan: A description of all the activities that must occur to change over to a new system. Direct Cut Over Strategy: A conversion plan in which people abruptly stop using an old system and immediately begin using a new one.31Senn, Information Technology, 3rd Edition