|
Article
|
Presenter
|
Date
|
|
Rapid prototyping: Lessons learned. (V. Scott Gordon
& J. Bielman, IEEE Software,
January 1995.)
|
1 (JB) | 9/29 |
|
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.)
|
2 (KJ) | 9/29 |
| Software Risk Management: Principles and Practices. (B. Boehm, IEEE Software, Jan. 1991, p. 32-41.) | 3 (SK) | 10/6 |
| Software Project Risks and their Effect on Outcomes. (Wallace and Keil, Communications of the ACM, 47(4): 68-73.) | 4 (KN) | 10/6 |
| Executable Use Cases: Requirements for a Pervasive Health Care System. (Jorgensen and Bossen, IEEE Software, March 2004, 34-41. ) | 5 (RS) | 10/6 |
| The Art of Requirements Triage. (Davis, IEEE Computer, Mar. 2003, p.42-49.) | 6 (WP) | 10/6 |
| 1. How is Open Source Affecting Software
Development? (D. Spinellis and C. Szyperski, IEEE Software, Jan.
2004, 28-33.)
2. The Many Meanings of Open Source (C. Gacek and B. Arief, IEEE Software, Jan. 2004, 34-49.) |
7 (RC) | 10/13 |
| Mission-Critical Development with Open Source Software: Lessons Learned. (J. S. Norris, IEEE Software, Jan. 2004, 42-49.) | 8 (JC) | 10/13 |
| Using Risk to Balance Agile and Plan-Driven Methods. (B. Boehm and R. Turner, IEEE Computer, June 2003, p. 57-66). | 9 (JL) | 10/13 |
|
Embracing change with extreme programming. (K. Beck,
IEEE Computer, 32(10), October 1999.)
|
10 (VR) | 11/3 |
|
1. Software process in the classroom: The capstone
project experience. (D.A. Umphress, T.D.
Hendrix, and J.H. Cross, IEEE Software, Sept/Oct 2002.) and
2. Real Work, Necessary Friction, Optional Chaos: Challenges in estimating software scope by effort. (P.G. Armour, Communications of the ACM47(6):15-18. |
11 (SR) | 11/3 |
| Best Practices in Code Inspection for Safety-Critical Software. (J.R.de Almeida et al. IEEE Software, May 2003, 56-63. | 12 (RN) | 11/3 |
|
An empirical comparison of seven programming languages.
(Lutz Prechelt, IEEE Computer,
Oct. 2000, p. 23-29)
|
13 (RP) | 11/3 |
|
How to design practical test cases. (T. Yamaura,
IEEE Software, 15(6), November 1998.)
|
14 (MM) | 11/10 |
|
Software Reliability from the Customer View. (Alan
P. Wood, IEEE Computer, August 2003, p. 37-42.)
|
15 (DL) | 11/10 |
|
Regression testing in an industrial environment.
(A.K. Onoma, W-T Tsai, M. Poonawalaand
H. Suganuma, Communications of the
ACM, 41(5), May 1998.)
|
16 (DS) | 11/10 |
|
Legacy information systems: Issues and directions.
(J. Bisbal, D. Lawless, B. Wu and J. Grimson,
IEEE Software, September/October 1999.
|
17 (RB) | 11/10 |
Instructions for Presentation
- Title slide: Give the full bibliographic reference (author, title, journal, vol., no., date, pages), your name, CSC640, Fall2004.
- Introduction: (1 slide) What is the topic (e.g. requirements elicitation) and who is the intended audience (e.g. software developers)?
- Summarize the main points (5-7 slides). You may include graphics 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):
Tips on Formatting Slides and Giving a PresentationPractice giving the talk 2 or 3 times to make sure that it is 15 +/- 1 minutes. You will be stopped if you run over! Turn in a copy of the .ppt file containing your presentation. You will be given instructions in class on copying your slides into the class folder. Bring a printed copy of the slides (Handouts - 6 per page) to give to the instructor at the beginning of your talk.
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: