【導(dǎo)讀】軟件生命周期，接著討論作為目前軟件工程技術(shù)基石的更全面的軟件開(kāi)發(fā)模型.個(gè)合理的概念計(jì)劃來(lái)管理軟件系統(tǒng)的開(kāi)發(fā).因此，這種計(jì)劃可以作為一個(gè)基礎(chǔ)規(guī)劃，組織，人員配備，協(xié)調(diào)，預(yù)算編制，并指導(dǎo)軟件開(kāi)發(fā)活動(dòng).爾1999年）.羅伊斯使用現(xiàn)在生活中熟悉的“瀑布”圖表，提出了周期的概念，樣的技術(shù)問(wèn)題但還是要必須解決這些問(wèn)題.在大多數(shù)情況下，不論是現(xiàn)有的信息處理機(jī)制。以前是自動(dòng)的，手工的，還是非正式的，新系統(tǒng)都會(huì)取代或補(bǔ)充它們.其所達(dá)到的性能特點(diǎn)，支持系統(tǒng)運(yùn)行和維護(hù)所需的條件.的操作，約束系統(tǒng)行為的限制等.系統(tǒng)之間的內(nèi)部關(guān)系和接口.系，并驗(yàn)證系統(tǒng)及其子系統(tǒng)的性能是否他們的要求匹配.的參數(shù)和用戶(hù)的訪問(wèn)權(quán)限，并運(yùn)行診斷測(cè)試，以保證系統(tǒng)的基本操作的正常運(yùn)作.

　　

【正文】 efinements to apply remain unstated. Instead, formalization is expected to emerge within the heuristics and skills that are acquired and applied through increasingly petent practice. This model has been most effective and widely applied in helping to teach individual programmers how to anize their software development work. Many interpretations of the classic software life cycle thus subsume this approach within their design and implementations. Alternatives to the Traditional Software Life Cycle Models There are at least three alternative sets of models of software development. These models are alternatives to the traditional software life cycle models. These three sets focus of attention to either the products, production processes, or production settings associated with software development. Collectively, these alternative models are finergrained, often detailed to the point of putational formalization, more often empirically grounded, and 12 in some cases address the role of new automated technologies in facilitating software development. As these models are not in widespread practice, we examine each set of models in the following sections. 3 Software Product Development Models Software products represent the informationintensive artifacts that are incrementally constructed and iteratively revised through a software development effort. Such efforts can be modeled using software product life cycle models. These product development models represent an evolutionary revision to the traditional software life cycle models (MacCormack 2021). The revisions arose due to the availability of new software development technologies such as software prototyping languages and environments, reusable software, application generators, and documentation support environments. Each of these technologies seeks to enable the creation of executable software implementations either earlier in the software development effort or more rapidly. Therefore in this regard, the models of software development may be implicit in the use of the technology, rather than explicitly articulated. This is possible because such models bee increasingly intuitive to those developers whose favorable experiences with these technologies substantiate their use. Thus, detailed examination of these models is most appropriate when such technologies are available for use or experimentation. Rapid Prototyping and Joint Application Development Prototyping is a technique for providing a reduced functionality or a limited performance version of a software system early in its development (Balzer 1983, Budde 1984,Hekmatpour 1987). In contrast to the classic system life cycle, prototyping is an approach whereby more emphasis, activity, and processing are directed to the early stages of software development (requirements analysis and functional specification). In turn, prototyping can more directly acmodate early user participation in determining, shaping, or evaluating emerging system functionality. Therefore, these upfront concentrations of effort, together with the use of prototyping technologies, seeks to tradeoff or otherwise reduce downstream software design activities and iterations, as well as simplify the software implementation effort. (see Rapid Prototyping). Software prototypes e in different forms including throwaway prototypes, mockups, demonstration systems, quickanddirty prototypes, and incremental evolutionary prototypes (Hekmatpour 1987). Increasing functionality and subsequent evolvability is what istinguishes the prototype forms on this list. Prototyping technologies usually take some form of software functional specifications 13 as their starting point or input, which in turn is simulated, analyzed, or directly executed. These technologies can allow developers to rapidly construct early or primitive versions of software systems that users can evaluate. User evaluations can then be incorporated as feedback to refine the emerging system specifications and designs. Further, depending on the prototyping technology, the plete working system can be developed through a continual revising/refining the input specifications. This has the advantage of always providing a working version of the emerging system, while redefining software design and testing activities to input specification refinement and execution. Alternatively, other prototyping approaches are best suited for developing throwaway or demonstration systems, or for building prototypes by reusing part/all of some existing software systems. Subsequently, it bees clear why modern models of software development like the Spiral Model (described later) and the ISO 12207 expect that prototyping will be a mon activity that facilitates the capture and refinement of software requirements, as well as overall software development. 14 指導(dǎo)教師意見(jiàn)： 指導(dǎo)教師簽字： 年 月 日 系 (教研室 )意見(jiàn)： 主任簽字： 年 月 日 注：此表單獨(dú)作為一頁(yè) .