View
222
Download
2
Tags:
Embed Size (px)
Citation preview
IS 421Information Systems Management
James Nowotarski
16 September 2002
• 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
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
Technology
ProcessPeople
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
SDLC
The systems development life cycle (SDLC) is a description of the phases of an information system
Planning Analysis Design Implementation
SDLC
Key Question: Deliverables
Steps Techniques
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
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
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
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
Scope of IS 421
The focus of IS 421 is the Analysis phase
Planning Analysis Design Implementation
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
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
Your grade
Assignments 30%
Quizzes 30%
Final Exam 30%
Participation 10%
--------
100%
IS 421
Core Exam
Core Exam
• 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
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
Course Assignments
• Assignment 1 - System Request
• Assignment 2 - Interview Report
• Assignment 3 - Data Model
• Assignment 4 - Process Model
• Assignment 5 - Project Plan
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
• email: [email protected]• phone: 708-352-2930• office hours: Mondays, 4:15-5:45
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 . . .”)
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
What Is a Methodology?
• A formalized approach or series of steps• Examples
– Structured Methods
– Information Engineering
– Rapid Application Development
– Object-Oriented Methods
– Agile Methods
Waterfall Development Method
Waterfall development is the most common form of structured methods
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
Alternatives to the Waterfall Method
• Structured Methods– Parallel Development
• Rapid Application Development (RAD)– Phased Development
– Prototyping
– Throw-Away Prototyping
Parallel Development Method
Pros and Cons of Parallel Development
Pros Cons
Reduces Scheduled Time
Less Chance ofRework
Still Uses PaperDocuments
Sub-projects May BeDifficult to Integrate
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)
Three RAD Categories
• Phased development– A series of versions
• Prototyping– System prototyping
• Throw-away prototyping– Design prototyping
How Prototyping Works
Throwaway Prototyping
Criteria for Selecting the Appropriate Methodology
• Clear user requirements• Familiar technology• Complexity• Reliability• Time schedule• Schedule visibility
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
Systems Development Project Roles
• Business analyst• System analyst• Infrastructure analyst• Change management analyst• Project manager
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.
• 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