In-class post, 23/10/2006
Well I'm back once more...*cough*....*shiver*...
God I hope this cold is gone soon, especially this fever.... -_-
The class started with some discussions over deadlines for various events associated with this course...
By the way, the schedule is modified for next week as follows:
Monday - Lecture with Ms. Mohammed , 2:10pm, submit project during lecture.
Tuesday - Presentation of 3 projects, 10am
Thursday - " " " " , 9am-11am
Friday - Coursework Test, 10am.
He then started speaking about the course, how we are now in the 8th week of the course, and started discussing about the topics coming up until the end of the course.
Dr. Mohan then went into some insight into the discussion held last week. The discussion then strayed into the bmobile/digicel competition, about who is giving the real details.
He went back into talking about UWI's Banner system, how good information is needed to make any such decision. He then asked the question:
How do we go about acquiring or developing a new Information System?
*detailed information will be covered later on*
El Guy suggested the analogy of placing data in separate sections (hardware, software etc), and applying the data as needed.
Dr. Mohan then suggested that no matter what IS you want, there is a process called requirements analysis, which is part of the Systems Development Life Cycle (SDLC).
What makes a system useful is to take the components of an IS, and put them to a specific purpose.
The requirements analysis is done by :
1) Getting requests from stakeholders. Choosing requests has to be done carefully, typically by sampling from the various stakeholders of the system.
The requirements usually listed are:
1)What features does it have?
2) What capabilities does it have?
3) What services should it provide?
Communication among the users of the system is a majour issue when it comes to the development of an Information System.
One example of getting this data is by using questionnaires, interviews etc.
After the list of requirements, has been sourced, a design phase starts. The design includes software design, data design and the network design primarily.
A design can be generally described as a drawing that is done before the actual construction begins, which forms the system in an abstract way, such that it is in existence in thought, but not physically present at that point.
He finished with a thought to ponder: How do you design the construction of a boat?
Well we're done for today, at least I can sleep tomorrow...so we shall be back on Thursday....yes we will.......precioussss..... :)
God I hope this cold is gone soon, especially this fever.... -_-
The class started with some discussions over deadlines for various events associated with this course...
By the way, the schedule is modified for next week as follows:
Monday - Lecture with Ms. Mohammed , 2:10pm, submit project during lecture.
Tuesday - Presentation of 3 projects, 10am
Thursday - " " " " , 9am-11am
Friday - Coursework Test, 10am.
He then started speaking about the course, how we are now in the 8th week of the course, and started discussing about the topics coming up until the end of the course.
Dr. Mohan then went into some insight into the discussion held last week. The discussion then strayed into the bmobile/digicel competition, about who is giving the real details.
He went back into talking about UWI's Banner system, how good information is needed to make any such decision. He then asked the question:
How do we go about acquiring or developing a new Information System?
*detailed information will be covered later on*
El Guy suggested the analogy of placing data in separate sections (hardware, software etc), and applying the data as needed.
Dr. Mohan then suggested that no matter what IS you want, there is a process called requirements analysis, which is part of the Systems Development Life Cycle (SDLC).
What makes a system useful is to take the components of an IS, and put them to a specific purpose.
The requirements analysis is done by :
1) Getting requests from stakeholders. Choosing requests has to be done carefully, typically by sampling from the various stakeholders of the system.
The requirements usually listed are:
1)What features does it have?
2) What capabilities does it have?
3) What services should it provide?
Communication among the users of the system is a majour issue when it comes to the development of an Information System.
One example of getting this data is by using questionnaires, interviews etc.
After the list of requirements, has been sourced, a design phase starts. The design includes software design, data design and the network design primarily.
A design can be generally described as a drawing that is done before the actual construction begins, which forms the system in an abstract way, such that it is in existence in thought, but not physically present at that point.
He finished with a thought to ponder: How do you design the construction of a boat?
Well we're done for today, at least I can sleep tomorrow...so we shall be back on Thursday....yes we will.......precioussss..... :)
posted by SPK at 10/23/2006 02:20:00 PM
3 Comments:
thanks for the update, man
it's a very valuable contribution
Thanks you all :)
It can be a bit tiring sometime, but at least it can give some idea to those that may have missed out class for any session...
Well I know sometimes it was missing, largely due to instances where I may not have been present (like when I was MIA for 2 days due to the cold), but when I am there, I certainly make an effort to post.
Post a Comment
<< Home