![Page 1: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/1.jpg)
IS 421Information Systems Management
James Nowotarski
16 September 2002
![Page 2: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/2.jpg)
• 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
Today’s Objectives
![Page 3: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/3.jpg)
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
Today’s agenda
![Page 4: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/4.jpg)
Technology
ProcessPeople
![Page 5: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/5.jpg)
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
Today’s agenda
![Page 6: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/6.jpg)
SDLC
The systems development life cycle (SDLC) is a description of the phases of an information system
Planning Analysis Design Implementation
![Page 7: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/7.jpg)
SDLC
Key Question: Deliverables
Steps Techniques
![Page 8: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/8.jpg)
Planning
Key Question: Deliverables
Steps Techniques
Why build the system?System requestFeasibility studyProject plansProject standardsDevelopment environmentProject organization & staffingRisk assessment
1. Identify business value2. Analyze feasibility3. Develop work plan4. Staff the project5. Control and direct the project
Net present value (NPV)Function point analysisCritical path analysisSubcontracting
![Page 9: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/9.jpg)
Analysis
Key Question: Deliverables
Steps Techniques
What does the system need to do?Functional requirementsQuality requirementsData modelProcess model
1. Gather requirements2. Create data model3. Create process model
InterviewingObservationEntity-relationship modelingNormalizationData flow modeling
![Page 10: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/10.jpg)
Design
Key Question: Deliverables
Steps Techniques
How will the system work?System architecture designApplication designUser interface designDatabase designProgram design
1. Design system architecture2. Design application3. Design user interfaces4. Design databases5. Design programs
PrototypingDenormalizationModularization/Components
![Page 11: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/11.jpg)
Implementation
Key Question: Deliverables
Steps Techniques
Does the system work?ProgramsDatabasesConverted dataEnd user trainingOperations processes
1. Build the programs 2. Build the databases3. Test the system4. Develop and conduct training5. Convert the data6. Migrate to production status
Code walkthroughsWhite box testingStress testingParallel testing
![Page 12: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/12.jpg)
Scope of IS 421
The focus of IS 421 is the Analysis phase
Planning Analysis Design Implementation
![Page 13: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/13.jpg)
![Page 14: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/14.jpg)
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
Today’s agenda
![Page 15: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/15.jpg)
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
![Page 16: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/16.jpg)
Your grade
Assignments 30%
Quizzes 30%
Final Exam 30%
Participation 10%
--------
100%
![Page 17: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/17.jpg)
IS 421
Core Exam
Core Exam
![Page 18: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/18.jpg)
• 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
Core Knowledge Exam Logistics
![Page 19: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/19.jpg)
Course Map
Contents
1. Introduction
Planning Phase2. Project Initiation3. Project Management
Analysis Phase4. Systems Analysis5. Gathering Information6. Process Modeling7. Data Modeling
1 2 3 4 6 7 8 9 10 115
Assignments
QuizzesFinal
Week
CoreExamReview
![Page 20: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/20.jpg)
Course Assignments
• Assignment 1 - System Request
• Assignment 2 - Interview Report
• Assignment 3 - Data Model
• Assignment 4 - Process Model
• Assignment 5 - Project Plan
![Page 21: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/21.jpg)
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
![Page 22: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/22.jpg)
• email: [email protected]• phone: 708-352-2930• office hours: Mondays, 4:15-5:45
![Page 23: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/23.jpg)
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 . . .”)
![Page 24: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/24.jpg)
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
Today’s agenda
![Page 25: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/25.jpg)
What Is a Methodology?
• A formalized approach or series of steps• Examples
– Structured Methods
– Information Engineering
– Rapid Application Development
– Object-Oriented Methods
– Agile Methods
![Page 26: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/26.jpg)
Waterfall Development Method
Waterfall development is the most common form of structured methods
![Page 27: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/27.jpg)
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
![Page 28: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/28.jpg)
Alternatives to the Waterfall Method
• Structured Methods– Parallel Development
• Rapid Application Development (RAD)– Phased Development
– Prototyping
– Throw-Away Prototyping
![Page 29: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/29.jpg)
Parallel Development Method
![Page 30: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/30.jpg)
Pros and Cons of Parallel Development
Pros Cons
Reduces Scheduled Time
Less Chance ofRework
Still Uses PaperDocuments
Sub-projects May BeDifficult to Integrate
![Page 31: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/31.jpg)
Rapid Application Development (RAD)
• Computer-aided software engineering (CASE) tools
• Joint application design (JAD) sessions• Fourth generation/visualization programming
languages• Code generators• Timeboxing (90-day implementation)
![Page 32: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/32.jpg)
Three RAD Categories
• Phased development– A series of versions
• Prototyping– System prototyping
• Throw-away prototyping– Design prototyping
![Page 33: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/33.jpg)
How Prototyping Works
![Page 34: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/34.jpg)
Throwaway Prototyping
![Page 35: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/35.jpg)
Criteria for Selecting the Appropriate Methodology
• Clear user requirements• Familiar technology• Complexity• Reliability• Time schedule• Schedule visibility
![Page 36: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/36.jpg)
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
Today’s agenda
![Page 37: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/37.jpg)
Systems Development Project Roles
• Business analyst• System analyst• Infrastructure analyst• Change management analyst• Project manager
![Page 38: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/38.jpg)
Summary
• The Systems Development Lifecycle consists of four stages: Planning, Analysis, Design, and Implementation
• There are multiple development methodologies. 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.
![Page 39: IS 421 Information Systems Management James Nowotarski 16 September 2002](https://reader036.vdocument.in/reader036/viewer/2022062407/56649d4b5503460f94a28481/html5/thumbnails/39.jpg)
• Read Chapters 1-2• End of chapter questions:
– Ch. 1: 1, 3-6, 17, 19-20
– Ch. 2: 1, 5, 7, 13, 15
Topics for September 23