CN101887368A - Requirement cloud language - Google Patents

Abstract

A requirement cloud language is a set of computer programming language specially designed for cloud computing in an information management system, which is oriented to user requirements. By virtue of the invention, a user can utilize an interactive tool on a browser to configure and generate cloud codes and deploy the cloud codes in cloud automatically; and when in operation, the requirement cloud language can be interpreted and executed by an interpretative program to directly generate webpages to be output to the browser end.

Description

Requirement cloud language

Technical field

Requirement cloud language is at the custom-designed cover computer programming language of management information system cloud computing, it is user demand oriented, the user can be by using the interactive tools configuration to generate the requirement cloud language code on browser and being deployed to high in the clouds automatically, then explain during operation and carry out, directly generate webpage and output to browser end by interpretive routine.

Background technology

Cloud computing is neither what calculating, neither a simple technological concept, but how one combine all hardware, software on the basis of existing internet, make full use of and transfer existing all information resources, by novel service mode of framework, a kind of new system architecture of service perhaps can be provided, the change of the low cost of various different levels, various different demands, high efficiency intelligentized service and Information Service Mode is provided for people.Just occupy the most output values of IT service sector gradually as the IT application in enterprises application service, it also will be the main body component part of cloud computing that the cloud of enterprise information system is used.We are reduced to demand and two processes of exploitation to development of information system, the former solves the problem of doing and so on, the latter solves the problem how to do, the infosystem cloud computing also is divided into demand cloud and two parts of exploitation cloud, in view of demand this quality factor in the success or failure of decision infosystem, we have set up application system cloud development language and the platform of demand cloud for guiding.The cloud computing most important characteristic is virtual, and cloud demand and cloud exploitation are also like this.User or consultant need the user directly in the processing and sorting of cloud demand platform, and this locality does not need to install any office and software for editing; The developer then directly develops on the cloud development platform, and this locality also no longer needs to install complicated various developing instrument; Do not need to carry out loaded down with trivial details deployment again after exploitation is finished yet, but be deployed on the Cloud Server automatically.And various other advantages of cloud computing and characteristics all are applicable to cloud demand and cloud exploitation.Why we put forward the notion of cloud demand separately, be because demand itself is the deciding factor of infosystem success or failure, the high reason of traditional software exploitation mortality is exactly that demand can't clearly be expressed the while demand in frequent variation, after virtual, owing to objectively reduced daily communication, this problem can be more outstanding.Requirement cloud language is all language that all center on user's request, it stands directly on user's position, all face demand directly, because software development ultimate aim is exactly to satisfy the demands and the satisfied rapidly demand that constantly changes, so only just caught the essence of software development towards demand.

Requirement cloud language is based upon on UML modeling language, OOP object-oriented development, the SOA Service-Oriented Architecture Based basis, comprises two aspects of requirement description and Demand Design.Requirement description is mainly provided by demand or the trimmer is responsible for, as the user, the consultant, the side of exploitation requirement investigation personnel etc., it mainly describes user's request from displaying interface and flow process two aspects, wherein flow process is divided into vocational work flow process and data logic flow two parts again, the requirement cloud language integrating and developing platform can provide interactively description displaying interface of a whole set of instrument and flow process, and generate requirement cloud language automatically, therefore the demand analysis of user demand cloud language definition can be accomplished standardization, procedure, make clear, do not cause demand uncertainty because of the difference in the natural language understanding.Demand Design mainly is responsible for by the developer, and he carries out the work such as refinement of further database design, service logic integration, interface and flow process according to user's descriptive language.Two aspects of this of demand cloud are what to mix so in one in language, actual items in the cycle then circulation intersect and carry out, carry out Demand Design behind the requirement description, carry out requirement description after the Demand Design again, till meeting consumers' demand.Therefore be based upon the management mode that cloud exploitation on the requirement cloud language basis has changed the traditional software engineering, more lay particular emphasis on and ensure that software development goes to meet consumers' demand.

Summary of the invention

Backus-Naur：＜RCL〉::＝＜statement〉+＜statement〉::＝include＜filepath〉＜statement〉::＝＜selection-statement〉＜statement〉::＝＜object〉＜selection-statement〉::＝if (＜expression〉)＜object〉＜selection-statement〉::＝if (＜expression〉)＜object〉else＜object〉＜object〉::＝＜object-name〉＜attribute〉*＜sub-object〉？＜object〉::＝＜sub-object〉＜sub-object〉::＝{＜object〉+}＜attribute〉::＝＜attribute-name〉＝＜attribute-value〉＜attribute-name〉::＝＜identifier〉＜attribute-value〉::＝＜expression〉＜attribute-value〉::＝{＜javascript〉}＜attribute-value〉::＝{＜sqlproc〉}＜filepath〉::＝＜string〉＜javascript〉::＝javascript＜sqlproc〉::＝SQL＜expression〉::＝＜conditional-expression〉＜conditional-expression〉::＝＜or-expression〉＜conditional-expression〉::＝＜or-expression〉？＜expression〉:＜conditional-expression〉＜or-expression〉::＝＜and-expression〉＜or-expression〉::＝＜and-expression||＜or-expression〉＜and-expression〉::＝＜equality-expression〉＜and-expression〉::＝＜equality-expression ﹠amp; ﹠amp;＜and-expression〉＜equality-expression 〉: :=＜relational-expression〉＜equality-expression 〉: :=＜relational-expression 〉==＜equality-expression〉＜equality-expression 〉: :=＜relational-expression 〉! ＝＜equality-expression〉＜relational-expression〉::＝＜additive-expression〉＜relational-expression〉::＝＜additive-expression〉＜＜relational-expression〉＜relational-expression〉::＝＜additive-expression〉〉＜relational-expression〉＜relational-expression〉::＝＜additive-expression〉＜＝＜relational-expression〉＜relational-expression〉::＝＜additive-expression〉〉＝＜relational-expression〉＜additive-expression〉::＝＜multiplicative-expression〉＜additive-expression〉::＝＜multiplicative-expression〉+＜additive-expression〉＜additive-expression〉::＝＜multiplicative-expression〉-＜additive-expression〉＜multiplicative-expression〉::＝＜unary-expression〉＜multiplicative-expression〉::＝＜unary-expression〉*＜multiplicative-expression〉＜multiplicative-expression〉::＝＜unary-expression〉/＜multiplicative-expression〉＜multiplicative-expression〉::＝＜unary-expression〉％＜multiplicative-expression〉＜unary-expression〉::＝＜factor〉＜unary-expression〉::＝+＜unary-expression〉＜unary-expression〉::＝-＜unary-expression〉＜unary-expression〉::＝！＜unary-expression〉＜factor: :=＜identifier＜factor: :=＜number＜factor: :=＜integer＜factor: :=＜string＜string: :=front and back are by double quotation marks " character string＜factor of causing: :=(＜expression 〉)＜identifier: :=by the alphanumeric underscore form not with the character string＜number of numeral beginning: :=numeral＜integer:: complete cloud requirement of engineering of=expression integer has the framework definition; flow definition; the definition of viewport basis; viewport represents four parts of definition; first three part is explained execution by basic engine; viewport represents definition and represents type according to difference and correspond respectively to different expansion engine rendering engines, certainly requirement cloud language has favorable expansibility, even first three part also all allows the user to expand.We still describe every class definition respectively with the Backus-Naur normal form and have used which object and attribute.＜RCLDEF 〉: :=＜object 〉+＜object 〉: :=＜object-name〉＜object-mark 〉?＜attribute〉*＜sub-object 〉?＜object 〉: :=＜sub-object〉＜sub-object 〉: :={＜object 〉+}＜attribute 〉: :=＜server-mark〉＜attribute-name〉＜attribute-mark 〉=＜value-type〉＜value-type 〉: :=num represents numeral＜value-type 〉: :=int represents integer＜value-type 〉: :=str represents character string＜value-type 〉: :=expr represents any expression formula＜value-type 〉: :=js represents javascript＜value-type 〉: :=sp represents SQL process＜value-type 〉: :=ident represents a unique identification＜value-type who is made of integer or identifier 〉: :=(＜enums 〉) expression is with the constant＜enums that enumerates of CSV 〉: :=comma is represented to divide into groups, can use in every group | expression multiselect one＜object-mark 〉: :=? expression does not occur or occurs 1 time, * expression does not occur or occurs repeatedly, + expression occurs 1 time or repeatedly, not having then, 1 time＜attribute-mark appears in expression 〉: :=? expression can not occur,=must then the grammer of requirement cloud language each several part appear defining thus below 1 time in expression: (one) frame part: page+name? ident url? expr{ frame+name=ident div=expr script onload=js javascript=js}frame+name? ident parent? expr title? expr image? expr width? expr height? expr{ viewport+name=ident div=expr parent? expr title? expr width=expr height=expr widthUnit? str heightUnit? str widthMinusPixel? expr heightMinusPixel? expr left? expr top? expr leftUnit? str topUnit? str leftOffsetPixel? expr topOffsetPixel? expr topMargin=expr bottomMargin=expr leftMargin=expr rightMargin=expr topHide=expr bottomHide=expr leftHide=expr rightHide=expr flow? expr flowNode? expr titlebar? expr { viewport foundation } script onconstruct=js onload=js ondestroy=js javascript=js} (two) flow process part: flow*name=ident title=str{ node+name=ident title=str type? (entity|virtual) inMode? (one|all|sql) inSQL? expr line+name=ident title=str from=str to=str condition? expr alert? expr confirm? expr preJS=js preSQL=sp postSQL=sp postJS=js} (three) viewport foundation table name=expr save? exprdata? name? str PK? expr FK? expr sql=exprbutton*name=ident command=expr title? expr image? expr div? expr popupWidth? expr popupHeight? expr popupTitle? expr position? (top|bottom|topNL|bottomNL) style? (text|pic|pictext) class? expr flowNode? expr flowLine? expr refresh? expr frame? expr viewporp? expr onclick=js preJS=js postSQL=sp postJS=js{ condition+expression? expr confirm? expr alert? expr}query? position? (right|bottom|popup) { the displaying interface part of inquiry } view template=str{ displaying interface part } print style? (portrait|landscape) paper? str leftMargin? num topMargin? numrightMargin? num bottomMargin? numscript onconstruct=js onload=js ondestroy=js javascript=jsonselchanging=js onselchanged=js (four) displaying interface part, be the viewport expansion: following with tabulation, card and tree be (1) tabulation viewport list for example? style? (checkbox) pageSize? int rowClass? expr headerClass? exprfield+width=str align=(center|left|right) name? expr title=expr data? str format=expr type? (text|integer|number|date|time|datetime|select|check|radi o|popup|image|link|download) class=expr frame? expr value? exprminValue? expr maxValue? expr minLength? expr maxLength? expronvaluechanged? js onfocus? js onlose? js (2) card viewport card? labelWidth? int controlWidth? int controlHeight? int rowHeight? intfield+type=(text|integer|number|date|time|datetime|password|textarea | select|check|radio|popup|image|link|label|upload|downloa d) labelWidth? int controlWidth? intname? expr title? expr data? str format=expr cols? int rows? int frame? expr value? exprstyle? (newrow, readonly|unmodifiable, unsave, notnull, nospace, trim, addnull, zero, negative, hidden) minValue? expr maxValue? expr minLength? expr maxLength? exprclass? expr headerClass? expr onvaluechanged? js onfocus? js onlose? js (3) tree viewport tree? root=expr expandLevel? int loadLevel? int width? str title? expr format=expridField=expr parentField=expr textField=expr orderField=expr imageField=expr style? (checkbox, edit) class=expr minLength? expr maxLength? expronvaluechanged? js onfocus? js onlose? jsfield+width=str align=(center|left|right) name? expr title=expr data? str format=expr type? (text|integer|number|date|time|datetime|select|check|radi o|popup|image|link|download) class=expr frame? expr value? exprminValue? expr maxValue? expr minLength? expr maxLength? expronvaluechanged? js onfocus? js onlose? js from last and, the interface of requirement cloud language definition is divided into Page, frame, three levels of viewport, viewport has comprised button again, three parts of query and view, we are called the RCL extension syntax syntactic definition under the view, explain by the expansion engine, user's viewport that can freely define all styles of represents the interface thus, at first should provide some to resemble list in the requirement cloud language kit, tree, card, report, the support of viewport type commonly used such as chart.And flow process is divided into node and line, and has certain related with viewport and button.Viewport, button, flow process line etc. locate to quote javascript language or SQL statement, expand at AM/BAM respectively.And requirement cloud language basis engine also provides a socket agreement, allow the user to use javascript at front end, then set up RDTP data-interface agreement in the rear end, can use any programming language to utilize modes such as pipe, tcp, http and basic engine to carry out data interaction, expanded.

Claims (6)

1. present technique is called requirement cloud language for the computer programming language that infosystem cloud computing exploitation provides, and English full name Requirement CloudLanguage is called for short RCL.

2. this patent provides the syntactic definition of the BNF form of requirement cloud language.

3. during the operation of requirement cloud language, need be on Cloud Server installation requirements cloud language basis rendering engine and expansion rendering engine.

4. the exploitation of requirement cloud language need be at Cloud Server deploy integrating and developing platform, English is called Cloud Development Studio, adopt platform to provide (Platfom as a Service) as the form of service, the client uses browser can carry out interactive development fully, need not to compile and be connected, and can automatically goal systems be deployed in appointment high in the clouds.

5. requirement cloud language implements to be divided into two links with infosystem, requirement description and demand realize that both circulation intersections are carried out in the project implementation cycle, carry out Demand Design behind the requirement description, carry out requirement description after the Demand Design again, till meeting consumers' demand.

6. requirement cloud language at first is applicable to SaaS (Software as a Service, software is as service) etc. the exploitation of cloud computing system, but be not limited to the application of cloud computing, after the respective explanations engine is provided, also applicable to but be not limited to the infosystem of other frameworks such as B/S, C/S, standalone version.