A little girl was talking to her teacher about whales.
The teacher said it was physically impossible for a whale to swallow a human because even though it was a very large mammal its throat was very small.
The little girl stated that Jonah was swallowed by a whale.
Irritated, the teacher reiterated that a whale could not swallow a human; it was physically impossible.
The little girl: said, "When I get to heaven I will ask Jonah".
The teacher: asked, " What if Jonah went to hell?"
The little girl: replied, "Then you ask him".
Wednesday, September 24, 2008
Wednesday, September 17, 2008
Wk 10: Use Case Realization
After last week horrible podcast, i've learnt to appreciate having a living lecturer speaking infront of the electronic rostrum. It is nice to have Rob back and hope he is all well from last week.
This week, we talked about use case realization, the design of class diagrams, interaction diagrams, sequence diagrams and collaboration diagrams. From assignment 1b, i should have sufficient practice for use case diagram and the class diagram. That assignment, we are talking and showing the functions of the system. This few diagrams shows how objects react with each other. The simplified or summarised name for these diagrams are known as object-oriented design.
I've not really read up much on this diagrams therefore unable at the moment to write much about each diagrams. But a quick glance through the slides, i am refreshing some of my memory through the lecture. Guess my next post will be much more detailed in the diagrams.
This week, we talked about use case realization, the design of class diagrams, interaction diagrams, sequence diagrams and collaboration diagrams. From assignment 1b, i should have sufficient practice for use case diagram and the class diagram. That assignment, we are talking and showing the functions of the system. This few diagrams shows how objects react with each other. The simplified or summarised name for these diagrams are known as object-oriented design.
I've not really read up much on this diagrams therefore unable at the moment to write much about each diagrams. But a quick glance through the slides, i am refreshing some of my memory through the lecture. Guess my next post will be much more detailed in the diagrams.
Friday, September 12, 2008
Assignment 1b completing
This assignment has been taking alot of my time recently. I have been doing the requirements and diagrams. And now i see the fruit of my labour. I'm not aiming for a HD but hopefully get a decent mark to make my life easier. Also, to prove that what i understand from this point onwards is correct.
Tuesday, September 2, 2008
Professional Report
The time has come to start doing and worrying about the report on analysis. A major 20% of the overall grade. It is something that will cause a worry among my peers. Hehe... Well, i've started by creating small steps or tasks that are required to be done. Once each task is done, i can compile them together to make the actual report.
Monday, September 1, 2008
Week 7: Ending Analysis Phase
This is the final lecture regarding analysis. I realise that we took three weeks to fully complete analysis studies. So this must have certain importance in this unit. The analysis of a system is very the basis of the system. As we discussed before, if the analysis is not done properly or critical tasks are not taken in during analysis the system will fail to fit the requirements of the client.
On this week, we talked about how much system costs, how much automation the system has to be, request for proposals, etc. Compared to the slides from the past week, this was rather done quickly. It was not rushed through and Rob really wanted to slow down but i think he has done a good job trying his best to slow down his talking.
Part of teh lecture we discussed about how systems are developed. It can be done via internal or external sources. Internal sources require the organisation to develop the system with their own staff. External sources means getting people outside the organisation to develop the system.
Pros and cons? Internal means staff from the organisation are asked to develop the system. This means that they are taken from their usual workload and given this new task. Sensitive data is kept within the organisation when the system is being developed in-house. Cost of developing is lower compared to external sources.
External sources are organisations that are experts in developing systems. These companies comes in, plan, analyze and design the system. They are good at what they are doing and they don't come cheap. I know how much a simple ERP solution cost while i was interning at Microsoft. Cost is not the important part. It is trust. Trust that these external sources do not leak sensitive data or even customer data to their rivals. As these organisations deal with plenty of other customers, the is a risk of losing sensitive data to competitors. MS made sure that the project leader sign a document with the company to trust them. Trust them not to comprommise sensitive data. If discovered, MS will pay damages. Usually amounts that i have dreamed of winning. Haha...
Lastly, we discussed about the professionalism in our work. How we present our analysis in a profesional way. How companies will ask for quote on developing the system. This is important as analysis understood by just the developers is not much of value when the clients do not understand them. Therefore we must create documents that satsify both parties than money will start to roll in.
On this week, we talked about how much system costs, how much automation the system has to be, request for proposals, etc. Compared to the slides from the past week, this was rather done quickly. It was not rushed through and Rob really wanted to slow down but i think he has done a good job trying his best to slow down his talking.
Part of teh lecture we discussed about how systems are developed. It can be done via internal or external sources. Internal sources require the organisation to develop the system with their own staff. External sources means getting people outside the organisation to develop the system.
Pros and cons? Internal means staff from the organisation are asked to develop the system. This means that they are taken from their usual workload and given this new task. Sensitive data is kept within the organisation when the system is being developed in-house. Cost of developing is lower compared to external sources.
External sources are organisations that are experts in developing systems. These companies comes in, plan, analyze and design the system. They are good at what they are doing and they don't come cheap. I know how much a simple ERP solution cost while i was interning at Microsoft. Cost is not the important part. It is trust. Trust that these external sources do not leak sensitive data or even customer data to their rivals. As these organisations deal with plenty of other customers, the is a risk of losing sensitive data to competitors. MS made sure that the project leader sign a document with the company to trust them. Trust them not to comprommise sensitive data. If discovered, MS will pay damages. Usually amounts that i have dreamed of winning. Haha...
Lastly, we discussed about the professionalism in our work. How we present our analysis in a profesional way. How companies will ask for quote on developing the system. This is important as analysis understood by just the developers is not much of value when the clients do not understand them. Therefore we must create documents that satsify both parties than money will start to roll in.
Subscribe to:
Comments (Atom)
