1 / 4

Software Engineering II (Spring 2007)

Software Engineering II (Spring 2007). Instructor: Dr. Damla Turgut Office: 450 ENGR 1 Bldg Office Phone: (407) 823-6171 Email: turgut@eecs.ucf.edu Web: http://www.eecs.ucf.edu/~turgut Class Time: Mondays and Wednesdays 7:30 PM – 8:45 PM

terence
Download Presentation

Software Engineering II (Spring 2007)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Engineering II(Spring 2007) Instructor:Dr. Damla Turgut Office: 450 ENGR 1 Bldg Office Phone: (407) 823-6171 Email:turgut@eecs.ucf.edu Web:http://www.eecs.ucf.edu/~turgut Class Time: Mondays and Wednesdays 7:30 PM – 8:45 PM Office Hours: Mondays and Wednesdays 5:45 PM – 7:15 PM Prerequisites: EEL 5881 or equivalent and/or instructor consent Textbooks: • Software Engineering, Volume 1: The Development Process, Ed. by Richard H. Thayer and Mark J. Christensen, 3rd Edition, IEEE Computer Society Press, 2005. • Software Engineering, Volume 2: The Supporting Processes, Ed. by Richard H. Thayer and Mark J. Christensen, 3rd Edition, IEEE Computer Society Press, 2005.

  2. Software Engineering II(Spring 2007) Reference Books: • Linda M. Laird and M. Carol Brennan, Software Measurement and Estimation: A Practical Approach, Wiley-IEEE Computer Society Press, July 2006. • 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. • Jeff Tian, Software Quality Engineering: Testing, Quality Assurance, andQuantifiable Improvement, Wiley-IEEE Computer Society Press, February 2005. • Donald J. Reifer (Editor), Software Management, 7th Edition, Wiley-IEEE Computer Society Press, August 2006. • Nazim H. Madhavji (Editors), Software Evolution and Feedback: Theory and Practice, Wiley-IEEE Computer Society Press, June 2006. • Martin Fowler, UML Distilled: A Brief Guide to the Standard Object Modeling Language, 3rd Edition, Addison-Wesley, 2004. • Stephen R. Schach, Object-Oriented and Classical Software Engineering, 7th Edition, McGraw-Hill, 2006. • Ian Sommerville, Software Engineering, 7th Edition, Addison Wesley, 2004. • 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.

  3. Software Engineering II(Spring 2007) Course Objectives: The course is designed for advanced level graduate students. The course objectives are to provide the students with an: • understanding of current current software engineering theory and practice through research publications • opportunity to work in a group environment on a project • experience on reading and writing research papers Course Description: Continuation of EEL 5881. This course emphasis more on the term projects and case studies. Project: Students will work in teams of two to do an in-depth study of some subject generally relevant and appropriate to the theme of this course. At the end of the semester, each team will submit a professional-quality conference-style paper on the selected topic Grading Scheme: • Individual or group project (max. 2 students) => 30% • Presentations => 25% • Assignments => 15% • Exam 1 => 15% • Exam 2 => 15%

  4. Software Engineering II(Spring 2007) Paper Reviews: • Written reviews (soft copies) for each paper 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 instructor • 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?

More Related