FIT5094 Lecture Notes - Lecture 9: Industrial Engineering, Human Factors And Ergonomics, Transaction Processing System
2 Jul 2018
School
Department
Course
Professor
Lesson 1: Evolutionary Development is essential for DSS.
In real life scenario, the users may or may not be the actual decision makers. We often find
with Business Intelligence systems a style of usage, where there is another individual directly
using the system in assisting the main client. In that case, it is important to take in to
consideration the needs and preferences of both the decision maker and the actual user of
the system. But then the users are not very clear about what exactly they need until they
start using the system. It’s an on-going, developing process. While developing BI/DW
systems the one thing you want to avoid is big delays before you actually deliver the
decision support. If the requirements of the system really come from the system use, we
don’t know what the requirements are until people start using, we have to bootstrap that
process, start small and deliver quick wins >>>> build prototypes, get the user to respond to
it and derive requirements from that for the next development cycle>>>>user specification
keeps changing with time>>>easier to rectify or rebuild with smaller chunks of system
output provided, rather than the entire system which may not be helping the users with
their decision process. The usage pattern of using a BI system is fundamentally different
from using a Transaction processing system; it’s a two-way process. The users might use a
system in a completely different way from what it was intended by the builders/
designers….Affordances>>>adaptive usage. This happens all the time and the systems have
to evolve and change accordingly. Therefore, a BI/DW system should be developed using a
cyclical, evolutionary methodology, where each cycle behaves like a mini waterfall model.
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
Lesson 1: evolutionary development is essential for dss. In real life scenario, the users may or may not be the actual decision makers. We often find with business intelligence systems a style of usage, where there is another individual directly using the system in assisting the main client. In that case, it is important to take in to consideration the needs and preferences of both the decision maker and the actual user of the system. But then the users are not very clear about what exactly they need until they start using the system. While developing bi/dw systems the one thing you want to avoid is big delays before you actually deliver the decision support. The usage pattern of using a bi system is fundamentally different from using a transaction processing system; it"s a two-way process. The users might use a system in a completely different way from what it was intended by the builders/ designers . affordances>>>adaptive usage.
