1 / 50

System Analysis Theory: Overview of IS Projects & Management

This course provides an overview of information system projects and their management, including challenges, motivations, and frameworks. Topics include IT strategy, knowledge management, operations research, and decision science.

williamwest
Télécharger la présentation

System Analysis Theory: Overview of IS Projects & Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MIS 370 System Analysis Theory Dr. Honghui Deng Assistant Professor MIS Department UNLV

  2. Educational Background Ph.D.,Red McCombs School of Business, University of Texas at Austin, 2002 --MSIS, OR/OM, Finance --Co-Supervised by Dr.s William W. Cooper & Patrick Brockett Visiting Scholar, Red McCombs School of Business, UT-Austin, 1997-1999 --Marketing Department MBA, College of Business Administration, Chongqing University, China, 1994 --Marketing & Finance B.E, Chongqing University, 1990 --Electronic and Computer Engineering

  3. Working Experience Academic Experience: Assistant Professor, School of Business, the University of Nevada, Las Vegas Research Associate, Center of Risk Management & Insurance, School of Business, University of Texas at Austin Instructor, MSSTC Program, The Innovation Creativity Capital Institute (IC2), Visiting Professor, Marketing Dept., School of Business, UT Austin Project Official, The Ministry of Education of China, Beijing, China Lecturer, College of Electronic Information Engineering, Chongqing University, China Industrial Experience: StrategyConsultant，Rapp Collins Inc. of Omnicom Group Ass. of Director & Consultant，IC2 and Texas Tech. Incubator Co-Founder & CEO, HHD Consulting LLC. Membership: The Institute of Operations Research and the Management Sciences (INFORMS) Association of Risk Management & Insurance Association for Information Systems (AIS)

  4. Current Research • IT Strategy & Organization • Knowledge Management • Operations Research • Management Science • Risk Management and Insurance • Decision Science • Data Communication & Networks

  5. Teaching Experience • Data Communications & Networks • Management Information Systems • Commercialization Strategy • Statistics I • Applied Information Technology • Supply Chain Management & Operation Strategy • Project Management

  6. Agenda for Today • Information System Project Landscape • Overview of syllabus and course objectives • Student information sheet • Term Project Group Assignment • Chapter 1, 2

  7. New Challenge of Information Technology • The New Trend of Knowledge Economy/Firm • Dell Computer Inc. • Increasing Digitalization of IT Industry • Amazon. com, CD.com etc.

  8. In the first half of the twentieth century industry replaced agriculture, in the second half of the twentieth century –“service” has replaced “manufacturing” -and right now, the knowledge industry is beginning to replace the others. −−George Kotzmetzk

  9. George Kotzmetzk

  10. Stage of Information Systems • A collection of data is not information. • A collection of information is not knowledge. • A collection of knowledge is not wisdom. • A collection of wisdom is not truth.

  11. Project Management Framework

  12. Motivation to study IS project • Information system projects are notorious for budget overrun and delay. • More importantly, the challenges of satisfying rising expectations for information systems require better management of project development.

  13. Motivation to study IS project • A 1995 Standish Group study found that only • a. 16.2% • b. 35.4% • c. 49.3% • d. 62.9% of IT/IS projects were successful.

  14. 1. Motivation to study IS project • The same study also found that • a. 31% • b. 22% • c. 17.3% • d. 37.5% of IS projects were cancelled before completion, costing over $81B in the U.S. alone.

  15. Motivation to study IS project • Studies have shown that • a. 73% • b. 55% • c. 42.3% • d. 31.5% of all ERP implementations fail!

  16. Motivation to study IS project • Of the few companies that actually do implement an ERP system, • _____% of the implementations run • _____% behind schedule and cost • _____% more than originally planned.

  17. Growth in PMP Certification

  18. MIS 370 System Analysis Theory Chapter 1 THE CONTEXT OF SYSTEMS ANALYSIS AND DESIGN METHODS

  19. Information Systems Framework • System is a group of interrelated components that function together to achieve a desired result. • Information System (IS) is an arrangement of people, data, processes, and information technology that interact to collect, process, store, and provide as output the information needed to support an organization. • Information technology (IT) is a contemporary term that describes the combination of computer technology (hardware and software) with telecommunications technology (data, image, and voice networks).

  20. People Data Software Hardware Network INFORMATION SYSTEMS What is an Information System?

  21. Types of Information System • A transaction processing system (TPS) is an information system that captures and processes data about business transactions. • A management information system (MIS) is an information system that provides for management-oriented reporting based on transaction processing and operations of the organization. • A decision support system (DSS) is an information system that either helps to identify decision making opportunities or provides information to help make decisions. • An executive information system (EIS) is an information system designed for top-level managers that integrates data from all over the organization into “at-a-glance” graphical indicators and controls. • An expert system (ES) is an information system that captures the expertise of workers and then simulates that expertise to the benefit of nonexperts. • An office automation system (OAS) is an information system that supports the wide range of business office activities that provide for improved work flow between workers.

  22. INTERRELATIONSHIPS AMONG SYSTEMS

  23. IS Stakeholders (I) • A stakeholder is any person who has an interest in an existing or proposed information system. Stakeholders can be technical or non-technical workers. They may also include both internal and external workers. • Information workers are those workers whose jobs involve the creation, collection, processing, distribution, and use of information. • Knowledge workers are a subset of information workers whose responsibilities are based on a specialized body of knowledge.

  24. IS Stakeholders (II) • System owners – an information system’s sponsor and executive advocate, usually responsible for funding the project of developing, operating, and maintaining the information system.

  25. IS Stakeholders (III) • System users – a “customer” who will use or is affected by an information system on a regular basis – capturing, validating, entering, responding to, storing, and exchanging data and information. • Internal users • Clerical and service workers • Technical and professional staff • Supervisors, middle managers, and executive managers • External users • Remote and mobile users (internal but disconnected)

  26. IS Stakeholders (IV) • System designer – a technical specialist who translates system users’ business requirements and constraints into technical solution. She or he designs the computer databases, inputs, outputs, screens, networks, and software that will meet the system users’ requirements. • System builders – a technical specialist who constructs information systems and components based on the design specifications generated by the system designers.

  27. IS Stakeholders (V) • Systems analyst – a specialist who studies the problems and needs of an organization to determine how people, data, processes, and information technology can best accomplish improvements for the business. • A programmer/analyst (or analyst/programmer) includes the responsibilities of both the computer programmer and the systems analyst. • A business analyst focuses on only the nontechnical aspects of systems analysis and design.

  28. Systems Analyst Skills • Working knowledge of information technology • Computer programming experience and expertise • General business knowledge • General problem-solving skills • Good interpersonal communication skills • Good interpersonal relations skills • Flexibility and adaptability • Character and ethics

  29. Other Stakeholders • External Service Provider (ESP) – a systems analyst, system designer, or system builder who sells his or her expertise and experience to other businesses to help those businesses purchase, develop, or integrate their information systems solutions; may be affiliated with a consulting or services organization. • Project Manager – an experienced professional who accepts responsibility for planning, monitoring, and controlling projects with respect to schedule, budget, deliverables, customersatisfaction, technical standards, and system quality.

  30. Business Drivers for IS • Globalization of the Economy • Electronic Commerce and Business • Security and Privacy • Collaboration and Partnership • Knowledge Asset Management • Continuous Improvement and Total Quality Management • Business Process Redesign

  31. Technology Drivers for IS • Networks and the Internet • Mobile and Wireless Technologies • Object Technologies • Collaborative Technologies • Enterprise Applications

  32. Technology Drivers for IS--Video 12. Communication in the future

  33. Enterprise Applications - ERP • Enterprise Resource Planning (ERP) – a software application that fully integrates information systems that span most or all of the basic, core business functions. • An ERP solution is built around a common database shared by common business functions. • Representative ERP vendors: • SSA • Oracle/Peoplesoft • SAP AG

  34. Enterprise Applications - SCM • Supply Chain Management (SCM) – a software application that optimizes business processes for raw material procurement through finished product distribution by directly integrating the logistical information systems of organizations with those of their suppliers and distributors. • Representative SCM vendors: • i2 Technologies • Manugistics • SAP • SCT

  35. Enterprise Applications - CRM • Customer Relationship Management (CRM) – a software application that provides customers with access to a business’s processes from initial inquiry through post-sale service and support. • Representative CRM vendors: • SAP • BroadVision • E.piphany • Kana • Amdocs • Oracle/Peoplesoft • Siebel

  36. Enterprise Applications - EAI • Enterprise Application Integration (EAI) – the process and technologies used to link applications to support the flow of data and information between those applications. • Middleware – software (usually purchased) used to translate and route data between different applications. • Representative EAI vendors: • BEA Systems • IBM (MQSeries) • Mercator Software • TIBCO Software

  37. System Development Process • System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders use to develop and maintain information systems and software. • A general problem-solving approach • Identify the problem. • Analyze and understand the problem. • Identify solution requirements or expectations. • Identify alternative solutions and choose the “best” course of action. • Design the chosen solution. • Implement the chosen solution. • Evaluate the results. If the problem is not solved, return to step 1 or 2 as appropriate.

  38. System Development Process Overview • System initiation – the initial planning for a project to define initial business scope, goals, schedule, and budget. • System analysis – the study of a business problem domain to recommend improvements and specify the business requirements and priorities for the solution. • System design – the specification or construction of a technical, computer-based solution for the business requirements identified in a system analysis. • System implementation – the construction, installation, testing, and delivery of a system into production.

  39. Project and Process Management • Project management – the activity of defining, planning, directing, monitoring, and controlling a project to develop an acceptable system within the allotted time and budget. • Process management – the ongoing activity that defines, improves, and coordinates the use of an organization’s chosen methodology (the “process”) and standards for all system development projects.

  40. MIS 370 System Analysis Theory Chapter 2 INFORMATION SYSTEM BUILDING BLOCKS

  41. Learning Objectives • Differentiate between front- and back-office information systems. • Describe the role of information systems architecture in systems development. • Identify three high-level goals that provide system owners and system users with a perspective of an information system. • Identify three technologies that provide system designers and builders with a perspective of an information system. • Describe four building blocks of the KNOWLEDGE goal for an information system. • Describe four building blocks of the PROCESS goal for an information system. • Describe four building blocks of the COMMUNICATIONS goal for an information system. • Describe the role of network technologies as it relates to Knowledge, Processes, and Communications building blocks.

  42. Front- and Back-Office IS • Front-officeinformation systems support business functions that extend out to the organization’s customers (or constituents). • Marketing • Sales • Customer management • Back-officeinformation systems support internal business operations of an organization, aw well as reach out to suppliers (of materials, equipment, supplies, and services). • Human resources • Financial management • Manufacturing • Inventory control

  43. Information Systems Architecture • Information systems architecture - a unifying framework into which various stakeholders with different perspectives can organize and view the fundamental building blocks of information systems.

  44. Focuses for Information Systems • Data/Knowledge— the raw material used to create useful information. • Process— the activities (including management) that carry out the mission of the business. • Communication— how the system interfaces with its users and other information systems.

  45. Views of Data/Knowledge • System owners’ view • Interested not in raw data but in information that adds new business knowledge and information that help managers make intelligent decisions. • Business entities and business rules. • System users’ view • View data as something recorded on forms, stored in file cabinets, recorded in books and binders, organized into spreadsheets, or stored in computer files and databases. • Tend to focus on the business issues as they pertain to the data. • Data requirement – a representation of users’ data in terms of entities, attributes, relationships, and rules independent of data technology. • System designers’ view • Data structures, database schemas, fields, indexes, and constraints of particular database management system (DBMS). • System builders’ view • SQL • DBMS or other data technologies

  46. Views of Process (I) • System owners’ view • Concerned with high-level processes called business functions. • Business function – a group of related processes that support the business. Functions can be decomposed into other subfunctions and eventually into processes that do specific tasks. • A cross-functionalinformation system – a system that supports relevant business processes from several business functions without regard to traditional organizational boundaries such as divisions, departments, centers, and offices.

  47. Views of Process (II) • System users’ view • Concerned with work that must be performed to provide the appropriate responses to business events. • Business processes – activities that respond to business events. • Process requirements – a user’s expectation of the processing requirements for a business process and its information systems. • Policy – a set of rules that govern a business process. • Procedure – a step-by-step set of instructions and logic for accomplishing a business process. • Work flow – the flow of transactions through business processes to ensure appropriate checks and approvals are implemented.

  48. Views of Process (III) • System designers’ view • Concerned with which processes to automate and how to automate them • Constrained by limitations of application development technologies being used • Software specifications – the technical design of business processes to be automated or supported by computer programs to be written by system builders. • System builders’ view • Concerned with programming logic that implements automated processes • Application program – a language-based, machine-readable representation of what a software process is supposed to do, or how a software process is supposed to accomplish its task. • Prototyping – a technique for quickly building a functioning, but incomplete model of the information system using rapid application development tools.

  49. Views of Communication (I) • System owners’ view • Concerned with communications scope of an information system. • Who (which business units, employees, customers, and partners) must interact with the system? • Where are these business units, employees, customers, and partners located? • What other information systems will the system have to interface with? • System users’ view • Concerned with the information system’s inputs and outputs.

  50. Views of Communication (II) • System designers’ view • Concerned with the technical design of both the user and the system-to-system communication interfaces. • Interface specifications – technical designs that document how system users are to interact with a system and how a system interacts with other systems. • User dialogue – a specification of how the user moves from window to window or page to page, interacting with the application programs to perform useful work. • System builders’ view • Concerned with the construction, installation, testing and implementation of user and system-to-system interface solutions. • Middleware – utility software that allows application software and systems software that utilize differing technologies to interoperate.

More Related