On the Presence of Green and Sustainable Software Engineering in Higher Education Curricula

Nowadays, software is pervasive in our everyday lives. Its sustainability and environmental impact have become major factors to be considered in the development of software systems. Millennials-the newer generation of university students-are particularly keen to learn about and contribute to a more sustainable and green society. The need for training on green and sustainable topics in software engineering has been reflected in a number of recent studies. The goal of this paper is to get a first understanding of what is the current state of teaching sustainability in the software engineering community, what are the motivations behind the current state of teaching, and what can be done to improve it. To this end, we report the findings from a targeted survey of 33 academics on the presence of green and sustainable software engineering in higher education. The major findings from the collected data suggest that sustainability is under-represented in the curricula, while the current focus of teaching is on energy efficiency delivered through a fact-based approach. The reasons vary from lack of awareness, teaching material and suitable technologies, to the high effort required to teach sustainability. Finally, we provide recommendations for educators willing to teach sustainability in software engineering that can help to suit millennial students needs.Comment: The paper will be presented at the 1st International Workshop on Software Engineering Curricula for Millennials (SECM2017

Sustainable software engineering education curricula development

Climate change risk and environmental degradation are the most critical issues of our society. Our technology influenced daily life style involves many software and apps which are used by large society and their use is increasing than ever before. Sustainability is a significant topic for future professionals and more so for Information Technology (IT) professionals and software engineers due to its impact on the society. It is significant to motivate and raise concern among students and faculty members regarding sustainability by including it into Software Engineering curriculum. Key words: Sustainability, Sustainable Software Engineering, Curricula, Software Engineering.publishedVersio

IT Systems Development: An IS Curricula Course that Combines Best Practices of Project Management and Software Engineering

Software Engineering in IS Curricula Software engineering course is taught to higher education students majoring in Computer Science (CS), Computer Engineering (CE), and Software Engineering (SE). Software engineering course is also taught in other disciplines, either as a mandatory or as an elective course, such as Information Systems (IS). IS is a broader field than CS and includes parts of CS. IS fie ld could be described as an interdisplinary field that studies the design and use of information systems in a social context. As noted in IS2002 model curricula (Gorgone et al., 2002) , IS as a fie ld of academic study exists under a variety of at least thirteen (13) different curricula, including Information Systems, Management Information Systems, Computer Information Systems, Information Management, Business Information Systems, Informatics, Information Resources Management, Information Technology, Information Technology Systems, Information Technology Resources Management, Accounting Information Systems, Information Science, and Information and Quantitative Science. The author\u27s early experience was that teaching IS students a software engineering course in the same way as CS students was not successful. This is mainly because IS students have significantly less background in programming than CS students. This experience encouraged him to accommodate topics on project management and SE best practices lab using Rational Suite Enterprise (Rational Suite Enterprise, 2008). This new approach was relevant to IS curricula and with accordance with IS2002.10 project management and practice course guidelines. Hilburn, Bagert, Mengel, & Oexmann (2008) proposed that several computing associations including the Association of Computing Machinery (ACM), the IEEE Computer Society (IEEECS), and the Computer Sciences Accreditation Board (CSAB) have provided encouragement, support, and guidance in developing quality curricula that are viable and dynamic. However, most computing programs still devote little time to software life cycle development, software processes, quality issues, team skills, and other areas of software engineering essentials to effective commercial software development. Hence, new graduates know little about what are best practices in software engineering profession (e.g., practices related to use of software processes, team building, front-end development). Therefore, it is the role of faculty members teaching such courses to redesign and implement curricula that focus on practice of software engineering, and other related issues. This paper is organized as follows: Section 2 presents arguments for the alternative approach. Section 3 presents IS2002.10 course specifications. Section 4 presents IS software engineering body of knowledge. Section 5 presents the project component, Section 6 presents a mapping from IS2002.10 course specification onto the IS software engineering course. Section 7 presents evaluation of the proposed approach. Finally, conclusions are presented in Section 8. Why IT Systems Development Course? We have taught the IT Systems Development course to IS students for seven years, and we believe we hit upon an approach that works. Instead of trying to instruct students in theory of various techniques, we teach them what we believe of as software development. From the management side IS students are expected to deal with non-technical challenges arising from project situations, including understand project domain and requirements, how to be a team player, how to schedule work between team members, and how to cope with time pressures and hard deadlines. As indicated by (Weaver, 2004), students often have limited experience in projects management. They do not appreciate the need for planning and take more time than anticipated to complete tasks. We have developed the creation of a set of guidelines for accommodating topics on project management to help students deal with non-technical issues of software development.

Graduate Curricula in Software Engineering and Software Assurance: Need and Recommendations

In discussions about the development and use of computer systems and software products, the term “professional software engineer” is used repeatedly. In the last two decades there has been significant effort devoted to enhancing and advancing the state of professional software engineering (SwE) – new software engineering processes, methods, tools, and practices; creation of a software engineering body of knowledge [1]; development of a code of ethics and professional conduct [2], and software certification and licensing programs [3] . In 1989 the Software Engineering Institute (SEI) of Carnegie Mellon University published a landmark report on graduate education in software engineering [4]. The guidelines in that report were used by several universities in establishing graduate software engineering degree programs that helped address the problem of improving professional software engineering. Since then, software’s scale, complexity, and criticality have accelerated; yet, until recently, no significant effort has been made to revisit and update the original SEI guidelines. This paper discusses two related efforts to provide guidance about improving professional software engineering through graduate education: a project which produced the Graduate Software Engineering 2009 (GSwE2009): Curriculum Guidelines for Graduate Degree Programs in Software Engineering [5] and a current SEI project which is developing a Master of Software Assurance Reference Curriculum (MSwA2010)

Rooting Formal Methods Within Higher Education Curricula for Computer Science and Software Engineering — A White Paper

This white paper argues that formal methods need to be better rooted in higher education curricula for computer science and software engineering programmes of study. To this end, it advocates improved teaching of formal methods;systematic highlighting of formal methods within existing, ‘classical’ computer science courses; andthe inclusion of a compulsory formal methods course in computer science and software engineering curricula. These recommendations are based on the observations that formal methods are an essential and cost-effective means to increase software quality; howevercomputer science and software engineering programmes typically fail to provide adequate training in formal methods; and thusthere is a lack of computer science graduates who are qualified to apply formal methods in industry. This white paper is the result of a collective effort by authors and participants of the 1st International Workshop on Formal Methods – Fun for Everybody which was held in Bergen, Norway, 2–3 December 2019. As such, it represents insights based on learning and teaching computer science and software engineering (with or without formal methods) at various universities across Europe.</p

HCI-E 2 : HCI Engineering Education

This workshop aims at identifying, examining, structuring and sharing educational resources and approaches to support the process of teaching/learning Human-Computer Interaction (HCI) Engineering. The broadening of the range of available interaction technologies and their applications, many times in safety and mission critical areas, to novel and less understood application domains, brings the question of how to address this ever-changing nature in university curricula usually static. Beyond, as these technologies are taught in diverse curricula (ranging from Human Factors and psychology to hardcore computer science), we are interested in what the best approaches and best practices are to integrate HCI Engineering topics in the curricula of programs in software engineering, computer science, human-computer interaction, psychology, design, etc. The workshop is proposed on behalf of the IFIP Working Groups 2.7/13.4 on User Interface Engineering and 13.1 on Education in HCI and HCI Curricula

Additive manufacturing of rectangular waveguide devices for teaching microwave laboratory

In this paper the outline of using of low-cost additive manufacturing FDM/FFF technology to build waveguide devices is presented. The focus is set in a full design from specifications to final measurements in a microwave teaching laboratory. Final results obtained asses that this experience is an extraordinary opportunity for students to get involved in waveguide technology. In addition, the use of 3D design software enriches the curricula of electronic engineering students.Universidad de Málaga. Campus de Excelencia Internacional Andalucía Tech