【導讀】完成適當?shù)姆治?；建立一份描述系統(tǒng)的工作陳述；從上述的工作陳述中收集需求；確定各個類的職責；確定各個類是如何相互交互的；這個模型應(yīng)當真實地表示系統(tǒng)，簡而言之，類似對象的一個藍圖。實際上，解釋類和對象時確實存在“先有雞還是先。例如，一輛自行車是一個對象。有價值的信息來幫助指導迭代完成設(shè)計過程。維護對象的狀態(tài)。運行程序是，如果沒有以某種方式保存對象，對象就會死亡，中，必須保存對象的狀態(tài)以備以后使用。現(xiàn)在的最新技術(shù)是基于XML的。UML用戶指南將UML定義為“一種用戶。Web服務(wù)通過使用XML來提供一種與平臺無關(guān)的數(shù)據(jù)交換方式。服務(wù)與對Web站點的請求。IIS管理器用樹形結(jié)構(gòu)顯示W(wǎng)eb站點的集群，每個站。點都被設(shè)置成通過IP地址，端口，和一個主機頭接受請求。IP地址，根據(jù)不同的域名，能訪問多個站點。擴展名，被請求的文件將不經(jīng)過任何處理直接發(fā)送給客戶端。起來供其他請求使用。在多種可能的編碼模型中，inline編碼和code-beside是最簡

　　

【正文】 different physical file schemes and caches that code for execution in other requests. Of the different schemes possible, inline code and codebeside are the easiest and most practical means of writing and maintaining code. The prepilation performed by the publishing utility can ease deployment by hiding your code, checking for errors, and avoiding the firstrun pilation process on the first request. 10 Test, Test, and Retest with All Stakeholders In my frequently lessthanhumble opinion, testing actually begins with the development of specifications and requirements. Before any developer types public class in Visual Studio, an extensive discovery process must take place to flesh out exactly what your application is supposed to do. This requires involvement from every stakeholder in the process. Endusers, subject matter experts (generally the business people), DBAs, hardware people…everyone. What39。s more, th ese people should stay involved throughout the entire process. It39。s easier to view development as an evolutionary process than getting a signoff at the start of the project and delivering what you think they wanted. Using testdriven development (TDD) principles (more on that in a moment), you39。ll write tests before the actual code. These tests are frequently simple enough that requirements analysts (yeah, that might be the same person as you) can read the code to understand what39。s going on and determine whether they match the stated goals or use cases of the application39。s function. As development progresses, your suite of tests must still pass. If one or more of the tests fails, you39。ll have to revisit the code and fix it so that it passes the tests. This absolutely must not be a process that es when you39。re done writing code. When the code is closer to done, then you can start to get into some of the traditional testing and use human beings to find out if your user interface does what it should (along with automated tools such as ACT). The theory is that your underlying business logic already works because you39。ve been testing it all along. Right up to the end of this process, to the release of the greatest software ever, all your stakeholders should be involved to make sure that the application performs as it should. 11 Accessing a Relational Database All databases applications have the following structure: n Database client n Database server n Database The database client is the user application that provides the interface to the system. Often it is a GUI application that allows users to query and update the database. SQL SQL stands for Structured Query Language. It is a standard way for database clients to municate with varied vendor database systems that implement this standard. The database client will municate with the database server via SQL statements. Figure displays a general solution to the database client/server model. User DB Client DB Server DB Driver SQL