ITU-T Z 333-1988 METHODOLOGY FOR THE SPECIFICATION OF THE MAN-MACHINE INTERFACE - TOOLS AND METHODS《人机接口规范的方法论 工具和方法》.pdf
《ITU-T Z 333-1988 METHODOLOGY FOR THE SPECIFICATION OF THE MAN-MACHINE INTERFACE - TOOLS AND METHODS《人机接口规范的方法论 工具和方法》.pdf》由会员分享,可在线阅读,更多相关《ITU-T Z 333-1988 METHODOLOGY FOR THE SPECIFICATION OF THE MAN-MACHINE INTERFACE - TOOLS AND METHODS《人机接口规范的方法论 工具和方法》.pdf(20页珍藏版)》请在麦多课文档分享上搜索。
1、INTERNATIONAL TELECOMMUNICATION UNION)45G134 : TELECOMMUNICATIONSTANDARDIZATION SECTOROF ITU-!.G13-!#().%G0G0,!.5!%-%4(/$/,/9G0G0 what the system is supposed to do; what the user is supposed to do; the complexity of the job from the users perspective (see Note); the frequency of the job (see Note);
2、at which level in the network hierarchy the job is supposed to be performed (exchange, OMC); safety aspects.Note The following assumptions have been taken to better identify what is meant for “frequency” and“complexity” of a job.3.1.1.1 FrequencyLow: if the job is supposed to be performed weekly or
3、at longer intervals.Medium: if the job is supposed to be performed daily._1)The tools and methods may be improved on the basis of user experience leading to additions or revisions.2 Fascicle X.7 - Rec. Z.333High: if the job is supposed to be performed several times in a day.3.1.1.2 ComplexityLow: lo
4、w number of parameters (in general sense) max 0 : 3; most information associated with these parameters are not compound; there is no semantic relationship among different parameters and parameter values.Medium: the number of parameters is greater than 4 but less than 6-8; much information associated
5、 to these parameters is compound; there is no semantic relationship among parameters and/or parameter values.High: there are many parameters; most information associated to these parameters is compound; there are semantic relationships among parameters and/or parameter values.3.1.2 For Phase 4No spe
6、cific guidelines are provided for phase 2.3.1.3 For phase 3Three main categories of outputs can be identified within the MML function semantics specification, namely:1) Response outputs inside the dialogue to the operator inputs.2) Result outputs whose end-user is supposed to be the operator (e.g. r
7、esults of reporting or interrogationfunctions).3) Result outputs whose end-user is not assumed to be the operator (e.g. data collected for furtherelaborations).The partitioning of the output media to be used and its component information entities should not be pursued indetail, with the following gu
8、idelines: Output media and output characteristics to support the first category of output (output inside dialogue) willnot appear in the diagrams. Output media and output characteristics to support the second category will be as shown in Figure 1/Z.333.It is also recognized that the lower level of d
9、etail, whose definition will depend on the individualAdministrations needs, could in general include the information shown in Figure 2/Z.333.Fascicle X.7 - Rec. Z.333 3Output media to support outputs belonging to the third category will be shown if possible in the same way asthe previous point.3.1.4
10、 For phase 4To define individual menus and forms, follow the guidelines for the design of menus and forms as defined inRecommendation Z.323.To define the individual inputs and outputs:1) Consider what the system is supposed to do.2) Select options in the function information structure.3) Define the
11、information to be represented by the command code or equivalent.4) Define the information to be represented by the parameters and, if appropriate, their order.5) For each parameter, when appropriate, identify the: range of values, default values, information to be automatically supplied by the syste
12、m.6) Define the response outputs within dialogue, the interaction request outputs and outputs outside dialoguewhen applicable after considering the various mode operating sequences and the users reactions to theoutputs.4 Fascicle X.7 - Rec. Z.3337) Define the associated syntactic structure.8) Select
13、 terms and abbreviations for inputs and outputs.3.1.5 For phase 51) Define a preliminary operational procedure in functional terms.2) Finalize operational procedures.3.1.6 General guidelines1) Determine that the MML functions support the jobs to be performed.2) It will be necessary to consider: huma
14、n factor aspects; adequate allocation of authorities; adequate definition of responsibility; training of the user.3.1.7 Terminology harmonization guidelines for Phases 1-3To harmonize terminology:1) Utilize existing CCITT vocabulary.2) Select appropriate terms included in the general functional term
15、inology (Appendix I).3) Derive specific terms and their definitions pertinent to the functional area involved based on the followingconsiderations: common usage; specificity; translatability.3.2 ModellingModelling involves the use of description text and/or figures drawn either with the support of f
16、ormalsymbology and rules (formal modelling) or without such rules (informal modelling).3.2.1 The need for modelsA tool available is the construction of informal models of those parts of telecommunications systems whichhave been selected for MML control. Also the organization of the Administration co
17、uld be subject to modelling.Several models could apply when defining a job or an MML function. The use of models has the following advantages.Fascicle X.7 - Rec. Z.333 51) Models provide a means for the exchange of functional descriptions.2) The validity of the derived man-machine interface can be c
18、onsistently demonstrated by reference to therelevant models.3.2.2 Interpretation of modelsA model can be defined as an abstraction of a reality as seen from a certain viewpoint.In Z.300 Recommendations the viewpoint assumed is that of their users, i.e. Administration specifiers andsuppliers designer
19、s.Models should therefore be interpreted as high level specifications and are not aimed to represent, suggest orimply any particular implementation.They intend to provide only an overview in a conceptual sense of the information which is primarily relevantfor the control of each particular functiona
20、l area and of the main relationships among the various entities in the operatorperspective.Models produced expressly to determine the MML control structure are interpreted purely with that use inmind. Other models must lend themselves to the generation of MML control message sequences. CCITT feel bo
21、und toproduce models which can be linked with the methods for determining information structure of MML functions.3.3 MML function decompositionThe general MML functions are structured into component MML functions. Multiple levels of decompositionare allowed. For examples see the Annexes to this Reco
22、mmendation.3.4 Information structure meta-languageEach MML function identified at the lowest level of the MML function decomposition is structured into theinformation components needed to perform it. A top-down structuring is performed and multiple levels of informationdecomposition are allowed. The
23、 supporting tool is the meta-language presented below.An aid in understanding of information structuring is to view a MML function as an action on an object(s).Information composed may therefore relate either to objects or to actions.A general action associated with a MML function can be decomposed
24、into subsidiary actions and modifiers tothose actions. It is possible that no decomposition will take place. However, if decomposition is necessary, it should benoted that “decomposition“ with respect to actions means both determining subsidiary actions and determining anyqualifiers (modifiers, opti
- 1.请仔细阅读文档,确保文档完整性,对于不预览、不比对内容而直接下载带来的问题本站不予受理。
- 2.下载的文档,不会出现我们的网址水印。
- 3、该文档所得收入(下载+内容+预览)归上传者、原创作者;如果您是本文档原作者,请点此认领!既往收益都归您。
下载文档到电脑,查找使用更方便
10000 积分 0人已下载
下载 | 加入VIP,交流精品资源 |
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- ITUTZ3331988METHODOLOGYFORTHESPECIFICATIONOFTHEMANMACHINEINTERFACETOOLSANDMETHODS 人机 接口 规范 方法论 工具 方法

链接地址:http://www.mydoc123.com/p-806678.html