CMS 370 Systems Analysis

1
CMS 370- Systems Analysis

• Jackie Trent

2
Session 1

• Introductions
• Administrative Tasks
• Course Objectives and Expectations
• Chapters One and Two

3
Administrative Tasks

• Sign in sheets
• Attendance
• Academic Dishonesty
• Center for Academic Excellence
• 884-2732 ext 251
• Syllabus
• Course Book - Systems Analysis and Design in a
  Changing World, 3nd Edition, Satzinger, Jackson,
  Burd

4
Introductions

• Name
• What is a system analysis?
• Previous course work in analysis and database

5
Course Objectives/Expectations

• Use a variety of techniques to perform
  requirements analysis and initiate systems
  design.
• Become exposed to CASE base tools and database
  applications
• Homework on time and complete.
• Open Forum qs, comments, suggestions

6
Grades/Exams

• Homework assignments (30)
• Mid Term Exam (20)
• Final Project (20)
• Final Exam (20)
• Class participation (10)

7
Course Format

• Lecture combined with on going in-class example
• Homework Assignments Build to final project
• Support website http//pubweb.csf.edu/jtrent
• Online exams to reinforce topics

8
Session One - -Chapters 1 2

• Explain key role of a systems analyst in business
  and types of systems an analyst might work on
• Describe the analysts role in a system
  development project
• Explain the various phases of the systems
  development lifecycle (SDLC)
• Explain the elements of project management and
  the responsibilities of a project manager
• Explain the activities in the project planning
  phase of the SDLC

9
Systems and Systems Analysis

• Information Systems
• Crucial to success of modern business
  organizations
• Constantly being developed to make business more
  competitive
• Impact productivity and profits
• Keys to successful systems development
• Thorough systems analysis and design
• Understanding what business requires

10
Overview (continued)

• Systems analysis what system should do
• Systems design how components of information
  system should be physically implemented
• Systems analyst uses analysis and design
  techniques to solve business problems with
  information technology

11
Information Systems and SubsystemsFigure 1-2
12
Information Systems and Component PartsFigure
1-3
13
System Boundary vs. Automation BoundaryFigure
1- 4
14
Types of Information SystemsFigure 1-5
15
The Analyst

• Business problem solver
• Has practical knowledge
• Computers
• Programming
• Understands business problems
• Uses logical methods for solving problems

16
Skills of the Analyst

• Technical Knowledge
• Business Knowledge
• People Skills

17
Approach to Problem SolvingFigure 1-1
Research and understand the problem
Verify that the benefits of solving the problem
outweigh the costs
Define the requirements for solving the problem
Develop a set of possible solutions (alternatives)
Decide which solution is best and make a
recommendation
Define the details of the chosen solution
Implement the solution
Monitor to make sure that you obtain the desired
results
18
Systems Development and problem-solving

• In line with solving to business problem-solving
• Organization recognizes problem (Project
  Planning)
• Project team investigates, understands problem
  and solution requirements (Analysis)
• Solution is specified in detail (Design)
• System that solves problem built and installed
  (Implementation)
• System used, maintained, and enhanced to continue
  to provide intended benefits (Support)

19
Systems Development Life Cycle (SDLC)

• Systems development life cycle (SDLC)
• Provides overall framework for managing system
  development process
• Two main approaches to SDLC
• Traditional approach structured systems
  development and information engineering
• Object-oriented approach object technologies
  requires different approach to analysis, design,
  and programming
• All projects use some variation of SDLC

20
Systems Development Life Cycle (SDLC)

• Systems development project
• Planned undertaking with fixed beginning and end
• Produces desired result or product
• Can be a large job of thousands of hours of
  effort or a small one month project
• Successful development project
• Provides a detailed plan to follow
• Organized, methodical sequence of tasks and
  activities
• Produces reliable, robust, and efficient system

21
SDLC Concepts

• Systems development project
• Planned undertaking with fixed beginning and end
• Produces desired result or product
• Can be a large job of thousands of hours of
  effort or a small one month project
• Successful development project
• Provides a detailed plan to follow
• Organized, methodical sequence of tasks and
  activities
• Produces reliable, robust, and efficient system

22
Phases of the SDLC

• Project planning initiate, ensure feasibility,
  plan schedule, obtain approval for project
• Analysis understand business needs and
  processing requirements
• Design define solution system based on
  requirements and analysis decisions
• Implementation construction, testing, user
  training, and installation of new system
• Support keep system running and improve

23
IS Development PhasesFigure 2-1
24
Planning Phase

• Define problem
• Confirm project feasibility
• Produce project schedule
• Staff the project
• Launch the project

25
Analysis Phase

• Gather information
• Problem Domain
• Application
• Define system requirements
• Build prototypes for discovery of requirements
• Prioritize requirements
• Generate and evaluate alternatives
• Review recommendations with management

26
Design Phase

• Design and integrate the network
• Design the application architecture
• Design the user interfaces
• Design the system interfaces
• Design and integrate the database
• Prototype for design details
• Design and integrate the system controls

27
Implementation Phase

• Construct software components
• Verify and test
• Convert data
• Train users and document the system
• Install the system

28
Support Phase

• Maintain the system
• Enhance the system
• Support the users
• Help desk

29
Scheduling of Project Phases

• Considerations
• Migration from waterfall approach to
• overlapping and concurrent phases
• Efficiency
• Dependency
• Iteration
• Ripple effect

30
Overlap of Systems Development ActivitiesFigure
2-2
31
Methodologies and Models

• Methodologies
• Comprehensive guidelines to follow for completing
  every SDLC activity
• Collection of models, tools, and techniques
• Models
• Representation of an important aspect of real
  world, but not same as real thing
• Abstraction used to separate out aspect
• Diagrams and charts
• Project planning and budgeting aids

32
Tools and Techniques

• Tools
• Software support that helps create models or
  other required project components
• Range from simple drawing programs to complex
  CASE tools
• Techniques
• Collection of guidelines that help analyst
  complete system development activity or task
• Can be step-by-step instructions or just general
  advice

33
Relationships Among Components of a Methodology
34
Two Approaches to System Development

• Traditional Approach
• Also called structured system development
• Structured analysis and design technique (SADT)
• Define what system needs to do (processing
  requirements)
• Define data system needs to store and use (data
  requirements)
• Define inputs and outputs
• Define how functions work together to accomplish
  tasks
• Data flow diagrams and entity relationship
  diagrams show results of structured analysis

35
Two Approaches to System Development

• Object Oriented Approach
• Views information system as collection of
  interacting objects that work together to
  accomplish tasks
• Objects - things in computer system that can
  respond to messages
• No processes, programs, data entities, or files
  are defined just objects
• Defines types of objects that do work of system
• Shows how objects interact with users to complete
  tasks

36
Tools to Support System Development

• Computer-Aided System Engineering (CASE)
• Automated tools to improve the speed and quality
  of system development work
• Contains database of information about system
  called repository
• Upper CASE - support for analysis and design
• Lower CASE - support for implementation
• ICASE - integrated CASE tools

37
Conclusions

• Systems analyst involves broad range of
  activities requiring a broad range of skills
• SDLC provides vital framework for activities
• Two main approaches to SDLC
• Planning first is vital to long term success

38
Assignment

• Read and Review Chapters 1-2
• Read Chapter 3, 4, 8
• Assignment 1Investigate work environment and
  identify current tools at work that are used in
  planning. Write a one page paper describing
  extent of use. Describe successes and failures
  of the tool.