This week we listened to the assignment MP3 in the tutorial. Honestly, I actually did not even realise there was an MP3 to listen to for the assignment. Good thing I attend classes then..haha :)
Lsitening to it once was not really enough, as I would phase out from time to time when trying to note down something important I heard. So I didn't get all the required details on the first time. Thank god for my lab partner who was actually listening to the recording while I was taking notes :)
The existing system seemed pretty simple and it reminded me A LOT of the case study for the IT in Organisations assignments. Instead of soft drinks delivery, it was about bread delivery.
During the interview, Daniel warned us that thinking too much about things the client did not ask for might make our assignments harder/longer.
I realised this was true after looking at the event table that was posted as an example on Moodle. Although a lot of the questions made sense, the client did not actually ask for these improvements to be made. I guess if we think it would make a lot of sense, then we just have to say that we have assumed the client agreed with this.
The event table itself was easy to understand. Although I think I need to actually make one to know if I'm having trouble understanding all the parts.
Thursday, March 26, 2009
Humans don't know what they want...
That video we watched in the tutorial about the Aeron Chair was REALLY interesting. Its amazing how the human mind works (or doesn't work :) )
Based on that video, I observed that humans can be fooled into believing they like something (or not) and that their taste keeps changing alllllll the time. The key here, I guess, is to know when to take what they have to say seriously and when to push forward with an idea even though the response was not great.
Based on that video, I observed that humans can be fooled into believing they like something (or not) and that their taste keeps changing alllllll the time. The key here, I guess, is to know when to take what they have to say seriously and when to push forward with an idea even though the response was not great.
Previously on SAD....
Things have been going pretty well for SAD.
We've been learning about System Analysts. This is the first time that I actually got a deeper insight into what they actually do and what is expected from them.
We've learned about the sets of skills an analyst is required to have (Fundamental knowledge of technology, technical, business and people skills) and also about his ethics and integrity. The role of the analyst in strategic planning was also covered. Basically we learned about all the important aspects surrounding an analyst and his contribution to the business.
We are now learning about the SDLC in more details every week. Ah, SDLC...I have been reciting these stages for too long now :)
1. Planning
2. Analysis
3. Design
4. Development
5. Testing
6. Maintenance
......
1. Planning
2. Analysis
3. Design
4. Development
5. Testing
6. Maintenance
......
1. Planning
2. Analysis
3. Design
4. Development
5. Testing
6. Maintenance
....
(that's me reciting the stages... :)
Each week SAD is going deeper into a different stage of the SDLC.
I've been keeping up with my readings most of the time. I don't always have time to read through the book, but definitely the study guide!
We've been learning about System Analysts. This is the first time that I actually got a deeper insight into what they actually do and what is expected from them.
We've learned about the sets of skills an analyst is required to have (Fundamental knowledge of technology, technical, business and people skills) and also about his ethics and integrity. The role of the analyst in strategic planning was also covered. Basically we learned about all the important aspects surrounding an analyst and his contribution to the business.
We are now learning about the SDLC in more details every week. Ah, SDLC...I have been reciting these stages for too long now :)
1. Planning
2. Analysis
3. Design
4. Development
5. Testing
6. Maintenance
......
1. Planning
2. Analysis
3. Design
4. Development
5. Testing
6. Maintenance
......
1. Planning
2. Analysis
3. Design
4. Development
5. Testing
6. Maintenance
....
(that's me reciting the stages... :)
Each week SAD is going deeper into a different stage of the SDLC.
I've been keeping up with my readings most of the time. I don't always have time to read through the book, but definitely the study guide!
First Entry
Before even starting this semester, I was not really looking forward to this unit. As most core units were to me, I thought this one would be boring too. The only factor that can make me change my mind about core units is often the staff.
Usually if the lecturer/tutor is boring or not passionate, it puts me off as well. I stop attending lectures and sometimes even tutorials and lose interest completely. On the other hand, if the lecturer is funny and is very clear in his/her explanation, then it keeps me awake and I will be regularly attending classes..and I will even read study guides! :)
Fortunately for this unit, we ended up with Cheryl instead of someone from Clayton. I have had classes with Cheryl almost every semester since I started this course (this is now my last semester), and I knew that her lectures were always good and she's really funny. As expected, I haven't missed any lectures and always leave without any confusion.
It's the first time I've had a class with Daniel as a tutor. Although I've seen him around uni a lot, I had no idea what kind of tutor he was. To my surprise, he was really funny in the tute. This alone makes tutorials enjoyable, especially since on Thursdays I have a very long day. He is very patient and talks 'human' to us (it's easy to understand his point).
All in all, great combo. It is similar to the staff we had for 'IT in organizations'... makes all the difference.
As for the unit content itself, it isn't as boring as Project Management. It also helps that we have already learned some parts of it in other units ( for e.g. IT in Organizations). The content is pretty straight forward and easy to understand (for the moment). I only have access to an old edition of the prescribed book, but I find that it is just as good as the new one. The gist of it is still the same.
Usually if the lecturer/tutor is boring or not passionate, it puts me off as well. I stop attending lectures and sometimes even tutorials and lose interest completely. On the other hand, if the lecturer is funny and is very clear in his/her explanation, then it keeps me awake and I will be regularly attending classes..and I will even read study guides! :)
Fortunately for this unit, we ended up with Cheryl instead of someone from Clayton. I have had classes with Cheryl almost every semester since I started this course (this is now my last semester), and I knew that her lectures were always good and she's really funny. As expected, I haven't missed any lectures and always leave without any confusion.
It's the first time I've had a class with Daniel as a tutor. Although I've seen him around uni a lot, I had no idea what kind of tutor he was. To my surprise, he was really funny in the tute. This alone makes tutorials enjoyable, especially since on Thursdays I have a very long day. He is very patient and talks 'human' to us (it's easy to understand his point).
All in all, great combo. It is similar to the staff we had for 'IT in organizations'... makes all the difference.
As for the unit content itself, it isn't as boring as Project Management. It also helps that we have already learned some parts of it in other units ( for e.g. IT in Organizations). The content is pretty straight forward and easy to understand (for the moment). I only have access to an old edition of the prescribed book, but I find that it is just as good as the new one. The gist of it is still the same.
Subscribe to:
Posts (Atom)