Method of Validation. Item OITM Batch OBTN From Warehouse OWHS From Bin OBIN To Warehouse OWHS To Bin OBIN Quantity Serial OSRN Edits Condition Special Circumstance Default Warehouse User Defined Quantity not greater than Quantity on Hand Quantity entered <=0 Function Keys Key Function F1 Show Menu F4 Exit F5 Search Considerations
Method of Validation process (i.e., study time frame, staff involved, request for record and review process)
Method of Validation. Shipping Point TVST table CIMCU Delivery Document LIKPUK table CIMCU Pack Material BAPI_MATERIAL_GET_DETAIL Material BAPI_MATERIAL_GET_DETAIL Line LIPSUP Serial EQUI and JEST Quantity Edits Condition Special Circumstance Default Branch Plant User Defined Quantity not greater than Quantity on Hand Quantity entered < = 0 Function Keys Key Function F3 Exit F5 Search Data for Current Field Considerations
Method of Validation usability case 26 6.3 Results of validation 30 Promisingness of COPE technology concept 30 Overall user experience 34
Method of Validation usability case The approach that we used to define the innovative features of COPE technology concept has been developed at VTT in some earlier design connections. The idea for the development of this method was borrowed from the well known case-based reasoning process used in checking the fulfilment of safety demands of complex systems, i.e. the safety case (Xxxxxx & Bloomfield, 1998). Our innovation was to develop a “usability case” for checking the aim of systems usability demands, fulfilment of which would speak of the promisingness of complex human-system interaction concepts for future work (Liinasuo & Xxxxxx, 2007). The original safety case concept was adapted to the needs of a usability case: Our experience in participating in design processes shows that there is a need for systematic procedures to provide evaluations and inputs into the design process. The first actual design case, in which the usability case approach was used, was when the task was to evaluate a new decision support system concept to be used in a ICT-based precision agriculture (included in Pesonen, Koskinen, & Xxxxxxx, 2008). The next development of the usability case was made in an on- going EURATOM project MMOTION in which a pilot exercise was accomplished for testing an innovative control room design with this method (Xxxxxx et al. 2010 at xxxx://xxxxxxx.xxx. In the case-based usability evaluation the reasoning about the quality of the system to be evaluated follows the logic proposed by Xxxxxx and Xxxxxxxxxx (1998) for safety case. In the evaluation a case is build and tested. The case is a documented body of evidence that provides a convincing and valid argument that a system is adequate for a given application in a given environment. Three concepts are used to structure usability information in both safety case and the usability case. Claims are entities that express the quality of the system in terms of usability. The abstraction level of a claim is high but various viewpoints and levels of detail are possible. Each claim comprehends of one or more arguments that are instrumental descriptions supporting the claim in question. Finally, each argument is based on evidence, that is, various data. The representation of claims, arguments and evidence is to be as a clear and extensive way to describe the status of usability. In the adaptation of the case-based reasoning to design contexts we made, however, some innovations concerning the formulation of claims ( in Xxxxxxx et al....
Method of Validation. Plant T001W table Material BAPI_MATERIAL_GETLIST Batch BAPI_MATERIAL_GETBATCHES Function Keys Key Function F3 Exit F4 Search Data for Current Field F8 Submit value for the Current Screen Display SAP Programs – Reference SAP Stock Overview: MMBE Test Script Description: Location Inquiry by Material RFgen Input Requirements Before you begin testing, ensure, for the combination of plant(s) and material(s) you will be testing, that the following is setup in SAP.
Method of Validation. Delivery Document ODLN Package Type DLN7 Quantity Edits Condition Special Circumstance Quantity not greater than Quantity on Hand Quantity entered < = 0 Function Keys Key Function F1 Show Menu F4 Exit F5 Search SAP Business One Programs – Reference Packing Slip Overview Basic Test Script
Method of Validation. Material Document MSEG table CIMCU Material Document Year MSEG table Line MSEG table Edits Condition Special Circumstance Function Keys Key Function F3 Exit F5 Search Data for Current Field SAP Programs – Reference SAP Cancel Material Document: MBST Basic Test Script
Method of Validation. Warehouse Not Validated Inventory Document LINK table with Status in I or A Recount LINV Bin LAGP Material BAPI_MATERIAL_GETLIST and must be in Cycle Count Batch Validated against the Cycle Count document Quantity Numeric and non-negative Plant T001W Edits Condition Special Circumstance Default Branch Plant User Defined Quantity entered < 0 Function Keys Key Function F3 Exit F5 Search Data for Current Field Considerations
Method of Validation. Plant T001W table CIMCU Delivery Document LIKPUK table CIMCU Material BAPI_MATERIAL_GET_DETAIL Location Must be the same as the displayed suggestion Bin Must be the same as the displayed suggestion Material Must be the same as the displayed suggestion Batch MCHB or LQUA Serial EQUI and JEST Quantity Edits
