1 / 36

BUSINESS SYSTEMS: ANALYSIS DESIGN AND MANAGEMENT

BUSINESS SYSTEMS: ANALYSIS DESIGN AND MANAGEMENT . COURSE INTRODUCTION SYLLABUS REVIEW INTRODUCTION TO SYSTEMS DEVELOPMENT VALUE CHAIN AND INFORMATION SYSTEMS SYSTEMS ANALYSIS AND DESIGN. SYSTEMS DEVELOPMENT. An organizational approach to systems development

aldis
Télécharger la présentation

BUSINESS SYSTEMS: ANALYSIS DESIGN AND 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. BUSINESS SYSTEMS: ANALYSIS DESIGN AND MANAGEMENT COURSE INTRODUCTION SYLLABUS REVIEW INTRODUCTION TO SYSTEMS DEVELOPMENT VALUE CHAIN AND INFORMATION SYSTEMS SYSTEMS ANALYSIS AND DESIGN

  2. SYSTEMS DEVELOPMENT An organizational approach to systems development is driven by methodologies, techniques, and tools 2

  3. APPROACHES TO SYSTEMS DEVELOPMENT 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 3

  4. APPROACHES TO SYSTEMS DEVELOPMENT 1980s: major breakthrough with 4GL, CASE tools, object oriented methods 1990s: focus on system integration, GUI applications, client/server platforms, Internet Current: Web application development, wireless PDAs, component-based applications 4

  5. Developing Information Systems System Development Methodology is a standard process followed in an organization to conduct all the steps necessary to analyze, design, implement, and maintain information systems. 5

  6. Business System Goals • Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization. • The primarily goal is to create value for the organization.

  7. Organizational Value Chain

  8. Information Systems in the Organizational Value Chain

  9. PORTER’S COMPETITIVE FORCES MODEL NEW MARKET ENTRANTS SUBSTITUTE PRODUCTS & SERVICES TRADITIONAL COMPETITION THE FIRM SUPPLIERS CUSTOMERS

  10. Value Chain Integration

  11. Standard and Evolutionary Views of SDLC 11

  12. SYSTEM ANALYSIS WHAT SHOULD THE SYSTEM CONTAIN ? REQUIREMENTS ANALYSIS DATA COLLECTION INTERVIEWS, QUESTIONNAIRES, JAD,.. PROBLEM USERS DON’T ALWAYS KNOW WHAT THEY WANT

  13. SYSTEM DESIGN HOW DO WE MEET THE REQUIREMENTS ? MULTIPLE DESIGNS CHOSING A DESIGN CONSTRAINTS TIME, MONEY,RESOURCES,...

  14. Construction Program building Program and system testing Installation Conversion strategy Training plan Support plan Implementation

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

  16. Standard and Evolutionary Views of SDLC 16

  17. Approaches to Improving Development Prototyping Computer-Aided Software Engineering (CASE) Tools Joint Application Design (JAD) Rapid Application Development (RAD) Agile Methodologies eXtreme Programming 17

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

  19. Prototyping (Cont.) 19

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

  21. Rapid Application Development (RAD) Methodology to radically decrease design and implementation time. Involves: extensive user involvement, prototyping, JAD sessions, integrated CASE tools, and code generators. 21

  22. Rapid Application Development (RAD) (Cont.) 22

  23. 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. 23

  24. Object-Oriented Analysis and Design (OOAD) Based on objects rather than data or processes. Object: a structure encapsulating attributes and behaviors of a real-world entity. 24

  25. Object-Oriented Analysis and Design (OOAD) (Cont.) 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. 25

  26. Rational Unified Process (RUP) An object-oriented systems development methodology. RUP establishes four phase of development: inception, elaboration, construction, and transition. Each phase is organized into a number of separate iterations. 26

  27. Phases of OOSAD-based Development Figure 1-14 Phases of OOSAD-based development 27

  28. Computer-Aided Software Engineering (CASE) Tools Diagramming tools enable graphical representation. Computer displays and report generators help prototype how systems “look and feel”. Analysis tools automatically check for consistency in diagrams, forms, and reports. Central repository for integrated storage of diagrams, reports, and project management specifications. 28

  29. Computer-Aided Software Engineering (CASE) Tools Documentation generators standardize technical and user documentation. Code generators enable automatic generation of programs and database code directly from design documents, diagrams, forms, and reports. 29

  30. CASE Tools 30

  31. PROJECT MANAGEMENT • INFORMATION SYSTEMS PROJECTS ARE NOTORIOUS FOR BEING FAILURES • EXAMPLES ? • PROBLEMS • USER EXPECTATIONS, CHANGING REQUIREMENTS, IMPRECISE AND DIFFICULT ESTIMATION, IMPROPER TESTING

  32. IT Project Failures Source: Michael Krigsman, ZDNet, http://blogs.zdnet.com/projectfailures

  33. Source: Michael Krigsman, ZDNet, http://blogs.zdnet.com/projectfailures

  34. Key Technologies • Database • Distributed Databases • Data Warehouses • Data Mining • Intelligent Agents • Client Server and Internet Technologies • Active Server Pages, Java, JSP,…..

  35. SYSTEM QUALITY • WHAT DOES SYSTEM QUALITY MEAN? • WHEN IS A SYSTEMS PROJECT SUCCESSFUL ? • MULTIPLE CUSTOMER GROUPS • USERS, MANAGEMENT, SUPPORT PERSONNEL,.. • MANAGING EXPECTATIONS

  36. Criteria for Selecting the Appropriate Methodology Clear user requirements Familiarity with technology Complexity of system Reliability of system Time schedule Schedule visibility

More Related