Week 5


Part Two: Possible Capstone Ideas (30 minutes)

After viewing at least 3 presentations of Capstone, list three possible capstone projects you might choose to do at the end of your study. These sample project ideas which you may or may not pursue.

1: Cardiac Analysis Trainer:

The last 5 years of my life I have been staring are cardiac rhythms. Maybe I should create an app that teaches people the basics of EKG analysis


2: Teledoc TELEkit

In a world where tele health has become more and more available. Non urgent check ups and urgent consulations can be done over a mobile device with a camera. I propse some kind of kit that you can pick up at a pharmacy that contains basic tools to collect vitals at home: blood pressure monitor, pulse-oximiter, thermometer, and scale. Just like tools a medical assistant would use at a clinic. All the items would be able to transmit data via Bluetooth to the teledoc app of choice

3: It's Dangerous to Go Alone! : Capstone team builder

Create a kind of bulletin  board of Capstones online! Create profiles of users and create a capstone proposal. Find people who have the same interest as you and build something great together

 

Part Three: Keep Up With Your Learning Journal (30 minutes)

Update the learning journal to include what have you learned from this week's activities, including if you are thinking about internship or graduate programs. 


This week we talked about how take advantage of AI when writing. Being able to ask AI the right questions can me all the difference. AI can be a little tricky to get a decent answer, and prompting effectively can either make or break your experience. We also dive deep into the ethical issues when using AI. It does make raw character and word generation easier, but it does not do a great job with analysis. It is our job as the students to take all the information and synthesize cohesive analysis and conclusion. 

 


Comments

Post a Comment

Popular posts from this blog

Journal week 6

 One of the most interesting sections from this week was the topic of semaphores as a synchronization primitive.  Semaphores serve as way to help manage concurrency and work very similarly to locks but rather than just letting one thread access critical sections. Semaphores can allow “n” number of threads through. But by setting s semaphore to a value of 1, it can act just like a binary lock. As threads pass through a semaphore, a counter goes ups and down depending on what integer was initialized. As threads use the semaphore, the value decrements and once it reaches 0, no more threads can make use of the critical section. Once a counter reaches zero, it does the “wait()” operation. As threads finish with the critical section, it lets go of the semaphore and increments the value, allowing another thread to make use of its resources. It can serve as great synchronization tool, when two semaphores are used in tandem.  Another synchronization primitive we learned about was ...
Read more

Journal Entry Week 2

 One of the most interesting things I learned this week was about CPU scheduling. Everyday I use my phones or laptop, I take for granted the amount of processing power that is being the machine! This week the most tedious thing we did was hand calculate turn around time and response time. We also had to assume that there was only one available core, as other resources were not factored into the calculation.  Among the different kinds of scheduling , each of them have their own strengths and weaknesses. For example the Round- Robin scheduling excels at response time but sacrifices turnaround time in the process. By frequently switching to different jobs in small slices, the computer is able to work on all jobs what seems like simultaneously. With responses times at basically zero,  the amount of context switching that the computer has to do may drastically increase the turn around time.  Another scheduling algorithm we applied this week was the shortest Job priority. ...
Read more

CST334 Operating Systems Week 1

This week was kind of an eye opener. Being raised in an era where the internet just started booming, I always saw a computer as a black box. Almost like a modern-day Ouija board; I use the letters on a magic board and I get to see and speak to another person not in the room.  The internet has become the culmination, and as a teenager I used that knowledge to download sketchy mp3 files off a green citrus application.   I never really thought about computers and how an operating system served as an API. As I my make my way through these computer science course, I now see that I stand on the shoulders of giants. I’ve grown a deeper appreciation for all groundwork laid before me. Breaking down everything that an operating system does for the user is incredible. By the use of virtualization, it almost seems like how flawless using a computer uses its resources. From the users perspective, you kind of just expect it work out of the box.  Another Idea that I take for gr...
Read more