Ian Sommerville · 1990
This paper describes how we have modified a software engineering stream within a computer science course to include broader concepts of systems engineering. We justify this inclusion by showing how many reported problems with large systems are not just software problems but relate to system issues such as hardware and operational processes. We describe what we mean by ‘systems engineering ’ and go on to discuss the particular course structure which we have developed. We explain, in some detail, the contents of two specific systems engineering courses (Software Intensive Systems Engineering and Critical Systems Engineering) and discuss the problems and challenges we have faced in making these changes. In the Appendix, we provide details of the case studies which are used as linking themes in our courses. 1.
Cited by 0
R. Baxter · 2004
Software engineering for high-performance computer systems (HPCS) is regarded by many including many of its practitioners - as strangely, even esoterically, different from "standard" software engineering. That there is nuances are undeniable, but it is our thesis that software engineering for HPCS should be approached like any other software engineering task. Based on over thirteen years of software development experience on parallel and other HPCS, we present an overview of the engineering processes used at EPCC. We describe our approaches to delivering high-quality software on time and to budget, approaches which have helped sustain EPCC as a self-funded institute at the University of Edinburgh.
Cited by 23
Dieter Rombach · Lecture notes in computer science · 1998
Cited by 2
D. Sarvani, R. Saradha · 2018
Cited by 0
Past Year Exam Question · UTPedia (Universiti Teknologi Petronas) · 2022
Cited by 0
Druskat, Stephan, Felderer, Michael, Haupt, Carina · elib (German Aerospace Center) · 2024
Research software is developed with aims and in contexts that differ from other software, by individuals who are often not trained software engineers. Furthermore, research software projects often suffer from resource scarcity, but produce artifacts that are crucial for research and require software engineering. These circumstances have an impact on how software engineering activities are performed in research contexts. This holds in particular for requirements engineering, which plays a crucial role for the success of traditional software engineering projects. In this paper, we discuss the relationship between research software and requirements engineering. For that purpose, we also reflect on research software engineering and its relationship to software engineering research. Closer collaboration between software engineering research and research software engineering creates opportunities for knowledge exchange and better research software engineering practice, and interesting new research questions for software engineering research. This is true also for requirements engineering, where lightweight methods are required, depending on the type of research software developed.
Cited by 0Open access
L. A. Belady · 1992
Cited by 0
Tharam S. Dillon, Elizabeth Chang, Pornpit Wongthongtham · Proceedings - Australian Software Engineering Conference/Proceedings · 2008
This paper describes the use of ontologies in different aspects of software engineering. This use of ontologies varies from support for software developers at multiple sites to the use of an ontology to provide semantics in different categories of software, particularly on the Web. The world's first and only software engineering ontology and a project management ontology in conjunction with a domain ontology are used to provide support for software development that is taking place at multiple sites. Ontologies are used to provide semantics to deal with heterogeneity in the representation of multiple information sources, enable the selection and composition of web services and grid resources, provide the shared knowledge base for multiagent systems, provide semantics and structure for trust and reputation systems and privacy based systems and codification of shared knowledge within different domains in business, science, manufacturing, engineering and utilities. They, therefore, bring a new paradigm to software engineering through the use of semantics as a central mechanism which will revolutionize the way software is developed and consumed in the future leading to the development of software as a service bringing about the dawn of software engineering 2.0.
Cited by 31Open access
Carl A. Argila, Paul C. Jorgensen · 2018
This chapter presents a synopsis of various practical software engineering techniques which can be used to construct software development models; these techniques are illustrated within the context of a simple case study system. Software engineering has focused primarily on computer programming with ad hoc analysis and design techniques. One of the most widely accepted approaches in the software engineering industry is to build two software development models. The term computer-aided software engineering is used to describe a collection of tools which automate all or some of various of the software engineering life cycle phases. Software testing has three distinct levels: unit, integration and system. The starting point of most code-based test methods is the program graph, a directed graph where nodes correspond to source statement fragments and edges indicate possible sequential execution. The goal of software testing at any level is to determine the extent to which the specified and implemented behaviors coincide.
Cited by 0
J. N. Buxton · 1978
Cited by 3
Birk, Volker · TIB KMO / FLOWWORKS GmbH · 2007
Wie schreibt man eine umfangreiche Software? Man setzt sich vor den leeren Editor und beginnt zu debuggen! Daß es nicht immer so funktioniert, erklärt uns dieser Vortrag.
Cited by 0Open access
Tom Gilb · ACM SIGSOFT Software Engineering Notes · 1984
article Free Access Share on Software engineering: using "design by objectives" tools (DBO) Author: Tom Gilb Independent Consultant, Kolbotn, Norway Independent Consultant, Kolbotn, NorwayView Profile Authors Info & Claims ACM SIGSOFT Software Engineering NotesVolume 9Issue 2April 1984 pp 104–113https://doi.org/10.1145/1010925.1010932Online:01 April 1984Publication History 2citation218DownloadsMetricsTotal Citations2Total Downloads218Last 12 Months4Last 6 weeks1 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF
Cited by 3
Rüdiger Heimgärtner · 2017
Cited by 1
2009
Cited by 0
Peter Weber, Roland Gabriel, Thomas Lux et al. · 2022
This chapter introduces software engineering as a structured process to develop and design business applications. The chapter deals with both the general phase approach and agile approaches to software development (Extreme Programming (XP) and Scrum). In addition, the basics of object-oriented software development as well as approaches and problems of cost estimation are presented. Since software engineering is carried out as a project, a brief introduction to project management is also included.
Cited by 1Open access
SpringerReference · 2011
Cited by 0
Lubos Brieda, Joseph Wang, Robert P. Martin · 2024
Cited by 0
WORLD SCIENTIFIC eBooks · 2009
Cited by 0
Бачинський, Т. · ELARTU (Ternopil National Technical University) · 2012
Cited by 0
Mufeti, T K · UNAM Scholarly Repository (University of Namibia) · 2016
Cited by 0