Dr. Damla Turgut
Office: ENG3 317
Phone: (407) 823-6171
Class Time: Section 001: T TH 9:00 AM - 10:15 AM and Section 002: T TH 4:30 PM - 5:45 PM
Classroom: Section 001: HEC 103 and Section 002: HEC 119
Office Hours: T TH 10:15 AM - 1:15 PM
Web site: http://www.cs.ucf.edu/~turgut/COURSES/COP4331C_OOD_Fall10/COP4331C_OOD_Fall10.html
Class Mailing List: To send an email to the class list, use firstname.lastname@example.org (section 001) and email@example.com (section 002)
Office: HEC 308
Office Hours: TH 2:00 PM - 5:00 PM
Office: HEC 254
Office Hours: W 10 AM - 1 PM
Recitations: F 2:30 PM - 3:20 PM HEC 104 and F 2:30 PM - 3:20 PM HEC 119
Pre-requisite: COP 3503 Computer Science II
Credit Hours: 4
Shari Lawrence Pfleeger and Joanne M. Atlee, "Software Engineering: Theory and Practice", 4th Edition, Prentice Hall, 2010.
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)
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 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.
3. The students shall be able to write technical high level design and detailed design of a software system.
4. The students shall be able to write userís manual including build instructions of a software system.
5. The students shall be able to prepare and successfully give oral presentation of a software system design and operation of the class project deliverables.
6. The students shall be able to read and critique a research paper on a specific area such as requirements, design, maintenance, and so on through class presentations and a written report.