{"title":"技术论证与结构","authors":"S. Bains","doi":"10.1093/OSO/9780198822820.003.0006","DOIUrl":null,"url":null,"abstract":"“Technical Argument and Structure” discusses the steps involved in constructing a report. For a technical story to be told coherently, the audience must be given the context they need to appreciate the work that has been done. The first part of this chapter covers a straightforward formula to achieve this. The argument starts by presenting the vision (goal) for the work and then narrows down to the reason why progress was needed, the specific technical problem or obstacle that needs to be tackled to make this progress, the prognosis, and the competing solutions (and why the status quo is not good enough in these particular circumstances). This then leads perfectly to a discussion of the new solution. The second part of the chapter talks about overlaying structure on top of that: specifically, how to think about introductions, titles, and conclusions in the context of the technical argument.","PeriodicalId":386509,"journal":{"name":"Explaining the Future","volume":"275 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2019-02-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Technical Argument and Structure\",\"authors\":\"S. Bains\",\"doi\":\"10.1093/OSO/9780198822820.003.0006\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"“Technical Argument and Structure” discusses the steps involved in constructing a report. For a technical story to be told coherently, the audience must be given the context they need to appreciate the work that has been done. The first part of this chapter covers a straightforward formula to achieve this. The argument starts by presenting the vision (goal) for the work and then narrows down to the reason why progress was needed, the specific technical problem or obstacle that needs to be tackled to make this progress, the prognosis, and the competing solutions (and why the status quo is not good enough in these particular circumstances). This then leads perfectly to a discussion of the new solution. The second part of the chapter talks about overlaying structure on top of that: specifically, how to think about introductions, titles, and conclusions in the context of the technical argument.\",\"PeriodicalId\":386509,\"journal\":{\"name\":\"Explaining the Future\",\"volume\":\"275 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2019-02-27\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Explaining the Future\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1093/OSO/9780198822820.003.0006\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Explaining the Future","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1093/OSO/9780198822820.003.0006","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
“Technical Argument and Structure” discusses the steps involved in constructing a report. For a technical story to be told coherently, the audience must be given the context they need to appreciate the work that has been done. The first part of this chapter covers a straightforward formula to achieve this. The argument starts by presenting the vision (goal) for the work and then narrows down to the reason why progress was needed, the specific technical problem or obstacle that needs to be tackled to make this progress, the prognosis, and the competing solutions (and why the status quo is not good enough in these particular circumstances). This then leads perfectly to a discussion of the new solution. The second part of the chapter talks about overlaying structure on top of that: specifically, how to think about introductions, titles, and conclusions in the context of the technical argument.