1. Systems Approach to Problem Solving
Define the Problem
Develop Alternative Solutions
Select the Solution
Design the Solution
Implement the Solution
Evaluate the Solution

2. Type of Feasibility Economic feasibility Technical feasibility
Operational feasibility
Organizational feasibility*
Legal feasibility
Schedule feasibiltiy

3. Systems Lifecycle Model (Waterfall Model)
Project
definition
Systems
study
Design
Programming
Installation
Post-
implementation

4. Plus/Minus of Lifecycle Systems
Good for projects which are
well defined
highly structured
need rigorous analysis and tight controls
Overall lifecycle model is
expensive
time-consuming
inflexible

5. Prototyping Project Identify Definition Requirements Develop Prototype
Improvement
Needed
Use
Prototype
Evaluate
Performance
Accepted
Prototype

6. Plus/Minus of Prototyping
Good for projects where
user requirements are uncertain
design solutions are uncertain
end-user interface is critical
size is smaller
Problems are
final prototype may not be well designed
user may want prototype immediately

7. Build versus Buy
Design phase may conclude that a better solution is to buy an application software package and adapt it to the organization needs.
Buy doesn’t require expensive in house development efforts
Buy may not fit unique needs of organization

8. End-User Development
Allow end user to access/develop information systems
A good match for distributed, end-user computing
Fourth generation tools allowing end-users to be more successful

9. Plus/Minus End-User Development
improved requirements determination
increased user involvement
reduced application backlog
Minus
end-user not performing core job
uncertain quality
poor integration
loss of management control over data

10. Outsourcing Going to the Cloud
Contract IS work to external vendor.
Not the same as buying a package.
Build = write custom payroll package
Buy = buy prewritten payroll package
Outsource = contract with PayCheck Corp. to do your payroll

11. Plus/Minus of Outsourcing
allow organization to make up for lack of IS expertise or capacity
vendor economies of scale may make it the more cost effective alternative
Minus
lose control of organization’s information
keep organization from developing infrastructure