1 / 26

Overview of Systems Analysis

Overview of Systems Analysis. Key Ideas. Many systems failures were because analysts tried to build wonderful systems without understanding the organization and applying a systematic approach. The primarily goal is to create value for the organization. Key Ideas.

dante-valencia
Download Presentation

Overview of Systems Analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Overview of Systems Analysis

  2. Key Ideas • Many systems failures were because analysts tried to build wonderful systems without understanding the organization and applying a systematic approach. • The primarily goal is to create value for the organization.

  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. Types of Information Systems • Transaction Processing Systems • Management Information Systems • Decision Support Systems • Expert Systems Development of these systems require a good understanding of business processes and data

  5. Systems Development Lifecycle Approach • The project • Moves systematically through phases where each phase has a standard set of outputs • Produces project deliverables • Uses deliverables in implementation • Uses gradual refinement and an iterative approach

  6. Project Phases • Planning • Why build the system? • Analysis • What will the system be? • Design • How will the system work? • Implementation • System delivery

  7. Planning • Identifying business value • Analyze feasibility • Develop work plan • Staff the project • Control and direct project

  8. Analysis • Analysis • Information gathering • Process modeling • Data modeling

  9. Design • Physical design • Architectural design • Interface design • Database and file design • Program design

  10. Implementation • Construction • Verification and testing • Installation

  11. Process Product Project Plan System Proposal System Specification New System and Maintenance Plan Planning Analysis Design Implementation Processes and Deliverables

  12. SYSTEM DEVELOPMENTMETHODOLOGIES

  13. What Is a Methodology? • A formalized approach or series of steps

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

  15. Waterfall Development Method

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

  17. Parallel Development

  18. Alternatives to the SDLC • Rapid Application Development (RAD) • Prototyping

  19. Critical elements CASE (computer-aided software engineering) tools JAD (join development design) sessions Fourth generation/visualization programming languages Code generators Rapid Application Development

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

  21. How Prototyping Works

  22. 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 • Functional, Static, and Dynamic views • Iterative and Incremental

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

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

  25. 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 The Key to Reusability

  26. UML • Unified Modeling Language • The full UML provides 9 separate diagramming techniques

More Related