EEL 5881-0L01 Software Engineering I (Fall 2008)



 Faculty:           Dr. Damla Turgut
Office:             ENG3 317
Phone:             (407) 823-6171
Email:             turgut@eecs.ucf.edu

Class Time:    W F 9:00 AM - 10:15 AM
Classroom:     ENG1 388
Office Hours: W F 10:20 AM - 11:50 PM or by appointment
Web site:        http://www.cs.ucf.edu/~turgut/COURSES/EEL5881_SEI_Fall08/EEL5881_SEI_Fall08.html
Class Mailing List: To send an email to the class list, use eel5881@eecs.ucf.edu

TA:                  There will be no TA assigned for this class.

Pre-requisite: EEL 4851 Engineering Data Structures
                         EGN 3420 Engineering Analysis

Credit Hours: 3

Required Textbooks:
1. Ian Sommerville, "Software Engineering", 8th Edition, Addison Wesley, 2007.
2. F.P. Brooks, Jr., "The Mythical Man-Month: Essays on Software Engineering, Addison-Wesley, Reading, MA, 1975. Twentieth Anniversary Edition, Addison-Wesley, Reading, MA, 1995.

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 advanced undergraduate and beginning graduate 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, critique, and present a research paper on a specific area such as requirements, design, maintenance, and so on through class presentations and a written report.

Topics:

  • Grading Scheme:

  •