抽象的な

INITIAL CONCEPT HOW TO DESIGN A SOFTWARE REQUIREMENT IDENTIFICATION MODEL

Sudhir Singh, Dr. Raj Kumar

Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitation before use. We design pre and post conditions that help identify and bound the problem and then present some methods and technology that assist in refining that boundary and also in recognizing essential characteristics of the problem. Problem identification focuses on going an understanding of the customer’s problem domain and identification the root of the symptoms being observed by customer. Problem decomposition on the other hand is the process of translating our understanding of that problem into a statement of needs that provides the basis for solution specification. Software development activities performed by humans to shift to the description of what computers are required to solve as opposed to how computer are to solve a particular problem. In this paper we propose a system for aiding the construction of a software requirement model through the techniques, that is a method for the support of idea formation and knowledge based modeling