Faculty:
Dr. Damla Turgut
Office:
ENG3 317
Phone:
(407) 823-6171
Email:
turgut@eecs.ucf.edu
Class Time: T TH 9:00 AM - 10:15 AM
Classroom: HEC 117
Office Hours: T TH 10:15 AM - 11:45 AM or by appointment
Web site: http://www.cs.ucf.edu/~turgut/COURSES/COP4331C_OOD_Fall09/COP4331C_OOD_Fall09.html
Class Mailing List:
To send an email to the class list, use cop4331@eecs.ucf.edu
TA 1:
Hector Lugo
Office:
HEC 308
Office Hours:M W 10:00 AM - 12:00 PM
Email:
hlugo@eecs.ucf.edu
TA 2:
Antoniya Petkova
Office:
HEC 250
Office Hours:W 8:30 AM - 10:00 AM and F 12:30 PM - 2:30 PM
Email:
apetkova@cs.ucf.edu
Pre-requisite: COP 3503 Computer Science II
Credit Hours: 4
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 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.
Topics: