1 / 64

Chapter 1 Assuming the Role of the Systems Analyst

Chapter 1 Assuming the Role of the Systems Analyst. Systems Analysis and Design Kendall & Kendall Sixth Edition. Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich. Chapter 1 The Systems Development Environment. Major Topics.

rod
Download Presentation

Chapter 1 Assuming the Role of the Systems Analyst

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. Chapter 1Assuming the Role of the Systems Analyst Systems Analysis and Design Kendall & Kendall Sixth Edition

  2. Modern Systems Analysisand DesignFourth EditionJeffrey A. Hoffer Joey F. GeorgeJoseph S. Valacich Chapter 1 The Systems Development Environment

  3. Major Topics • Information systems • Phases of analysis and design • System maintenance • CASE tools • Alternate methodologies 2005 Pearson Prentice Hall

  4. Information • Information is an organizational resource, which must be managed as carefully as other resources. • Costs are associated with information processing. • Information processing must be managed to take full advantage of its potential. 2005 Pearson Prentice Hall

  5. Information Systems Analysis and Design • Complex organizational process whereby computer-based information systems are developed and maintained • Application Software • Computer software designed to support organizational functions or processes • Systems Analyst • Organizational role most responsible for analysis and design of information systems

  6. A Modern Approach to Systems Analysis and Design • 1950s: focus on efficient automation of existing processes • 1960s: advent of 3GL, faster and more reliable computers • 1970s: system development becomes more like an engineering discipline • 1980s: major breakthrough with 4GL, CASE tools, object oriented methods • 1990s: focus on system integration, GUI applications, client/server platforms, Internet • The new century: Web application development, wireless PDAs, component-based applications

  7. Categories Information systems fall into one of the following eight categories: • Transaction processing systems (TPS). • Office automation systems (OAS). • Knowledge work systems (KWS). • Management information systems (MIS). • Decision support systems (DSS). • Expert systems (ES) and Artificial Intelligence (AI). • Group decision support systems (GDSS) and Computer-Supported Collaborative Work Systems. • Executive support systems (EES). 2005 Pearson Prentice Hall

  8. Types of Information Systemsand Systems Development • Transaction Processing Systems (TPS) • Automate handling of data about business activities (transactions) • Process orientation • Management Information Systems (MIS) • Converts raw data from transaction processing system into meaningful form • Data orientation • Decision Support Systems (DSS) • Designed to help decision makers • Provides interactive environment for decision making • Involves data warehouses, executive information systems (EIS) • Database, model base, user dialogue

  9. Types of Information Systemsand Systems Development (cont.)

  10. New Technologies New technologies are being integrated into traditional systems: • Ecommerce uses the Web to perform business activities. • Enterprise Resource Planning (ERP) has the goal of integrating many different information systems within the corporation. • Wireless and handheld devices, including mobile commerce (mcommerce). • Open source software. 2005 Pearson Prentice Hall

  11. 2005 Pearson Prentice Hall

  12. Advantages of Using the Web The benefits of using the Web are: • Increasing awareness of the availability of the service, product, industry, person, or group. • 24-hour access for users. • Standard interface design. • Creating a global system. 2005 Pearson Prentice Hall

  13. Nature of Analysis and Design Systems analysis and design is a systematic approach to: • Identifying problems, opportunities, and objectives. • Analyzing the information flows in organizations. • Designing computerized information systems to solve a problem. 2005 Pearson Prentice Hall

  14. Systems Analyst • Systems analysts act as: • Outside consultants to businesses. • Supporting experts within a business. • As change agents. • Analysts are problem solvers, and require communication skills. • Analysts must be ethical with users and customers. 2005 Pearson Prentice Hall

  15. Developing Information Systems and the SDLC System Development Methodology • Standard process followed in an organization • Consists of: • Analysis • Design • Implementation • Maintenance

  16. Systems Development Life Cycle (SDLC) • Traditional methodology for developing, maintaining, and replacing information systems • Phases in SDLC: • Planning • Analysis • Design • Implementation • Maintenance Hoffer, George & Valacich

  17. Traditional Waterfall SDLC One phase begins when another completes, little backtracking and looping

  18. Problems with Waterfall Approach • System requirements “locked in” after being determined (can't change) • Limited user involvement (only in requirements phase) • Too much focus on milestone deadlines of SDLC phases to the detriment of sound development practices

  19. Alternatives to Traditional Waterfall SDLC • Prototyping • CASE tools • Joint Application Design (JAD) • Rapid Application Development (RAD) • Agile Methodologies • eXtreme Programming • ETHICS. • Project Champions. • Soft Systems Methodology. • Multi-view.

  20. Standard and Evolutionary Views of SDLC

  21. 2005 Pearson Prentice Hall

  22. Systems Development Life Cycle • The systems development life cycle is a systematic approach to solving business problems. • It is divided into seven phases. • Each phase has unique activities. • Kendall & Kendall 2005 Pearson Prentice Hall

  23. 2005 Pearson Prentice Hall

  24. Phase 1 • Identifying: • Problems. • Opportunities. • Objectives. • Personnel involved: • Analyst. • User management. • Systems management. 2005 Pearson Prentice Hall

  25. Phase 2 • Determining information requirements: • Interview management, operations personnel. • Gather systems/operating documents. • Use questionnaires. • Observe the system and personnel involved. • Learn the who, what, where, when, and how, and the why for each of these. 2005 Pearson Prentice Hall

  26. Phase 2 (Continued) • Personnel involved: • Analyst. • User management. • User operations workers. • Systems management. 2005 Pearson Prentice Hall

  27. Phase 3 • Analyzing system needs: • Create data flow diagrams. • Document procedural logic for data flow diagram processes. • Complete the data dictionary. • Make semistructured decisions. • Prepare and present the system proposal. • Recommend the optimal solution to management. 2005 Pearson Prentice Hall

  28. Phase 3 (Continued) • Personnel involved: • Analyst. • User management. • Systems management. 2005 Pearson Prentice Hall

  29. Phase 4 • Designing the recommended system: • Design the user interface. • Design output. • Design input. • Design system controls. • Design files and/or database. • Produce program specifications. • Produce decision trees or tables. 2005 Pearson Prentice Hall

  30. Phase 4 (Continued) • Personnel involved: • Analyst. • System designer. • User management. • User operations workers. • Systems management. 2005 Pearson Prentice Hall

  31. Phase 5 • Developing and documenting software: • Design computer programs using structure charts, Nassi-Schneiderman charts, and pseudocode. • Walkthrough program design. • Write computer programs. • Document software with help files, procedure manuals, and Web sites with Frequently Asked Questions. 2005 Pearson Prentice Hall

  32. Phase 5 (Continued) • Personnel involved: • Analyst. • System designer. • Programmers. • Systems management. 2005 Pearson Prentice Hall

  33. Phase 6 • Testing and maintaining the system: • Test and debug computer programs. • Test the computer system. • Enhance system. 2005 Pearson Prentice Hall

  34. Phase 6 (Continued) • Personnel involved: • Analyst. • System designer. • Programmers. • Systems management. 2005 Pearson Prentice Hall

  35. Phase 7 • Implementing and evaluating the system: • Plan conversion. • Train users. • Purchase and install new equipment. • Convert files. • Install system. • Review and evaluate system. 2005 Pearson Prentice Hall

  36. Phase 7 (Continued) • Personnel involved: • Analyst. • System designer. • Programmers. • User management. • User operations workers. • Systems management. 2005 Pearson Prentice Hall

  37. System Maintenance • System maintenance is: • Removing undetected errors, and • Enhancing existing software. • Time spent on maintenance typically ranges from 48-60 percent of total time. 2005 Pearson Prentice Hall

  38. System Enhancements Systems are enhanced for the following reasons: • Adding additional features to the system. • Business and governmental requirements change over time. • Technology, hardware, and software are rapidly changing. 2005 Pearson Prentice Hall

  39. The Heart of the Systems Development Process Current practice combines analysis, design, and implementation into a single iterative and parallel process of activities

  40. Joint Application Design (JAD) • Structured process involving users, analysts, and managers • Several-day intensive workgroup sessions • Purpose: to specify or review system requirements

  41. Rapid Application Development (RAD) • Methodology to decrease design and implementation time • Involves: prototyping, JAD, CASE tools, and code generators

  42. Prototyping Iterative development process: Requirements quickly converted to a working system System is continually revised Close collaboration between users and analysts

  43. Agile Methodologies • Motivated by recognition of software development as fluid, unpredictable, and dynamic • Three key principles • Adaptive rather than predictive • Emphasize people rather than roles • Self-adaptive processes

  44. eXtreme Programming (XP) • Extreme programming takes good software development practices and pushes them to the limit. • It is based on: • Values. • Principles. • Core practices. 2005 Pearson Prentice Hall

  45. eXtreme Programming • Short, incremental development cycles • Automated tests • Two-person programming teams • Coding and testing operate together • Advantages: • Communication between developers • High level of productivity • High-quality code

  46. Extreme Programming (XP) (Continued) • Extreme programming values are: • Communication. • Simplicity. • Feedback. • Courage. 2005 Pearson Prentice Hall

  47. Object-Oriented Analysis and Design • Object-oriented (O-O) analysis and design is used to build object-oriented programs. • O-O programming examines the objects of a system. • Objects are grouped into classes for optimal reuse and maintainability. 2005 Pearson Prentice Hall

  48. Based on objects rather than data or processes • Object: a structure encapsulating attributes and behaviors of a real-world entity • Object class: a logical grouping of objects sharing the same attributes and behaviors • Inheritance: hierarchical arrangement of classes enable subclasses to inherit properties of superclasses

More Related