CCA220-Analisis dan Perancangan system Informasi

Similar documents
Chapter 1 The Role of the Systems Analyst

Assuming the Role of the Systems Analyst. Learning Objectives. Major Topics. Information A Key Resource 1/28/2008

Chapter 1 Assuming the Role of the Systems Analyst (SOOADM) 1

SCSD2613 System Analysis and Design. PART 1 Fundamentals of Systems Analysis & Design

Chapter 1 The Systems Development Environment

Meltem Özturan

CHAPTER 7 Information System

Mod-TWO. Transaction Processing System (TPS) Office Automation System (OAS)

Modern Systems Analysis and Design Seventh Edition

MINGGU Ke 1 Analisa dan Perancangan Sistem Informasi

CONTENTS. Part I BUSINESS PROCESSES AND INFORMATION SYSTEMS FOUNDATION 1. Part II TECHNOLOGY FOR BUSINESS PROCESSES AND INFORMATION SYSTEMS 65

Introduction to Systems Analysis and Design

Unit 9 Information Systems

Learning Objectives. Agile Modeling and. Major Topics. Prototyping. Patched Up Prototype. Agile Modeling, but First. Prototyping

Content. Computer System. Unit 1

Information Systems in Business

Managing Information Technology 6 th Edition

INFORMATION SYSTEMS IN THE ENTERPRISE

WKU-MIS-B11 Management Decision Support and Intelligent Systems. Management Information Systems

Systems Analysis and Design Methods Chapter 2: Information System Building Blocks

Building Information Systems

Chapter by Prentice Hall

Information Technologies: Concepts and Management. MIT 21043, Technology Management and Applications

Management Information Systems. B14. Acquiring IT Applications and Infrastructure

1-2 Copyright 2011 Pearson Education, Inc. Publishing as Prentice Hall

What is a Computer-based Information System? Chapter 14: Information Systems Types and Presentations. Classification of Information Systems

Chapter 1 Systems Development in an Organization Context

Information System - Classification & Types. Chapter 2 1

Chapter. Redesigning The Organization With Information Systems

Decision Support System Definition. Supporting Business Decision-Making. DSS Assumptions. MIS and DSS History. Characteristics of DSS

Introduction to Information Technology

Designing Business Architecture and Application of E- Collaboration for Small and Medium Enterprises in Indonesia Using Service Oriented Architecture

CAPE Information Technology

Turban and Volonino. Business Intelligence and Decision Support Systems

System Engineering and Analysis. system environments. Lecture Objectives. System Elements. Definition of System. Information system types

Information Systems in Organizations. Decision Making. Mintzberg s five 5 organizational parts. Types of Organizations.

Fundamentals of Information Systems, Seventh Edition

This week. Welcome to TDT4175 Information Systems. Course introduction. Types of information systems (today and tomorrow)

Design of Information Systems 1st Lecture

Learning Outcomes. Computing Essentials

Managing Information Systems Seventh Canadian Edition. Laudon, Laudon and Brabston. CHAPTER 11 Managing Knowledge

Building Information Systems

System Development Life Cycle Fall Introduction to Information and Communication Technologies CSD 102

Unit 2 : Decision Making Concepts. By Mahesh R. Sanghavi SNJB s KBJ CoE, Chandwad.

CS200-Chapter12-Homework

Chapter 6. Supporting Processes with ERP Systems. Copyright 2015 Pearson Education, Inc. 6-1

Chapter 3 DECISION SUPPORT SYSTEMS CONCEPTS, METHODOLOGIES, AND TECHNOLOGIES: AN OVERVIEW

INTRODUCTION TO INFORMATION SYSTEMS & DECISION MAKING

First: University Requirements (27 credit-hours)

CHAPTER 1 INTRODUCTION TO INFORMATION SYSTEMS

Redesigning the Organization with Information Systems

Focus Area Level Report Including Knowledge and Skills, and Performance Indicators

INFORMATION SYSTEMS ANALYSIS AND DESIGN

Chapter 3. Information Systems Development. McGraw-Hill/Irwin. Copyright 2007 by The McGraw-Hill Companies, Inc. All rights reserved.

STUDY GUIDE CHAPTER 10

Harry J. Rosenblatt. (2014). Systems Analysis and Design, 10 th Edition, International Edition. Course Technology, Cengage Learning.

Focus Area Level Report Including Knowledge and Skills, and Performance Indicators

MODULE 1 INFORMATION SYSTEMS

The Systems Development Lifecycle

Management Information Systems. B02. Information Technologies: Concepts and Management

2 Why is systems development difficult and risky? 3 How do businesses use the systems development life cycle (SDLC) process?

Information Technologies: Concepts and Management

Systems Analysis and Design 8 th Edition. Chapter 1 Introduction to Systems Analysis and Design

AQU Information Systems Fundamentals Spring Pg. 10.1

Modern Systems Analysis and Design Sixth Edition. Jeffrey A. Hoffer Joey F. George Joseph S. Valacich. Chapter 14 Maintaining Information Systems

6/29/ Professor Lili Saghafi

Fundamentals of Information Systems, Seventh Edition

Managing Systems Development. Definitions. Opening case. Off the Shelf software. Custom software. In house system development.

Business Intelligence. Slides by: Shree Jaswal

COMM 205 Introduction to Management Information Systems

Major attributes of the Lifecycle. The Systems Development Lifecycle. Project phases. Planning. Design. Analysis

Chapter 13. Building Information Systems

Modern Systems Analysis and Design Seventh Edition

Chapter 1 Introduction to Systems Analysis and Design

IT1104: Information Systems & Technology Multiple Choice Question Paper

SMuE« ND DESIG. Rutgers University School of Business-Camden Camden, New Jersey. Rutgers University School of Business-Camden Camden, New Jersey

Dr. Mounir Kehal BSc Comp. (IS Eng), MBA, MPhil, PhD AI/KM Carleton University, American University in London, Surrey University

one Introduction chapter Overview Chapter

2) When systems are integrated they can share information in real-time. Answer: TRUE Diff: 1 Page Ref: 37

Fundamentals of Information Systems, Seventh Edition

B.Tech. (VIII Semester) Examination 2013 (Information Technology) SOLUTION OF MANAGEMENT INFORMATION SYSTEM

Session 2. World Med MBA

Business Information Systems. Decision Making and Problem Solving. Figure Chapters 10 & 11

2-2 Copyright 2011 Pearson Education, Inc. Publishing as Prentice Hall

Systems Analysis and Design in a Changing World, Fifth Edition

Chap 1 : Business Process Management & IT

Chapter 14: Information Technology Careers 1/5/2018. Chapter 14: Information Technology Careers. Chapter 14: Information Technology Careers

CHAPTER 4 SYSTEM USERS AND DEVELOPERS

Preface... iii Introduction... xvii Chapter 1: Introduction to Management Information System... 1

Managing Information Systems Seventh Canadian Edition. Laudon, Laudon and Brabston. CHAPTER 2 How Businesses Use Information Systems

Enhancing Decision Making

Chapter No 11 Batch Management Information Systems. Management Information Systems. Compiled By: Muzammil Ahmad Khan and Kashif Shaikh

Laudon & Laudon MIS, 7th Edition. Pg. 1.1

Global E-Business: How Businesses Use Information Systems

Building Information Systems

Managing Knowledge in the Digital Firm

P a g e 1. Course Description

Introduction. Figure 1-1

Software tool support for software development

INFORMATION TECHNOLOGY

Transcription:

CCA220-Analisis dan Perancangan system Informasi Dosen Pengampu : 5165-Kundang K Juman, Ir, MMSI Prodi Teknik Informatika dan Sistem Informasi - Fakultas Ilmu Komputer

Chapter 1 Assuming the Role of the Systems Analyst Systems Analysis and Design Kendall & Kendall Sixth Edition

Major Topics Information systems Phases of analysis and design System maintenance CASE tools Alternate methodologies Kendall & Kendall 2005 Pearson Prentice Hall 1-3

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. Kendall & Kendall 2005 Pearson Prentice Hall 1-4

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). Kendall & Kendall 2005 Pearson Prentice Hall 1-5

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. Kendall & Kendall 2005 Pearson Prentice Hall 1-6

Kendall & Kendall 2005 Pearson Prentice Hall 1-7

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. Kendall & Kendall 2005 Pearson Prentice Hall 1-8

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. Kendall & Kendall 2005 Pearson Prentice Hall 1-9

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. Kendall & Kendall 2005 Pearson Prentice Hall 1-10

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 1-11

Kendall & Kendall 2005 Pearson Prentice Hall 1-12

Phase 1 Identifying: Problems. Opportunities. Objectives. Personnel involved: Analyst. User management. Systems management. Kendall & Kendall 2005 Pearson Prentice Hall 1-13

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. Kendall & Kendall 2005 Pearson Prentice Hall 1-14

Phase 2 (Continued) Personnel involved: Analyst. User management. User operations workers. Systems management. Kendall & Kendall 2005 Pearson Prentice Hall 1-15

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. Kendall & Kendall 2005 Pearson Prentice Hall 1-16

Phase 3 (Continued) Personnel involved: Analyst. User management. Systems management. Kendall & Kendall 2005 Pearson Prentice Hall 1-17

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. Kendall & Kendall 2005 Pearson Prentice Hall 1-18

Phase 4 (Continued) Personnel involved: Analyst. System designer. User management. User operations workers. Systems management. Kendall & Kendall 2005 Pearson Prentice Hall 1-19

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. Kendall & Kendall 2005 Pearson Prentice Hall 1-20

Phase 5 (Continued) Personnel involved: Analyst. System designer. Programmers. Systems management. Kendall & Kendall 2005 Pearson Prentice Hall 1-21

Phase 6 Testing and maintaining the system: Test and debug computer programs. Test the computer system. Enhance system. Kendall & Kendall 2005 Pearson Prentice Hall 1-22

Phase 6 (Continued) Personnel involved: Analyst. System designer. Programmers. Systems management. Kendall & Kendall 2005 Pearson Prentice Hall 1-23

Phase 7 Implementing and evaluating the system: Plan conversion. Train users. Purchase and install new equipment. Convert files. Install system. Review and evaluate system. Kendall & Kendall 2005 Pearson Prentice Hall 1-24

Phase 7 (Continued) Personnel involved: Analyst. System designer. Programmers. User management. User operations workers. Systems management. Kendall & Kendall 2005 Pearson Prentice Hall 1-25

Rapid Application Development Rapid Application development (RAD) is an object-oriented approach to systems development. Kendall & Kendall 2005 Pearson Prentice Hall 1-26

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. Kendall & Kendall 2005 Pearson Prentice Hall 1-27

Kendall & Kendall 2005 Pearson Prentice Hall 1-28

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. Kendall & Kendall 2005 Pearson Prentice Hall 1-29

Kendall & Kendall 2005 Pearson Prentice Hall 1-30

CASE Tools CASE tools are automated, microcomputerbased software packages for systems analysis and design. Four reasons for using CASE tools are: To increase analyst productivity. Facilitate communication among analysts and users. Providing continuity between life cycle phases. To assess the impact of maintenance. Kendall & Kendall 2005 Pearson Prentice Hall 1-31

CASE Tool Categories CASE tools may be divided into several categories Upper CASE (also called front-end CASE) tools, used to perform analysis and design. Lower CASE (also called back-end CASE). These tools generate computer language source code from CASE design. Integrated CASE, performing both upper and lower CASE functions. Kendall & Kendall 2005 Pearson Prentice Hall 1-32

Upper CASE Upper CASE tools: Create and modify the system design. Store data in a project repository. The repository is a collection of records, elements, diagrams, screens, reports, and other project information. These CASE tools model organizational requirements and define system boundaries. Kendall & Kendall 2005 Pearson Prentice Hall 1-33

Lower CASE Lower CASE tools generate computer source code from the CASE design. Source code may usually be generated in several languages. Kendall & Kendall 2005 Pearson Prentice Hall 1-34

Advantages of Generating Code Time to develop new systems decreases. The time to maintain generated code is less than to maintain traditional systems. Computer programs may be generated in more than one language. CASE design may be purchased from third-party vendors and tailored to organizational needs. Generated code is free from program coding errors. Kendall & Kendall 2005 Pearson Prentice Hall 1-35

Kendall & Kendall 2005 Pearson Prentice Hall 1-36

Reverse Engineering Reverse engineering is generating the CASE design from computer program code. Source code is examined, analyzed, and converted into repository entities. Kendall & Kendall 2005 Pearson Prentice Hall 1-37

Reverse Engineering (Continued) Reverse engineering produces (depending on the tool set used): Data structures and elements, describing the files, records, and field. Screen designs, if the program is online. Report layouts for batch programs. A structure chart showing the hierarchy of the modules in the program. Database design and relationships. Kendall & Kendall 2005 Pearson Prentice Hall 1-38

Advantages of Reverse Engineering Reverse Engineering has the following advantages: Reduced system maintenance time. Program documentation is produced for loosely documented programs. Structured programs may be generated from unstructured, older programs. Future system maintenance is easier to implement. Unused portions of programs may be eliminated. Kendall & Kendall 2005 Pearson Prentice Hall 1-39

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. Kendall & Kendall 2005 Pearson Prentice Hall 1-40

The Unified Modeling Language The Unified Modeling Language (UML) is an industry standard for modeling object-oriented systems. It breaks down a system into a use case model. Kendall & Kendall 2005 Pearson Prentice Hall 1-41

Extreme Programming (XP) Extreme programming takes good software development practices and pushes them to the limit. It is based on: Values. Principles. Core practices. Kendall & Kendall 2005 Pearson Prentice Hall 1-42

Extreme Programming (XP) (Continued) Extreme programming values are: Communication. Simplicity. Feedback. Courage. Kendall & Kendall 2005 Pearson Prentice Hall 1-43

Alternate Methodologies Alternate methodologies are available for analyzing systems. These include: Prototyping. ETHICS. Project Champions. Soft Systems Methodology. Multi-view. Kendall & Kendall 2005 Pearson Prentice Hall 1-44