25 Model-Based Design of Product-Related Information …
363
• System boundary and scope: the proposed model describes interactions among the
stakeholders in a product life cycle. These interactions can specify requirements
of the information management system in terms of input and output flows of
items (e.g. products, parts, and materials) and information. But the model regards
the system as a black-box. In other words, the model lacks capability to define
the internal structure of the system, which partly represents the system’s design.
Therefore, this capability enables designers to test whether a system with a certain
internal structure can realize intended flows of items and information.
• Measures to data unavailability: the availability of detailed data defined and owned
by manufacturers to recyclers in the life cycle depends partly on the design of
the product model and the information management system. The product model
should possess a composition so that the information management system can
partly retrieve information consistent with the given authorization and security
criteria.
• Model verification procedure: the paper described the development process of the
proposed model, but the verification process was out of the scope of this paper. The
verification process can be divided in terms of the type of models to be verified;
life cycle models, information management system models, and product models.
First, a life cycles model can be verified regarding capability of the model to
simulate expected (qualitative and quantitative) behavior specified by model users,
while assuming the internal structure of the employed information management
system and the product model is regarded as black boxes. Second, an information
management system model can be verified regarding capability to model the
internal structure of the system, and simulate the variations on decision making
policies regarding, for instance, access control and security. Finally, a product
model can be verified regarding capability of a model to define its attributes
intended by model users and store its data and to define a view specified by each
stakeholder (e.g. users and stakeholders.).
Furthermore, the model will be used to analyze the value of the variables representing the life cycle model that satisfy the external requirements and identify the
appropriate input and output of the information management system. Then, the model
will be used to model the detailed logic of the analysis of the collected information so that the quality and quantity of output information satisfy the needs of the
stakeholders.
Acknowledgements This paper is based on results obtained from a project commissioned by the
New Energy and Industrial Technology Development Organization (NEDO). The authors thank Mr.
Asada for supporting the development of the life cycle model on the simulation framework.
363
• System boundary and scope: the proposed model describes interactions among the
stakeholders in a product life cycle. These interactions can specify requirements
of the information management system in terms of input and output flows of
items (e.g. products, parts, and materials) and information. But the model regards
the system as a black-box. In other words, the model lacks capability to define
the internal structure of the system, which partly represents the system’s design.
Therefore, this capability enables designers to test whether a system with a certain
internal structure can realize intended flows of items and information.
• Measures to data unavailability: the availability of detailed data defined and owned
by manufacturers to recyclers in the life cycle depends partly on the design of
the product model and the information management system. The product model
should possess a composition so that the information management system can
partly retrieve information consistent with the given authorization and security
criteria.
• Model verification procedure: the paper described the development process of the
proposed model, but the verification process was out of the scope of this paper. The
verification process can be divided in terms of the type of models to be verified;
life cycle models, information management system models, and product models.
First, a life cycles model can be verified regarding capability of the model to
simulate expected (qualitative and quantitative) behavior specified by model users,
while assuming the internal structure of the employed information management
system and the product model is regarded as black boxes. Second, an information
management system model can be verified regarding capability to model the
internal structure of the system, and simulate the variations on decision making
policies regarding, for instance, access control and security. Finally, a product
model can be verified regarding capability of a model to define its attributes
intended by model users and store its data and to define a view specified by each
stakeholder (e.g. users and stakeholders.).
Furthermore, the model will be used to analyze the value of the variables representing the life cycle model that satisfy the external requirements and identify the
appropriate input and output of the information management system. Then, the model
will be used to model the detailed logic of the analysis of the collected information so that the quality and quantity of output information satisfy the needs of the
stakeholders.
Acknowledgements This paper is based on results obtained from a project commissioned by the
New Energy and Industrial Technology Development Organization (NEDO). The authors thank Mr.
Asada for supporting the development of the life cycle model on the simulation framework.