Architectures for Software Systems: A Curriculum Development Proposal in Undergraduate Software Engineering

1993 ◽  
Author(s):  
David Garlan ◽  
Mary Shaw
Keyword(s):  
Software Engineering ◽  
Curriculum Development ◽  
Software Systems

scholarly journals Synthesis of Code Anomalies: Revealing Design Problems in the Source Code

2020 ◽  
Author(s):  
Willian N. Oizumi ◽  
Alessandro F. Garcia
Keyword(s):  
Software Engineering ◽  
Source Code ◽  
New Technique ◽  
Software Systems ◽  
Identification Task ◽  
Software Projects ◽  
Design Problems ◽  
Engineering Community ◽  
Synthesis Technique ◽  
A New Technique

Design problems affect most software projects and make their maintenance expensive and impeditive. Thus, the identification of potential design problems in the source code – which is very often the only available and upto-date artifact in a project – becomes essential in long-living software systems. This identification task is challenging as the reification of design problems in the source code tend to be scattered through several code elements. However, stateof-the-art techniques do not provide enough information to effectively help developers in this task. In this work, we address this challenge by proposing a new technique to support developers in revealing design problems. This technique synthesizes information about potential design problems, which are materialized in the implementation under the form of syntactic and semantic anomaly agglomerations. Our evaluation shows that the proposed synthesis technique helps to reveal more than 1200 design problems across 7 industry-strength systems, with a median precision of 71% and a median recall of 78%. The relevance of our work has been widely recognized by the software engineering community through 2 awards and 7 publications in international and national venues.

scholarly journals RESEARCH TRENDS IN SOFTWARE ENGINEERING FIELD: A LITERATURE REVIEW

2020 ◽  
Vol 7 (6) ◽  
pp. 58-65
Author(s):  
Hiba Al Sghaier
Keyword(s):  
Software Engineering ◽  
Programming Languages ◽  
New Technologies ◽  
Research Trends ◽  
Mobile Technologies ◽  
Smart Devices ◽  
Software Systems ◽  
Current Time ◽  
Develop Software ◽  
Software Engineers

Software engineering is one of computer science branches, it comprises of building and developing software systems and applications. Software engineering is a discipline that has a constant growth in research in aim to identify new technologies and adopt it in different areas; there is a considerable investment on software engineering trends at the current time due to the availability of mobile technologies. With millions of billions of smart devices that are connected to the internet, all industries around the world are rapidly becoming a technology driven industries. Software engineers are aware of programming languages that are employed to develop software systems, by applying engineering principles to development process; they can design customized software systems for individual or organizational customers. The new trends in software engineering are numerous, Cloud Computing, machine learning, deep learning, big Data, mobile Computing. Nevertheless, there are many more other research trends in software engineering's field that have been intensively explored and implemented in many different industries. In this paper, authors try to summarize the most fields that are integrated with software engineering recently.

Supporting Model-Driven Development

2017 ◽  
pp. 396-432
Author(s):  
Rita Suzana Pitangueira Maciel ◽  
Ana Patrícia F. Magalhães Mascarenhas ◽  
Ramon Araújo Gomes ◽  
João Pedro D. B. de Queiroz
Keyword(s):  
Software Engineering ◽  
Process Models ◽  
Software Systems ◽  
Model Driven Development ◽  
Model Driven ◽  
Process Specification ◽  
Process Enactment ◽  
Support Tools ◽  
Important Approach ◽  
Engineering Environment

The adoption of Model-Driven Development (MDD) is increasing and it is widely recognized as an important approach for building software systems. In addition to traditional development process models, an MDD process requires the selection of metamodels and mapping rules for the generation of the transformation chain which produces models and application code. However, existing support tools and transformation engines for MDD do not address different kinds of software process activities, such as application modeling and testing, to guide the developers. Furthermore, they do not enable process modeling nor the (semi) automated execution of activities during process enactment. MoDErNE (Model Driven Process-Centered Software Engineering Environment) uses process-centered software engineering environment concepts to improve MDD process specification and enactment by using a metamodeling foundation. This chapter presents model driven development concept issues and the MoDErNE approach and environment. MoDErNE aims to facilitate MDD process specification and enactment.

An Approach to Formal Specification of Component-Based Software

2011 ◽  
pp. 34-42
Author(s):  
Tarek Zernadji ◽  
Raida Elmansouri ◽  
Allaoua Chaoui
Keyword(s):  
Software Engineering ◽  
Software Reuse ◽  
Formal Specification ◽  
Component Composition ◽  
Software Systems ◽  
Software Components ◽  
Design Component ◽  
Component Design ◽  
Component Based Software Engineering ◽  
Expected Benefits

Current research on software reuse in Component Based Software Engineering (CBSE) covers a variety of fields, including component design, component specification, component composition, component-based framework. CBSE is quickly becoming a mainstream approach to software development and most researchers are hoping that it will be solutions to all the problems that led to software crisis. The software engineering techniques specific to this discipline, in phases such as modeling, verification or validation of component based software systems still insufficient and need more research efforts. ECATNets (Extended Concurrent Algebraic Term Nets) are frameworks for specification, modeling and validation of concurrent and distributed systems. They are characterized by their semantics defined in terms of rewriting logic. The objective of this article is to propose a formal specification of software components by using ECATNets formalism. The expected benefits of this work are: Offer a formal notation for describing the different features of concurrent and distributed software components; Defining a formal unambiguous semantic to describe behavior of the composed system.

Architecture, Specification, and Design of Service-Oriented Systems

2011 ◽  
pp. 68-83
Author(s):  
Jaroslac Král ◽  
Michal Žemlicka
Keyword(s):  
Software Engineering ◽  
Peer To Peer ◽  
Requirements Specification ◽  
Engineering Properties ◽  
Software Systems ◽  
Service Orientation ◽  
Engineering Product ◽  
Service Oriented ◽  
Development Processes ◽  
Architecture Specification

Service-oriented software systems (SOSS) are becoming the leading paradigm of software engineering. The crucial elements of the requirements specification of SOSSs are discussed as well as the relation between the requirements specification and the architecture of SOSS. It is preferable to understand service orientation not to be limited to Web services and Internet only. It is shown that there are several variants of SOSS having different application domains, different user properties, different development processes, and different software engineering properties. The conditions implying advantageous user properties of SOSS are presented. The conditions are user-oriented interfaces of services, the application of peer-to-peer philosophy, and the combination of different technologies of communication between services (seemingly the obsolete ones inclusive), and autonomy of the services. These conditions imply excellent software engineering properties of SOSSs as well. Service orientation promises to open the way to the software as a proper engineering product.

A Social Ontology for Integrating Security and Software Engineering

2007 ◽  
pp. 70-106 ◽  
Author(s):  
E. Yu ◽  
L. Liu ◽  
J. Mylopoulous
Keyword(s):  
Software Engineering ◽  
Social Ontology ◽  
Software Systems ◽  
Engineering Process ◽  
Future Directions ◽  
The Core ◽  
Modelling Framework ◽  
The Social ◽  
The World ◽  
Software Engineering Process

As software becomes more and more entrenched in everyday life in today’s society, security looms large as an unsolved problem. Despite advances in security mecha-nisms and technologies, most software systems in the world remain precarious and vulnerable. There is now widespread recognition that security cannot be achieved by technology alone. All software systems are ultimately embedded in some human social environment. The effectiveness of the system depends very much on the forces in that environment. Yet there are few systematic techniques for treating the social context of security together with technical system design in an integral way. In this chapter, we argue that a social ontology at the core of a requirements engineering process can be the basis for integrating security into a requirements driven software engineering process. We describe the i* agent-oriented modelling framework and show how it can be used to model and reason about security concerns and responses. A smart card example is used to illustrate. Future directions for a social paradigm for security and software engineering are discussed.

Software Security Engineering

2008 ◽  
pp. 927-942
Author(s):  
Mohammad Zulkernine ◽  
Sheikh I. Ahamed
Keyword(s):  
Software Engineering ◽  
Software Security ◽  
Rapid Development ◽  
Process Models ◽  
Software Systems ◽  
Engineering Process ◽  
Software Life Cycle ◽  
Security Engineering ◽  
Controlled Systems ◽  
Protection Mechanisms

The rapid development and expansion of network-based applications have changed the computing world in the last decade. However, this overwhelming success has an Achilles’ heel: most software-controlled systems are prone to attacks both by internal and external users of the highly connected computing systems. These software systems must be engineered with reliable protection mechanisms, while still delivering the expected value of the software to their customers within the budgeted time and cost. The principal obstacle in achieving these two different but interdependent objectives is that current software engineering processes do not provide enough support for the software developers to achieve security goals. In this chapter, we reemphasize the principal objectives of both software engineering and security engineering, and strive to identify the major steps of a software security engineering process that will be useful for building secure software systems. Both software engineering and security engineering are ever-evolving disciplines, and software security engineering is still in its infancy. This chapter proposes a unification of the process models of software engineering and security engineering in order to improve the steps of the software life cycle that would better address the underlying objectives of both engineering processes. This unification will facilitate the incorporation of the advancement of the features of one engineering process into the other. The chapter also provides a brief overview and survey of the current state-of-the-art of software engineering and security engineering with respect to computer systems.

Software Security Engineering

2011 ◽  
pp. 215-233 ◽  
Author(s):  
Mohammad Zulkernine ◽  
Sheikh I. Ahamed
Keyword(s):  
Software Engineering ◽  
Software Security ◽  
Rapid Development ◽  
Process Models ◽  
Software Systems ◽  
Engineering Process ◽  
Software Life Cycle ◽  
Security Engineering ◽  
Controlled Systems ◽  
Protection Mechanisms

The rapid development and expansion of network-based applications have changed the computing world in the last decade. However, this overwhelming success has an Achilles’ heel: most software-controlled systems are prone to attacks both by internal and external users of the highly connected computing systems. These software systems must be engineered with reliable protection mechanisms, while still delivering the expected value of the software to their customers within the budgeted time and cost. The principal obstacle in achieving these two different but interdependent objectives is that current software engineering processes do not provide enough support for the software developers to achieve security goals. In this chapter, we reemphasize the principal objectives of both software engineering and security engineering, and strive to identify the major steps of a software security engineering process that will be useful for building secure software systems. Both software engineering and security engineering are ever-evolving disciplines, and software security engineering is still in its infancy. This chapter proposes a unification of the process models of software engineering and security engineering in order to improve the steps of the software life cycle that would better address the underlying objectives of both engineering processes. This unification will facilitate the incorporation of the advancement of the features of one engineering process into the other. The chapter also provides a brief overview and survey of the current state-of-the-art of software engineering and security engineering with respect to computer systems.

Sign in / Sign up

Export Citation Format

Share Document