Authors: Eva Kern, Matthias Giesselmann, Patrick Lang, Markus Dick, Stefan Naumann, Timo Johann


Abstract:
“Sustainable Software Engineering is the art of defining and developing software products in a way so that the negative and positive impacts on sustainability that result and/or are expected to result from the software product over its whole lifecycle are continuously assessed, documented, and optimized.” [1]
Based on that definition it is required to pay attention to the whole lifecycle of a software product from beginning on, starting with the requirements review. Since many different processes, products and services are involved in this lifecycle, which have impacts on sustainable development, they must be considered in order to figure out if a software product and even its engineering process is green or not.
The conceptual reference model shown in our multi-media presentation supports sustainable production and usage of software. It includes a lifecycle of software products, sustainability criteria and metrics for software products, procedure models as well as recommendations for actions and tools for purchasers, developers, administrators, and users. In that way the different user roles are addressed.

The model shows, that sustainability aspects of Software must be taken into account as early as possible, e.g. within the requirement engineering phase.

Submission download:
Multimedia poster in Flash format: GREENSOFT Poster

Reviews

Review 1

  • TITLE: Green Requirements Engineering with the GREENSOFT Model Taking the whole Lifecycle of Software into Account
  • AUTHORS:
Reviewers' expertise from 1 (low) to 5 (high): 3

  • SCORES 1 (Very Bad) 2 (More or less OK) 3 (Very Good)
Adequacy for RE4SuSy: 3
Originality of the content: 3
Significance of the work: 3
Soundness and accuracy of the technical content: 2
Style and clarity of the paper: 1
OVERALL RECOMMENDATION (Strong Reject - Reject - Conditional Accept - Accept - Strong Accept): Accept

  • REVIEW:
The poster seems to present an end-to-end development for sustainable software development. Most of the information is contained in the interactive poster, which is however not self-explanatory. It would be useful to provide some more detailed explanation in the poster paper, so that the poster can be understood without a poster presenter.

Review 2

  • TITLE: Green Requirements Engineering with the GREENSOFT Model Taking the whole Lifecycle of Software into Account
  • AUTHORS: Eva Kern, Matthias Giesselmann, Patrick Lang, Markus Dick, Stefan Naumann, Timo Johann
Reviewers' expertise from 1 (low) to 5 (high): 4

  • SCORES 1 (Very Bad) 2 (More or less OK) 3 (Very Good)
Adequacy for RE4SuSy: 2
Originality of the content: 2
Significance of the work: 2
Soundness and accuracy of the technical content: 2
Style and clarity of the paper: 1
OVERALL RECOMMENDATION (Strong Reject - Reject - Conditional Accept - Accept - Strong Accept): Conditional Accept

  • REVIEW:
1. Software is a product that can be multiplied with almost no effort, so it is n times more often used than produced, for very high n. I would therefore expect that the use phase has n times higher relevance for sustainability than the production phase, with very high n. The authors should give reasons why they think it is important that "even its engineerig process is green" and why it is important to take "the whole life cycle" into account" (title). If they address issues of engineering that are effective via the use phase (which would make sense), this view differs from the usual LCA view which the authors refer to. If so, this should be made explicit.
2. The 1-pager as it is contains too many black boxes to be judged. The quality depends on the content of the cited literature which the reader of this paper does not see while reading. The paper has almost no argumentation structure, it is basically a collection of references. It would possibly need more space show the argumentation structure the authors have in mind.
3. Self-quotations are not necessary, in particular not as a first sentence. If you refer to your own work (which can be perfectly ok), you don't have to use quotes.
4. English grammar and style should be checked by a native speaker who is a good writer.

Review 3

  • TITLE: Green Requirements Engineering with the GREENSOFT Model Taking the whole Lifecycle of Software into Account
  • AUTHORS: Eva Kern, Matthias Giesselmann, Patrick Lang, Markus Dick, Stefan Naumann, Timo Johann
Reviewers' expertise from 1 (low) to 5 (high):
General Requirements Engineering - 5,
RE for sustainability specifically - 1

  • SCORES
Adequacy for RE4SuSy: 2
Originality of the content: 2
Significance of the work: 2
Soundness and accuracy of the technical content: 2
Style and clarity of the paper: 2
OVERALL RECOMMENDATION: Conditional Accept
  • REVIEW:
(Note - I was unable to view the "multi-media presentation" on either my work or home PC.) The final sentence is quite a weak way to end the paper - have the authors forgotten that this paper has been submitted to a requirements engineering workshop? Of course sustainability impacts all phases of the software lifecycle, but I would expect the RE aspects to be emphasised, not just cited as an example. It seems like an odd way to conclude the paper. The paper seems rather superficial, but there may be some good work behind it. A little informal in style in places (for example "in order to figure out...", use of "e.g.") and some suspect grammar. I think that the authors should rewrite the paper to emphasise the impact of requirements engineering specifically on the sustainability of a software programme.

Discussion

please add your comments here and leave your name and email.

I have put the Flash format on an extra webpage to better display it - now everybody should be able to view it.
Birgit (penzenst@in.tum.de)

Thank you for your comments. In case of being accepted we will improve our flash model and the description.
Stefan (s.naumann@umwelt-campus.de)