【正文】 ingual, and userfriendly, fast response, support for data uploading and downloading, printing, and so a large number of reports have offered a more high functional demands. For the development side, how fast, better and cheaper to provide a solution to meet the above requirements and near the possible increase code reuse, standard uniformity and can be incremental in order to meet the changing needs of the growing market, and large scale integrated development requirement is tha t the current urgent need to address and research issues. This article, through a munications products of pany39。s production management system, a description of the development process for the above problems made preliminary attempts to meet the plex customer business requirements, to plete production management system developed at the same time with the MVC architecture that construction and implementation of general use for improving the product can be incrementalbased, normative consistency and so on have done a focus on research,. After the implementation of customer requirements to achieve, not only the system itself, but also this structure and mode of implementation of other projects have been promoting the use. The development which based on the architecture, ponentstyle has bee a mainstream enterpriseclass application development. Good multilayer system architecture is a plex system, which is the first demand of rapid application development to each enterprise. This paper first describes the background of the subject, and the reasons that using the MVC architecture. Using the J2EE platform to develop, it will be much cheap and for high availability, high reliability and scalability of applications. Then, take advantage of this unified development platform, using the industry software layer, smart logic layer and data persistence layer of the latest ponent technology to design a software system architecture strategy: Seasar2 as a system development framework for the environment, Mayaa corresponding MVC View layer, S2Struts corresponding MVC control layer, S2Dao corresponding MVC model 山東 大 學(xué)碩士學(xué)位論文 IV layer. On this basis, to reach the MVC software architecture model structure, namely, model, view and controller. The data management and display functions dispersed to different objects, reducing the coupling between the object granularity. Each part of the deal with specific tasks, and is responsible for pleting the rest of munication. First, with the detailed investigation of the customer production status, it analyzes the user39。s overall business, put forward the system goals. With the flow charts, use case diagram, activity diagram, it describes the system39。s functional requirements and nonfunctional requirements. Based on the demand analysis, this paper conducted a systematic summary of the design. First conduct a software architecture design. According to customer requirements and expectations to achieve the goal, it designs mon classes in detail and system functional plan. Take full account of the system scalability, maintainability and performance issues, it maximize the reusability of the system. Finally, it made a brief introduction of the system security architecture also. In summary, based on the design, select the order management subsystem representation of a detailed design of subsystems. Individual modules are described in detail, given the system the screen model, class structure, design and database design. On the basis of the detailed design, first carried out for the realization of the system a brief introduction, and given the realization of the system environment, the overall effect of diagram, the database function implementation, mon processing implementation, the resource file to achieve the realization of various parts. Finally in this section, the performance of the system was tested, functional testing design gives the testing book, and in the nonfunctional testing it gives some test code. Keywords： Software Architecture。 MVC pattern。 Production Management Software。 Scalability 山東大學(xué)碩士學(xué)位論文 1 第 1章 緒論 課題背景 隨著 Web和 Inter的增長，越來越多的企業(yè)開始開發(fā)與部署基于 Web的企業(yè)內(nèi)部網(wǎng)和外部網(wǎng)應(yīng)用。如何通過信息化的建設(shè)進行對其更好的管理并節(jié)省成本、提高效率，而采用何種方式建立一個以 Inter技術(shù)體系構(gòu)架為基礎(chǔ)，集信息查詢、訂單處理、業(yè)務(wù)管理、信息發(fā)布和計算機網(wǎng)絡(luò)通訊于一體的綜合信息系統(tǒng)成為目前關(guān)鍵的問題。而 J2EE為基于 Web的企業(yè)應(yīng)用恰恰提供了無與倫比的支持。該體系采用分布式結(jié)構(gòu)、重用性組件技術(shù)和基于 Web構(gòu)架的分布式數(shù)據(jù)庫技術(shù)，符合軟件發(fā)展的最新趨勢 [1]。 在實施中，用戶希望保持交互操作界面的相對穩(wěn)定，但同時更希望根據(jù)需求的改變而調(diào)整顯示的內(nèi)容和形式。要做到這一點，從界面構(gòu)成的角度來看，困難在于：在滿足對界面要求的同時，如何使軟件的計算模型獨立于界面的構(gòu)成。目前流行的模式：模型一視圖一控制 (MVC)就是這樣的一種交互界面的結(jié)構(gòu)組織模型。該開發(fā)模式可以分離數(shù)據(jù)表現(xiàn)和數(shù)據(jù)訪問，通過一個可伸縮性的、便于擴展的控制器， 來維護整個流程。由此分析，設(shè)計模式對一個軟件系統(tǒng)的整體開發(fā)是其為關(guān)鍵，通過嚴(yán)密的設(shè)計模式設(shè)計出來的架構(gòu)能夠把開發(fā)者從編碼中徹底的解放出來，使他們可以專心于業(yè)務(wù)的邏輯 (這一點對客戶來說十分重要 )，從而達到事半功倍的效果。 當(dāng)前各大公司都已經(jīng)在開源的基礎(chǔ)上自行設(shè)計出各自領(lǐng)域的 J2EE架構(gòu)，但目前大多都是基于一個開源架構(gòu)進行開發(fā)，例如 struts方式、 spring方式，或者基于 Struts+Hibernate的基礎(chǔ)上進行拓展。用這些開源架構(gòu)己經(jīng)可以很有效的開發(fā)出一個系統(tǒng)，但是如果把這三大架構(gòu)的各自優(yōu)勢整合到一起， 將為 Web應(yīng)用創(chuàng)造出更好的架構(gòu) [2]。本文就生產(chǎn)管理系統(tǒng)架構(gòu)的設(shè)計與實現(xiàn)此探討一下整合架構(gòu)的策略： Seasar2作為系統(tǒng)的開發(fā)框架環(huán)境， Mayaa對應(yīng) MVC視圖 層， S2Struts對應(yīng) MVC控制 層， S2Dao對應(yīng) MVC模型 層。 用來提高在其基礎(chǔ)上開發(fā)的軟件系統(tǒng)的效率性和重用性、擴展性等。 本文主要針對一日本通信產(chǎn)品公司的生產(chǎn)系統(tǒng)做定制設(shè)計，整個開發(fā)過程完山東 大 學(xué)碩士學(xué)位論文 2 全按照 CMM3（ Capability Maturity Model3） 的項目開發(fā)過程管理體系來進行，通過架構(gòu)設(shè)計和實現(xiàn)，盡力采用共通組件，而且為了達到客戶多變 的需求和多樣化業(yè)務(wù)管理要求，完全分解表示層和邏輯層，業(yè)務(wù)功能實現(xiàn)即數(shù)據(jù)庫更新等均使用共通類在數(shù)據(jù)庫端完成，頁面內(nèi)容，菜單實現(xiàn)等也均由數(shù)據(jù)庫內(nèi)容動態(tài)控制，大大提高了系統(tǒng)易維護性，能方便對應(yīng)客戶實際業(yè)務(wù)中的變更，提高了軟件開發(fā)效率和日常維護效率以及系統(tǒng)今后的復(fù)用和擴展性。 課題研究的目的和意義 隨著經(jīng)濟的發(fā)展，管理水平的高低對于企業(yè)生存、發(fā)展的影響越來越大，而自動化、信息化的管理已成為現(xiàn)代企業(yè)管理的主流。近幾年來，企業(yè)的新業(yè)務(wù)，管理的新需求推出的越來越快，這種情況下， 大部分用過程語言比如 ASP、 PHP 開發(fā)出來 的 Web 應(yīng)用，初始的開發(fā)模板就是混合層的數(shù)據(jù)編程。例如，直接向數(shù)據(jù)庫發(fā)送請求并用 HTML顯示 ,開發(fā)速度往往比較快 ,但由于數(shù)據(jù)頁面的分離不是很直接 ,因而很難體現(xiàn)出業(yè)務(wù)模型的樣子或者模型的重用性。產(chǎn)品設(shè)計彈性力度很小，很難滿足用戶的變化性需求。 系統(tǒng)擴展與整合的難度越來越大，系統(tǒng)再開發(fā)與維護的成本也越來越高。如何讓管理系統(tǒng)發(fā)布更便利，功能擴展簡單，業(yè)務(wù)功能模塊化，人機操作更人性化，是企業(yè)迫切希望解決的問題。 與此同時， 現(xiàn)代信息技術(shù)迅猛發(fā)展 、不斷完善，為企業(yè)的管理升級提供了堅實的技術(shù)基礎(chǔ)。 MVC 框架 要求對應(yīng)用分層， 雖然要花費額外的工作，但產(chǎn)品的結(jié)構(gòu)清晰，產(chǎn)品的應(yīng)用通過模型可以得到更好地體現(xiàn)。 MVC 框架的優(yōu)點在于： 首先，最重要的是應(yīng)該有多個視圖對應(yīng)一個模型的能力。在目前用戶需求的快速變化下，可能有多種方式訪問應(yīng)用的要求。例如，訂單模型可能有本系統(tǒng)的訂單，也有網(wǎng)上訂單，或者其他系統(tǒng)的訂單，但對