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

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

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

    Tauruser

    JSF will hibernate in spring.

      BlogJava :: 首頁(yè) :: 新隨筆 :: 聯(lián)系 :: 聚合  :: 管理 ::
      24 隨筆 :: 2 文章 :: 19 評(píng)論 :: 0 Trackbacks

    2006年11月28日 #

    物料

    物料用于表示成品、原料或中間產(chǎn)品。每個(gè)物料對(duì)應(yīng)于一個(gè)最小存貨單位(SKU)。例如,同一個(gè)庫(kù)存中的兩個(gè)不同模型的白襯衫,如果尺寸不同或款式不同,則它們?yōu)閮蓚€(gè)不同的 SKU。兩個(gè)不同庫(kù)存中的同一模型的襯衫也是兩個(gè)不同的 SKU。因此如果您要表示不同倉(cāng)庫(kù)中的同一襯衫的庫(kù)存,您需要?jiǎng)?chuàng)建不同的物料,并在需要時(shí)將它們分在一個(gè)物料分組中,從而便于在報(bào)告中集合結(jié)果。

    資源

    通常情況下,資源被用于建模機(jī)器、工具、車(chē)輛、設(shè)備或工人。不要使用資源來(lái)建模正被消耗或生產(chǎn)的物料;請(qǐng)使用物料來(lái)完成上述目的。資源可被組合成資源分組,以便更好地組織數(shù)據(jù);例如,改進(jìn)甘特圖的可見(jiàn)性。資源分組可在主數(shù)據(jù)制表符上獲得。

    儲(chǔ)存單元

    儲(chǔ)存單元用來(lái)表示物料或場(chǎng)所的物理儲(chǔ)存設(shè)施。儲(chǔ)存單元可以為單目的(可以儲(chǔ)存一個(gè)物料),也可以為多目的(可以儲(chǔ)存幾個(gè)物料)。如果不是附屬于一個(gè)一元的資源,那么儲(chǔ)存單元只是一個(gè)帶可能的最大儲(chǔ)存能力的場(chǎng)所。它可用來(lái)建模一個(gè)倉(cāng)庫(kù)。當(dāng)附屬于一個(gè)一元的資源時(shí),儲(chǔ)存單元可以建模一個(gè)儲(chǔ)存容器。一元的資源確保容器中各批次的順序。生產(chǎn)活動(dòng)可能會(huì)產(chǎn)出或消耗一些儲(chǔ)存單元中的物料。物料可通過(guò)采購(gòu)或需求的功能在一個(gè)特定的儲(chǔ)存單元中獲得。注意當(dāng)為物料指定一個(gè)儲(chǔ)存單元時(shí),任何關(guān)于該物料的需求、采購(gòu)或物料生產(chǎn)都必須指定該儲(chǔ)存單元。注意您必須聲明可儲(chǔ)存的物料,這樣該儲(chǔ)存單元就能夠儲(chǔ)存這些物料。對(duì)多場(chǎng)所的問(wèn)題,儲(chǔ)存單元也可用來(lái)建模場(chǎng)所。可為其指定經(jīng)度、緯度和類別。

    配方

    有關(guān)物料清單和程序安排的配方組信息配方通常建模了生產(chǎn)流程,并由活動(dòng)原型和關(guān)聯(lián)的約束所組成。每個(gè)活動(dòng)是批大小為 1 的規(guī)范生產(chǎn)訂單的原型。每個(gè)活動(dòng)可能會(huì)使用一個(gè)可供選擇的模式按不同的費(fèi)用在可供選擇的資源上執(zhí)行。模式可從不同的儲(chǔ)存單元進(jìn)行生產(chǎn)或消耗。

    單元

    單元用來(lái)表示消耗或生產(chǎn)的物料數(shù)量的量度單位。這個(gè)編輯器允許創(chuàng)建和編輯一個(gè)單元,并且在適用的條件下,也允許從公制的標(biāo)準(zhǔn)單位換算成其他單位。一個(gè)度量單位沒(méi)有維度或標(biāo)準(zhǔn)換算系數(shù)。例如,托盤(pán)、被子或盒子根據(jù)里面包含的物料可能有不同的換算系數(shù)。其他的度量單位有維數(shù),因?yàn)榭砂凑諛?biāo)準(zhǔn)的方式換算成公制,如長(zhǎng)度、表面積、體積和質(zhì)量。例如,公制的噸是一個(gè)質(zhì)量的維數(shù),在公制(公斤)中來(lái)自維數(shù)的標(biāo)準(zhǔn)單元的換算系數(shù)總是1/1000,它不依賴于被量的物料。 質(zhì)量的標(biāo)準(zhǔn)單位是公斤,長(zhǎng)度的標(biāo)準(zhǔn)單位是米,表面積的標(biāo)準(zhǔn)單位是平方米,而體積的標(biāo)準(zhǔn)單位是立方米。
    所有的計(jì)算都是按照物料的主單元來(lái)進(jìn)行的。但是,您可以為用在圖形用戶界面進(jìn)行顯示的物料定義二級(jí)單元。在物料制表符上標(biāo)記物料的主要和顯示單元。請(qǐng)注意不同換算系數(shù)的幾個(gè)物料可能會(huì)共享同一個(gè)單元。

    物料分組

    物料分組用于集合報(bào)告中的結(jié)果。一個(gè)物料可以為多個(gè)分組的成員。

    資源分組

    對(duì)一個(gè)給定的資源分組類型,資源可為該類型的一個(gè)分組的成員。資源分組用來(lái)改進(jìn)數(shù)據(jù)結(jié)構(gòu)或資源相關(guān)信息的可見(jiàn)型。

    配方分組

    配方分組可用來(lái)將配方組合到一起,以用于部分的加載或分解。一個(gè)配方可以為多個(gè)分組的成員。

    需求

    使用以要求在一個(gè)時(shí)間窗口內(nèi)有一定數(shù)量的可交付物料使用以要求在一個(gè)時(shí)間窗口內(nèi)有一定數(shù)量的可交付物料

    采購(gòu)

    使用以輸入從工廠外采購(gòu)的物料或根據(jù)生產(chǎn)的日期給庫(kù)存一個(gè)使用年限。

    posted @ 2009-07-23 14:24 Tauruser 閱讀(314) | 評(píng)論 (0)編輯 收藏

    ILOG's supply chain applications provide powerful and easy-to-use supply chain planning and scheduling capabilities that are complementary to SAP and utilize ILOG's optimization, scheduling and visualization technologies.

    ILOG LogicNet Plus XE

    ILOG LogicNet Plus XE is a network design and planning solution that combines the advanced optimization technology of ILOG CPLEX with an easy-to-use graphical user interface to manage the world’s most complex supply chain.
    ILOG LogicNet Plus XE facilitates quick analysis of the tradeoffs between production, warehousing, transportation costs, carbon footprint, and service requirements; as well as the calculation of the optimal network configuration for different cost and service objectives. A model’s solutions can be viewed, compared and easily exported to tables and graphs for presentations and further analysis.

    ILOG Inventory Analyst

    ILOG Inventory Analyst is a Web-based, multi-echelon inventory optimization solution that provides end-to-end functionality for manufacturers, retailers and distributors. It combines the advanced optimization technology of ILOG CPLEX with an easy-to-use graphical user interface (GUI), to manage the world’s most complex supply chains. It handles both inbound/outbound and distribution-focused business models, allowing companies to answer a broad range of business questions—from determining the right inventory policies and strategic positioning of inventory, to the ongoing setting of safety stocks and inventory levels in operational environments.

    ILOG Product Flow Optimizer

    ILOG Product Flow Optimizer (PFO) is a part of ILOG’s LogicTools Suite of Supply Chain Applications. It is a powerful and easy-to-use integrated stocking and distribution strategy solution for supply chain and inventory optimization. It helps facilitate both strategic and tactical planning, with built-in integration capabilities to easily connect plans to other systems. Users share a common database that fosters fast movement from one module to another.

    With ILOG PFO, businesses can analyze tradeoffs between transportation, warehousing, inventory carrying costs, and service requirements to arrive at the optimal product delivery path for customers. Companies improve profitability and meet their customers' requirements. Solutions can be viewed, compared and easily exported to tables and graphs for presentations and further analysis.

    ILOG Plant PowerOps

    Extend the value of your existing IT investments with ILOG Plant PowerOps (PPO). ILOG Plant PowerOps takes production planning to a new level for managing demand variability and building executable schedules. It's the only application that offers integrated planning and detailed scheduling for the difficult production challenges associated with the fast-moving consumer goods, pharmaceutical and chemical industries. No other supply chain application contributes as much to the efficient management of tanks, cleaning or sterilization-in-place and process step changeover procedures.

    ILOG Plant PowerOps is based on the most effective optimization models ever built for these challenges. It is the perfect extension to your enterprise resource planning (ERP) or supply chain management (SCM) system and it performs beyond the capabilities of traditional advanced planning and scheduling solutions. ILOG Plant PowerOps helps you address key issues in the food and beverage, chemical, pharmaceutical, and other consumer packaged goods (CPG) industries.

    ILOG Transportation Analyst

    Companies must analyze their transportation network strategies and compare multiple what-if scenarios across many dimensions. Existing transportation solutions focus on the operational and are overly complex for strategic use. Spreadsheet analysis is too limited to find the most economical solutions.

    ILOG Transportation Analyst lets you quickly analyze many different strategies so you can promptly determine the best way to deliver your products and utilize your transportation assets. Manage your vehicle shipment assignments and determine your company's pickup and delivery sequencing to minimize costs while adhering to business constraints.


    posted @ 2009-07-22 15:13 Tauruser 閱讀(417) | 評(píng)論 (0)編輯 收藏

    Through its Java, .NET, Ajax, C++, Eclipse and Adobe Flex/AIR graphics libraries and components, ILOG provides the industry’s most comprehensive set of graphics tools for creating sophisticated, interactive user displays. ILOG's graphics products enhance decision-making speed and ability by making vast quantities of complex data more comprehensible and manageable for users.
    Including ILOG JViews Diagrammer, ILOG JViews Maps , ILOG JViews Gantt , ILOG JViews Charts , ILOG JViews TGO , ILOG JViews Maps for Defense , ILOG JViews Graph Layout for Eclipse, ILOG Gantt for .NET , ILOG Diagram for .NET , ILOG Views Component Suite , ILOG Server , ILOG DB Link , ILOG Elixir .
    posted @ 2009-07-22 14:51 Tauruser 閱讀(301) | 評(píng)論 (0)編輯 收藏

    ILog Optimization Suits is Integrated Tools and Engines for Optimization Modeling and Application Development.
    ILOG has long offered the world's most advanced optimization engines for solving tough business and research problems. ILOG OPL Development Studio provides the most complete integrated development environment (IDE) for developing, debugging and tuning optimization models.
    With the introduction of ILOG Optimization Decision Manager (ODM), ILOG offers complete support for the optimization model-based application development process. Modelers and IT personnel can collaborate in entirely new ways to rapidly develop and deploy state-of-the-art planning and scheduling applications that take decision support to a new level.

    ILOG OPL Development Studio
    ILOG OPL Development Studio is a complete, integrated development environment (IDE) for building, debugging and tuning optimization models across the full range of planning and scheduling problems. ILOG OPL Development Studio supports the complete model development and deployment process and is required in order to use ILOG ODM. It is designed to take maximum advantage of ILOG CPLEX's and ILOG CP Optimizer's advanced features.

    ILOG Optimization Decision Manager (ODM)
    ILOG Optimization Decision Manager (ODM) is a specialized application development and deployment tool that help ILOG OPL Development Studio users build highly interactive, state-of-the-art decision support applications. Business users can participate easily in the model and application development process, ensuring the final planning or scheduling application accurately captures decision-making problems while providing excellence in scenario creation and comparison, constraint relaxation and goal balancing.


    ILOG CPLEX
    ILOG CPLEX delivers high-performance, robust, flexible optimizers for solving linear, mixed-integer and quadratic programming problems in mission-critical resource allocation applications.

    ILOG CP Optimizer
    ILOG CP Optimizer uses domain reduction and constraint propagation to efficiently solve problems that are highly combinatorial with highly logical content—problems that are usually difficult or impossible to represent with linear expressions.



    posted @ 2009-07-22 14:36 Tauruser 閱讀(381) | 評(píng)論 (0)編輯 收藏

    Automated decisions, ranging from whether to accept a loan application or pay a health care claim, to whether a credit card transaction should be flagged as suspect or awarded loyalty points, are the lifeblood of business. But defining and changing those decisions (business rules) can be a challenge with traditional software solutions.
    ILOG BRMS solutions allow your organization to make easy, safe and reliable decision changes. We give you the right tools in the right environments for every stakeholder with a role in managing automated decisions.
    With a BRMS, developers and architects can extract the business logic from the traditional code of an application. When business policies are hard-coded into an enterprise application, the process of updating the system requires specialist programming staff, puts the stability of the system at risk, and can take a long time. By externalizing the business logic from a business application with business rules, IT users can develop and run the business logic independently of the application.
    ILOG JRules is a Business Rule Management System (BRMS) that allows both business and IT users to manage the rules that drive business.
    posted @ 2009-07-22 14:16 Tauruser 閱讀(375) | 評(píng)論 (0)編輯 收藏

    Activities

    Defines activities in the data model.
    An activity is a task to be completed. Activities are hierarchical in nature. This means that a main activity, called parent activity, can be broken down into subactivities. A subactivity, or child activity, can in turn be a parent activity of other subactivities or, if it is at the very end of a branch of the hierarchy, it is a leaf activity. A leaf activity is an activity that has no child activity.
    In addition to its name and identifier, an activity is defined by its start time and end time, which determine an interval called the duration of the activity. If the start and end times are identical, the duration is equal to 0. A zero-duration activity is commonly called a milestone. Typically, milestones are not rendered by the same renderer as activities with a non-zero duration.

    Resources


    A resource is a means by which an activity can be completed. Resources can be persons, premises, equipment, and so forth. Like activities, resources are also hierarchical in nature.
    If resources are people, the parent resource is a department while the child resources are the individual employees. Likewise, you may want to group resources by physical location or by type of machinery.

    Constraints


    A constraint is a type of condition set between two activities. Constraints are represented by arrowed polyline links.
    Constraints can have one of the following types:
    • start to start
    • start to end
    • end to start
    • end to end

    The source activity—that is, the activity whose start or end controls the start or end of another activity—is called the From activity. Conversely, the target activity—that is, the activity whose start or end depends on the start or end of another activity—is called the To activity.

    Reservations

    When a resource is assigned to an activity, this assignment is called a reservation. In the terminology of JViews Gantt, a reservation represents the assignment of one resource to one activity.
    An activity can have multiple resources reserved and similarly, a resource can be reserved for more than one activity. The activity that reserves the resource cannot be changed after the reservation is created.

    posted @ 2009-07-15 16:15 Tauruser 閱讀(367) | 評(píng)論 (0)編輯 收藏

    裝好ILOG后,ILOG使用的是自帶的JDK版本,可以按照下面的方法將ILOG升級(jí)到新的JDK版本上去。
    1、安裝新的JDK到機(jī)器上,設(shè)安裝目錄為%NEW_JDK_HOME%.
    2、找到%ILOG_HOME%\ODME33\Developer\bin\x86_win32\javapath.odmcfg,將里面的內(nèi)容更新為%NEW_JDK_HOME%/BIN
    3、將%NEW_JDK_HOME%/jre拷貝到%ILOG_HOME%\ODME33\Developer下,當(dāng)然最好先對(duì)原%ILOG_HOME%\ODME33\Developer\jre做一下備份。
    4、打到Eclipse ODM Enterprise,在首選項(xiàng)->Java->已安裝的JRE中添加我們新安裝的JDK。
    5、在首選項(xiàng)Java->編譯器,將JDK的一致性級(jí)別設(shè)為1.6.

    Done

    posted @ 2009-07-15 10:37 Tauruser 閱讀(406) | 評(píng)論 (0)編輯 收藏

    <dependency>
         <groupId>org.apache.struts</groupId>
         <artifactId>struts2-rest-plugin</artifactId>
         <version>2.1.6</version>
    </dependency>
    posted @ 2009-02-09 19:44 Tauruser 閱讀(401) | 評(píng)論 (0)編輯 收藏

    在動(dòng)態(tài)創(chuàng)建控件的時(shí)候有時(shí)候需要根據(jù)現(xiàn)有的控件高度去設(shè)置新控件的高度,如何動(dòng)態(tài)取得已有控件的高度就是一個(gè)問(wèn)題了。可以使用下面的代碼進(jìn)行取得控件高度。
    dojo.style(dojo.byId("mapRegion"), "height")
    頁(yè)面上已有代碼:
    <div dojoType="dijit.layout.ContentPane" region="center" id="mapRegion">
    </div>


    posted @ 2009-02-01 21:35 Tauruser 閱讀(503) | 評(píng)論 (0)編輯 收藏

    下面為使用dojo動(dòng)態(tài)創(chuàng)建Button的代碼段。
    function createButton(id, params){
        
    var button = document.createElement("span");
        button.setAttribute(
    "id", id);
        dojo.byId(
    "somewherePlaceButton").appendChild(button);
                               
        
    new dijit.form.Button(
            params
            ,dojo.byId(id));
    }
    調(diào)用例子:
    createScenicSpotButton('button1',{id: "html_Button1",label: "",alt: "My button",title: "Button1",onClick: HandleFunction});


    posted @ 2009-02-01 13:26 Tauruser 閱讀(645) | 評(píng)論 (0)編輯 收藏

    把mgscl更名為mgsclp后,文哥就跟我說(shuō)項(xiàng)目在他的Eclipse里Run不起來(lái)了。拋出以下異常。

    嚴(yán)重: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener
    org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 
    'dataSource' defined in class path resource [applicationContext-resources.xml]: Circular placeholder reference 'jdbc.driverClassName' in property definitions
        at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.processProperties(PropertyPlaceholderConfigurer.java:
    268)
        at org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:
    75)
        at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:
    554)
        at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:
    528)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:
    363)
        at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:
    255)
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:
    199)
        at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:
    45)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:
    3843)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:
    4342)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:
    1045)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:
    719)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:
    1045)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:
    443)
        at org.apache.catalina.core.StandardService.start(StandardService.java:
    516)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:
    710)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:
    578)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
    39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
    25)
        at java.lang.reflect.Method.invoke(Method.java:
    597)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:
    288)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:
    413)

    這個(gè)問(wèn)題在之前bsdts里也遇到過(guò),主要是因?yàn)樵赼ppfuse生成的項(xiàng)目里配置文件jdbc.properties里都使用了占位符 placeholder,如果項(xiàng)目需要正常在Eclipse的Tomcat里Run里來(lái),這個(gè)文件的占位符應(yīng)該正確的給Replace掉。出現(xiàn)上面的異常 主要就是占位符沒(méi)有被正確的Replace掉。好了,既然原因找到了,我們下面來(lái)看下如何解決。
    在Bsdts里面遇到這個(gè)問(wèn)題的時(shí)候,我們經(jīng)常是重新在Console下面運(yùn)行mvn package 或者mvn install后,再重新Deploy就可以了。但是實(shí)踐證明在mgsclp里面是行不通的。這是為什么呢?
    經(jīng)過(guò)查看mgsclp里的Target里的jdbc.properties文件,發(fā)現(xiàn)其已經(jīng)給正確Replace掉了。只是沒(méi)有正確地給Eclipse Deploy到tomcat里。
    根據(jù)上面,我初步確定是Eclipse配置的問(wèn)題。
    我們現(xiàn)在知道的情況有哪些呢?
    一是maven是會(huì)把placeholder自動(dòng)replace的.這個(gè)我們可以通過(guò)查看Target/classes目錄下面的jdbc.properties文件可以看到,經(jīng)過(guò)maven處理后的placeholder是給正確replace了.
    2.在Eclipse里面部署過(guò)后的jdbc.properties文件的plackholder沒(méi)有被replace掉.

    Solution:
    我們的jdbc.properties文件就是位于src/main/resources目錄下面的.我們可以看到Excluded里面已經(jīng)有很多 properties給Excluced了.這是i18n的文件,同樣也是需要maven進(jìn)行編碼處理的,而jdbc.properties文件是要進(jìn)行 replace plackholder處理.本質(zhì)上是一樣的.這里把文件加進(jìn)去后,eclipse也不會(huì)進(jìn)行處理的.所以,我們需要把jdbc.properties文 件同樣加入excluded里面.我們不需要Eclipse對(duì)這些文件進(jìn)行處理.maven處理就行了.這樣子,Eclipse 就不會(huì)把maven處理的結(jié)果用原來(lái)的版本覆蓋了.

    好,現(xiàn)在說(shuō)回到部署問(wèn)題.我們的War工程在maven里,只要把target/classes里的東西與src/webapp里面的東西放到 Tomcat就行了.這次相關(guān)的配置文件有org.eclipse.wst.common.component. Eclipse是如何知道哪些內(nèi)容需要部置到Tomcat就是在這個(gè)文件里面定義的.關(guān)鍵的節(jié)點(diǎn)就是<wb-resource>.由前面所說(shuō) 我們需要的內(nèi)容只有兩個(gè)target/classes,src/webapp.所以實(shí)際上我們只要把這兩個(gè)目錄上面的東西放到正確的部署位置就行了.其它 內(nèi)容都是多余的.于是我只保留下面兩個(gè)內(nèi)容
    <wb-resource deploy-path="/" source-path="src/main/webapp"/>
    <wb-resource deploy-path="/WEB-INF/classes" source-path="target/classes"/>
    這里的部署,只是把這里指定的目錄Copy過(guò)去而已不做任務(wù)處理,(從我目前觀察的情況是這樣子的).
    我們之前為什么不會(huì)呢,就是因?yàn)橛泻芏鄠€(gè)這樣的節(jié)點(diǎn).有些節(jié)點(diǎn)會(huì)引用沒(méi)有處理過(guò)的文件.Eclipse再一次把沒(méi)有處理過(guò)的文件蓋掉處理過(guò)的文件,就出現(xiàn)的我們剛開(kāi)始的時(shí)候的問(wèn)題了.

    好了,今天就到這里。

    posted @ 2008-09-11 23:06 Tauruser 閱讀(3065) | 評(píng)論 (0)編輯 收藏

    Last night, I got the book Pragmatic Software Testing-Becoming an Effective and Efficient Test Professional from www.freebookspot.com. I am instrest in the title.
    Recently, most development team try to use the agile process in the development. And most of them are test driven. I also have done many effort to the test. But I still can't do the job well. I hope this book will give me a new vision on the software testing. This page will record my reading note. As you know I can't have the book finished in a short time, so this page will keep updating. Thanks for your reading, If you have any questions and suggestions, plz give a comment.

    Book Structure

    The book was divide into 6 parts, as follow.

    Part I - Goals, Strategies, and Tactics

    Part II - Risk-Based Testing

    Part III - Static Testing

    Part IV - Behavioral Testing

    Part V - Structural Testing

    Part VI - Appendices

    Reading note

    Part I
    Obvious Quesions will be ask, but in many time there is not obvious answer to them. What is effective software testing? What is efficient software testing? What is software testing, anyway? What is quality?
    The answer is important, bacause Your answers to these questions determine what you expect to do as a tester. Other people’s answers to these questions determine what they expect you to do as a tester. Having common expectations up, down, and across the organizational chart and throughout the project team is essential to success. Without such commonality, no matter what you do, someone’s sure to be disappointed. With common expectations, you can all strive for the same goals, and support others in their endeavors.

    Effective as “producing a decided, decisive, or desired result; impressive.”
    Efficient as “productive of the desired effect; especially to be productive without waste.”

    Should look at test effectiveness and efficiency from the project perspective, not the test subproject perspective.
    posted @ 2008-09-05 11:01 Tauruser 閱讀(383) | 評(píng)論 (0)編輯 收藏

    昨天,IBM在南校區(qū)信科A講學(xué)廳舉行了關(guān)于這次SOA大賽的宣講會(huì)。我們?cè)跂|校區(qū)一行四人早早就出發(fā)了,在信科A會(huì)合Tomara后,到了講學(xué)廳,這次 宣講會(huì)到場(chǎng)的人并不多,佑大個(gè)講學(xué)廳就只有大概二十多人到場(chǎng),這是出乎我意料之外的。宣講會(huì)持續(xù)了一個(gè)半小時(shí),從19:00開(kāi)始到20:30結(jié)束,這次宣 講會(huì)總體上來(lái),我感覺(jué)不錯(cuò),讓我更加了解了此次比賽的一個(gè)目的與比賽過(guò)程中要注意的地方。本來(lái)昨天晚上就想動(dòng)手寫(xiě)這文章,由于人懶,拖到了現(xiàn)在。

    從這次宣講會(huì)上來(lái)看,我的理解主要有兩點(diǎn),一是關(guān)注的是參賽團(tuán)隊(duì)對(duì)所選問(wèn)題領(lǐng)域的業(yè)務(wù)流程理解,優(yōu)化;二是關(guān)注參賽團(tuán)隊(duì)對(duì)于IBM提供的整套工具的使用程度。下面我將分別就兩方面談一下我的想法。

    一、關(guān)注參賽團(tuán)隊(duì)對(duì)所選問(wèn)題領(lǐng)域的業(yè)務(wù)流程理解與優(yōu)化。這一點(diǎn)要求團(tuán)隊(duì)能夠?qū)ζ髽I(yè)現(xiàn)有流程進(jìn)行建模,發(fā)現(xiàn)模型在企業(yè)真正營(yíng)運(yùn)當(dāng)中遇到的問(wèn)題,何處是流程的瓶頸所在。并針對(duì)這些問(wèn)題與瓶頸所在的地方進(jìn)行流程重構(gòu),優(yōu)化現(xiàn)有的流程。為了在實(shí)施前就能夠知道優(yōu)化后的流程是否比現(xiàn)有的流程真正的了改善的地方,需要對(duì)流程進(jìn)行模擬。模擬之后,我們可以基于模型的一系列運(yùn)行指標(biāo)(KPI)來(lái)比較流程的運(yùn)行情況。根據(jù)模擬的情況可以再對(duì)流程進(jìn)行修改,直到得出一個(gè)比較合理的結(jié)果。

    在這一部份當(dāng)中,個(gè)人覺(jué)得最重要的是對(duì)業(yè)務(wù)流程的理解,找出問(wèn)題所在,并能靈活的對(duì)其進(jìn)行調(diào)整,以改善企業(yè)運(yùn)營(yíng)情況。

    二、關(guān)注對(duì)IBM提供的整套工具的使用。本次比賽IBM可以說(shuō)是做到了多贏。一方面提供了一個(gè)很好的機(jī)會(huì)讓在校大學(xué)生參與企業(yè)的流程整合工作;一方面為企業(yè)提供了一個(gè)機(jī)會(huì)讓一批有專業(yè)知識(shí)的專家與學(xué)生為他們現(xiàn)在流程進(jìn)行義診,提出改進(jìn)方案;一方面宣傳與推廣了IBM這一套工具,可以說(shuō)是在市場(chǎng)上一次很好的推廣宣傳。所以,在這次比賽中,一個(gè)重要的,對(duì)方案評(píng)價(jià)的標(biāo)準(zhǔn)就是對(duì)IBM工具的使用。是否對(duì)工具有一個(gè)很好的正體把握,是否充分利用的工具提供給我們的功能。宣講當(dāng)中,李師兄也特別提到了對(duì)于規(guī)則引擎的靈活運(yùn)用。通過(guò)這點(diǎn)做到,當(dāng)業(yè)務(wù)規(guī)則變化的時(shí)候,普通業(yè)務(wù)人員就可以通過(guò)規(guī)則引擎的配置做到快速應(yīng)用新的規(guī)則到業(yè)務(wù)系統(tǒng),靈活應(yīng)對(duì)業(yè)務(wù)需求的變更。而不需要開(kāi)發(fā)人員針對(duì)變更的需要重新去更改源碼來(lái)適應(yīng)這樣的變更。

     

    總的來(lái)說(shuō),此次比賽給我的感覺(jué)要特別注意這兩點(diǎn)。對(duì)問(wèn)題領(lǐng)域業(yè)務(wù)流程整合的深入理解,找出問(wèn)題,提出優(yōu)化解決方案。有了解決方案后,再使用IBM提供的參賽工具對(duì)優(yōu)化方案進(jìn)行實(shí)現(xiàn)。這個(gè)實(shí)現(xiàn)要求我們對(duì)工具有非常深入的了解,能夠靈活應(yīng)用現(xiàn)有功能實(shí)現(xiàn)開(kāi)發(fā)部署。當(dāng)然,我們的解決方案也要考慮除業(yè)務(wù)外的其它內(nèi)容。如是否能靈活適應(yīng)業(yè)務(wù)的快速變更。實(shí)施變更,是否對(duì)現(xiàn)有業(yè)務(wù)有影響。變更是否能夠在不停止現(xiàn)有服務(wù)的情況下得到部署,即熱部署。等等一系列,我們?cè)谙旅姹荣愡^(guò)程中要深入討論研究的問(wèn)題。

    淺談至此,希望大家指點(diǎn)批評(píng)。

    By Tauruser 2008-5-15


    posted @ 2008-05-15 10:45 Tauruser 閱讀(278) | 評(píng)論 (1)編輯 收藏

    今天真是一個(gè)好日子,奧運(yùn)圣火在廣州傳遞,我們Sparkle團(tuán)隊(duì)Blog正式開(kāi)通,今天下午團(tuán)隊(duì)五位成員將在南校區(qū)第一次正式會(huì)面。當(dāng)然恰逢奧運(yùn)圣火經(jīng)過(guò)南校,我們還是會(huì)去感受一下中國(guó)百年奧運(yùn)夢(mèng)的盛況。我們先來(lái)看一下上午奧運(yùn)圣火在廣州傳遞的情況吧。


    posted @ 2008-05-07 11:43 Tauruser 閱讀(257) | 評(píng)論 (2)編輯 收藏

         摘要: 在Sas IntrNet? Module很多功能都是需要用到CGI(Common Gateway Interface)進(jìn)行工作。在使用CGI進(jìn)行工作時(shí)候,我們首先要進(jìn)行CGI服務(wù)器的配置。一般情況下可以直接使用Apache來(lái)架設(shè)CGI服務(wù)器。由于我們后期的一些應(yīng)用可能是在JEE平臺(tái)上進(jìn)行開(kāi)發(fā),所以在一個(gè)可以運(yùn)行Web Container的Server?上架設(shè)CGI服務(wù)是有必要的。本文將介紹如何在Tomcat下配置CGI服務(wù)。  閱讀全文
    posted @ 2007-09-06 10:40 Tauruser 閱讀(7988) | 評(píng)論 (3)編輯 收藏

         摘要: 最近試著用一下了MyEclipse發(fā)現(xiàn)MyEclipse果然比較好用,于是想把以前在Eclipse下的項(xiàng)目轉(zhuǎn)移到MyEclipse下繼續(xù)開(kāi)發(fā)。在轉(zhuǎn)移的過(guò)程中出現(xiàn)了一些問(wèn)題,解決了,寫(xiě)此文記之。  閱讀全文
    posted @ 2007-03-10 18:33 Tauruser 閱讀(6446) | 評(píng)論 (7)編輯 收藏

         摘要: ENIAC simulation是什么?ENIAC是什么你不會(huì)忘記了吧,世界上的第一臺(tái)數(shù)字計(jì)算機(jī)啊。去年是ENIAC誕辰60周年。為了慶祝ENIAC60周年ENIAC Museum Online特別制作了一個(gè)ENIAC的模擬器。  閱讀全文
    posted @ 2007-03-01 22:38 Tauruser 閱讀(2137) | 評(píng)論 (0)編輯 收藏

         摘要: 自定義Hibernate的Dialect成功拿到數(shù)據(jù)庫(kù)里的Decimal類型。  閱讀全文
    posted @ 2007-01-31 11:22 Tauruser 閱讀(2822) | 評(píng)論 (1)編輯 收藏

         摘要: 從去年7月份開(kāi)始參加 Sysu_SF 的培訓(xùn),到如今已經(jīng)有差不多半年的時(shí)間了。這半年以來(lái),辛苦是沒(méi)得說(shuō)了,但同時(shí)也收獲了不少。其中有專業(yè)知識(shí)上的收獲,軟件工程管理方面的收獲,更重要的收獲是結(jié)識(shí)到了許多有技術(shù),有理想的同學(xué),并與他們建立了深厚的友誼和合作。回首這半年時(shí)間,有許多東西可以總結(jié),有許多東西可以說(shuō)。下面就簡(jiǎn)單談一下,我在這半年時(shí)間以來(lái)的感想。   閱讀全文
    posted @ 2007-01-28 10:43 Tauruser 閱讀(482) | 評(píng)論 (1)編輯 收藏

         摘要: 幾道有一定挑戰(zhàn)性的Sql題目。  閱讀全文
    posted @ 2007-01-25 19:32 Tauruser 閱讀(351) | 評(píng)論 (0)編輯 收藏

      最近去圖書(shū)館借了本《Java Web 服務(wù)編程指南》,讀了第一章,寫(xiě)點(diǎn)自己的看法吧。
      在還沒(méi)有接觸這本書(shū)的時(shí)候,我一直的以為WS就只是網(wǎng)絡(luò)上的web應(yīng)用,這么說(shuō)吧,就是我們經(jīng)常上的網(wǎng)站。看了第一章之后,我才發(fā)現(xiàn)之前的直觀的看法是錯(cuò)誤的,Web Service并不只是一個(gè)網(wǎng)站。Web Service使我們能夠?qū)W(wǎng)絡(luò)上的一個(gè)對(duì)象進(jìn)行遠(yuǎn)程調(diào)用,也就是Remote Procedure Calls,RPC。
      我是這么理解的,一般性的網(wǎng)站我們也可以看成是廣義上的Web Service,但是Web Service并不僅局限行一般性的網(wǎng)站,他更加強(qiáng)大的功能在于提供一個(gè)公開(kāi)的,標(biāo)準(zhǔn)化的接口,讓所有的客戶都能通過(guò)一服務(wù)注冊(cè)表,查找到此項(xiàng)服務(wù),并對(duì)此項(xiàng)服務(wù)進(jìn)行綁定。客戶可以通過(guò)這個(gè)公開(kāi)的,標(biāo)準(zhǔn)化的API接口,進(jìn)行遠(yuǎn)程的服務(wù)調(diào)用。這些服務(wù)如,查詢天氣預(yù)報(bào),查詢機(jī)場(chǎng)服務(wù),在一個(gè)網(wǎng)絡(luò)商場(chǎng)進(jìn)行下訂單操作,等等。只要服務(wù)商愿意公開(kāi)他的Web服務(wù),并在服務(wù)注冊(cè)表發(fā)布其服務(wù),所有的潛在客戶都可以通過(guò)在服務(wù)注冊(cè)表中查找此服務(wù),并得到關(guān)于此項(xiàng)服務(wù)的一些具體的描述,從而在服務(wù)商與客戶之間建立bind關(guān)系,遠(yuǎn)程調(diào)用這些服務(wù)。
    ?  在Web服務(wù)中,我們可以看到有三個(gè)不同的角色。他們之間的交互關(guān)系如下圖所示。
    ??
      
      從這個(gè)圖我們可以很清楚地看到三者之間的關(guān)系。服務(wù)提供者提供Web Service,服務(wù)消費(fèi)者是使用此服務(wù)客戶,而位于最頂端的服務(wù)注冊(cè)表,則為兩者互相尋找對(duì)方提供了一個(gè)橋梁。服務(wù)提供者在服務(wù)注冊(cè)表上發(fā)布自己提供的服務(wù),服務(wù)消費(fèi)者從服務(wù)注冊(cè)表上查找自己需要的服務(wù),找到后,就可以在服務(wù)消費(fèi)者和服務(wù)提供者之間進(jìn)行綁定,服務(wù)消費(fèi)者就可以對(duì)服務(wù)提供者提供的服務(wù)進(jìn)行訪問(wèn),遠(yuǎn)程調(diào)用。這里需要注意的是,服務(wù)提供者提供的服務(wù)可能是一個(gè)非常復(fù)雜的服務(wù),他這項(xiàng)服務(wù)可能還會(huì)調(diào)用其它服務(wù)提供者提供的服務(wù),他將所有的這些信息整合處理,最終為服務(wù)消費(fèi)者完成此項(xiàng)服務(wù)。當(dāng)然這項(xiàng)服務(wù)也可以很簡(jiǎn)單,簡(jiǎn)單到服務(wù)消費(fèi)者發(fā)起一個(gè)訪問(wèn),直接返回一個(gè)響應(yīng)就可以了。
      三個(gè)實(shí)體之間要進(jìn)行通信,為了保證這些通信都能順利的進(jìn)行,我們需要為這些通信定義規(guī)則,如果大家都遵守這些規(guī)則行事,這樣我們提供的服務(wù)就可以給任何消費(fèi)者使用,消費(fèi)者也就可以使用任何的服務(wù)提供者的服務(wù)了。這些規(guī)則有:
      
    1. Web Service Description Language, WSDL,Web服務(wù)描述語(yǔ)言,用來(lái)描述Web服務(wù)。
        
    2. Universal Description, Discovery, and Integration, UDDI,通用描述,發(fā)現(xiàn),集成標(biāo)準(zhǔn)。這個(gè)是用來(lái)發(fā)布和查找Web服務(wù)的標(biāo)準(zhǔn)協(xié)議。
    3. Simple Object Access Protocol,SOAP,簡(jiǎn)單對(duì)象訪問(wèn)協(xié)議。用于綁定到Web服務(wù)的標(biāo)準(zhǔn)應(yīng)用程序協(xié)議。

      這三個(gè)協(xié)議可以簡(jiǎn)單的和上圖的三個(gè)操作對(duì)應(yīng)。
      最終我們得到了基本W(wǎng)eb服務(wù)棧:
      
    上面的功能都需要下面的支持。從最底層我們可以看到,Web服務(wù)不一定是建立在HTTP之上的,我們可以使用多種基于TCP/IP的應(yīng)用層協(xié)議來(lái)實(shí)現(xiàn)我們的web service。

    posted @ 2006-11-28 12:34 Tauruser 閱讀(856) | 評(píng)論 (2)編輯 收藏

    主站蜘蛛池模板: 国产成人亚洲精品无码AV大片| 亚洲熟妇丰满多毛XXXX| 女人被弄到高潮的免费视频| 99免费在线观看视频| 久久精品免费视频观看| 花蝴蝶免费视频在线观看高清版 | 久久亚洲sm情趣捆绑调教| 亚洲AV日韩AV永久无码下载| 水蜜桃亚洲一二三四在线| 91情国产l精品国产亚洲区| 久久精品国产亚洲AV无码偷窥 | 日本不卡在线观看免费v| 国产成人无码免费视频97| 免费一区二区三区四区五区| 亚洲成aⅴ人片久青草影院| 国产亚洲精aa成人网站| 亚洲人成亚洲人成在线观看 | 国产午夜亚洲精品理论片不卡| 国产国拍亚洲精品福利| 国产亚洲真人做受在线观看| 亚洲影院在线观看| 亚洲制服丝袜一区二区三区| 午夜在线a亚洲v天堂网2019| 国产尤物在线视精品在亚洲| 久久毛片免费看一区二区三区| 免费观看男人吊女人视频| 16女性下面扒开无遮挡免费| 18禁无遮挡无码网站免费| 国产一级理论免费版| 亚洲精品夜夜夜妓女网| 亚洲资源在线视频| 亚洲色大成网站www久久九| 免费人成视频在线观看免费| 三年片免费高清版 | 亚洲精品国产电影| 亚洲av无码国产精品色午夜字幕 | 亚洲AV无码一区二区一二区| 国产精品福利在线观看免费不卡 | 福利片免费一区二区三区| 成人免费区一区二区三区| 日本三级2019在线观看免费|