4everedit — Team-based Process Documentation Management.
Saved in:
| Title: | 4everedit — Team-based Process Documentation Management. |
|---|---|
| Authors: | Meisinger, Michael1, Rausch, Andreas2 rausch@informatik.uni-kl.de, Sihling, Marc3 |
| Source: | Software Process: Improvement & Practice. Nov2006, Vol. 11 Issue 6, p627-642. 16p. 1 Color Photograph, 4 Diagrams, 2 Graphs. |
| Subjects: | Software documentation, Electronic data processing documentation, Electronic records, Software architecture, Software engineering |
| Abstract: | The introduction and successful application of engineering processes demands a modern infrastructure that supports efficient and convenient management of the various work products, their life cycle, and their relations to each other. Mostly, work products are realized in the form of electronic documents that can easily be edited, stored, copied and exchanged. However, most infrastructure is fundamentally limited by the fact that the information contained in many documents is not accessible because its semantics is unknown. For example, software engineers often document the design of a software architecture in a rather unstructured way and hence cannot benefit from automatic evaluations such as consistency checks regarding the document itself (is it complete?) or its dependencies to other documents (is there a test specification for each component?). Because most documents are inherently structured as a result of the application of certain methods (such as CRC-Cards for software requirements engineering) and because techniques are available to model and handle structured documents (such as XML), combining both successfully seems to be a small gap to bridge. In this article we present the essential concepts to support team-based editing of structured text-based engineering documents. We report on our experiences from the application of the infrastructure ‘4everedit’ in a large-scale industrial process engineering project. Copyright © 2006 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR] |
| Copyright of Software Process: Improvement & Practice is the property of Wiley-Blackwell and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.) | |
| Database: | Engineering Source |
| FullText | Links: – Type: pdflink Text: Availability: 0 |
|---|---|
| Header | DbId: egs DbLabel: Engineering Source An: 23297851 AccessLevel: 6 PubType: Academic Journal PubTypeId: academicJournal PreciseRelevancyScore: 0 |
| IllustrationInfo | |
| Items | – Name: Title Label: Title Group: Ti Data: 4everedit — Team-based Process Documentation Management. – Name: Author Label: Authors Group: Au Data: <searchLink fieldCode="AR" term="%22Meisinger%2C+Michael%22">Meisinger, Michael</searchLink><relatesTo>1</relatesTo><br /><searchLink fieldCode="AR" term="%22Rausch%2C+Andreas%22">Rausch, Andreas</searchLink><relatesTo>2</relatesTo><i> rausch@informatik.uni-kl.de</i><br /><searchLink fieldCode="AR" term="%22Sihling%2C+Marc%22">Sihling, Marc</searchLink><relatesTo>3</relatesTo> – Name: TitleSource Label: Source Group: Src Data: <searchLink fieldCode="JN" term="%22Software+Process%3A+Improvement+%26+Practice%22">Software Process: Improvement & Practice</searchLink>. Nov2006, Vol. 11 Issue 6, p627-642. 16p. 1 Color Photograph, 4 Diagrams, 2 Graphs. – Name: Subject Label: Subjects Group: Su Data: <searchLink fieldCode="DE" term="%22Software+documentation%22">Software documentation</searchLink><br /><searchLink fieldCode="DE" term="%22Electronic+data+processing+documentation%22">Electronic data processing documentation</searchLink><br /><searchLink fieldCode="DE" term="%22Electronic+records%22">Electronic records</searchLink><br /><searchLink fieldCode="DE" term="%22Software+architecture%22">Software architecture</searchLink><br /><searchLink fieldCode="DE" term="%22Software+engineering%22">Software engineering</searchLink> – Name: Abstract Label: Abstract Group: Ab Data: The introduction and successful application of engineering processes demands a modern infrastructure that supports efficient and convenient management of the various work products, their life cycle, and their relations to each other. Mostly, work products are realized in the form of electronic documents that can easily be edited, stored, copied and exchanged. However, most infrastructure is fundamentally limited by the fact that the information contained in many documents is not accessible because its semantics is unknown. For example, software engineers often document the design of a software architecture in a rather unstructured way and hence cannot benefit from automatic evaluations such as consistency checks regarding the document itself (is it complete?) or its dependencies to other documents (is there a test specification for each component?). Because most documents are inherently structured as a result of the application of certain methods (such as CRC-Cards for software requirements engineering) and because techniques are available to model and handle structured documents (such as XML), combining both successfully seems to be a small gap to bridge. In this article we present the essential concepts to support team-based editing of structured text-based engineering documents. We report on our experiences from the application of the infrastructure ‘4everedit’ in a large-scale industrial process engineering project. Copyright © 2006 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR] – Name: AbstractSuppliedCopyright Label: Group: Ab Data: <i>Copyright of Software Process: Improvement & Practice is the property of Wiley-Blackwell and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract.</i> (Copyright applies to all Abstracts.) |
| PLink | https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=egs&AN=23297851 |
| RecordInfo | BibRecord: BibEntity: Identifiers: – Type: doi Value: 10.1002/spip.296 Languages: – Code: eng Text: English PhysicalDescription: Pagination: PageCount: 16 StartPage: 627 Subjects: – SubjectFull: Software documentation Type: general – SubjectFull: Electronic data processing documentation Type: general – SubjectFull: Electronic records Type: general – SubjectFull: Software architecture Type: general – SubjectFull: Software engineering Type: general Titles: – TitleFull: 4everedit — Team-based Process Documentation Management. Type: main BibRelationships: HasContributorRelationships: – PersonEntity: Name: NameFull: Meisinger, Michael – PersonEntity: Name: NameFull: Rausch, Andreas – PersonEntity: Name: NameFull: Sihling, Marc IsPartOfRelationships: – BibEntity: Dates: – D: 01 M: 11 Text: Nov2006 Type: published Y: 2006 Identifiers: – Type: issn-print Value: 10774866 Numbering: – Type: volume Value: 11 – Type: issue Value: 6 Titles: – TitleFull: Software Process: Improvement & Practice Type: main |
| ResultId | 1 |
