Fundamentals of
System Analysis and Design
(INSY2051)
Instructor: Wondwossen Mulugeta (PhD)
e-mail: wondemule@yahoo.com
Office: Eshetu Chole Building, Office No. : 114
Course Objectives:
Describe concepts underlying system development using
structured approach
Understand the system development process of structured
approach,
Clearly define problems, opportunities, or mandates that
initiate projects.
Demonstrate the use of various Systems Design techniques.
Demonstrate the study, model and design of new systems
Understand the types of business needs that can be addressed
using information technology-based solutions.
Manage information systems projects
2
Course Content
Chapter
1) Basic Concepts in
Information System
development:
2) System
Development:
Problem
Identification,
Selection and
Planning Phase
Topics
1.1.Definitions, system thinking
1.2.types and characteristics of information systems
1.3.participant in information system development
1.4.the modern system analyst
1.5.the multiple roles of the analyst
1.6.information systems building blocks
1.7.qualities of system development
1.8.system development methodologies,
processes/phase
2.1.Problem identification
2.2.problem definition: symptoms vs problems
2.3.prioritizing problems
2.4.project initiation and planning
2.5.planning tools and techniques
2.6. Gantt& PERT
Weeks
1-4
5-6
Assessment 1
3
Course Content
Chapter
3) System
Development:
Analysis
Phase:
4) System
Development:
Design Phase:
Topics
3.1. Data collection
3.2. determining scope and measurable
objectives
3.3. defining business needs in systems terms
3.4. system requirement
determination/determination: sources, tools and
techniques
3.5. Process, logic, and data Modeling
4.1.Purpose and deliverables
4.2.logical and physical design
4.3.Databases design
4.4.Human interface design
4.5. Program design
Weeks
7-8
10-12
Assessment 2
4
Course Content
Chapter
5) Systems
Implementation
and
Maintenance
Phase:
6) Current Trends
in
System
Development
Final Assessment
Topics
5.1.System Support, maintenance,
enhancement, reengineering, and design
recovery System testing techniques;
5.2.Systems and user documentation;
5.3.user training guidelines;
5.4.Developing installation plans;
5.5.conversion techniques;:
5.6.Types and procedures of system
maintenance;
5.7. Post installation follow-up
Weeks
13-14
Current Trends in System Development
15
Project presentation and Final exam
16
5
Instructional Methods:
Lecture,
Assignments,
Discussions,
Practical Project.
Evaluations:
Assessment 1
Assessment 2
Project
Final
15% (End of Chapter 2)
15% (End of Chapter 4)
30%
40%
Text Book:
1. Hoofer, J. George, J., & Valacich, J.S.(2005).
Modern System Analysis and Design (6th
edition)
Recommended Text:
1. Bentley, L.D. and Whitten, J.L. (2002). Systems
Analysis and Design Methods, 7th Edition
Information Systems Analysis and
Design
A method used by companies to create and
maintain systems that perform basic business
functions more efficiently
Major goal: to improve organizational systems
by developing or acquiring software and training
employees in its use
Components of an INFORMATION System
Components of a CBIS
10
System
Systems range from very simple to very complex.
There are numerous types of systems. The human body is a good
example of a system.
There are
biological systems (the heart, etc.),
mechanical systems (thermostat, etc.),
human/mechanical systems (riding a bicycle, etc.), and
social systems (groups, supply and demand, organization etc.).
Any more?...........
11
System
System: Turns data into information and includes:
Hardware and system software
Documentation and training materials
Job roles associated with the system
Controls to prevent theft or fraud
The people who use the software to perform their jobs
System
A system is an interrelated set of business procedures used within
one business unit working together for a purpose
A system has nine characteristics
A system exists within an environment
A boundary separates a system from its environment
12
Characteristics of a System
13
System
What is a System?
How is a system characterized?
Why do we need a system?
14
Developing IS Solutions to Business Challenges
15
Analytical Skills for Systems
Analysis
Four Sets of Analytical Skills
Systems Thinking
Understanding everything as a system
Organizational Knowledge
Knowing the organization business or problem domain
Problem Identification
Capability to identify systems problem
Problem Analyzing and Solving
Capability to suggest a solution based on system
thinking and organizational understanding
16
Systems Thinking
System (recall)
A system is an interrelated set of business procedures
used within one business unit working together for a
purpose
A system has nine characteristics
A system exists within an environment
A boundary separates a system from its environment
17
Systems Thinking
Is a mind set or way of thinking to view the world
(every thing in the world) as a system.
It emphasizes on interaction that keeps the system alive.
Creates a framework for problem solving and
decision making.
Systems thinking is a discipline for seeing wholes, recognizing
patterns and interrelationships, and learning how to structure
those interrelationships in more effective and efficient ways.
P. Senge and C. Lannon-Kim
18
Characteristics of a System
1. Components: An irreducible part or aggregation of parts
that makes up a system. Can also be called a subsystem
2. Interrelationship: Dependence of one component
(subsystem) on the other to serve a purpose or solve a
problem
3. Boundary: The line that marks the inside and outside of a
system and that sets off the system from its environment. A
logical or physical demarcation that separates the system
from other systems.
4. Purpose: The function or overall goal of the system.
19
Characteristics of a System
5. Environment: Everything external to the system that
interacts with the system
6. Interfaces: Point of contact where a system meets its
environment or where subsystems meet each other
7. Input: Whatever a system takes from it environment in
order to fulfill its purpose.
8. Output: Whatever a system returns to its environment in
order to fulfill its purpose.
9. Constraints: A limit to what a system can accomplish
20
System Thinking
Every thing is a system..
Give examples
Characterize each using our earlier approach
Identification of a system leads to abstraction
From systems abstraction you can think about
essential characteristics of specific system
Abstraction allows analyst to gain insights into
specific system, to question assumptions, provide
documentation and manipulate the system without
disrupting the real situation
21
System
A System is an interrelated set of business
procedures used within one business unit working
together towards achieving some specific goals.
A System exists within an environment
A boundary
environment
separates
system
from
its
22
Problem Analyzing and Solving
Four Phases
Intelligence
All relevant information is collected and analyzed
Design
Alternative solutions are formulated with sufficient information
Choice
Best alternative solution is chosen from the options available in design
Implementation
The selected Solution is converted into a working system and put into
practice
23
Information Systems
An information system is a specific type of system
in general.
A system is a set of components (subsystems) that
operate together to achieve certain objectives.
The objectives of a system are realized in its outputs.
In particular, the objective of an information
system is to provide appropriate outputs to the members
of the organization
24
Why Information Systems
Why do we need a change in an organizations system of performing
things???
Improving productivity
Efficient utilization of resources
Stepping with the technology
Being competitive in the market
25
Information Systems
Thus an IS is a set of interrelated components that
collect, manipulate & disseminate data & information &
provide feedback to meet an objective.
Manual or computer based
Examples:
airline reservation systems;
course reservation systems,
HRMS,
Library Systems
Name more..
26
Information Systems
Are arrangement of people , data , process,
communication and IT that interacts
to support and improve day-to-day operations in business
support the problem solving and decision making needs
of a management and users
Can exist with or without computers
Transfer data in to useful information
27
Information Systems
Information systems use data stored in computer
databases to provide needed information.
A database is an organized collection of interrelated data
reflecting a major aspect of the organization activities.
Information systems capture data from the organization
(internal data) and its environment (external data). the
concept of Open System
They store the database items over an extensive period of
time.helps for knowledge acquisition
28
Information Systems
When specific information is needed, the appropriate data
items are manipulated as necessary, and the user receives
the resulting information.
Depending on the type of information system, the
information output may take the form a query response,
decision outcome, expert-system advice, transaction
document, or a report.
29
Information Systems
Formal
information
systems
rely
on
procedures
(established and accepted by organizational practice) for
collecting, storing, manipulating, and accessing data in
order to obtain information.
Formal systems do not have to be computerized, but
today they usually are.
So Information System is an enabler
30
Information Systems
Most of the data captured by information systems
relates to the operations of the organization itself,
serving to produce internal information.
But in an increasingly competitive marketplace, a firm
needs to access more and more external information.
Therefore, it is important to note that decision
makers need both the internal information about
their organization and the external information
about its environment.
openness and interfacing the environment
31
General Functions of an Information System
32
Input, Processing, Output,
Feedback
Input: activity of gathering and capturing raw data
Processing: converting or transforming data into useful
outputs
Output: production of useful information, usually in the
form of documents and reports
Feedback: output that is used to make changes to input or
processing activities
33
Types of Information Systems
Transaction Processing Systems (TPS)
Automate handling of data about business activities
(transactions)
Management Information Systems (MIS)
Converts raw data from transaction processing system
into meaningful form for managers
Decision Support Systems (DSS)
Designed to help decision makers
Provides interactive environment for decision making and
reasoning
34
Types of Information Systems
Expert Systems (ES)
Replicates decision making process by experts
Knowledge representation describes the way an expert
would approach the problem and suggest most applicable
solution to a problem like an expert do.
35
TPS DATA FOR MIS APPLICATIONS
TPS
Order Processing
MIS
SALES
DATA
System
ORDER FILE
Materials Resource
Planning System
PRODUCTION MASTER FILE
General Ledger
System
ACCOUNTING FILES
UNIT
PRODUCT
COST
MIS
REPORTS
PRODUCT
CHANGE
DATA
EXPENSE
DATA
MANAGERS
MIS FILES
36
Roles in Info System Development
Project Manager
System Analyst
System Designer
Application Programmer
End User
37
Home Take Exam
Write the responsibility of roles in
Information System Development
38
System Analyst
A systems analyst is an IT professional who
specializes
in
analyzing,
designing
and
implementing information systems. Systems
analysts assess the suitability of information
systems in terms of their intended outcomes and
liaise with end users, software vendors and
programmers in order to achieve these outcomes.
39
40
Roles of System Analyst
The role of an analyst is to help organizations understand the challenges
before them to make this transition and to ensure that the needs and
expectations of the client are represented correctly in the final solution.
The roles of a System Analyst include:
1. Analyzing and understanding the current state processes
to ensure that the context and implications of change are
understood by the clients and the project team.
2. Developing an understanding of how present and future
business needs will impact the solution
3. Identifying the sources of requirements and
understanding how roles help determine the relative
validity of requirements
41
Roles of System Analyst
4. Identifying the sources of requirements and
understanding how roles help determine the relative
validity of requirements Developing a Requirements
Management Plan and disseminating the Plan to all
stakeholders
5. Identifying and documenting all business, technical,
product and process requirements
6. Working with the client to prioritize and rationalize the
requirements
7. Helping to define acceptance criteria for completion of
the solution
42
Building Blocks of Information System
43
Perspectives or Stakeholders
System owners pay for the system to be built and maintained.
System users use the system to perform or support the work to be
completed.
System designers design the system to meet the users requirements.
System builders construct, test, and deliver the system into operation.
Systems analysts facilitate the development of information systems and
computer applications by bridging the communications gap that exists
between nontechnical system owners and users and technical system
designers and builders.
IT vendors and consultants sell hardware, software, and services to
businesses for incorporation into their information systems.
44
Focuses for Information
Systems
Datathe raw material used to create useful
information.
Processesthe activities (including management)
that carry out the mission of the business.
Interfaceshow the system interfaces with its
users and other information systems.
45
System Devt Life Cycle
The life of a software system can be represented as a series of cycle.
A cycle ends with the release of a version of the system to the customers.
SDLC in general consists of 5 basic phases
1.
2.
3.
4.
5.
System identification and planning
System Analysis (system, requirement)
System Design
System Construction
System deployment and maintenance
46
System Devt Life Cycle
System identification and planning
Determining the software system to be developed
and how to go about it
Including
Need assessment
initial investigation
Selection
Why this all?
to be sure of what to develop
47
System Devt Life Cycle
Analysis (system, requirement)
Collecting and Structuring the requirements
includes requirement
capturing/elicitation,
Modeling
Validation
Why do you think we need to do so?
48
System Devt Life Cycle
System design
Architecting the system with implementation oriented
details and specifications
Design level models
How to store the data
How to accept input or provide out put
How efficiently the process/the logic should be
represented
Etc..
49
System Devt Life Cycle
System construction/implementation
Providing working systems/software
includes
Coding (what does it mean?)
..the conversion/realization
System testing (types and reasons)
at various level with various techniques
Documentation
..the product and the process
50
System Devt Life Cycle
System deployment and maintenance
Installation
Changeover from the old system to the new
Putting in to work
51
System Devt Methodologies
There are various System Development Methods
Waterfall Model,
Iterative Model,
Unified Process,
Incremental Models
Evolutionary Process Models
Rational Unified Process
Other Specialized Process Models
Agile ( a philosophy or a process?)
Cleanroom
DSDM - Dynamic Systems Development Method
XP eXtreme Programming
52
The Waterfall Model
Requirements
Definition
System and
Software design
Programming
and Unit Testing
Integration and
System Testing
Operation and
Maintenance
53
Incremental Models
Incremental Model (delivers software in
small but usable pieces, each piece builds
on pieces already delivered)
Rapid Application and Development (RAD)
Model (makes heavy use of reusable software
components with an extremely short
development cycle)
54
Evolutionary Process Models
(Iterative Refinement)
Prototyping Model (good first step when customer
has a legitimate need, but is clueless about the
details, developer needs to resist pressure to
extend a rough prototype into a production
product)
Spiral Model (couples iterative nature of
prototyping with the controlled and systematic
aspects of the linear sequential model)
55
Iterative Refinement
Evaluation
Implementation
(prototype)
Requirements
Design
56
Iterative Refinement
Concurrent
Activities
Requirements
Outline
Description
Design
Implementation
Initial
Version
Intermediate
Versions
Final
Version
57
Rational Unified Process (Modern)
Use-case driven,
architecture centric, iterative, and
incremental software process
Attempts to draw on best features of traditional
software process models and implements many
features of agile software development
58
The Rational Unified Process
A modern process model derived from the work on the UML and
associated process.
Normally described from 3 perspectives
A dynamic perspective that shows phases of the model over time;
A static perspective that shows process activities that are enacted;
A practice perspective that suggests good practice to be used
during the process.
59
Rational Unified Process (RUP)
phase model
Phase iteration
Inception
Elaboration
Construction
Transition
Inception: Establish the business case for the system.
Elaboration: Develop an understanding of the problem
domain and the system architecture.
Construction: System design, programming and testing.
Transition: Deploy the system in its operating environment.
60
Phases
and Load
Distribution
The Unified
Process
Life Cycle Model
61
Agility in SW Development
Agility
An agile team is able to respond to changes during project
development
Agile development recognizes that project plans must be
flexible
Agility encourages team structures and attitudes that make
communication among developers and customers more facile
Agility eliminates the separation between customers and
developers
Agility emphasizes the importance of rapid delivery of
operational software and de-emphasizes importance of
intermediate work products
62
Other parts of the life cycle
Other aspects of developing software
Feasibility analysis
Is it technically possible to build the system?
Does the company have the ability to build it
People
Skills
Finance
Time
technology
Project scoping - putting limits on how much you will develop
63
Other aspects of developing software
Project management
Estimating development time
Ensuring people are used effectively
Ensuring good communication and a healthy work
environment
Managing budgets
Training and handover
Maintenance
64
Cont
Another Example:
In a structured approach
Requirement collection/determination
SRS (system requirement specification)
Requirement Analysis (structuring)
Process, logic and data models
System design
Interface, data base and architectural
Implementation and testing
Deployment and maintenance
65
Cont
SRS
Functional requirement
None functional requirement
Pseudo requirement
Analysis Models
Process (function) models
DFD (data flow diagram)
Logic models
Structured English, decision table, decision tree
Data models
ERD (entity relationship diagram)- Conceptual
66
Cont
Design models
UI prototype
Database design
Logical and physical
Architectural design using SSC (system
structure chart)
67
Software Engineering Process
A process used to create a software system
Consists of:
Methods (steps)
A sequence of step-by-step approaches that help develop the information system
Techniques
Processes that the analyst follows to ensure thorough, complete and comprehensive analysis
and design
Tools
Computer programs and modeling tools that aid in applying techniques
68
End of Chapter One
69
