CST 462s - Module 2

Week 2,

This week is when we start putting in some work to our service learning and research paper. For the service learning, I was taught how to look for bug reports, and generally how long it takes to complete it. I have noticed there are some Linux users among the reports, and I tend to focus more on Windows. So, I started using a virtual machine to run Debian Linux so I can test more bug reports. 


For the research paper, my team and I started looking at related academic sources that can help us get an idea of what to research for. As I said last week, our topic is focused on a high school student’s access to technology and how it affects their educational outcomes and STEM participation. What we found was interesting, and a common topic we found was the Digital Divide, which in short is the gap between different groups of people created by unequal access to modern technology. There are a good number of papers that discuss this, and this helped us develop our research question, “How does limited access to technology affect STEM engagement and the academic success of underrepresented high school students from socioeconomically challenged communities?”.

Comments

Post a Comment

Popular posts from this blog

CST 311 - Module 3

 Week 3 This week's material was very more focused on the transport layer. One topic was multiplexing and demultiplexing. To sum the topic up, this is how data is handled from multiple sockets using a transport header. The multiplexing occurs at the sender, using the transport header containing the source and destination port number, then demultiplexing occurs at the receiver, which allows the receiver to deliver the received segments to the correct socket. There are also two variants of these, connectionless demux and connection-oriented demux.  More on the topic of connection and connectionless transport, connectionless refers to the UDP protocol and is considered bare bones, there is no handshaking and each UDP segment is handled independently. What makes it bare bones is the fact that there is no effort in flow control, delivering data in order, reliable data transfer. However, it can be implemented at the application layer. On the other hand, with connection transport (us...
Read more

CST 338 - Module 4

 This week in CST 338, there were few assignments to complete. This time we got to get our hands on Android Studio, where we created very simple app where android users can convert temperature °c to temperature °f, or vice versa. We also got to complete our first project, where we practiced inheritance using an abstract class, and concrete classes. However, besides that, we were also allowed to go back to our previous assignment, Markov, and have our teammates review each other's code. I worked with my teammate Ryan Matsuo  and after reviewing his code, I learned a few things that could help me in the future, like splitting a string using str.split() with a regex of "\\s+" instead of what I did which was more complicated. My strategy with solving the Markov assignment was that I started writing the code right away. I didn't put anything to practice into paper because I feel I can do the same thing in the code. I would read the prompt, create stubs for the methods to b...
Read more

CST 334 - Module 5

 Week 5, This module's subject involved a lot to do with using threads and dealing with concurrency. Having processes use threads to complete smaller portions of the process concurrently with other threads is a good way to complete tasks quickly. However, the main problem with using threads is making sure the outcome of the process is determinate, meaning you get the result you want every time. Sometimes without taking measures to keep the processes determinate, you can get an unexpected outcome. An example that the text we are reading brings to light is say you want to use a thread to increment a global variable 1 million times. So, if you want 2 threads to do this, you expect the outcome of the whole process to return 2 million. However, what you ended up getting was 1,984,865, not quite 2 million is it? This happens when two or more threads try and read/write a global variable (critical section) at the same time. Before one thread can change the global variable, another thread r...
Read more