UNIT 5- SYSTEMS DEVELOPMENT

E-TUTOR PRESENTATION
 UNIT OBJECTIVES
By the end of this Unit you will be able to:
1. Examine approaches to building information systems
2. Explore business roles in a software development or selection or replacement
project
3. Examine the concept of business process reengineering
KEY POINTS TO NOTE

 Information systems have an effect on the way that

organization operates
 In order to accommodate the introduction of
information systems in an organization there may
be need to change or redesign the structure, scope,
workflow and business processes of an organization
KEY POINTS TO NOTE

 There are many factors which an

organization need to consider when
considering implementing information
systems such as internal resources ,
cost/budget, impact on work processes
KEY POINTS TO NOTE

 The inclusion of an information system in any

Organization must be planned to identify the
direction of the development of the proposed
system, its rationale, the current situation,
the management strategy , the
implementation plan, and of course, the
budget allocated to such as system
KEY POINTS TO NOTE

 Systems development is the entire set of

activities needed to construct an
information systems solution to a business
problem or opportunity.
 Here, we are not distinguishing between
creating the system yourself or buying
someone else’s solutions, because, for
complex systems, the same level of rigor and
analysis is required for both.
KEY POINTS TO NOTE

Note that system development steps are often preceded by some sort
of business planning or a desire to change the way in which an
organization function whether it be to improve productivity and
efficiency etc.

 Enterprise analysis, also known as business systems planning, looks at the entire
business in terms of the individual units within the business. For example, the
functions, processes, data elements and even the departments are scrutinized to
identify the Organisation’s data (entities and attributes)

 Strategic Analysis with Critical Success Factors (CSFs) looks at the external
environment to identify threats and opportunities. Two techniques PESTLE Analysis
and Porter’s Five Forces Analysis are used to examine the business environment.
The company then develops a list of Critical Success Factors. Critical Success
factors (CSFs) are a few key factors that organisations should focus on to be
successful.
KEY POINTS TO NOTE

 If done correctly, the organizational level strategic plan

will be used to guide and align an overall IS plan, which
will ultimately result in planned IS development projects.
 Note the objectives of the IS plan as listed on page 4 in
the unit
 It must be aligned with the organization’s strategic plan.
 It must provide for an IT architecture that enables users,
applications, and databases to be seamlessly networked and
integrated.
 It must efficiently allocate IS development resources among
competing projects, so the projects can be completed on time,
within budget, and have the required functionality
KEY POINTS TO NOTE

 Please refer to the Case Study on Page 5

 Note the topic of Systems Development and
Organizational Change: The four types of
change, arranged in order of both risk and return
on investment are; Automation, Rationalization,
Reengineering, and Paradigm Shifts.
 Note the definitions in the unit reading
KEY POINTS TO NOTE
 Automation – this is the method of speeding up the
performance of tasks by computerizing or
mechanizing existing procedures.
 Rationalization of procedures – the streamlining of
standard operating procedures including cutbacks,
consolidations, changes in organizational structure
etc.
 Business process reengineering – analysis and
redesign of business processes to reorganize
workflows and reduce waste and repetitive tasks
 Paradigm shift – radical reconceptualization of the
nature of the business and the nature of the
Organization.
The first two forms of Organizational change above
(automation and rationalization) are easier to do,
offering modest rewards at relatively low risk. In
contrast, reengineering and paradigm shift, are more
difficult to do. They offer higher rewards but are
more prone to failure. See more details in your
readings
KEY POINTS TO NOTE

 One of the options that an organization can consider for

implementing an IS is that of developing a system to
meet their specific needs. There are many approaches to
systems development, one of them being the traditional
or what is referred to as the “Waterfall” method.
 Please note the Systems Development Life Cycle (SDLC)
as expressed in the unit reading. The SDLC provides a
structured and standardized process for all phases of any
system development effort. These phases track the
development of a system through several development
stages as determined by the 7 steps listed in the unit.
KEY POINTS TO NOTE
KEY POINTS TO NOTE

Testing is the process that validates if the system is

preforming as designed and as required. There are three (3)
levels of testing.
 Unit testing which checks for programming bugs and logic
errors;
 Systems integration testing (SIT) to make sure the modules
are working together and that the system is doing what it
says it will do;
 User Acceptance Testing (UAT), business process by
business process testing – not only must the system do what it says it
will do, but more importantly, what it does MUST give you your desired result.
KEY POINTS TO NOTE

 There are alternate methods to the SDLC that an

organization can consider as well.
 Why consider alternatives? Simply because the
SDLC:
 Formal, detailed, therefore cumbersome
 “Freeze” users’ requirements
 Users not part of development
 Often leads to overruns
 Fixed rules for techies and non-techies
 KEY POINTS TO NOTE

Some of the alternate strategies include:

 Prototyping ..fast, easy, user-centered
 Joint Application Design/Development (JAD)…involves users at
an intense level.
 Packaged Software..fast, easy, comvenient and user-driven.
 Object Oriented Systems Development…data and processes
are combined to form objects.
 Rapid Application Development (RAD)….the use of CASE Tools
and $G tools with prototyping.
 KEY POINTS TO NOTE

 Prototyping –
 Developing an experimental system rapidly and inexpensively for
end users to evaluate
 Used as a template to develop final system
 An iterative process of trial-and-revision
 Useful when there is some uncertainty about requirements or
design solutions
 Encourages end-user involvement and is more likely to fulfill end-
user requirements
 KEY POINTS TO NOTE

 End User development

 The development of information systems by end users with little or
no formal assistance from technical specialists
 Enabled by the use of fourth-generation languages
 Software tools that allow end users to create reports or develop software
applications with minimal or no technical assistance

 Allow rapid development but testing and documentation

may be inadequate
 KEY POINTS TO NOTE

Joint Application Development (JAD)

 Similar to interviews and questionnaires.
 A structured series of meetings of users, analysts, technical
personnel, sponsors

Why the need for JAD?

 For developing a common understanding
 People involved in a JAD session.
 Brings end users and Systems Analysts together in interactive sessions
to discuss the system design.
 KEY POINTS TO NOTE

Packaged Software
 Software designed and built by Software companies for
general use.
 Cheaper alternative to Custom systems.
 KEY POINTS TO NOTE

The Limitations to be considered are:

 Integration with existing applications.

 How customizable is the software package?
 Customization vs business process re-engineering and the effect
on the organization's culture.
 How easy is the package for users to learn?
 System documentation and training manuals provided.
 Updates and enhancements provided on websites
 KEY POINTS TO NOTE

RAD – Rapid Application Development

 Uses JAD and Prototyping to define requirements and
radically decrease the time needed to design and
implement information systems.
– Key point: delay producing system design until after user
requirements are clear
 KEY POINTS TO NOTE

Now remember an information system consists of five

components: hardware, software, data, procedures and
people

 As it relates to conversion to a new system, we

must remember that all five IT components must be
considered in any conversion. Conversion of any element
may impact elements to either side
 KEY POINTS TO NOTE

 Direct conversion – is the riskiest method. an entire

organization stops using the old system at one time and
begins using the new one immediately thereafter.
 Pilot conversion: Part of an organization uses the new
system while the rest of it continues to use the old. This
localizes problems to the pilot group so support resources
can focus on it. Possible to have interface issues within
systems
 KEY POINTS TO NOTE

 Phased (Modular) conversion: Part of the new system is

introduced while the rest of the old one remains in use.
Possible to have interface issues within modules
 Parallel Conversion: The new system is introduced while
the old one is still in use. Both systems process all activity
and the results are compared. Once there is confidence
that the new one operates properly, the old one is shut
down.
CONVERSION METHODS
 KEY POINTS TO NOTE

 Note the Team roles in MIS Projects on page 14.

 Refer to the Learning Activity 5.2 for additional reading
 Note the ways that an organization can change
structurally. Note especially the process of Business
Process Reengineering. Please research on the
internet, an example of a business that undertook
BPR and what the result was.
 KEY POINTS TO NOTE

 Why do Information Systems Project Fail???

- Note Table 5.2 on page 20
COMMON SYSTEM FAILURES
Kindly turn your attention to the discussion forum
to participate in this week’s discussion!
Post all questions in the Students Question Forum
for Unit 5

THANK YOU!!!