Writing a Minipaper

1
Writing a Mini-paper
2
The Mini-Paper

• What is it?
• A discussion based on computing literature
• Relevant to your project
• Similar to an article published in a journal
• A demonstration of your ability to
• Understand academic literature
• Use references
• Present a coherent argument

3
Writing the Mini-Paper

• Identify some relevant sources
• Identify issues that are worth discussing
• Define a title to provide focus
• Identify at least two viewpoints
• Draft a conclusion
• Define the overall structure of the paper
• Write the paper
• Write how the ideas can be used in the project
• Write the conclusion and abstract

4
Do Software Developers Need The Personal Software
Process?

• Software developers want to improve quality.
• The paper considers
• If PSP is consistent with good SE practice
• If it is used in practice
• If the experimental evidence justifies the claims
• Potential problems with the PSP.
• The paper concludes that
• the PSP philosophy is relevant for developers,
  and can improve software quality.
• the cost of PSP is too high for it to be widely
  adopted.

5
Diary of a minipaper
6
Step 1 Review of Material

• Most Relevant Material
• Introduction to PSP Book (Humphrey)
• 2 key papers by Humphrey others
• 1 paper on experiment
• 1 paper using PSP to compare Java to C
• (might have to twist this to make it relevant -
  maybe use it as evidence that other factors can
  affect PSP results)
• Demarco's review of A Discipline for Software
  Engineers
• ( by chance the following article suggests that
  Yourdon may support Humphrey's ideas in a book
  search Amazon)
• 1 article suggesting that PSP favours
  individuality.

7
Step 1 Review of Material

• Possible context avoid over diversity
• Confessions of a QA addict
• standards, costs, creativity QMS
• ISO9000 book
• supports constant review of processes
• DoD Guidelines
• Paper on why good projects fail
• May identify other factors which affect software
  quality
• Brooks Mythical Man-Month Van Vliet SE text
• primitive nature of Humphrey's models
• Managing Software Development Projects
• discipline commitment which are part of PSP

8
Step 2 What to include?

• A statement of claims
• In Para. 1 of Using A Defined
• Alternative approaches
• 'good practice' paper
• Evaluation of experimental evidence
• Subjects are students but from industry
• One paper looks at use in practice

9
Possible Issues

• Experimental support for improved quality
• Consistent with good practice (theory)
• Costs, anecdotal problems, creativity constraints
• What is quality?
• Process vs. Product
• Must be brief, but it's probably a good
  introduction.
• Other Issues
• Professional issues - BCS upgrading
  responsibility
• Relationship with the Capability Maturity Model
• Lots of material - How to organise it?

10
Step 3 The First Plan
Note originally the mini-paper was 4000
words. Ive cut down my example paper and it
shows.
11
Step 4 The First Draft

• Mark important sections in your references
• Post-it Notes
• Highlighter pen
• Conclusion first
• Only include material relevant to the conclusion
• Change conclusion if necessary
• Group related references
• link different references relevant to logical
  idea
• cut-out quotes - but don't lose author
• jot down links on your plan or spider diagram

12
Step 4 The First Draft

• Write sections
• Ensure each section has a clear theme
• Ensure sections are logically ordered
• Ensure clear flow from one paragraph to the next
• Weave quotes ideas from your references
  together
• Edit ruthlessly
• If it's not relevant, cut it
• If it's relevant, simplify it
• Don't use terms you can't explain, at least in
  outline.

13
Step 5 Review Revision

• Read after a few days - fresh perspective
• Check important things
• Does each section have a purpose?
• Are the sections logically ordered?
• Does each section follow on from its predecessor?
• Does the conclusion make a statement?
• Does the body support the conclusion?
• Is there sufficient evidence?
• Are significant counter-arguments missing?

14
Step 5 Review Revision

• Check the English
• Is the tone right?
• should have, not should of
• it's means "it is" it does not mean its
• Spell-check the work
• Don't waste your share of the reviewer's time
• Use supervisor to review
• Agree a reasonable return date
• Discuss unclear points with the reviewer
• Revise re-read until satisfied

15
Additional Advice

• Keep all references
• For papers or web sites that you have read.
• I wasted time finding sites and papers again.
• Look for guidelines
• If reviewing something, e.g. a GUI, seek
  guidelines on doing a review and apply them.
• If you find contradictory guidelines, apply all
  and discuss differences.
• Use citation searches
• If you find an old paper, look for later papers
  by the same person in the same area and see if
  their views have changed, and why.

16
Marking Scheme 1

• Mini-Paper Content 65
• 0-10 Information Integration
• Use of references
• 0-10 Research Skills
• selection of literature supporting evidence
• 0-25 Understanding
• understanding of complex area
• 0-20 Logical analysis
• relating evidence to conclusion

17
Marking Scheme 2

• Mini-Paper Presentation 25
• 0-5 structure
• abstract, introduction, structured
  body,conclusion
• 0-9 style
• competent language, technical style
• 0-7 clarity
• explanation of complex issues
• 0-4 layout
• layout reflects structure, diagrams support
  points in text
• Relation to project 10
• 0-10 implications for project

18
Guidance on minipaper writing

• Mini-paper template
• Checklist
• Help file
• Mark scheme
• Harvard referencing convention
• Project Handbook
• Mini-paper review session
• With your second reader other students