The objective of the course is to provide students with a working knowledge of the underlying foundations of object-oriented design and analysis and the current state of practice. Object-oriented analysis involves developing conceptual models of the problem domain of a software product. Object-oriented design involves developing models of the software solution to the problem clarified during analysis, and constructing programs that implement the design models. A fundamental objective of the course is for students to learn to think in terms of objects, so that they can identify the objects in a system and assign responsibilities to system components.

The topics covered in this course are listed below (subject to change, not in exact order, as time permits):

• Java coding style and idioms.
• Object-oriented analysis and design.
• Problem analysis.
• Conceptual modeling.
• System behavior modeling.
• Software architecture.
• Design modeling.
• Design patterns.
• Refactoring.

By the end of the course:

• Students will be able to analyze problems and develop conceptual models, generate designs from the models, and write program code that implements the designs.
• Students will be able to evaluate and improve object-oriented models and code.
• Students will be proficient at using the Unified Modeling Language (UML) to develop object models, and Java to implement the designs.
• Students will be familiar with some facets from agile programming.

4 semester hours (3 lecture, 1 lab)

Lab hour to be arranged by students to work on assignments and project deliverables.

This course is geared towards undergraduate students in Computer Science.

• This is not an introductory course on Java programming. Students must have experience in programming and debugging object-oriented software (e.g., Java and C++). Programming exercises in CS414 use Java. Our department uses Java in many courses (CS160, CS161, CS200, CS314, etc.), so students are expected to be proficient in Java programming.
• Students are expected to know the basics of software engineering as taught in CS314 using a text such as:
  • Lethbridge, T.C. and Laganiere, R., 2005. Object-oriented software engineering: Practical software development using UML and Java. New York: McGraw-Hill.
  • Pressman, R.S., 2005. Software engineering: a practitioner's approach. Palgrave Macmillan.
  • Sommerville, I., 2004. Software Engineering. International computer science series. Ed: Addison Wesley.
• A good understanding of discrete math and logic including first-order predicate calculus is expected (CS166), and data structures (CS200). CS200 and CS253 are prerequisites to CS314, which is a prerequisite to this course.

Required texts

Optional (but useful) texts

Lecture slides

Minimal equipment and resources required

Although CS 414 has a general email account, Canvas will be the main communication platform for this course. Therefore, if you need to communicate with the instructor or the GTA, you should do so through Canvas. The CS 414 email account should be only used as a last resort, or if you do not have access to the course in Canvas. Do not email the instructor or the GTA directly.

All presentations will be held in the same classroom as the regular lectures.

^* Subject to changes. A detailed class schedule will be made available.

Next are the formally graded elements of the course and associated weighting:

^* Subject to changes.

Calculation of the final class score is the average of grades for the category times the weight for the category shown in table above. The final point score will not be curved. The assignment of letter grades will be made as follows:

Some clarifications:

1. Class participation will be determined in a variety of ways. Attendance is required. There may be in-class exercises or quizzes that are graded. You are strongly encouraged to ask questions in class.
2. Design assignments will be of two types, short assignments and long team projects. Each design assignment needs to be turned in electronically via Canvas or GitHub (depending on the assignment requirements) by 2:59pm on the due date.
   Short assignments: There will be a couple of short modeling assignments, as well as programming assignments that involve writing code to implement requirements and use design patterns, and also writing code to implement test cases. Short assignments are individual.
   Long team project: There will be a long project with several deliverables including requirements, use cases, domain models, design models, program code, and test code. This will be done as an iterative project with code due several times during the semester. Each team will have 5 members.
3. Canvas will be used by students to discuss challenges and issues related to the project (e.g., its analysis, design and implementation), class topics, or questions formulated by the instructor along the semester. Students are strongly encouraged to start discussions and actively participate in them. We expect each student to make an initial posting, followed by responses to other students' postings. Merely having one sentence that says, for example, "I agree with everyone", is not enough to get a grade.
4. There will be one final exam to take place around week 16. Exact dates will be announced later.

Submissions can be re-graded if you feel that there was a mistake in grading. Contact us within 4 calendar days for a re-grade. Work will be re-graded in its entirety, and may result in an increase, decrease, or no change in the grade. Note that, once an assignment has been graded, no re-dos or re-submissions are allowed.

There will be no makeup for missed assignments or in-class activities, and students will receive a score of zero. If a student is unable to deliver an assignment due to a documented illness, accommodations will be made by the instructor according to university policy.

If a student miss the final exam, the student will receive a score of zero.

Assignments are to be submitted through Canvas, presentend in class or stored in a repository. Specifics will be included in each assignment. Always check the assignment information for due dates. You lose 15% of the maximum possible grade per day for any late submissions. No late submissions will be accepted after three days of the original due date.

Students are expected to attend every class. Students should not ask for special considerations to allow them to miss classes or not take examinations, including finals, at appointed times.

Respect for your classmates is necessary at all times. We work to maintain an environment supportive of learning in the classroom and laboratory. Towards that end, we require that you be courteous to and respectful of your fellow participants (i.e., classmates, instructors, GTAs and any tutors). In particular, unless otherwise directed for an in-class activity:

• Put away your cellphone. If you are expecting an emergency call, sit near the door and slide out discretely to take it.
• In class use of electronic devices in general, and laptops specifically, is permitted as a courtesy so that you may better participate and learn. If at any time the instructor judges that your use of an electronic device is becoming a distraction to others, you may be asked to to turn it off and put it away. Laptop/tablet users must sit in the back row starting from the corners.

Respect for your classmates is necessary at all times. We work to maintain an environment supportive of learning in the discussion forum. Towards that end, we require that you be courteous to and respectful of your fellow participants (i.e., classmates, instructors, GTAs and any tutors). In particular:

• Be professional and corteous.
• Do not post any questions about your grade or any grading issues. Such questions are private communication and must be emailed.
• Do not post any opinions regarding your graded assignment, or any aspect of the course. You will have a chance to submit anonymous reviews at the end of the semester. Email feedback to the instructor regarding the course is acceptable and welcome.
• Be constructive and provide complete answers.
• Provide references and attribute credit for the content you post when needed.

The instructor reserves the right to delete postings that do not promote a conducive learning experience for students in the class.

Students are expected to be professional in the way they communicate with their fellow participants (i.e., classmates, instructors, GTAs and any tutors). Many guidelines exist for academic etiquette and written communication. Students are highly encouraged to read the next articles:

• U Can't talk to Ur Professor Like This (Molly Worthen, NY Times).
• Email Etiquette: Guidelines for Writing to Your Professors (Mark Tomforde, University of Houston).

All students are expected to conduct themselves professionally. . Students are assumed to be familiar with the policies in the student information sheet for the department.

This course will adhere to CSU Academic Integrity Policy as found in the the General Catalog and the Student Conduct Code. At a minimum, violations will result in a grading penalty in this course and a report to the Office of Conflict Resolution and Student Conduct Services.

students are considered computing professionals, albeit perhaps just starting. Students should be familiar with the code of conduct for the primary professional society, ACM. The ACM Code of Conduct can be found HERE.

Please visit http://catalog.colostate.edu/general-catalog/policies/students-responsibilities/ for other policies.