Monday, August 17, 2009
The pivot week.
It's not that i am an IT snob. Okay, maybe i am. But pivot tables aren't really that intuitive to me. Just cos you can drag and drop doesn't mean that that makes sense. That's leaving alone the facts that you are using a absolutely horrible data structure for decision support. Clearly excel isn't very scalable. You can do everything in the query if you want to (as is in excel) but it's not easier from a user perspective. If you want a usable data structure star schemas are much better. They require extra effort to create rather than just using an excel table but it's a much better solution. You can make a star scheme in access and make queries in that and it should be much easier (evidenced by the FI5095 DW tute in access).
Maybe I have too much trust in the POD but i think i will be following his suggestions on when to do work on the assignment and do it in small bits after we do stuff in the tutes. Which means I need to start doing my assignment, which is really disappointing for me as a lazy person.
Something tells me the diagram on the right is going to be on the exam. I have no idea how i would get that idea. Might have been the incredibly subtle hints, not sure though. I think it's just the vibe. The great thing about this model is that you kind of know it already. Like it's like a combination of everything i've learned in a way. It's a triangle (kinda) and has evolutionary development like Keen's model. It's kinda got SDLC-like boxes in; planning, deliver and use. What goes in those boxes is sort of obvious. The circles are just components (sub-processes) of the boxes. I could argue that strategy and resourcing is typically a little bit going to be controlled in the boardroom and could be outside the boundaries of evolutionary dev. You could add a big box around everything saying organisational culture or something similar, but then it would be ugly. I find that you can put such a big box around almost all diagrams.
You only have 15 readings for week 5. I look forward to skipping them.
It's not that i am an IT snob. Okay, maybe i am. But pivot tables aren't really that intuitive to me. Just cos you can drag and drop doesn't mean that that makes sense. That's leaving alone the facts that you are using a absolutely horrible data structure for decision support. Clearly excel isn't very scalable. You can do everything in the query if you want to (as is in excel) but it's not easier from a user perspective. If you want a usable data structure star schemas are much better. They require extra effort to create rather than just using an excel table but it's a much better solution. You can make a star scheme in access and make queries in that and it should be much easier (evidenced by the FI5095 DW tute in access).
Maybe I have too much trust in the POD but i think i will be following his suggestions on when to do work on the assignment and do it in small bits after we do stuff in the tutes. Which means I need to start doing my assignment, which is really disappointing for me as a lazy person.
Something tells me the diagram on the right is going to be on the exam. I have no idea how i would get that idea. Might have been the incredibly subtle hints, not sure though. I think it's just the vibe. The great thing about this model is that you kind of know it already. Like it's like a combination of everything i've learned in a way. It's a triangle (kinda) and has evolutionary development like Keen's model. It's kinda got SDLC-like boxes in; planning, deliver and use. What goes in those boxes is sort of obvious. The circles are just components (sub-processes) of the boxes. I could argue that strategy and resourcing is typically a little bit going to be controlled in the boardroom and could be outside the boundaries of evolutionary dev. You could add a big box around everything saying organisational culture or something similar, but then it would be ugly. I find that you can put such a big box around almost all diagrams.You only have 15 readings for week 5. I look forward to skipping them.
0 comments:
Post a Comment