1. 2 Systems Analysis – ITEC 3155 Systems Analysis Tasks

2. 2 Systems Analysis and Design in a Changing World, 4th Edition 2 Learning Objectives u Explain the purpose and various phases of the systems development life cycle (SDLC) u Describe the two overall approaches used to develop information systems: the traditional method and the object-oriented method u Explain the differences between a model, a tool, a technique, and a methodology

3. 2 Systems Analysis and Design in a Changing World, 4th Edition 3 Learning Objectives ( continued ) u Describe some of the variations of the systems development life cycle (SDLC) u Describe the key features of current trends in systems development: the Unified Process (UP), Extreme Programming (XP), Agile Modeling, and Scrum u Explain how automated tools are used in system development

4. 2 Systems Analysis and Design in a Changing World, 4th Edition 4 The Systems Development Lifecycle (SDLC) u Systems development life cycle (SDLC) l The methodology that provides overall framework for managing systems development process. The phases a project or system goes through from its beginning to project or system completion. u In effect, the development process describes how the project is to be done. l The SDLC is a logical approach to building systems l The SDLC avoids the problem of rushing to create code l The SDLC allows thoughtful review of the project and whether to proceed further u All projects use some variation of SDLC

5. 2 Systems Analysis and Design in a Changing World, 4th Edition 5 SDLC and Problem Solving u Similar to problem-solving approach in lecture 1 l Organization recognizes problem (project planning) l Project team investigates, understands problem and solution requirements (analysis) l Solution is specified in detail (design) l System that solves problem is built and installed (implementation) l System used, maintained, and enhanced to continue to provide intended benefits (support)

6. 2 Systems Analysis and Design in a Changing World, 4th Edition 6 Five Phases of the Traditional SLDC (p.38) u Systems (Project) planning – initiate, ensure feasibility, plan schedule, obtain approval for project u Systems Analysis – understand business needs and processing requirements u Systems Design – define solution system based on requirements and analysis decisions u Systems Implementation – construct, test, train users, and install new system u Systems Support – keep system running

7. 2 Systems Analysis and Design in a Changing World, 4th Edition 7 Two Approaches to System Development (pp. 51-58) u Traditional approach l Also called structured system development l Structured analysis and design technique (SADT) l Includes information engineering (IE) u Object-oriented approach l Also called OOA, OOD, and OOP l Views information system as collection of interacting objects that work together to accomplish tasks

8. 2 Systems Analysis and Design in a Changing World, 4th Edition 8 Differences in the Traditional Structured vs. Object-Oriented approaches u Structured approaches take a top-down or decomposition approach, breaking models into further refined diagrams with more detail. Is therefore a sequential approach and assumes development from scratch. OO is more iterative and builds part of the system before the system is fully analyzed. u Both approaches focus on data and processes u Both approaches use models (abstractions) of the real world. u Both approaches use IDEs or CASE tools

9. 2 Systems Analysis and Design in a Changing World, 4th Edition 9 “Waterfall” Approach to the SDLC (p. 39) The old standard was known as the Waterfall method. This method was sequential, not conducive to changing requirements. (p.39)

10. 2 Systems Analysis and Design in a Changing World, 4th Edition 10 Data Flow Diagram (DFD) Created Using Structured Analysis Technique (Figure 2-15) u Dataflow diagrams (DFDs) – shows processes with database interactions or data being passed between processes. (p.54 )

11. 2 Systems Analysis and Design in a Changing World, 4th Edition 11 Entity-Relationship Diagram (ERD) Created Using Structured Analysis Technique Show data at rest (or static data). Static means a snapshot. u “Information engineering” approach if data is emphasized over processes / functions. Also IE begins by looking at the strategic plan of the organization and decomposing it into data (p. 55)

12. 2 Systems Analysis and Design in a Changing World, 4th Edition 12 Criticism of structured approaches u In structured approaches, the emphasis is on the analysis phase and models that are static. They do not show the interactions of components (such as the logic or programming code). The result is that often there is a gap between drawing DFDs and ERDs and the actual detailed design and implementation phases.

13. 2 Systems Analysis and Design in a Changing World, 4th Edition 13 Newer Approaches to the SDLC u Spiral Model (Fig 2-6) l Project cycles through development activities over and over until project is complete l Prototype created by end of each cycle l Focuses on mitigating risk l Uses Iteration

14. 2 Systems Analysis and Design in a Changing World, 4th Edition 14 u Iteration – Work activities are repeated l Each iteration refines previous result l Approach assumes no one gets it right the first time l There are a series of mini projects for each iteration Iteration (p. 56)

15. 2 Systems Analysis and Design in a Changing World, 4th Edition 15 Methodologies and Models (pp. 47-48) u Methodologies l Comprehensive guidelines to follow for completing every SDLC activity l Collection of models, tools, and techniques u Models l Representation of an important aspect of real world, but not same as real thing l Abstraction used to separate out aspect l Diagrams and charts l Project planning and budgeting aids

16. 2 Systems Analysis and Design in a Changing World, 4th Edition 16 Tools and Techniques (pp. 48-49) u Tools l Software support that helps create models or other required project components l Range from simple drawing programs to complex CASE tools to project management software u Techniques l Collection of guidelines that help analysts complete a system development activity or task l Can be step-by-step instructions or just general advice

17. 2 Systems Analysis and Design in a Changing World, 4th Edition 17 Object-Oriented Approach u Completely different approach to information systems u Views information system as collection of interacting objects that work together to accomplish tasks l Objects – things in computer system that can respond to messages l Conceptually, no processes, programs, data entities, or files are defined – just objects u OO languages: Java, C++, C#.NET, VB.NET

18. 2 Systems Analysis and Design in a Changing World, 4th Edition 18 Object-Oriented Approach ( continued ) u Object-oriented analysis (OOA) l Defines types of objects users deal with l Shows use cases are required to complete tasks u Object-oriented design (OOD) l Defines object types needed to communicate with people and devices in system l Shows how objects interact to complete tasks l Refines each type of object for implementation with specific language of environment u Object-oriented programming (OOP) l Writing statements in programming language to define what each type of object does

19. 2 Systems Analysis and Design in a Changing World, 4th Edition 19 Class Diagram Created During OO Analysis

20. 2 Systems Analysis and Design in a Changing World, 4th Edition 20 SDLC Variations u Many variations of SDLC in practice l Based on variation of names for phases l No matter which one, activities/tasks are similar u Some increase emphasis on people l User-centered design, participatory design u Some increase speed of development l Rapid application development (RAD) l Prototyping

21. 2 Systems Analysis and Design in a Changing World, 4th Edition 21 Current Trends in Development u The Unified Process (UP) u Extreme Programming (XP) u Agile Modeling u Scrum

22. 2 Systems Analysis and Design in a Changing World, 4th Edition 22 The Unified Process (UP) (pp. 61-62) u Object-oriented development approach u Offered by IBM / Rational l Booch, Rumbaugh, Jacobson u Unified Modeling Language (UML) used primarily for modeling u UP defines four life cycle phases l Inception, elaboration, construction, transition

23. 2 Systems Analysis and Design in a Changing World, 4th Edition 23 The SDLC Phases of the UP u Four life cycle “phases”: l Inception - scope, participants, business purpose and initial budget and schedule estimates. Scope is defined through a context diagram and use cases. Unified Modeling Language (UML) used primarily for modeling l Elaboration – defines requirements, designs the solution, implement the solution using use case diagrams, class diagrams, sequence diagrams. Costs and benefit estimates occur at the end of this phase. l Construction – additional requirements, design and implementation l Transition – turn system over to the users u Note that Inception and Elaboration are similar to Systems Planning and Analysis in the traditional SDLC

24. 2 Systems Analysis and Design in a Changing World, 4th Edition 24 The Unified Process (UP) ( continued ) u Reinforces six best practices of systems development l Develop iteratively l Define and manage system requirements l Use component architectures l Create visual models l Verify quality l Control changes

25. 2 Systems Analysis and Design in a Changing World, 4th Edition 25 Extreme Programming (XP) (p.62) u Recent, lightweight, development approach to keep process simple and efficient u Describes system support needed and required system functionality through informal user stories u Has users describe acceptance tests to demonstrate defined outcomes u Relies on continuous testing and integration, heavy user involvement, programming done by small teams

26. 2 Systems Analysis and Design in a Changing World, 4th Edition 26 Agile Modeling (pp. 62-63) u Hybrid of XP and UP; has more models than XP, fewer documents than UP u Interactive and Incremental Modeling l Apply right models l Create several models in parallel l Model in small increments u Teamwork l Get active stakeholder participation l Encourage collective ownership l Model with others and display models publicly

27. 2 Systems Analysis and Design in a Changing World, 4th Edition 27 Agile Modeling ( continued ) u Simplicity l Use simple content l Depict models simply l Use simplest modeling tools u Validation l Consider testability l Prove model is right with code

28. 2 Systems Analysis and Design in a Changing World, 4th Edition 28 Scrum (p.63) u For highly adaptive project needs u Respond to situation as rapidly as possible u Scrum refers to rugby game l Both are quick, agile, and self-organizing u Team retains control over project u Values individuals over processes

29. 2 Systems Analysis and Design in a Changing World, 4th Edition 29 Tools to Support System Development (pp.63-67) u Computer-aided system engineering (CASE) l Automated tools to improve the speed and quality of system development work l CASE systems offer tools to automate, manage and simplify the development process. CASE is available for traditional structured approaches as well as object-oriented approaches. u Summarizing initial requirements u Developing flow diagrams u Scheduling development tasks u Preparing documentation u Controlling software versions (configuration management) u Developing or generating program code (forward engineering) u Generating models from existing code (reverse engineering)

30. 2 Systems Analysis and Design in a Changing World, 4th Edition 30 CASE Tool Repository Contains All System Information

31. 2 Systems Analysis and Design in a Changing World, 4th Edition 31 Summary u System development projects are organized around the systems development life cycle (SDLC) u Some projects use a predictive approach to the SDLC, and others use a more adaptive approach to the SDLC u SDLC phases include project planning, analysis, design, implementation, and support

32. 2 Systems Analysis and Design in a Changing World, 4th Edition 32 Summary ( continued ) u In practice, phases overlap, and projects contain many iterations of analysis, design, and implementation u Models, techniques, and tools make up a system development methodology u System development methodology provides guidelines to complete every activity in the SDLC

33. 2 Systems Analysis and Design in a Changing World, 4th Edition 33 Summary ( continued ) u System development methodologies are based on traditional approach or object-oriented approach u Current trends include: Extreme Programming (XP), Unified Process (UP), Agile Modeling, and Scrum u CASE tools are designed to help analysts complete system development tasks

34. 2 Systems Analysis and Design in a Changing World, 4th Edition 34 Next Class u Read Chapter 4 u Read “Make requirements gathering interviews less stressful for users” u Assignments for Term Project