Protocol Analysis: A NEGLECTED PRACTICE.
The article describes the experience of the authors related to the use of protocol analysis. They adopted protocol analysis when studying how software designers employ available documentation for designing systems from existing components. They used tools for extracting and composing components and...
| Publicado en: | Communications of the ACM Vol. 49; no. 2; pp. 117 - 123 |
|---|---|
| Autores principales: | , , |
| Formato: | Artículo |
| Publicado: |
Association for Computing Machinery
Feb2006
|
| Materias: | |
| Acceso en línea: | Ver este registro en EBSCOhost |
| fields | @attributes: recordID: 1 pdfLink: plink: https://search.ebscohost.com/login.aspx?direct=true&db=hlh&AN=19568347&site=ehost-live header: @attributes: shortDbName: hlh uiTerm: 19568347 longDbName: Humanities International Complete uiTag: AN controlInfo: bkinfo: jinfo: jid: 00010782 ACM jtl: Communications of the ACM issn: 00010782 maglogo: N pubinfo: dt: Feb2006 vid: 49 iid: 2 pid: 68 pub: Association for Computing Machinery artinfo: ui: 19568347 10.1145/1113034.1113039 ppf: 117 ppct: 6 formats: tig: atl: Protocol Analysis: A NEGLECTED PRACTICE. aug: au: Owen, Stephen Budgen, David Brereton, Pearl affil: Lecturer, School of Computing and Mathematics, Keele University, Keele, U.K. Professor, School of Computing and Mathematics, Keele University, Keele, U.K. Professor, Department of Computer Science, Durham University, Durham, U.K. su: Computer network protocols Computer software development Unix operating systems Computer operating systems Computer software Source code Computer science Computer files Systems design sug: subj: Computer network protocols Computer software development Unix operating systems Computer operating systems Computer software Source code Computer science Computer files Systems design ab: The article describes the experience of the authors related to the use of protocol analysis. They adopted protocol analysis when studying how software designers employ available documentation for designing systems from existing components. They used tools for extracting and composing components and for document browsing they developed for their earlier work, along with integral logging capabilities that could be used to record developer actions in a nonintrusive manner. They employed Unix processes as components and a group of four subjects, each with several years' experience using Unix but no experience writing shell scripts. They were allocated two tasks. First task was to produce a simple source code control system that would allow users to store and retrieve particular versions of source code. Second task was to produce a utility to count types of files in a specified path. They gave subjects access to all component utilities available on the system utilities. Extra introductory documentation regarding the use of the editor software and the production of shell scripts was provided on paper pubtype: Periodical doctype: Article src: R language: English refInfo: copyright: @attributes: flag: Y dt: @attributes: year: 2006 holdings: @attributes: islocal: N |
|---|