There's not too much to say about our Capstone proposal. There's only one new section (Executive Summary), and there's no new content involved. It's just a re-hashing of everything in our proposal so far, or at least the important stuff. We had to give a summary of the problem and solution, include some information about our resources and budget, talk about the dates on the Timeline for the most important things, and I added a bit about the Methodology (what I'm actually doing to complete this project).
Other than that, we've just been working on our Capstones. I think we'll have the rest of the semester to work on them, too. There's going to be a final presentation in early December where we talk about what we've done so far and why we should be allowed to go forward with our project. There was also the Proposal Defense earlier. Even in the Capstone class there's a lot of stuff to do other than Capstone. Heh, I guess that's why we need a portfolio system at CSUMB.
As for my project, I'd say it's going along well. I'm learning about Moodle, and about how to implement all of the things I'm going to need to implement. I hope to have access to the iLearn testing environment soon. Not much to say. Planning is on track.
Showing posts with label week12. Show all posts
Showing posts with label week12. Show all posts
Friday, November 20, 2009
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:
Comments (Atom)