3. INTERNATIONAL STANDARDS GENERIC VIEW OF FURAccording to ISO/IEC 14143-1:2007 [34], functional size measurement method (FSM), designed to overcome the limitations of past software sizing methods. As a result, we are coming up with a set of observations in terms of the ISO/IEC 19761:2011, COSMIC functional dimensions measurement method, where it helps illustrate a generic view of the data flow from the FUR perspective, from hardware to software. Figure 2 illustrates the generic model of software FURs, as shown, we can see the following perception: • Software is limited by hardware. Where the functional user can be a human or an engineered device. In fact, we use the term "front-end" direction (i.e. the left side of the functional user boundary of Figure 2) as the functional user (human) bounded by the I/O hardware, we also use the term "back-end" to indicate direction (i.e. on the right side of the persistent memory boundary of Figure 2), the software is bounded by persistent memory such as hard disk, RAM and ROM. Therefore, the functional user (human) is limited by the I/O hardware, such as mouse, keyboard, display, while the functional user (engineered device) directly interacts with the software boundaries, such as sensors, relays, voltage detector. • The functionality of the software associated with the functional flows of the data groups. Where, there are four different types of data movements of data group functional flows. In the "front-end" direction, there are two types of data movements: a) In the front-end: ENTRY and EXITES, this allows the functional user to interact across the boundary. b) In the backend: READS and WRITES, this allows data exchange with persistent storage.• Different measurement purposes, depend on...... half of the document ......tips Training Training duration Training effectiveness Retraining Training devices and facilities Integrated training Staffing Staffing levels Team composition Organizational structure Staff selection Minimum skill levels Special skills Experience levels• Human factors safety (environmental ergonomics) Mechanical safety Electrical safety Environmental safety Operational safety Psychophysiological safety• Human interface factors Visual, audio or tactile cues and information on interface characteristics and task performance, Personalization of the interface and Identification of security-related controls.5. A GENERIC STANDARDS-BASED MODELThis section presents a standards-based definition of a generic requirements model across the ECSS standards for software, to implement the Human Factors NFR system.