Integrating Sensor-Network Research and Development into a Software Engineering Curriculum

The emergence of a sensor-networked world produces a clear and urgent need for well-planned, safe and secure software engineering. It is the role of universities to prepare graduates with the knowledge and experience to enter the work-force with a clear understanding of software design and its application to the future safety of computing. The snBench (Sensor Network WorkBench) project aims to provide support to the programming and deployment of Sensor Network Applications, enabling shared sensor embedded spaces to be easily tasked with various sensory applications by different users for simultaneous execution. In this report we discus our experience using the snBench research project as the foundation for semester-long project in a graduate level software engineering class at Boston University (CS511)

Professionalism In The First Year Of A Software Engineering Curriculum

Professionalism is an important part of any subject of study where graduates subsequently move into a professional career following their degree course. Most professional bodies therefore require accredited degree programmes to include this topic in the curriculum. The British Computer Society gives guidelines to institutions in the UK. These guidelines have been followed in the construction of the current Software Engineering Curriculum in the Department Of computer Science at the University of Sheffield. However it is unclear how effective the current form of presentation is. This report seeks to investigate this and look to possible ways of improving the presentation, particularly in the first year. I conclude that the most important factor in teaching professionalism; is the professionalism of the teachers. Students seem to learn these skills best by example, and therefore the greatest improvements are likely to be found by implementing common standards for teaching practice across the syllabus

Integrating Security into the Undergraduate Software Engineering Curriculum

This research included a thorough examination of the existing software assurance or what is commonly called software security knowledge, methodologies and what information security technologies is currently being recommended by the information technology community. Finally it is demonstrated how this security knowledge could be incorporated into the curriculum for undergraduate software engineering

Extracting a Body of Knowledge as a First Step Towards Defining a United Software Engineering Curriculum Guideline

In general, the computing field is a rapidly changing environment, and as such, software engineering education must be able to adjust quickly to new needs. Industry adapts to technologies as fast as it can, but the critical issue is a need for recent graduates with the necessary expertise and knowledge of new trends, technologies, and practical experience. The industries that employ graduates of computing degree programs aim to hire those who are familiar with the latest technical traits, tools, and methodologies to meet these needs, and the software engineering curriculum needs to respond quickly to these needs. Still, unfortunately, software engineering curriculums cannot change and adopt new technologies fast. Modifying the curriculum to serve industry needs better is a long and tedious process in an academic setting. It is essential to give software engineers top-notch education and training to make sure they have the information and abilities needed to succeed in their careers. In addition, there are multiple computing curriculum recommendations endorsed by computing professional organizations that provide guidelines for curriculum design. The work proposed for this research plans to develop a method of extracting a body of knowledge and generating an ontology using Natural Language Processing algorithms. This will automate the process of extracting information from curriculum guidelines and models and storing that information in one unified ontology. It is then envisioned that the resulting ontology will be used in future research to assist in creating or validating a Software Engineering curriculum to ensure that all knowledge areas are covered and that the outcomes match the established guidelines and models. This automated extracting a body of knowledge process is the first and fundamental step in defining the United Software engineering Curriculum Guideline

Learning software engineering at a distance

There are many challenges in delivering a software engineering curriculum by distance learning. The Open University has offered distance learning master's programs in computing and software engineering for over 20 years. The nature of the main student constituency shapes the curriculum's structure, content, and delivery for its master's in software development and related programs. Theses programs are characterized as part-time, open, large-scale distance learning, professionally accredited, and primarily aimed at practitioners in the IT industry. The article discusses the implications of each of these characteristics for the curriculum and its delivery and outlines the program's future directions

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

Software process improvement in graduate software engineering programs

At the École de technologie supérieure (ÉTS), software process improvement (SPI) is taught in lecture format and with a 10-week implementation project in an organization by teams of students of the graduate software engineering curriculum. The SPI course is taught using a ‘problem- goal-solution’ approach where students learn that any process improvement initiative must be based on issues preventing an organization in achieving its organizational goals whether the organization is a company or a not-for- profit organization. An important aspect of this course is the management of technological change where students learn and put in practice in their project the ‘soft’ issues which are part of most SPI organizational initiatives

Categorizing Non-Functional Requirements Using a Hierarchy in UML.

Non-functional requirements (NFRs) are a subset of requirements, the means by which software system developers and clients communicate about the functionality of the system to be built. This paper has three main parts: first, an overview of how non-functional requirements relate to software engineering is given, along with a survey of NFRs in the software engineering literature. Second, a collection of 161 NFRs is diagrammed using the Unified Modelling Language, forming a tool with which developers may more easily identify and write additional NFRs. Third, a lesson plan is presented, a learning module intended for an undergraduate software engineering curriculum. The results of presenting this learning module to a class in Spring, 2003 is presented