1. During this last part of the project, I reflected on my project. I used the paragraphs I had written prior to me starting my project and compared the goals I had originally made, to what I had actually accomplished. I wrote more paragraphs in this reflection to further explain the project and I went into detail of how I actually did accomplish my goals.
2. I learned the importance of a reflection. If I were to just finish a project and just forget about it, I wouldn't understand the importance of the project and all the steps I took to completing it. With this reflection, and the pre-written paragraphs, I was able to identify what I accomplished with this project, where my plan come in handy, and what my strengths/weakness were in this project. That way I can apply what I learned this time to future projects.
3. This took me one hour. It took me so long because I wanted to compare the reflection to the pre-written paragraphs and I didn't want to forget any aspect of the project in the reflection.
Senior Project
Saturday, January 11, 2014
Project: Programming: December 28th 2013
1. During this part of the project, I took what I learned earlier, and programmed my routers. Properly working routers are essential to a working network, so I took my time and made sure everything was right and programmed correctly so ensure a good connection between devices in my network.
2. During this part of the project, I learned that research is VERY helpful. My previous research made programming my routers a breeze. I also learned that plans aren't always set in stone. I learned this because I had planned to program my routers one week before I set up my network. I realized that that made no sense, I can't program my routers with IP addresses if I don't even know what IP addresses I would use or need. Therefore, I had to move this part back a week and program the routers during the setup of my project.
3. This took me 1 hour. I had two routers, and both needed to be programmed. I went through each router making sure the configuration was correct and would allow a proper connection. After this, I tested each router every way I could, and when I found errors in the programming I would fix the errors and re-test.
2. During this part of the project, I learned that research is VERY helpful. My previous research made programming my routers a breeze. I also learned that plans aren't always set in stone. I learned this because I had planned to program my routers one week before I set up my network. I realized that that made no sense, I can't program my routers with IP addresses if I don't even know what IP addresses I would use or need. Therefore, I had to move this part back a week and program the routers during the setup of my project.
3. This took me 1 hour. I had two routers, and both needed to be programmed. I went through each router making sure the configuration was correct and would allow a proper connection. After this, I tested each router every way I could, and when I found errors in the programming I would fix the errors and re-test.
Project: Virtual server: December 21st 2013
1. For this part I downloaded a virtual server software. I did this because I wanted to practice setting up a domain controller the provides necessary services that allow a network to work properly (like DHCP and DNS). Servers are essential to a network, and so I used this part of my project to allow me to familiarize myself with a server and how to set it up.
2. This made me learn the importance of practice. I say this because I ran into many problems with the virtual server. But I was able to work through these problems and fix them, that way when I really had to set up a server I already knew how to do so. I still ran into problems, but I knew how to fix them, or at least, how to troubleshoot them.
3. This took me about 2 hours. It took so long because, I first had to download the software. After this, I spent a lot of time setting up the server. I took my time so I didn't miss anything, that way I would set up a good server that wouldn't have a lot of problems right off the bat.
2. This made me learn the importance of practice. I say this because I ran into many problems with the virtual server. But I was able to work through these problems and fix them, that way when I really had to set up a server I already knew how to do so. I still ran into problems, but I knew how to fix them, or at least, how to troubleshoot them.
3. This took me about 2 hours. It took so long because, I first had to download the software. After this, I spent a lot of time setting up the server. I took my time so I didn't miss anything, that way I would set up a good server that wouldn't have a lot of problems right off the bat.
Project: Research routers: December 6th 2013
1. During this part of my project I had to research which kind of routers I wanted. I also had to research how to program these routers. Having the right kind of routers and having them programmed in a way that would work with the network I wanted to set up was essential to having a functional network.
2. During this, I learned that research is critical in a project like this one. If I didn't research routers I would have been completely clueless as to what kind of routers to use with my network. This research made the end result functional, and it made the project much easier because I already had everything planned out.
3. This took me about 2 hours. It seems like a long time, but it took me this long because I had to sort through many different routers before I found the one that would work for me in my network. Also, after finding the appropriate router, I had to find out how to program it in a way that would work with my network.
2. During this, I learned that research is critical in a project like this one. If I didn't research routers I would have been completely clueless as to what kind of routers to use with my network. This research made the end result functional, and it made the project much easier because I already had everything planned out.
3. This took me about 2 hours. It seems like a long time, but it took me this long because I had to sort through many different routers before I found the one that would work for me in my network. Also, after finding the appropriate router, I had to find out how to program it in a way that would work with my network.
Project: Paragraphs: December 4th 2013
1. In this part of the project I decided to put all of my goals into writing. I did this so I would always be able to look back at the paragraphs if I got lost or off topic. I also did this so at the end of my project I could look at my paragraphs and make sure I DID complete all my goals or if I had to go back and revise my project in order to complete all my primary goals.
2. This also taught me the importance of planning. These paragraphs became the basis of my project. I wanted to achieve every goal I wrote with my project. These paragraphs are what drove my whole project.
3. This took my about half an hour. I had a couple of goals in mind and with each goal I wrote details on how I was going to achieve each goal, this helped me set up my network in a way that would accomplish every goal of mine.
2. This also taught me the importance of planning. These paragraphs became the basis of my project. I wanted to achieve every goal I wrote with my project. These paragraphs are what drove my whole project.
3. This took my about half an hour. I had a couple of goals in mind and with each goal I wrote details on how I was going to achieve each goal, this helped me set up my network in a way that would accomplish every goal of mine.
Project: Diagram: December 4th 2013
1. In this part of my project I wanted to create a diagram of my network. The reasoning behind this was to give me a map for my network, that way I wouldn't be lost when I was setting it up. This was also a planning step before I actually set up my network, and it really helped me when I had to set up my network. I had my basic network all planned out before I even started setting it up.
2. This part, much like the overall plan, taught me that planning, even very small details, are essential. When I actually got to set up my network, I had no question as to how I was going to do it, I already knew where I wanted every component to go, this made the whole thing easy and quick.
3. This diagram only took me about 30 minutes. I used a program to help organize my ideas of where my components should be placed. In the end, I had a diagram that served as my map for the project.
2. This part, much like the overall plan, taught me that planning, even very small details, are essential. When I actually got to set up my network, I had no question as to how I was going to do it, I already knew where I wanted every component to go, this made the whole thing easy and quick.
3. This diagram only took me about 30 minutes. I used a program to help organize my ideas of where my components should be placed. In the end, I had a diagram that served as my map for the project.
Project: Interview: December 1st 2013
1. For this assignment I interviewed an IT manager and a programmer to get both sides of creating a network. I did this because it takes the IT manager to set up the network (hardware and software) but it also takes some programming to set up the routers and other equipment.
2. I learned that there is multiple things to consider in a project like this one. For example, if I just set up a network but I completely forget to program the routers right, my network wouldn't work. This made me realize that projects require a lot of consideration and leaving out one essential part can create problems with my end result. This is where the plan was very helpful, I made sure I didn't forget any part.
3. This took me 1 hour. I interviewed the IT manager for 30 minutes and the programmer for 30 minutes. I felt like this was long enough to really understand each aspect of the project before I set off to do some research on my own.
2. I learned that there is multiple things to consider in a project like this one. For example, if I just set up a network but I completely forget to program the routers right, my network wouldn't work. This made me realize that projects require a lot of consideration and leaving out one essential part can create problems with my end result. This is where the plan was very helpful, I made sure I didn't forget any part.
3. This took me 1 hour. I interviewed the IT manager for 30 minutes and the programmer for 30 minutes. I felt like this was long enough to really understand each aspect of the project before I set off to do some research on my own.
Subscribe to:
Posts (Atom)