2009 | ||
---|---|---|
35 | EE | Ryo Hasegawa, Motohiro Kitamura, Haruhiko Kaiya, Motoshi Saeki: Extracting Conceptual Graphs from Japanese Documents for Software Requirements Modeling. APCCM 2009: 87-96 |
34 | EE | Shunichi Suzuki, Akira Osada, Tomonori Sato, Haruhiko Kaiya, Masaaki Tanigawa, Kenji Kaijiri: A systematic method for generating quality requirements spectrum. SAC 2009: 399-400 |
2008 | ||
33 | EE | Motoshi Saeki, Haruhiko Kaiya: Supporting the Elicitation of Requirements Compliant with Regulations. CAiSE 2008: 228-242 |
32 | EE | Naoyuki Kitazawa, Akira Osada, Kazuyuki Kamijo, Haruhiko Kaiya, Kenji Kaijiri: So/M: A Requirements Definition Tool Using Characteristics of Existing Similar Systems. COMPSAC 2008: 255-262 |
31 | EE | Motoshi Saeki, Haruhiko Kaiya: Security Requirements Elicitation Using Method Weaving and Common Criteria. MoDELS Workshops 2008: 185-196 |
30 | EE | Yijun Yu, Haruhiko Kaiya, Hironori Washizaki, Yingfei Xiong, Zhenjiang Hu, Nobukazu Yoshioka: Enforcing a security pattern in stakeholder goal models. QoP 2008: 9-14 |
29 | EE | Daisuke Tanabe, Kohei Uno, Kinji Akemine, Takashi Yoshikawa, Haruhiko Kaiya, Motoshi Saeki: Supporting Requirements Change Management in Goal Oriented Analysis. RE 2008: 3-12 |
28 | EE | Haruhiko Kaiya, Tomonori Sato, Akira Osada, Naoyuki Kitazawa, Kenji Kaijiri: Toward quality requirements analysis based on domain specific quality spectrum. SAC 2008: 596-601 |
27 | EE | Akira Osada, Daigo Ozawa, Naoyuki Kitazawa, Haruhiko Kaiya, Kenji Kaijiri: Proposing metrics of difficulty of domain knowledge using usecase diagrams. SAC 2008: 624-629 |
26 | EE | Haruhiko Kaiya, Akira Osada, Kenji Kaijiri: Identifying Stakeholders and Their Preferences about NFR by Comparing Use Case Diagrams of Several Existing Systems. IEICE Transactions 91-D(4): 897-906 (2008) |
2007 | ||
25 | EE | Motoshi Saeki, Haruhiko Kaiya: Measuring Model Transformation in Model Driven Development. CAiSE Forum 2007 |
24 | EE | Masayuki Shibaoka, Haruhiko Kaiya, Motoshi Saeki: GOORE : Goal-Oriented and Ontology Driven Requirements Elicitation Method. ER Workshops 2007: 225-234 |
23 | Motohiro Kitamura, Ryo Hasegawa, Haruhiko Kaiya, Motoshi Saeki: An Integrated Tool for Supporting Ontology Driven Requirements Elicitation. ICSOFT (SE) 2007: 73-80 | |
22 | Junzo Kato, Motoshi Saeki, Atsushi Ohnishi, Haruhiko Kaiya, Shuichiro Yamamoto: Effects of Thesaurus in Requirements Elicitation. RCIS 2007: 385-394 | |
2006 | ||
21 | EE | Takako Nakatani, Haruhiko Kaiya: Japanese Workshop on Requirements Engineering Tools (JWRET). ASE 2006: 378 |
20 | Haruhiko Kaiya, Kouta Sasaki, Chikanobu Ogawa, Kenji Kaijiri: A Supporting Tool to Identify both Satisfied Requirements and Tolerant Threats for a Java Mobile Code Application. ICEIS (3) 2006: 444-448 | |
19 | EE | Haruhiko Kaiya, Kouta Sasaki, Kenji Kaijiri: PORTAM: Policy, Requirements and Threats Analyzer for Mobile Code Application. QSIC 2006: 125-132 |
18 | EE | Haruhiko Kaiya, Motoshi Saeki: Using Domain Ontology as Domain Knowledge for Requirements Elicitation. RE 2006: 186-195 |
17 | EE | Shuichiro Yamamoto, Haruhiko Kaiya, Karl Cox, Steven J. Bleistein: Goal Oriented Requirements Engineering: Trends and Issues. IEICE Transactions 89-D(11): 2701-2711 (2006) |
2005 | ||
16 | EE | Akira Osada, Daigo Ozawa, Haruhiko Kaiya, Kenji Kaijiri: Modeling Software Characteristics and Their Correlations in A Specific Domain by Comparing Existing Similar Systems. QSIC 2005: 215-222 |
15 | EE | Haruhiko Kaiya, Motoshi Saeki: Ontology Based Requirements Analysis: Lightweight Semantic Processing Approach. QSIC 2005: 223-230 |
14 | EE | Kazuma Aizawa, Haruhiko Kaiya, Kenji Kaijiri: Practical and Incremental Maintenance of Software Resources in Consumer Electronics Products. IEICE Transactions 88-D(6): 1117-1125 (2005) |
13 | EE | Haruhiko Kaiya, Daisuke Shinbara, Jinichi Kawano, Motoshi Saeki: Improving the detection of requirements discordances among stakeholders. Requir. Eng. 10(4): 289-303 (2005) |
2004 | ||
12 | EE | Haruhiko Kaiya, Motoshi Saeki: Weaving Multiple Viewpoint Specifications in Goal Oriented Requirements Analysis. APSEC 2004: 418-427 |
11 | EE | Kazuma Aizawa, Haruhiko Kaiya, Kenji Kaijiri: FC Method: A Practical Approach to Improve Quality and Efficiency of Software Processes for Embedded System Revision. COMPSAC 2004: 286-292 |
10 | EE | Haruhiko Kaiya, Akira Osada, Kenji Kaijiri: Identifying Stakeholders and Their Preferences about NFR by Comparing Use Case Diagrams of Several Existing Systems. RE 2004: 112-121 |
2003 | ||
9 | EE | Junzo Kato, Morio Nagata, Shuichiro Yamamoto, Motoshi Saeki, Haruhiko Kaiya, Hisayuki Horai, Atsushi Ohnishi, Seiichi Komiya, Kenji Watahiki: PAORE: Package Oriented Requirements Elicitation. APSEC 2003: 17- |
8 | EE | Hisayuki Suzumori, Haruhiko Kaiya, Kenji Kaijiri: VDM over PSP: A Pilot Course for VDM Beginners to Confirm its Suitability for Their Development. COMPSAC 2003: 327- |
7 | EE | Haruhiko Kaiya, Kouta Sasaki, Yasunori Maebashi, Kenji Kaijiri: Trade-off Analysis between Security Policies for Java Mobile Codes and Requirements for Java Application. RE 2003: 357-358 |
2002 | ||
6 | Haruhiko Kaiya, Hitoshi Furukawa, Kenji Kaijiri: Security Policy Checker and Generator for Java Mobile Codes. Engineering Information Systems in the Internet Context 2002: 255-264 | |
5 | EE | Haruhiko Kaiya, Hisayuki Horai, Motoshi Saeki: AGORA: Attributed Goal-Oriented Requirements Analysis Method. RE 2002: 13-22 |
1999 | ||
4 | EE | Haruhiko Kaiya, Kenji Kaijiri: Conducting Requirements Evolution by Replacing Components in the Current System. APSEC 1999: 224- |
1997 | ||
3 | EE | Haruhiko Kaiya, Nobuyuki Miura, Go Anai, Tsuyoshi Ebata, Hiroki Nagaoka, Motoshi Saeki: Preliminary experiments of a computer system for face-to-face meetings. Systems and Computers in Japan 28(2): 21-32 (1997) |
1996 | ||
2 | EE | Motoshi Saeki, Kinji Matsumura, Jun'ichi Shimoda, Haruhiko Kaiya: Structuring utterance records of requirements elicitation meetings based on speech act theory. ICRE 1996: 21-30 |
1995 | ||
1 | EE | Nobuyuki Miura, Haruhiko Kaiya, Motoshi Saeki: Building the Structure of Specification Documents from Utterances of Requirements Elicitation Meetings. APSEC 1995: 64- |