Catalogue Search | MBRL
Search Results Heading
Explore the vast range of titles available.
MBRLSearchResults
-
DisciplineDiscipline
-
Is Peer ReviewedIs Peer Reviewed
-
Reading LevelReading Level
-
Content TypeContent Type
-
YearFrom:-To:
-
More FiltersMore FiltersItem TypeIs Full-Text AvailableSubjectPublisherSourceDonorLanguagePlace of PublicationContributorsLocation
Done
Filters
Reset
1,333
result(s) for
"Software engineering History."
Sort by:
Software technology : 10 years of innovation in IEEE Computer
Sales handles: - Introduces the software landscape and challenges associated with emerging technologies - Covers the life cycle of software products, including concepts, requirements, development, testing, verification, evolution, and security - Written by leaders in the software industry - Articles cover both theoretical and practical topics Market description: Primary Audience: Researchers and Practitioners Secondary Audience: Graduate Students-- Provided by publisher.
The Computer Boys Take Over
by
Ensmenger, Nathan L
in
Academic profession
,
Communications & Telecommunications
,
Computer programmers
2012,2010
This is a book about the computer revolution of the mid-twentieth century and the people who made it possible. Unlike most histories of computing, it is not a book about machines, inventors, or entrepreneurs. Instead, it tells the story of the vast but largely anonymous legions of computer specialists--programmers, systems analysts, and other software developers--who transformed the electronic computer from a scientific curiosity into the defining technology of the modern era. As the systems that they built became increasingly powerful and ubiquitous, these specialists became the focus of a series of critiques of the social and organizational impact of electronic computing. To many of their contemporaries, it seemed the \"computer boys\" were taking over, not just in the corporate setting, but also in government, politics, and society in general. In The Computer Boys Take Over , Nathan Ensmenger traces the rise to power of the computer expert in modern American society. His rich and nuanced portrayal of the men and women (a surprising number of the \"computer boys\" were, in fact, female) who built their careers around the novel technology of electronic computing explores issues of power, identity, and expertise that have only become more significant in our increasingly computerized society. In his recasting of the drama of the computer revolution through the eyes of its principle revolutionaries, Ensmenger reminds us that the computerization of modern society was not an inevitable process driven by impersonal technological or economic imperatives, but was rather a creative, contentious, and above all, fundamentally human development.
The golden age of software architecture
2006
Since the late 1980s, software architecture has emerged as the principled understanding of the large-scale structures of software systems. From its roots in qualitative descriptions of empirically observed useful system organizations, software architecture has matured to encompass a broad set of notations, tools, and analysis techniques. Whereas initially the research area interpreted software practice, it now offers concrete guidance for complex software design and development. It has made the transition from basic research to an essential element of software system design and construction. This retrospective examines software architecture's growth in the context of a technology maturation model, matching its significant accomplishments to the model's stages to gain perspective on where the field stands today. This trajectory has taken architecture to its golden age.
Journal Article
Think black : a memoir
\"The story of America's first Black engineer, his revolutionary son, and the corporation that destroyed their relationship\"-- Provided by publisher.
\The Golden Age of Software Architecture\ Revisited
2009
In \"The Golden Age of Software Architecture\" Paul Clements and Mary Shaw reviewed the emergence of software architecture as the principled understanding of the large-scale structures of software systems. Here they reflect on progress since that article, updating the state of practice and reassessing some of the opportunities.
Journal Article
25 Years of Software
2008
The column points to the November/December 2008 issue's many special features celebrating IEEE Software's 25th anniversary of publication. This overview summarizes how experts in requirements, design, architecture, software technology and tools, interface design, and more view their areas' notable milestones and accomplishments.
Journal Article
Arguments that Count
2013
In a rapidly changing world, we rely upon experts to assess the promise and risks of new technology. But how do these experts make sense of a highly uncertain future? In Arguments that Count , Rebecca Slayton offers an important new perspective. Drawing on new historical documents and interviews as well as perspectives in science and technology studies, she provides an original account of how scientists came to terms with the unprecedented threat of nuclear-armed intercontinental ballistic missiles (ICBMs). She compares how two different professional communities -- physicists and computer scientists -- constructed arguments about the risks of missile defense, and how these arguments changed over time. Slayton shows that our understanding of technological risks is shaped by disciplinary repertoires -- the codified knowledge and mathematical rules that experts use to frame new challenges. And, significantly, a new repertoire can bring long-neglected risks into clear view. In the 1950s, scientists recognized that high-speed computers would be needed to cope with the unprecedented speed of ICBMs. But the nation's elite science advisors had no way to analyze the risks of computers so used physics to assess what they could: radar and missile performance. Only decades later, after establishing computing as a science, were advisors able to analyze authoritatively the risks associated with complex software -- most notably, the risk of a catastrophic failure. As we continue to confront new threats, including that of cyber attack, Slayton offers valuable insight into how different kinds of expertise can limit or expand our capacity to address novel technological risks.
SciPy 1.0: fundamental algorithms for scientific computing in Python
2020
SciPy is an open-source scientific computing library for the Python programming language. Since its initial release in 2001, SciPy has become a de facto standard for leveraging scientific algorithms in Python, with over 600 unique code contributors, thousands of dependent packages, over 100,000 dependent repositories and millions of downloads per year. In this work, we provide an overview of the capabilities and development practices of SciPy 1.0 and highlight some recent technical developments.
This Perspective describes the development and capabilities of SciPy 1.0, an open source scientific computing library for the Python programming language.
Journal Article
Change Distilling:Tree Differencing for Fine-Grained Source Code Change Extraction
by
Wursch, Michael
,
Gall, Harald
,
Fluri, Beat
in
Algorithm design and analysis
,
Algorithms
,
Computer programs
2007
A key issue in software evolution analysis is the identification of particular changes that occur across several versions of a program. We present change distilling, a tree differencing algorithm for fine-grained source code change extraction. For that, we have improved the existing algorithm of Chawathe et al. for extracting changes in hierarchically structured data. Our algorithm detects changes by finding a match between nodes of the compared two abstract syntax trees and a minimum edit script. We can identify change types between program versions according to our taxonomy of source code changes. We evaluated our change distilling algorithm with a benchmark we developed that consists of 1,064 manually classified changes in 219 revisions from three different open source projects. We achieved significant improvements in extracting types of source code changes: our algorithm approximates the minimum edit script by 45% better than the original change extraction approach by Chawathe et al. We are able to find all occurring changes and almost reach the minimum conforming edit script, i.e., we reach a mean absolute percentage error of 34%, compared to 79% reached by the original algorithm. The paper describes both the change distilling and the results of our evaluation.
Journal Article