Professional Documents
Culture Documents
Sad Notes
Sad Notes
DESIGN
WILLLIAM MUNYIRI
Lesson 1
Systems Theory
Objectives
System concept and the Organization
System Theory/Concept
Types of Systems
System Components
Characteristics of Systems
Data and Information
SYSTEM THEORY / CONCEPT
components
Objectives of an org. have higher priority than objectives of its sub-
systems
TYPES OF SYSTEMS
Inputs –elements that enter the system e.g. data entered into
comp. raw materials to a plant,
Processes – operations necessary to convert / transform inputs to
outputs. Computer processing involves activating commands,
execution, computations and storage
Control – elements that guide the system in decision making by
monitoring pattern of activities that govern input, processing
and output e.g. OS, management etc
Outputs – Describes finished products / services as consequences
of inputs being in the system
SYSTEM COMPONENTS
installation
Feeling of intimidation by users who have limited training in
Computer skills.
Discussion Exercise:
List other potentially negative impacts of automating operations.
For each of the above give ways on how the negative impacts can be
minimized.
End Lesson 1
Lesson 2
INFORMATION SYSTEM
Objectives
Categories of IS
IS Stakeholders
Database Systems Approach
Systems Organizational levels
Definitions
System Builders - construct, test and deliver the new system into
the operation.
Vendors / Consultants – sell system hardware, software and
services to business for incorporation into their information
systems.
System Analyst - facilitator to the development of IS and
computer applications by bridging the communication gap that
exits between non technical system owners and users as well as
the technical system designers and builders.
DATABASE SYSTEMS APPROACH
Database Administrator.
Centralization enables DBA to be impartial toward individual
departments needs and to make decisions that are to the best of the
interest of the organization.
Adaptability - Database approach is adaptable to change.
that emerge.
New requests are easily assimilated into the existing database as
data about one record may bear inconsistent values, thus leading to
inaccurate reporting.
Incapable of ad hoc reporting - Since the files are not related easily
users
DATABASE SYSTEMS APPROACH
STRATEGIC LEVEL
The characteristics of the information at the strategic level is as
follows
Unstructured - concerned with long term goals of an
MANAGERIAL LEVEL
The characteristics of the information at the strategic level is as
follows
Semi-structured - concerned with medium range goals of an
organization
Source – usually of medium quality and obtained from restricted
range of sources
Largely quantitative – based on routine operations and non
OPERATIONAL LEVEL
The characteristics of the information at the strategic level is as
follows
Structured – decisions associated with activities that are routine
data, highly detailed and help in the daily routines and procedures
End Lesson 2
Lesson 3
SYSTEM ANALYSIS
Objectives
Context of System Analysis
Information System Analyst
System Requirements
System Analyst
System Investigation and Analysis
System design techniques
SYSTEM ANALYSIS
Flow of useful, accurate and timely info back to the Business and its
people
SYSTEM ANALYSIS
of complaints
Directives - priorities to change a situation regardless of any / no
experienced users.
Heavy user involvement and motivation is difficult
scenario.
Feasible - narrowing to the realizable requirements
backward
Verifiable - formatting into formal styles
SYSTEM ANALYST
The interpersonal skills deal with the user training and selling the
user the benefits and potentials of the candidate system.
During system analysis there is a greater need for interpersonal
skills since it concerns analyst working with the user to determine
requirements and translate them into design criteria.
The analyst has to capture the inner working of a business and
have competence in system tools and methodologies
SYSTEM ANALYST
of the system where their thinking and ideas are revealed in the
achieved goals and objectives
In conclusion, an analyst has to be orderly, pay attention to details
design tools since each project has a different intelligence that needs
to be tackled differently
Currency - keeping track of the latest HW and SW for appropriate
recommendations
Modification – adjusting to suit changes to the requirements after a
return on investment
SYSTEM INVESTIGATION AND ANALYSIS
SYSTEM INVESTIGATION
The initial investigation has the objective of determining the
DATA ANALYSIS
This approach involves getting information from the existing
PROTOTYPING
Prototyping is an approach of building a model to represent the new
requirements determination
DETERMINING INFORMATION REQUIREMENTS
reference, reasons for the study, current situation and its overview,
identified problems and requirements, proposed situation (with
technical, operational and cost implications), cost – benefit analysis
and its recommendations
FEASIBILITY STUDY
Is a fact –finding process to show or reveal the viability and the
ability to successfully complete a proposed system project
Economic feasibility – concerns the financial assessment of
the market for the technical expertise needed to develop, operate and
maintain the system
Operational feasibility – assessing whether the system will meet the
Objectives
System Development Life Cycle
Feasibility Techniques
Fact – Finding Techniques
Analysis and Design Tools
SDLC:
A system development process is a set of activities, methods, best
practices, deliverables and automated tools that stakeholders use
to develop and maintain IS and SW
A system development methodology is a very formal and precise
system development process that system developers and project
managers are to use to develop and maintain IS and SW
A system life cycle divides the life of an IS into stages:-
System development using development methodology
System operation, support and maintenance using IT
SDLC:
study
Do not be afraid to cancel or revise the scope
feasibility study
User changing requirements / objectives that can not be met by the
existing design
Benefits realized from the proposed system do not justify
commitment to implementation
IMPORTANCE OF PROJECT SCHEDULING
The project manager musts know the duration of each activity, the
order in which the activities must be performed, the start and end
times for each activity, and who will be assigned each specific
task.
The scheduling allows for a balanced activity time estimate,
sequences and personnel assignments to achieve a workable
schedule, which is essential for project success
The schedule provides:
Effective use of estimating processes
Successful Project:
Within the allocated time
Within the budgeted cost
At the proper performance or specification level
With acceptance by the customer/user
With minimum or mutually agreed upon scope changes
Without disturbing the main work flow of the organization
Without changing the corporate culture
Within required quality and standards thus use the customer’s
name as a reference
POTENTIAL BENEFITS OF PROJECT
MANAGEMENT
Identification of functional responsibilities to ensure that all
activities are accounted for regardless of personnel turnover
Minimizing the need for continuous reporting
Identification of time limits for scheduling
Measurement of accomplishment against plans
Early identification of problems so that corrective action may
follow
Improved estimating capability for future planning
Knowing when objectives cannot be met or will be exceeded
ESTABLISHING SYSTEM REQUIREMENTS
the origin
ESTABLISHING SYSTEM REQUIREMENTS
Logical design - lays out the components of the system and their
relationship to each other, as they would appear to user.
Show what the user would do not how
and controls
Testing tools
SYSTEM PROGRAMMING
failures.
End Lesson 4
Lesson 5
SYSTEM ANALYSIS METHODOLOGY
Objectives
System Models
System Tools
CASE
GANT
PERT
SYSTEM ANALYSIS METHODOLOGY
to accomplish tasks.
Thus techniques are the procedure that apply tools in carrying out a
SYSTEM TOOLS
The analyst begins by creating a model / representation of reality
Flow system Tools – this shows the flow of materials, energy and
information that hold the system together.
In it there is orderly flow of the logic, manipulation of specific
values to determine the critical path, interpret the relationships
and relay them back as a control
Project Evaluation and Review Technique (PERT) models show
the schedule for the completion time in relation to resources and
the performance specifications
SYSTEM ANALYSIS METHODOLOGY
Provide everyone on the project team with easy access to the latest
Disadvantages
CASE products can be expensive
environment
There is usually a long time for learning before the tools can be
GANTT CHARTS
A Gantt chart is a horizontal bar chart that illustrates a project task
against a calendar.
The horizontal position of the bar shows the start and end of the
horizontal axis
A vertical line indicates a current or reporting date
SYSTEM ANALYSIS METHODOLOGY
GANTT CHARTS
To reduce complexity a Gantt chart for a large project can have a
GANTT CHARTS
Popular due to its simplicity – it is easy to read, learn, prepare and
use
More effective than PERT/CPM charts when one is seeking to
communicate schedules
They do not show activity dependencies.
One cannot determine from the Gantt chart the impact on the entire
PERT/CPM
Program Evaluation and Review Technique (PERT), (Also Critical
It forms the basis for planning and provides management with the
PERT/CPM
Helps management handle the uncertainties involved in programs
well organized diagram from which both the contractor and the
customer can make joint decisions
SYSTEM ANALYSIS METHODOLOGY
PERT/CPM
Allows one to evaluate the effect of changes in the program
More effective than Gantt charts when you want to study the
NOTE:
Gantt Charts and PERT/CPM are not mutually exclusive techniques
resources
SYSTEM ANALYSIS METHODOLOGY
NETWORK ANALYSIS
Network analysis is a generic name for a family of related
restrictions exist.
The critical path method is applied most where a network is drawn
NETWORK ANALYSIS
In the network analysis a project is broken down into consistent
estimate the time and cost, locate the critical path, schedule the
project, monitor and control the progress of the project and revise the
plan.
SYSTEM ANALYSIS METHODOLOGY
Example: draw a network and find the critical path for the
following project
SYSTEM ANALYSIS METHODOLOGY
diagram shows how the different tasks and activities relate together
making it easier to understand a project intuitively, improving
planning and enhancing communication details of the project plan to
the interested parties
More effective planning – CPM forces the management to think
the project through for it requires careful detailed planning and high
discipline that justifies its use
Better focusing on the problem areas – the technique enables the
Objectives
Types of models
Benefits of System models
System Development Process
System Development Models
SDLC
Waterfall
Prototyping
Spiral Development Models
SYSTEM DEVELOPMENT MODELS
TYPES OF MODELS
Logical models - Also known as essential conceptual or business
models
Show what a system is / does disregarding its technical
implementation
Physical models - Also known as implementation \technical
models
Show what the system is / does and its technical implementation
language
SYSTEM DEVELOPMENT MODELS
that of errors
Can model large and extremely complex systems with possibly
infinite solutions
SYSTEM DEVELOPMENT MODELS
Waterfall model
Prototyping
Iterative Development
WATERFALL MODEL
The waterfall model (sometimes called the classic life cycle or the
systems projects.
The main reasons for the failures appeared to be a lack of formality
WATERFALL MODEL
The development process was not allowed to move onto the next
system.
SYSTEM DEVELOPMENT MODELS
WATERFALL MODEL
Volumes of new documents must be generated and steps repeated
.
SYSTEM DEVELOPMENT MODELS
WATERFALL MODEL
Real projects rarely follow the sequential model that the model
proposes.
The customer must be patient as a working version will only be
available late in the project time span and does not accommodate
customer uncertainty.
The model is only appropriate when the requirements are well-
understood
SYSTEM DEVELOPMENT MODELS
problems
Identify constraints on time and project resources
overly specific
Define detailed requirements necessary to assist in the
application specific
Decomposes main task into sub-tasks with available tools
Reuse the existing code whenever possible to save time and effort
SYSTEM DEVELOPMENT MODELS
changing specifications
The rigid sequential flow of the model is rarely encountered in real
address with a system, but they do not know all the nuances of the
data.
Nor do they know the details of the system features and capabilities.
Design
Prototype Creation/Modification
Assessment
Prototype Refinement
System Implementation
SYSTEM DEVELOPMENT MODELS
BENEFITS OF PROTOTYPING
Shorter development time by accelerating some phases
better solutions
SYSTEM DEVELOPMENT MODELS
BENEFITS OF PROTOTYPING
Facilitates rapid development of the system
User gets hands –on experience of the system before it becomes fixed
frustrations
SYSTEM DEVELOPMENT MODELS
control of progress
Maintenance is more costly and difficult
SYSTEM DEVELOPMENT MODELS
class of problems.
In general, a prototype is valuable when heavy human-machine
increments
Further planning based on the user comments; hence
Waterfall Model
Objectives are determined, obstacles are identified and alternative
to analyze the results of the version created in the Engineering step and
to offer feedback to the developer.
SYSTEM DEVELOPMENT MODELS
Objectives
Structured Methods Features
Structured Analysis
Structured Analysis Approaches
Tools for Structured Analysis
STRUCTURED APPROACHES TO SYSTEMS
DEVELOPMENT
Originated from the observation that most Information Systems
development had gone wrong or had failed to meet the
requirements, goals or objectives, the condition coming from poor
system analysis
There arose the need for the new methods of analysis and design
that would offer
Greater formality of approach to bring system development to a
compact well functioning entity for example:
STRUCTURED APPROACHES TO SYSTEMS
DEVELOPMENT
More flexible design of the system
Less scope for un ambiguity and understanding
Specifications and finally into technical specifications
Much more user involvement at all the stages off development
Greater focus on identifying and satisfying business needs
Ability to trace requirements through the initial analysis into the
business level
Clarity of the stated requirements by the use of text and the
graphical representation
STRUCTURED APPROACHES TO SYSTEMS
DEVELOPMENT
FEATURES OF STRUCTURED METHODS
Focus on the data structure
modify or complete
STRUCTURED APPROACHES TO SYSTEMS
DEVELOPMENT
FEATURES OF STRUCTURED METHODS
STRUCTURED ANALYSIS
Structured analysis is a set of techniques and graphical tools that
Project management
Personnel consideration
STRUCTURED APPROACHES TO SYSTEMS
DEVELOPMENT
Structured analysis considers new goals and tools for analysis
where the goals specify
Use of the graphics for the better communication with the user
characteristics
STRUCTURED APPROACHES TO SYSTEMS
DEVELOPMENT
Structured analysis is basically a four-stage process carried out
during system analysis; and the phases include
1. Understand the current physical system
Through fact-finding activities and recording of information about how the
current system operates.
Need to construct a data flow model, processing sequence and
documentation requirements as described by the users of the system
STRUCTURED APPROACHES TO SYSTEMS
DEVELOPMENT
Structured analysis is basically a four-stage process carried out
during system analysis; and the phases include
2. Describe the current logical system
Show the logical functions carried out by the system without considering
how the current system is physically implemented i.e. state exactly what the
system is doing rather than how it is doing it
and highly readable manner showing the workings of the system, save
its implementation
Thoroughness – calls for a rigorous study of the user for commitment
down to the lowest level of details and describes what data flow
(logical model) rather than how data is processed (physical model)
i.e. independent of the hardware, software, data structures or file
organizations
DATA FLOW DIAGRAM (DFD)
STRUCTURED APPROACHES TO SYSTEMS
DEVELOPMENT
EXAMPLE OF DATA FLOW DIAGRAM (DFD)
STRUCTURED APPROACHES TO SYSTEMS
DEVELOPMENT
ADVANTAGES OF DD
Documentation – serves as a valuable reference in any organization
element
Standardizing - an important feature necessary in building a
database
Helps simplify structure for meeting data requirements of a system
End Lesson 7
Lesson 8
SYSTEM DOCUMENTATION
Objectives
Documents Produced
Quality Control SWT
Choosing SW and HW
SYSTEM DOCUMENTATION
SOFTWARE DOCUMENTATION
The typical items included in the software documentation are:
Introduction – shows the organization’s principles, abstracts for
be performed
SYSTEM DOCUMENTATION
SOFTWARE DOCUMENTATION
The typical items included in the software documentation are:
Accuracy constraints – how close output values must be ideal to
everything
Fundamental assumptions – the characteristics of the program
that will stay the same, no matter what changes are made
Software Code – this refers to the code written for the information
system
SYSTEM DOCUMENTATION
SOFTWARE DOCUMENTATION
The typical items included in the software documentation are:
Test Report – this should contain test details e.g. sample test data
technical terms
SYSTEM DOCUMENTATION
ROLES IN A WALKTHROUGH
Presenter – is a person who has done all the work and presents the
raised and then reading them back at the end of the meeting so that
priorities can be assigned and the follow-up action agreed
Reviewer – is the person from the same project as the presenter
SYSTEM DOCUMENTATION
STAGES OF SWT
Preparation – presenter prepares documentation on the product to be
defects
Author being defensive about his work
inconsequential parts
Tendency to fix blame on others attempting to discredit their work
SYSTEM DOCUMENTATION
the meeting
Avail a checklist of specific topics for review to keep the team on
track
SYSTEM DOCUMENTATION
earlier applications
Available – software products can be obtained sooner from the market
Shorter time - user personnel can bring up the new system in less time
Easily applied - users can try out the product without investing a great
deal of money
SYSTEM DOCUMENTATION
Disadvantages
Rarely meets user needs – users may have to adapt their procedures to
the requirements
Incompatible – product may not be compatible with the existing
software applications
User interface – different user interface may make it difficult for the
Objectives
Implementation Strategies
System Evaluation
SYSTEM IMPLEMENTATION
IMPLEMTATION STRATEGIES
Also known as the system conversion or changeover methods; that
concerns the transformation from the old to new system with
minimum visible differences between the two systems
1. Direct changeover
The old system is stopped and the new system replaces it
IMPLEMTATION STRATEGIES
2. Phased conversion
If the new system has several components, they can be introduced
one at a time
The staff can become accustomed to one change before facing the
IMPLEMTATION STRATEGIES
3. Pilot Conversion
If the organization has several branches or departments where the
IMPLEMTATION STRATEGIES
4. Parallel conversion
Involves keeping the old system running while the new system is
SYSTEM EVALUATION
Evaluation of the systems to produce information about the system
SYSTEM EVALUATION
system
To clarify and set priorities for the needed modification
To transfer the responsibility for the system from the development
Areas to be evaluated
Accuracy of the information
Timelines and currency of the information
User satisfaction
Attitudes towards the system
Internal controls of the system
Project schedule compliance
The quality of the programs
The net operating costs
Savings of the system
Systems impact on the user and their jobs
Quality and completeness of the system documentation
SYSTEM IMPLEMENTATION
BENEFITS OF EVALUATION
Improvement of the systems development practice decisions to
system development
Improvement in the effectiveness and the productivity of the
design
Realization of the cost savings by modifying the system