Business System Analysis Methodology Presentation.

Slides:



Advertisements
Similar presentations
Project Management Based on Sommerville’s “Software Engineering” textbook.
Advertisements

Project Management Process. Project Complexity means that: a team of people are needed to supply expertise the work needs to be broken into manageable.
Evaluating Decision Support Systems Projects. Who Evaluates Technical Managers  Chief Information Officer,  Corporate IT professionals,  Database administrators,
Class 8 Systems Development Asper School of Business - MBA 6150 Management of Information Systems & Technology April-June 2009 Instructor: Bob Travica.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 feasibility 1 why address feasibility? to answer the questions... can the project be done.
Chapter 12: Planning for Electronic Commerce
QUALITY MANAGEMENT DEFINITIONS AND CONCEPTS QUALITY MANAGEMENT TOOLS QA / QC PROCESS COMPUTERS AND PROJECT QUALITY.
Chapter 2: Planning. Planning steps Establishing project team Defining system requirements Performing feasibility analysis Obtaining support for the HRMS.
Review Questions List and describe the purpose of the four phases of Systems Analysis. The preliminary investigation phase quickly determines whether or.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
The Analyst as a Project Manager
CHAPTER 9: LEARNING OUTCOMES
Project Management and MS Project. The project management triangle: Time Resources Scope.
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 1-1 Enterprise Resource Planning, 1 st Edition by Mary Sumner Chapter.
CHAPTER 6 Controlling Expenses
© Pearson Education Limited 2008 MANAGEMENT ACCOUNTING Cheryl S. McWatters, Jerold L. Zimmerman, Dale C. Morse Cheryl S. McWatters, Jerold L. Zimmerman,
STRATEGIES FOR NEW PRODUCT DEVELOPMENT (AGENDA ITEM 5) DECISION EXPECTED TAKE NOTE OF THE PAPER th PAPU Administrative Council 24 May – 3 June, 2015,
Software Evolution Planning CIS 376 Bruce R. Maxim UM-Dearborn.
METODOLOGI SIX SIGMA PERTEMUAN 12 IMPROVE PHASE OLEH: EMELIA SARI.
Complete and Integrated Lifecycle Management. Challenges 1.
13-1 Information Technology Economics Information Technology: Economic and Financial Trends Internal IT versus outsourcing Expanding power / declining.
The Importance of Thinking Strategically Tribal Development Seminar November 30, 2010 Steve Walker, Managing Director Heartland, LLC.
Chapter 5 Conducting a Feasibility Analysis. Copyright © Houghton Mifflin Company. All rights reserved.5 | 2 Learning Objectives Prepare to conduct a.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Investment Portfolio Methodologies Pertemuan Matakuliah: A Strategi Investasi IT Tahun: 2009.
Tietojärjestelmien peruskurssi Systeemisuunnittelu ja prototyyppimenetelmä Malin Brännback.
Change Management “Getting from where you are, to where you want to be”
Systems Development Lifecycle Project Identification & Selection Project Initiation & Planning Analysis Logical Design Physical Design Implementation Maintenance.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
The Systems Proposal What the book calls the “Updated Baseline Project Plan” - no standard name for it Presents the different options to the customer along.
Systems Analysis – ITEC 3155 Feasibility Analysis
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
© 2009 Capaccio Environmental Engineering, Inc. “Helping Industry and the Environment Prosper” Pollution Prevention Saves Money By Reducing Operational.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
Production and Operations Management Chapter Learning Objectives Explain the strategic importance of the production. Identify and describe.
ACCOUNTING INFORMATION SYSTEMS
SANILAB THE LOGICAL INDUSTRY CHOICE. SANILAB Industry edition Risk management is costly and stressing for production, quality and any other people of.
NHS Highland Stuart Caldwell. Our Kaizen Programme 6 week programme in June Work streams –New patient referral –Re-referral –Depot MDT teams -
A Portfolio Approach to IT Projects Chapter 10. Project Risk Consequences of Risk: –Failure to obtain all, or any, of the anticipated benefits because.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 3 Systems Planning and Selection 3.1.
ENTERPRISE RESOURCE PLANNING(ERP). Contents Introduction ERP-Definition Evolution of ERP Enabling Technologies ERP Characteristics Features of ERP Benefits.
2  Mission Statement.  Company’s overall purpose and direction, products, services and values.  Goals.  That accomplish the mission. E.g. 5 year plan.
Business Driven Technology Unit 5 Transforming Organizations Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution.
3 1 Project Success Factors u Project management important for success of system development project u 2000 Standish Group Study l Only 28% of system development.
Project Management Methodology Development Stage.
14-1 Systems Development Concept of Systems Development Life Cycle (SDLC) Definition of SDLC Stages of SDLC Traditional versus modern SDLCs.
12/10/15.  It is a Cross Life Cycle Activity (CLCA) that may be performed at any stage ◦ In fact, some part of it (e.g. risk analysis and management)
Accounts Chamber of the Russian Federation Approaches to comprehensive project and program audit in the Accounts Chamber of the Russian Federation.
Lecture 4. IS Planning & Acquisition To be covered: To be covered: – IS planning and its importance Cost-benefit analysis Cost-benefit analysis Funding.
HAZARDOUS WASTE ($) MINIMIZATION TABLE 4 TEAM Tom Finley Mitch Campbell Melenda Powers Doris Reid Drew Jacobs.
Copyright 2003 Lynn Frock & Company. All Rights Reserved. 1 Five Ways to Build a Microsoft Project Schedule Lynn Frock, PMP Phone
Presented By T. J. Crayne Panelists Wayne Stillwagon, Executive VP, Miller’s Supplies At Work Steve Gordon, President, Independence Business Supply Robert.
1 - 1 Systems Analysis and Design, Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
Exploration of parallels in Lean and VM methodology in construction Steve Parker, Institute of Value Management.
Feasibility Analysis for a Software Project Dr. Pedro Mejia Alvarez Seccion de Computacion, CINVESTAV-IPN.
PLANNING AND DECISION- MAKING IN AN ORGANIZATION Business Management Copyright © Texas Education Agency, All rights reserved.
1 visit: New Product Development Strategy.
New Product Development Strategy. Key Steps in New Product Development.
University of Sunderland COMM80 Risk Assessment of Systems ChangeUnit 10 Decision Points COMM80: Risk Assessment of Systems Change Unit 10.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
IS Development Methodology
Information Technology Economics
17. Managing GIS © John Wiley & Sons Ltd.
Chapter 4 Systems Planning and Selection
Introduction to Projects
Tour VII: Change Management
Enterprise Resource Planning, 1st Edition by Mary Sumner
Presentation transcript:

Business System Analysis Methodology Presentation

The following scenario will be addressed: a. Getting what you do not have: (Integrated system to manage the maintenance department spare parts and work orders). b. Getting rid of what you do have: (Poor spare parts inventory management and unneeded legacy system).

 prototyping and reverse engineering of the current Perzak legacy system  developments learned in the legacy system will provide a quick development program that will be much more faster to implement  Microsoft Visio  UML Methodology  OO Techniques

 Constraints: time, money, and functionality  Prior to implementation, all functions must be drafted first

 Non-IS Influences  A development team must know how to anticipate unforeseen circumstances  Resource Limits  The development team must know its capability to estimate who will do what and the timeframe to achieve the stipulated objective in the contract

 Cost - Benefit Analysis  When expertise is available, reverse engineering is fast  Net Present Value and Cost/economic analysis  The net present value is positive. If it were negative, the project must be disregarded anyway.

 Least Cost Alternative  During reverse engineering stage, working in-house requires longer time and is expensive for the company  Decision evaluation matrix  The decision whether the business must move forward or wait with the idea in the application is made

 Risk analysis  To know the risks and how it will affect the company, the group must distribute the risks into their accurate category

 Tangible and Intangible Benefits  Reverse engineering will allow the company to save money  The information generated is up-to-date in real time  All employees will be trained on the usage of the new application before implementation of the new system

 Process for handoff to development and implementation teams will be provided.  A schedule must be available for post implementation audit.  Each organization functions to maximize its efficiency and minimize losses.  Inconsistencies is harmful for business interests.