China
Africa
Explore chapters and articles related to this topic
Mechanics of the Mind under Uncertainty and Cognitive Illusion Involving Risk Assessment in National Security
Published in Anna M. Doro-on, Handbook of Systems Engineering and Risk Management in Control Systems, Communication, Space Technology, Missile, Security and Defense Operations, 2023
The fundamental risk assessment guidance for the DoD is the “Risk Management Guide for DoD Acquisition” (JITC 2013). Although the principles explained in the guide are not mandatory, they are recommended and applicable to DoD Information Technology Standard Registry (DISR) and non-DISR standards (JITC 2013). By organizing the risk analysis, potential issues may be eliminated from consideration due to low mission impact and/or low probability of occurrence (likelihood of failure) (JITC 2013). The Department of the Air Force (DOAF), 2003, stated that the seriousness of a risk can be determined by multiplying the probability of the event occurring by the potential negative impact to the cost, schedule or performance of the Project: Risk Severity = Probability of Occurrence × Potential Negative Impact. Traceability is a requirements management activity where requirements are traced back to their original higher-level requirement sources (DOAF 2003). This ensures that all higher-level requirements are being met by detailed requirements (DOAF 2003). Tailoring traceability based on risk maximized benefit realization. As the risk of counterfeiting increases along with the consequence, more rigorous countermeasures must be taken throughout the supply chain (DoD 2012a).
Requirements Management
Published in Phillip A. Laplante, Mohamad H. Kassab, Requirements Engineering for Software and Systems, 2022
Phillip A. Laplante, Mohamad H. Kassab
Requirements management involves identifying, documenting, and tracking system requirements from inception through delivery. Inherent in this definition is the understanding of the true meaning of the requirements and the management of customer (and stakeholder) expectations throughout the system’s lifecycle. A solid requirements management process is the key to a successful project.
Requirements Management
Published in Phillip A. Laplante, Requirements Engineering for Software and Systems, 2017
Requirements management involves identifying, documenting, and tracking system requirements from inception through delivery. Inherent in this definition is understanding of the true meaning of the requirements and the management of customer (and stakeholder) expectations throughout the system’s lifecycle. A solid requirements management process is the key to a successful project.
Understanding Failed Software Projects through Forensic Analysis
Published in Journal of Computer Information Systems, 2022
William H. Money, Stephen H. Kaisler, Stephen J. Cohen
Fretty15 article begins to address the forensic analysis advocated in this paper by citing the need for a solid measurement system and a comprehensive risk-tracking mechanism to help unearth the root cause(s) of a failing project’s problem. This could realistically involve identifying stakeholders, needs, attributes of the needs, and performance measures. Fretty’s citation of a survey of the top 10 reasons why IT projects fail according to iRise (Software services company in El Segundo, Calif., USA., unpublished) helps to that focus failed project analysis on two key failure factors – the team and the requirements. The survey produced a broad list of reasons for reasons for project failures attributable to these categories. It identifies inconsistent team skill sets; extensive (too many) requirements; an overwhelmed requirements management process; ambiguous requirements; unrealistic requirements that cannot be implemented; a focus on simple requirements (not difficult ones); requirements that are clear to the team but not to stakeholders; a belief that requirements review iterations are too time-consuming; stakeholders who don’t mean what they say; and too difficult to manage requirements traceability. Another surveys by Discenza and Forman16 used a survey to identify the common causes of project to suggest mitigation approaches, damage control strategies, and recovery techniques.
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
Wiegers and Beatty (2013) divided requirements engineering into the requirements development process (RDP) and requirements management. RDP, a series of processes to organise user requirements and the input information of users and to deploy functional requirements from the user requirements, plays a key role in determining the characteristics and functions of a manufacturing information system. As shown in Table 1, the causes of failure in RDP were found to be insufficient input by the user, and incomplete requirements and specifications. Thus, the stakeholders of manufacturing information system construction projects should consider reorganising RDP activities so that user requirements are adequately reflected in manufacturing information systems.
A review of methodologies for integrating human factors and ergonomics in engineering design
Published in International Journal of Production Research, 2019
Xiaoguang Sun, Rémy Houssin, Jean Renaud, Mickaël Gardoni
To better understand the requirements of complex sociotechnical systems, Jones and Maiden (2005) developed a method (Requirements Engineering with Scenarios for a User-centred Environment, RESCUE) for integrating human activity models, creative design workshops, and system goal models. The RESCUE processes consist of four streams that run concurrently and are mutually supportive, which cover human activity modelling, system goal modelling, use case modelling and specification, and requirements management. This method has been applied in specifying requirements of air traffic control (CORA-2 system).