CREATING INFORMATION SYSTEMS
WEEK 4
INTRODUCTION
General managers don’t need to take part in hardware
decisions, but must take part in software design,
acquisition and implementation processes.
Developing organizational information systems is
complex and risky because it involves both technical and
social changes in the workplace.
WHY CREATE INFO MANAGEMENT SYSTEM?
Fulfill an organization's information processing needs
Optimize how firms capture, store and use data
HOW ARE THEY INTRODUCED?
1. Technology is developed – either purchased or created from scratch.
2. Information system is developed – integrate technology with all other
components of the organization to develop a working info management system.
** Must take into account how the tech will be employed, who will use it and for
what purpose
3 MAIN APPROACHES TO BUILDING INFO SYSTEMS
1. Custom Design
Advantages:
Unique and tailored to exact needs of the org
Flexibility and full control
2. Selection and purchase off shelf
Advantages:
Fast and efficient Rollout of system
Learning curve experience from hundreds/thousands of previous
users
Economic value – fixed low price
High quality through trial and error
3. End-User Development
4. Hybrid – Make & Buy
Buy off shelf and customize to their more specific needs
METHODOLOGIES FOR BUILD YOUR OWN PROJECT
1. SDLC - System Development Life Cycle
Concept = detailed justification and planning is the key to reduce risk and
uncertainty in system design.
Considerable up front effort
Outputs of one stage = inputs for next stage
Done in Three Phases:
a) Definition – identify features of proposed info system. Actors in this
phase are General and Functional Managers.
Steps:
i. Investigation – what business issues are you solving/covering
ii. Feasibility analysis – scrutinize project from technical, operational and
economic perspective. Outcome of this analysis is a
“Go” – “No Go” recommendation.
METHODOLOGIES FOR BUILD YOUR OWN PROJECT
iii. System Analysis – identify and articulate system requirements
* Outcome of this stage is the system requirements document by project
team. Contains what the inputs to system will be, what outputs will be, which users
have which access. Screenshots and mock up may be included.
b) Build – Done by developers. Take system requirements and build a robust, secure
and efficient application.
Steps:
i. System Design – create structure, identify hardware to be used, language to be
adopted and data structure. Output is a precise set of documents that programmers
use to write code.
METHODOLOGIES FOR BUILD YOUR OWN PROJECT
ii. Programming – abstract software design turned into set of
commands/instructions that can be executed by the hardware.
iii. Testing – Alpha testing by developers themselves, Beta testing by limited
number of users.
iv. Implementation
v. Installation – 4 ways to install:
a. Parallel – run old and new together for time
b. Direct – Cut old system straight off
c. Phased – replace piece by piece
d. Pilot – small department or area first as test run
End user training and change management done at this stage.
METHODOLOGIES FOR BUILD YOUR OWN PROJECT
Advantages of SDLC Approach:
Systematic – reduced uncertainty and risk
Clear roles and expectations for all people involved
Well suited for large scale and sensitive projects
Limitations of SDLC Approach:
Highly structured – rigid
Substantial time and cost overheads up front
Hard to make changes/adapt throughout
METHODOLOGIES FOR BUILD YOUR OWN PROJECT
2. Prototyping
About staying nimble and iterating through many versions to get to end product
Easier for end user to react/feedback about working prototype than an idea on
paper
Increases chances of accurate end product if you have their feedback
Prototyping Lifecycle:
Requirements definition – Development team draws up basic requirements
Initial prototype – First iteration – partially functional
Evaluation – Review and feedback
Revision
Completion
Advantages of Prototyping:
Quick delivery
Closer to user needs – they are more involved throughout
Best use in small scale project
Limits sunk cost and risk
Allows for trial and error
Limitations of Prototyping:
Can be less secure, robust or reliable because basic
Not suited for large scale or complex projects
METHODOLOGIES FOR BUILD YOUR OWN PROJECT
3. Agile Methodology
Values: Individuals & interactions, working software, Customer Collaboration,
Responding to change
Centres around being adaptable at speed for short periods
Small amount of planning – ability to adopt new information easily
More focused on customer needs at that given time
Done in open office spaces, daily face to face meetings and a designated
customer representative
METHODOLOGIES FOR BUILD YOUR OWN PROJECT
4. Outsourced Development
Software firms that fill in for a firm’s information system development
Can be done virtually, from anywhere in the world – ability to pull best talent
without location barriers
CMM = Capability Maturity Model rates companies on the quality of the
software they produce.
Benefit is a superior cost - quality ratio as it can be outsourced to high skilled,
low wage workers.
BUYING OFF THE SHELF
1. Definition
Components of the system articulate a vision for the
proposed information management system and evaluate its
technical, operational and economic viability.
a. System analysis – functionality required of the proposed system,
done by system analysts and stakeholders.
b. Evaluation Criteria – talk to software vendor through a RFP
(Request for proposal) process. Tell them what are the Essential
features, value add features and nonessential features.
c. Compile shortlist of vendors
d. Create and send out RFP to shortlist
e. Evaluate alternatives received
f. Negotiate a contract with chosen vendor.
END USER DEVELOPMENT
Knowledge workers create software, instead of IT professionals
Can be as small as a Spreadsheet, to personal databases, to fully fledged
software systems
Advantages:
Increased speed of development
End user guaranteed satisfaction because they build it
Reduce pressure in the Information System function of a business
Risks:
Unreliable quality standards
High risk and incidents of errors
Continuity risks – anyone who isn’t the creator might struggle to understand it
Can put more pressure on Info System managers due to needing help to complete