Drilldown: CapGrads
Use the filters below to narrow your results.
Graduate:
Gradlast:
Gradyear:
Gradhouse:
Gradplans:
Gradadvice:
HAVE A BACKUP PLAN!! And a backup plan for that. But remember there is a such thing as too safe. Let loose but be prepared for failures and lessons. (1) ·
Make a plan at the beginning of the year, see if it is possible or acceptable, see how everything is going to work, and give it your best. (1) ·
Make sure you plan out your capstone well, and set your goals reasonably accounting for personal work ethic. (1)
Captype:
Capformat:
Capssubject: (Click arrow to add another value)
Capaward:
Capdiscipline:
Capdescription:
A slide show of some of the topics I went through in the TulsaTech class "Cyber security and forensics." Though it may not be the most polished thing in the world, I wanted to at least make the average computer/phone user aware of the different types of security threats that one could face while onl (1) ·
My original capstone project was to create an irrigation system for the plants in the Commons on top of the bookshelf. I designed the dropper, the base, end caps, the hose splitter, and connectors. I have my irrigation system put together on a metal shelf that I bought to finish the project. My irri (1) ·
We use computers every day of our lives, but have you ever stopped to ask what all the parts inside your computer do? I decided to tackle that question head on by having my friend and computer expert Maxwell Mahabir walk me through the process of building myself a new computer from the ground up. Be (1)
Capshortdescrip:
Capstonebegin:
A sort of TED talk like presentation. (1) ·
My capstone project was an indoor irrigation system for the plants on top of the book shelves in the Commons. The irrigation system was to be automated and would only need for the reservoir to be filled every so often; everything else would be taken care of by the system. The system would run off of (1) ·
My original project was going to be a video game coded in C# with a team of two other people aiding in code, assets, and sound design. (1)
Capchange:
It felt like I had to completely change my project. I had to downsize everything and almost start over. I lost the capability to set up the system how I had originally designed it. In order for the new system to work I had to completely change the way that the water was going to flow to the plants. (1) ·
The game project would have needed more time for us to fully learn Unity and C#, so we were forced to switch to building a computer. This project was still at least in the field of computer science so it still applied to what I will go on to study in college. (1) ·
Things didn't go exactly as planned, of course as stated many times it's not the most polished thing in the world but I feel like I could have maybe added more. (1)
Capreflection:
I did the best that I could with the time that I had. I made a system that worked and that watered my plants. It is not nearly as fancy or sophisticated as I had originally planned on it being, but I still made it happen and I am proud of it. It was a struggle and a half to completely spin and start (1) ·
I now know with great detail how all the parts in a computer fit together and can build a computer from the ground up without the assistance of my friend and mentor. (1) ·
While going to the Tulsa Tech for this capstone, I've learned many different things. Sure there was the initial cyber security, but I've also learned small bits of networking, and operating systems. Mainly different types of cyber attacks as shown in the slideshow, but also different types of connec (1)
Cappresentation:
Capadvisor:
Showing below up to 3 results in range #1 to #3.
View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)