|
Article
|
Presenter
|
Date
|
|
Embracing change with extreme programming. (K. Beck,
IEEE
Computer, 32(10), October 1999.)
|
1 MS
|
Oct. 1
|
|
Rapid prototyping: Lessons learned. (V. Scott Gordon
& J. Bielman, IEEE Software,
January 1995.)
|
2 CP
|
Oct. 1
|
|
Trade-offs between Productivity and Quality in Selecting
Software Development Practices. (A. MacCormack,
C.F. Kemerer, M. Cusumano,
B. Crandall, IEEE Software, 20(5), September/October 2003, p. 78-85.)
|
3 CC
|
Oct. 8
|
|
UMLoquent expression of AWACS Software Design (A.
Bell and R. Schmidt, CACM, October 1999)
|
4 AW
|
Oct. 8
|
|
Formal methods: Promises and problems. (Luqi
and J. Goguen, IEEE Software, 14(1),
January 1997.)
|
5 AI
|
Oct. 15
|
|
How perspective-based reading can improve requirements
inspections. (F. Shull, I. Rus, and V. Basili,
IEEE
Computer, July 2000, p. 73-79.)
|
6 SS
|
Oct. 15
|
|
Making sense of measurement for small organisations.
(K. Kautz, IEEE Software, March/April
1999.)
|
7 SA
|
Oct. 22
|
|
Nine management guidelines for better cost estimating.
(A. Lederer and J. Pasad,
CACM,
35(2), February 1992.)
|
8 JH
|
Oct. 22
|
|
Legacy information systems: Issues and directions.
(J. Bisbal, D. Lawless, B. Wu and J. Grimson,
IEEE
Software, September/October 1999.)
|
9 JC
|
Oct. 29
|
|
An empirical comparison of seven programming languages.
(Lutz Prechelt, IEEE Computer, Oct.
2000, p. 23-29)
|
10 BL
|
Oct. 29
|
|
How to design practical test cases. (T. Yamaura,
IEEE
Software, 15(6), November 1998.)
|
11 AC
|
Nov. 5
|
|
Software Reliability from the Customer View. (Alan
P. Wood, IEEE Computer, August 2003, p. 37-42.)
|
12 KV
|
Nov. 5
|
|
Regression testing in an industrial environment.
(A.K. Onoma, W-T Tsai, M. Poonawala
and H. Suganuma, CACM, 41(5), May
1998.)
|
13
|
Nov. 12
|
|
Software process in the classroom: The capstone
project experience. (D.A. Umphress, T.D.
Hendrix, and J.H. Cross, IEEE Software, Sept/Oct 2002.)
|
14
|
Nov. 12
|
| The Art of Requirements Triage. (Davis, IEEE Computer, Mar. 2003, p.42-49.) | 15 |
Instructions for Presentation
·Preparation
oRead
the assigned paper.You
do not need to consult other sources of information.
oPrepare
a 15-minute Power Point presentation summarizing the paper.Use
the following structure:
§Title
slide: Give the full
bibliographic reference to the paper, your name, CSC640, Fall
2003.
§Slide 2: Describe the topic of the article (ex. Requirements Elicitation, Unit Testing) and the type(s) of argument used in the article. Examples of types of argument in articles:
·Lessons
learned from one or more case studies of SWE Projects
·Conclusions
based on quantitative analysis of data
·Conclusions based on a reasoned argument given in the paper
·Other?
If the article does not fit the above, then describe its type
§Outline slide: Outline your talk.
§Slides in the middle: Approximately 5-10 slides summarizing the article.
§Evaluation: At least 1 slide giving your evaluation of the paper. Some questions to consider are:
·Is the paper well-written and well-organized?
·Are the claims of the paper adequately supported?
·Does the list of references offer pointers to related work that look helpful?
·What are the strengths and weaknesses of the paper?
·Evaluation: Would you recommend this paper? To whom and why?
oSee
my tips below on how to format your slides.
oPractice giving the talk 2 or 3 times to make sure that it is under 15 minutes. You will not be allowed more than 15 minutes to make your point!
oCopy your Power Point presentation into the folder assigned to you by the instructor before class begins. You will use the computer in the classroom to run your slide show.
oPrint
out a paper copy of the slides (4 to a page) to give the instructor at
the beginning of your talk.
oReturn the paper copy of the article to the instructor at the beginning of your talk.
·Tips
on Making Slides:The
slides should not contain every word of your presentation! Instead,
they should help the audience to organize the material that you present
verbally. Also, you may use diagrams or pictures. Here are some general
tips on using slides:
·no
more than 10 lines per slide
·no
more than 7 words per line
·text
must readable from back of room
·consistent
use of color, format, and other visual features
·check
spelling
·do
not read slides word for word
·do
not stand silently expecting the audience to read the slides
·spend
about 2 minutes per slide
·do
not block the audience's view of the slides.
·Use
of notes: Ideally, a business or conference speaker should use notes
sparingly. However, because you may not have had much experience
with spoken presentations, or if English is not your first language, you
may use detailed written notes. If you choose to use written notes,
please follow these guidelines:
·Do
not use long sentences!
·Look
up to establish eye contact fairly often.
·Vary the sound of your speaking voice (tone, speed, accent) to maintain interest.
·Leading
discussion: After your talk, you will lead a short discussion.
Be prepared to ask a few stimulating questions in case no one in the audience
raises any questions.