All issues
Volume 42 (2012)
- Issue 4 Pages 440-
- Issue 3 Pages 290-
- Issue 2 Pages 168-
- Issue 1 Pages 6-
Volume 42, Issue 4
Displaying 1-12 of 12 articles from this issue
- |<
- <
- 1
- >
- >|
Features
-
Keiji OSHIMAArticle type: Features 〔Trends and Futures of Software Quality Technologies in Japan〕
2012 Volume 42 Issue 4 Pages 440-447
Published: October 15, 2012
Released on J-STAGE: August 30, 2017
JOURNAL RESTRICTED ACCESSSoftware has various aspects of character. While it is hard to handle, it sometimes brings about unexpected value. Therefore, discussing the quantity of its fault could not escape the charge of "not seeing the wood for the trees". The author has been in charge of the development of large scale software systems, embedded systems, software engineering, and also management of the software development project for many years. This paper describes, based on those experiences, the various properties and interesting points of software from its quality or value's point of view while comparing it with hardware. In this paper, there is no formal classification or any arrangement, some ideas are just hitting on, and not taking "MECE" among categories into consideration, so there may be some redundancies of the contents. The author hopes that you read this paper with some feelings such as "That's interesting !" or "That may not be correct", and so on. The author believes that it is possible to make an approach to the essential of software through a warm debate sprinkled with objections or refutations, and pursue the potential of it by struggling for the problem which confronts us. The readers of this paper are expected to be related to software, to be concrete, software developers, managers, quality assurance members, users, and also hardware engineers.View full abstractDownload PDF (956K) -
Takamasa NARAArticle type: Features 〔Trends and Futures of Software Quality Technologies in Japan〕
2012 Volume 42 Issue 4 Pages 448-453
Published: October 15, 2012
Released on J-STAGE: August 30, 2017
JOURNAL RESTRICTED ACCESSThis paper shows fundamentals and historical growth of software quality management (SQM) and assurance (SQA) in Japan from 1980s. Early activities of SQM/SQA began by simply applying concepts and techniques of statistical quality control (SQC) and total quality management (TQM) for hardware manufacturing. They consisted of three approaches : analysis and clarification of actual problems, continuous improvement named PDCA cycle or Deming cycle and Seven QC tools. Next activities of SQM/SQA were adaptations of concepts and techniques of SQC/TQM for hardware. One of major instance was a control chart adapted to software testing for visualizing and grasping. It made advances to statistical analysis of software bugs and test criteria, reorganization of concepts and techniques of tests and reviews, and expansion of scope of SQM/SQA from testing-limited activity into process-wide quality management such as process assessment and improvement. Modern activities have been caused by rapidly increasing software size and complexity as well as number of developers. They have focused on reinforcement of organizational framework such as establishment of software quality assurance divisions and project management offices for continuous company-wide quality management.View full abstractDownload PDF (1351K) -
Hideto OGASAWARAArticle type: Features 〔Trends and Futures of Software Quality Technologies in Japan〕
2012 Volume 42 Issue 4 Pages 454-459
Published: October 15, 2012
Released on J-STAGE: August 30, 2017
JOURNAL RESTRICTED ACCESSIn recent years, software has come to be used increasingly in various domains. Consequently, the scale and complexity of software is increasing, and development organizations are becoming large. In order to build in higher quality and develop large-scale or complex software efficiently, it is necessary to implement the optimum software development process in a development organization. Indeed, the development process of software has become a focus of attention in recent years. The various process models and software development methods which are represented by Capability Maturity Model Integration (CMMI) and agile software development are proposed. However, in order to improve a software development process efficiently, it is not necessarily sufficient just to introduce such an existing process improvement technique. Regarding the improvement of a software development process, a Quality Management System (QMS) is an important factor in determining success or failure. Thus, for the effective introduction of new process and techniques in a organization, it is necessary to establish the framework of fundamental software quality control. This paper explains the outline and history of QMS, and shows how software process improvement activities should be promoted with some practical examples.View full abstractDownload PDF (1097K) -
Makoto NONAKAArticle type: Features 〔Trends and Futures of Software Quality Technologies in Japan〕
2012 Volume 42 Issue 4 Pages 460-466
Published: October 15, 2012
Released on J-STAGE: August 30, 2017
JOURNAL RESTRICTED ACCESSQuantitative management of software development projects is one of the most common practices among Japanese software organizations. It is usually driven by a support division such as a software quality management group to help software development divisions to focus on transforming customer requirements into software. However, quantitative management is not always considered as a meaningful practice by developments. There are at least three challenges for effective quantitative management to cooperate with both support and development divisions for excellent software quality. The three challenges include : (1) focus on external quality requirements to be excellence, (2) evaluation of internal quality in contract-based software development, and (3) utilization of process quality data to reveal mechanisms of software quality improvement. A support division needs to play an important role on quantitative management of software quality to drive organizational continuous improvement.View full abstractDownload PDF (821K) -
Satomi YOSHIZAWA, Yasuharu NISHIArticle type: Features 〔Trends and Futures of Software Quality Technologies in Japan〕
2012 Volume 42 Issue 4 Pages 467-477
Published: October 15, 2012
Released on J-STAGE: August 30, 2017
JOURNAL RESTRICTED ACCESSRecently the more large-scale and complicated software are, the more large-scale and complicated test cases are also. Traditional software testing techniques are not so powerful for large-scale and complicated test cases. This paper shows forefront software testing and front-loading technologies and in Japan. First we categorize purposes of software testing as pinpoint testing and exhaustive testing. Pinpoint testing aims at detecting bugs while exhaustive testing aims at making evidences of quality. Second we introduce pinpoint testing technology based on patterns of bugs as well as exploratory testing as application of bug patterns. Third we discuss exhaustive testing technologies focusing on test viewpoints. The concept of test viewpoint makes it possible to establish test architecture model for grasping big picture of large-scale and complicated test cases. Next we mention combinatorial testing and critical combination analysis (CCA). CCA can reduce complication of software and number of combinatorial test cases by encourage refining "hot spots" of software design. Moreover, risk-based testing, automation and process are other approaches mentioned for large-scale and complicated test cases. Finally we describe front-loading technology of testing named W model for obtain extremely excellent software quality.View full abstractDownload PDF (1269K) -
Noriko IIZUMIArticle type: Features 〔Trends and Futures of Software Quality Technologies in Japan〕
2012 Volume 42 Issue 4 Pages 478-485
Published: October 15, 2012
Released on J-STAGE: August 30, 2017
JOURNAL RESTRICTED ACCESSThe latest software development tends to become a modification type development which develops the target software by changing the existing software. Modification type development requires both domain-specific knowledge and programming skills in severe constraint of time for delivery. In order to overcome this difficulty, many organizations have groped for and adopted the success cases. However, the organizations are faced with obstacles. These problems are caused by lack of understanding of each organization's situation, and shortage of devices for fitting the organization. The primary purpose of this paper is to propose an approach of built-in quality by engineer itself in consideration of the strong point and weak point of an organization. By analyzing the fault of the software, weakness and skill level of organization become clear. The effect of built-in quality is led by understanding the prerequisite of success cases correctly and practicing a countermeasure. In fact, two cases introduced in this paper demonstrate this. Accumulating built-in quality experience becomes the continuous capability of an organization as well as engineers' confidence.View full abstractDownload PDF (1023K) -
Naomi HONDAArticle type: Features 〔Trends and Futures of Software Quality Technologies in Japan〕
2012 Volume 42 Issue 4 Pages 486-494
Published: October 15, 2012
Released on J-STAGE: August 30, 2017
JOURNAL RESTRICTED ACCESSThis paper introduces the results of quality improvement activities at a CMMI level 5 organization by tracking for four years. Based on the results and other examples of several Japanese companies, a realization model of software quality beyond CMMI level 5 is proposed.View full abstractDownload PDF (1025K) -
Yoshimichi WATANABE, Takeshi KENEKOArticle type: Features 〔Trends and Futures of Software Quality Technologies in Japan〕
2012 Volume 42 Issue 4 Pages 495-501
Published: October 15, 2012
Released on J-STAGE: August 30, 2017
JOURNAL RESTRICTED ACCESSSoftware division of JSQC makes a study on the arrangement and the systematization of practical knowledge of software development. There are many textbooks about software development or software engineering. Many of them are, however, the textbooks overemphasized in theoretical knowledge. There are many troubles in actual software development, and there is almost no software development which goes smoothly. Under the circumstance, the software division of JSQC collected and systematized the knowledge which is useful in the spot of practice. Its activity of knowledge collection is called the last word project as a term of endearment. The result of the last word project is shown in this article. The knowledge is described not only in a formal description but in narrative depiction form. It is easy to understand a narrative depiction for a beginner. In this article, the feature of the last word project and 3 teachings stored in the last word project are described.View full abstractDownload PDF (867K)
Serial
-
Junichi OCHIArticle type: Serial [ISO 26262 –Approaches to Functional Safety in Automotive Industry-]
2012 Volume 42 Issue 4 Pages 502-507
Published: October 15, 2012
Released on J-STAGE: August 30, 2017
JOURNAL RESTRICTED ACCESSISO 26262, "Road Vehicles-Functional Safety", has been valid since the end of 2011. The standard regulates the functional safety of electrical and electronic systems of road vehicles for the first time. Some of the requirements of ISO 26262 were formulated in an abstract and visionary way because this standard was intended to reflect the "state of the art" of the automotive industry on the one hand, but wanted to orientate also on future safety designs of automotive E/E systems on the other hand. Therefore the appropriate interpretations of ISO 26262 in the global automotive industry are necessary which could be different and confusing and could therefore lead to extensive product-adaptations. The goal of ISO 26262 is not to revolutionize the development of safety relevant systems. Rather, it seeks to reflect the real situation in the automotive industry. The standard should be interpreted based on the established state of the art. Bosch shows where some risks of such different interpretations may lie and how they can be dealt with and show that this is possible in an efficient way that considers the intention of ISO 26262.View full abstractDownload PDF (982K) -
–Interview with Akira Shindo (director, Ooguno Hospital) and Yukio Shindo (director, Shindo clinic)Satoko TSURU, Shogo KATOArticle type: Serial [Activity for Quality and Safety Assurance in Healthcare and Social Service]
2012 Volume 42 Issue 4 Pages 508-511
Published: October 15, 2012
Released on J-STAGE: August 30, 2017
JOURNAL RESTRICTED ACCESSWe interviewed Dr. Akira Shindo (Director, Ooguno Hospital) and Dr. Yukio Shindo (Director, Shindo Clinic), who is the younger brother of Akira Shindo. Ooguno Hospital is a recovery stage hospital in Nishi-Tama, Tokyo, and there are 158 beds, with a total employee count of 220 (4 doctors, 41 nurses, 36therapists). Shindo Clinic is a satellite of Ooguno Hospital with a total employee count of 4 (1 doctor and 1 nurse). They started Ooguno Hospital in the current management setup at 1996, and started activities for quality and safety assurance from around 2005. Then, they started Shindo Clinic as a satellite at 2011, because they considered that it is necessary to cover the whole services they want to provide in the recovery stage and chronic stage. Their activities are progressing with specifying their service and customers, which are different from acute hospitals. Interview contents are (1) History of Ooguno Hospital and Shindo Clinic, (2) Services and customers in the recovery stage and chronic stage 1, (3) History and organizational efforts forquality assurance and management (Process Flow Chart, internal audit, problem-resolution), (4) Difficulty and special efforts, and (5) Future aspect.View full abstractDownload PDF (1121K)
Research Papers
Contributed Paper
-
- Rehabilitation for Improving ADL at Recovery Stage -Shogo KATO, Wataru ISHIZUKA, Akira SHINDO, Satoko TSURU, Yoshinori IIZ ...Article type: Contributed Paper
2012 Volume 42 Issue 4 Pages 553-566
Published: October 15, 2012
Released on J-STAGE: August 30, 2017
JOURNAL RESTRICTED ACCESSIn Japan, the importance of rehabilitation is increasing as people face the growing risk of disease and injury, with aging society. Along with the amendment of the medical service fee system enforced in April 2006, length of rehabilitation program covered by medical care insurance is limited to 180 days at maximum from onset. On one hand, greater time pressure is imposed on rehabilitation by the medical care insurance scheme, and on the other hand, needs for rehabilitation are ever growing. To address these challenges, it is required to provide rehabilitation services more effectively and efficiently. Rehabilitation services are provided in accordance with a rehabilitation program, which is designed by therapists according to a doctor's prescription. However, a scientific methodology for designing a rehabilitation program has not been established, and it depends on the personal ability of each therapist. In this paper, we aim to establish a methodology for designing a rehabilitation program by visualizing and structuring the thinking process of therapists. We propose a logical model and implementation model, focusing on rehabilitation, which is provided to improve ADL ability of a patient in a hospital at recovery stage. Then, we make a verification to assess the validity of our model, through a workshop, in which therapists designed rehabilitation program for a supposed patient.View full abstractDownload PDF (2311K)
Applied Research
-
Kouichi AKIYAMA, Tomohiko TAKAGI, Zengo FURUKAWAArticle type: Applied Research
2012 Volume 42 Issue 4 Pages 567-576
Published: October 15, 2012
Released on J-STAGE: August 30, 2017
JOURNAL RESTRICTED ACCESSThe HAYST method that is a combination software testing technique using orthogonal array has been developed to improve the quality and efficiency of testing for embedded software. On the other hand, I thought it should be applied HAYST method for large scale business software. Because there is a case of symptomatic handling like a whack-a-mole game for defects after delivery. However, HAYST method has tended to increase in linear scale of test cases for the count of factors ; it could not be applied directly. So, HAYST method was added some extension for to confirm that the method can be applied even for large scale business software. In large scale business software, there are many combinations of errors in customer data patterns, these patterns creation is the key for success. And, defects can be detected by testing a combination of state variables rather than designing the test from the state diagram. And, each group assigned to a small orthogonal array, which reduces the number of test cases by combining them. 1 year after delivery of the defects were not detected, It's confirmed that HAYST method is effective in large scale business software.View full abstractDownload PDF (1076K)
- |<
- <
- 1
- >
- >|