CSC640 Fall 2005 Assignment

CSC 640, Fall 2005, UNCG
Critical Review of Paper (In-class Presentation) - See Instructions Below List of Articles

Article

Presenter

Date

The Art of Requirements Triage. (Davis, IEEE Computer, Mar. 2003, p.42-49.) 1 9/28

Legacy information systems: Issues and directions. (J. Bisbal, D. Lawless, B. Wu and J. Grimson,IEEE Software, September/October 1999.)

2 9/28

Mission-Critical Development with Open Source Software: Lessons Learned. (J. S. Norris, IEEE Software, Jan. 2004, 42-49.) 3 10/5

The Many Meanings of Open Source (C. Gacek and B. Arief, IEEE Software, Jan. 2004, 34-49.)
4 10/5

An empirical comparison of seven programming languages. (Lutz Prechelt, IEEE Computer, Oct. 2000, p. 23-29)
5 10/19

Embracing change with extreme programming. (K. Beck,IEEE Computer, 32(10), October 1999.)

6 10/19

Best Practices in Code Inspection for Safety-Critical Software. (J.R.de Almeida et al. IEEE Software, May 2003, 56-63. 7 11/9

How to design practical test cases. (T. Yamaura,IEEE Software, 15(6), November 1998.)
8 11/09

Software Reliability from the Customer View. (Alan P. Wood, IEEE Computer, August 2003, p. 37-42.) 9 11/16

Regression testing in an industrial environment. (A.K. Onoma, W-T Tsai, M. Poonawalaand H. Suganuma, Communications of the ACM, 41(5), May 1998.)

10 11/16

Article	Presenter	Date
The Art of Requirements Triage. (Davis, IEEE Computer, Mar. 2003, p.42-49.)	1	9/28
Legacy information systems: Issues and directions. (J. Bisbal, D. Lawless, B. Wu and J. Grimson,IEEE Software, September/October 1999.)	2	9/28
Mission-Critical Development with Open Source Software: Lessons Learned. (J. S. Norris, IEEE Software, Jan. 2004, 42-49.)	3	10/5
The Many Meanings of Open Source (C. Gacek and B. Arief, IEEE Software, Jan. 2004, 34-49.)	4	10/5
An empirical comparison of seven programming languages. (Lutz Prechelt, IEEE Computer, Oct. 2000, p. 23-29)	5	10/19
Embracing change with extreme programming. (K. Beck,IEEE Computer, 32(10), October 1999.)	6	10/19
Best Practices in Code Inspection for Safety-Critical Software. (J.R.de Almeida et al. IEEE Software, May 2003, 56-63.	7	11/9
How to design practical test cases. (T. Yamaura,IEEE Software, 15(6), November 1998.)	8	11/09
Software Reliability from the Customer View. (Alan P. Wood, IEEE Computer, August 2003, p. 37-42.)	9	11/16
Regression testing in an industrial environment. (A.K. Onoma, W-T Tsai, M. Poonawalaand H. Suganuma, Communications of the ACM, 41(5), May 1998.)	10	11/16

Instructions for Presentation

Preparation

Download your assigned paper from our shared folder: ...\csc640-f05\readings. (Look for the first author's last name.)
Read the assigned paper. Do not consult other sources of information on the subject. This should be entirely your own work.
Prepare a 25-30 minute Power Point presentation about the paper. Use the following organization for your talk:

Title slide: Give the full bibliographic reference (author, title, journal, vol., no., date, pages), your name, CSC640, Fall2005.

Introduction: (1 slide) What is the topic (e.g. requirements elicitation) and who is the intended audience (e.g. software developers)?

Summarize the content (10-15 slides). You may include figures and tables from the article.

Summarize the methods (case studies, personal experience, opinion, quantitative analysis, rational argument, other?) used by the author to support his claims (1 slide)

Evaluation (1 slide):

Is the paper well-written and organized?
Are the claims adequately supported?
Are the references to other research adequate?
What are the strengths and weaknesses of the paper?

Would you recommend this paper? To whom and for what purpose?

The slides should not contain every word that you say! Instead, they should help the audience to organize and visualize the material that you present verbally. You may include outlines, diagrams, graphs, or pictures. Here are some general tips on using slides: