Dr. Damla Turgut
Office: ENG3 317
Phone: (408) 823-6171
Class Time: M W 3:00 PM - 4:15 PM
Classroom: BA 216 (FEEDS)
Office Hours: M W 1:20 PM - 2:50 PM
Web site: http://www.eecs.ucf.edu/~turgut/COURSES/EEL6883_SEII_Spr08/EEL6883_SEII_Spr08.html
Class Mailing List: To send an email to the class list, use firstname.lastname@example.org
Office: ENG3 242
Office Hours: T TH F 11:00 AM - 12:00 PM
Pre-requisite: EEL 5881 or equivalent and/or consent of instructor
Credit Hours: 3
No required textbooks. The lectures will be based on latest published research papers in journals, conferences and reference books.
1. Linda M. Laird and M. Carol Brennan, Software Measurement and Estimation: A Practical Approach, Wiley-IEEE Computer Society Press, July 2006.
2. J. Fernando Naveda and Stephen B. Seidman, IEEE Computer Society Real-World Software Engineering Problems: A Self-Study Guide for Today's Software Professional, Wiley-IEEE Computer Society Press, July 2006.
3. Jeff Tian, Software Quality Engineering: Testing, Quality Assurance, and Quantifiable Improvement, Wiley-IEEE Computer Society Press, February 2005.
4. Donald J. Reifer (Editor), Software Management, 7th Edition, Wiley-IEEE Computer Society Press, August 2006.
5. Nazim H. Madhavji (Editors), Software Evolution and Feedback: Theory and Practice, Wiley-IEEE Computer Society Press, June 2006.
6. Martin Fowler, "UML Distilled: A Brief Guide to the Standard Object Modeling Language, 3rd Edition", Addison-Wesley, 2004.
7. Stephen R. Schach, "Object-Oriented and Classical Software Engineering", 7th Edition, McGraw-Hill, 2006.
8. Ian Sommerville, "Software Engineering", 7th Edition, Addison Wesley, 2004.
9. 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.
Continuation of EEL 5881. This course emphasis more on the term projects and case studies.
This course is designed for advanced graduate students. The course objectives are to provide students with an:
The assignments will include weekly research paper critiques and programming assignments.
Paper review assignments:
Written reviews (soft copies) for selected papers to be presented and discussed in class for the coming week are due on the previous Friday. The file(s) should be sent to email account of the class TA.
For each paper, students should write a review answering each of the following questions:
1. What problems (with prior work or the lack thereof) were addressed or surveyed by the authors?
2. What solutions were proposed or surveyed by the authors?
3. What are the technical strengths and main contributions of the paper's proposed solutions?
4. What are the technical weaknesses of the paper's proposed solutions?
5. What suggestions do you have to improve upon the paper's ideas?
Possible projects will be posted and students are welcome to propose their own projects by turning maximum of 2 pages long project proposal to the instructor on or shortly after the projects are posted.