{"_buckets": {"deposit": "d59a6bf4-5e7f-49bf-b136-bec6358c9fb2"}, "_deposit": {"id": "12373", "owners": [], "pid": {"revision_id": 0, "type": "depid", "value": "12373"}, "status": "published"}, "_oai": {"id": "oai:soar-ir.repo.nii.ac.jp:00012373", "sets": ["1221:1222"]}, "item_6_biblio_info_6": {"attribute_name": "\u66f8\u8a8c\u60c5\u5831", "attribute_value_mlt": [{"bibliographicIssueDates": {"bibliographicIssueDate": "2012-04", "bibliographicIssueDateType": "Issued"}, "bibliographicIssueNumber": "4", "bibliographicPageEnd": "1043", "bibliographicPageStart": "1031", "bibliographicVolumeNumber": "E95D", "bibliographic_titles": [{"bibliographic_title": "IEICE TRANSACTIONS ON INFORMATION AND SYSTEMS"}]}]}, "item_6_description_20": {"attribute_name": "\u6284\u9332", "attribute_value_mlt": [{"subitem_description": "Defining quality requirements completely and correctly is more difficult than defining functional requirements because stakeholders do not state most of quality requirements explicitly. We thus propose a method to measure a requirements specification for identifying the amount of quality requirements in the specification. We also propose another method to recommend quality requirements to be defined in such a specification. We expect stakeholders can identify missing and unnecessary quality requirements when measured quality requirements are different from recommended ones. We use a semi-formal language called X-JRDL to represent requirements specifications because it is suitable for analyzing quality requirements. We applied our methods to a requirements specification, and found our methods contribute to defining quality requirements more completely and correctly.", "subitem_description_type": "Abstract"}]}, "item_6_description_30": {"attribute_name": "\u8cc7\u6e90\u30bf\u30a4\u30d7\uff08\u30b3\u30f3\u30c6\u30f3\u30c4\u306e\u7a2e\u985e\uff09", "attribute_value_mlt": [{"subitem_description": "Article", "subitem_description_type": "Other"}]}, "item_6_description_5": {"attribute_name": "\u5f15\u7528", "attribute_value_mlt": [{"subitem_description": "IEICE TRANSACTIONS ON INFORMATION AND SYSTEMS. E95D(4):1031-1043 (2012)", "subitem_description_type": "Other"}]}, "item_6_link_67": {"attribute_name": "WoS", "attribute_value_mlt": [{"subitem_link_text": "Web of Science", "subitem_link_url": "http://gateway.isiknowledge.com/gateway/Gateway.cgi?\u0026GWVersion=2\u0026SrcAuth=ShinshuUniv\u0026SrcApp=ShinshuUniv\u0026DestLinkType=FullRecord\u0026DestApp=WOS\u0026KeyUT=000302834400013"}]}, "item_6_publisher_4": {"attribute_name": "\u51fa\u7248\u8005", "attribute_value_mlt": [{"subitem_publisher": "IEICE-INST ELECTRONICS INFORMATION COMMUNICATIONS ENG"}]}, "item_6_relation_46": {"attribute_name": "\u4ed6\u306e\u8cc7\u6e90\u3068\u306e\u95a2\u4fc2\uff1aURI", "attribute_value_mlt": [{"subitem_relation_name": [{"subitem_relation_name_text": "http://search.ieice.org/"}], "subitem_relation_type_id": {"subitem_relation_type_id_text": "http://search.ieice.org/", "subitem_relation_type_select": "URI"}}]}, "item_6_relation_48": {"attribute_name": "DOI", "attribute_value_mlt": [{"subitem_relation_name": [{"subitem_relation_name_text": "10.1587/transinf.E95.D.1031"}], "subitem_relation_type_id": {"subitem_relation_type_id_text": "http://dx.doi.org/10.1587/transinf.E95.D.1031", "subitem_relation_type_select": "DOI"}}]}, "item_6_rights_62": {"attribute_name": "\u6a29\u5229", "attribute_value_mlt": [{"subitem_rights": "Copyright\u00a9 2012 IEICE"}]}, "item_6_select_64": {"attribute_name": "\u8457\u8005\u7248\u30d5\u30e9\u30b0", "attribute_value_mlt": [{"subitem_select_item": "publisher"}]}, "item_6_source_id_35": {"attribute_name": "ISSN", "attribute_value_mlt": [{"subitem_source_identifier": "0916-8532", "subitem_source_identifier_type": "ISSN"}]}, "item_6_source_id_39": {"attribute_name": "NII ISSN", "attribute_value_mlt": [{"subitem_source_identifier": "0916-8532", "subitem_source_identifier_type": "ISSN"}]}, "item_6_source_id_40": {"attribute_name": "\u66f8\u8a8c\u30ec\u30b3\u30fc\u30c9ID", "attribute_value_mlt": [{"subitem_source_identifier": "AA10826272", "subitem_source_identifier_type": "NCID"}]}, "item_6_text_69": {"attribute_name": "wosonly authkey", "attribute_value_mlt": [{"subitem_text_value": "requirements analysis; case frame; quality requirements; spectrum analysis"}]}, "item_6_text_70": {"attribute_name": "wosonly keywords", "attribute_value_mlt": [{"subitem_text_value": "SPECTRUM ANALYSIS"}]}, "item_6_textarea_68": {"attribute_name": "wosonly abstract", "attribute_value_mlt": [{"subitem_textarea_value": "Defining quality requirements completely and correctly is more difficult than defining functional requirements because stakeholders do not state most of quality requirements explicitly. We thus propose a method to measure a requirements specification for identifying the amount of quality requirements in the specification. We also propose another method to recommend quality requirements to be defined in such a specification. We expect stakeholders can identify missing and unnecessary quality requirements when measured quality requirements are different from recommended ones. We use a semi-formal language called X-JRDL to represent requirements specifications because it is suitable for analyzing quality requirements. We applied our methods to a requirements specification, and found our methods contribute to defining quality requirements more completely and correctly."}]}, "item_creator": {"attribute_name": "\u8457\u8005", "attribute_type": "creator", "attribute_value_mlt": [{"creatorNames": [{"creatorName": "Kaiya,  Haruhiko"}], "nameIdentifiers": [{"nameIdentifier": "37650", "nameIdentifierScheme": "WEKO"}]}, {"creatorNames": [{"creatorName": "Ohnishi,  Atsushi"}], "nameIdentifiers": [{"nameIdentifier": "37651", "nameIdentifierScheme": "WEKO"}]}]}, "item_files": {"attribute_name": "\u30d5\u30a1\u30a4\u30eb\u60c5\u5831", "attribute_type": "file", "attribute_value_mlt": [{"accessrole": "open_date", "date": [{"dateType": "Available", "dateValue": "2015-09-28"}], "displaytype": "detail", "download_preview_message": "", "file_order": 0, "filename": "Finding_Incorrect_Missing_Quality_Requirements_Definitions.pdf", "filesize": [{"value": "574.6 kB"}], "format": "application/pdf", "future_date_message": "", "is_thumbnail": false, "licensetype": "license_free", "mimetype": "application/pdf", "size": 574600.0, "url": {"label": "Finding_Incorrect_Missing_Quality_Requirements_Definitions.pdf", "url": "https://soar-ir.repo.nii.ac.jp/record/12373/files/Finding_Incorrect_Missing_Quality_Requirements_Definitions.pdf"}, "version_id": "40878026-a2d4-481e-9f42-04b1579d292b"}]}, "item_keyword": {"attribute_name": "\u30ad\u30fc\u30ef\u30fc\u30c9", "attribute_value_mlt": [{"subitem_subject": "requirements analysis", "subitem_subject_scheme": "Other"}, {"subitem_subject": "case frame", "subitem_subject_scheme": "Other"}, {"subitem_subject": "quality requirements", "subitem_subject_scheme": "Other"}, {"subitem_subject": "spectrum analysis", "subitem_subject_scheme": "Other"}]}, "item_language": {"attribute_name": "\u8a00\u8a9e", "attribute_value_mlt": [{"subitem_language": "eng"}]}, "item_resource_type": {"attribute_name": "\u8cc7\u6e90\u30bf\u30a4\u30d7", "attribute_value_mlt": [{"resourcetype": "journal article", "resourceuri": "http://purl.org/coar/resource_type/c_6501"}]}, "item_title": "Finding Incorrect and Missing Quality Requirements Definitions Using Requirements Frame", "item_titles": {"attribute_name": "\u30bf\u30a4\u30c8\u30eb", "attribute_value_mlt": [{"subitem_title": "Finding Incorrect and Missing Quality Requirements Definitions Using Requirements Frame"}]}, "item_type_id": "6", "owner": "1", "path": ["1221/1222"], "permalink_uri": "http://hdl.handle.net/10091/17153", "pubdate": {"attribute_name": "\u516c\u958b\u65e5", "attribute_value": "2013-09-18"}, "publish_date": "2013-09-18", "publish_status": "0", "recid": "12373", "relation": {}, "relation_version_is_last": true, "title": ["Finding Incorrect and Missing Quality Requirements Definitions Using Requirements Frame"], "weko_shared_id": null}