A Generation-Selection Process of Product Architecture

Fukuzawa, Mitsuhiro

doi:10.7880/abas.7.1

Cited by 4 publications

(3 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In recent years, architectural theory is used to explain product design. Architecture is a design concept for products and processes, and is categorized into integral and modular architectures (Fukuzawa, 2008;Ge & Fujimoto, 2004;Ulrich, 1995). Integral architecture features a high level of dependency among components, and requires intensive coordination.…”

Section: Rv and Product Featuresmentioning

confidence: 99%

Relational View

Kobayashi

2014

ABAS

View full text Add to dashboard Cite

Dyer and Singh (1998) use the dyad or network, rather than the single firm, as their unit of analysis, and suggest a relational view (RV), which considers interfirm competitive advantage. However, when discussing competitive advantage from the perspective of RV, one must be aware that the special case of Toyota and its suppliers is the assumption. Even in comparison with other Japanese automakers, Toyota and its suppliers have certain characteristics, such as: a) they are geographically close to each other; b) they have substantive special assets; and c) they proactively share knowledge via human interaction, and have a systematic inter-organizational learning system to support this knowledge sharing. Thus, firms trying to acquire competitive advantage of RV need to meet the above prerequisites. Further, RV discussions advocating an increase in special assets for long-term transactional advantage rely on d) product features. If one assumes a less-complex product such as a personal computer, with frequently changing transaction partners where short-term transactions are insignificant, the effectiveness of RV cannot be guaranteed. Given these considerations, this paper summarizes the characteristics a) through d) as prerequisites that generate competitive advantage, from the perspective of RV.

show abstract

Section: Rv and Product Featuresmentioning

confidence: 99%

Relational View

Kobayashi

2014

ABAS

View full text Add to dashboard Cite

show abstract

“…Here, high interdependence refers to how a change in one part may directly affect another. Low interdependence means the parts are relatively independent, and the chance of a change in one part affecting another part is low (Fukuzawa, 2008;Ge & Fujimoto, 2004;Hong & Hartley, 2011).…”

Section: Interdependence In the Task-related Contextmentioning

confidence: 99%

Interdependence in buyer–supplier relationships

Kobayashi

2023

ABAS

View full text Add to dashboard Cite

In studies on buyer-supplier relationships, interdependence is a commonly used keyword; however, its definition and measurement items have not received much attention. By reviewing the literature, this study found two streams in studies associated with interdependence, with each stream having certain commonalities in its measurement items. In the power-related context based on Resource Dependence Theory by (1) Pfeffer and Salancik (1978), it tends to use the percentage of sales accounted for by the trading partner, the substitutability of trading partners, and the switching cost, whereas in the task-related context based on (2) Thompson's (1967) technology, dependence on the traded input and output is often used as measurement items for interdependence. In fact, both logics are implemented in Toyota Motor Corporation's supplier management, using multiple suppliers to avoid resource dependence while some parts are determined by technology.

show abstract

“…Ge and Fujimoto (2004) andFukuzawa (2008) focus on architecture, a design concept of product systems.…”

mentioning

confidence: 99%

Requirement for Engineers in Embedded Software Development Outsourcing

Kobayashi

2015

ABAS

View full text Add to dashboard Cite

In general, research on software development outsourcing, which implicitly assumes application software development, tends to ignore hardware product characteristics. However, in embedded software development, the skills and knowledge required of engineers can differ depending on hardware product characteristics. This study employs the data from an interview-based survey to identify the impact of hardware product characteristics on software development outsourcing. In the case of embedded software, engineers at companies that undertake outsourced work must possess not only knowledge of software developed by the outsourcer but also technical information and knowledge regarding hardware product characteristics that can only be acquired from the same client. This accumulation of firm-specific knowledge and information occurs on a continual basis, and is necessary for this type of outsourcing business. Thus, maintaining a low engineer turnover is important.

show abstract

A Generation-Selection Process of Product Architecture

Cited by 4 publications

References 7 publications

Relational View

Relational View

Interdependence in buyer–supplier relationships

Requirement for Engineers in Embedded Software Development Outsourcing

Contact Info

Product

Resources

About