| Campus: | University of Hawaii at Manoa | Course: | ICS 414 - Software Engineering II |
|---|---|---|---|
| Department: | Information& Computer Sciences | Crn (Section): | 85108 (001) |
1. The instructor demonstrated knowledge of course content.
|
||||||||||||||||||
2. The instructor fulfilled the goals of the course.
|
||||||||||||||||||
3. The instructor communicated effectively.
|
||||||||||||||||||
4. I learned to apply principles from this course to new situations.
|
||||||||||||||||||
5. I developed the ability to solve real problems in this field.
|
||||||||||||||||||
6. I deepened my interest in the subject matter of this course.
|
||||||||||||||||||
7. I enjoyed this course.
|
||||||||||||||||||
8. I developed skills needed by professionals in this field.
|
||||||||||||||||||
|
9. Which aspects of the course were most valuable? |
||||||||||||||||||
|
The course project allowed us to gain more experience with working not only with each other but engineers as well.
The group work and task driven design. This was important because it taught me to work well within a group.
Getting the chance to be a part of the solar decathlon was a wonderful experience.
The ability to work in groups was valuable because it really focused on the aspect of real-world software engineering. For any other programming class, the assignments are only based upon your work, but for this class you have to ensure that every group member knows the direction of the project to make it successful.
Having to do many projects throughout the course with group members. This allowed me a chance to apply the subject material of the course taught into meaningful work. Concepts such as project management, test cases, and utilizing QA tools.
Learning to effectively use the resources at our disposal and the experience
of several team working on different components of a single system at the
same time.
learning to cooperatively work on a project, version control, the importance
of testing
Working with web servers, XML, HTTP, HTML/Wicket. Oh and something about teamwork.
We developed skills needed by professionals in this field.
Group work was really helpful.
1) Being able to apply everything we learned in 413 to a real world project.
Sure, you get the gist of everything from 413, but you don't really know it
at a deeper level until you take 414. 2) Learning how to build a web server.
3) Learning how to use build tools to make our lives easier. 4) Being forced
to work in large teams and learning how to cooperate with each other. This is
synonymous to what happens in the real world. 5) Being forced to update our
portfolio and blog. This is useful for marketing ourselves to employers and
also keeping a history of the things we've done. 6) Learning the importance
of quality (unit testing) and scalability. 7) Getting experience in
integrating software systems together.
Working in small groups helped to develop better organization and communication skills.
Developing software/application that will actually be put in use in real life. It's always fun and rewarding thing to do knowing that it'll be use by others. It was also a very good motivation to do work. Also, the group work was very very valuable. Not only you get a good support but you'll also learn a lot from your other group members. This is the only ICS class that you'll be able to get to know the whole class.
incrementally building on knowledge from previous assignments helped in gaining understanding of
the overall process of the solar decathlon web application process
|
||||||||||||||||||
|
10. Which aspects of the course were least valuable? |
||||||||||||||||||
|
Pretty much everything Professor Johnson taught was relevant and valuable.
none...
Having quickie quizzes.
Everything seemed worthwhile.
n/a
meh.
None.
1) I'm still iffy on using Wicket. Sure it will help us learn bits of the
Document Object Model, but it is still very painful and has a steep learning
curve. 2) We need better web designers if we're making webpages. Students
who don't know squat about web design shouldn't be designing a commercial-
grade web interface.
They were all equally valuable.
nothing.
|
||||||||||||||||||
|
11. Ten years from now I'll probably remember this course most by ... |
||||||||||||||||||
|
The course project.
The Solar Decathlon Project.
I will remember this course by the iHale project. Taking a course that is focused on bring a web interface to Hawaii's solar decathlon house is unforgettable.
Always run ant -f verify.build.xml before committing changes. Don't want to waste the other group members' time when they want to work on the system/project.
Doing what we can to help with the Solar Decathlon project.
version control and using higher level functions/aspects of java
The crapload of work I had to do...
QA tools and Wicket.
The systemh project.
1) This course will give me a strong base from which to jump off of for a
career in software development. 2) This course alone will let me start off
with a higher entry level position and salary. 3) This course has opened
lots of doors for me in terms of future employment.
Solar Decathlon 2011
The fun times building projects with the other students.
The fun things we got to code. Like the Solar House management system
|
||||||||||||||||||
|
12. How can the instructor improve the teaching of this course? |
||||||||||||||||||
|
No comment.
I really liked the midnight deadlines instead for 10am before class. =]
Enforce more intermediary milestones in group projects to push orderly effort in project progression.
Although most assignments have been changed to a midnight deadline, having
noon deadlines (except on days we had class at noon) was a bit strange.
Majority of students will have free time during those few hours before a
midnight deadline, but not all will have those few hours before a noon
deadline available. So mentally it feels like we lost precious time to work
on an assignment with a noon deadline, although not necessarily true.
idk my bff jill?
N/A
1) Get students who can do great web design. Or if you're up for the
challenge, teach them how to become great web designers. 2) Teach students
how to create their own build system. Better yet, give them some katas on
Apache Ant, Ivy, etc.
More coding tips/tricks/hacks.
More small assignments between milestones, a bit more guidance to see learn what types of things
to consider when designing a system.
Maybe take more input from students before deciding on a project
|
||||||||||||||||||
|
13. My overall evaluation of this instructor is.... |
||||||||||||||||||
|
A great guy and a great teacher. Kept the lines of communication open and was always down to help. Could be a bit sarcastic at times, but always explained himself after (after all software engineering can be frustrating) . Johnson is very fair and caring but also a no nonsense guy who pushes each student according to their needs. Although I might not have done too well in his class I can say that UHM would be hard-pressed to find a better Professor.
He is a very good professor. His expectations are not unimaginable, but this doesn't mean his class is easy. The amount of work he expects is very reasonable for a 400 level course.
A very knowledgeable and enthusiastic professor, who makes the course fun to attend and work hard in. Although it appears that he'll require students to invest a large amount of time when compare to other equal weighted courses (3-credits), the payoff in knowledge gain is worth it. Compare to last semester (Fall 2010), this semester he provides grades and changes to assignment instructions within an appropriate time frame.
Great teaching style, guides you to a solution rather than giving it to you.
Good teacher. Really knows his material; but the most impressive part is how
much time he spends prepping for class. Really appreciate the effort.
pretty cool guy.
He cares about his students.
Good teacher. Knows what he's talking about.
Outstanding. Not a micromanager. Offers help but forces us to solve our own
problems. Fair grader.
A decent professor, might want to spend more time to know students.
He's a cool dude
Good. If there was a software engineering III, I would take it.
|
||||||||||||||||||
|
14. Other comments: |
||||||||||||||||||
|
Recommend this class to all ICS students. Here is where all the drudgery of the intro classes culminates into a hands-on, results-based, whirlwind of a class. Just make sure you are prepared to be rocked. Wish I studied more java...
I would take another class Professor Johnson taught.
A very fun course with lots of projects and assignments to be done.
I'm really glad that i took both 413/414. There are a number of things that
I can apply from these classes to the real world. I've already had some
experience as an intern and it's really helped to make the transition smooth.
As some have said before me, this class is a must!
meh.
N/A
Demand far outstrips supply for Philip Johnson's class. For every 20 people
who were able to enroll in this class, there are probably over 20 others who
could not get in. Some people even wait a year to get in. The ICS
department probably needs 2 more Philip Johnson clones to meet demand.
|