Finding a history for software engineering

Mahoney, Michael S.

doi:10.1109/mahc.2004.1268389

Cited by 9 publications

(6 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The second Age began after about 25 years after the first milestone, when SE was sufficiently resilient to reach maturity [27]. Several changes forced SE to grow up.…”

Section: The Second Agementioning

confidence: 99%

Software Engineering Timeline: major areas of interest and multidisciplinary trends

Cano¹,

Sagrado²,

Cañadas³

2020

Preprint

View full text Add to dashboard Cite

Society today cannot run without software and by extension, without Software Engineering. Since this discipline emerged in 1968, practitioners have learned valuable lessons that have contributed to current practices. Some have become outdated but many are still relevant and widely used.From the personal and incomplete perspective of the authors, this paper not only reviews the major milestones and areas of interest in the Software Engineering timeline helping software engineers to appreciate the state of things, but also tries to give some insights into the trends that this complex engineering will see in the near future.

show abstract

“…The second Age began after about 25 years after the first milestone, when SE was sufficiently resilient to reach maturity [27]. Several changes forced SE to grow up.…”

Section: The Second Agementioning

confidence: 99%

Software Engineering Timeline: major areas of interest and multidisciplinary trends

Cano¹,

Sagrado²,

Cañadas³

2020

Preprint

View full text Add to dashboard Cite

show abstract

“…Around 1968 software engineering came to be recognized as an engineering discipline of its own (Mahoney 2004in Neubert 2015. This recognition came shortly before IBM decided to unbundle its hardware and software, paving the way to the commodification of software products (Neubert 2015).…”

Section: From Waterfall To Agile Developmentmentioning

confidence: 99%

Privacy after the Agile Turn

Gürses¹,

Hoboken²

2017

Preprint

View full text Add to dashboard Cite

Moving beyond algorithms and big data as starting points for discussions about privacy, the authors of Privacy After the Agile Turn focus our attention on the new modes of production of information systems. Specifically, they look at three shifts that have transformed most of the software industry: software is now delivered as services, software and hardware have moved into the cloud and software’s development is ever more agile. These shifts have altered the conditions for privacy governance, and rendered the typical mental models underlying regulatory frameworks for information systems out-of-date. After 'the agile turn', modularity in production processes creates new challenges for allocating regulatory responsibility. Privacy implications of software are harder to address due to the dynamic nature of services and feature development, which undercuts extant privacy regulation that assumes a clear beginning and end of production processes. And the data-driven nature of services, beyond the prospect of monetization, has become part of software development itself. With their focus on production, the authors manage to place known challenges to privacy in a new light and create new avenues for privacy research and practice.

show abstract

“…No caso da ES, há uma particularidade de excepcional relevância, caso se aceite o argumento de MAHONEY [23]. Isto porque, em seu artigo Finding a History for Software Engineering, [23, pp.8-9], historiadores e os próprios engenheiros são surpreendentemente colocados lado a lado no interesse pela história da engenharia de software.…”

Section: A "Desnaturalização" Dos Modelos E Artefatos Através De Suasunclassified

Um Olhar Sociotécnico sobre a Engenharia de Software

Cukierman

Teixeira

Prikladnicki

2007

RITA

View full text Add to dashboard Cite

Resumo:As novas tecnologias modificam a forma e a substância do controle, da participação e da coesão social. Porém, ao fazê-lo, são também modificadas pela experiência social, de sorte que o técnico e o social constituem um movimento de "co-modificação", somente percebido por uma aproximação concomitantemente social e técnica, por um olhar sociotécnico. O artigo pretende apresentar algumas das principais características deste olhar, bem como discutir os desafios que coloca para a engenharia de software.Abstract: New technologies modify the form and the substance of social control, participation and cohesion. However, as they modify, they are also modified by social practices in such a way it is possible to argue that social and technical dimensions constitute a process of mutual construction, only apprehended through an approach simultaneously social and technical, trough a sociotechnical frame. This article presents some of this frame's main features, as well as its challenges to software engineering. Palavras-chave:Engenharia de Software, Olhar Sociotécnico, Interdisciplinaridade, WOSES 1 PESC/COPPE/UFRJ {hcukier, cant}@cos.ufrj.br 2 FACIN/PUCRS {rafaelp@pucrs.br}

show abstract

Finding a history for software engineering

Cited by 9 publications

References 0 publications

Software Engineering Timeline: major areas of interest and multidisciplinary trends

Software Engineering Timeline: major areas of interest and multidisciplinary trends

Privacy after the Agile Turn

Um Olhar Sociotécnico sobre a Engenharia de Software

Contact Info

Product

Resources

About