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

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

Class Time:   T TH 09:00 AM - 10:15 AM
Classroom:    CB2 (Classroom Building 2) 105
Office Hours: T TH 14:45 PM - 16:00 PM

GTA:Gurkan Solmaz
Office: HEC 308 and HEC 315
Office Hours: M 09:00 AM - 12:00 PM

Grader: Anvesh Thota
Office: HEC 308
Office Hours: T 12:00 PM - 2:00 PM and W 3:30 PM - 5:30 PM

Grader: Amirreza Samiei
Office: HEC 308
Office Hours: T W 10:30 AM - 12:30 PM

Recitations: F 2:30 PM - 3:20 PM and F 3:30 PM - 4:20 PM in ENG2 203

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: UCF's Golden Rule will be strickly applied.