• Journal of Information Technology Services
• /
• v.11 no.2
• /
• pp.259-274
• /
• 2012

A well organized system requirements provide a solid basis of achiving a successful project and are effective methods of communication among stakeholders. We illustrate and propose a 'System Requirement Development Framework' to develop correct requirements as a methodical approach. We first organize a 'Requirement Development Process' and then establish a 'Non-Functional Requirements Principle'. On these basis, we next propose a 'Requirement Development Guideline' from a perspective of 'Functional Requirement', 'Non-Functional Requirement' and 'Triage' in advanced stages. We also verify and evaluate the suitability of our proposed 'System Requirement Development Framework' by applying it to several projects.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.13 no.9
• /
• pp.4207-4213
• /
• 2012

Software quality is strongly associated with requirement quality. Accordingly, companies are trying effect for enhancing requirement quality. But, it is difficult to verify the requirement of specification format, which have to rely on abnormal business knowledge of analyst. Also, it is insufficient to normal methodology or automated technique for enhancing requirement quality of specification format. In this paper, we propose the process of requirement verification and automated verification tool for enhancing requirement quality. we compare the external view design and internal view design for verifying requirement. In the case study, we evaluate the feasibility of the proposed automated verification technique of requirement.

• Proceedings of the Korean Society of Agricultural Engineers Conference
• /
• 2005.10a
• /
• pp.80-84
• /
• 2005

The water requirement of transplanting culture(TC) consisting of 16 plots and direct seeding culture in a well-drained paddy field(DC) also having 15 plots were measured in order to clarify the influence factors on water requirement. Each plot was maintained under different cultivation conditions. Those varied cultivation conditions were classified into 7 items. Subsequently, the relationship between water requirement and 7 items were analyzed by evaluating the average water requirement in each condition to clarify the items influencing water requirement. From the analysis of the results, the water requirement of DC was determined to be 3.5 times of the TC. Furthermore, water requirement in DC and TC were influenced mainly by ponding depth and locational condition respectively.

• International Journal of Knowledge Content Development & Technology
• /
• v.3 no.2
• /
• pp.43-65
• /
• 2013

In this work, we first introduce two main approaches to writing requirements and then propose a method based on Natural Language Processing to improve requirement authoring and the overall coherence, cohesion and organization of requirement documents. We investigate the structure of requirement kernels, and then the discourse structure associated with those kernels. This will then enable the system to accurately extract requirements and their related contexts from texts (called requirement mining). Finally, we relate a first experimentation on requirement mining based on texts from seven companies. An evaluation that compares those results with manually annotated corpora of documents is given to conclude.

• International journal of advanced smart convergence
• /
• v.9 no.4
• /
• pp.167-172
• /
• 2020

In the 4th industrial revolution, there are many projects for diverse software applications of smart city environments. Most of the stakeholders focus on considering software quality for their developed software. Nobody doesn't guarantee requirement satisfaction after complete development. At this time, we can only work on user acceptance testing for requirement satisfaction on frequently changing requirements. Why keeps the requirement traceability? This traceability is to identify risks related to requirements, to assure correct software development based on customer requirements. To solve this, we are researching how to implement requirement traceability across each artifact's relationship to each activity of a whole development lifecycle.

• Journal of the Semiconductor & Display Technology
• /
• v.22 no.1
• /
• pp.88-93
• /
• 2023

In software engineering, requirement analysis is an important task throughout the process and takes up a high proportion. However, factors that fail to analyze requirements include communication failure, different understanding of the meaning of requirements, and failure to perform requirements normally. To solve this problem, we derived actors and behaviors using morpheme analysis and BERT algorithms in the Korean requirement document and constructed them as ontologies. A chatbot system with ontology data is constructed to derive a final system event list through Q&A with users. The chatbot system generates the derived system event list as a requirement diagram and a requirement specification and provides it to the user. Through the above system, diagrams and specifications with a level of coverage complied with Korean requirement documents were created.

• The KIPS Transactions:PartD
• /
• v.14D no.6
• /
• pp.641-648
• /
• 2007

To develop a dynamic system project in which the requirement changes frequently, it's impossible to finish the development within a fixed-cost due to additional budget occurring in need of requirement creep. To manage the successive project within a fixed-cost, it's better to manage the ratio of necessarily changed size of project and necessary optional requirement. According to Bhagwat, it is occurred in the construction phase. Also, he stated that the software development cost, construction phase cost and requirement cost are equal and it was wrong explanation in the ratio of requirement creep and optional requirement. This paper assumes the requirement creep to be happening in the phase of elaboration and construction. In addition, some differences were supposed to happen between software development cost, construction phase cost, and requirement creep cost. As a result, the reality was preferred rather than the ratio of optional requirement and the ratio of requirement creep.

• Asian-Australasian Journal of Animal Sciences
• /
• v.10 no.3
• /
• pp.277-283
• /
• 1997

Purified diets containing five levels of methionine with 0.4% cystine were fed to growing chicks (8 days old male Arbor Acre strain) to evaluate methionine requirements for growth and maintenance. A model was developed to separate methionine requirement for maintenance from requirement for growth. From this model the daily methionine requirement for growth was 4.22 mg/g gain, and the daily methionine requirement for maintenance was 0.034 times metabolic body size ($W^{0.75}$). Based on nitrogen gain response, the methionine requirement for growth was 0.162 mg/mg N gain, and the daily maintenance requirement was 0.037 times metabolic body size. The plateau of plasma methionine concentration reached at 117.16 mg intake pre day. The total methionine requirement determined based on weight gain response was 138.29 mg/day or 0.33% of the diet and the one determined based on nitrogen gain response was 141.7 mg/day of 0.34% of the diet, respectively. As a percentage of protein, methionine was calculated to be 2.6%; the reported methionine content of carcass CP was 1.76%.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.9 no.1 s.24
• /
• pp.135-143
• /
• 2006

This paper describes a requirement architecture modeling for the front end of KT-1 export version requirement definition processes to construct SDS(system development specification). The requirement definition process is a highly conceptual process that is difficult to carry out. This paper focuses on how to perform the KT-1 export version requirements definition process including the integration of process, methods and tools for the front-end activity of requirements definition process. This requirement model is structured in four segments, including requirement layering, requirement categorization, life cycle stakeholder and requirement definition process using Computer-Aided Systems Engineering tool(CORE).

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.16 no.1
• /
• pp.263-271
• /
• 2016

Software requirement analysis is necessary for successful software development project. Specially, incomplete requirement is the most influential causes of software project failure. Incomplete requirement can bring late delay and over budget because of the misunderstanding and ambiguous criteria for project validation. Software requirement patterns can help writing more complete requirement. These can be a reference model and standards when author writing or validating software requirement. Furthermore, when a novice writes the software scenario, the requirement patterns can be one of the guideline. In this paper proposes an automatic approach to identifying software scenario patterns from various software scenarios. In this paper, we gathered 83 scenarios from eight industrial systems, and show how to extract 54 scenario patterns and how to find omitted action of the scenario using extracted patterns for the feasibility of the approach.