1. EEL 6883 Exam I Review Spring 2007

2.  The exam I will cover  Lectures 1-12  Software Usability paper from Chapter 4, Vol. 1  Open book, open notes exam  The exam will be sent to the class email address by no later than March 7 th, 7:30pm  The students are expected to send the exam paper back to the instructor via email (turgut@eecs.ucf.edu) by no later than March 11, midnight. turgut@eecs.ucf.edu  The exam will be created using MS Word and the students are required to  include the answers in the same file, add pages and figures as necessary  Please do not send separate files, include everything in one file Exam Coverage

3. Types of Questions  One UML question  Given a problem statement, draw oUse-cases oClass diagram oSequence diagram According to the UML notations  Implement one or two modules in a chosen OO programming language  Feel free to use any case tool to draw the figures and use any OO programming language  Deliverables:  Diagrams embedded into MS Word file  Executable source code and a sample script file included in the MS Word file

4. Types of Questions  Three to four questions will come from the textbook  Mix of open-ended and specific questions on a specific paper  It may require you to do some research  Make sure to include your references (conference/journal papers, book chapters, web links, discussions with other software engineers, etc)

5. Example Questions  What are the expected/recommended skills and knowledge for software engineers in today’s world according to your own opinion?  Feel free to give specifics and examples from your professional experience if applicable.  You can also refer to the paper titled “Recommended skills and knowledge for software engineers” by Tockey, in Vol. 1, Ch 1. pp. 47- 53 or other references.  Make sure to include references used

6. Example Questions  Please answer the following questions according to the paper titled “Software Requirements” by Sawyer in Vol. 1. Ch. 3, pp. 113-123.  The author states that during elicitation workshops, one must be careful not to fall into the “groupthink” phenomena. Explain in your own words, what do you think the author means by this statement?  What do “testable requirements” mean in this context? Is it important to ensure the requirements are testable? If so, why? If not, why? Explain your reasoning briefly.  Who should be in charge of writing software requirements: software engineers, systems engineers, or both? Explain your answer briefly. Feel free to give examples from your professional experience if applicable.

7. Example Questions  Please answer the following questions according to the paper titled “Software Design: An introduction” by Budgen in Vol. 1. Ch. 4, pp. 209-220.  What does the “opportunistic design” means according to the author? What does it mean according to you? Explain the reasoning behind if you disagree with the author.  What does it mean “we do not teach how to design, but we teach methods of design”?  What does “invisibility of software” means according to the article? Explain briefly and give example if possible.