由於消費性電子產品的市場競爭激烈,產品的種類不斷地推陳出新,許多廠商也紛紛成立設計團隊,希望能設計出良好的產品介面,來提升產品的競爭力。為了研究如何降低設計師的工作負擔,並提昇產品介面的品質,本研究以手機選單操作介面為主,利用案例式推理軟體(CBR-Works)建構一套手機選單操作介面設計之案例式推理系統,並找一組設計團隊實際運用本系統來輔助設計手機選單操作介面。另外再找一組設計團隊在不使用本系統的狀況下來設計手機選單操作介面作為對照組。最後利用RapidPLUS這套產品使用者介面開發工具來模擬這兩組手機選單介面的原型並進行實驗。 在介面設計的過程中,由於本研究的手機選單操作介面設計之案例式推理系統將手機劃分出許多屬性,因此第一組設計師在使用這套系統時,隨著每一項屬性的設定,設計師便會很自然地開始構思該屬性的類別,並會去思考各屬性之間的相關問題。而當系統回傳的資料出現案例調適時,除了能提供設計師較佳的設計案例,也能讓設計師注意到為何系統會對該案例屬性做出這樣的調適,進而引發設計師對於該法則做出更多的聯想與應用。 在介面的編排上,第一組設計師所設計的介面A與第二組設計師所設計的介面B有著許多不同點。首先在主選單的編排方式,兩組介面皆採用矩陣式,但是在排列上有點不同,介面A的說明文字擺在螢幕的下緣,介面B則是擺在螢幕的正中央。在子選單的編排方式介面A採用條列式,介面B則採用翻頁式。在功能鍵的部分,兩組介面的差異性就更明顯了,介面A的進入鍵為偏左的硬體鍵,返回鍵為偏右的硬體鍵,功能表鍵則為置中的軟體鍵;介面B的進入鍵為偏右的軟體鍵,返回鍵為偏左的軟體鍵,功能表鍵則為置中的硬體鍵。經過實驗測試與統計分析後發現,在(1)子選單目標功能項目搜尋的累計多餘步驟次數、(2)開啟選項功能畫面的累計操作錯誤次數、(3)總累計多餘步驟次數以及(4)總累計操作時間,介面A的操作績效均優於介面B。由此驗證本研究所建構的手機選單操作介面設計之案例式推理系統的確可以有效提升產品介面設計的品質,希望藉由本文的研究能讓各界對手機選單操作介面設計之案例式推理系統有更進一步的了解,進而共同研發相關的系統來協助未來的設計師,減輕其工作的負擔,並提升產品介面的品質。
Due to intensive competition in the market of consumer electronics, new products are being launched with relatively short life cycles. Many manufacturers have established in-house design team in hope of designing ideal product interfaces that enhance competitiveness of their products. With a purpose to reduce workload of designers and improve quality of product interface, this paper focused on mobile phone menu interfaces. Case based reasoning software (CBR-Works) was applied in the construction of a case based reasoning system for mobile phone menu interface design. A design team was aided with this system in the design of mobile phone menu operation interface, while another team, as the control group, was not given this system. Finally, RapidPLUS, a product user interface development tool, was used in the simulation of these two mobile phone menu interface prototypes for experiment. In the process of interface design, the case based reasoning system for mobile phone menu interface design extracted many mobile phone attributes. Therefore, designers of the Group 1 who were aided by this system naturally consider attribute values and the correlations between attributes. And when the system conducts case adaptation, not only that better design cases are provided to the designer but that designers can be reminded to notice why the system conducted such adjustment on the case attribute. Thus, for the designers, more thinking and applications of the rules may be inspired. As for the interface layout, numerous differences were found between Interface A designed by designers of Group 1 and Interface B of Group 2. First, both groups adopted matrix style for the main menu, but their layouts differed. Interface A had the texts disposed in the lower part of the display screen while Interface B had it in the center. Second, Interface A applied lists in the submenu while Interface B adopted page type. Greater difference is found in the function keys. Interface A used the left hard key for “enter”, right hard key for “back”, and the soft key in the middle for menu button, while Interface B had the right soft key as “enter”, left soft key for “back”, and hard key in the middle for menu button. Experimental tests and statistical analysis revealed that operation performance of Interface A surpassed Interface B in the following aspects: (1) Accumulative redundant step count in the navigation of target submenu function item, (2) Accumulative operation error count while opening the target function menu, (3) Total accumulative redundant step count, and (4) Total accumulative operation time. Thus it is verified that the case based reasoning system constructed in this study may indeed effectively improve the quality of product interface design of mobile phones. It is hoped that this paper may provide further understanding on the case based reasoning system for menu interface design of mobile phone among the public, so as to promote collaboration in the development of relevant systems that help future designers reduce workload, and thus enhance the quality of product interface.