<rt id="bn8ez"></rt>
<label id="bn8ez"></label>

  • <span id="bn8ez"></span>

    <label id="bn8ez"><meter id="bn8ez"></meter></label>

    LittleCloud's Java World

    Live and learn.
    posts - 18, comments - 29, trackbacks - 0, articles - 1
      BlogJava :: 首頁(yè) :: 新隨筆 :: 聯(lián)系 :: 聚合  :: 管理

    2008年3月18日



    謝朓《王孫游》賞析

    綠草蔓如絲①,雜樹(shù)紅英發(fā)②。無(wú)論君不歸③,君歸芳已歇④。 


      


    想要下載直接在地址欄輸入:http://www.tkk7.com/Files/ash011/wangsunyou.mp3


        【注釋】①蔓:蔓延。 ②英:花。這兩句是說(shuō)地上長(zhǎng)滿了如絲的綠草,樹(shù)上開(kāi)滿了各樣的紅花,已是暮春時(shí)節(jié)了。 ③無(wú)論:莫說(shuō)。 ④歇:盡。這兩句是說(shuō)莫說(shuō)你不回來(lái),即使回來(lái),春天也過(guò)去了。

        【賞析】
      這是一首樂(lè)府詩(shī),《樂(lè)府詩(shī)集》收入“雜曲歌辭”一類。魏晉以來(lái),文人創(chuàng)作樂(lè)府詩(shī)往往有一個(gè)特點(diǎn):總是圍繞著“古辭”(漢樂(lè)府)打轉(zhuǎn)轉(zhuǎn),或擬古辭,或以古辭為引子生發(fā)開(kāi)去(當(dāng)然也有棄古辭于不顧而自鑄偉辭的)。這種從古辭中尋找“母題”使創(chuàng)作上有所依傍的作法,已形成一個(gè)程式。南朝詩(shī)人寫(xiě)樂(lè)府詩(shī)雖然也依這一程式,但卻出現(xiàn)另一種傾向,他們有時(shí)撇開(kāi)漢樂(lè)府古辭,而直接上溯到《楚辭》中去尋找“母題”。比如,南齊王融和蕭梁費(fèi)昶都寫(xiě)過(guò)一首《思公子》,中心題旨就是采自《楚辭·九歌》:“風(fēng)颯颯兮木蕭蕭,思公子兮徒離憂。”謝朓的這首詩(shī)也屬于這種情況,其“母題”出于《楚辭·招隱士》:“王孫游兮不歸,春草生兮萋萋。”也就是說(shuō),詩(shī)人的創(chuàng)作靈感獲自《楚辭》,而所寫(xiě)內(nèi)容則完全是現(xiàn)實(shí)生活中的感受。在古老的“母題”之中,貫注了活生生的現(xiàn)實(shí)內(nèi)容。
      蔓,蔓延;紅英,即紅花。春天,綠草如絲,蔥蔥茸茸,蔓延大地,繪寫(xiě)出一派綠的世界;各種各樣的樹(shù)上,紅花競(jìng)放,絢麗奪目。綠的氛圍,紅的點(diǎn)染,在鮮明的對(duì)比之中,烘托出一派生機(jī)勃勃的景象。窈窕少女,目睹此景,心傷離情,不禁怦然心動(dòng),情思繾綣,不無(wú)惆悵地發(fā)出了感嘆:“無(wú)論君不歸,君歸芳已歇。”且不要說(shuō)心上的人兒不回來(lái),即使等到他回來(lái),那絢麗的花朵早已凋謝了,那大好春光早已白白地流逝了,我那美妙的年華也早巳悄然飄去了。紅顏難久持啊!這里,詩(shī)人不主要寫(xiě)少女如何急切地等待著情人,如何急不可耐,而是著重寫(xiě)她對(duì)于紅花的珍惜,對(duì)于大好春色的留戀,由此描寫(xiě)出她思君、戀君的春一般的情愫。如此寫(xiě)來(lái),就把主人公的心態(tài)從一般的少女懷春,從感情的傾訴和渲泄,升華到了一種對(duì)春的珍惜、對(duì)時(shí)的留戀的理性高度,滲透出一種強(qiáng)烈的時(shí)間意識(shí)和生命意識(shí)。這樣,從景的描繪,到情的抒發(fā),再到理性的升華,三者水乳交融般地融匯在一起了。所以,這是一首充滿了生命意識(shí)的景、情、理俱佳的好詩(shī)。
      詩(shī)雖短小,藝術(shù)風(fēng)格卻頗具特色,體現(xiàn)了齊梁間詩(shī)歌創(chuàng)作雅俗結(jié)合的一種傾向。首先,從《楚辭》中生發(fā)出來(lái)的母題,顯而易見(jiàn)帶有文人的雅、艷色彩,暗示了它與文人文學(xué)的關(guān)系;但詩(shī)人卻用南朝樂(lè)府民歌五言四句的詩(shī)歌形式,來(lái)表現(xiàn)這一古老“母題”,這便將原有華貴、雍雅的色彩悄悄褪去,淡化,使之在語(yǔ)言風(fēng)格上呈現(xiàn)出清思婉轉(zhuǎn),風(fēng)情搖曳的特色。其次,詩(shī)寫(xiě)春的景色逗引起春的情思,因景而生情,情景相生,短章逸韻,風(fēng)姿綽約,這原是南朝樂(lè)府民歌的本色,是“俗”。然而在描寫(xiě)筆法上卻頗具匠心,詩(shī)人在綠的氛圍中綴以紅花的點(diǎn)染,巧筆對(duì)比,著意渲染,流露出文人精心構(gòu)制的痕跡,表現(xiàn)出“雅”。雅俗結(jié)合,創(chuàng)為佳構(gòu)。另外,詩(shī)的用韻也值得一提。詩(shī)用仄韻,短促,急切,對(duì)表現(xiàn)出主人公惜春、惜時(shí)的時(shí)不我待的急切心情,起到很好的作用,呈現(xiàn)出語(yǔ)淺意深、韻短情長(zhǎng)的藝術(shù)風(fēng)貌。



    我本人很喜歡,聽(tīng)了心里很平靜的感覺(jué)~

    posted @ 2008-07-09 12:56 walkingpig 閱讀(3211) | 評(píng)論 (7)編輯 收藏



    Listen:/Files/ash011/struts2.rar

    Since arriving on the scene in 2000, Apache Struts has enjoyed a very successful run, by most any standard, helping to build many, if not most, of the Java-based web applications deployed today. Its history tells of how Struts provided a solid framework to organize the mess of JSP and Servlets to make developing applications, which used mostly server-generated HTML with a touch Javascript for client-side validation, easier to develop and maintain. As time moved forward, and customer demands of web applications grew and grew, Struts 1 pretty much stayed the same, leaving more and more plumbing to the web developer.

    At JavaOne 2005, several of the Struts developers (Martin Cooper, Don Brown) sat down with Rich Feit (Apache Beehive) and a few Struts users to discuss the future of Struts. We came up with the Struts Ti proposal, which described a framework that brought together a lot of good things that were developing in the web framework community. The problem is that the Struts 1 code base didn’t lend itself to drastic improvements, and its feature set was rather limited, particularly lacking in features such as Ajax, rapid development, and extensibility.

    At the same JavaOne, I sat down with Jason Carreira of the OpenSymphony WebWork 2 project to discuss how we could better work together. I was interested in building on XWork, the core of their command pattern implementation, but he suggested building on WebWork 2 directly. As Rich and I worked on the first few versions of Struts Ti, we decided to take Jason’s advice. We thought it was time for a framework to address higher level application needs, and by building on the proven WebWork 2 framework, we could spend our precious spare time where we felt it would make a difference. From then on, Rich and I worked mostly with Patrick Lightbody, also a core WebWork 2 developer, and found ourselves constantly “stealing” each others ideas for our respective code bases.

    Around this time, Patrick and Keith Donald of the Spring WebFlow project were kicking around an idea of a web framework to bind them all, Clarity. Clarity brought together Spring WebFlow (Keith), Struts (Ted Husted and myself), WebWork (Patrick and Jason), and Beehive (Rich) to talk about the possibility of combining efforts into one framework. Unfortunately, the devil is in the details as soon as Beehive and WebFlow were unable to make progress on merging their wizard/conversion scope features, and questions about project ownership, brand, and identity soon broke up the party.

    Not wanting to lose momentum, Ted and I started discussions with Patrick and Jason on how we could better work together, and after Patrick casually suggested the idea of a merger, Ted jumped on it and the Struts/WebWork merger was born. Since Struts Ti was already based on WebWork, it wasn’t that far a leap to bring the WebWork code into the Struts project. We started the Apache Incubator process for WebWork 2 in January and graduated the WebWork 2 code, developers, and community to Apache Struts that May.

    At that time, Struts was struggling with the project’s core identity, whether it was an umbrella for multiple web frameworks or not. We had Apache Shale, a web framework based off JSF, as a Struts subproject, along side Struts Action 1 (now called Struts 1) and Struts Action 2 (the graduated WebWork 2 code). Unfortunately, these subprojects were confusion to the developer and user community, accustomed to the name “Struts” referring to a single framework. After an attempt to unify the Struts Action 2 and Shale subprojects into a single Struts 2 framework, the Shale developers felt it would be better if they were their own top level project (TLP) where they are today. Struts Action 2 was soon after renamed to simply Struts 2.

    Today, the Apache Struts project has two major versions of its framework, but it is one action-based framework project. WebWork continues to deliver patch releases, and will certainly continue to do so until Struts 2 goes GA or final, but all new development takes place on the Struts 2 code. For those looking for drama or a controversy in the Struts/WebWork merger story, you’ll have to look elsewhere. Both groups of developers are working happily towards a Struts 2.0 GA release, trying to combine the stability and accessibility of Struts 1 with the elegant architecture of WebWork 2. Since the initial incubation, the Struts 2 code has added major features including a plugin framework, a new API, and better Ajax tags, and as promised in the Struts Ti proposal, we won’t stop there.

    I decided to write this down to help clear up where this Struts 2.0 project came from and why it includes WebWork 2 code. Mergers are tricky things and it seems even in the Open Source community, one that champions collaboration, a merger between two projects is a rarity and needs to be defended. Amusing, because you’d be hard pressed to find a Java web developer that felt there are too few web frameworks. I think the WebWork and Struts communities pulled off something special in Struts 2, and hope the merger fever catches on in the Open Source world.

    posted @ 2008-06-26 10:40 walkingpig 閱讀(448) | 評(píng)論 (0)編輯 收藏

    偶也是第一次配這東西,參考了許多網(wǎng)友的帖子,可半路上出現(xiàn)了很多報(bào)錯(cuò),郁悶得死,

    這里我把我自己最后成功的筆記分享給大家.

     

    CVS服務(wù)器的安裝:

    1. 查看你的操作系統(tǒng)上是否安裝了CVS
    #> rpm -qa|grep cvs

    guile-1.8.0-8.20060831cvs

    cvs-1.11.22-4

    2. 建立cvs用戶組:

    /usr/sbin/groupadd cvs

    3         建立cvs組的cvsroot用戶和所屬的目錄:
    #> /usr/sbin/useradd -g cvs -G cvs –d /cvsroot cvsroot

    4         cvsroot用戶添加密碼:
    #> passwd cvsroot

          密碼:cvsroot123456

    5         改變 /cvsroot/ 的目錄屬性:
    #> chmod –R 770 /cvsroot


    6
    改變用戶登陸身份:
    #> su cvsroot

    開(kāi)始創(chuàng)建單個(gè)項(xiàng)目:
    #> cd /cvsroot
    #> mkdir configuration
    #>mkdir psgui

    #>mkdir davinci


    開(kāi)始建立倉(cāng)庫(kù):
    #> cvs –d /cvsroot/configuration init
    #> cvs –d /cvsroot/psgui init

    #> cvs –d /cvsroot/davinci init
    #> chmod -R 770 ./configuration/ ./psgui/ ./davinci/

    9建立CVS服務(wù)啟動(dòng)文件,我們使用xinetd方式:
    #> [Crtl]+[d]
    切換到root用戶身份
    #> cd /etc/xinetd.d
    #> vi cvspserver

    service cvspserver

    {

            disable = no

            flags = REUSE

            socket_type = stream

            wait = no

            user = root

            server = /usr/bin/cvs

            server_args = -f --allow-root=/cvsroot/configuration --allow-root=/cvsroot/psgui --allow-root=/cvsroot/davinci pserver

            log_on_failure += USERID

    }

    注:由于xinetdserver_args長(zhǎng)度限制,當(dāng)你想運(yùn)行很多的單個(gè)倉(cāng)庫(kù)的時(shí)候,可以這么做:

    10 加入cvs服務(wù):
    #>vi /etc/services

    cvspserver 2401/tcp #pserver cvs service
    cvspserver 2401/udp #pserver cvs service

    已經(jīng)存在了,如下:(沒(méi)有添加了)

    cvspserver      2401/tcp                        # CVS client/server operations

    cvspserver      2401/udp                        # CVS client/server operations

    11 啟動(dòng)cvs服務(wù):
    #> /etc/init.d/xinetd restart

    12 檢查cvspserver服務(wù)是否已經(jīng)啟動(dòng):
    #> netstat -l |grep cvspserver
    應(yīng)該有如下結(jié)果:
    tcp 0 0 *:cvspserver *:* LISTEN

    已經(jīng)有上面的顯示結(jié)果

    CVS服務(wù)的用戶管理:

    上面我們已經(jīng)建立了configurationpsguidavinci三個(gè)CVS倉(cāng)庫(kù),下面我們分別給這三個(gè)倉(cāng)庫(kù)建立cvs用戶。

    13創(chuàng)建可以登陸cvs服務(wù)器的用戶名和密碼:

    #> su cvsroot
    #> vi /cvsroot/configuration/CVSROOT/passwd
    yujiabo:*****:cvsroot

    #>vi /cvsroot/psgui/CVSROOT/passwd

    lianghuoyan:*****:cvsroot
    yujiabo:*****:cvsroot

    這兩個(gè)文件的意思是有yujiabolianghuoyan兩個(gè)cvs用戶,lianghuoyan擁有psgui的使用權(quán)限,yujiabo擁有configurationpsgui的使用權(quán)限,登陸后的權(quán)限是cvsroot權(quán)限。
    注意:這里的cvs用戶和系統(tǒng)用戶是不同的。


    14 *****
    為密碼,由以下文件生成:

    #> vi /cvsroot/passwd.pl

    #!/usr/bin/perl
    srand (time());
    my $randletter = "(int (rand (26)) + (int (rand (1) + .5) % 2 ? 65 : 97))";
    my $salt = sprintf ("%c%c", eval $randletter, eval $randletter);
    my $plaintext = shift;
    my $crypttext = crypt ($plaintext, $salt);
    print "${crypttext}
    ";
    #>chmod a+x /cvsroot/passwd.pl


    15
    如果你想生成一個(gè)密碼是“123456”,則:
    #> /cvsroot/passwd.pl “123456”
    回車(chē)即可得到加密密碼,用其替換passwd文件中的*****


    16 Ok
    cvs現(xiàn)在已經(jīng)全部安裝完成了,如果你想讓一個(gè)用戶擁有psgi的權(quán)限,你就在/cvsroot/psgui/CVSROOT/passwd中給他加入一個(gè)用戶;如果你想讓一個(gè)用戶同時(shí)具有psguidavinci的權(quán)限,你就給/cvsroot/psgui/CVSROOT/passwd/cvsroot/davinci/CVSROOT/passwd里給他加一個(gè)用戶名和密碼相同的用戶即可。最后,我們?cè)囉靡幌拢?/span>
    #> cvs -d :pserver:yujiabo@168.68.73.122:/cvsroot/psgui login


    敲入命令回車(chē)后提示輸入yujiabo的密碼,你按照自己設(shè)置的密碼輸入,如果沒(méi)有什么錯(cuò)誤信息出現(xiàn)就是成功了(我的機(jī)器IP地址是168.68.73.122)

    客戶端測(cè)試:

    ash用戶登陸168.68.73.123

    運(yùn)行#

    cvs -d :pserver:yujiabo@168.68.73.122:/cvsroot/configuration login

    123456(輸入的密碼)

    出現(xiàn)錯(cuò)誤:2401 failed: No route to host

    客戶端連接不上,放開(kāi)服務(wù)器防火墻2401端口,方法如下:

    168.68.73.122root登陸后,運(yùn)行#system-config-securitylevel

    選擇“定制”,其它端口處輸入:2401,然后“確定”設(shè)置。

    現(xiàn)在客戶端可以連接了。

    Windows下的客戶端軟件WinCvs1.3配置如下:
    CVSROOT
    認(rèn)證方式:pserver
    路徑:/cvsroot/configuration
    用戶名:yujiabo
    CVSROOT:yujiabo@168.68.73.122:/cvsroot/configuration

    posted @ 2008-04-17 16:38 walkingpig 閱讀(1826) | 評(píng)論 (2)編輯 收藏

    安裝好TestLink 和Mantis后,所有配置好以后,發(fā)現(xiàn)測(cè)試相關(guān)的BUG標(biāo)題中文是亂碼,網(wǎng)上找了若干文章沒(méi)有解決,自己摸索出一下方法。

    Mantis版本: 1.1.0(RC2)
    TestLink版本:1.7.1
    PHP版本:5.2.5
    MySQL版本:5.0.22

    需要修改TestLink的文件:lib\bugtracking\int_mantis.php

     function getBugSummaryString($id)
     {
      if (!$this->isConnected())
       return false;
      
      //$this->m_dbConnection->aaa();
      $this->m_dbConnection->exec_query("set names 'GB2312'");  //<-新增加的
      
      $status = null;
      // 20070302 - {$this->m_dbName}.mantis_bug_table -> mantis_bug_table
      // Problems with MS-SQL
      $query = "Select summary FROM mantis_bug_table Where id='" . $id."'";
      
      $result = $this->m_dbConnection->exec_query($query);
      if ($result)
      {
       $summary = $this->m_dbConnection->fetch_array($result);

       // 20070302 - BUGID - on MS-SQL fetch_array() does not returns numeric indexes, then
       //                    only choice is accessing my field name (IMHO better)
       if ($summary)
        $summary = iconv("GB2312",TL_TPL_CHARSET,$summary['summary']);//<-修改的
       else
        $summary = null;
      }
      return $summary;
     }



    源文出自:http://www.joyblog.cn/article.asp?id=463

    posted @ 2008-04-15 16:18 walkingpig 閱讀(929) | 評(píng)論 (1)編輯 收藏

    TestLink中集成Mantis bug 管理系統(tǒng)

    相信大家在選擇測(cè)試管理工具的時(shí)候,除了Free這個(gè)重要因素之外,是否也想讓其功能更全呢?如果功能不夠全,那么就想著是否能集成其他系統(tǒng)的功能進(jìn)而完善呢?下面要說(shuō)的就是一個(gè)集成功能的運(yùn)用,希望對(duì)大家有幫助。

    簡(jiǎn)述

    在TestLink和bug 管理系統(tǒng)集成必須具備以下特點(diǎn):
    1.       在TestLink和bug 管理系統(tǒng)之間所有的信息交流都是在數(shù)據(jù)庫(kù)中完成。
    2.       TestLink(現(xiàn)在版本)既不能發(fā)信息給bug 管理系統(tǒng),也不能從bug 管理系統(tǒng)接收信息,只是單純的調(diào)用。
    在配置完成之后運(yùn)行,TestLink用戶的使用步驟如下:
    1.       當(dāng)執(zhí)行某個(gè)測(cè)試失敗。
    2.       用戶點(diǎn)擊鏈接打開(kāi)bug 管理系統(tǒng),將issue提交。
    3.       當(dāng)issue提交完畢之后,用戶必須將bug 管理系統(tǒng)的issue ID記錄到TestLink。
    4.       用戶返回到TestLink的測(cè)試執(zhí)行頁(yè)面,將issue ID記錄到Bug問(wèn)題的地方。
    5.       在用戶保存執(zhí)行結(jié)果之后,Testlink將顯示從Bug 管理系統(tǒng)獲取的數(shù)據(jù)。

    環(huán)境要求示例:
    l       TestLink和Mantis安裝在同一臺(tái)服務(wù)器上
    l       Mantis的鏈接:http://168.68.73.29/mantis/
    l       TestLink的鏈接:http://168.68.73.29/TestLink/
    l       Mantis數(shù)據(jù)庫(kù)名字:mantis
    l       Mysql登錄名字:mantis_user
    l       登錄密碼:Mantis_passwd
    第一步:編輯config.inc.php
    找到$g_interface_bugs='NO';
    改成$g_interface_bugs='MANTIS';

    第二步:在mantis上設(shè)置匿名登錄權(quán)限
    l       匿名登錄的設(shè)置需要打開(kāi)。
    l       Mantis的匿名用戶具備對(duì)所有的項(xiàng)目都可以瀏覽的權(quán)限。
    Change the following in your mantis config_inc.php (replace dummy with your created user)
    # --- anonymous login -----------
    # Allow anonymous login
    $g_allow_anonymous_login = ON;
    $g_anonymous_account = 'dummy';

    注:這個(gè)dummy用戶需要administrator在后臺(tái)添加,注冊(cè)不了的

    第三步:在TestLink里配置mantis的界面參數(shù)。
    你必須編輯TL_ABS_PATH/cfg/mantis.cfg.php,如下所示:
    /** The DB host to use when connecting to the mantis db */
    define('BUG_TRACK_DB_HOST', 'localhost');

    /** The name of the database that contains the mantis tables */
    define('BUG_TRACK_DB_NAME', 'manti');

    /** The DB type being used by mantis
    values: mysql,mssql,postgres
    */
    define('BUG_TRACK_DB_TYPE', 'mysql');

    /** The DB type being used by mantis */
    define('BUG_TRACK_DB_USER', 'mantis_user');

    /** The DB password to use for connecting to the mantis db */
    define('BUG_TRACK_DB_PASS', 'mantis_passwd');

    /** link to the bugtracking system, for viewing bugs */
    define('BUG_TRACK_HREF', "http://168.68.73.29/mantis/view.php?id=");

    /** link to the bugtracking system, for entering new bugs */
    define('BUG_TRACK_ENTER_BUG_HREF'," http://168.68.73.29/mantis/");


    測(cè)試配置:
    首先在TestLink里面執(zhí)行一條測(cè)試用例,執(zhí)行之后,如果發(fā)現(xiàn)問(wèn)題,則點(diǎn)擊“Create New Bug”,則打開(kāi)mantis頁(yè)面,將發(fā)現(xiàn)的問(wèn)題報(bào)告至mantis上,報(bào)告成功之后,回到TestLink,將Issue ID填寫(xiě)到“Bug/Problem Report”的文本框里,然后點(diǎn)擊“Save Result”,這樣,Testlink就能把Mantis上的issue數(shù)據(jù)顯示在執(zhí)行測(cè)試用例頁(yè)面下方了。

    此外,你還可以TestLink的bug報(bào)表功能,點(diǎn)擊“Total Bugs For Each Test Case”,則在右邊的頁(yè)面里顯示該項(xiàng)目所有測(cè)試用例下的bug列表。

    posted @ 2008-04-15 15:27 walkingpig 閱讀(2362) | 評(píng)論 (0)編輯 收藏

         摘要:   <?php # Mantis - a php based bugtracking system # Copyright (C) 2000 - 2002  Kenzaburo Ito - kenito@...  閱讀全文

    posted @ 2008-04-11 18:41 walkingpig 閱讀(2268) | 評(píng)論 (0)編輯 收藏

    可惜不是java 寫(xiě)的,用的php
    在本機(jī)裝好兩天了,
    今天一天都在用這個(gè)系統(tǒng),
    可是發(fā)現(xiàn)里面的用戶權(quán)限有些亂.
    搞不清楚項(xiàng)目經(jīng)理應(yīng)該分配什么權(quán)限,
    項(xiàng)目組員分什么權(quán)限,
    項(xiàng)目總經(jīng)理應(yīng)該是什么權(quán)限來(lái)的,

    中文資料也很少,在opensorce里找到英文手冊(cè)看不懂,
    有個(gè)中文手冊(cè)講得不清不楚的~~~暈
    看樣子要自己慢慢摸索了

    posted @ 2008-04-08 15:34 walkingpig 閱讀(1694) | 評(píng)論 (3)編輯 收藏

    去年8月份做的"房地產(chǎn)案件管理系統(tǒng)"
    到現(xiàn)在為止,客戶那邊已經(jīng)上線,
    這兩天客戶反映的問(wèn)題比較多,
    由此,對(duì)這個(gè)項(xiàng)目有些感慨,現(xiàn)在記錄下來(lái),


    以便往后借鑒:

    1 需求不穩(wěn)定,從一開(kāi)始,需求就沒(méi)有完全確定過(guò),直到現(xiàn)在,需求還在增加或變動(dòng)。
    感覺(jué)現(xiàn)在整個(gè)系統(tǒng)就像在打補(bǔ)丁,客戶那這突然想起哪里缺了什么,就要補(bǔ)什么,
    不會(huì)顧及系統(tǒng)架構(gòu),這樣子多多少少會(huì)破壞之前搭建好的系統(tǒng)架構(gòu).

    2 我自己犯的錯(cuò),在實(shí)施過(guò)程中,發(fā)現(xiàn)某些需求有歧義,但未反饋給客戶確認(rèn),
    自己下了結(jié)論,按自己的想法做,結(jié)果并不是客戶的意思.

    3 這個(gè)是最煩人的,整個(gè)系統(tǒng)代碼一個(gè)月多一點(diǎn)就全部完成,但那時(shí)一直打電話要求客戶那邊協(xié)助測(cè)試,
    因?yàn)榭蛻舻臉I(yè)務(wù)很復(fù)雜,也有很多特例,系統(tǒng)哪里有問(wèn)題,只要他們自己一用就會(huì)發(fā)現(xiàn)的,可那時(shí)客戶那邊
    沒(méi)有專門(mén)負(fù)責(zé)這方面的人,一直都拖著,直到現(xiàn)在他們沒(méi)有怎么測(cè)試,就上線,發(fā)現(xiàn)問(wèn)題較多。

    posted @ 2008-03-18 15:40 walkingpig 閱讀(1235) | 評(píng)論 (3)編輯 收藏

    主站蜘蛛池模板: 亚洲Aⅴ无码一区二区二三区软件 亚洲AⅤ视频一区二区三区 | 免费夜色污私人影院在线观看| a级毛片毛片免费观看永久| 亚洲熟女www一区二区三区| 久久精品国产亚洲av高清漫画| 亚洲日韩人妻第一页| 日本一线a视频免费观看| 999国内精品永久免费观看| 久久精品视频免费| 国产激情久久久久影院老熟女免费| 亚洲欧美日韩一区二区三区| 亚洲国产精品久久人人爱| 亚洲av不卡一区二区三区| 伊人久久大香线蕉亚洲 | 国产精品美女久久久免费 | 亚洲视频免费观看| 日韩视频在线观看免费| 久久久WWW免费人成精品| 一级做a爰片性色毛片免费网站| 亚洲成a人片在线不卡一二三区| 亚洲香蕉久久一区二区三区四区| 久久久久久亚洲精品成人| 久久精品国产精品亚洲艾| 国产亚洲精品看片在线观看| 亚洲成a人片在线观看国产| 免费人成视频x8x8入口| 免费国产成人高清在线观看麻豆| 日本免费一区二区三区最新 | 亚洲综合精品第一页| 亚洲日韩精品无码专区| 亚洲性色AV日韩在线观看| 亚洲人成电影网站免费| 亚洲乱人伦中文字幕无码| 亚洲精品无码久久久久YW| 亚洲精品国产suv一区88| 亚洲精华液一二三产区| 久久精品亚洲日本波多野结衣| 国产亚洲一卡2卡3卡4卡新区| 欧美日韩亚洲精品| 色吊丝免费观看网站| sss在线观看免费高清|