INFORMATION SYSTEMS PLANNING Module A. Stakeholder Requirements Specification Information Technology Staff Analysis Design and Implementation Requirements.

Slides:



Advertisements
Similar presentations
Enterprise Architecture Planning Methodology - Implementation Steps - Tony Baker, MBA, CMC
Advertisements

Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
*This is an Example of Presentation Layout
1 Eurostat Unit B1 – IT Systems for Statistical Production IT outsourcing in Eurostat – our experience Georges Pongas, Adam Wroński Meeting on the Management.
Software Engineering 1. Software development – the grand view 2. Requirements engineering.
ITIL: Service Transition
Marketing Strategy MAR 4803
Systems Development Life Cycle:
Lecture 13 Revision IMS Systems Analysis and Design.
Managing the Information Technology Resource Jerry N. Luftman
Centers for IBM e-Business Innovation :: Chicago © 2005 IBM Corporation IBM Project October 2005.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Lecture 6 - Project Planning. Lecture 6: Project Planning Overview Creating an outline plan –Work Breakdown Structure –Identifying tasks Waterfall and.
The onion model for strategic roadmaps How to use roadmaps to communicate product strategy top-down for various target groups with different needs By Harri.
Leading Edge Climbing Equipment
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.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Context of Software Product Design.
Moving into Design SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
Introduction to information systems
Foundations of Geospatial System Development Todd S. Bacastow Professor of Practice for Geospatial Intelligence John A. Dutton e-Education Institute The.
PROJECT TITLE Project Leader: Team: Executive Project Sponsor (As Required): Date: Month/Day/Year 6/25/2015 V2.
Work Breakdown Structure Presentation. Creating the Work Breakdown Structure (WBS) Project deliverable – an interim but tangible result achieved at some.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Lecture4 : Project planning Lecturer: Kawther Abas 447CS – Management of Programming Projects.
Software Engineering Management Lecture 1 The Software Process.
PROJECT 123 Business Case March 30, Page 1 Authors: Saltlane Table of Contents Executive Summary Background Scope Approach Resource Requirements.
<Idea Title> Students : XXX, YYY (University)
CIS 499 Senior Seminar Introduction to IT project management.
Presented by: Masoud Shams Ahmadi February 2007 Enterprise Resource Planning (ERP) Selection Presented by: Masoud Shams Ahmadi
1-1 System Development Process System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Project Life Cycle – Project Initiation © Ed Green Penn State University All Rights Reserved.
BE-SECBS FISA 2003 November 13th 2003 page 1 DSR/SAMS/BASP IRSN BE SECBS – IRSN assessment Context application of IRSN methodology to the reference case.
Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition Irwin/McGraw-Hill.
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
Intuit Canada ULC How to Implement QuickBooks Training in your Practice.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Software Acquisition and Project Management Lesson I: Introduction.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
BIS 360 – Lecture Four Ch. 5: Identifying and Selecting Projects
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
International Marketing Final Term Presentation: Presented to: Presented to: Mr. Ali Saeed Mr. Ali Saeed Presented by: Presented by: Ibrar Ahmed Hunzai.
Definitions of GIS Works with geographic information Performs data input, management, manipulation/analysis, and output functions Composed of hardware,
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Foundations of Geospatial System Development Todd S. Bacastow Professor of Practice for Geospatial Intelligence John A. Dutton e-Education Institute The.
Or How to Gain and Sustain a Competitive Advantage for Your Sales Team Key’s to Consistently High Performing Sales Organizations © by David R. Barnes Jr.
U.S. Department of Agriculture eGovernment Program eDeployment Kickoff August 26, 2003.
CSE Senior Design II Staged Delivery Instructor: Manfred Huber Partially adapted from Mike O’Dell.
MARCH 1 Project Management Problem statement l no hurdles, no problem just a goal l open-ended … no single correct answer l closed-ended … single answer.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Appendix B: Getting Started in Systems Analysis and Design.
Marketing Management 16 February Company and Marketing Strategy Current Situation, Opportunities, Objectives and Resources – Inputs of Strategic.
As Partial fulfilment of Master of Computer Application [M.C.A. sem-6] Submitted by: – Suman M chauhan Project Guide: Mrs Vaishali Kaneriya.
© 2015 IBM Corporation IBM and IBM Business Partner Use Only Business Partner Technical Vitality Overview January, 2015 Send an to
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Increasing the Success of Business Analytics: Improving Requirements Determination? Ulrike Schultze, Cox School of Business, SMU.
Understand major difficulties and problems of ES implementations and their effect on organizations. Guidelines for a successful ES purchase decisions.
ITIL: Service Transition
Software Engineering Management
COMP532 IT INFRASTRUCTURE
Principles of Information Systems Eighth Edition
2 Selecting a Healthcare Information System.
BUS 201: Introduction to Business
Systems analysis and design, 6th edition Dennis, wixom, and roth
Systems analysis and design, 6th edition Dennis, wixom, and roth
COMPANY NAME/ PRODUCT NAME
Project Procurement Management
INTERNATIONAL COMPETITIVE STRATEGY
Joint Application Development (JAD)
System architecture, Def.
Presentation transcript:

INFORMATION SYSTEMS PLANNING Module A

Stakeholder Requirements Specification Information Technology Staff Analysis Design and Implementation Requirements Continued Involvement Information System Problem Definition Skills Problem Solution Skills Information Systems Planning Inputs & Outputs Information Systems Planning Business Mission & Goals Existing Information System Details Information Systems Plans and Project Information

Information Systems Planning Business Mission & Goals Existing Information System Details Information Systems Plans and Project Information Revise and Study the Business Mission & Goals Define an Information Architecture A Generic Information Systems Planning Methodology (Adapted from Whitten, J.L., Bently, L.D., and Barlow, V.M., Systems Analysis & Design Methods, 3rd Edition, Irwin, Boston, MA., 1994, p. 103.) Evaluate Business Areas and Applications Business Plans Business Areas and Applications Note: Dotted line symbols are optional

MISSION STATEMENT To be the video store of choice by successfully providing a generous selection of home video products for sale or rental at competitive prices. GOALS 1. Increase market share and maintain profitability 2. Offer superior customer assistance and browsing environment 3. etc... Video Store Mission Statement and Goals (partial) Revise and Study the Business Mission and Goals

What is it?  An INFORMATION ARCHITECTURE is a plan for selecting the appropriate information technology and information systems that will best support the business mission and goals. How long does it take to create an Information Architecture? Could take 6 to 12 months or longer, depending on: 1. scope to be covered 2. experience of staff doing it 3. availability of staff doing it What are its deliverables? 1. Plan for a people architecture (organization chart) 2. Plan for telecommunications network architecture 3. Plan for data architecture (enterprise data model) 4. Plan for applications architecture along with interfaces to each other 5. Plan for technology architecture to support the information architecture Define an Information Architecture

Information Systems Planning Business Mission & Goals Existing Information System Details Information Systems Plans and Project Information Revise and Study the Business Mission & Goals Define an Information Architecture A Generic Information Systems Planning Methodology (Adapted from Whitten, J.L., Bently, L.D., and Barlow, V.M., Systems Analysis & Design Methods, 3rd Edition, Irwin, Boston, MA., 1994, p. 103.) Evaluate Business Areas and Applications Business Plans Business Areas and Applications Note: Dotted line symbols are optional

Business areas = groups of logically related business functions and activities (e.g., academic affairs in your university) Applications = information systems that support business functions and activities (e.g., course registration system at your university) Prioritization criteria are used to determine rank order Evaluate Business Areas and Applications (optional)

Potential Problems when not doing Information Systems Planning Rushed work near the end of a project, causing the team to minimize critical implementation tasks Missed opportunities to take advantage of product differentiation, and productivity and management situations Loss or reduction of credibility with users because of missed deadlines High prices paid for hardware, software, and telecommunications equipment because of short deadlines to acquire Disruption of users when system resources peak out causing slowdowns and response time delays