1. Application Development and Integration life cycle

    Waterfall Lifecycle          This model supports large and complex projects in which the requirements are well defined.   It adopts sequential approach from requirements analysis through design, construction, testing and application deployment.   2. V Lifecycle       适合对系统可靠性要求比较高的项目。强调测试。     This model supports new product development or large enhancement projects when the size and complexity of the system is large enough to have a multilayered design.  Adopt this model when the requirements are well understood, complete, and stable and the technology & architecture of the solution is clear and visible.        SOW(UAT plan)---Requirement(System Test plan)---Architecture Design(Integration Test plan)---Low Level Design(Unit Test Plan)----Construct(V model bottom) ---Unit Test ---Integration Test ---System Test ---UAT   2.1 Feature  Concurrent Phases or Activities  Mandatory unit testing  Easy to plan   Emphasizes and encourages Verification and Validation at all phases       2.2 Disadvantage  Does not handle iterations  Changes are expansive  More documentation and mandatory sign-off to move out  of the phase  Like waterfall model, Product is not visible until the end   3. Staged Lifecycle     架构已经定义好,允许分阶段的Low Level Design 和实现。   In this model, certain intermediate work products (incremental deliveries) will be delivered to the client before final delivery of the entire application.   It supports product development or large enhancement projects when the requirements are not well understood and skeptic on stability of requirements.   The Staged Lifecycle is best suitable for the development of new products or for executing large enhancements.    Cycle: Low level Design --- Build --- IT,ST,REL,AT 3.1 Feature when the requirements not well understood, not complete or not stable. when there is a need for continuous deliveries from customer side. when allow incremental design and implementation in a number of stages. allow for specification changes in the subsequent release   3.2 Disadvantage need careful planning extra overhead on multiple release determining stage dependencies is difficult     4. Iterative Lifecycle  This model supports large and complex projects with the following characteristics:  Where continuous quality check & high degree of requirements management is needed through out the project.    Where the requirements will change considerably and the environment is not stable. Where it is not possible to specify the requirements in enough details upfront. Where delivering on time is essential, irrespective of the functionality.   cycle: Envisioning(构思) --- Design ---Build --- Test --- Release & Deployment           上面cycle中每个阶段中分多次迭代。     5. Rapid Applicaton Development Lifecycle    

    2017/02/12 iteye

  2. 软件过程

    Engineering 1.1 Requirments Enginerring 1.2 Design 1.3 Technical Review 1.4 Construct(Code & Unit Testing ) 1.5 System & Software Integration 1.6 Integration & System & User Acceptance Testing 1.7 Release Management 1.8 User Documentation 1.9 Maintenance & Migration/Porting Process   2. Project Managment 2.1 Project Initiation 2.2 Project Planning & Estimation 2.3 Risk Management 2.4 Project Quality Management 2.5 Project Monitoring & Control 2.6 Project Closure 2.7 Supplier Agreement Management   3. Process Management 3.1 Process Definition & Improvement & Deployment 3.2 Organization Innovation 3.3 Quantitative Process Management     4. Support 4.1 Change Management 4.2 Configuration Management 4.3 Quality Assurance 4.4 Causal Analysis & Resolution 4.4.1 Defect Classification 4.4.2 Fishbone Diagram 4.4.3 Pareto Analysis 4.4.4 5Whys   4.5 Decision Analysis & Resolution 4.5.1 PUGH Matrix  

    2017/02/12 iteye

  3. 签名证书

    Java  

    2017/02/12 iteye

  4. SQL

    Oracle SQL 摘自:http://www.itpub.net/608483.html DECODE的语法DECODE(value,if1,then1,if2,then2,if3,then3,...,else)

    2017/02/12 iteye

  5. WID & Process Server

    How to deploy CommonLibrary project?  We know module is deployed in the form of  ear.   2. 业务流程执行语言 (BPEL)     BPEL 流程和其他的组件都是使用 WSDL 接口进行描述的。   3. 业务规则有两种类型:规则集 和决策表   4. IBM 定义的SOA的生命周期: Model, Assemble, Deploy, Manage     WID 支持 Assemble阶段     WAS 支持 Deploy 阶段

    2017/02/12 iteye

  6. 隔离级别与脏读幻读

    数据库操作 issue

    2017/02/12 iteye

  7. websphere 小知识

    Websphere 产品安装信息命令 versionInfo     产品属性文件查找 查看<was_home>/properties/version/WAS.product       查看任意概要文件(profile)下的SystemOut.log文件,此文件包含WebSphere Application Server产品相关信息. <profile_home>/logs/server1/SystemOut.log     2. 故障诊断工具 FFDC(First Failure Data Capture) <profile_home>/logs/ffdc   3.  通过从命令行运行 java -fullversion 看JDK信息    <was_home>/java/bin/java -fullversion   4. 检查Windows平台上的IBM HTTP Server的版本信息,运行apache.exe -v   5. 日志文件 5.1 JVM日志 installation_root/profiles/profile_name/logs/server_name 5.2 进程日志 installation_root/logs/applicationServerName/native_stderr.log 和 native_stdout.log 5.3 服务日志(二进制文件)  install_root/logs/activity.log installation_root/bin/showlog   6. 日志分析器 <was_home>/bin/waslogbr.bat install_root/logs/activity.log   7. port config WAS_INSTALL_ROOT\profiles<profileName>\config\cells<cellName>\nodes<nodeName>        

    2017/02/12 iteye

  8. JDBC Driver Type

    Type 1: JDBC-ODBC Drawback: client code must be loaded and configured on each client machine.  

    2017/02/12 iteye