FORDHAM CSLU 3598 - chap01 INTRODUCTION TO INFORMATION SYSTEMS (26 pages)

Previewing pages 1, 2, 3, 24, 25, 26 of 26 page document View the full content.
View Full Document

chap01 INTRODUCTION TO INFORMATION SYSTEMS



Previewing pages 1, 2, 3, 24, 25, 26 of actual document.

View the full content.
View Full Document
View Full Document

chap01 INTRODUCTION TO INFORMATION SYSTEMS

55 views


Pages:
26
School:
Fordham University
Course:
Cslu 3598 - Software Engineering
Unformatted text preview:

Slide 1 1 An Introduction to Object Oriented Systems Analysis and Design with UML and the Unified Process McGraw Hill 2004 Stephen R Schach srs vuse vanderbilt edu Copyright 2004 by The McGraw Hill Companies Inc All rights reserved CHAPTER 1 Slide 1 2 INTRODUCTION TO INFORMATION SYSTEMS Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Chapter Overview Categories of Information Systems Traditional Information System Development The Requirements Phase The Analysis Phase The Design Phase The Implementation Phase The Maintenance Phase Retirement Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Slide 1 3 Chapter Overview contd Why There Is No Planning Phase Why There Is No Testing Phase Why There Is No Documentation Phase Systems Analysis and Design Maintenance Information Technology Professionals Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Slide 1 4 Jethro s Boot Emporium Automated reordering system Jethro s formula for predicting future trends The formula works perfectly at first Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Slide 1 5 Definitions Artifact Component System Set of artifacts that achieve some outcome Information system System that achieves a business outcome Computerized information system COTS commercial off the shelf package Custom information system Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Slide 1 6 Custom Information System Stakeholders Client Users Developers Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Slide 1 7 COTS Software Shrinkware Clickware Stakeholders Users Developers Enterprise Resource Planning ERP system Examples PeopleSoft SAP Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Slide 1 8 Traditional Information System Development Slide 1 9 Information system life cycle The way that software is constructed Six traditional phases Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Overview of the Traditional Phases Requirements phase Find the client s requirements Draw up the requirements document Analysis phase Draw up the specification document Draw up the project management plan Design phase Determine the modules Determine algorithms and data structures for each module Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Slide 1 10 Overview of the Traditional Phases contd Slide 1 11 Implementation phase Translate the modules into a programming language Integrate the modules Maintenance phase Modify the system Remove any remaining faults Extend the system in some way Retirement The system no longer provides a useful service Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Why There Is No Planning Phase Slide 1 12 We cannot plan until we have accurate detailed information There are three types of planning activities There is preliminary planning at the start of the project The project management plan is drawn up after the specifications have been approved by the client Management monitor the plan all through the project Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Why There Is No Planning Phase contd Slide 1 13 Planning activities are carried out all through the life cycle There is no separate planning phase Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Why There is No Testing Phase Checking the information system just before delivery is much too late An information system must be checked continually There is no separate testing phase Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Slide 1 14 Why There Is No Documentation Phase Slide 1 15 The documentation must be complete correct and up to date at all times Personnel turnover in the information system industry Performing a phase requires the documentation from the previous phase Testing activities require documentation Maintenance activities require documentation There is no separate documentation phase Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Systems Analysis and Design Slide 1 16 The word analysis is used in two different ways Analysis Phase 2 Systems analysis Phases 1 and 2 The term systems analyst is also used in two different ways Responsible for Phases 1 and 2 or Responsible for Phases 1 2 and 3 The second usage is more common That is the way systems analyst is used in this book Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Maintenance Bad information systems are thrown away Good information systems are maintained for many years Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Slide 1 17 The Financial Implications of Maintenance Slide 1 18 For very 1 spent on development at least 2 is spent on maintenance Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Maintenance Activities There are three main maintenance activities Corrective maintenance Slide 1 19 Fixing faults Perfective maintenance Adding functionality Adoptive maintenance Making changes because the environment changes Enhancement Corrective Perfective maintenance Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Software Organizations Software Computer program code documentation Many organizations produce software They employ systems analysts Some organizations outsource Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Slide 1 20 Software Organizations Organizations like Microsoft and Oracle produce software As a primary product Slide 1 21 Organization like General Motors and General Electric produce software But not as a primary product Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Typical Information Systems Division Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Slide 1 22 Information Technology Professionals Technical positions Programmer Programmer analyst Systems analyst Alternative career path Business analyst Acquire programming skills Systems analyst Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Slide 1 23 Information Technology Professionals contd Slide 1 24 Management hierarchy Manager for information system development Vice President for information system development Chief information officer CIO Chief executive officer CEO Copyright 2004 by The McGraw Hill Companies Inc All rights reserved Essential Systems Analyst Skills Slide 1 25 Technical skills Communication skills


View Full Document

Access the best Study Guides, Lecture Notes and Practice Exams

Loading Unlocking...
Login

Join to view chap01 INTRODUCTION TO INFORMATION SYSTEMS and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view chap01 INTRODUCTION TO INFORMATION SYSTEMS and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?