This document discusses the reorganization of a development team at Cisco WebEx. It proposes separating front-end developers (F2E) and server-side developers (SDE) into different teams for improved productivity, quality, and skill development. It also recommends establishing explicit requirements, change control processes, and an agreed-upon data interface specification to facilitate separation and cooperation between the F2E and SDE teams.

1. Cisco WebEx – Charlie Du

2.  Brief historical retrospect of web develop
◦ Problems and challenge
 Re-organization
◦ F2E & SDE1
◦ Process
◦ Benefits
 Separation and Cooperation
◦ How did Y! do it
◦ How did Cisco WebEx do it
◦ Replicable model of any languages

3.  1 man, from end 2 end.
 Small business
 Most of the sites
look the same
 No innovation

4.  How to handle the big business dev?
 How to improve the productivity?
 How to improve the quality?

6.  We need Re-organization in our developer team.

7.  Organization
Organization
Team Leader
Technic Leader
Team member

8.  Explicit Requirements
 Change Control

9.  For Company
Improve productivity
Improve product quality
Save cost
Professional
 For Developer
Improve skill to be a master
Do what you want to do
Help for the career planning

11.  PHP
 Maple System + PHP
 What is the problem?
 Hard to replace the mock data
 Always lost the close tag
 QA joined too later

12.  Java + Freemarker + Data Interface Spec
 What is the problem?
 Environment data have no handled
 Two frameworks conflict

13. Language URL
Register
Template Data
Interface
Directive
Implementing
Java URL/Template
Mapping
Freemarker
Velocity
Mock Data(.json)
Form Data
Link URL
I18N For JS
I18N For Template
Biz Data Access
Env Data Access
Static Resource Access
Php N/A .php
Asp(.net) N/A .asp(x)

15.  Biz Data and Ajax Call Response
◦ It should be agreement with F2E and SDE
{
status: “SUCCESS|FAILURE”,
message: “Response report of current request”,
result: “Return value, it can be any data type,
Such as String, Array, Object,
F2E and SDE need agree on
the data structure here”
}
{
status: “SUCCESS|FAILURE”,
message: “Response report of current request”,
result: “Return value, it can be any data type,
Such as String, Array, Object,
F2E and SDE need agree on
the data structure here”
}

16.  Environment Data
◦ It should be agreement with F2E and SDE
{
skinpath: “/resource/image/”,
jspath: “/resource/css/”,
rootpath: “/resource/js/”,
currentuser.cred: “U1U7EXG5”,
currentuser.username: “Charlie Du”
}
{
skinpath: “/resource/image/”,
jspath: “/resource/css/”,
rootpath: “/resource/js/”,
currentuser.cred: “U1U7EXG5”,
currentuser.username: “Charlie Du”
}

17.  Environment Data
◦ In order to decide where are these environment data from @SDE
{
currentuser.cred: {
from: “session”
},
currentuser.username:{
from: “session”
}
}
{
currentuser.cred: {
from: “session”
},
currentuser.username:{
from: “session”
}
}

18.  Mock Data File Structure

19.  Form Data
 Action URL
 Items’ Name
 Submit Method
 Link URL

20.  All these need to be a
document of
Data
Interface
Specification
finally!
Data Interface Specification
XXX Project
Version:0.1
F2E Owner: Charlie Du
SDE Owner: Bo Song
2010/10/09

21.  I18N For JS
 <@easySC.i18nJs path=“…/feed.js”/>
 It should generated these codes:
 <script type=“text/javascript” src=“…/feed_en_US.js”></script>
 <script type=“text/javascript” src=“…/feed.js”></script>
 “en_US” should match the client language.

22.  I18N For Template
 <@easySC.i18nMsg key=“feed.userinfo”
arguments=“Charlie” />
 It should get the key “feed.userinfo” from the i18n properties and
pass the arguments to render the final content.
 For example: feed.userinfo={0}&#39;s Info
The result should be: Charlie’s Info

23.  Biz Data Access
 <@easySC.bizData name=“feed” service=“feed.feed_list”
param=“{pageSize:10,pageIndex:0}” />
 “service” should match the mockdata/biz/feed/feed_list.json (Mock Env)
it as a Service Name on Production ENV.
 “param” will be used by Production Env
 “name” will be the returned value, a JSON Object from the .json mock data Or true
data.
 Then, we can use the variable “feed” to access the data, such as: feed.status,
feed.message, feed.result.

24.  Biz Data Access For AJAX Call
 bizcall.ext [.do, .php, .asp(x)]
 All Ajax call point to the JSONRPCHandler.ext, and post a field:
 Name: bizcall
 Value: {name:“feed”, service:“feed.feed_list”, params:{pageSize:10,pageIndex:0}}
 Then, on the SDE side, they still can use the easySC.bizData’s Handle, on F2E
side, they can use the unique mock data.
 Tips: you can build the request as a utility function. Such as “bizCall”

25.  ENV Data Access
 <@easySC.envData name=“username”
key=“currentuser.username” />
 “key” should match the property “currentuser.username” in
mockdata/env/env.txt (Mock Env)
 “name” will be the returned value: “Charlie Du”
 Then, we can use the variable “username”

26.  Directive can be implemented any way
with different languages!
 The core is:
 Access txt file and parse the content to a JSON Object on Mock
Env
 Assembling true data to a JSON Object on Production Env
 They should provide least 2 types of return value : JSON Object
and JSON Text (For Template and Ajax Call)

30. dh20156@126.com