| Campus: | University of Hawaii at Manoa | Course: | ICS 414 - Software Engineering II |
|---|---|---|---|
| Department: | Information& Computer Sciences | Crn (Section): | 85564 (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 learned a lot in this course.
|
||||||||||||||||||
6. I developed skills needed by professionals in this field.
|
||||||||||||||||||
7. I have become more competent in this subject area during this course.
|
||||||||||||||||||
|
8. What did you find most valuable and helpful about the course? |
||||||||||||||||||
|
Having weekly discussion meeting with the professor certainly helped to fix problems and reminded us the purpose of this course. Being able to practice what we have learned from previous ICS courses as well as personal skills to incorporate into a real experience, this course is the reason why I have decided to become an ICS major.
Exposure to a more freeform and probably workplace realistic project system.
The diversity of the projects gave a more real life feel to the class.
Since this course is a continuation of ICS 413 I felt that I got to practice the principles of
software engineering in a real world setting.
I found the experience interacting with an outside organization to be most valuable. We were faced with problems that were outside of our control and learned how we could still be productive while waiting for these issues to be resolved. I also found the weekly meetings to be helpful because they provided guidance for our project to ensure that we stayed on track. The meetings were also good for providing new ideas and critiquing the work we had previously accomplished.
i find it very valuable to at least meet up once a week with our Professor to discuss our current progress and set a goal what to accomplish for the next week.
I like how this course is taught using methods that similar to what we might encounter in the real world rather than following the standard academia approach.
Having no lecture and only weekly meetings allows more time to work on projects.
Project planning & execution, teamwork, and weekly meeting with the professor were all valuable experiences.
The continuation and development of good coding practices, along with weekly meetings that helped simulate real life situations. Ironically always had words of encouragement/inspiration.
I got a lot of experience from working in a team environment.
Working in groups is a very valuable experience. Many courses don't have group work and working together on a project allows us to apply it to something more than an assignment.
Working in groups, was really a great experience. I enjoyed working with my
teammates since the project started. We accomplished much more as a team and
we supported each other when we had any problems.
Real world experience in software development field.
Being pushed to find and learn things ourselves and implementing them.
The ability to work in a team environment. Able to approach a problem with minimal requirement
with confidence. Gained proper knowledge and mindset to produce objectives for resolving difficult
issues. Professionalism was expected throughout the entire course.
Philip Johnsons class is a class that makes me feel sorry for people who never took it. The
knowledge you learn from him and what he pushes you to learn will put you leagues ahead of the
others. He encourages you, engages you in long conversations, you develop perspectives and skills
you probably won't even get after you're hired. His 413-414 combination was the best move I made
in my undergrad degree and I highly suggest you give it your all (it is a lot of work) when you take
this class as you will not be disappointed with what you take away.
More over, I feel that now I am able to walk into any software project and find my way to becoming
an active contributor.
The strong aspect of cooperative work that was missing for most part of the first part of the software engineering course.
This is the first project based course that I have taken. I learned a lot from working in groups and how to effectively communicate with the other group members.
|
||||||||||||||||||
|
9. What did you find least valuable and helpful about the course? |
||||||||||||||||||
|
Having presentations for the class is kind of pointless when the majority have no clue what is actually going on. The only feeling I have after every presentation is lower self-esteem and I could only envy other's work which might be the same for others.
uncertain defining of requirements and necessary factors.
None
I thought that having presentations every week was a little too much. Many of the presentations were similar. Although progress had been made, it may be on an aspect of the project that is not seen visually. I think that having presentations every other week might be better, so each group has more to present.
I guess it would be that some instructions is a little unclear and some objectives may change out of nowhere.
Nothing at the moment
Usually when we tried something new or did what we thought would be best for the project and it did not conform to the Professors ideas we were shot down.
Some of software engineering principles that we studied in ICS413 were not enforced. I have a feeling that I would have been able to complete this course without having to take ICS413 previously.
It was nice to have a choice on which things we wanted to develop, however, some categories didn't seem like it was Software Engineering at all but something that the Kukui Kup needed and people were assigned to do it. Groups like Content Development where you make a video or create rules for a competition, don't seem Software Engineer-ish. You could have spent the entire semester and not learn a new language or create a software app, but instead create mock-ups and make a video. Learning a new language is great, and it seemed like you really wanted us to come through on our deliverable's, but in the end, even if we tried our best, but the deliverable wasn't par, our grade suffered.
There wasn't a lot of structure in this course at the beginning. I wish there was a 1-2 week period where students not only started researching into their projects but also received a lot more guidance.
None
Fewer class meeting.
Time consuming
None.
There were very high expectations made for undergraduate students. Although it pushed us to achieve higher goals it also made other school work especially stressful when deadlines fell into the same period.
Learning on my own.
|
||||||||||||||||||
|
10. Other comments: |
||||||||||||||||||
|
Overall, working with various tools, i.e project hosting site, discussion, programming languages for this course is excellent, working with smaller groups is also a plus. I would suggest instead of traditional presentation, maybe recording the groups' presentation and displaying them online may attract more comments and reviews.
This class was unlike any other class that I have taken. It allowed us more freedom to work on projects of our choosing. I liked the fact that we could choose the direction of our project rather than being given strict guidelines to follow.
Other than that I learned how to collaborate with my group and acknowledge each of the members' strenghts and weaknesses to figure what each member can do to contribute in the project.
WattDepot + Software Engineering = Kukui Kup
Very good class. It is very beneficial for any ICS student to take.
Great course and great teacher.
It was a very fun course! Thank you for all the priceless knowledge you've passed to the class.
Overall a good class, but the workload (even though it is open ended) can be really stressful to the average student that wishes to have a very structured course.
|