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

2. 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

3. Topic Duration Questionnaire & Intros30 minutes Systems Development Life Cycle45 minutes *** Break15 minutes Course Overview30 minutes Methodologies45 minutes Roles and Skills30 minutes Today’s agenda

4. Technology Process People

5. Topic Duration Questionnaire & Intros30 minutes Systems Development Life Cycle45 minutes *** Break15 minutes Course Overview30 minutes Methodologies45 minutes Roles and Skills30 minutes Today’s agenda

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

7. SDLC Key Question:Deliverables StepsTechniques

8. Planning Key Question:Deliverables StepsTechniques Why build the system? System request Feasibility study Project plans Project standards Development environment Project organization & staffing Risk assessment 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 StepsTechniques What does the system need to do? Functional requirements Quality requirements Data model Process model 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 StepsTechniques How will the system work? System architecture design Application design User interface design Database design Program design 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 StepsTechniques Does the system work? Programs Databases Converted data End user training Operations processes 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. Scope of IS 421 The focus of IS 421 is the Analysis phase PlanningAnalysisDesign Implementation

14. Topic Duration Questionnaire & Intros30 minutes Systems Development Life Cycle45 minutes *** Break15 minutes Course Overview30 minutes Methodologies45 minutes Roles and Skills30 minutes Today’s agenda

15. 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

16. Your grade Assignments30% Quizzes30% Final Exam30% Participation10% -------- 100%

17. IS 421 Core Exam

18. 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

19. 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 1234678910115 Assignments Quizzes Final Week Core Exam Review

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

21. 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

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

23. 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...”)

24. Topic Duration Questionnaire & Intros30 minutes Systems Development Life Cycle45 minutes *** Break15 minutes Course Overview30 minutes Methodologies45 minutes Roles and Skills30 minutes Today’s agenda

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

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

27. Pros and Cons of the Waterfall Method ProsCons 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

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

29. Parallel Development Method

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

31. 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)

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

33. How Prototyping Works

34. Throwaway Prototyping

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

36. Topic Duration Questionnaire & Intros30 minutes Systems Development Life Cycle45 minutes *** Break15 minutes Course Overview30 minutes Methodologies45 minutes Roles and Skills30 minutes Today’s agenda

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

38. 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.

39. 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