This week was all about refining our Capstone proposal. It is now structured, and each section has clearly defined requirements. This makes it much easier to write. I'm glad we started out informally, it makes this feel like a big step. I guess it's partly because our proposal now has a title page and a table of contents (even if there are only two things listed so far).
Now that we've got requirements on each section, I know how to separate my ideas, and what to put in each section. Because of this, my proposal feels more like a proposal now. I had some areas I really needed to expand on. I still do, I guess, but I know what kinds of things should go there. Specifically, I feel like my problem statement needs work. I did a fairly good job of not talking about the solution (have you ever tried it? It's hard - I want to dive into the answer and stop talking about the problem), but that part is a bit empty compared to my solution description. Then again, in addition to general requirements, the solution description is the area to talk about how the solution fulfills the 5 required elements of a Capstone. I guess it makes sense that the solution section is bigger than the problem section, but it still makes the problem section feel smaller by comparison.
I also had to get my advisor contact form signed and scanned, but that wasn't a big deal.
Friday, September 18, 2009
Friday, September 11, 2009
Thoughts, Week 2
This week, web site modification was easy for me. I had to add a paragraph describing my Capstone idea, which was easy once I'd selected an idea and written the 200 more words describing it. I was basically summarizing from a larger document. I also changed the formatting of the assignments a little bit. I'm using my website template from my Web Design class, which has cool stuff like CSS dropdown menus. In that class, I had to talk a bit about each assignment, so each one needed its own page. In this class, the files are self-descriptive, so without a page describing each assignment, I needed to revise the structure of my links.
That's just esoteric stuff though, not what this class is about. Our main goal this week was to select one of our two ideas from last week. I had to think about it a lot. I've had some good times with Tarsier, and I can tell that they're a good group of people, and a good project to be involved with. Still, they're more science-oriented than I am, and the iLearn portfolio system is closer to what I see myself doing once I finish college. I ended up going with that (the iLearn portfolio system, that is).
The other thing we had to do this week was find and talk to a Capstone adviser. My concentration is programming, both of my potential Capstones are mainly about programming, there's only one pure programming teacher at CSUMB, I've taken many classes from him and know him well, and we've been working together this semester for a different class (independent study). Suffice to say, this part wasn't a problem. I didn't even look at this part of the assignment until today, which turned out to be my downfall - we have to get our potential adviser to sign a piece of paper saying we really did talk to them. Oh well, we meet Mondays for the independent study, so I'll do it then.
That's just esoteric stuff though, not what this class is about. Our main goal this week was to select one of our two ideas from last week. I had to think about it a lot. I've had some good times with Tarsier, and I can tell that they're a good group of people, and a good project to be involved with. Still, they're more science-oriented than I am, and the iLearn portfolio system is closer to what I see myself doing once I finish college. I ended up going with that (the iLearn portfolio system, that is).
The other thing we had to do this week was find and talk to a Capstone adviser. My concentration is programming, both of my potential Capstones are mainly about programming, there's only one pure programming teacher at CSUMB, I've taken many classes from him and know him well, and we've been working together this semester for a different class (independent study). Suffice to say, this part wasn't a problem. I didn't even look at this part of the assignment until today, which turned out to be my downfall - we have to get our potential adviser to sign a piece of paper saying we really did talk to them. Oh well, we meet Mondays for the independent study, so I'll do it then.
Friday, September 4, 2009
Thoughts, Week 1
The thing that surprised me most this week was how easy it was to get ideas for a Capstone project. I didn't know we'd have to come up with ideas so quickly, and I didn't have any planned, but I was able to talk to a few people and find ideas that just needed a chance to happen. I knew Tarsier* would be an option, but Eric Tao talked about an iLearn Portfolio, and it sounds like an interesting idea for a Capstone. A background with Tarsier won't help me out in the world, but a background with iLearn definitely might. Lots of people have heard of Moodle/iLearn. On the other hand, Tarsier is a full-featured modeling program, though it's only used by a small group.
Thankfully we can put down two ideas and narrow it down to one by next week, so I can spend a few days thinking of pros and cons for both sides.
* Tarsier is a 3D modeling program used by a few individuals in the Science department. I worked with them a little bit last semester.
Thankfully we can put down two ideas and narrow it down to one by next week, so I can spend a few days thinking of pros and cons for both sides.
* Tarsier is a 3D modeling program used by a few individuals in the Science department. I worked with them a little bit last semester.
Wednesday, December 5, 2007
Class Summary, Nov 29
This week we learned how to give technical presentations. I already knew a lot of this stuff, but not all. In fact, I learned something today that helped me give a better presentation the following week in the lab for this class. That piece of information was that people only remember about 30% of what you tell them, so the best way to give a presentation is to tell them what you're going to tell them (intro; what you'll cover), tell it to them (body), and then tell them what you told them (summary). The teacher for the lab class said she really likes it when people do this.
So, general presentation tips: don't have too much text, don't use just one color, have a background that is more interesting than a single color without clashing with the text, no more than seven things per slide (studies have shown that more than seven things, including pictures and the title, is less effective), and dress appropriately (your audience remembers your presentation, not your attire).
Now for some specific tips. First, for the opening: Establish relevancy to your audience. Give an overview of your presentation - tell them what you're going to tell them. Relate it to the big picture; how will it affect the future, how will it affect their lives, etc. Lastly, thank the people that helped you - they'll appreciate it.
For the body of the presentation: When using a chart to show data, choose the right type of chart. Make sure it doesn't give the wrong impression or convey the data incorrectly. Make sure it's easily readable and appropriate to your data. When designing slides, don't put more than one concept on a single slide. Low-content slides are okay, but two concepts on the same slide is a bad idea. If possible, start the slide title with a verb, because it sounds more active than a noun or other type of word. When going through your presentation, you should take about 90 seconds on each slide. A bit less is okay, but not too much, because with each new slide the audience doesn't listen to you for ~30 seconds while they read/understand it. A bit more is okay, but if you go for too long with a single slide the audience will get bored. Subtle animations are best, so you don't distract your audience from your content.
For the ending: When answering questions, approach the person as you call on them, so they know you're talking to them. Repeat the question to the audience, both so everybody can hear it and to give yourself a few seconds to think. Finally, talk to the audience as you answer it, so they continue to feel involved. There are a few ways of dealing with hostile questions, but the best way is to dodge them.
The most import thing to do, in my opinion, is to not read your own slides. They should be a guide to what you're presenting, but you need to give the meat of the presentation. Otherwise, why not just give the audience the presentation to read themselves?
So, general presentation tips: don't have too much text, don't use just one color, have a background that is more interesting than a single color without clashing with the text, no more than seven things per slide (studies have shown that more than seven things, including pictures and the title, is less effective), and dress appropriately (your audience remembers your presentation, not your attire).
Now for some specific tips. First, for the opening: Establish relevancy to your audience. Give an overview of your presentation - tell them what you're going to tell them. Relate it to the big picture; how will it affect the future, how will it affect their lives, etc. Lastly, thank the people that helped you - they'll appreciate it.
For the body of the presentation: When using a chart to show data, choose the right type of chart. Make sure it doesn't give the wrong impression or convey the data incorrectly. Make sure it's easily readable and appropriate to your data. When designing slides, don't put more than one concept on a single slide. Low-content slides are okay, but two concepts on the same slide is a bad idea. If possible, start the slide title with a verb, because it sounds more active than a noun or other type of word. When going through your presentation, you should take about 90 seconds on each slide. A bit less is okay, but not too much, because with each new slide the audience doesn't listen to you for ~30 seconds while they read/understand it. A bit more is okay, but if you go for too long with a single slide the audience will get bored. Subtle animations are best, so you don't distract your audience from your content.
For the ending: When answering questions, approach the person as you call on them, so they know you're talking to them. Repeat the question to the audience, both so everybody can hear it and to give yourself a few seconds to think. Finally, talk to the audience as you answer it, so they continue to feel involved. There are a few ways of dealing with hostile questions, but the best way is to dodge them.
The most import thing to do, in my opinion, is to not read your own slides. They should be a guide to what you're presenting, but you need to give the meat of the presentation. Otherwise, why not just give the audience the presentation to read themselves?
Thursday, November 29, 2007
Reflection on my 7 habits
Ah, assignments. This one is about the 7 habits from the book Seven Habits of Highly Successful People. The instructions are as follows:
Include a reflection of the 7 habits; do you think they are important for you as a students? Why? Which of the 7 habits that you already have? Which you don't?
Again, those seven habits are:
I think those habits are useful for everybody, student and professional alike. The first three are important for personal success. For example, there are many helpful programs in college, but they don't seek out students. Students need to be proactive and seek them out. For college students, beginning with the end in mind is the best way to take classes. I know several friends who take the classes they feel like taking, without any regard for what their overall college education will look like. That's the end, the goal of college - to be educated. How educated do 50 easy classes make a person? Not very educated at all.
The second three habits (#4-7) are important for group projects. In group projects, students need to work together to make sure everybody gets a good grade, and more importantly to make sure everybody learns from doing the project. If one person does it all, the entire group might get a good grade, but they wouldn't learn. That's the purpose of group projects. That's what "winning" means in the context of a group project.
Understanding others is also very important to group projects; both when listening to other people's presentations, and when presenting your own; you need to know the material before you can tell others about it. The last of these habits, synergizing is a very important part of being in a group.
The last habit, sharpening the saw, is perhaps the most important one for students. We're here to learn about our field of choice, but extraneous knowledge matters a lot in life. If we don't know basic things about geography, history, health, etc, we won't get far in life.
Include a reflection of the 7 habits; do you think they are important for you as a students? Why? Which of the 7 habits that you already have? Which you don't?
Again, those seven habits are:
- Be proactive
- Begin with the end in mind
- Put first things first
- Think win-win
- Seek first to understand, then to be understood
- Synergize
- Sharpen the saw (upgrade your physical, mental, social, and spiritual health)
I think those habits are useful for everybody, student and professional alike. The first three are important for personal success. For example, there are many helpful programs in college, but they don't seek out students. Students need to be proactive and seek them out. For college students, beginning with the end in mind is the best way to take classes. I know several friends who take the classes they feel like taking, without any regard for what their overall college education will look like. That's the end, the goal of college - to be educated. How educated do 50 easy classes make a person? Not very educated at all.
The second three habits (#4-7) are important for group projects. In group projects, students need to work together to make sure everybody gets a good grade, and more importantly to make sure everybody learns from doing the project. If one person does it all, the entire group might get a good grade, but they wouldn't learn. That's the purpose of group projects. That's what "winning" means in the context of a group project.
Understanding others is also very important to group projects; both when listening to other people's presentations, and when presenting your own; you need to know the material before you can tell others about it. The last of these habits, synergizing is a very important part of being in a group.
The last habit, sharpening the saw, is perhaps the most important one for students. We're here to learn about our field of choice, but extraneous knowledge matters a lot in life. If we don't know basic things about geography, history, health, etc, we won't get far in life.
Wednesday, November 28, 2007
Class Summary, Nov 15
Today we didn't have any speakers. Rather, we learned all about Capstones. I've been hearing about them since I came here, but they were never clearly defined. Until now. A Capstone presentation is basically the final presentation before you graduate. It's more about the preparation than the final presentation, so as long as you did the work you should do alright, grade-wise. Capstones are cool because everybody does a different one, so there are all these big projects you can look at. It demonstrates to me that CSUMB students can really produce something.
Well, that's what it demonstrates in general, but it means more than that to me because I like looking at other people's projects, and since everybody does a Capstone there are tons of projects that are all different, all student-chosen. Fun stuff to look through if I ever have a lot of spare time.
The presentations are usually done in the classroom for this class, building 18, room 118. They're also broadcast to a monitor outside, and furthermore they're recorded and stored for 5 years. We can request a copy of 'em too. These things are official.
They're usually PowerPoint presentations, and usually about 10 slides long. Some people do other formats, but that's the norm. The standard Capstone presentation engages the audience, describes a problem, describes some potential solutions, states the chosen solution and why it was chosen, and shows how well it has worked. As usual for presentations, the audience can ask questions at the end. This means that the Capstone projects have to solve a problem. They also need to use sophisticated technology and/or design, and involve a community partner or a client. The intent here is to use our technology to solve problems in the community.
Heh. Salinas/Marina/Monterey must love CSUMB. There are all these helpful projects, done by CSUMB students, for free.
Anyway, Capstones have three classes dedicated to them: CST 400 (choosing a Capstone), CST 401 (doing that Capstone), and CST 496 (working with your Capstone advisor). CST 400 and 496 are taken one semester, then 401 and 496 the next semester. Yes, that means taking CST 496 twice; it ensures your advisor is involved in the entire process.
There are lots of potential Capstones, but there are some requirements. As stated before, a Capstone needs to:
A Capstone itself requires:
Another important thing is that since a community partner is involved, the Capstone needs to be able to be finished if that partner bails from the project. Thus Capstones are usually things developing everything required to set up a database of <something>, rather than actually setting it up. Setting it up would be very easy from the finished Capstone, but it would require buying the computers and software necessary. That part is up to the community partner, and if they choose not to do it the student can still complete his/her Capstone.
Well, that's what it demonstrates in general, but it means more than that to me because I like looking at other people's projects, and since everybody does a Capstone there are tons of projects that are all different, all student-chosen. Fun stuff to look through if I ever have a lot of spare time.
The presentations are usually done in the classroom for this class, building 18, room 118. They're also broadcast to a monitor outside, and furthermore they're recorded and stored for 5 years. We can request a copy of 'em too. These things are official.
They're usually PowerPoint presentations, and usually about 10 slides long. Some people do other formats, but that's the norm. The standard Capstone presentation engages the audience, describes a problem, describes some potential solutions, states the chosen solution and why it was chosen, and shows how well it has worked. As usual for presentations, the audience can ask questions at the end. This means that the Capstone projects have to solve a problem. They also need to use sophisticated technology and/or design, and involve a community partner or a client. The intent here is to use our technology to solve problems in the community.
Heh. Salinas/Marina/Monterey must love CSUMB. There are all these helpful projects, done by CSUMB students, for free.
Anyway, Capstones have three classes dedicated to them: CST 400 (choosing a Capstone), CST 401 (doing that Capstone), and CST 496 (working with your Capstone advisor). CST 400 and 496 are taken one semester, then 401 and 496 the next semester. Yes, that means taking CST 496 twice; it ensures your advisor is involved in the entire process.
There are lots of potential Capstones, but there are some requirements. As stated before, a Capstone needs to:
- Solve a problem
- Use sophisticated technology and/or design
- Involve a community partner or a client
A Capstone itself requires:
- Complexity (it can't be too easy)
- Integration of technology and design
- Technology/design excellence (this is a professional project)
- Client/community involvement
- Project management
Another important thing is that since a community partner is involved, the Capstone needs to be able to be finished if that partner bails from the project. Thus Capstones are usually things developing everything required to set up a database of <something>, rather than actually setting it up. Setting it up would be very easy from the finished Capstone, but it would require buying the computers and software necessary. That part is up to the community partner, and if they choose not to do it the student can still complete his/her Capstone.
Subscribe to:
Posts (Atom)