1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senn’s Information Technology, 3 rd Edition Chapter 11 Creating Enterprise.

Slides:



Advertisements
Similar presentations
Systems Investigation and Analysis
Advertisements

© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
Systems Analysis and Design 9th Edition
Chapter 1 Assuming the Role of the Systems Analyst
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Chapter 1 Assuming the Role of the Systems Analyst
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Lecture 13 Revision IMS Systems Analysis and Design.
Discovering Computers 2008 Chapter 12 Information System Development.
12 C H A P T E R Systems Investigation and Analysis and Analysis.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Computers: Tools for an Information Age
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Systems Development Life Cycle
Chapter 1 Assuming the Role of the Systems Analyst
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
1-1 © Prentice Hall, 2007 Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
James A. Senn’s Information Technology, 3rd Edition
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 1.1.
Chapter 6: The Traditional Approach to Requirements
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Systems Analysis and Design: The Big Picture
Chapter 6 The Traditional Approach to Requirements
Lesson 1 Week01.
CHAPTER 1: THE DATABASE ENVIRONMENT AND DEVELOPMENT PROCESS Modern Database Management 11 th Edition Jeffrey A. Hoffer, V. Ramesh, Heikki Topi © 2013 Pearson.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Chapter 1: The Database Environment and Development Process
Computers Are Your Future Eleventh Edition Chapter 13: Systems Analysis & Design Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall1.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 14 Information System Development
Modern Systems Analysis and Design Third Edition
Chapter 1 Assuming the Role of the Systems Analyst Systems Analysis and Design Kendall & Kendall Sixth Edition.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
1 4 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 4 Beginning the Analysis: Investigating System Requirements.
1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senn’s Information Technology, 3 rd Edition Chapter 12 Creating Web-Enabled.
 2004 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, by Bodnar/Hopwood 10 – 1 Systems Planning and Analysis Chapter 10.
CISB113 Fundamentals of Information Systems IS Development.
Chapter 1 Introduction to Systems Design and Analysis Systems Analysis and Design Kendall and Kendall Sixth Edition.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
1Lecture 8 Introduction to Systems Analysis l Objectives –Explain how systems analysis relates to business needs, problems, and opportunities –List and.
ANALISA & PERANCANGAN SISTEM Disusun Oleh : Dr. Lily Wulandari Program Pasca Sarjana Magister Sistem Informasi Universitas Gunadarma.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
1-1 © Prentice Hall, 2004 Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Information Technology, 3 rd Edition Chapter 1 Information Technology: Principles,
Chapter 1 Assuming the Role of the Systems Analyst.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
C_ITIP211 LECTURER: E.DONDO. Unit 1 : The Systems Development Environment.
Systems Development Life Cycle
Fundamentals of Information Systems, Sixth Edition
James A. Senn’s Information Technology, 3rd Edition
Chapter 11 Information System Development
Chapter 1 The Systems Development Environment
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Systems Development Life Cycle
UNIT No- III- Leverging Information System ( Investing strategy )
Presentation transcript:

1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senn’s Information Technology, 3 rd Edition Chapter 11 Creating Enterprise Applications

2 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Objectives Describe the principal functions and roles of a system analyst. Identify the characteristics of shared systems. Discuss the changing process for developing information systems applications.

3 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Objectives (Continued) Describe the tools and techniques available to system analysts for collecting data and developing IT applications. Summarize the purpose and characteristics of unified modeling language (UML). Explain the roles of the four types of IT systems development professionals.

4 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Developing Open Shared Systems Development Alternatives Build the application itself. Purchase a prewritten application. Contract out the application development.

5 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Developing Open Shared Systems Open Systems for Sharing Open System: A software system that performs on different computer and communications hardware. Interoperability: The perfect exchange of data and information in all forms (data, text, sound, and image, including animation) between the individual components of an application (hardware, software, network).

6 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Developing Open Shared Systems Shifting Development Model Craft Approach Assembly Approach Object: A component that contains data about itself and how it is to be processed.

7 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Developing Open Shared Systems Building IT with Components

8 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall The System Analyst’s Tools and Techniques Definition Systems Analyst: The IT professional responsible for working with users to determine a system’s requirements and for describing the features needed in the system.

9 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall The System Analyst’s Tools and Techniques Data Collection Techniques Interviews –Structured Interview: An interview in which the questions are prepared in advance and each interviewee is asked the same set of questions. –Unstructured Interview: An interview in which the questions may be prepared in advance, but follow-up questions vary, depending on the interviewees’ background and answer.

10 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall The System Analyst’s Tools and Techniques Data Collection Techniques (Continued) Questionnaire: A sheet of questions used to collect facts and opinions from a group of people. Document Examination/Record Inspection: The review of company documents about a system or opportunity under investigation. Observation: The process of watching an activity take place to collect information about that activity.

11 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall The System Analyst’s Tools and Techniques Data Collection Techniques (Continued) Sampling: The process of collecting data and information at prescribed intervals.

12 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall The System Analyst’s Tools and Techniques System Flowcharts System Flowcharts: A graphical description of a business process or procedure using standard symbols to show decision logic.

13 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall The System Analyst’s Tools and Techniques System Flowcharts (Continued)

14 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall The System Analyst’s Tools and Techniques Dataflow Diagram Dataflow Diagram (DFD): A chart showing the movement of data through a system. –DFD Levels Leveling: The process of exploding processes in a dataflow diagram to show more detail.

15 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall The System Analyst’s Tools and Techniques Dataflow Diagram (Continued)

16 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall The System Analyst’s Tools and Techniques Dataflow Diagram (Continued)

17 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall The System Analyst’s Tools and Techniques Data Dictionaries Data Dictionary/Repository: A catalog that lists and describes all the types of data flowing through a system. Composed of data elements and a data structure. Data Element: The component of a data dictionary that includes data names, alternate names, and length allowances.

18 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall The System Analyst’s Tools and Techniques Data Dictionaries (Continued)

19 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall The System Analyst’s Tools and Techniques Data Dictionaries (Continued) Data Structure: The set of data elements used together and the name that collectively identifies the set.

20 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Computed-Aided Systems Engineering (CASE) Definition Computed-Aided Systems Engineering/Computer-Aided Software Engineering (CASE): A set of tools used in systems development to improve the consistency and quality of the system while automating many of the most tedious and time-consuming systems tasks. –Charting and Diagramming Tools –Centralized Information Repository –Interface Generators –Code Generators –Project Management Tools

21 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Computed-Aided Systems Engineering (CASE) Definition (Continued)

22 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Computed-Aided Systems Engineering (CASE) Front-End, Back-End, and Integrated CASE Front-End CASE Tool: A CASE tool that automates the early (front-end) activities in systems development. Back-End CASE Tool: A CASE tool that automates the later (back-end) activities in systems development. Integrated CASE (I-CASE) Tool: A CASE tool that spans activities throughout the entire systems development life cycle.

23 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Computed-Aided Systems Engineering (CASE) Front-End, Back-End, and Integrated CASE (Continued)

24 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Unified Modeling Language Definition Unified Modeling Language (UML): The standard vehicle for visualizing, describing,and documenting the details of an IT application. Actor: Anyone or anything that will interact with the application. Activity Diagram: Shows the flow of control in an application.

25 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Unified Modeling Language Definition (Continued)

26 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Unified Modeling Language Definition (Continued) Use Case Diagram: Provides context for the system, illustrating the actors, the use cases, and the flow or interaction between use cases and actors. –Use Case: Identifies the sequence of activities performed for an actor. Use Case Description: Describes the use case in ordinary language, including its identifying name and actors.

27 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Unified Modeling Language Definition (Continued)

28 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Unified Modeling Language Definition (Continued) Class Diagram: Describes an object class, including the class name, attributes, and methods. Other UML Diagrams –Sequence Diagram –State Transition Diagram –Component Diagram

29 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall Unified Modeling Language Definition (Continued)

30 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall IT Development Personnel The Systems Analyst: The Key Roles Change Agent: A person who acts as a catalyst for change. Professional Skills –Problem Solving –Outcome Thinking –Creativity –Meeting Skills –Communication Skills

31 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall IT Development Personnel The Systems Analyst: The Key Roles

32 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall IT Development Personnel The Chief Information Officer Chief Information Officer (CIO)/IT Director/Director of Information Systems: The person given the responsibility of managing and developing the firm’s information technology capabilities.

33 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall IT Development Personnel The Chief Information Officer (Continued)

34 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall IT Development Personnel Computer Programmers Computer Programmers –Responsible for turning detailed specifications into computer software. –Responsible for documenting the program.

35 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall IT Development Personnel System Contractors System Contractor: An outside person or firm that contracts with a company to develop IT applications. System Integrator: A type of systems contractor who is retained to take responsibility for acquiring hardware, software and network capacity for an application, as well as for implementing the application.