Automatic Control of the Software Development Process with Regard to Risk Analysis

摘要: In this paper, we present a method for analysing risk in software development. Before describing the details, let us define basic terms that are important further discussion. Among them, most import is risk. context of engineering it represents any potential situation or event can negatively affect project future and may arise from some action. Software risks usually scheduling, cost product quality. Further details given Section 2.2. The will be discussed requirements releases. (or requirement model) represent requests customer should transformed into features implemented product. releases refer to phase development life cycle. It term used denote ready has been delivered customer. This work takes consideration agile (i.e. processes with short iterations many releases) therefore, emphasized internal. These not scheduled customer; nevertheless they ’potentially shippable’.