yeah i know week 3 already, it's not all as new and exciting anymore is it? u start thinking about "oohhh what if i just miss this lecture and have a nice sleep in and just come to my tut. in the afternoon". bad boy/girl! i know bed is v. interesting u wont learn anything there. so turn up 4 lectures u big ugly boy or girl.
well lets do the boring stuff and talk about week 3 content for a while cos i mean that's what i'm meant to do right? it all sounds a bit familiar to material covered in IT in organisations FIT1003 the whole SLDC was covered a bit there, this is in much more detail of course.
YAY for Analysis
– Gather information: easy u just go talk to stake-holders and watch users.
– Define system requirements: after u have gathered info u can then make a document that lists the requirements that the stake-holders want
– Prioritize requirements: put in order of importance which of these requirements are important
– Prototype for feasibility and discovery: make a mock up of a system and figure out how possible it is to make and what problems u might encounter
– Generate and evaluate alternatives: think about what other solutions are out there for your problem eg: vendor solutions
– Review recommendations with management: present to managers all the advantages and disadvantages of different alternatives.
BPR is for dumbies unless the existing system really suffers from serious issues.
to be honest all of the content seemed pretty straigh foward i can't really find anything particularly challenging from this week cos i've done alot of this kinda stuff in other units.
Alors les garçons et les filles,
untill next time,
Toodles
1 comment:
Pretty cool blog - nice layout.
By the way POD doesn't have an iPOD (Can't afford one!).
POD
Post a Comment