1. 1 Introduction Chapter 1

2. 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization. The primarily goal is to create value for the organization.

3. 3 Key Ideas The systems analyst is a key person analyzing the business, identifying opportunities for improvement, and designing information systems to implement these ideas. It is important to understand and develop through practice the skills needed to successfully design and implement new information systems.

4. 4 THE SYSTEMS DEVELOPMENT LIFE CYCLE

5. 5 Major Attributes of the Lifecycle The project Moves systematically through phases where each phase has a standard set of outputs Produces project deliverables Uses deliverables in implementation Results in actual information system Uses gradual refinement

6. 6 Project Phases Planning Why build the system? Analysis Who, what, when, where will the system be? Design How will the system work? Implementation System delivery

7. 7 A “Simple” Process for Making Lunch

8. 8 Identifying business value Analyze feasibility Technical feasibility (Can we do?) Economic feasibility (Can it provides value?) Organizational feasibility (Will it be used?) Develop work plan Staff the project Control and direct project Planning

9. 9 Analysis Information gathering Process modeling Data modeling Analysis

10. 10 Physical design Architectural design Interface design Database and file design Program design Design

11. 11 Construction Installation Implementation

12. 12 Processes and Deliverables ProcessProduct Planning Analysis Design Implementation Project Plan System Proposal System Specification New System and Maintenance Plan

13. 13 THE EVOLUTION OF SYSTEM DEVELOPMENT

14. 14 What Is a Methodology? A formalized approach or series of steps Writing code without a well-thought-out system request may work for small programs, but rarely works for large ones.

15. 15 Structured Design Projects move methodically from one to the next step Generally, a step is finished before the next one begins

16. 16 Waterfall Development Method

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

18. 18 Alternatives to the SDLC Rapid Application Development (RAD) Phased Development Prototyping Throw-Away Prototyping

19. 19 Rapid Application Development Critical elements CASE tools JAD sessions Fourth generation/visualization programming languages Code generators

20. 20 Rapid Application Development Categories Phased development A series of versions Prototyping System prototyping Throw-away prototyping Design prototyping

21. 21 How Prototyping Works

22. 22 Throwaway Prototyping

23. 23 Object-Oriented Analysis and Design Attempts to balance emphasis on data and process Uses Unified Modeling Language (UML) for diagramming Use-case Driven Architecture Centric Iterative and Incremental

24. 24 BASIC CHARACTERISTICS OF OBJECT-ORIENTED SYSTEMS

25. 25 Key Elements Classes -- template to define objects Instances -- specific examples of class members Objects -- building block of the system Attributes -- describe data aspects of the object Methods -- the processes the object can perform Messages -- instructions sent to or received from other objects

26. 26 A Class and Its Objects PATIENT -Name -Birthdate -Phone Number +Insert ()() +Delete ()() PATIENT 1: TOP PACKAGE: PATIENT -Name = Teresa Marks -Birthdate = March 16, 1975 -Phone number = 314-997-3456 PATIENT 2: TOP PACKAGE: PATIENT -Name = Mel Bourne -Birthdate = May 11, 1965 -Phone number = 314-997-3219 Attributes Methods Class Instantiated Objects of the Class

27. 27 The Key to Reusability Information hiding is the principle that only information required to use the object is available outside the object Encapsulation is the mechanism that combines data and processes in a single object

28. 28 Class Hierarchy

29. 29 Inheritance Abstract Class Concrete Class

30. 30 Polymorphism

31. 31 OBJECT-ORIENTED ANALYSIS AND DESIGN USING UML

32. 32 UML The full UML provides 9 separate diagramming techniques Structure Diagrams Class Diagram, Object Diagram Package Diagram, Deployment Diagram Component Diagram Behavioral Diagrams Activity Diagram, Sequence Diagram Use Case Diagram, Interaction Diagram State Machine

33. 33 PROJECT TEAM ROLES AND SKILLS

34. 34 Information Systems Roles Business analyst System analyst Infrastructure analyst Change management analyst Project manager