Dataflow Comprehensive Training Documents

1 Overview

This document is a comprehensive training document for IT personnel's work awareness, product learning and project management capabilities. The purpose is to help company employees to have a unified understanding and quickly understand the product knowledge of Shutong Changlian.

2. Intended audience

1. Internal employees of
Shutong Changlian 2. IT workers and enthusiasts

3. Training content

3.1 Description of ability promotion

3.1.1 Capability dimension

Rely on intelligence in the short term, ability in the medium term, and character in the long run.

3.1.2 Promotion method

1)  Personnel distribution

Job-hopping can solve the current salary problem, but not the grade problem, which is ultimately determined by the grade.

2)  Career

• Fixed in Gao Fushuai company - backbone, old scalpers (weak risk, few opportunities)
• Fixed in high growth companies - executives, partners (low risk, high reward)
• Weak rationality, drinking poison to quench thirst - choosing a career, opening a restaurant (low risk, low return)
• Have a goal, choose the opportunity - start a business, be the boss (high risk, high reward)

3.2 Description of working methods

3.2.1 Consciousness attitude

• Refuse to position yourself as a "little brother"

          Make plans for your own future, don't think that you are working for others, even if someone really exploits you, you can still think that you are making an investment;

• Try to set some lofty goals

          Those who do not seek the overall situation are not enough to seek a domain, and those who do not seek the world are not enough to seek a moment; try a few times, and the ability will be improved;

• Positively face challenges and difficulties

          Many problems are just a piece of paper, which can be broken with a stab, but we imagine it is very difficult; have the courage to try to break through, don't delay;

• Experience the workplace with a good attitude

          Everything you do is rewarded. Serious unfairness in the workplace is rare. It is fair in the long run. Don't be preoccupied.

3.2.2 Working method

• Clarify goals, decompose tasks, retell things, communicate and confirm;
• Empathy, know ourselves and others, structure first, key breakthroughs;
• Solve the problem, use the exclusion approximation method, and push to the limit;
• Take more steps forward, summarize more, and chain learning method;
• Plan and communicate in advance, don't wait for problems to arise in time, and treat leaders as customers;
• Frameworks, languages, and software are all tools, don’t be limited by tools;
• 良好的工作习惯：及时提交代码和文档至SVN；设计文档和数据库专人维护，SVN总是先更新，在新版本基础上修改；保持日报在打开状态、随时记录、总是去分解工作，做计划。
• 多思考、勤总结、能力提高会增速、且质量更高，思维懒惰最可怕；
• 如果感觉产品使用有问题或者别扭，尽快沟通，可能是产品问题，也可能是自己不会使用；
• 价值体现被替换的难易度，而不是会做什么，提高自己能力稀缺性。

3.3   产品学习说明

3.3.1 AEAI DP开发平台

3.3.3.1 知识重点

• 主键生成、加密解密、日期处理、文件上载；
• 获取User对象方式（ User的跟角色、群组关联属性等）；
• 常见CSS标记、常见JS方法；校验设置（两种方式）；
• Handler调用机制、各ViewRender的用法；
• FormSelect各种创建方法、PageBean各种属性获取方式；
• ServiceContext.xml中典型配置属性：如数据库、appConfig等；
• 树形功能开发，递归的用法；
• 熟练框架功能，如授权、菜单配置等；
• 熟练既有的授权体系（开发平台、Portal）；
• 熟练框架代码，知道如何去参考既有代码；
• 熟练典型功能模型的封装机制；
• 深刻理解DispatherServlet、Handler、Service、DaoHelper、ViewRender、PageBean之间的交互机制；
• 熟练功能模型扩展开发方法（Web/Handler/Service/SQLMAP，以及相关配置)。

3.3.3.2 最佳实践

• 查询条件表单参数最好是组合编码，如：sysCode、sysName、sysType，不宜code、name、type；
• 从handler分析业务流程，习惯查看CMD输出来分析问题；
• 在没有手工调整代码之前，可以反复调整，生成代码来完善功能；一但手写代码来完善功能后不要再生成代码了，会覆盖既有的功能；
• 写出main函数来对类库、代码进行验证（ESB也是如此）；
• 先写功能代码大框，然后由易到难开始调试完善，先让程序运行起来；
• 调试要成为习惯，在调试中深入理解、人脑模拟电脑运行过程。

3.3.2 AEAI ESB集成平台

3.3.2.1 知识重点

• 深入了解组件的扩展用法；
• 掌握各种组件机制，都创建Java工程，采用Java代码模拟实现一下；
• 对JSON、XML、JDBC、HttpClient、WebService等基本知识熟练掌握；
• 熟练：循环、判断、子流程调用、变量传输、远程调试；
• 了解ESB引擎运行机制：资源、服务、流程、组件、变量等；
• 明确DXP、ETL、EAI三个常见典型场景实现模式；
• 基于SOAP UI调用WebService；以及基于axis，cxf生成代码以及调用。

3.3.2.2 最佳实践

• 需求Excel列表、梳理需求；
• 流程框架优先、原型倒逼需求、高效沟通；
• 在流程设计的时候必须考虑多种方式调用，子流程设计；
• 熟练SMC资源配置；
• 如果有对应的组件，优先既定组件，最后考虑通用转换组件和调用组件。

3.3.3 AEAI Portal门户平台

3.3.3.1 知识重点

• 熟练各种解决方案场景配置，熟练对应的Portlet；
• 熟练后台各管理配置功能；
• 熟练权限体系以及权限配置；
• 明确Portal跟开发平台的结合方式：视图方式复用权限体系（6个表）；开发平台开发Portlet等。
• 熟练扩展开发Portlet；
• 了解掌握主题扩展开发。

3.3.3.2 最佳实践

• 尽快配置出原型，基于原型与客户沟通，明确功能需求以及非功能需求，如：交互方式、页面风格、界面布局、数据展现等；
• 调试时候可以不显示其他Portlet，只显示待调试Portlet。

3.4   外围技能说明

3.4.1 工作范围

• 代码规范：包名、类名、方法名、变量名；代码自注释；
• 代码规范：无用的代码（如：临时测试代码）不要在工程中长时间保留，不要提交至SVN；
• 数据库规范；
• 文档规范以及文档习惯；
• 工作日志以及周报，注意：周计划只能做大纲，需要在日报中细化工作。

3.4.2 外围技能

• Eclipse的相关设置，如字符集、用户库等；
• Chrome调试JS、调整HTML、CSS；
• SVN客户端以及Eclipse插件客户端；
• Word、Excel、Visio、PowerPoint、PowerDesigner 、Dreamweaver、Kettle；
• 数据库：

1. 数据库：表、视图、存储过程、触发器、表空间、用户；
2. MySQL、Oracle、SQLServer安装配置；
3. 熟练Navicate、Toad、PLSQL、SQL Server Management Studio；
4. 熟练各数据库备份、恢复方法。

• 跨平台：

1. PHP、.NET环境的搭建；
2. 使用PHP、.NET调用Http流程、Web服务。
3. 熟练Linux的各平台服务端配置（如：环境设置、VI编辑器等）。

3.5   项目交付说明

3.5.1 基本内容

• 明确里程碑（总体目标、阶段目标）、明确工作内容（有哪些具体事情）、分解工作内容（谁来做，什么时候做、什么时候完成）、沟通协作及考核（技术支持、配合沟通、工作考核）

1. 项目总体计划，分解到日。
2. 项目周总结与计划，计划分解到要可以执行（汇报给相关人等）。总结的各项目后面添加（完成、未开始，进行中），没完成红色高亮显示。在邮件主体内容中要有本周工作的简单总结，下周工作计划目标项。以及相关人等的工作完成情况简单评价，偏差较大的建议加班完成。
3. 工作日报，日报中对功能要进一步细化。
4. 代码Review以及功能测试（按照测试大纲来做，一定预留出时间来做）。

• 核心文档：需求规格说明书文档、需求大纲Excel(集成系统[相关系统部署、相关厂商、人员的联系方式清单]、集成功能说明、交付系统部署）、设计、测试大纲以及测试报告、分项验收单、培训（使用）手册、维护手册

1. 核心文档：在SVN里，文件名不要有版本号、文档内部标题有版本号，里程碑文档名有版本号，跟文档内部的标有版本号一致。
2. 功能联测一定要做，文档必须跟上；单元测试开发人员自己来完成。

• 必须要有验收单，但不一定是100%完成，可以是70%完成+备注意见；然后再下一个轮次中完成。项目一般都有初验、终验两个阶段。

3.5.2 工作方法

• Communicate and interact with customers as frequently as possible to let users know the progress of the project and the completion time;
• Whenever there is a demand change, there must be a change document, and the customer must sign it to converge the demand;
• Urgent things are done first, and important things are done every day;
• The progress should be advanced as far as possible, the amount of advance should be made enough in advance, and the problem should be communicated in time; the more problems, the more busy they should be communicated;
• If the established goal cannot be achieved, report it in advance, instead of saying that it can’t be done at the end of the day;
• Blacksmithing needs to be very strong, the work plan must be clear and checked; there must be a summary in the weekly report;
• Communication, interaction, planning, inspection, collaboration, and negotiation are important/necessary abilities of project managers;
• The database is often backed up, and the code is uploaded to SVN every day;
• The project manager has the right to decide the performance salary and project bonus (the mechanism needs to be improved).

3.5.3 Job Responsibilities

• Project Manager Competency Requirements:

1. It is not a microphone, it must be able to judge, analyze, decompose, and guide;
2. Theoretically, the project manager should be involved and competent in all aspects of the project: document writing, requirement research, architecture design, functional design, technical research, code implementation, work assignment and inspection (white-box testing: code review, black-box testing : interaction test), interaction of all parties (work report).

• Difference between project manager and technical manager:

1. The project manager emphasizes more: communication, collaboration, planning, inspection, and promotion. Generally, a single project is involved in the whole process;
2. The technical manager emphasizes more: technical research, project structure, problem solving, skills training, generally support multiple projects, staged and irregular support.

 Document download address: http://pan.baidu.com/s/1pJIg1Lp