1 / 39

IS 421 Information Systems Management

Learn about the course objectives, the systems development life cycle, methodologies, and key roles and skills in systems development projects.

josephjohnson
Download Presentation

IS 421 Information Systems Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IS 421Information Systems Management James Nowotarski 16 September 2002

  2. Today’s Objectives • Understand what the course is about (i.e., course objectives) • Understand how the course will achieve its objectives • Begin to get acquainted • Understand the systems development life cycle (SDLC) • Understand what a systems development methodology is • Understand key roles and skills on a systems development project

  3. Today’s agenda Topic Duration • Questionnaire & Intros 30 minutes • Systems Development Life Cycle 45 minutes *** Break 15 minutes • Course Overview 30 minutes • Methodologies 45 minutes • Roles and Skills 30 minutes

  4. People Process Technology

  5. Today’s agenda Topic Duration • Questionnaire & Intros 30 minutes • Systems Development Life Cycle 45 minutes *** Break 15 minutes • Course Overview 30 minutes • Methodologies 45 minutes • Roles and Skills 30 minutes

  6. Planning Analysis Design SDLC The systems development life cycle (SDLC) is a description of the phases of an information system Implementation

  7. SDLC Key Question: Deliverables Steps Techniques

  8. Planning Key Question: Deliverables System request Feasibility study Project plans Project standards Development environment Project organization & staffing Risk assessment Why build the system? Steps Techniques 1. Identify business value 2. Analyze feasibility 3. Develop work plan 4. Staff the project 5. Control and direct the project Net present value (NPV) Function point analysis Critical path analysis Subcontracting

  9. Analysis Key Question: Deliverables Functional requirements Quality requirements Data model Process model What does the system need to do? Steps Techniques 1. Gather requirements 2. Create data model 3. Create process model Interviewing Observation Entity-relationship modeling Normalization Data flow modeling

  10. Design Key Question: Deliverables System architecture design Application design User interface design Database design Program design How will the system work? Steps Techniques 1. Design system architecture 2. Design application 3. Design user interfaces 4. Design databases 5. Design programs Prototyping Denormalization Modularization/Components

  11. Implementation Key Question: Deliverables Programs Databases Converted data End user training Operations processes Does the system work? Steps Techniques 1. Build the programs 2. Build the databases 3. Test the system 4. Develop and conduct training 5. Convert the data 6. Migrate to production status Code walkthroughs White box testing Stress testing Parallel testing

  12. Planning Analysis Design Scope of IS 421 The focus of IS 421 is the Analysis phase Implementation

  13. Today’s agenda Topic Duration • Questionnaire & Intros 30 minutes • Systems Development Life Cycle 45 minutes *** Break 15 minutes • Course Overview 30 minutes • Methodologies 45 minutes • Roles and Skills 30 minutes

  14. Course Objectives • Understand the systems development life cycle • Be able to perform a feasibility analysis • Be able to create a project work plan • Understand how to gather system requirements • Be able to create data flow diagrams • Be able to create entity relationship diagrams

  15. Your grade Assignments 30% Quizzes 30% Final Exam 30% Participation 10% -------- 100%

  16. IS 421 Core Exam Core Exam

  17. Core Knowledge Exam Logistics • December 3, 2002 beginning at 6pm • Each exam lasts 75 minutes • Location: Loop campus • “Specific building and room locations will be posted on the CTI web site the day before the exam” • Deadline for applications is November 19, 2002 • IS 421 Core Exam Study Guide can be accessed from http://www.cti.depaul.edu/programs/core_guide.asp

  18. Course Map Contents 1. Introduction Planning Phase 2. Project Initiation 3. Project Management Analysis Phase 4. Systems Analysis 5. Gathering Information 6. Process Modeling 7. Data Modeling 1 2 3 4 5 6 7 8 9 10 11 Week Core Exam Review Assignments Quizzes Final

  19. Course Assignments • Assignment 1 - System Request • Assignment 2 - Interview Report • Assignment 3 - Data Model • Assignment 4 - Process Model • Assignment 5 - Project Plan

  20. My role • Facilitate learning • Plan, prepare, and conduct lectures and learning activities • Assess student progress and provide feedback • Relate class concepts to real-world problems • Provide classroom environment conducive to learning • Clearly state expectations • Gather and implement suggestions for improving the class • Keep it fun

  21. email: jnowotarski@cti.depaul.edu • phone: 708-352-2930 • office hours: Mondays, 4:15-5:45

  22. Your role • Be proactive • Share your experience • Come to class prepared • Collaborate with other students as appropriate • Ask if you don’t understand or if I’m not clear • Provide constructive feedback (“This class would be better if . . .”)

  23. Today’s agenda Topic Duration • Questionnaire & Intros 30 minutes • Systems Development Life Cycle 45 minutes *** Break 15 minutes • Course Overview 30 minutes • Methodologies 45 minutes • Roles and Skills 30 minutes

  24. What Is a Methodology? • A formalized approach or series of steps • Examples • Structured Methods • Information Engineering • Rapid Application Development • Object-Oriented Methods • Agile Methods

  25. Waterfall Development Method Waterfall development is the most common form of structured methods

  26. Pros and Cons of the Waterfall Method Pros Cons Identifies systems requirements long before programming begins Design must be specified on paper before programming begins Long time between system proposal and delivery of new system

  27. Alternatives to the Waterfall Method • Structured Methods • Parallel Development • Rapid Application Development (RAD) • Phased Development • Prototyping • Throw-Away Prototyping

  28. Parallel Development Method

  29. Pros and Cons of Parallel Development Pros Cons Reduces Scheduled Time Still Uses Paper Documents Less Chance of Rework Sub-projects May Be Difficult to Integrate

  30. Computer-aided software engineering (CASE) tools Joint application design (JAD) sessions Fourth generation/visualization programming languages Code generators Timeboxing (90-day implementation) Rapid Application Development (RAD)

  31. Phased development A series of versions Prototyping System prototyping Throw-away prototyping Design prototyping Three RAD Categories

  32. How Prototyping Works

  33. Throwaway Prototyping

  34. Criteria for Selecting the Appropriate Methodology • Clear user requirements • Familiar technology • Complexity • Reliability • Time schedule • Schedule visibility

  35. Today’s agenda Topic Duration • Questionnaire & Intros 30 minutes • Systems Development Life Cycle 45 minutes *** Break 15 minutes • Course Overview 30 minutes • Methodologies 45 minutes • Roles and Skills 30 minutes

  36. Systems Development Project Roles • Business analyst • System analyst • Infrastructure analyst • Change management analyst • Project manager

  37. Summary • The Systems Development Lifecycle consists of four stages: Planning, Analysis, Design, and Implementation • There are multiple developmentmethodologies. There is no “one size fits all” solution. Methodologies must be carefully selected and tailored based on the organization’s requirements. • There are five major team roles: business analyst, systems analyst, infrastructure analyst, change management analyst and project manager.

  38. Topics for September 23 • Read Chapters 1-2 • End of chapter questions: • Ch. 1:  1, 3-6, 17, 19-20 • Ch. 2:  1, 5, 7, 13, 15

More Related