{"title":"构建软件开发的对话框架","authors":"A. Finkelstein, H. Fuks, Celso Niskier, M. Sadler","doi":"10.1145/75110.75118","DOIUrl":null,"url":null,"abstract":"The most significant informal motivation for using an understanding of dialogue to explicate program development is readily available. The notion of software development as a dialogic activity coincides with the traditional conception of client(s) and developer(s) sitting face to face across a table the client explaining the requirements and the developer occasionally asking guiding questions, seeking clarification, pointing out inconsistencies and raising unanticipated consequences.","PeriodicalId":414925,"journal":{"name":"International Software Process Workshop","volume":"436 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1988-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"3","resultStr":"{\"title\":\"Constructing a dialogic framework for software development\",\"authors\":\"A. Finkelstein, H. Fuks, Celso Niskier, M. Sadler\",\"doi\":\"10.1145/75110.75118\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The most significant informal motivation for using an understanding of dialogue to explicate program development is readily available. The notion of software development as a dialogic activity coincides with the traditional conception of client(s) and developer(s) sitting face to face across a table the client explaining the requirements and the developer occasionally asking guiding questions, seeking clarification, pointing out inconsistencies and raising unanticipated consequences.\",\"PeriodicalId\":414925,\"journal\":{\"name\":\"International Software Process Workshop\",\"volume\":\"436 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1988-04-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"3\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"International Software Process Workshop\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/75110.75118\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"International Software Process Workshop","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/75110.75118","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Constructing a dialogic framework for software development
The most significant informal motivation for using an understanding of dialogue to explicate program development is readily available. The notion of software development as a dialogic activity coincides with the traditional conception of client(s) and developer(s) sitting face to face across a table the client explaining the requirements and the developer occasionally asking guiding questions, seeking clarification, pointing out inconsistencies and raising unanticipated consequences.