Trab. Ingles

Evidence-based software engineering
Abstract:
Our objective is to describe how software engineering might benefit from an

evidence-based approach and to identify the potential difficulties associated with the
approach. We compared the organisation and technical infrastructure supporting
evidence-based medicine (EBM) with the situation in software engineering. We
considered the impact that factors peculiar to software engineering (i.e. the skill factor
and the lifecycle factor) would have on our ability to practice evidence-based software
engineering (EBSE). EBSE promises a number of benefits by encouraging integration of
research results with a view to supporting the needs of many different stakeholder groups.
However, we do not currently have the infrastructure needed for widespread adoption of
EBSE. The skill factor means software engineering experiments are vulnerable to subject
and experimenter bias. The lifecycle factor means it is difficult to determine how
technologies will behave once deployed. Software engineering would benefit from
adopting what it can of the evidence approach provided that it deals with the specific
problems that arise from the nature of software engineering.
Source: https://ieeexplore.ieee.org/abstract/document/1317449
Process Models in Software Engineering
Abstract
Software systems come and go through a series of passages that account for their
inception, initial development, productive operation, upkeep, and retirement from one
generation to another. This article categorizes and examines a number of methods for
describing or modeling how software systems are developed. It begins with background
and definitions of traditional software life-cycle models that dominate most textbook
discussions and current software development practices. This is followed by a more
comprehensive review of the alternative models of software evolution that are of current
use as the basis for organizing software engineering projects and technologies.
Source: https://onlinelibrary.wiley.com/doi/abs/10.1002/0471028959.sof250
Software Engineering Standards
James W. Moore
Abstract
Although not a recognized engineering profession, the discipline called “software

engineering” is evolving toward professional acceptance. One element of this evolution is
the creation of a body of standards for the responsible practitioners. This article describes
those standards.
The standards described in this article have been developed by Standards

Developing Organizations (SDOs) operating on the principles of consensus development.
The community of consensus varies, though. For example, the Institute of Electrical and
Electronic Engineers (IEEE) generally develops its standards by achieving a consensus of
technical professionals self-selected from the membership of the organization. On the
other hand, international standards are formed by a consensus of “national bodies,”
representatives of nations who cast ballots presumably representing national interests.
Nearly all of the standards discussed in this article are intended for voluntary
adoption; that is, an organization makes its own decision, without coercion, to adopt the
standard. (This contrasts with regulatory standards, imposed by processes similar to law,
and mandated stadards, such as military standards, required as a precondition of doing
business with a dominant customer.) Organizations adopt voluntary standards because
they improve their products, or improve the perception of their products in a competitive
marketplace. Alternatively, the standards may improve the organization's business
processes, allowing them to make their products more cost-effectively.
Examples of benefits that standards may provide are given.
Source: https://onlinelibrary.wiley.com/doi/abs/10.1002/0471028959.sof319
A survey of controlled experiments in software engineering
Abstract:
The classical method for identifying cause-effect relationships is to conduct

controlled experiments. This paper reports upon the present state of how controlled
experiments in software engineering are conducted and the extent to which relevant
information is reported. Among the 5,453 scientific articles published in 12 leading
software engineering journals and conferences in the decade from 1993 to 2002, 103
articles (1.9 percent) reported controlled experiments in which individuals or teams
performed one or more software engineering tasks. This survey quantitatively
characterizes the topics of the experiments and their subjects (number of subjects,
students versus professionals, recruitment, and rewards for participation), tasks (type of
task, duration, and type and size of application) and environments (location, development
tools). Furthermore, the survey reports on how internal and external validity is addressed
and the extent to which experiments are replicated. The gathered data reflects the
relevance of software engineering experiments to industrial practice and the scientific
maturity of software engineering research.
Software Engineering
January 1996
Abstract
From the Publisher:
This book describes current best practices in software engineering. It begins with
an overview of current issues and in particular the engineering of large, complex software-
intensive systems. It presents software engineering as an important part of the solution to
the "software crisis," enabling developers to deliver software systems on time, within
budget, that meet their requirements and the needs and expectations of the users. The
activities of the software life cycle - requirements engineering, design, coding, validation,
verification, testing, and maintenance - are discussed in the context of conventional and
innovative life cycles. Methods used in software engineering, such as object-oriented
development, structured development, and formal methods, are presented. The book
then describes the roles of project management, quality assurance, configuration
management, standards, metrics, and the software process. Finally, emerging
technologies and the education of software engineers are discussed.
The New Software Engineering
December 1993
Abstract
From the Publisher:
Software engineering from the standpoint of business Conger covers it all: Three
widely used analysis and design methods in business application development - process,
data, and object oriented - including the reason behind using each method and their
similarities and differences; The benefits and pitfalls of using automated support tools in
business, including CASE tools, program development tools, testing aids, and group
support tools; and many often-ignored yet hot topics such as organizational
reengineering, software reengineering, user involvement techniques, interface design,
purchasing software and hardware change control, and testing.
Source: https://dl.acm.org/doi/abs/10.5555/528883
Software engineering in the academy
Abstract:
Institutions that teach software are responsible for producing professionals who
will build and maintain systems to the satisfaction of their beneficiaries. The article
presents some ideas on how best to honor this responsibility. It presents five goals of a
curriculum: principles: lasting concepts that underlie the whole field; practices: problem-
solving techniques that good professionals apply consciously and regularly; applications:
areas of expertise in which the principles and practices find their best expression; tools:
state-of-the-art products that facilitate the application of these principles and practices;
mathematics: the formal basis that makes it possible to understand everything else.
Ethical issues in empirical studies of software engineering
Abstract:
The popularity of empirical methods in software engineering research is on the

rise. Surveys, experiments, metrics, case studies, and field studies are examples of
empirical methods used to investigate both software engineering processes and
products. The increased application of empirical methods has also brought about an
increase in discussions about adapting these methods to the peculiarities of software
engineering. In contrast, the ethical issues raised by empirical methods have received
little, if any, attention in the software engineering literature. This article is intended to
introduce the ethical issues raised by empirical research to the software engineering
research community and to stimulate discussion of how best to deal with these ethical
issues. Through a review of the ethical codes of several fields that commonly employ
humans and artifacts as research subjects, we have identified major ethical issues
relevant to empirical studies of software engineering. These issues are illustrated with real
empirical studies of software engineering.

Trab. Ingles

Uploaded by

Copyright:

Available Formats

Trab. Ingles

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Trab. Ingles

Uploaded by

Copyright:

Available Formats

Evidence-based software engineering

Our objective is to describe how software engineering might benefit from an

Process Models in Software Engineering

Software Engineering Standards

Although not a recognized engineering profession, the discipline called “software

The standards described in this article have been developed by Standards

Examples of benefits that standards may provide are given.

A survey of controlled experiments in software engineering

The classical method for identifying cause-effect relationships is to conduct

From the Publisher:

From the Publisher:

Software engineering in the academy

Ethical issues in empirical studies of software engineering

The popularity of empirical methods in software engineering research is on the

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.