巻号一覧
42 巻 (2012)
- 4 号 p. 440-
- 3 号 p. 290-
- 2 号 p. 168-
- 1 号 p. 6-
42 巻, 4 号
選択された号の論文の12件中1～12を表示しています
- |<
- <
- 1
- >
- >|
特集
-
大島 啓二原稿種別: 特集 『我が国のソフトウェア品質技術の潮流 』
2012 年 42 巻 4 号 p. 440-447
発行日: 2012/10/15
公開日: 2017/08/30
ジャーナル 認証ありSoftware 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.抄録全体を表示PDF形式でダウンロード (956K) -
奈良 隆正原稿種別: 特集 『我が国のソフトウェア品質技術の潮流 』
2012 年 42 巻 4 号 p. 448-453
発行日: 2012/10/15
公開日: 2017/08/30
ジャーナル 認証ありThis 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.抄録全体を表示PDF形式でダウンロード (1351K) -
小笠原 秀人原稿種別: 特集 『我が国のソフトウェア品質技術の潮流 』
2012 年 42 巻 4 号 p. 454-459
発行日: 2012/10/15
公開日: 2017/08/30
ジャーナル 認証ありIn 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.抄録全体を表示PDF形式でダウンロード (1097K) -
野中 誠原稿種別: 特集 『我が国のソフトウェア品質技術の潮流 』
2012 年 42 巻 4 号 p. 460-466
発行日: 2012/10/15
公開日: 2017/08/30
ジャーナル 認証ありQuantitative 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.抄録全体を表示PDF形式でダウンロード (821K) -
吉澤 智美, 西 康晴原稿種別: 特集 『我が国のソフトウェア品質技術の潮流 』
2012 年 42 巻 4 号 p. 467-477
発行日: 2012/10/15
公開日: 2017/08/30
ジャーナル 認証ありRecently 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.抄録全体を表示PDF形式でダウンロード (1269K) -
飯泉 紀子原稿種別: 特集 『我が国のソフトウェア品質技術の潮流 』
2012 年 42 巻 4 号 p. 478-485
発行日: 2012/10/15
公開日: 2017/08/30
ジャーナル 認証ありThe 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.抄録全体を表示PDF形式でダウンロード (1023K) -
誉田 直美原稿種別: 特集 『我が国のソフトウェア品質技術の潮流 』
2012 年 42 巻 4 号 p. 486-494
発行日: 2012/10/15
公開日: 2017/08/30
ジャーナル 認証ありThis 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.抄録全体を表示PDF形式でダウンロード (1025K) -
渡辺 喜道, 兼子 毅原稿種別: 特集 『我が国のソフトウェア品質技術の潮流 』
2012 年 42 巻 4 号 p. 495-501
発行日: 2012/10/15
公開日: 2017/08/30
ジャーナル 認証ありSoftware 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.抄録全体を表示PDF形式でダウンロード (867K)
連載
-
越智 純一原稿種別: 連載 『ISO 26262 －自動車業界における機能安全に対する取り組み－』
2012 年 42 巻 4 号 p. 502-507
発行日: 2012/10/15
公開日: 2017/08/30
ジャーナル 認証ありISO 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.抄録全体を表示PDF形式でダウンロード (982K) -
－進藤晃先生(大久野病院院長)・進藤幸雄先生(進藤医院院長)へのインタビュー－水流 聡子, 加藤 省吾原稿種別: 連載 『医療・福祉機関における質・安全保証に関する取り組み』
2012 年 42 巻 4 号 p. 508-511
発行日: 2012/10/15
公開日: 2017/08/30
ジャーナル 認証ありWe 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.抄録全体を表示PDF形式でダウンロード (1121K)
論文誌編
報文
-
－回復期におけるADL向上を目的としたリハビリテーション－加藤 省吾, 石塚 渉, 進藤 晃, 水流 聡子, 飯塚 悦功原稿種別: 報文
2012 年 42 巻 4 号 p. 553-566
発行日: 2012/10/15
公開日: 2017/08/30
ジャーナル 認証あり日本では,社会の高齢化による病気や怪我のリスク増大に伴い,リハビリテーションの重要性が高まっている.一方, 2006年4月に実施された診療報酬制度の改訂により,医療保険が適用されるリハビリの期間が発症から最大180日に制限された.リハビリに対するニーズの高まり,保険制度面からの時間的制約により,リハビリの効果的・効率的な提供が求められている.リハビリは,医師が処方を出した後で,療法士が設計する訓練計画に基づいて行われる.しかしながら,療法士が訓練計画を設計する科学的な方法論は確立しておらず,訓練計画の設計は療法士個人に依存しているのが現状である.本研究では,療法士が訓練計画を設計する思考プロセスを可視化・構造化し,リハビリ訓練設計のための方法論を確立することを目的とする.回復期の患者に対して病院で行われる,日常生活の基盤であるADL (Activity of Daily Living)向上を目的とするリハビリテーションを対象として,リハビリ訓練設計過程の論理モデル,実装モデルを提案する.また,仮想患者に対して療法士が訓練計画を設計するワークショップにおいて,提案モデルの妥当性を確認する.抄録全体を表示PDF形式でダウンロード (2311K)
応用研究論文
-
秋山 浩一, 高木 智彦, 古川 善吾原稿種別: 応用研究論文
2012 年 42 巻 4 号 p. 567-576
発行日: 2012/10/15
公開日: 2017/08/30
ジャーナル 認証あり直交表を用いたHAYST法という組合せテスト技法は,組込み系ソフトウェアに対する品質向上とテストの効率化を目的として開発された.一方で,受注ソフトウェアの開発において,納品後の不具合に対して,対症療法的な対応がされているケースがあり,HAYST法を適用すべきであると考えた.しかし,HAYST法は,因子数に対してテストケース数が一次関数的に増加する傾向にあり,そのまま適用することはできなかった.そこで,HAYST法に拡張を行い,受注ソフトウェアに対してもHAYST法を適用することができることを確認した.受注ソフトウェアにおいては,顧客データのエラーの組合せパターンが多く,その作成が鍵であった.また,状態遷移図からテスト設計するのではなく状態変数の組合せを状態としてテストしたことで欠陥が検出できた.そして,グループ別に小さな直交表に割り付けて,それらを組み合わせることでテストケース数を削減した.納品後1年間,欠陥が検出されなかったことから,HAYST法が受注ソフトウェアのテストにおいても有効であることが確認できた.抄録全体を表示PDF形式でダウンロード (1076K)
- |<
- <
- 1
- >
- >|