• Nuclear Engineering and Technology
• /
• 제56권8호
• /
• pp.3286-3297
• /
• 2024

Traditional text-based system engineering, which has been used in the design and application of passive residual heat removal system (PRHRS) for lead-cooled fast reactors, is prone to several problems such as low development efficiency, long iteration cycles, and model ambiguity. This study aims to effectively address the abovementioned problems by adopting a model-based system engineering (MBSE) method, which has been preliminarily applied to meet the design requirements of a PRHRS. The design process has been implemented based on the preliminary design of the system architecture and consists of three stages: top-level requirement analysis, functional requirements analysis, and design requirements synthesis. The results of the top-level requirements analysis and the corresponding use case diagram can determine the requirements, top-level use cases, and scenario flow of the system. During the functional requirements analysis, the sequence, activity, and state machine diagrams are used to develop the system function model and provide early confirmation. By comparing these sequence diagrams, the requirements for omissions and inconsistencies can be effectively checked. In the design requirements synthesis stage, the Analytic Hierarchy Process is used to conduct preliminary trade-off calculations on the system architecture, after which a white box model is established during the system architecture design. Through these two steps, the analysis and design of the system architecture are ultimately achieved. The resulting system architecture ensures the consistency of the design requirements. Ultimately, a functional hazard analysis was conducted for a specific incident to validate case requirements and further refine the system architecture. Future research can further reduce the design risk, improve the design efficiency, and provide a practical reference for the design and optimization of PRHRS in digital lead-cooled fast reactors.

• Industrial Engineering and Management Systems
• /
• 제11권1호
• /
• pp.70-81
• /
• 2012

The subject of "Design Requirements" (DR) is central to the design of software and engineering systems. The main reason for this is that quality aspects are usually closely tied to requirements, among other things. In this review paper, we consider how the subject of requirements is being managed in these two seemingly different design disciplines. Two important aspects are covered, namely: (a) requirements development, describing various activities leading to requirements documentation, and (b) requirements change management, describing various activities needed for the proper treatment of the inevitable changes in requirements. Similarities and differences on how these two aspects are handled in software and engineering systems are highlighted. It is concluded from this literature survey that the management of software requirements is quite coherent and well established as a science. On the other hand, management of engineering systems requirements suffer from being unstructured, in particular when requirements changes are involved. Important gaps and future important research areas are identified.

• 대한안전경영과학회지
• /
• 제10권1호
• /
• pp.83-90
• /
• 2008

Development of human-system interfaces (HSI) supporting the interaction between human and automation-based systems, particularly safety-critical sociotechnial systems, entails a wide range of design and evaluation problems. To help HSI designers deal with these problems, many methodologies from traditional human-computer interaction, software engineering, and systems engineering have been applied; however, they have been proved inadequate to develop cognitively well engineered HSI. This paper takes a viewpoint that HSI development is itself a cognitive process consisting of various decision making and problem solving activities and then proposes a design requirements-driven process for developing HSI. High-level design problems and their corresponding design requirements for visual information display are explained to clarify the concept of design requirements. Lastly, conceptual design of software system to support the requirements-driven process and designers' knowledge management is described.

• International journal of advanced smart convergence
• /
• 제10권2호
• /
• pp.130-137
• /
• 2021

In the current software project, it is still very difficult to extract and define clear requirements in the requirement engineering. Informal requirements documents based on natural language can be interpreted in different meanings depending on the degree of understanding or maturity level of the requirements analyst. Also, Furthermore, as the project progresses, requirements continue to change from the customer. This change in requirements is a catastrophic failure from a management perspective in software projects. In the situation of frequent requirements changes, a current issue of requirements engineering area is how to make clear requirements with unclear and ambigousrequirements. To solve this problem, we propose to extract and redefine clear requirements by incorporating Design Thinking methodologies into requirements engineering. We expect to have higher possibilities to improve software quality by redefining requirements that are ambiously and unclearly defined.

• 한국주거학회논문집
• /
• 제17권4호
• /
• pp.145-153
• /
• 2006

Ubiquitous space can be described as a combined space of physical space and digital space. Ubiquitous space possesses new possibilities by combining the two. The concept of ubiquitous home will bring new changes in residential space design. First of all, it makes possible for more convenient and secure home. It has to be developed along with city and town level changes as ubiquitous environment. Secondly, concept of extended space as an extension of living space becomes possible by linking with outside spaces. Thirdly, as consumer requirements for residential spaces will become more versatile by social changes, ubiquitous home can be a good means to meet these versatile consumer requirements by accommodating concept of multi-functional space and flexible space. It is quite important to predict user requirements in rapidly changing social environment and versatile personal inclinations. Instead of POE methodology which can analyze and evaluate in exiting types of designs, storytelling methodology can be used to predict and direct for future requirements of living. The methodology makes scenarios of space usage for future living and extracts design requirements for the living. The concept of intelligent space has to be introduced. It is different from digital home that only accomodate digital devices in space. In intelligent space, space itself has to be recognized as an identity that interacts human directly. Intelligent space recognize human requirements and control digital devices as a response. Multi-functional space is closely related with intelligent space that can changes for business, entertainments as well as for rests by user requirements instantly. Flexible space that also intends to meet requirements of mobility and versatility can be attained through the integration of digital technology into current physical mobile systems. Interaction design becomes integral part for ubiquitous space design along with physical design. For the residential space design, digital illiteracy has to be considered for interaction design. Instead of the concept of passive existence, space itself has to be recognized as active subsistence that reacts with human. Intuitive and natural interaction for human will be a key design element for space-human interface design.

• 한국정밀공학회:학술대회논문집
• /
• 한국정밀공학회 2004년도 추계학술대회 논문집
• /
• pp.82-86
• /
• 2004

To cope with the challenge from global market characterized by frequent changes in requirements, manufacturing enterprise should be able to promptly adjust its manufacturing system accordingly. Therefore, it is important to provide manufacturing system designer with an appropriate methodology to (re-)design a manufacturing system subject to requirements change. Axiomatic design theory focuses design activity mainly on functional consideration rather than physical, and has been known as effective especially in the conceptual design phase. This paper introduces an approach to apply the axiomatic design principle to manufacturing system design. It is shown that a new design solution can be reached quickly by finding design parameters for the added or revised functional requirements and thus achieving a set of functional requirements as well as design parameters that satisfy the independence axiom. Some illustrative examples are also given.

• 대한인간공학회지
• /
• 제12권2호
• /
• pp.29-43
• /
• 1993

This paper presents a conceptual approach to convert customer requirements expressed in ordinary language into a form of qualitative and quantitative functions for developing new products. This approach attempts to combine the concepts of the value engineering and the Kansei engineering. It emphasizes that customer require- ments should be interpreted and reflected on the design of new product. Specific are discussed for extracting subjective requirements and transforming them into qualitative and quantitative functions for product design. This approach is expected to provide the product designer with a systematic efficient tool for incorporating subjective requirements into a product design.

• 제어로봇시스템학회:학술대회논문집
• /
• 제어로봇시스템학회 2000년도 제15차 학술회의논문집
• /
• pp.419-419
• /
• 2000

This paper describes a requirement analysis for automotive engine design using a computer aided systems engineering tool RDD-100. Because the engine is a complex system with many subsystems, there are many needs of stakeholder throughout the life-cycle of the engine. The originating requirements have been derived from the needs and decomposed into leaf-node requirements with the tool. Many requirement errors have been detected during the decomposition process and resolved by modifying the requirements. Inconsistency problems have been also resolved with the tool, Analysis of engine requirements using RDD-100 brings clarity to engine design early in the development process.

• 한국컴퓨터정보학회논문지
• /
• 제24권3호
• /
• pp.95-104
• /
• 2019

Crowdsourcing is growing its interests in designing where various designers work independently to a given design task. Recent researchers discovered that collaboration by sharing designs among designers helps to produce high-quality designs. However, design task may still be hard even with that collaboration in case the requirements are not well-defined. Most customers sometimes do not know what they really want and do not know how to clearly define the requirements. Consequently, the lack of requirements creates issues on designers, such as spending much time and effort on collecting requirements alone or from the customers. The designers even end up missing important necessities to complete their tasks. To address this issue, we proposed a collaborative requirements elicitation method that supports designers who are working on the same task. We developed CREFD (Collaborative Requirements Elicitation For Designers and Developers) tool to enable designers collaboratively provide requirements, identify dependencies, add annotations and votes to the provided requirements. We performed the hypothetical and empirical evaluations to test and compare the proposed method with one of the existing elicitation methods, the results show that the proposed method helps in collecting accepted and well-organized requirements better than individual requirements elicitation.

• 디자인학연구
• /
• 제4권1호
• /
• pp.31-37
• /
• 1991

Process of thinking on the form in product design includes the process in which unclear requirements are transformed into defined concepts, and the process in which the design as a form conforming to the concepts in conc1uded.(The former is called fconceptualizationJ which deals with abstract matters, and the latter "manipulation of the formJ which deals with more embodied matters) In conceptualization process the operation which transform the diverse requirements in the initial phase of de\ulcornersign to related linguistic expressions or to an image that directly suggests the form is executed. In the process of manipulation of the form the transformation to design as the description of relationships between the formal elements of the design solution resulted from the transformed requirements. It is the job of selecting the most suitable formal elements, balancing the relationships between them, out 01 the possibilities that reside in the individual attributes of formal elements, and finally leading to the design as the end solution. This writing focuses down to the wilfulness and ambiguity of design, and the diversity of design solution after the requirements, formal elements, and the process of relating the formal attributes to each other is built up the two phases.ases.