PPK: A method for recording and analyzing software design processes

Tsuyoshi Nakajima, Naoki Tamura, Kenji Uehara

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

The authors propose a method for recording and analyzing actual design processes, which is called the problem-product-knowledge (PPK) method. This method consists of two parts: a method for recording design activities and a framework for organizing the record. The recording method allows designers to record their activities easily, and the framework allows analysts to organize a record into a design process description and provides two different views of a design process: a problem solving process and a product generating process. The PPK model can be considered as a tool which analysts can use to construct a tree (or dag) of the designer's activity in a bottom-up manner. This tree/dag includes abstraction of both the problem-solving process and the product generating process. Such an abstraction greatly enhances the understandability of the design.

Original languageEnglish
Title of host publicationProceedings - IEEE Computer Society's International Computer Software & Applications Conference
PublisherPubl by IEEE
Pages555-563
Number of pages9
Publication statusPublished - 1990
Externally publishedYes
EventProceedings of the 14th Annual International Computer Software and Applications Conference - COMPSAC 90 - Chicago, IL, USA
Duration: 1990 Oct 291990 Nov 2

Other

OtherProceedings of the 14th Annual International Computer Software and Applications Conference - COMPSAC 90
CityChicago, IL, USA
Period90/10/2990/11/2

Fingerprint

Software design

ASJC Scopus subject areas

  • Engineering(all)

Cite this

Nakajima, T., Tamura, N., & Uehara, K. (1990). PPK: A method for recording and analyzing software design processes. In Proceedings - IEEE Computer Society's International Computer Software & Applications Conference (pp. 555-563). Publ by IEEE.

PPK : A method for recording and analyzing software design processes. / Nakajima, Tsuyoshi; Tamura, Naoki; Uehara, Kenji.

Proceedings - IEEE Computer Society's International Computer Software & Applications Conference. Publ by IEEE, 1990. p. 555-563.

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Nakajima, T, Tamura, N & Uehara, K 1990, PPK: A method for recording and analyzing software design processes. in Proceedings - IEEE Computer Society's International Computer Software & Applications Conference. Publ by IEEE, pp. 555-563, Proceedings of the 14th Annual International Computer Software and Applications Conference - COMPSAC 90, Chicago, IL, USA, 90/10/29.
Nakajima T, Tamura N, Uehara K. PPK: A method for recording and analyzing software design processes. In Proceedings - IEEE Computer Society's International Computer Software & Applications Conference. Publ by IEEE. 1990. p. 555-563
Nakajima, Tsuyoshi ; Tamura, Naoki ; Uehara, Kenji. / PPK : A method for recording and analyzing software design processes. Proceedings - IEEE Computer Society's International Computer Software & Applications Conference. Publ by IEEE, 1990. pp. 555-563
@inproceedings{1e4ecf9d66f1415490326ff7d5b6574e,
title = "PPK: A method for recording and analyzing software design processes",
abstract = "The authors propose a method for recording and analyzing actual design processes, which is called the problem-product-knowledge (PPK) method. This method consists of two parts: a method for recording design activities and a framework for organizing the record. The recording method allows designers to record their activities easily, and the framework allows analysts to organize a record into a design process description and provides two different views of a design process: a problem solving process and a product generating process. The PPK model can be considered as a tool which analysts can use to construct a tree (or dag) of the designer's activity in a bottom-up manner. This tree/dag includes abstraction of both the problem-solving process and the product generating process. Such an abstraction greatly enhances the understandability of the design.",
author = "Tsuyoshi Nakajima and Naoki Tamura and Kenji Uehara",
year = "1990",
language = "English",
pages = "555--563",
booktitle = "Proceedings - IEEE Computer Society's International Computer Software & Applications Conference",
publisher = "Publ by IEEE",

}

TY - GEN

T1 - PPK

T2 - A method for recording and analyzing software design processes

AU - Nakajima, Tsuyoshi

AU - Tamura, Naoki

AU - Uehara, Kenji

PY - 1990

Y1 - 1990

N2 - The authors propose a method for recording and analyzing actual design processes, which is called the problem-product-knowledge (PPK) method. This method consists of two parts: a method for recording design activities and a framework for organizing the record. The recording method allows designers to record their activities easily, and the framework allows analysts to organize a record into a design process description and provides two different views of a design process: a problem solving process and a product generating process. The PPK model can be considered as a tool which analysts can use to construct a tree (or dag) of the designer's activity in a bottom-up manner. This tree/dag includes abstraction of both the problem-solving process and the product generating process. Such an abstraction greatly enhances the understandability of the design.

AB - The authors propose a method for recording and analyzing actual design processes, which is called the problem-product-knowledge (PPK) method. This method consists of two parts: a method for recording design activities and a framework for organizing the record. The recording method allows designers to record their activities easily, and the framework allows analysts to organize a record into a design process description and provides two different views of a design process: a problem solving process and a product generating process. The PPK model can be considered as a tool which analysts can use to construct a tree (or dag) of the designer's activity in a bottom-up manner. This tree/dag includes abstraction of both the problem-solving process and the product generating process. Such an abstraction greatly enhances the understandability of the design.

UR - http://www.scopus.com/inward/record.url?scp=0025532512&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=0025532512&partnerID=8YFLogxK

M3 - Conference contribution

AN - SCOPUS:0025532512

SP - 555

EP - 563

BT - Proceedings - IEEE Computer Society's International Computer Software & Applications Conference

PB - Publ by IEEE

ER -