is2210 systems analysis and systems design and change n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
IS2210: Systems Analysis and Systems Design and Change PowerPoint Presentation
Download Presentation
IS2210: Systems Analysis and Systems Design and Change

Loading in 2 Seconds...

play fullscreen
1 / 38

IS2210: Systems Analysis and Systems Design and Change - PowerPoint PPT Presentation


  • 119 Views
  • Uploaded on

IS2210: Systems Analysis and Systems Design and Change. Email: cathal.doyle@umail.ucc.ie Twitter: @InstCathalDoyle Website: www.cathaldoyle.com. Tutorials. Location: O’Rahilly Building (ORB) B.05 Start Date: Thursday 10/10/2013 (bi-weekly) Time: 5-6pm. Last Week….

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'IS2210: Systems Analysis and Systems Design and Change' - leroy


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
is2210 systems analysis and systems design and change

IS2210: Systems Analysis and Systems Design and Change

Email: cathal.doyle@umail.ucc.ie

Twitter: @InstCathalDoyle

Website: www.cathaldoyle.com

tutorials
Tutorials
  • Location: O’Rahilly Building (ORB) B.05
  • Start Date: Thursday 10/10/2013 (bi-weekly)
  • Time: 5-6pm
last week
Last Week…
  • From todays lesson you should…
    • Understand what constitutes an information system
    • Know the major role of Information Systems (IS)
    • Understand Analysis and Design
questions
Questions
  • What is the difference between data and information?
  • What are the five components of an information systems?
  • What is the difference between analysis and design?
learning outcomes
Learning Outcomes
  • From todays lecture you should:
    • Understand what SDLC is
    • Understand the five stages of SDLC
    • Understand the key deliverables of these five stages
why systems development
Why Systems Development?

To correct problem in existing system

To improve existing system

Outside group may mandate change

Competition can lead to change

how it can go
How It Can Go…
  • The next few slides are an exaggerated way systems development can go
  • However these are not unusual issues
  • How can we change that?
slide9

“ Tree Swing – hanging from branch which people can sit and swing on”

“Seat hanging from tree branches”

“Swing from tree hanging from tree branches which people can sit on”

slide10

Seat which hangs from a tree

Comfortable and brilliant tree swing

slide11

Obviously no documentation

Only partial instalment

Budgets overran

Was it required?

slide12

Customers may not fully know what they want.

Important to ask the correct questions!! - Errors and omissions can be costly.

Follow SDLC to ensure the correct steps are undertaken

Communication

Tyre Swing

guidelines for system development
Guidelines for System Development
  • Arrange tasks into phases (groups of activities)
  • Involve users (anyone for whom the system is being built)
  • Develop clearly defined standards (procedures the company expects employees to follow)
systems development lifecycle sdlc
Systems Development Lifecycle (SDLC)
  • A process that can be applied to create, or alter information systems
  • Consists of different models and methodologies that people use to develop/alter IS
  • It can be seen as a very structured, and methodological way of developing IS
emergence of sdlc
Emergence of SDLC
  • Winston Boyce conceived SDLC as an aid to programming, with two stages of analysis and coding in 1970
  • Further to this, Dr. Barry Boehm listed a number of the main phases of software development in 1974
what it tries to do
What It TRIES To Do…
  • It tries to ease the process of building a system
  • It tries to help reduce failures like unclear objectives, cost overruns, etc.
  • It tries to reduce the possibility of a system not meeting user needs
phase 1 planning
Phase 1: Planning
  • Initial phase of any SDLC
  • We initially would receive a request from the user for systems development
  • We do NOT just go and build it!!!
planning stages
Planning Stages:
  • Identify the problem to be solved by investigating the issue
  • Establish a team
  • Develop appropriate documentation
    • Project Charter (scope, objectives, participants)
    • Business Case
    • Project Feasibility (legally, technically, economically)
key deliverables
Key Deliverables
  • General Problem Statement
  • Team members and roles
  • Feasibility Report
phase 2 analysis
Phase 2: Analysis
  • Analysis: System requirements are studied and structured
  • This is achieved by asking questions such as:
    • Why do problems exist?
    • Why were certain methods of work adopted?
    • Are there alternative methods?
analysis stages
Analysis Stages:
  • Study and analyse the current system
    • System analysts collect facts from existing users
    • Existing systems limitations and details
    • Define new system objectives
slide24

Define and Prioritise Users Requirements

    • The analyst approaches the users to find out what they want from the system
    • They use different data gathering techniques such as interviews, observations, and surveys
    • This is an attempt to understand all aspects of the current system and eventually indicate how things may be improved by a new system
key deliverables1
Key Deliverables
  • Formal requirements document (business requirements statement)
  • Data Flow Diagram (DFD) and Entity Relationship Diagram (ERD) of current system
phase 3 design
Phase 3: Design
  • System Design: Describes how the system will fulfill the user requirements
  • To achieve this, we must create both a logical design and physical design
  • Coding does not occur here!!!
design stages
Design Stages:
  • Choosing an appropriate Database Management System (DBMS)
  • Establishing system security standards
  • Interface Design
slide28

Data Capture Requirements

  • Standards for printed report production
  • System navigation methods
slide29

What are possible solutions?

Horizontal market software— meets needs of many companies

Buypackaged software - prewritten software available for purchase

Vertical market software — designed for particular industry

Write own customsoftware – softwaredeveloped at user’s request

Outsource – have outside source develop the software

key deliverables2
Key Deliverables
  • Functional Specification Document
    • data, processes, inputs, outputs, etc.
  • Technical Specification Document
    • programs, files, network, etc.
  • Implementation Schedule
phase 4 implementation
Phase 4: Implementation
  • We now need to convert our physical system specifications into a working and reliable solution
  • This is where we develop our system
  • This is followed by testing and then implementation
implementation stages
Implementation Stages:
  • Coding
    • the physical design specifications are turned into working computer code
  • Integration and Testing
    • We create a testing environment where all our components are brought together
  • Installation
    • The new system is rolled out
key deliverables3
Key Deliverables
  • Fully Installed system
  • Fully trained users
  • User and Operational Documentation
phase 5 maintenance
Phase 5: Maintenance
  • Occurs once the system is operational
  • Monitor system performance, and rectify bugs
  • Make requested changes
key deliverables4
Key Deliverables
  • Keep system live
  • Maintain code
  • Update software when required
overview of sdlc
Overview of SDLC

Establishes a high-level view of the intended project and determines its goals.

  • Software Changes are made here!

Analyses end-user information needs in terms of what the IS should do.

Describes desired features and operations in detail - how the parts of an information system should be implemented

  • Convert final physical system specifications into working and reliable software
questions1
Questions
  • Q1: What is meant by SDLC?
  • Q2: What stage of the SDLC are requirements gathered and structured?
  • Q3: At what stage does coding take place?
thanks
Thanks
  • Any questions?