Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Hisayuki Horai

dblp:14/2213 · DBLP profile ↗
← Back
5ranked-venue papers
1as first author
0since 2021 · last 2003
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 5 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Requirements engineering and software design · 56% Program synthesis and code generation · 44%

Topics — the 2 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › specification
natural language specification
0.011989
Software Development Process from Natural Language Specification · ICSE 1989
Requirements engineering and software design › requirements analysis
natural language requirements analysis
0.011989
Software Development Process from Natural Language Specification · ICSE 1989

Methods — techniques the papers use, named apart from their topics

natural language processing · 0.0
YearPublicationVenuePosition
2003 PAORE: Package Oriented Requirements Elicitation
abstract
We propose a new requirements elicitation method in the domains of ERP, CRM, and SCM by using specifications of several existing package software. We have analyzed the requirements elicitation processes of experienced analysts in a specific domain, and found that they clarify requirements by referring the specifications of existing packages that seem to be satisfied with customer's needs. This process can be formulated into two subprocesses: 1) package selection, where an analyst compares the customer's needs with functions/nonfunctions of packages and selects the suitable candidates of packages; and 2) requirements evolution, where he examines the selected packages with his customer and an approved part of specifications of packages are added into their requirements. The proposed method, called PAORE (package oriented requirements elicitation method) is designed based on the analysis. We applied this method to a simple but realistic example of Web-based sales supporting system and assessed it.
Junzo Kato, Morio Nagata, Shuichiro Yamamoto, Motoshi Saeki, Haruhiko Kaiya, Hisayuki Horai, Atsushi Ohnishi, Seiichi Komiya, Kenji Watahiki
APSEC6
2002 AGORA: Attributed Goal-Oriented Requirements Analysis Method
abstract
This paper presents an extended version of the goal-oriented requirements analysis method called AGORA, where attribute values, e.g. contribution values and preference matrices, are added to goal graphs. An analyst attaches contribution values and preference values to edges and nodes of a goal graph respectively during the process for refining and decomposing the goals. The contribution value of an edge stands for the degree of the contribution of the sub-goal to the achievement of its parent goal, while the preference matrix of a goal represents the preference of the goal for each stakeholder. These values can help an analyst to choose and adopt a goal from the alternatives of the goals, to recognize the conflicts among the goals, and to analyze the impact of requirements changes. Furthermore the values on a goal graph and its structural characteristics allow the analyst to estimate the quality of the resulting requirements specification, such as correctness, unambiguity, completeness etc. The estimated quality values can suggest which goals should be improved and/or refined. In addition, we have applied AGORA to a user account system and assessed it.
Haruhiko Kaiya, Hisayuki Horai, Motoshi Saeki
RE2
2001 A Model for Navigating Interview Processes in Requirements Elicitation
abstract
Experts in requirements elicitation interview stakeholders using various levels of knowledge to grasp and elicit users' requirements. This paper analyzes expert interview processes and explores a computation model for simulating them. This model can be used to navigate a novice analyst's interview processes. It consists of a blackboard model and a state transition model in order to narrow the candidates for questions that an expert analyst will ask stakeholders next in the interview process. The candidates are selected based on information that has been elicited from stakeholders, and the blackboard model is for holding this information in the form of IEEE 830, a standard form of requirements specification documents. We have analyzed experts' interview processes and constructed a computation model in the sales management domain. We also recorded novice processes and showed that we could improve them by means of the model.
Junzo Kato, Seiichi Komiya, Motoshi Saeki, Atsushi Ohnishi, Morio Nagata, Shuichiro Yamamoto, Hisayuki Horai
APSEC7
1995 Flexible Module Operation Scheme in Formal Specification Process
abstract
We describe a fundamental and important activity named "Specification Generation" in the specification process which generates a specification from requirements, the output of the prior requirement process. We propose a new mechanism of specification languages which moderate requirements adding, deleting and changing. It follows our consideration concerning characteristics of requirements and requirements process. More concretely speaking, we provide a module operation mechanism of specification languages. The mechanism modifies modules and resolves conflicts which occur in case of the module operation if needed. Although we realise the mechanism by enhancing a multi sort functional language, we claim that the mechanism can be generally applicable to any specification languages which have modularity because the key issue of the mechanism is not "functional language" but "operation on modules".
Hisayuki Horai
APSEC1
1989 Software Development Process from Natural Language Specification
abstract
Article Software development process from natural language specification Share on Authors: Motoshi Saeki Tokyo Institute of Technology, 2-12-1 Ookayama, Meguro-ku, Tokyo 152, Japan Tokyo Institute of Technology, 2-12-1 Ookayama, Meguro-ku, Tokyo 152, JapanView Profile , Hisayuki Horai Fujitsu Limited IIAS-SIS, 1-17-25 Shin-Kamata, Oota-ku, Tokyo 144, Japan Fujitsu Limited IIAS-SIS, 1-17-25 Shin-Kamata, Oota-ku, Tokyo 144, JapanView Profile , Hajime Enomoto Fujitsu Limited IIAS-SIS, 1-17-25 Shin-Kamata, Oota-ku, Tokyo 144, Japan Fujitsu Limited IIAS-SIS, 1-17-25 Shin-Kamata, Oota-ku, Tokyo 144, JapanView Profile Authors Info & Claims ICSE '89: Proceedings of the 11th international conference on Software engineeringMay 1989 Pages 64–73https://doi.org/10.1145/74587.74594Published:15 May 1989 26citation846DownloadsMetricsTotal Citations26Total Downloads846Last 12 Months63Last 6 weeks14 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteGet Access
Motoshi Saeki, Hisayuki Horai, Hajime Enomoto
ICSE2