CSE 2221 * We aren't endorsed by this school

CSE 2221 Software I: Software Components

  • Average Course Rating (from 2 Students)

    4.0/5
    Overall Rating Breakdown
    • 2 Advice
    • 5
      50%
    • 4
      0%
    • 3
      50%
    • 2
      0%
    • 1
      0%
  • Course Difficulty Rating

    • Easy 0%

    • Medium 100%

    • Hard 0%

  • Top Course Tags

    Background Knowledge Expected

    Great Intro to the Subject

    Group Projects

* We aren't endorsed by this school

Software I: Software Components Questions & Answers

Software I: Software Components Flashcards

Software I: Software Components Advice

Software I: Software Components Documents

Showing 1 to 30 of 363

Sort by:
{[$select.selected.label]}

Recent Documents


Software I: Software Components Questions & Answers


Software I: Software Components Advice

Showing 1 to 2 of 2

View all
    • Profile picture
    Sep 05, 2017
    | No strong feelings either way.

    Not too easy. Not too difficult.

    Course Overview:

    The course isn't about learning to be a good developer. Is how to memorize the slides.

    Course highlights:

    Easy course. Just read the slides. Make sure to go to office hours if you really need help. If you let yourself fall behind you will.

    Hours per week:

    6-8 hours

    Advice for students:

    Don't skip class, a lot of what is on the midterm is said in class

    • Fall 2016
    • WayneHeym
    • Yes
    • Math-heavy Background Knowledge Expected Group Projects
    • Profile picture
    Dec 05, 2016
    | Would highly recommend.

    Not too easy. Not too difficult.

    Course Overview:

    This course is absolutely fundamental in getting a solid basis in good software design, and I emphasize good. Anyone can hack together software, but documentation, standards, and coding practices learned in this class will contribute to successful software development going forward.

    Course highlights:

    Good software design, the Java programming language, and the basic of ideas of object oriented programming, along with a little HTML and some data structures.

    Hours per week:

    6-8 hours

    Advice for students:

    Show up to every single lab, do them completely. Start the projects the day they're assigned, and review them for the tests. The tests are not hard, they're simple made to trick you, or are highly pedantic.

    • Fall 2016
    • Mike Fritz
    • Yes
    • Great Intro to the Subject Many Small Assignments Participation Counts

Ask a homework question - tutors are online