COP 4331C-001: Processes for Object Oriented Software Development (Fall 2017)

 Faculty:           Dr. Damla Turgut
Office:             ENG3 316
Phone:             (407) 823-6171

Class Time:   M W 6:00 PM - 7:15 PM
Classroom:    HPA1 112
Office Hours: M W 4:30 PM - 5:45 PM

GTA: Salih Safa Bacanli
Office: HEC 308
Office Hours: Mondays 2:00 PM - 4:00 PM

GTA: Jun Xu
Office: HEC 308
Office Hours: Thursdays 2:00 PM - 4:00 PM

Recitations: M 5:00 PM - 5:50 PM and W 5:00 PM - 5:50 PM in BA1 218

Pre-requisite: COP 3503C, COT 3960 (Foundation Exam - for Computer Science students)

Credit Hours: 3

Required Textbook:
Shari Lawrence Pfleeger and Joanne M. Atlee, "Software Engineering: Theory and Practice", 4th Edition, Prentice Hall, 2010.

Reference Books:
1. Perdita Stevens and Rob Pooley, "Using UML, Software Engineering with Objects and Components", 2nd Edition, Addison-Wesley, 2006.
2. James Rumbaugh, Ivar Jacobson, and Grady Booch, "The Unified Modeling Language Reference Manual", 2nd Edition, 2005.
3. Martin Fowler, "UML Distilled: Applying the Standard Object Modeling Language", 2nd Edition, Addison-Wesley, 2000.
4. Readings from classical and current software engineering literature (software engineering journals available via UCF electronic library resources)

Catalog Description:
Design, implementation, and testing of computer software for Engineering applications.

Course Assessment Outcomes:
This course is designed for undergraduate computer sciend and computer engineering students.
1. The students shall be able to construct UML diagrams of the following types: Use Case Diagram, Class Diagram, Activity Diagram, Collaboration Diagram, State Transition Diagram, Sequence Diagram and Data Flow Diagram
2. The students shall be able to work in a group environment.
3. The students shall be able to work on a project for a client, performing all the steps associated with the object-oriented software development life cycle including elicitation of the requirements from a client, preparation of software requirements specification, project management plan and test plan of a software system.
4. The students shall be able to write technical high level design and detailed design of a software system.
5. The student shall be able to produce implementation of design and write user's manual including build instructions of a software system.
6. The students shall be able to prepare and successfully give oral presentation of a software system design and operation of the class project deliverables.


  • Grading Scheme:
  • Standard 90/80/70/60 scale will be used for grading (curved if necessary) and also the instructor may use +/- grading for the final grades.

    Academic Dishonesty: The department, college, and University are committed to honesty and integrity in all academic matters. We do not tolerate academic misconduct by students in any form, including cheating, plagiarism and commercial use of academic materials. Please consult the Golden Rule Handbook for the procedures which will be applied.

    Verification of engagement: As of Fall 2014, all faculty members are required to document students' academic activity at the beginning of each course. In order to document that you began this course, please complete the following academic activity by the end of the first week of classes, or as soon as possible after adding the course, but no later than August 25. Failure to do so will result in a delay in the disbursement of your financial aid. To satisfy this requirement, you must finish the first quiz posted online. Log in to Webcourses, choose COP4331-002, and submit your answers online.