Pattern Paper Writing: Some Specifics
Upcoming SlideShare
Loading in...5
×
 

Pattern Paper Writing: Some Specifics

on

  • 521 views

 

Statistics

Views

Total Views
521
Views on SlideShare
521
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Pattern Paper Writing: Some Specifics Pattern Paper Writing: Some Specifics Presentation Transcript

  • Pattern Paper Writing: Some specifics Jaap Kabbedijk, MSc. Utrecht University June 4, 2012
  • At a glance• Deadline: 14/06 - 17:00h• Email the PDF to me and your first and second reviewer• Email addresses will be made available in time on the website• Write your paper in LNCS style• Write your paper in LaTeX• Paper probably between 12 and 20 pages• Best 3 papers may be transformed to a conference / journal submission• Please check the LaTeX crash course
  • Make sure these elements are in your paper• Introduction• Case Study Description• Domain, Problem, Forces• Pattern Description• Diagram(s)• Advantages, Liabilities• Variability Consequences• Conclusion• References
  • Pay specific attention to• To improve the credibility of your case study be sure to list the following case company characteristics • Programming language • Number of customers • Role of the interviewee • Architecture type • Lines of code • SaaS vs. Non-SaaS • Product vs. Custom software• Be sure that the solution you propose, really solves the problem and forces you identified• Have a clear focus. ONE clear problem and ONE clear solution
  • Consequence categorization• Database related• Development efficiency• Infrastructure related• Client related consequences• Security• Performance• Maintainability• Testability• Variability / Flexibility• Reusability• Paradigm shift• Data consistency• Control
  • Next Week: Proto-pattern Brainstorm• Bring your progress till now on paper twice• Prepare things you are struggling with• Give feedback to the people you have to review• Several feedback rounds given and received• A bit like speed dating ;)
  • Good luck!Good Luck :)