Article Title Author Publication Date

1
ltArticle TitlegtltAuthorgtltPublication Dategt

• EEL6887 Software Engineering
• ltPresentergt
• ltPresentation Dategt

2
Reference Sources

• List the primary source for paper being
  presented.
• Identify and acquire at least two other
  supporting articles (preferably conference or
  journal articles), of the same or more recent
  vintage. These should be submitted in electronic
  format for posting on the course web site. These
  articles could be references listed in the
  primary source, if they provide additional detail
  of interest. URLs to downloadable public images
  of these articles would be acceptable.

3
Body

• Summarize the most significant and important
  content of the article. Try to paraphrase
  material, but without changing its meaning or
  giving your own "spin" that is, be factual and
  objective. Enclose verbatim text in quotes.
• Use diagrams where possible to summarize and
  abstract essential content.
• Your slides should be self-contained and
  understandable by someone who did not hear your
  presentation. In other words, do not produce a
  set of slides that have no value without the
  speaker to explain them.

4
Summary

• Summarize the main points of the article you feel
  were most significant and relevant to this
  course. These are points you think the audience
  should remember above all other information in
  the article.

5
Conclusions

• Discuss or summarize the software tools that were
  mentioned or implied by the article.
  Specifically tools that relate to software
  development or software project support.
• Classify tools mentioned or discussed in the
  article according to how they would be used in
  the software development cycle. Discuss what
  type of user would use these tools project mgr,
  SQA mgr, software designer, software tester,
  programmer, etc.
• Discuss, to the extent possible, how tools or
  techniques addressed in your article might apply
  to CMM Level 2 (or some higher level).