Explore chapters and articles related to this topic
Evaluating the Reliability of Digital Forensics Tools for Cyber-Physical Systems
Published in Yassine Maleh, Mohammad Shojafar, Ashraf Darwish, Abdelkrim Haqiq, Cybersecurity and Privacy in Cyber-Physical Systems, 2019
Precilla M. Dimpe, Okuthe P. Kogeda
Functional requirements define the functionality of a software or system, i.e., how it should act in response to certain input or react in certain situations (Nidhra 2012). The functional requirements were determined in order for us to know what to test and how to test it. The core functional requirements of our model are as follows: The model shall recommend a suitable tool based on the task, category and cost.The model shall inform the user (DFI) if the required tool is not available.The model shall allow the user to provide feedback on the tool.The model shall ignore feedback from the beginner and novice user and consider only feedback from the intermediate, advanced and expert user.The model shall calculate feedback based on the weighted score.The model shall use the feedback provided by users to update the data in the database.
Requirements and Analysis
Published in Miroslav Popovic, Communication Protocol Engineering, 2018
Answering the former question leads to a set of functional requirements, most frequently adorned by non-functional requirements. Functional requirements describe the desired system behavior, while nonfunctional requirements can be imagined as the additional attributes to the behavior related to time restrictions, performance, and so on. To answer the latter question, we must quantify the behavior of the system. Normally, we would say, “For this input, the system should produce this output.” Such thinking implies the existence of a test setup that enables automated (most preferably automatic) testing, referred to as a test bed. A test bed provides a test harness by generating the input to the system and capturing its output.
Requirements and Analysis
Published in Miroslav Popovic, Communication Protocol Engineering, 2018
Answering the former question leads to a set of functional requirements, most frequently adorned by nonfunctional requirements. Functional requirements describe the desired system behavior, while nonfunctional requirements can be imagined as the additional attributes to the behavior related to time restrictions, performance, and so on. To answer the latter question, we must quantify the behavior of the system. Normally, we would say, “For this input, the system should produce this output.” Such thinking implies the existence of a test setup that enables automated (most preferably automatic) testing, referred to as a test bed. A test bed provides a test harness by generating the input to the system and capturing its output.
Requirements development process for manufacturing information systems based on quality function deployment
Published in International Journal of Computer Integrated Manufacturing, 2018
Hong Jin Jeong, Chang Wook Kang, Bo Hyun Kim
The requirements validation phase is the step of checking whether the converted functional requirements meet the user requirements and examining the completeness, possibility of realisation and the possibility of proving the functional requirements. The completeness check ensures that the functional requirements include the user requirements. The realisation possibility check of the functional requirements ensures that the derived functional requirements can be realised as system functions under the constraints. Finally, the proving possibility check documents the activity to demonstrate that the functional requirements conform to the user requirements.
A novel fuzzy credit risk assessment decision support system based on the python web framework
Published in Journal of Industrial and Production Engineering, 2020
Yung-Chia Chang, Kuei-Hu Chang, Yi-Hsuan Huang
User requirements are divided into two types: functional and nonfunctional requirements. Functional requirements define the functions and services that the system must perform. Nonfunctional requirements, also known as system quality requirements or limitations, define the system’s characteristics to judge its work based on certain conditions. The functional and nonfunctional requirements defined for this system are described as follows:
Investigating the impact of requirements elicitation and evolution on course performance in a pre-capstone design course
Published in Journal of Engineering Design, 2019
Beshoy Morkos, Shraddha Joshi, Joshua D. Summers
Moreover, the timing was an indicator of course grade as those teams that finalised their projects early performed higher on their course grade. It is observed that it is prudent to change functional requirements often and early in the process. Table 6 details the observations and explanation of the findings of the requirements evolution study.