Vol.5 No.1 2012

Research paper : Construction of a traceability matrix for high quality project management (A. Sakaedani et al.)−14−Synthesiology - English edition Vol.5 No.1 (2012) ReferencesAuthorsAkihiro SakaedaniCurrently in residence at the doctoral program at the Graduate School of System Design and Management, Keio University. Works at NTT COMWARE Corporation. Completed the master’s program at the Graduate School, Gakushuin University, in 1994, and joined NTT. Worked as a system engineer in information system development for about 15 years. Completed the master’s program at the Graduate School of System Design and Management, Keio University, in 2010. In this study, proposed the concept of the traceability matrix and was in charge of the construction of scenario and solution.Yoshiaki OhkamiReceived a Doctor of Engineering from the Graduate School of Engineering, Tokyo Institute of Technology, in 1968. Worked at the National Aerospace Laboratory of Japan, Science and Technology Agency; Department of Mechano-Aerospace Engineering, Tokyo Institute of Technology; Professor, Department of System Design Engineering, Keio University; and Professor and Chairman, Graduate School of System Design and Management, Keio University. Currently, Advisor, SDM Research Institute, Keio University. Visiting Researcher at UCLA, and Research Director, Japan Aerospace Exploration Agency (JAXA). Specializes in dynamics and control of space system. Fellow of the Japan Society of Mechanical Engineers. INCOSE Fellow. Member of The Society of Instrument and Control Engineers, The Japan Society for Aerospace and Space Sciences, IEEE, and others. For this study, was in charge of mathematical verification.Naohiko KohtakeCompleted the course at the Graduate School of Science and Technology, Keio University, in 1998. Joined the National Space Development Agency of Japan (NASDA) in 1998. Engaged in the R&D for devices onboard the H-IIA rocket. After working as a Visiting Researcher at the European Space Agency, returned to the Japan Aerospace Exploration Agency (JAXA) as a senior developer to work on the independency [1]Project Management Institute: A Guide to the Project Management Body of Knowledge: Official Japanese Translation, Global Standard (2008) (in Japanese).[2]K. Forsberg, H. Moozand and H. Cotterman: Visualizing Project Management Models and Frameworks for Mastering Complex Systems, Third Edition, John Wiley & Sons (2005).[3]SWEBOK, http://www.computer.org/portal/web/swebok, accessed in 2011.[4]P. Krucheten: The Rational Unified Process: An Introduction, Second Edition, Pearson Education (2001).[5]W. Royce: Software Project Management A Unified Framework, Addison-Wesley (1998). [6]Japan Users Association of Information Systems: Dai 15 Kai Kigyo IT Doko Chosa 2009 (15th Corporate IT Trend Survey 2009), http://www.juas.or.jp/servey/it09/summary09_0507.pdf, accessed in 2010 (in Japanese).[7]M. Frank, A. Sadeh and S. Ashkenasi: The relationship among systems engineers’ capacity for engineering systems thinking, project types, and project success, Project Management Journal, 42 (5), 31-41 (2011).[8]Standish Group: Chaos Summary 2009: The ten laws of chaos, http://www1.standishgroup.com/newsroom/chaos_2009.php, accessed in 2011.[9]E. V. Hippel: “Sticky information” and the locus of the problem solving: Implications for innovation, Management Science, 40 (4), 429-439 (1994).[10]D. Leffingwell and D. Widrig: Managing Software Requirements: A Unified Approach, Addison-Wesley (2000). [11]H. Yoshikawa: Introduction to theory of service engineering: Framework for theoretical study of service engineering, Synthesiology, 1(2), 111-122 (2008).[12]N. P. Suh: Axiomatic Design: Advances and Applications, Oxford University Press, New York (2001) [M. Nakao, K. Iino and Y. Hatamura, trans.: Koriteki Keikaku, Morikita Publishing, Tokyo (2004)].[13]N. P. Suh: The Principles of Design, Oxford University Press, New York (1990).[14]Y. Aoshima and A. Takeishi: Architecture thinking, Business Architecture, Ch. 2, 27-70, Yukikaku (2001) (in Japanese).[15]A. Takeishi, T. Fujimoto and S. H. Ku: Modularization in automotive industry: Interlinked hierarchies of product, production, and procurement system, Business Architecture, Ch. 4, 101-120, Yukikaku (2001) (in Japanese).[16]TOGAF, https://www2.opengroup.org/ogsys/jsp/publications/PublicationsBySubjectType.jsp?limit=mainSubjectId-50:secSubjectId-50:statusId-1, accessed in 2011.Term 1.Needs expressed, for example, as “we want x.”Term 2.Feature: expressed, for example, as “system is to realize x.”Term 3.Requirement: expressed, for example, as “x is done by the system, and y is output.”Term 4.Function: indicates the roles of the substance or component in realizing the requirement.Term 5.Component: has implemented artifact and has function.Term 6.Artifact: produced by activity; for example, a design plan.Term 7.Activity: indicates work done by the team, produces artifact.Term 8.Team: individual or group assigned to various roles within the organization.Term 9.Reference architecture: architecture created especially for a certain region, and used as reference in conducting the system design for that region.Term 10.Scratch development: development in which the developer implements everythingTerminology


page 17