1 IPT CORE TOPICS 9.1 Project Work (20%) 9.2 Information System & Databases (20%) 9.3 Communications Systems (20%) OPTIONS 9.4.1Transaction Processing.

Slides:



Advertisements
Similar presentations
System Development Life Cycle (SDLC)
Advertisements

Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
The System Development Life Cycle
Principles and Learning Objectives
6.1 Copyright © 2014 Pearson Education, Inc. publishing as Prentice Hall Building Information Systems Chapter 13 VIDEO CASES Video Case 1: IBM: Business.
System Design and Analysis
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.
Fundamentals of Information Systems, Second Edition
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Computers: Tools for an Information Age
Systems Development Life Cycle
System Development Life Cycle (SDLC)
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
7.2 System Development Life Cycle (SDLC)
The Agile vs. Waterfall Methodologies Systems Development:  the activity of creating new or modifying / enhancing existing business systems.  Objectives.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
Introduction to Computer Technology
CORE 1: PROJECT MANAGEMENT Overview TECHNIQUES FOR MANAGING A PROJECT Communication Skills Active Listening Mirroring Paraphrasing Summarizing Clarifying.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
1.Database plan 2.Information systems plan 3.Technology plan 4.Business strategy plan 5.Enterprise analysis Which of the following serves as a road map.
SYSTEM ANALYSIS AND DESIGN
Chapter 8: Systems Development Please turn your cell phone off.
Introduction to Systems Analysis and Design Trisha Cummings.
Systems Analysis and Design: The Big Picture
Initiating and Planning Systems Development projects
Succeeding with Technology Systems Development An Overview of Systems Development Tools and Techniques for Systems Development Systems Investigation Systems.
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Computers Are Your Future Eleventh Edition Chapter 13: Systems Analysis & Design Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall1.
Transaction Processing Systems and System Development Life Cycle
Chapter 8: Systems analysis and design
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Chapter 13: Developing and Implementing Effective Accounting Information Systems
Chapter 14 Information System Development
Computers Are Your Future © 2006 Prentice Hall, Inc.
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
Systems Analysis and Design
Computers Are Your Future © 2008 Prentice Hall, Inc.
Computers Are Your Future Tenth Edition Chapter 13: Systems Analysis & Design Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall1.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
ANALYSIS PHASE Purpose of information systems in organisations Information systems exist in organisations to serve organisations. Therefore the aims.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Systems Development Life Cycle
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.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
10-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Public Management Information Systems System Analysis & Design Saturday, June 11, 2016 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
Chapter 1 Assuming the Role of the Systems Analyst.
The System Development Life Cycle
Systems Development Life Cycle
Information Systems Development
Fundamentals of Information Systems, Sixth Edition
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design
The System Development Life Cycle
Introduction to Systems Analysis and Design
Chapter 13: Systems Analysis and Design
Systems Analysis and Design
Systems Development Life Cycle
UNIT No- III- Leverging Information System ( Investing strategy )
Presentation transcript:

1 IPT CORE TOPICS 9.1 Project Work (20%) 9.2 Information System & Databases (20%) 9.3 Communications Systems (20%) OPTIONS 9.4.1Transaction Processing (20%) Decision Support Automated Manufacturing Multimedia Systems (20%)

2

3 Project Work Project Management Social & Ethical Design Understanding the Problem Making Decisions Designing Solutions Implementing Testing, evaluating & maintaining

9.1.1 Project Management

5 Projects A PROJECT is a temporary endeavour undertaken to create a unique product or service. –Temporary means an END DATE –Unique means the end result (final deliverable) is different than the results of other endeavours of the organisation

6 Project Management The application of a range of activities to meet particular requirements: Range of activities – knowledge – skills – tools, and – techniques Carried out during all stage of a project

7 Advantages of PM Cost control Development within specified times Organised use of the available hardware and software An improved end product

8 Project Manager The person (or firm) responsible for planning, coordination, and controlling a project from inception to completion Expected to bring the project ‘in’ on time and on budget to a specific quality

9 Steps in Project Management 1.PLAN Understand the problem Making decisions 2.DESIGN Designing and building the solution 3.DEPLOY Implement solution Testing, Evaluation and Maintaining This equates to UM-DITEM (System Development Cycle)

10 System Development Cycle BENEFITS Efficient system Error free as possible Understand the problem Make decision Design solution Implement Test, evaluate, maintain Statement of problem Type of new system New system Using new system Change In purpose Change type Of system Change system Change use Of system Problems

11 System Development Cycle (2) UNDERSTAND THE PROBLEM (Capture user requirements & prototype system) MAKING DECISION (Review requirements, constraints & feasibility) IMPLEMENTING (Planning: conversion, participant training, testing) TESTING, EVALUATING & MAINTAINING (System test, evaluation form, modifications Design Report Built Solution Activities Deliverable Requirements Report Feasibility Study DESIGNING SOLUTIONS (Scope & build solution) Implementation Plans Evaluation Report

12 Project Plan A management document for the project in terms of its objectives, justification and how the objectives will be met. Used as a record of decisions and a means of communication among stakeholders

13 Project Plan Contents Project Title –Project Statement Overview –Background –Aims & Objectives –Direction –Planned Deliverables Resources –People –Timeframe –Money –Resources Gantt Chart

14 Project Statement Project statement: –Objective –Timeframe –Budget e.g Develop a new web site within six months for a total cost not exceeding $50,000

15 Project Schedule Gantt chart

16 Gantt Chart

17 Communication Skills Actively listening (hearing) Conflict resolution Negotiation Interview techniques People in the project must be kept informed Team Building is crucial

18 Active Listening The art of giving individual, undivided attention to a speaker in a genuine effort to understand their point of view Important when interviewing or surveying users as part of a project

19 Conflict Resolution Conflicts among people arise from time to time The process of resolving a dispute or disagreement Methods include: – negotiation, –Mediation, or –arbitration

20 Methods of Resolution Negotiation: discussion between people intended to produce agreement Mediation: negotiation conducted by an independent third-party. Arbitration: formal hearing and determination of a dispute by an impartial referee agreed to by all parties.

21 Interview Techniques An important analysis tool Opportunity to interact with people who have first-hand practical knowledge Consider similarities and differences: –Interview –Survey –Questionnaire

22 Team Building Process of getting people working well together Each team member usually has a specific role What would some of those roles be?

9.1.2 Social & Ethical Design

24 Social Issue A social issue may arise when a decision or action we make impacts other people in a negative way. For example: –loss of jobs due to new system –privacy of people’s personal data is jeopardised

25 Ethical Issue An ethical issue can arise when a decision or action we make is perceived by other people as being inappropriate or wrong. For example: –you might be legally able to publish personal information you have collected because the person clicked a box on a computer screen without thinking BUT it is clear that the publication of the data will cause the person embarrassment. What should you do?

9.1.3 Understanding the Problem

27 Steps in Understanding Preliminary investigation –Determine the exact nature of the problem –Determine if a ‘quick-fix’ is possible or if new system required –Details of existing system and processes examined Collect data from participants and users Produce User Requirements Report and Project Plan (including Gantt Chart)

28 Prototypes Working model of an information system, built in order to understand the requirements of the system: – used when the problem is not easily understood –Repetitive process of prototype modifications and participants’ feedback until the problem is understood can be the basis for further development

29 Prototyping Cycle Create Prototype Implement Communicate with participants Feedback from participants Modify prototype Evolutionary prototyping

30 System Environment

31 System Environment (2)

9.1.4 Making Decisions

33 Making Decisions Conduct a Feasibility Study of proposed solutions and the judging criteria: – is it economically feasible? – is it technically feasible? – does it fit the objectives of the owners of the information system and are there participants who can operate it (organisational)? – can it be implemented in the available time- frame? Produce Feasibility Report –Benefits, costs and risks

9.1.5 Designing Solutions A Building Solution

35 Refine Prototype Initial prototype concentrates on inputs and outputs (sample data) Enhanced prototype involves making prototype more user friendly and developing underlying processes using real data Screen & report generators used

36 Participant Development Participant development, when people within the information system develop the solution Participant designed solutions Special Computer-Aided Systems Engineering software (CASE) often used

37 Design Tools Tools used in designing, including: –Context Diagrams –Data Flow Diagrams (DFD) –Decision trees & tables –Data Dictionaries –System flow charts

38 Context diagram Graphical method for representing a system using a single process Process External entity Single process: Circle represents the entire system Data flow: Flow of data between process and external entities External entity: Represents any person or organisation that sends data to or receives data from the system ID number

39 Video Store System Hire Videos Distributors Employees Customers Video details Hiring details Receipt

40 Video Store System VSS Distributors Employees Customers Product details Hire & sales g details Receipt Product details

41 Data flow diagram Graphical method for representing a system using a number of processes Process External entity Process: Circle represents the various processes involved Data flow: Flow of data between processes, external entities and data store External entity: Represents any person or organisation that sends data to or receives data from the system Data store Data store: location where data is stored ID number

42 Distributors Customers Purchase Videos Process Rentals Video Details Register Members Membership Card Employees Video & Member ID Customer Details Name Address Phone# Video Details Title ID# Process Enquiry Title ID # Date available Due date Video Card Member ID Due Date Customer Record Card Video ID Date Process Overdues Date Member ID Customer Details Overdue letter Jim’s Video Store Data Flow Diagram

43 Decision Trees Diagrammatic way of representing all possible decisions and their resulting actions e.g. determine a basic computer problem

44 Decision Tree Example

45 Decision Table Table that represents all possible conditions and actions

46 Decision Table Example

47 Decision Table Describe a process within a system

48 Four Quadrants

Determine Conditions

50 2- Determine Actions

Construct Condition Alternatives Usually two alternatives (Y/N) per condition 2* X where x = number of conditions

Simplify table Eliminate logical inconsistencies

53 4a - Simplified Table

Complete Actions

55 Data Dictionaries Table that describes the data in a system

56 Data Dictionary Example

57 System Flow Chart Graphical method of representing both the flow of data and the logic of the system Many of these symbols have become out of date as a result of changes in technology.

58 Flow Chart Symbols

59 System Flow Charts Graphical method of representing both the flow of data and the logic of the system

60 Receipting Flow Chart B B

9.1.6 Implementing

62 Implementation Plan Training Conversion Testing methods Develop an implementation plan for the project – convert from the old to the new system – determine the training needs arising from the creation of a new system

63 Participant Training Need to consider: –Requirements& complexity of new system –Previous skills of participants –When training can occur –Who will do the training (trainers and participants) Who needs training? –Operators, system managers (participants); users (managers) Methods of training

64 Training Methods

65 Conversion Methods DIRECT: immediate change with all data transferred on a specific date –Minimal transition costs BUT high risk PARALLEL: old and new at same time –Extra work load but LOWER risk (BUT can be confusing) PHASED: Gradual implementation of new system PILOT: Trial new system in a small part of the organisation –Longer lead time but lower risk

66 Conversion Methods (2) Methods are not necessarily mutually exclusive e.g. –Might run a pilot then implement fully using direct, phased or parallel

67 Deciding Testing Methods Stress test - loads to stretch capacity of system Participant testing - people familiar with requirements Bench testing - checks each component against specification System test - tests all components working together Acceptance test - check delivered product against specifications

9.1.7 Testing, Evaluating & Maintaining

69 Test & Evaluate Testing and evaluating the solution with live test data Checking to see if the original objectives of the project have been achieved (acceptance testing) Compare the new system to the old and evaluate whether objectives for the project have been met (Project Evaluation) Did we get what we wanted on time & on budget?

70 Maintaining Documenting the system Fixing ‘bugs’ Accommodating changes e.g. changed legislation, tax rates etc. Enhancements to the system

71 Documentation The operation manual detailing procedures participants follow when using the new system Document the new system

72 THE END