May 2020 Semester Reflection #2 Week 4

Week 4 - 25 / 6 / 2020

The topic for this week is Database and Big Data. For Big Data, I have asked the students to go through a digital lesson that I created on my Google Site. I hope they go through it. 

I begin the class with an activity on System Architecture. This activity is to demonstrate the IS components and also serves like a teaser to database. I could see that it does not turn out the way that I wanted.

The student end up doing like a flowchart which is not the diagram that I wanted. WHAT SHOULD I DO INSTEAD? I should have recap and show examples again on what is system architecture OR I could have guide the students like, I need servers and desktops from the icon library etc. It still good in a way because at least I know that student have lack of understanding on system architecture. But this also serves me an a warning on what Assignment 1 has set to become. 

After an hour or so doing it, which takes me around 10 minutes to do it (multiply by 6? If a 5 minute work of time, should be a 30 minute of student's work time 🤦, I give feedback to the students and explain to them the right way to do it. In WEEK5, I should ask the students to do it all over again. Make sure that it is correct this time AND PUT IT IN THEIR ONENOTE. 

Then I describe about database. The concept of database. So, with that I concluded the lecture. 

WEEK 5 (Announcement to be given Monday morning)

For Week 5, I will enhance the activity. The DUE DATE for the activity will be on the Week 5 before class. Firstly, student will

1. Improve the diagram. Make sure that it is relevant to the business process. 
2. Identify the Entity and its relationship. 
3. Draw an entity relationship.

For Big Data Lecture (Announcement on Monday morning Week 5)

1. Watch the videos on Banking and Customer Loyalty. 
2. Write a summary of the videos that you watch

In Class Week 5 (The first 20 mins)

1. Work in pairs
2. Explain to your partner about Banking and the other explain about customer loyalty

May 2020 Semester Reflection #1 Week 3

It is already Week 3. The topic for the first two weeks is about Introduction to Information Systems in Organization. The objective of this topic is to introduce to the students the concept of Information System, how IS can be adopted in organization and what are the competitive advantage that IS brings to organization. The concept of IS includes the components of systems IPOF and components of information system HSDTPP. 

The first class was only attended by 2 students. The lecture begins with definition of IS until the components of IS. 

In Week 2, the topic Intro to IS continues. The student number has increased to 20-something. Since majority of the students did not attend week 1, I recorded a video lecture for week 1. I don't repeat the lecture. I ask the students to watch the video. I only recap. I also develop a digital lesson on Google site for the students to go through and learn from it.

The topic for Week 3 is hardware and software. A digital lesson on hardware was developed for the class. The students have to go through the digital lesson. Students have to self learn the topics on hardware and I cover the software topics in class. At the beginning of the class, I asked students to ask questions on hardware and recap on the hardware. It takes about one hour to do that. Maybe, I would ask students to go through the lesson and ask questions on Telegram. In class, I will entertain those questions. I think it is going to save time. The intention of topic is to introduce students to IS architecture. At the moment, when they see an IS architecture, they can see the client, server and network devices which are all hardware. If the students can identify those components in the architecture, that is good enough.

The topic for Week 4 is database. My idea is not to go through the slides. Explain to them in a concept that they understand. I just want to show them how database fits in the IS. 

Idea for an activity is to show them the architecture and identify what data should be in the database server.