Introduction to Systems

Analysis and design

Systems Analysis and design - We e k 0 1
Aim…

• Define a system
• Types of systems & their characteristics
• Systems Development Stages
• Who are the Actors
What is a System?
A group of interrelated elements
organised as an identifiable whole so as
to function together to achieve a
desired result.

Characteristics of a System
• Interrelated Components
• has a purpose
• Has a boundary
• Exists with in an environment
• Has interfaces
• Exists within constraints
• Has inputs and outputs
Types of Systems
• Natural
• Physical
• Living
• Man-made
• Computer systems

• Common behaviors?
Computer Systems
Man-made automated systems

Common Characteristics
• Require hardware
• Involve software
• Enforce business rules
• Process data into information
• Human interaction?
Computer Systems
Man-made automated systems

System Characteristics
• Specialized vs General
• Systems & Sub-systems
• Resource requirement
• Tend to grow
What is information system?

What?
An information system is a collection of software,
hardware, procedures, data and computer networks
used by people in organizations.

Why?
An information system is used to collect, store,
manage and distribute data to support specific
activities.
What is Systems
Development?
A process of …
planning, analysing, designing,
implementing, testing and deploying
an information system.

7 phases of system development

• Investigation
• Analysis
• Design
• Implementation
• Testing
• Deployment
• Maintenance and review
Actors in systems development

• Users
Who are the actors • Managers
Business Analyst
in systems •
• Systems Analysts
development? • Technical Architects
• System Designers
• Developers
• Testers & QA
people
• Others
Users
• Direct interaction with the system
• May be product owners
• Inputs to requirements
• Usually more than one
• Differing skills
Project Managers
• Higher level requirements
• Resources
• Schedule
Business Analysts (BA)
• Identify and evaluate options for improving business
systems
• High level feasibility study
• Define business requirements
• Produce reports on analysis
• Involvement is sooner at & higher level than the SA.
• On changes to the People, Organisation, Processes and
the Technology
System Analysts (SA)
• Understand the role of the software in the processes
• Investigate the current system(s)
• Document ‘as is’ system using standard models
• Define new system requirements
• Requirements analysis
• Involvement is at a lower level than the BA

• Output: Requirements Spec

System Analysts (SA)
SA’s other roles
• Design and Document
• Design systems to meet requirements
• Implementation
• Documentation
• Training
• Testing,
• Handover
• Review
• Review of live system
• Review of development method
• Lessons learnt
• What next
SA’s Skills and Qualities

• Effective written and verbal communicator

• Able to use an appropriate range of analysis and modelling
techniques
• Able to use appropriate tools
• Methodical
• Take personal responsibility for quality
Technical Architects/Designers
• Designing the solution’s technical architecture
• Defines overall structure of the technical solution so that
non-functional requirements will be met, including:
• Performance
• Operating system / network / database
Developers
• Understand the specification
• Design the components
• Design the testing
• Write the code
• Test the component
Testers and QA
• Planning
• Specifying
• Executing
• Recording
• Checking
Others?
• Operations personnel
• IT admin, network, security, data
• 3rd-party suppliers
• Auditors
• etc
 How roles may be structured
• A typical traditional
structure might be:
• Project manager (PM)
• Business analyst (BA)
• Systems analyst (SA)
• Designers/Developers
• Supporting roles, e.g.
• Testers
• DBA
• Technical architect
Systems
Development
Stages

1. Initiation
2. Feasibility study
3. Requirements
analysis
4. Design
5. Implementation
6. Testing
7. Deployment &
Evaluation
8. Maintenance
Systems development stages
Define the project
scope.

Deliverables? Initiation
• Scope definition/vision
document
• Project plan

Stakeholders?
• Product owners
• Managers
• BAs/SAs
Systems development stages
Is the project
viable?

Feasibility study
Deliverables?
• Feasibility study report. • Technical
• Economic
• Schedule
• Operational
• Legal
Stakeholders? • social
• System analysts
• Product owners
• Managers
Systems development stages
What are we
building?

Deliverables? Requirements
• Requirements Analysis
specification

Stakeholders?
• System analysts, BA
• Managers
• users
Systems development stages

Design solution

Deliverables? Design
• System architecture
• Detained design

Stakeholders?
• Technical architects
• Designers
• System analysts
• Developers
Systems development stages
System
construction

Deliverables?
• Software code Implementation
• Hardware
• Documentation

Stakeholders?
• Developers
• Designers
• System analysts
Systems development stages
Correctness,
Completeness,
Quality

Deliverables?
• Test plan Testing
• Test data
• Test results
• V&V documents

Stakeholders?
• Testers/QA
• Developers
• Designers
• System analysts
Systems development stages

System Release

Deliverables?
• Application Deployment &
• Deployment
instructions
Evaluation

Stakeholders?
• Developers
• System analysts
• Project managers
• Users
Systems development stages

System Release

Deliverables?
• Updated
software/hardware Support &
• Documentation Maintenance

Stakeholders?
• Users
• Project managers
• Developers
• System analysts
 What we covered …

• Defined Systems

• Types and characteristics of systems

• Overview of Systems development

stages

• Actors and their roles in Systems

development
What we covered …

• Systems development stages

• Activities
• Who is involved
• Key deliverables
Questions?
Remember to complete all the seminar activities