Miroirs/cooperative-software-development
1
0
Fork 0
mirror of https://github.com/amyjko/cooperative-software-development synced 2024-12-25 21:58:15 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated chapters.

Browse source
This commit is contained in:
Amy J. Ko 2020-10-10 13:06:58 -07:00
parent 0807161ca3
commit 71ef3753c7
1 changed files with 16 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

33
book.json
View file

@ -1,26 +1,25 @@
{
"title": "Cooperative Software Development",
"authors": ["[Amy J. Ko|https://faculty.washington.edu/ajko/]"],
"contributors": ["[Benjamin Xie|http://benjixie.com]"],
"license": "[Creative Commons Attribution-NoDeriviatives 4.0|https://creativecommons.org/licenses/by-nd/4.0/]",
"cover": ["cover.jpg", "A photograph of a racially and gender diverse team of six making decisions.", "Software engineering is inherently social.", "Shutterstock"],
"unknown": ["error.png", "A screen shot of a Linux operating system kernel panic", "Uh oh, something went wrong.", "William Pina"],
"cover": "|cover.jpg|A photograph of a racially and gender diverse team of six making decisions.|Software engineering is inherently social.|Shutterstock|",
"unknown": "|error.png|A screen shot of a Linux operating system kernel panic|Uh oh, something went wrong|William Pina|",
"description": "This book is an introduction to the many human, social, and political aspects of software engineering. It's unique in two ways. First, unlike many software engineering books, it explictly avoids centering technical questions about software engineering, instead focusing on the many ways that software engineering work is cognitive, social, and organizational. Second, it does so by engaging extensively with academic research literature, summarizing key findings, but also questioning them, opening a dialog about the nature of software engineering work and the many factors that shape it. Anyone that reads it will be better prepared to critically engage in creating software in teams.\n\nThis book is a living document. Do you see ways to improve it? [Submit an issue|https://github.com/amyjko/cooperative-software-development/issues] or a [pull request|https://github.com/amyjko/cooperative-software-development/pulls] to its [GitHub repository|https://github.com/amyjko/cooperative-software-development].\n\n_This material is based upon work supported by the National Science Foundation under Grant No. 0952733. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation._",
"chapters": [
["History", "history", "Hamilton.jpg", "Margaret Hamilton working on the Apollo flight software.", "Margaret Hamilton working on the Apollo flight software.", "NASA"],
["Organizations", "organizations", "team.jpg", "A software team hard at work", "Early days at the author's software startup in 2012.", "Amy J. Ko"],
["Communication", "communication", "communication.png", "A man and a woman having a conversation", "Clear and timely communication is at the heart of effective software engineering.", "Public domain"],
["Productivity", "productivity", "productivity.jpg", "A women working at a laptop", "Productivity isn't just about working fast.", "Creative Commons CC0"],
["Quality", "quality", "zoho.jpg", "A screenshot of the Zoho issue tracker.", "Software quality is multidimensional and often coursely measured through issue trackers like this one.", "Zoho, Inc."],
["Requirements", "requirements", "scaffolding.jpg", "An architectural structure showing the framework of a glass structure", "Requirements specify what software must do, constraining, focusing, and defining it's successful functioning.", "Public domain"],
["Architecture", "architecture", "church.jpg", "A photograph of a church hallway with arches.", "Architecture is how code is organized", "Creative Commons 0"],
["Specifications", "specifications", "blueprint.jpg", "A blueprint for an architectural plan", "Specifications add a layer of detail onto architectural plans.", "Public domain"],
["Process", "process", "flow.jpg", "A photograph of a river", "Good process is like a river, seamlessly flowing around obstacles", "Public domain"],
["Comprehension", "comprehension", "network.png", "A visualization of many interconnected node", "Program comprehension is about understanding dependencies", "Public domain"],
["Verification", "verification", "check.png", "A check mark", "Have you met your requirements? How do you know?", "Public domain"],
["Monitoring", "monitoring", "monitoring.jpg", "A photograph of a lifeguide monitoring a beach.", "It's not always easy to see software fail.", "Public domain"],
["Evolution", "evolution", "atsign.png", "Four variations on an at sign.", "Software changes and that requires planning.", "Public domain"],
["Debugging", "debugging", "swatter.png", "An illustration of a fly swatter.", "Debugging is inevitable because defects are inevitable", "Public domain"]
{ "id": "history", "title": "History", "image": "|Hamilton.jpg|Margaret Hamilton working on the Apollo flight software.|Margaret Hamilton working on the Apollo flight software|NASA|" },
{ "id": "organizations", "title": "Organizations", "image": "|team.jpg|A software team hard at work|Early days at the author's software startup in 2012.|Amy J. Ko|" },
{ "id": "communication", "title": "Communication", "image": "|communication.png|A man and a woman having a conversation|Clear and timely communication is at the heart of effective software engineering.|Creative Commons CC0|" },
{ "id": "productivity", "title": "Productivity", "image": "|productivity.jpg|A women working at a laptop|Productivity isn't just about working fast|Creative Commons CC0|" },
{ "id": "quality", "title": "Quality", "image": "|zoho.jpg|A screenshot of the Zoho issue tracker.|Software quality is multidimensional and often coursely measured through issue trackers like this one.|Zoho, Inc.|" },
{ "id": "requirements", "title": "Requirements", "image": "|scaffolding.jpg|An architectural structure showing the framework of a glass structure|Requirements specify what software must do, constraining, focusing, and defining it's successful functioning.|Public domain|" },
{ "id": "architecture", "title": "Architecture", "image": "|church.jpg|A photograph of a church hallway with arches.|Architecture is how code is organized|Creative Commons 0|" },
{ "id": "specifications", "title": "Specifications", "image": "|blueprint.jpg|A blueprint for an architectural plan|Specifications add a layer of detail onto architectural plans.|Public domain|" },
{ "id": "process", "title": "Process", "image": "|flow.jpg|A photograph of a river|Good process is like a river, seamlessly flowing around obstacles|Public domain|" },
{ "id": "comprehension", "title": "Comprehension", "image": "|network.png|A visualization of many interconnected node|Program comprehension is about understanding dependencies|Public domain|" },
{ "id": "verification", "title": "Verification", "image": "|check.png|A check mark|Have you met your requirements? How do you know?|Public domain|" },
{ "id": "monitoring", "title": "Monitoring", "image": "|monitoring.jpg|A photograph of a lifeguide monitoring a beach.|It's not always easy to see software fail.|Public domain|" },
{ "id": "evolution", "title": "Evolution", "image": "|atsign.png|Four variations on an at sign.|Software changes and that requires planning.|Public domain|" },
{ "id": "debugging", "title": "Debugging", "image": "|swatter.png|An illustration of a fly swatter.|Debugging is inevitable because defects are inevitable|Public domain|" }
],
"revisions": [
["September 2020", "Migrated to [Peruse|https://github.com/amyjko/peruse]."],