website paiken:publications

Selected Papers Available Online

Below is a selection of papers that are currently available at this site. I'll be adding more in response requests. So keep in touch! To download a copy of the paper just follow the links to each paper's abstract. From there another link will permit you to download a version of the paper if the abstract intrigues you.

• Peter Aiken, Chris Metz, Anthony Berta, Bill Finkel, Tracy Skalak, Bob Stanley, Susan Carter, Graham Blevins, John Sells, John McKeon, Debi Crockett, David Rafner, Diane Hara, Jennifer Farris "Assuring Data Quality For ERP Implementation-Part 2 Comprehending The Evolving Picture" Proceedings of the 11th International Conference on Information Quality (the 2006 MIT ICIQ Conference), ISSN 1544-1342, pp. 430-444.
  
  
• Peter Aiken "Using Your Information:  Metadata – The Number One Issue For The Intelligence Community" Intelligence & Warning America Fall 2004 pp. 4-8
  
  
• M. David Allen, Peter Aiken, & Susan Carter, Mary Kay Cyrus, Kathy Wade and Sid McCormac - "Extracting Data from Free Text Fields: Assuring Data Quality for ERP Implementation" ICIQ-03 Proceedings - view abstract.
  
  
• A short paper describing how XML-based portal technologies can save your organization money.
  
  
• Kathi Hoggshead Davis and Peter Aiken "Data Reverse Engineering: An Historical Survey" Proceedings of the 7th Working Conference on Reverse Engineering Brisbane, Queensland, Australia • November 23-25, 2000 • pages 70-78 - view abstract.
  
  
• Peter Aiken "Case Study and Discussion: From T+3 to T+1" Digital Dimensions of Time - TTI/Vanguard San Digeo, CA, February 8, 2000 - view a .pdf version.
  
  
• Peter Aiken, Ojelanki Ngwenyama, and Lewis Broome "Reverse Engineering New Systems for Smooth Implementation" IEEE Software. March/April 1999 16(2):36-43 - view abstract.
  
  
• Peter Aiken & Bill Girling "Data Reengineering Fits the Bill" InformationWeek May 26, 1997, pp. 8A-12A - view a .pdf version of the article
  
  
• Yoon, Y., Aiken, P., Guimaraes, T. "Managing Organizational Data Resources: Quality Dimensions" Information Resources Management Journal 13(3) July-September 2000 pp. 5-13 - view abstract.
  
  
• Peter Aiken "Hypermedia-based Requirements Engineering" (chapter in) Advanced Technology for Command and Control Systems Engineering (Stephen J. Andriole, editor), AFCEA International Press, 1990 ISBN 0916159221 - view abstract.
  
  
• Juanita Billings, Lynda Hodgson & Peter Aiken, "The BRIDGE: A Toolkit Approach to Reverse Engineering System Metadata in Support of Migration to Enterprise Software" (Advances in Conceptual Modeling ER'99 Workshop on Reverse Engineering in Information Systems Paris, France November 15-17, 1999, pages 134-148.) - view abstract.
  
  
• Dave Swafford, Diana Elman, Peter Aiken, Jeff Merhout "Experiences Reverse Engineering Manually" Proceedings of the Fourth European Conference on Software Maintenance and Reengineering, Reengineering Week Zurich 29 February – 3 March 2000, pages 189 – 198.
  - view abstract.
  
  
• Peter Aiken "Reverse Engineering of Data" IBM Systems Journal 37(2), 1998 - view abstract.
  
  
• Tina Roth, Peter Aiken, and Scarlette Hobbs "Hypermedia Support For Software Development: A Retrospective Assessment" HYPERMEDIA Winter 1994 6(3) - view abstract.
  
  
• Peter Aiken, Alice Muntz, and Russ Richards "DoD Legacy Systems: Reverse Engineering Data Requirements" Communications of the ACM May 1994 37(5):26-41 - view abstract.
  
  
• Peter Aiken and Lynda Hodgson "Synergistic Dependence Between Analysis Techniques" Proceedings of the 9th Software Technology Conference April 1997 - view abstract.
  
  
• Kim H. Madsen and Peter Aiken, "Some Experiences Using Cooperative Interactive Storyboard Prototyping" Communications of the ACM, 1993. 36(4): p. 57-67 - view abstract
  
  
• Peter Aiken & James Bach "Hypermedia-based Support For Requirements Analysis: Promise And Problems" in Proceedings of the Southeast Decision Sciences Institute 1994 Annual Meeting. 1994. Williamsburg, VA. - view abstract

Abstracts

• Abstract of Assuring Data Quality For ERP Implementation-Part 2 Comprehending The Evolving Picture by Peter Aiken, Chris Metz, Anthony Berta, Bill Finkel, Tracy Skalak, Bob Stanley, Susan Carter, Graham Blevins, John Sells, John McKeon, Debi Crockett, David Rafner, Diane Hara, Jennifer Farris
  
  Presenting results subsequent to those presented at the 2003 ICIQ Conference, we describe how our team-based approach to addressing legacy data quality has necessarily evolved over a multi-year period.  Developed as a team by the government in conjunction with a research institute, an initial task has evolved considerably over the ensuing years.  A "data quality challenge" associated with DoD/DLA's migration from SAMMS to SAP, has now evolved through six distinct phases. Tangible savings and results have been documented.  Perhaps more useful are the lessons learned over the multiple project years as we collectively reached improved understandings of the problem nature and its implications.  These involve evolving and maturing our understanding and approach to data quality by adding a structure-orientation to what had been addressed as a practice-oriented data quality challenge.  Earlier recognition would have permitted additional savings to be realized. 
  
  View a .pdf version of this paper or return to index of papers online
  
  
• Abstract of Extracting Data from Free Text Fields: Assuring Data Quality for ERP Implementation by M. David Allen, Peter Aiken, & Susan Carter (VCU/Data Blueprint, Inc.) Mary Kay Cyrus, Kathy Wade, Sid McCormac (Defense Supply Center Richmond)
  
  This experience paper describes a repeatable model developed to address a class of data quality problems encountered when converting text data to ERPs. Users often devise their own means of implementing system features not directly supported by the systems. Often they employ what are known as clear-text, free-text, or "comment" fields to support the desired features. Moving data from these fields to ERPs involves first extracting atomic data items. Unlike most data, free text is not subject to structural or practice-oriented data quality measures when it is created. This results in a range of data quality challenges ranging from typing errors to structural errors such as prime key mismatch, duplication, and other issues. In our experiences with one large government system, a number of challenges were encountered that contained enough internal differences to require the development of a more generic framework for addressing this type of problem. The specifics of the actual issues confronted are not as interesting as the lessons that can be learned from the general approach to problems of this type. The solution type developed demonstrated a positive return on investment to the government. We will discuss the challenges, the costs associated with continuing along the original path, the solution developed, and its applicability to other organizations and situations..
  
  View a .pdf version of this paper or return to index of papers online
• Abstract of Peter Aiken & James Bach "Hypermedia-based Support For Requirements Analysis: Promise And Problems" in Proceedings of the Southeast Decision Sciences Institute 1994 Annual Meeting. 1994. Williamsburg, VA.
  
  This paper describes our efforts at providing hypermedia-based support for requirements analysis. We present: an overview of our concept of hypermedia-based support for the requirements analysis process; our experiences using this technology; and some remaining tech-nological challenges highlighted by our experi-ences. Our analy-sis of requirements analyst's needs indicates several productivity related benefits will result from the success-ful application of hypermedia tech-nologies especially in rapid prototyping contexts. These relate to hypermedia's ability to more faithfully capture and represent system requirements, pro-viding increased re-quirements traceability and giving analysts di-rect, repeat-able access to mul-timedia requirements information that would otherwise be un-available.
  
  View a .pdf version of this paper or return to index of papers online.
  
  
• Abstract of Kathi Hoggshead Davis and Peter Aiken "Data Reverse Engineering: An Historical Survey" Proceedings of the 7th Working Conference on Reverse Engineering Brisbane, Queensland, Australia • November 23-25, 2000 • pages 70-78.
  
  Data reverse engineering is a rapidly growing field, which is sometimes misunderstood. In our effort to promote the realization that data reverse engineering is a valuable and essential part of reverse engineering and is now finding its place in software engineering, we present a summary of the history of data reverse engineering. In this paper, a definition of data reverse engineering, a summary of the history of what has been done and published, a statement about the state-of-the-art today, and a comment on the future of DRE is presented.
  
  View a .pdf version of this paper or return to index of papers online.
  
  
• Abstract of Yoon, Y., Aiken, P., Guimaraes, T. "Managing Organizational Data Resources: Quality Dimensions" Information Resources Management Journal 13(3) July-September 2000 pp. 5-13.
  
  Little guidance has been available to organizations interested in addressing the necessary dimensions of data resources management to ensure data quality in increasingly encountered situations when data usage crosses system boundaries. The basic concept of metadata quality as a foundation for data quality engineering is proposed, as well as an extended data life cycle model consisting of eight phases: metadata creation, metadata structuring, metadata refinement, data creation, data utilization, data assessment, data refinement, and data manipulation. This extended model will enable further development of life cycle phase-specific data quality engineering methods. The paper also expands the concept of applicable data quality dimensions, presenting data quality as a function of four distinct components: data value quality; data representation quality; data model quality; and data architecture quality. Each of these, in turn, is described in terms of specific data quality attributes.
  
  View a .pdf version of this paper or return to index of papers online.
  
  
• Abstract of Peter Aiken, Ojelanki Ngwenyama, and Lewis Broome, "Reverse Engineering New Systems for Smooth Implementation" IEEE Software. March/April 1999 16(2):36-43
  
  Practitioners and researchers are currently investigating reverse engineering as a means of leveraging system reengineering and maintenance efforts. This article illustrates the utility of reverse engineering new systems, using as an example a commercial, client server system. We describe the motivations for, approach to, and results of reverse engineering a new system from PeopleSoft (see Enterprise Software side bar). The reverse engineering was a preliminary implementation activity that was designed to derive unavailable metadata describing the PeopleSoft system architecture. The derived metadata was maintained in a repository and used in subsequent implementation activities. An important finding was that, maintained in a normalized format, the three metadata types (describing system, workflow, and data structures) effectively assisted system implementation. This case study contributes both theoretical and practical insights, broadening the perceived utility of reverse engineering.
  
  View a .pdf version of this paper or return to index of papers online.
  
  
• "Hypermedia-based Requirements Engineering" (chapter in) Advanced Technology for Command and Control Systems Engineering (Stephen J. Andriole, editor), forthcoming from AFCEA International Press, 1990
  
  This chapter outlines a hypermedia-based approach to the requirements engineering portion of software development life cycle. While as yet untested, hypermedia-based tools and techniques seem to offer promising benefits to the analysis and design phases of certain classes of software system development. The first half of the chapter is devoted to a examination of the development of hypermedia as a technology. While its conceptual origin dates to 1945, only recent efforts by software engineers have resulted in tools that begin to approach the functionality of concepts put forth by researchers in the field. These concepts are briefly reviewed. A wide range of software packages have what are labeled as hypermedia capabilities. The next section presents definitions intended to cut through the hype surrounding the evolution of this new technology. The following section presents an examination of the actual capabilities of hypermedia-based systems. These have been summarized as eight features common to systems with hypermedia capabilities. The second half of the chapter is devoted to a discussion of the application of hypermedia features to requirements engineering functions. While not applicable, to all cases each of the eight features can be implemented in a fashion augmenting the development of certain classes of software applications. Specific classes of systems benefitting from the application of hypermedia-based requirements engineering are identified. The requirements engineering process is briefly described in terms of four basic functions: capture, organize, structure, and present. Hypermedia support for each function is outlined. The chapter closes with a brief description of a workstation constructed from off-the-shelf components capable of supporting hypermedia-based requirements engineering.
  
  View a .pdf version of this paper or return to index of papers online.
  
  
• Abstract of Juanita Billings, Lynda Hodgson & Peter Aiken, "The BRIDGE: A Toolkit Approach to Reverse Engineering System Metadata in Support of Migration to Enterprise Software" (under review)
  
  The role of reverse engineering system metadata when migrating legacy systems to enterprise software such as PeopleSoft‰ has not been widely articulated. Bridging the gap between new enterprisewide software systems and legacy systems has proven to be an enormous and costly hurdle when attempted without sufficient understanding of the legacy environment and enterprise metadata. We present a model-based methodology for providing a metadata-based foundation for migrating data from legacy systems to enterprise software. The methodology components are: metadata reverse engineering/extraction load; technical metadata/migration rules mapping; data migration directory development; and process/interface directories development. Following metadata reverse engineering and extraction, the metadata is loaded into the repository. Once loaded, the rules mappings and migration directory developments can begin. Process/interface directories development can occur exclusive of metadata and migration directory development tasks. Methodologies work best when supported by appropriate tools. Based on widely available Office-suite components, we developed a flexible toolkit to support the methodology and facilitate enterprise software system migration. The toolkit allows users to capture, analyze, and publish various implementation-specific metadata. We used the toolkit to publish metadata for use by the technical implementation team as well as by project management and business users. We describe each methodology component, the associated toolkit elements developed to implement each component, the various component outputs, and the resources required to implement the solution. The methodology was developed in the context of an anonymous real world implementation. Organizations can use this approach to create a sound basis for reverse engineering system metadata when migrating to enterprise software.
  
  View a .pdf version of this paper or return to index of papers online.
  
  
• Abstract of Dave Swafford, Diana Elman, Peter Aiken, Jeff Merhout "Experiences Reverse Engineering Manually" Proceedings of the Fourth European Conference on Software Maintenance and Reengineering, Reengineering Week Zurich 29 February – 3 March 2000, pages 189 – 198.
  
  Whether automated or manual techniques are employed, reverse engineering goals remain identical. This paper describes the development and application of a manual reverse engineering analysis of a large, legacy system. The reverse engineering analysis goal was to provide a preliminary analysis identifying potential functionality in a legacy system that could be reused as part of a larger system reengineering effort. The manual analysis was required because circumstances prevented the application of automated reverse engineering techniques. The paper describes: the larger organizational systems reengineering context in which the reverse engineering was required; the circumstances motivating the specific reverse engineering analysis goals; the situational characteristics preventing application of automated techniques; the manual reverse engineering process developed to achieve the analysis goals; the evolution of the analysis products during the course of the analysis; the analysis results; the resources required to produce the results; and an evaluation of the process effectiveness.
  
  View a .pdf version of this paper or return to index of papers online.
  
  
• Abstract of Peter Aiken "Reverse Engineering of Data" IBM Systems Journal 37(2), 1998, pp. 246-269.
  
  Data reverse engineering (DRE) is a relatively new approach used to address a general category of data disintegration problems. DRE combines structured data analysis techniques with rigorous data management practices. The approach is growing in popularity as an integrative systems reengineering method because of its ability to address multiple problem types concurrently. Integrative problem solving is key to effective application of DRE. A general DRE template is described as both an activity model and as a data model to be populated with reverse engineered data. DRE is shown to offer an integrated common solution methodology for addressing a range of problems. In addition, DRE outputs can be used to develop a more flexible and useful reengineered system. Four scenarios describe DRE used to: 1) harness data assets to address organizational data integration problems; 2) develop organizational data migration strategies 3) specifying distributed systems architectures; and 4) implement and propagate organizational CASE tool usage to address system maintenance problems. Selectively applied DRE can be an important first step toward eventual organization-wide data integration.
  
  This article is available in .pdf format or return to index of papers online.
  
  
• Abstract of "Hypermedia Support For Software Development: A Retrospective Assessment" by Tina Roth, Peter Aiken, and Scarlette Hobbs appeared in HYPERMEDIA in the Winter 1994 volume 6(3):149-173.
  
  Hypermedia technologies have been available for about a decade. Beginning with Douglas Engelbart, researchers have become interested in applying hypermedia concepts and technologies to software development. This paper assesses this symbiosis between hypermedia and software development as described by research contributions; by our count, more than one hundred articles. To date, no collection of, or guide to, this literature has been published. A number of significant contributions are classified, described, and appraised - providing a guide into what has been a rich but perhaps under-reported research area. Hypermedia has made significant contributions to software development in three primary areas: coping with massive amounts of information associated with software development projects; establishing and maintaining linkages between various types of software engineering documents; and enabling development engineers to record, document, and preserve knowledge about development thoughts, processes and rationale. These contributions may help direct the focus of future research towards building on, combining and assessing the resulting contributions. A research agenda is proposed along these lines.
  
  View .pfd version or return to index of papers online.
  
  
• Abstract of "DoD Legacy Systems: Reverse Engineering Data Requirements" by Peter Aiken, Alice Muntz, and Russ Richards appeared in the Communications of the ACM in May 1994 volume 37(5):26-41.
  
  As with most large organizations, the Department of Defense has both strategic and economic needs to capitalize on and to consolidate existing information systems. This paper reports on a framework currently being used to reverse engineer selected legacy information systems in DoD's heterogeneous environment. This generic approach was developed to recover organizational business rules, business domain information, system functional requirements, functional dependencies, and system data architectures, largely in the form of normalized logical data models. We are applying the approach as a series of pilot studies on systems ranging from those using home grown languages and database management systems developed during the late 1960's to those using high order languages and commercial network database management systems. These pilot studies are being used to validate and refine the framework with real-life systems; to develop a baseline approach for reverse engineering DoD legacy information systems; and to scope and estimate future system reengineering costs. Furthermore, the results of these projects will help to determine the economic viability of reengineering, reverse, and forward engineering efforts for these legacy systems.
  
  View .pfd version or return to index of papers online.
  
  
• Abstract of Peter Aiken and Lynda Hodgson "Synergistic Dependence Between Analysis Techniques" Proceedings of the 9th Software Technology Conference April 1997
  
  Business process reengineering (BPR) and systems reengineering (SR) are often implemented separately, in an uncoordinated fashion. Yet practitioners realize that BPR can be informed by SR and that SR can benefit from the application of BPR concepts. This research indicates that potential synergies can result when BPR and SR are pursued in an integrated fashion. The paper presents an integrated BPR and SR model that has been successfully applied in practice.
  
  View .pfd version or return to index of papers online.
  
  
• Abstract of Aiken, P.H. and P. Piper. Estimating Data Reverse Engineering Projects. in 5th Annual Systems Reengineering Workshop. 1995. Monterery, CA: Johns Hopkins University Applied Physics Laboratory Research Center
  
  Systems reengineering projects are defined by the process of first reverse engineering appropriate components of the target system and then forward engineering it using the knowledge gained from the reverse engineering efforts [Chikofsky & Cross 1990]. The cost of the reverse engineering portion(s) can be a major determinate of the ultimate viability of the reengineering effort. This paper describes an approach to developing reverse engineering project estimates based on our experience with several Department of Defense data reverse engineering efforts. Like all analysis problems, useful project estimates can be best established only after preliminary study of the project context. As a result, it is necessary to invest a relatively small amount of resources in a preliminary system survey prior to attempting to develop project estimates. The information gained from this approach can be used to better evaluate the overall system reengineering costs.

  View .pfd version or return to index of papers online.
• Abstract of Kim H. Madsen and Peter Aiken, "Some Experiences Using Cooperative Interactive Storyboard Prototyping" Communications of the ACM, 1993. 36(4): p. 57-67
  
  Certain types of products appear to be continually associated with poor interfaces. Especially for these product types, the need for active end-user participation in development activities is seen increasingly as critical to quality interface development. Cooperative Interactive Storyboard Prototyping (CISP) is a development approach facilitating active end-user participation in design activities that help to address these apparently difficult design problems. Key features of CISP include: 1) reducing the time and effort required to produce iterations of prototype interfaces; 2) support for interactive prototype use, evaluation and modification; and 3) creation and use of modifiable, domain specific building blocks.

  View .pfd version or return to index of papers online.