Search

In June 2015 a group of experts in Software Process Improvement (SPI) and Education from all over the world gathered at the 1st International Workshop on Software Process Education, Training and Professionalism held in connection with 15th International Conference Software Process Improvement and Capability Determination. Discussions with key players in the relevant professional and personal certification fields, as well as experienced educators led to a consensus that it is time for the industry to rise to the new challenges and set out in a manifesto a common vision for educators and trainers together with a set of recommendations to address the challenges faced. At the workshop 14 “experts” from education and industry presented and discussed their “wisdom and experience” of the challenges faced for software process education, training and professionalism, especially with the background of the new modes of learning and teaching in higher education. Based on the presentations, 32 workshop participants brainstormed core values and principles specifically addressing the needs of software process education, training and professionalism. Via affinity analysis and group thinking exercises we identified an initial manifesto, consisting of 10 values and 4 principles. It is expected that this draft manifest will give expression to state-of-the-art knowledge on software process education, training and professionalism. It is based on hundreds of person-years of practice and experience from educators and industry professionals globally. Further work is currently being undertaken to extend and validate this draft manifesto with a view to publishing in its entirety by 2016.

peer-reviewed In work that is ongoing, the authors are examining the extent of software development process terminology drift. Initial findings suggest there is a degree of term confusion, with the mapping of concepts to terms lacking precision in some instances. Ontologies are concerned with identifying the concepts of relevance to a field of endeavour and mapping those concepts to terms such that term confusion is reduced. In this paper, we discuss how ontologies are developed. We also identify various sources of software process terminology. Our work to date indicates that the systematic development of a software development process ontology would be of benefit to the entire software development community. The development of such an ontology would in effect represent a systematic refactoring of the terminology and concepts produced over four decades of software process innovation.

The practice of software development has evolved considerably in recent decades, with new programming technologies, the affordability of hardware, pervasive internet access and mobile computing all contributing to the emergence of new software development processes. The newer process initiatives, which include those which are sometimes referred to as agile or lean methods, have brought with them new terms, which sometimes reflect the introduction of novel concepts. Other times, new terms correspond to long established concepts that have been repackaged. The net position is that we have a proliferation of language and term usage in the software development process domain, a problem which has implications for assessors and assessment frameworks, and for the broader community. In this paper, we explore this problem, finding that it is worthy of further research. Plus, we identify a technique suited to addressing this concern: the establishment of a canonical software process ontological model.

The question is: Can an ISO 9001 certificate lead to software improvement? The answer is: yes — based on 50 BOOTSTRAP maturity assessments carried out in Danish companies.

To define the role of T cells and B cells in resistance to vesicular stomatitis virus (VSV) infection, knockout mice with different specific immune defects on an identical background were infected i.v. and the outcome of infection was compared; in this way a more complete picture of the relative importance of various host defence mechanisms could be obtained. Compared to T and B cell-deficient SCID mice which all succumbed from encephalitis within 5-9 days of infection, T cell-deficient nude mice generally lived longer, but within a period of approximately 1 month after challenge all died. In contrast, B cell-deficient mice were highly susceptible even to low doses of virus and mortality could be prevented by transfer of naive B cells prior to challenge as well as by immune serum given after challenge. Analysis of MHC class I- and class II-deficient mice revealed that CD8+ T cells could exert some antiviral activity, but CD4+ T cells sufficed for survival and were required for optimal resistance. Consistent with this it was found that in nude mice a lethal outcome could be prevented by transfer of CD8-depleted cells from B cell-deficient mice. Thus our results clearly demonstrate that while antibodies are pivotal for survival in the early phase of VSV infection, T cells are required for long-term survival, with CD4+ T cells being more effective in controlling this infection than CD8+ T cells.

This paper describes the standardisation process for B-ISDN from the selection of ATM as the transfer method until the present date where most of the ATM functionality's are specified. It states the current status of the B-ISDN standards and identifies still open questions. Traffic issues are not dealt with in detail since other papers treat this subject specifically. The paper finally addresses the work presently done in ETSI/NA5 and discusses the future work to be done. Emphasis is put on the B-ISDN work done and going on in CCITT SGXVIII and ETSI/NA5.

Oxygen absorption in the light exhibited by spinach chloroplasts is traditionally explained by assuming that oxygen functions as Hill acceptor (Mehler, A.H. (1951) Arch. Biochem. Biophys. 34, 339–351). In this paper it is suggested that the light-driven absorption of oxygen results in the production of superoxide and that this process is catalyzed by a 58 kDa catalase. Superoxide then dismutates to hydrogen peroxide and oxygen. It is further suggested that the production of hydrogen peroxide takes place in the lumin of the thylakoid and that the hydrogen peroxide is used as electron donor for photosynthesis. There will only be little loss of oxidizing equivalents, since the oxygen-evolving complex does not have to reach higher oxidation steps. This will be an advantage for light-limited plants. The use of hydrogen peroxide as electron donor will have the consequence that the production of oxygen is higher on the second flash in a series of flashes than when water is used as electron donor. It is also suggested that hydrogen peroxide can deactivate the higher oxidation steps in the oxygen-evolving complex.