作者是 寶盛   

 How Lancer Contributes to Cloud?

 

Lancer has been developing SOA technology and SOA-ERP applications since 2004, and announced a new product, NEO, in 2009. We have a SaaS development environment (SDE), and have been using it to create near 5,000 ERP SaaS.

We have a SaaS execution mechanism that enables service registration, authorization, request, logging, and monitoring. We also created a service framework that components, Java classes including EJBs, and relationships among classes common to all services are defined and can be inherited to develop services complying with Web service standards such as WSDL, SOAP, BPEL, etc. Based on service framework, we created a code generator which generates service codes automatically.

We have an UI framework that divides the UI into several parts and the relationships among the parts are defined. All UI programs inherit the UI framework. Programmers use UI sample codes to quickly create UI programs. We will create UI code generator.

Combining system specification tools, service framework, service code generator, UI framework, UI code generator, testing tool, bug management tool, and version management tool, we are developing a SaaS development environment (SDE), also known as SOA Software Factory, and have been using it to develop NEO SOA-ERP system which contains more than 4,700 services (SaaS) and various ERP applications. We are also developing EUD customization tools including around 30 ways to customize the systems developed by SDE without creating or changing any codes.

In the near future, we are willing to share our SDE, i.e., SOA Software Factory, and existing services with software houses so that they can develop their SaaS applications quickly. There are two implications:

1.Software supply chain: Coordinated by cloud operator, Lancer provides ERP SaaS, software houses familiar with specific industries develop vertical line services in the cloud using Software Factory, local vendors introduce ERP and provide customization services to SME customers by using EUD tools.

2.Collaborative SaaS Community: Experienced consultants or users use ERP SaaS in the cloud, generate new function ideas and post specifications on the Web. Suggestions from the community finalize the specifications. Lancer implements the functions and deploys them onto ERP SaaS in the cloud to be tested by the consultants or users who have posted the requirements. Lancer officially releases the tested new functions. Eventually, sophisticated ERP SaaS applications can be developed by the members of the community.

Note 1: Abbreviations

  1. SaaS stands for software as a service;
  2. SOA stands for service-oriented architecture;
  3. EUD stands for end user development;
  4. NEO stands for neo enterprise orchestration.

Note 2: SOA Software Factory (PaaS) includes

  1. SaaS execution mechanism: Services registration, service authorization, service request, service log, and service monitoring.
  2. SaaS Administration module: service privilege management, account privilege management, program management, message management, consultant tools.
  3. EUD customization tools: Around 30 ways to customize the systems developed with SOA Software Factory without creating or changing any codes.
  4. SaaS Design Pattern: UI sample codes, service sample codes.
  5. Framework: UI framework, service framework.
  6. Eclipse plug-in: Eclipse IDE, service code gen, UI code gen, report code gen, iReport, BPEL service composition, CVS, Deployment tool, service JavaDoc generator, WSDL generator, DB script generator, UI framework JavaDoc, service framework JavaDoc, service JavaDoc.
  7. Test and bug management tools: service auto tester, Mantis.
  8. Coding and testing job assignment tool: Mantis.
  9. Specifications: draft specification templates, final specification templates.
  10. Project Management：Requirement feedback tracking, product decision meeting, seasonal job plan, job items control, biweekly job dispatching, project review and coordination meeting.