Newsletter

From RESG

Jump to: navigation, search

Requirements Quarterly


The quarterly newsletter of the BCS Requirements Engineering Specialist Group edited by Simon Hutton.


The most recent issue is Requirements Quarterly 53, January 2010. Please feel free to comment on any of the articles in this issue using the comments section.


If you'd like to contribute to Requirements Quarterly, visit the How to Contribute section.

A copy of Tom Gilb’s book ‘Competitive Engineering’ will be awarded for the best contribution to RQ 54!


RQ Archive

Pages from RQ49.
RQ – Issue 1.7, October 1994
  • Requirements Quarterly 53 (pdf) | January 2010 [Comments]
  • Requirements Quarterly 52 (pdf) | October 2009 [Comments]
  • Requirements Quarterly 51 (pdf) | April 2009 [Comments]
  • Requirements Quarterly 50 (pdf) | January 2009 [Comments]
  • Requirements Quarterly 49 (pdf) | October 2008
  • Requirements Quarterly 48 (pdf) | June 2008
  • Requirements Quarterly 47 (pdf) | March 2008
  • Requirements Quarterly 46 (pdf) | December 2007
  • Requirements Quarterly 45 (pdf) | September 2007
  • Requirements Quarterly 44 (pdf) | June 2007
  • Requirements Quarterly 43 (pdf) | March 2007
  • Requirements Quarterly 42 (pdf) | December 2006
  • Requirements Quarterly 41 (pdf) | September 2006
  • Requirements Quarterly 40 (pdf) | June 2006
  • Requirements Quarterly 39 (pdf) | March 2006
  • Requirements Quarterly 38 (pdf) | December 2005
  • Requirements Quarterly 37 (pdf) | September 2005
  • Requirements Quarterly 36 (pdf) | June 2005
  • Requirenautics Quarterly 35 (pdf) | March 2005
  • Requirenautics Quarterly 34 (pdf) | December 2004
  • Requirenautics Quarterly 33 (pdf) | September 2004
  • Requirenautics Quarterly 32 (pdf) | June 2004
  • Requirenautics Quarterly 31 (pdf) | March 2004
  • Requirenautics Quarterly 30 (pdf) | December 2003
  • Requirenautics Quarterly 29 (pdf) | August 2003
  • Requirenautics Quarterly 28 (pdf) | February 2003
  • Requirenautics Quarterly 27 (pdf) | November 2002
  • Requirenautics Quarterly 26 (pdf) | May 2002
  • Requirenautics Quarterly 25 (pdf) | January 2002
  • Requirenautics Quarterly 24 (pdf) | July 2001
  • Requirenautics Quarterly 23 (pdf) | March 2001
  • Requirenautics Quarterly 22 (pdf) | October 2000
  • Requirenautics Quarterly 21 (pdf) | July 2000
  • Requirenautics Quarterly 20 (pdf) | March 2000
  • Requirenautics Quarterly 19 (pdf) | December 1999
  • Requirenautics Quarterly 18 (pdf) | August 1999
  • Requirenautics Quarterly 17 (pdf) | June 1999 (Links may no longer be current.)
  • Requirenautics Quarterly 16 (pdf) | February 1999 (Links may no longer be current.)
  • Requirenautics Quarterly 15 (pdf) | October 1998
  • Requirenautics Quarterly 14 (pdf) | April 1998
  • Requirenautics Quarterly 13 (pdf) | January 1998
  • Requirenautics Quarterly 12 (pdf) | October 1997
  • Requirenautics Quarterly 11 (pdf) | July 1997
  • Requirenautics Quarterly 10 (pdf) | April 1997
  • Requirenautics Quarterly 09 (pdf) | January 1997
  • Requirenautics Quarterly 08 (pdf) | October 1996 (Links may no longer be current.)
  • Requirenautics Quarterly 07 (pdf) | July 1996 (Links may no longer be current.)
  • Requirenautics Quarterly 06 (pdf) | April 1996 (Links may no longer be current.)
  • Requirenautics Quarterly 05 (pdf) | January 1996 (Links may no longer be current.)
  • Requirenautics Quarterly 04 (pdf) | October 1995 (Links may no longer be current.)
  • Requirenautics Quarterly 03 (pdf) | April 1995 (Links may no longer be current.)
  • Requirenautics Quarterly 02 (pdf) | January 1995
  • Requirenautics Quarterly 01 (pdf) | October 1994



Notes for Contributors

Please send articles to Simon Hutton, our RQ editor.

Submissions must be in electronic form and preferably in plain ASCII text. RQ specifically welcomes the following kinds of contributions:



Experience reports

We are very keen to print articles from RE practitioners that describe industrial or commercial experience. Examples might include descriptions of practical experience with a tool, method, process model, research methodology, or even just reflections on recent adventures in requirements engineering. Please include enough background for readers to understand the context in which the method, tool or whatever was used. In particular, please identify the domain, approximate size and duration of the project(s), and the type of customer and developer organisations. If any of the personnel, projects, or organisations involved need remain anonymous, please make this clear in the article.



Short descriptions of work in progress

While we do not intend to print refereed papers, we are keen to encourage short articles describing work in progress, especially where the work is not yet mature enough for publication elsewhere. Articles should be informal, and should emphasise the background and rationale to the work, rather than the technical details. Please also make the current state of progress clear, and feel free to invite comment from the readership.



Lab overviews

Summaries of work ongoing at research laboratories, whether academia or industry. These should be no more than two pages long, and if possible should include selected references for further information.



Opinions

RQ welcomes opinion statements from readers. These should be one page long, and should present a more or less controversial point of view, with informally-presented supporting argumentation. A long list of references is not required, but one or two links to interesting websites or articles that support the opinion would be welcome.



News items and events for the diary

Please include an address for full information (preferably a web page), as we can only print a quick summary for most events.



Book reviews

We welcome reviews of any books that may be of interest to RESG members. There is no length restriction, but book reviews should be reasonably concise. Please summarise the scope of the book being reviewed, but try not to reproduce the contents in detail. Please also include full publication details of the book, as well as your own name and address.



Meetings summaries

One of the committee members usually writes up a summary of each RESG meeting for RQ, but we'd be delighted to have volunteers to do this. We'll even consider printing multiple reviews of a meeting, if we get more than one viewpoint.



Conference/workshop reviews

As with book reviews, we will accept reviews of any conference or workshop of interest to RESG members. Length should be proportional to the relevance of the conference: we'd like to print short summaries of conferences of marginal interest, and detailed reviews of the main Requirements Engineering events. Reviews need not be balanced: cover those aspects of the event that most interested you.



Calls for papers

For symposia that are of direct relevance to the RESG members, we like to print a full call for papers (space permitting); otherwise we put a summary in the list of calls, and details of where to find the full call. Please supply a web address if possible.



Adverts

Although RQ is not a commercial venture, we will consider advertisements if they contain information about a product or service of direct relevance to RESG's mission statement. In addition, corporate members are entitled to a limited amount of free advertising space in each issue.



Letters

Please feel free to take issue with anything that appears in RQ, or with anything said or implied at RESG events. For that matter, write in with complaints about government policy if you feel so inclined.

Views