CN1604099B - Method and system for constructing software system structure of telecommunication operation support system - Google Patents
Method and system for constructing software system structure of telecommunication operation support system Download PDFInfo
- Publication number
- CN1604099B CN1604099B CN 200410009412 CN200410009412A CN1604099B CN 1604099 B CN1604099 B CN 1604099B CN 200410009412 CN200410009412 CN 200410009412 CN 200410009412 A CN200410009412 A CN 200410009412A CN 1604099 B CN1604099 B CN 1604099B
- Authority
- CN
- China
- Prior art keywords
- architecture
- module
- mode
- support system
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 136
- 238000004458 analytical method Methods 0.000 claims abstract description 37
- 230000008569 process Effects 0.000 claims description 127
- 230000006870 function Effects 0.000 claims description 107
- 238000010276 construction Methods 0.000 claims description 73
- 238000007726 management method Methods 0.000 claims description 37
- 230000015572 biosynthetic process Effects 0.000 claims description 32
- 230000002452 interceptive effect Effects 0.000 claims description 27
- 238000010586 diagram Methods 0.000 claims description 24
- 238000012545 processing Methods 0.000 claims description 24
- 238000011161 development Methods 0.000 claims description 22
- 230000018109 developmental process Effects 0.000 claims description 22
- 230000011218 segmentation Effects 0.000 claims description 22
- 238000013461 design Methods 0.000 claims description 21
- 230000002093 peripheral effect Effects 0.000 claims description 20
- 238000005516 engineering process Methods 0.000 claims description 13
- 230000003068 static effect Effects 0.000 claims description 12
- 230000007246 mechanism Effects 0.000 claims description 10
- 230000008520 organization Effects 0.000 claims description 10
- 238000003032 molecular docking Methods 0.000 claims description 9
- 238000005314 correlation function Methods 0.000 claims description 7
- 230000003993 interaction Effects 0.000 claims description 7
- 238000004519 manufacturing process Methods 0.000 claims description 6
- 230000000977 initiatory effect Effects 0.000 claims description 4
- 230000026676 system process Effects 0.000 claims description 4
- 230000008878 coupling Effects 0.000 claims description 3
- 238000010168 coupling process Methods 0.000 claims description 3
- 238000005859 coupling reaction Methods 0.000 claims description 3
- 238000004801 process automation Methods 0.000 claims description 3
- 230000002123 temporal effect Effects 0.000 claims description 3
- 230000003319 supportive effect Effects 0.000 abstract 5
- 238000011160 research Methods 0.000 description 10
- 238000012423 maintenance Methods 0.000 description 9
- 238000013459 approach Methods 0.000 description 8
- 239000000284 extract Substances 0.000 description 5
- 230000000694 effects Effects 0.000 description 4
- 238000003860 storage Methods 0.000 description 4
- 238000012360 testing method Methods 0.000 description 4
- 239000000203 mixture Substances 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000004904 shortening Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000003542 behavioural effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000002860 competitive effect Effects 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 230000002950 deficient Effects 0.000 description 1
- 238000009795 derivation Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 239000004615 ingredient Substances 0.000 description 1
- 230000004807 localization Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 102220038125 rs13286358 Human genes 0.000 description 1
- 102220181094 rs373609902 Human genes 0.000 description 1
- 102220162169 rs575633576 Human genes 0.000 description 1
- 102220096718 rs865838543 Human genes 0.000 description 1
- 102220037530 rs9827878 Human genes 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
Images
Landscapes
- Stored Programmes (AREA)
Abstract
This invention relates to a supportive software system creation method and its system, which is used to create a telecom operation supportive system software structure comprising the charging, settlement, operation, accounting, customer service or business analysis. The system comprises the following: a reference system to create the whole software system of the supportive system; a creation system to establish the supportive software system; a supportive software system by use of creation system.
Description
Technical field
The present invention relates to the communication software technical field, be particularly related to a kind of construction method and constructing system of software architecture of the telecom business support system of forming by functions such as charging, clearing, business, account, customer service, performance analyses (OSS/BSS:OperationsSupport System/Business Support System is hereinafter to be referred as support system).
Background technology
Current, the competition of each telecom operation enterprise increasingly sharpens, and along with reducing of hardware facility gap, the competition between each operation enterprise is with the competition in the final body service now, i.e. personalized service with high-quality, active attracts clients, yet these competition measures be unable to do without the support of support system.Support system is the system of a complexity, and its construction is not accomplished in one move, and is a progressively perfecting process, but simultaneously, the fast development in market requires support system in time to adjust and to develop again, to adapt to the development and change in market.Above situation has determined necessary quickening building of supporting system and perfect paces.
Software architecture is to forming component software and the design that concerns between them and the description of system.But effect analogy architectural design under construction the effect of software architecture in software systems, the structure of software architecture plays key effect to the whole construction speed and the construction quality of software systems, yet domestic at present, international associated mechanisms and tissue still lack research about the construction method of support system software architecture.
At present, research situation about the support system aspect, though domestic each operation enterprise has formed support system software architecture separately, but owing to emergency pressure under the pressure of engineering construction at that time, construction method to software architecture lacks research, majority is from current single practical standpoint, the architecture ubiquity one-sidedness problem that makes up, this holds system performance comprehensively and has brought certain difficulty for the user of service, also the maintenance in system's later stage has been brought certain hidden danger with further developing simultaneously.At present each operation enterprise is mainly from construction plan personnel's angle of subsystem, mainly embodied between the hierarchical block, each subsystem of each subsystem planning aspect problem such as border between border and peripheral system in the software architecture, but the content of others such as less embodiment software system design and research and development.
Tele Management Forum (TMF:TeleManagement Forum) is an alliance of non-profile international corporations that is absorbed in communications industry operation support system and problem of management.Operation system of new generation that this tissue proposes and software (NGOSS:New Generation Operation System and Software) are divided into service view, system view, realization view and operation view four parts with its knowledge hierarchy.The NGOSS standard is mainly from the soft project angle, embodied the particular content that support system relates to from links such as demand, analysis, design, integrated, deployment, tests, coverage rate is very complete, extremely valuable directive function has been played in the localization construction of operation enterprise, but aspect the support system software architecture, for how building comprehensive, perfect support system software architecture fast, also do not provide relevant systematicness suggestion at present.
About the research situation of software architecture aspect, what open distribution process reference model RM-ODP (Open Distributed Processing) standard was ISO (International Standards Organization) ISO/IEC and ITU-T in the common exploitation nineties is used to instruct the generalized reference model that open system is carried out specification description and exploitation under the distributed environment.Proposed five viewpoints in the RM-ODP standard, these five viewpoints are: enterprise's viewpoint (functional requirement of attention location system), information viewpoint, calculating viewpoint, engineering viewpoint, technology viewpoint.It is desirable that the RM-ODP standard is taked the disposal route of " dividing and rule " to complication system, promptly considers in actual the construction division demand to subsystem but lack the research of system dynamic characteristic and lack the systems organization viewpoint.
" 4+1 " view model of Rational company is that the Philippe Kruchten of Rational company proposed in nineteen ninety-five, this model clearly proposes to adopt many view approach description architecture, wherein, " 4 " view comprises logical view, process view, Physical View, exploitation view, and " 1 " view is a scene view in addition." 40 1 " are though utilize " scene " to describe the seamless cooperative mechanism of system in the view model, remedied in the traditional architectures definition and lacked the defective that dynamic perfromance is described, but the scene view that proposes in " 4+1 " view is still mainly paid close attention to scene to the test role, does not propose the composition structure of scene itself.
IEEE Std 1471-2000 is that the software architecture that IEEE recommends is described rules suggestions (industrial standard).In the standard to definition of view be: " view " is the set of the model of an aspect can describing total system.Though propose in the standard can utilize the single view of mode development and utilize a plurality of views to make up the suggestion of software architecture, but the emphasis of STD 1471-2000 standard is providing general cardinal rule, does not provide the structure suggestion of support system software architecture at the field characteristics of support system.
Therefore be that the enterprise in research centre and international symposium tissue lack the research to the software architecture construction method with the support system, the support system software architecture that has now made up is single, unilateral, though to be the mechanism in research centre and ISO (International Standards Organization) with the software architecture proposed certain suggestion to the construction method of software architecture to the descriptive system feature comprehensively, but it gives advice and only is cardinal rule, the characteristics in conjunction with support system do not provide the suggestion with operability, do not have reality for the actual construction of support system, practicable directive significance.Relevant party organizes the construction method that all lacks the system dynamics architecture to advise.
Therefore, be necessary to find a kind of effective, at the software architecture construction method of support system, to instruct operation enterprise to build perfect relatively support system software architecture fast, all sidedly, one comprehensive, perfect relatively support system software architecture constructing system is provided simultaneously, thereby assist the related personnel fast, understanding and grasping support system all sidedly, and can generate required software architecture fast, reach the pace of construction of accelerating support system, the purpose that improves the building of supporting system quality.
Summary of the invention
The objective of the invention is to propose a kind of software architecture construction method and system of telecom business support system, be in order to remedy in the support system field about software architecture construction method research defect of insufficient, remedy industry about software architecture Research on Dynamic Characteristic defect of insufficient, overcome at present ubiquitous shortcoming to support system characteristic understanding one-sidedness, in addition, the present invention also provides the system that a cover can generate required support system software architecture automatically based on the software architecture modular system storehouse of setting up, and has remedied blank about system's invention of automatic generating software architecture at present.Embodiment software architecture method of dynamic characteristics that this invention proposes and the thinking by system's automatic generating software architecture not only can be used for telecom business support system, equally also can be used for other software systems.
The object of the present invention is achieved like this:
Disclosure of the Invention of the present invention a kind of support system software architecture construction method, be used for making up and comprise charging, clearing, business, account, customer service or performance analysis at least, perhaps charge, settle accounts, business, account, customer service and performance analysis be in the software architecture of interior telecom business support system, described construction method comprises:
(1) sets up the reference hierarchy of the whole software architecture of support system;
(2) set up the constructing system of support system software architecture;
(3) utilize constructing system to generate the support system software architecture;
(4) the concrete software architecture of output generation.
The described reference hierarchy of setting up the whole software architecture of support system comprises sets up the reference hierarchy that comprises application architecture module, view architecture module and business scenario architecture module; Wherein:
Described application architecture module: be used to set up between the hierarchical block, each subsystem of each subsystem of support system border relation between border and peripheral system, satisfy that support system designer and engineering construction person use to instruct engineering the demand of subsystem definition in the operation enterprise;
Described view architecture module: be used for from analysis, the required different points of view of design and development person, set up " viewpoint is divided figure ", make up pairing groupware architecture under the different points of view, satisfy support system analysis, design and development person's demand, respectively support system is carried out one-side specific definition from some main viewpoints, and then obtain different types of view architecture module;
Described business scenario architecture module: be used for setting up the role who participates in scene, the business function that scene is finished, the collaboration process of scene, and the not only cooperation but also the relation of constraint mutually mutually between the three, satisfy user of system and tester's demand, set out with the cooperating process of paying close attention to a certain business function in related personnel's using system, describe the cooperative mechanism of all kinds of entities in the support system operation process.
Described view architecture module comprises one of functional architecture module, flow process architecture module, information architecture module, interface architecture module and technical architecture module at least.
The described constructing system of setting up the support system software architecture comprises:
(41) set up the running environment of constructing system;
(42) set up also each business module of initialization, data module, access module, its core is the modular system storehouse in foundation and the initialization data module;
Described business module comprises one of parameter management module, schema management module, mode construction module and instance management module at least, and described data module comprises one of common parameter part, modular system storehouse and case library at least.
Modular system storehouse in described foundation and the initialization data module comprises:
(61) public parameter value in the initialize mode system library comprises one of relation between MODE name, pattern, modular system topology institutional framework, pattern rank and architecture classification at least;
(62) initialize mode system basic parameter comprises one of relation between modular system title, formation pattern, pattern, modular system topology institutional framework and supplementary notes at least;
(63) comprise the application architecture pattern in the initialize mode system, the functional architecture pattern that view architecture mode and business scenario architecture mode and view architecture mode comprise, the flow process architecture mode, the information architecture pattern, the interface architecture pattern, basic parameter in one of technical architecture pattern, to set up the described pattern in the modular system storehouse, comprise MODE name, the mode of constructive system structure, the problem set that the constructive system structure need solve, the solution collection of problem set correspondence, architecture component, the inter-module relation, the formation rule collection, the architecture classification, the architecture describing mode, the pattern rank, higher level's MODE name, one of replaceable MODE name.
The application architecture pattern basic parameter of described initialize mode system library comprises the application architecture assembly at least, and described application architecture assembly comprises subsystem at least.
Described application architecture assembly also comprises level, classification and/or peripheral system.
The application architecture pattern basic parameter of described initialize mode system library also comprises:
(91) mode of structure application architecture comprises from the application of engineering project of division, positioning subsystem making up software architecture;
(92) make up the problem set that application architecture need solve, comprise at least defining subsystem; Arrange out the hierarchical relationship of each subsystem; Subsystem is sorted out processing; With define one of interface with peripheral system;
(93) the solution collection of structure problem set correspondence comprises the tightness definition subsystem according to Function Coupling at least; Contact closely with network element device that subsystem comes lower floor, the subsystem that is closely related with client's access processing capacity comes the upper strata; According to supporting production or supporting the different disposal character of performance analysis that subsystem is sorted out; Clearly go out one of peripheral system;
(94) inter-module relation comprises that a subsystem can stride many levels; A subsystem only belongs to a kind usually; Do not belong to one of any support system classification with peripheral system;
(95) formation rule collection comprises further segmentation; Do not need further segmentation and one of following layer architecture of constructing this architecture;
(96) application architecture describing mode can be the hierarchical classification block diagram.
The view architecture mode basic parameter of described initialize mode system library comprises the view architecture component at least, and described view architecture component comprises viewpoint at least.
Described view architecture component also comprises role, concrete view architecture.
The view architecture mode basic parameter of described initialize mode system library also comprises:
(121) mode of structure view architecture module: comprise demand angle at least,, make up pairing groupware architecture under the different points of view for reaching purpose deep, detail knowledge system aspect characteristic from the role;
(122) make up the problem set that the view architecture module need solve, comprise at least and find out main viewpoint; Correspondence goes out the concrete view architecture under the different points of view;
(123) the solution collection of structure problem set correspondence comprises that at least some main aspect characteristic of system of paying close attention to according to needs in analysis, design, the development support system process defines viewpoint; The different correspondences of paying close attention to content and the personnel of concern classification according to each viewpoint go out the concrete view architecture under this viewpoint;
(124) formation rule collection further makes up each concrete view architecture module of lower floor according to the viewpoint dividing condition; According to the practical experience of analysis, design, development support system, related development personnel mainly pay close attention to the characteristic of one side of function at least, flow process, information, interface, the technical system of support system;
(125) the inter-module relation comprises that at least a role can be from one or more viewpoint observing systems; A role may relate to a plurality of concrete view architectures, but because the division of duty difference of different role, and the related concrete view architecture level of different role is also different generally speaking; The corresponding different concrete view architecture of different points of view, each viewpoint one of can only corresponding concrete view architectures;
(126) view architecture describing mode can be and comprises viewpoint division figure;
The functional architecture pattern basic parameter of described initialize mode system library comprises the functional architecture assembly at least, and described functional architecture assembly comprises functional module at least.
Described functional architecture assembly also comprises the relation between level and/or functional module.
The functional architecture pattern basic parameter of described initialize mode system library also comprises:
(151) mode of constructing function architecture module comprises at least from angle structure software architecture deep, detail knowledge systemic-function characteristic;
(152) the constructing function architecture module problem set that need solve comprises defining relatively independent functional module at least; The module that defines is carried out classification to be handled; And one of the incidence relation of functional module between definite level;
(153) the solution collection of structure problem set correspondence comprises according to function proximity and granularity similarity each function is sorted out, and to form relatively independent functional module, wherein, the function proximity principle of different stage may be different; According to the granularity similarity of each functional module, the functional module that granularity is close belongs to same one-level; And/or the incidence relation of each functional module between the analysis adjacent level, if higher level's functional module realizes by subordinate's functional module combination, determine that then there is incidence relation in functional module between adjacent level;
(154) formation rule collection comprises making up subordinate's functional architecture; Lowermost layer functional module to higher level's architecture is segmented, and defines the subordinate's function that realizes bottom functional module; Subordinate's function is sorted out; And/or define the incidence relation of subordinate's functional module;
(155) the inter-module relation comprises that each functional module can only be positioned at a level; And/or if higher level's functional module realizes that by subordinate's functional module combination then there is incidence relation in functional module between adjacent level;
(156) functional architecture describing mode can be functional organization figure, promptly by organization unit functional module is described, and by the classification of institutional framework and the relation of sorting out relation between functional module is described;
(157) higher level's pattern can be the view architecture.
The flow process architecture mode basic parameter of described initialize mode system library comprises the flow process architecture component at least, and described flow process architecture component comprises between functional module/role at least and concerning.
Described flow process architecture component also comprises functional module/role.
The flow process architecture mode basic parameter of described initialize mode system library also comprises:
(181) mode of structure flow process architecture module is included as the process automation configuration purpose of realizing in the support system, from angle structure software architecture deep, detail knowledge system flow characteristic;
(182) make up the problem set that the flow process architecture module need solve, comprise the functional module or the role that relate in definite flow process; And/or define cooperation and restriction relation between each module/role;
(183) make up the solution collection of problem set correspondence, comprise in the function of reference architecture, according to granularity similarity principle or according to the actual requirements, determine the functional module or the role that relate in the overall flow about the functional module definition; And/or, locate each functional module/role's order according to the flow process sequential, define cooperation and temporal constraint relation between each module/role;
(184) formation rule collection comprises making up subordinate's flow process architecture; According to the demand of reality to the segmentation of functional module/role, about the classification and the definition of functional module, the functional module/role of higher level's architecture is segmented in the function of reference architecture, define the functional module/role of subordinate; And/or, reorientate the relation between each functional module of subordinate/role's order and each functional module/role according to the flow process sequential;
(185) the inter-module relation comprises the process according to realization certain or certain group function, determines that wherein each functional module/role gets in touch with the corresponding of various relations;
(186) flow process architecture describing mode can be sequential chart, has promptly described cooperation and restriction relation between correlation function module/role by the interactive relation of sequential chart;
(187) higher level's pattern can be the view architecture.
The information architecture pattern basic parameter of described initialize mode system library comprises the information architecture assembly at least, and described information architecture assembly comprises information field at least.
Described information architecture assembly also comprises information model.
The information architecture pattern basic parameter of described initialize mode system library also comprises:
(211) mode of structure information architecture module is included as relation between all kinds of static informations and information classification is carried out necessary constraint, from angle structure software architecture deep, detail knowledge system static information characteristic;
(212) make up the problem set that information architecture need solve, comprise marking off main information field; And/or define information model in each information field;
(213) making up the solution collection of problem set correspondence, comprise for information field at the same level, is foundation with the associating information degree, with association relatively closely information be classified as same class; And/or analyze in each information field and concern between each information, define the relevant information model;
(214) formation rule collection comprises according to the actual requirements, can further make up subordinate's information architecture; Each information field is subjected to the administration of certain function collection corresponding to certain function collection, so, but the classification of function of reference architecture is carried out classification to the corresponding information territory; And/or the segmentation of information field not necessarily produces new information, but if cause the situation of information subdivision, the new information model that produces of definition;
(215) the inter-module relation comprises that each information model generally only belongs to an information field; And/or be incidence relation information model relatively closely in the same information field;
(216) information architecture describing mode can be information model and/or information field division figure, has promptly described incidence relation between information by information model, has described the classification situation of information by information field division figure);
(217) higher level's pattern can be the view architecture.
The interface architecture pattern basic parameter of described initialize mode system library comprises the interface architecture assembly at least, and described interface architecture assembly comprises at least.
Described interface architecture assembly also comprises the interface service unit.
The interface architecture pattern basic parameter of described initialize mode system library also comprises interface object and/or interface mode:
(241) make up the mode of interface architecture module, comprise at least from deeply, the angle structure software architecture of interaction characteristic between the detail knowledge system;
(242) make up the problem set that interface architecture need solve, comprise and distinguish interactive system; Define to the required interface service unit that provides of each system is provided alternately; And/or the interactive mode between the agreement object;
(243) make up the solution collection of problem set correspondence, comprise that according to the observation interface range determines the interactive system that relates to; The information content defining interface service unit that transmits or obtain to the other side according to needs in mutual purpose and the reciprocal process; And/or according to the processing power of interactive system, system performance agreement both sides' interactive mode;
(244) formation rule collection comprises according to the actual requirements, can further make up subordinate's interface architecture; Carry out classification according to the functional class docking port architecture that the classification and the interface service unit of interface service unit are realized; High-level interface architecture can be segmented to make up subordinate's interface architecture by the classification of docking port service unit, further is subdivided into management and production interface and operation information service interface as external interface; But low level interface architecture function of reference architecture is segmented to make up subordinate's interface architecture by the function that the docking port service unit is realized; And/or, determine boundary high-level, the low level interface architecture according to actual conditions;
(245) inter-module relation comprises that an interface object can provide a plurality of interface service unit, and mutual interface object is when realizing same mutual purpose, and both sides provide the interface service unit of identical type; When the interface object that interface object is different with all the other is mutual, can adopt different interactive modes; And/or an interface service unit generally only takes a kind of interactive mode, realizes same mutual purpose and when taking the distinct interaction mode, is commonly defined as different interface service unit;
(246) the interface architecture describing mode can be message sequence chart, promptly in the message sequence chart entity description interface object, the inter-entity sequence has been represented interface service unit concrete between system, information has been represented interface message in the sequence;
(247) higher level's pattern can be the view architecture.
The technical architecture pattern basic parameter of described initialize mode system library comprises the technical architecture assembly at least, and described technical architecture assembly comprises technical parts at least.
Described technical architecture assembly also comprises the technical parts location.
The interface architecture pattern basic parameter of described initialize mode system library also comprises:
(271) mode of constructing technology architecture module comprises at least from deep, detail knowledge back-up system and implementing and turn round employed technical parts and the orientation angle structure software architecture of parts system;
(272) the constructing technology architecture problem set that need solve comprises that distinguishing back-up system implements and the employed technical parts that turns round; And/or each parts positioned;
(273) the solution collection of structure problem set correspondence comprises the character according to all kinds of technology building blocks of system, and related tightness degree each other, and all kinds of building blocks of system are sorted out; And/or every base part is positioned according to degree of support, degree of dependence and the classification situation of each base part to all the other base parts;
(274) formation rule collection comprises according to the actual requirements, can further make up subordinate's technical architecture; Because each positioning parts is by level and classification decision, so the segmentation of and classification middle-level according to higher level's technical system can be carried out subordinate's classification to technical system; According to dependence between each technical parts and supporting relation, can carry out the level Subdividing Processing to higher level's technical system, by being segmented the dependence of remainder layer, each layer make up subordinate's technical architecture; And/or according to the similarity of function, can sort out the parts of higher level's technical system and carry out Subdividing Processing, make up subordinate's technical architecture by each classification being carried out the branch subdivision;
(275) the inter-module relation comprises that level and classification that a technical parts is in are certain, so a technical parts can only have a location, and each classification comprises each level parts;
(276) technical architecture describing mode can be the hierarchical classification structural drawing;
(277) higher level's pattern can be the view architecture.
The business scenario architecture mode basic parameter of described initialize mode system library comprises the business scenario architecture component at least, and described business scenario architecture component comprises the role at least.
Described business scenario architecture component also comprises function and/or flow process.
30., it is characterized in that the business scenario architecture mode basic parameter of described initialize mode system library also comprises as claim 28 or 29 described support system software architecture construction methods:
(301) mode of structure business scenario architecture comprises that at least the dynamic cooperative operative mechanism angle of entire system from analyze professional use makes up software architecture;
(302) make up the problem set that the business scenario architecture need solve, comprise defining the assembly that participates in the scene running; And/or analyze the relation of each inter-module;
(303) the solution collection of problem set correspondence comprises user to system, for satisfying the required function of finishing of user and use is analyzed, thereby obtains the assembly that participates in the scene running; And/or to each assembly in scene mutual cooperation and mutually constraint analyze, thereby obtain each inter-module relation;
(304) inter-module relation comprises that the function that the role passes through using system realizes professional use, and the function privilege that different role can be used is different; The role finishes mutual with system by flow process; The flow process collection difference that different role can relate to; Correlation function is finished the use of whole service by the common cooperation of corresponding flow process; And/or same function related flow process difference in the different business use;
(305) formation rule collection is according to role's further segmentation and the following layer architecture of constructing this architecture of subdivision rules; And/or according to the following layer architecture of the further segmentation of the subdivision rules of functional architecture, flow process architecture with this architecture of structure;
(306) business scenario architecture describing mode can be role-function-flow process three-dimensional plot.
The described constructing system generation support system software architecture of utilizing one of comprises the steps at least:
(311) selection needs the software architecture pattern of structure;
(312) adjust initiation parameter in the modular system storehouse of selected software architecture pattern;
(313) make up each concrete software architecture, determined each parameter is carried out instantiation, make up rule, generate each software architecture example automatically according to fixed software architecture in each pattern;
(314) make up whole software architecture system,, generate the whole software architecture system of support system example automatically according to relation between the topological institutional framework of determining in each pattern, pattern based on each the concrete software architecture that has generated;
(315) the support system whole software architecture system example of output desired form and wherein each concrete software architecture example.
Described support system software architecture construction method, also comprise constructing system the modular system storehouse safeguard step, comprise at least increasing, optimizing and one of delete.
The invention also discloses a kind of support system software architecture constructing system, be used for making up and comprise charging, clearing, business, account, customer service or performance analysis at least, perhaps charge, settle accounts, business, account, customer service and performance analysis be in the software architecture of interior telecom business support system, this constructing system is made up of Access Layer, operation layer, data Layer, wherein data Layer is stored related data in the constructing system, operation layer has comprised the application processing module of constructing system at least, and Access Layer is for using the access way and the access approach of constructing system.
This constructing system also comprises interface management, the system management processing module of three layers of function cross-over connections; Wherein the interface management module is responsible for finishing with constructing system and is carried out mutual interface processing; System management module is responsible for the required bookkeeping of the normal operation of constructing system.
Described data Layer comprises one of common parameter part, modular system storehouse, case library at least, and wherein, common parameter has partly been stored constructing system needs common parameter and the required common parameter of the normal O﹠M of back-up system used in structure; The modular system library storage support system software architecture mode data and the wherein all kinds of mode data in the constructing system; Case library has been stored classical structure case and support system software architecture reference template data.
Described common parameter can comprise user of service's password and permissions data.
Described operation layer comprises one of parameter management module, schema management module, mode construction module, instance management module at least, and wherein, the parameter management module is used for all kinds of parameters are carried out maintenance management; The schema management module is used for each quasi-mode of modular system storehouse is increased, optimizes, deletes newly maintenance; The mode construction module is responsible for the flexible revision parameter value according to the initialization data of each quasi-mode in the modular system storehouse and user of service, the classics of reference example library storage make up case data simultaneously, make up the required concrete support system software architecture of user of service automatically; The instance management module is used for classics structure case and reference template are increased, optimize, delete newly maintenance.
Described Access Layer provides the access way and the access approach of all kinds of feasible use constructing systems for the user of service of constructing system and operation maintenance personnel.
Described access way comprises Web mode, Windows interface mode at least, and that described access approach comprises at least is long-range, one of LAN (Local Area Network), wired, wireless mode.
The invention also discloses a kind of support system software architecture constructing system, be used for making up and comprise charging, clearing, business, account, customer service or performance analysis at least, perhaps charge, settle accounts, business, account, customer service and performance analysis be in the software architecture of interior telecom business support system, described constructing system core ingredient is modular system storehouse and modular system wherein, concrete pattern comprises application architecture module, view architecture module and business scenario architecture module, wherein:
Described application architecture module: be used to set up between the hierarchical block, each subsystem of each subsystem of support system border relation between border and peripheral system, satisfy that support system designer and engineering construction person use to instruct engineering the demand of subsystem definition in the operation enterprise;
Described view architecture module: be used for from analysis, the required different points of view of design and development person, set up " viewpoint is divided figure ", make up pairing groupware architecture under the different points of view, satisfy support system analysis, design and development person's demand, respectively support system is carried out one-side specific definition from some main viewpoints, and then obtain different types of view architecture module;
Described business scenario architecture module: be used for setting up the role who participates in scene, the business function that scene is finished, the collaboration process of scene, and the not only cooperation but also the relation of constraint mutually mutually between the three, satisfy user of system and tester's demand, set out with the cooperating process of paying close attention to a certain business function in related personnel's using system, describe the cooperative mechanism of all kinds of entities in the support system operation process.
Described view architecture module comprises at least with one of lower module:
Functional architecture module: be used to set up level and incidence relation between functional entity and functional entity;
Flow process architecture module: be used to set up rank and incidence relation between flow process and flow process;
Information architecture module: be used to set up the static information that each functional domain is managed, mainly comprise one of information model, information classification at least;
Interface architecture module: be used to set up between functional entity, carry out mutual related multidate information between functional entity and outside role, mainly comprise one of interface content, interface mode at least.
Technical architecture module: set up the technical system of application software, mainly comprise at least between back-up system is implemented and running is adopted parts, parts one of concerning.
The assembly of application architecture module comprises subsystem, level, classification at least described in the described modular system storehouse, and/or peripheral system, and one of them subsystem can be striden many levels; A subsystem only belongs to a kind; And/or peripheral system does not belong to the classification of any support system.
View architecture module described in the described modular system storehouse comprises one of role, viewpoint, concrete view architecture at least, and wherein, a role can be from one or more viewpoint observing systems; A role may relate to a plurality of concrete view architecture modules, but because the division of duty difference of different role, and the related concrete view architecture module level of different role is also different generally speaking; And/or the corresponding different concrete view architecture module of different points of view, each viewpoint can only corresponding concrete view architecture module.
Functional architecture module described in the described modular system storehouse comprises at least between functional module, level, functional module and one of concerning that wherein, each functional module can only be positioned at a level; And/or if higher level's functional module realizes that by subordinate's functional module combination then there is incidence relation in functional module between adjacent level.
Flow process architecture module described in the described modular system storehouse comprises at least between functional module/role, functional module/role and one of concerning, wherein, determine that wherein each functional module/role gets in touch with the corresponding of various relations according to the process of realization certain or certain group function.
The information architecture module comprises one of information field, information model at least described in the described modular system storehouse, and wherein, each information model generally only belongs to an information field; And/or be incidence relation information model relatively closely in the same information field.
The interface architecture module comprises one of interface object, interface service unit, interface mode at least described in the described modular system storehouse, wherein, an interface object can provide a plurality of interface service unit, mutual interface object is when realizing same mutual purpose, and both sides provide the interface service unit of identical type; When the interface object that interface object is different with all the other is mutual, can adopt different interactive modes; And/or an interface service unit generally only takes a kind of interactive mode, realizes same mutual purpose and when taking the distinct interaction mode, is commonly defined as different interface service unit.
Technical architecture module described in the described modular system storehouse comprises one of technical parts, technical parts location at least, wherein, level and classification that technical parts is in are certain, and a technical parts can only have a location, and each classification comprises each level parts.
The business scenario architecture module comprises one of role, function, flow process at least described in the described modular system storehouse, and wherein, the role realizes professional use by the function of using system, and the function privilege that different role can be used is different; The role finishes mutual with system by flow process; The flow process collection difference that different role can relate to; Correlation function is finished the use of whole service by the common cooperation of corresponding flow process; And/or same function related flow process difference in the different business use.
From the above description, implementation procedure and relative theory as seen, the modular system storehouse that utilizes the present invention to propose makes up support system and has the following advantages:
(1) simple, practical, easy to operate, easy realization: it is the empirical mode of passing through practical proof that the complex software architecture structure problem of complicated support system is converted into the support system software architecture reference template that simple pattern is extracted and pattern provides problem the present invention to propose, and has practicable practicality.
(2) open good: the modular system that the present invention proposes and wherein the parameter of each pattern all have opening, can adjust and further perfect according to actual conditions.
(3) make up the quality height: utilize pattern, the constructing plan of reusable similar software architecture, to accelerate structure speed and to utilize the relation of replenishing mutually between each pattern in the modular system, can build comprehensive software architecture to solve the one-sidedness problem that exists in the structure by the utilization of experimental knowledge in the past being improved the structure quality.
(4) adaptability is strong: the invention provides one and be enclosed within comprehensive, complete relatively support system software architecture reference template at present, applicable to the support system software architecture structure problem of different operation enterprises.
(5) directiveness is strong: the present invention has been for telecom operation enterprise provides a kind of effective support system software architecture construction method, solved present support system software architecture and had one-sidedness and make up slow-footed problem in making up; For each side personnel such as the analysis of support system, design, test, use provide a kind of deeply, the method and the approach of complete understanding support system intension, improved operation enterprise related personnel's quality.
(6) enhance the competitiveness: by structure speed, the shortening of shortening the support system software architecture and the understanding process of deepening the support personnel, carry out for the new business of operation enterprise and to have striven for market hours, and improved the support quality, thereby strengthen the competitive power of operation enterprise.
Description of drawings
Fig. 1 is a general flow chart of the present invention;
Fig. 2 is for setting up the whole software architecture reference hierarchy process flow diagram of support system among the present invention;
Fig. 3 is whole software architecture reference hierarchy figure among the present invention;
Fig. 4 is support system software architecture constructing system among the present invention;
Fig. 5 is for setting up the constructing system process flow diagram of support system software architecture among the present invention;
Fig. 6 is application architecture module diagram among the present invention;
Fig. 7 is view architecture module synoptic diagram among the present invention;
Fig. 8 is functional architecture module diagram among the present invention;
Fig. 9 is flow process architecture module synoptic diagram among the present invention;
Figure 10 is information architecture module diagram among the present invention;
Figure 11 is interface architecture module diagram among the present invention;
Figure 12 is technical architecture module diagram among the present invention;
Figure 13 is business scenario architecture module synoptic diagram among the present invention;
Figure 14 is restriction relation between " role-flow process " in the business scenario architecture module among the present invention;
Figure 15 is restriction relation between " function-flow process " in the business scenario architecture module among the present invention;
Figure 16 generates concrete support system software architecture process flow diagram for constructing system among the present invention;
Figure 17 is the process flow diagram of safeguarding in modular system storehouse among the present invention;
Figure 18 is for obtaining customer demand business scenario architecture module output result schematic diagram among the present invention.
Embodiment
Support system software architecture construction method proposed by the invention not only is suitable for the static nature of descriptive system, and is suitable for the behavioral characteristics of descriptive system, has multi-faceted property; Support system software architecture constructing system described in the invention can satisfy the structure demand of all kinds of related personnel of support system about architecture, has adaptability widely.
Below main-process stream of the present invention and concrete technical scheme are described in detail:
Main-process stream of the present invention is seen Fig. 1, comprises step 11 at least, sets up the whole software architecture reference hierarchy of support system; Step 12 is set up the constructing system of support system software architecture; Step 13 utilizes constructing system to generate concrete practical support system software architecture; Step 14, the concrete support system software architecture that output generates.
Specifically:
From different personnel's demand, from multi-angle the feature of support system is described, step 21 from the angle of engineering construction person with the designer, is set up support system application architecture module 34; Step 22 from analysis, design and development person's angle, is set up support system view architecture module 35; Step 221 from the function viewpoint, is set up the functional architecture module; Step 222 from the flow process viewpoint, is set up the flow process architecture module; Step 223 from the information viewpoint, is set up the information architecture module; Step 224 from the interface viewpoint, is set up the interface architecture module; Step 225 from the technology viewpoint, is set up the technical architecture module; Step 23 from using and tester's angle, is set up the business scenario architecture module of support system; Step 24 is finished the whole software architecture reference hierarchy of setting up support system.
According to shown in Figure 3, set up the whole software architecture reference hierarchy of comprehensive, perfect relatively support system, telecom business support system architecture 31 is divided into static architecture 32 and dynamic architecture 33, and static architecture 32 comprises application architecture module 34 and view architecture module 35 at least, dynamic architecture 33 comprises that at least business scenario architecture module 36 can replenish integral system according to Future Development, wherein:
Application architecture module 34: be used to set up between the hierarchical block, each subsystem of each subsystem of support system border relation between border and peripheral system; Satisfy mainly that support system designer and engineering construction person are applied as purpose to the demand of subsystem definition to instruct engineering in the operation enterprise.
View architecture module 35: be used for setting up " viewpoint is divided figure " from analysis, the required different points of view of design and development person, make up pairing groupware architecture under the different points of view; Mainly satisfy support system analysis, design and development person's demand, from some main viewpoints (as, function, flow process, information, interface, Technical Architecture) respectively support system is carried out one-side specific definition, and then obtain different types of view architecture module.
Functional architecture module 351: set up level and incidence relation between functional entity and functional entity.
Flow process architecture module 352: set up rank and incidence relation between flow process and flow process.
Information architecture module 353: set up the static information that each functional domain is managed, mainly comprise information model, information classification at least.
Interface architecture module 354: set up between functional entity, carry out mutual related multidate information between functional entity and outside role, mainly comprise interface content, interface mode at least.
Technical architecture module 355: set up the technical system of application software, mainly comprise at least between back-up system is implemented and running is adopted parts, parts concerning.
Business scenario architecture module 36: be used for setting up the role who participates in scene, the business function that scene is finished, the collaboration process of scene, and not only cooperation but also the relation that retrains mutually mutually between the three; Mainly satisfy user of system and tester's demand, set out with the cooperating process of paying close attention to a certain business function in related personnel's using system, the cooperative mechanism of describing all kinds of entities in the support system operation process is a purpose.
Support system software architecture constructing system of the present invention is made up of " access, professional, data " three layers, sees shown in Figure 4.Related data in " data Layer " storage constructing system, " operation layer " comprised the application processing module of constructing system at least, " Access Layer " is for using the access way and the access approach of constructing system.
" data Layer " mainly comprises common parameter part 41, modular system storehouse 42, case library 43 at least.Wherein, common parameter part 41 has been stored constructing system needs common parameter and the required common parameter of the normal O﹠M of back-up system used in structure, as user of service's password and permissions data; Support system software architecture mode data and the wherein all kinds of mode data in the constructing system stored in modular system storehouse 42, as the initiation parameter value of each quasi-mode; Case library 43 has been stored classical structure case and support system software architecture reference template data.Following italic why?
" operation layer " mainly comprises parameter management module 44, schema management module 45, mode construction module 46, instance management module 47 at least, and other has the interface management 48 of three layers of function cross-over connections, system management to handle module 49.Wherein, parameter management module 44 is responsible for all kinds of parameters are carried out maintenance management; Schema management module 45 is responsible for each quasi-mode in the modular system storehouse is increased, optimizes, deletes newly maintenance; Mode construction module 46 is responsible for according to the initialization data of each quasi-mode in the modular system storehouse and user of service's flexible revision parameter value, the classics of reference example storehouse 43 storages simultaneously make up case data, make up the required concrete support system software architecture of user of service automatically; Instance management module 47 is responsible for classics structure case and reference template are increased, optimize, delete newly maintenance; Interface management module 48 is responsible for finishing with constructing system and is carried out mutual interface processing, as automatic importing, the derivation of mode data; System management module 49 is responsible for the required bookkeeping of the normal operation of constructing system, as daily record, rights management.
" Access Layer " provides the access way and the access approach of all kinds of feasible use constructing systems for the user of service of constructing system and operation maintenance personnel, access way commonly used has Web mode, Windows interface mode etc., and that the access approach has is long-range, LAN (Local Area Network), wired, wireless etc.
According to the composition of support system software architecture constructing system shown in Figure 4, set up each application module, database and realize relevant access way.Wherein, the core of constructing system is the modular system storehouse, its method for building up is: in conjunction with the characteristics of support system, and conclude, sum up according to practical experience, extract support system software architecture masterplates dissimilar among Fig. 3 and make up rule, form the modular system storehouse of support system software architecture constructing system.
Utilize the masterplate in the modular system storehouse and make up rule, real needs during in conjunction with practical application, and related data in the reference example storehouse, adjust and the instantiation correlation parameter, support system software architecture constructing system generates all kinds of support system software architectures of practical requirement automatically.
Describe step 12 of the present invention below in detail, how to set up the constructing system of support system software architecture, idiographic flow is seen Fig. 5:
At first, set up the running environment of constructing system; Then, set up the also modular system storehouse of initialization constructing system.
1. MODE name: C1=" application architecture pattern "; C2=" vision architecture mode "; C3=" business scenario architecture mode "; C21=" functional architecture pattern "; C22=" flow process architecture mode "; C23=" information architecture pattern "; C24=" interface architecture pattern "; C25=" technical architecture pattern ";
2. concern between pattern: (1)＜Ci, Ci, Cl ... 〉=k.When k=01, be " complementary relationship at the same level "; When k=02, be " set membership ", and Ci is that father, the Ci of Ci is the father of Cl; When k=03, be " fallback relationship ", and replace priority and arrange in order, have precedence over Cl as Ci and replace Ci.(2)<Ci<Ci1，Ci2，…>>＝k。When k==10, be " the many subrelations of a father ", and Ci1 and the same father Ci of Ci2.…
3. modular system topology institutional framework: when Tsaps=1, be by " tree type "; When Tsaps=2, be " pattern ";
4. pattern rank: when L=1, be " one-level "; When L=2, be " secondary ", and " secondary " is lower than " one-level ";
5. architecture classification: when Type=1, be " static architecture module "; When Type=2, be " dynamic architecture module ";
6. every default definition: NULL.
Modular system title＜=" telecom business support system software architecture modular system "
The formation pattern＜=＜C1, C2＜C21, C22, C23, C24, C25 〉, C3 ...
Relation between pattern＜=＜＜C1, C2, C3 〉=01,＜C21, C22, C23, C24, C25 〉=01,＜C2＜C21, C22, C23, C24, C25〉〉=10 ...
Modular system topology institutional framework＜=1
Supplementary notes＜=", can only select C1 if only be concerned about practical engineering application; Can replenish selection C2 if be concerned about system development; Can replenish selection C3 if be concerned about system testing; C1, C2, C3 are selected in suggestion simultaneously; ... "
Describe the foundation of all kinds of concrete patterns in the modular system storehouse below in detail:
According to following order, required following basic parameter in all kinds of concrete patterns foundation is carried out initialization, comprise application architecture pattern, view architecture mode and business scenario architecture mode at least.
1, application architecture pattern, application architecture synoptic diagram such as Fig. 6? shown in.
Step 551 (Fig. 5), the following basic parameter of initialization application architecture pattern:
MODE name=C1
The mode of structure application architecture=" make up software architecture from the application of engineering project of division, positioning subsystem; ... "
The problem set that the structure application architecture need solve=" define subsystem; Arrange out the hierarchical relationship of each subsystem; Subsystem is sorted out processing; Define interface with peripheral system; ... "
The solution collection of problem set correspondence=" according to the tightness definition subsystem of Function Coupling; Contact closely with network element device that subsystem comes lower floor, the subsystem that is closely related with client's access processing capacity comes the upper strata; According to supporting production or supporting the different disposal character of performance analysis that subsystem is sorted out; Clearly go out peripheral system; ... "
The application architecture assembly=＜subsystem, level, classification, peripheral system ...
The inter-module relation=＜＜subsystem, level 〉=" subsystem can be striden many levels ";＜subsystem, classification 〉=" subsystem only belongs to a kind usually ";＜peripheral system, classification 〉=" peripheral system does not belong to any support system classification ";
{ formation rule collection }=" generally speaking, do not need further segmentation and the following layer architecture of constructing this architecture; ... "
Application architecture module classification=1
Application architecture module describing mode=" hierarchical classification block diagram ";
Pattern rank=1
Higher level MODE name=NULL
Replaceable MODE name=NULL
2, view architecture mode, view architecture module synoptic diagram is shown in Fig. 7 " viewpoint is divided figure ".
Step 552 (Fig. 5), the following basic parameter of initialization view architecture mode:
MODE name＜=C2
The mode of structure view architecture module=",, make up pairing groupware architecture under the different points of view for reaching purpose deep, detail knowledge system aspect characteristic from analysis, design, developer's (role) demand angle; ... "
The problem set that structure view architecture module need solve=" find out main viewpoint; Correspondence goes out the concrete view architecture module under the different points of view; ... "
The solution collection of structure problem set correspondence=" some the main aspect characteristic of system according to needs concern in analysis, design, the development support system process defines viewpoint; The different correspondences of paying close attention to content and the personnel of concern classification according to each viewpoint go out the concrete view architecture module under this viewpoint; ... "
View architecture module assembly=＜role, viewpoint, concrete view architecture module ...
Inter-module relation=＜＜role, viewpoint 〉=" role can from one or more viewpoint observing systems ";＜role, concrete view architecture module 〉=" role may relate to a plurality of concrete view architecture modules; but because the division of duty difference of different role, and the related concrete view architecture module level of different role is also different generally speaking ";＜viewpoint, concrete view architecture module 〉=" the concrete view architecture module that different points of view is corresponding different, each viewpoint can only corresponding concrete view architecture module ";
Formation rule collection=" further make up each concrete view architecture module of lower floor according to the viewpoint dividing condition; Practical experience according to analysis, design, development support system, related development personnel mainly pay close attention to function, flow process, information, the interface of support system, the characteristic of technical system aspect, are function, flow process, information, interface, technical architecture module so need the concrete view architecture module of lower floor of definition in this project; ... "
View architecture module classification=1
View architecture module describing mode=" viewpoint is divided figure ";
Pattern rank=1
Higher level MODE name=NULL
Replaceable MODE name=NULL
In above-mentioned view architecture mode, mainly comprise function, flow process, information, interface, technology five architecture patterns at least:
(1) functional architecture pattern, the functional architecture synoptic diagram is shown in Fig. 8 " functional organization figure ".
0 grade of function comprises at least: customer demand, client's identification, marketing, customer service, customer value
1 grade of function comprises at least: corresponding to marketing, for opening an account, change card or the like.
MODE name=C21
The mode of constructing function architecture module=" from angle structure software architecture deep, detail knowledge systemic-function characteristic; ... "
The problem set that the constructing function architecture module need solve=" define relatively independent functional module; The module that defines is carried out classification to be handled; Determine the incidence relation of functional module between level; ... "
The solution collection of structure problem set correspondence=" according to function proximity and granularity similarity each function is sorted out, to form relatively independent functional module, wherein, the function proximity principle of different stage may be different; According to the granularity similarity of each functional module, the functional module that granularity is close belongs to same one-level; Analyze the incidence relation of each functional module between adjacent level, if higher level's functional module is realized that by subordinate's functional module combination there is incidence relation in functional module between then definite adjacent level; ... "
The functional architecture modular assembly=＜functional module, level concerns between functional module ...
The inter-module relation=＜＜functional module, level 〉=" each functional module can only be positioned at a level ";＜functional module concerns between functional module 〉=" if higher level's functional module realizes that by subordinate's functional module combination then there is incidence relation in functional module between adjacent level ";
Formation rule collection=" according to the actual requirements, can further make up subordinate's functional architecture module; Lowermost layer functional module to higher level's architecture module is segmented, and defines the subordinate's function that realizes bottom functional module; Subordinate's function is sorted out; Define the incidence relation of subordinate's functional module; ... "
Functional architecture module classification=1
Functional architecture module describing mode=" functional organization module map " (by organization unit functional module is described, relation between functional module is described) by the classification of institutional framework and the relation of sorting out;
Pattern rank=2
Higher level MODE name=C2
Replaceable MODE name=NULL
(2) flow process architecture mode, the flow process architectural schematic is shown in Fig. 9 " sequential chart ".Its flow process is for obtaining demand, identification demand, marketing, service, analysis.
MODE name=C22
The mode of architecture module " make up flow process "=" for realizing the process automation configuration purpose in the support system, from deeply, the angle of detail knowledge system flow characteristic makes up the software architecture module; ... "
Make up the problem set that the flow process architecture module need solve=" determine the functional module or the role that relate in the flow process; Define cooperation and restriction relation between each module/role; ... "
The solution collection of problem set correspondence=" in the function of reference architecture module about functional module definition, according to granularity similarity principle or according to the actual requirements, determine the functional module or the role that relate in the overall flow; According to the flow process sequential, locate each functional module/role's order, define cooperation and temporal constraint relation between each module/role; ... "
Flow process architecture module assembly=＜functional module/role, concern between functional module/role ...
The inter-module relation=＜＜functional module/role, concern between functional module/role=", determining that wherein each functional module/role gets in touch with the corresponding of various relations " according to the process of realization certain or certain group function;
Formation rule collection=" according to the actual requirements, can further make up subordinate's flow process architecture module; According to the demand of reality to the segmentation of functional module/role, about the classification and the definition of functional module, the functional module/role of higher level's architecture module is segmented in the function of reference architecture module, define the functional module/role of subordinate; According to the flow process sequential, reorientate the relation between each functional module of subordinate/role's order and each functional module/role; ... "
Flow process architecture module classification=1
Flow process architecture module describing mode=" sequential chart " (having described cooperation and restriction relation between correlation function module/role) by the interactive relation of sequential chart;
Pattern rank=2
Higher level MODE name=C2
Replaceable MODE name=NULL
(3) information architecture pattern, the information architecture module diagram is shown in Figure 10 " information model+information field is divided figure ".
MODE name=C23
Make up the mode of information architecture module=" for relation between all kinds of static informations and information classification are carried out necessary constraint, from deeply, the angle of detail knowledge system static information characteristic makes up the software architecture module; ... "
The problem set that structure information architecture module need solve=" mark off main information field; Define the information model in each information field; ... "
Make up the solution collection of problem set correspondence=" for information field at the same level, be foundation with the associating information degree, with association relatively closely information be classified as same class; Analyze in each information field and concern between each information, define the relevant information model; ... "
The information architecture modular assembly=＜information field, information model ...
The inter-module relation=＜＜information field, information model 〉=" each information model generally only belongs to an information field "; " in the same information field is incidence relation information model relatively closely ";
Formation rule collection=" according to the actual requirements, can further make up subordinate's information architecture module; Each information field is subjected to the administration of certain function collection corresponding to certain function collection, so, but the classification of function of reference architecture module is carried out classification to the corresponding information territory; The segmentation of information field not necessarily produces new information, but if cause the situation of information subdivision, the new information model that produces of definition; ... "
Information architecture module classification=1
Information architecture module describing mode=" information model+information field divide figure " (described incidence relation between information by " information model ", described the classification situation of information by " information field is divided figure ");
Pattern rank=2
Higher level MODE name=C2
Replaceable MODE name=NULL
(4) interface architecture pattern, the interface architecture module diagram is shown in Figure 11 " message sequence chart ".
MODE name=C24
Make up the mode of interface architecture module=" from deeply, the angle of interaction characteristic makes up the software architecture module between the detail knowledge system; ... "
The problem set that structure interface architecture module need solve=" distinguish interactive system; Define to the required interface service unit that provides of each system is provided alternately; Interactive mode between the agreement object; ... "
The solution collection of problem set correspondence=" interface range is according to the observation determined the interactive system that relates to; The information content defining interface service unit that transmits or obtain to the other side according to needs in mutual purpose and the reciprocal process; According to the processing power of interactive system, system performance agreement both sides' interactive mode; ... "
The interface architecture modular assembly=＜interface object, interface service unit (multidate information that contains interactive interfacing), interface mode (as the interface message form of expression, interface communications protocol etc.) ...
Inter-module relation=＜＜interface object, the interface service unit 〉=" interface object can provide a plurality of interface service unit, and mutual interface object is when realizing same mutual purpose, and both sides provide the interface service unit of identical type ";＜interface object, interface mode 〉=" when the interface object that interface object is different with all the other is mutual, can adopt different interactive modes ";＜interface service unit, interface mode 〉=" interface service unit is generally only taked a kind of interactive mode to realize same mutual purpose and when taking the distinct interaction mode, is commonly defined as different interface service unit ";
Formation rule collection=" according to the actual requirements, can further make up subordinate's interface architecture module; The functional class docking port architecture module of realizing according to the classification of interface service unit and interface service unit carries out classification segmentation that the high-level interface architecture module of classification can be by the docking port service unit to make up subordinate's interface architecture module, further is subdivided into management and production interface and operation information service interface as external interface; But low level interface architecture module function of reference architecture module segments to make up subordinate's interface architecture module by the function that the docking port service unit is realized; According to actual conditions, determine boundary high-level, low level interface architecture module; ... "
Interface architecture module classification=1
Interface architecture module describing mode=" message sequence chart " (in the message sequence chart entity description interface object, the inter-entity sequence has been represented interface service unit concrete between system, information has been represented interface message in the sequence);
Pattern rank=2
Higher level MODE name=C2
Replaceable MODE name=NULL
(5) technical architecture pattern, the technical architecture module diagram is shown in Figure 12 " hierarchical classification construction module figure ".
MODE name=C25
The mode of constructing technology architecture module=" from deeply, detail knowledge back-up system implement and turn round employed technical parts and the orientation angle of parts system make up the software architecture module; ... "
The problem set that the constructing technology architecture module need solve=" distinguishing back-up system implements and the employed technical parts that turns round; Each parts is positioned; ... "
The solution collection of problem set correspondence=" according to the character (as belonging to data class, business processing class, access processing class etc.) of all kinds of technology building blocks of system; and related tightness degree each other (be divided into the interface management class, use and handle class, system management class etc. as the business processing class), all kinds of building blocks of system are sorted out; According to degree of support, degree of dependence and the classification situation of each base part every base part is positioned all the other base parts; ... "
The technical architecture modular assembly=＜technical parts, technical parts location (comprising parts level of living in and institute's belonging kinds at least) ...
The inter-module relation=＜＜technical parts, technical parts location 〉=" level and classification that technical parts is in are certain; so a technical parts can only have a location, and each classification comprises each level parts (handle class and comprise data Layer, operation layer, Access Layer parts as using) ";
Formation rule collection=" according to the actual requirements, can further make up subordinate's technical architecture module; Because each positioning parts is by level and classification decision, so the segmentation of and classification middle-level according to higher level's technical system can be carried out subordinate's classification to technical system; According to dependence between each technical parts and supporting relation, can carry out the level Subdividing Processing to higher level's technical system, by being segmented the dependence of remainder layer, each layer make up subordinate's technical architecture module; According to the similarity of function, can sort out the parts of higher level's technical system and carry out Subdividing Processing, make up subordinate's technical architecture module by each classification being carried out the branch subdivision; ... "
Technical architecture module classification=1
Technical architecture module describing mode=" hierarchical classification construction module figure " (the middle-level dependence of having described between each parts of hierarchical classification construction module figure, classified description the classification situation of each parts);
Pattern rank=2
Higher level MODE name=C2
Replaceable MODE name=NULL
3, business scenario architecture mode, business scenario architecture module synoptic diagram is shown in " role-function-flow process " three-dimensional plot of Figure 13.To the result of study of business scenario architecture module effect, common software architecture mode attribute has been increased " business scenario architecture module purposes " Purp attribute according to the present invention.
Step 553 (Fig. 5), the following basic parameter of initialization business scenario architecture mode:
MODE name=C3
Make up mode=" the dynamic cooperative operative mechanism angle of the entire system structure software architecture module from analyze professional use of business scenario architecture module; ... "
The problem set that structure business scenario architecture module need solve=" define the assembly that participates in the scene running; Analyze the relation of each inter-module; ... "
Make up the solution collection of problem set correspondence=", thereby obtain the assembly that participates in the scene running to the user of system, for satisfying the required function of finishing of user and use is analyzed; Mutual cooperation and mutual constraint in scene analyzed to each assembly, thereby obtains each inter-module relation; ... "
Business scenario architecture module assembly=＜outside role, intraware i, intraware j ... the role of 〉=＜, function, flow process ...
The inter-module relation=＜＜outside role, intraware i 〉;＜intraware i, intraware j 〉; 〉=＜＜role, function 〉;＜role, flow process 〉;＜flow process, function 〉; 〉=＜" role realizes professional use by the function of using system, and the function privilege that different role can be used is different "; " role finishes mutual with system by flow process; The flow process collection difference that different role can relate to "; " the same function of use related flow process difference in the different business use that correlation function is finished whole service by the common cooperation of corresponding flow process ";
The formation rule collection=" according to role's further segmentation and lower floor's architecture module of constructing this architecture module of subdivision rules; Further segmentation and lower floor's architecture module of constructing this architecture module of subdivision rules according to functional architecture module, flow process architecture module; ... "
Business scenario architecture module classification=2
Business scenario architecture module describing mode=" role-function-flow process three-dimensional plot ".Restriction relation has been described specific role and can only have been used specific one group of function as shown in figure 14 between " role-flow process ", and this group function i.e. role's action scope for this reason; Restriction relation has been described specific flow process and can only is by one group of specific function cooperation and finished as shown in figure 15 between " function-flow process ";
Pattern rank=1
Higher level MODE name=NULL
Replaceable MODE name=NULL
Business scenario architecture module purposes=" be easy to intuitivism apprehension system; Embody the overall operation core of support system; Instruct support system internal process, function and outside role's division and tissue "
Step 56 (Fig. 5) is finished the constructing system of setting up the support system software architecture.
Describe step 13 of the present invention below in detail, how to utilize constructing system to generate concrete practical support system software architecture, idiographic flow is seen Figure 16.：
(1) preference pattern: the parameter of modular system SAPS " supplementary notes " Dsaps in the reference model system library, according to actual conditions, the user of service need to select the software architecture pattern of structure, step 161.
(2) adjust initiation parameter: at software architecture pattern selected in the step 161, according to the actual requirements, the user of service replenishes, adjusts step 162 initialized default parameter in the modular system storehouse.
(3) make up each concrete software architecture: each parameter of determining in the step 162 is carried out instantiation (can directly utilize the default instantiation data that carry in the system, also can manually import as required), step 163; Constructing system makes up regular Rule according to fixed software architecture among each Mode S AP, generates each software architecture example automatically, step 164.As, in " functional architecture pattern " " Comp=functional architecture modular assembly=＜functional module, level concerns between functional module; ... " can be instantiated as＜＜customer demand, client's identification, marketing, customer service, customer value 〉, 0 grade, concern between functional module ....Judge whether to finish the structure work of all selected software architectures, step 165; If not, return step 162, if continue next step, step 166.
(4) make up whole software architecture system: constructing system is based on each the concrete software architecture that has generated, according to concerning between the topological institutional framework Tsaps that determines among the SAPS, pattern that Rsaps generates the whole software architecture system of support system example, step 166 automatically.
(5) output makes up the result: according to the self-defined mode of user of service, the whole software architecture system of the support system example of output desired form reaches wherein each concrete software architecture example, step 167.
Referring to Figure 17, the modular system storehouse safeguard process flow diagram.According to actual operating position, the modular system storehouse of constructing system needs to be serviced under the situation that produce to trigger service mode system database condition, so as to continue to optimize, perfect, carry out the wherein life cycle management of each pattern, safeguard that specifically flow process comprises at least:
(1) increases new model:, extract it and form parameters such as assembly, inter-module relation, structure rule, step 1721,1722,1723 for the architecture demand of new generation; Generate newly-increased pattern and initialization, step 1724; Determine the position of this pattern in whole modular system, step 1725; Newly-generated pattern is added modular system storehouse, step 1726.
(2) optimize existing pattern: according to operating position, to the default parameter of existing pattern be optimized, perfect, and the classical case that will often use deposits in the case library, so that directly call the related example data during instantiation.Specifically comprise at least: step 1711, the parameter type in the newly-increased pattern; Step 1712 is deleted unnecessary parameter type; Step 1713, the initialized default value of correlation parameter in the adjustment modes; Step 1714 is adjusted the topological structure of whole modular system; Step 1715 deposits the classical mode case of often using in the case library in.
(3) delete useless pattern: each applying unit can be according to the handling characteristics of this enterprise, the pattern that is not used for a long time in the puncturing pattern system library.Specifically comprise at least: step 1731, confirm the deletion condition; Step 1732, the pattern of deletion condition is satisfied in selection; Step 1733 is known associative mode data in the modular system storehouse; Step 1734 is adjusted the topological structure of whole modular system.
According to use experience and service regeulations, also constructing system can be built up intellectualizing system, with the service regeulations of using in the attributes composition knowledge bases such as situation, application target, use schema category, can carry out the intellectuality prompting to relevant user of service.
Provide the constructed embodiment of a concrete business scenario architecture module that proposes based on the present invention below, be illustrated so that the pattern that proposes in this project is used, so that more understand content of the present invention and purposes.
Present embodiment is that this business scenario is an example " to obtain the customer service demand " in the customer life cycle, needs the parameter of instantiation to comprise at least: the assembly of compositional system construction module, inter-module relation, formation rule collection.
For normal client: the marketing personal is with the questionnaire input customer service system of formulating, the business configuration personnel of customer service system are according to the concrete outbound call policy of questionnaire configuration of input, customer service system is carried out outgoing call automatically according to collocation strategy and is handled to finish survey task customer service system the questionnaire of client and affiliate's feedback is offered the marketing personal, the marketing personal utilizes operation analysis system to analyze that the client proposes the rationality of demand in the questionnaire, thereby extracts practicable demand collection.
For big customer and affiliate: the function that the marketing personal utilizes big customer's service system to provide, obtain big customer and affiliate's feedback questionnaire, and utilize the operation analysis system analysis, extract rational demand collection.
" assembly (role, function, flow process) " parameter is carried out following instantiation in the business scenario architecture mode to constructing system:
Role: client, affiliate, marketing personal, business configuration personnel; Function: customer service functions, big customer's service function, performance analysis function; Flow process: market survey, demand analysis.
" inter-module relation " parameter is carried out following instantiation in the business scenario architecture mode to constructing system:
＜role, function 〉: see Table 1 " role-function " relation;
＜flow process, function 〉: see Table 2 " flow process-functions " relation;
＜role, flow process 〉: see Table 3 " role-flow processs " relation.
Table 1
Table 2
Table 3
" formation rule collection " carries out following instantiation in the business scenario architecture mode to constructing system:
Rule={ formation rule collection }={ " the instantiation result according to above role does not need further segmentation and lower floor's architecture module of constructing this architecture module " }
According to business scenario architecture module instantiation parameter and structure rule, make up " obtaining the customer service demand " business scenario architecture module, and outgoing traffic scene architecture module, its output the results are shown in shown in " role-function-flow process " three-dimensional plot of Figure 18.
Claims (31)
1. support system software architecture construction method is characterized in that described construction method comprises at least:
(1) sets up the reference hierarchy of the whole software architecture of support system;
(2) set up the constructing system of support system software architecture;
(3) utilize constructing system to generate the support system software architecture;
(4) the concrete software architecture of output generation;
The described constructing system generation support system software architecture of utilizing comprises the steps:
(311) selection needs the software architecture pattern of structure;
(312) adjust initiation parameter in the modular system storehouse of selected software architecture pattern;
(313) make up each concrete software architecture, determined each parameter is carried out instantiation, make up rule, generate each software architecture example automatically according to fixed software architecture in each pattern;
(314) make up whole software architecture system,, generate the whole software architecture system of support system example automatically according to relation between the topological institutional framework of determining in each pattern, pattern based on each the concrete software architecture that has generated;
(315) the support system whole software architecture system example of output desired form and wherein each concrete software architecture example.
2. support system software architecture construction method as claimed in claim 1, it is characterized in that the described reference hierarchy of setting up the whole software architecture of support system comprises that at least foundation comprises the reference hierarchy of application architecture module, view architecture module and business scenario architecture module at least; Wherein:
Described application architecture module: be used to set up between the hierarchical block, each subsystem of each subsystem of support system border relation between border and peripheral system, satisfy that support system designer and engineering construction person use to instruct engineering the demand of subsystem definition in the operation enterprise;
Described view architecture module: be used for from analysis, the required different points of view of design and development person, set up " viewpoint is divided figure ", make up pairing groupware architecture under the different points of view, satisfy support system analysis, design and development person's demand, respectively support system is carried out one-side specific definition from some main viewpoints, and then obtain different types of view architecture module;
Described business scenario architecture module: be used for setting up the role who participates in scene, the business function that scene is finished, the collaboration process of scene, and the not only cooperation but also the relation of constraint mutually mutually between the three, satisfy user of system and tester's demand, set out with the cooperating process of paying close attention to a certain business function in related personnel's using system, describe the cooperative mechanism of all kinds of entities in the support system operation process.
3. support system software architecture construction method as claimed in claim 2, it is characterized in that described view architecture module comprises one of functional architecture module, flow process architecture module, information architecture module, interface architecture module and technical architecture module at least.
4. support system software architecture construction method as claimed in claim 2 is characterized in that, the described constructing system of setting up the support system software architecture comprises at least:
(41) set up the running environment of constructing system;
(42) set up also each business module of initialization, data module, access module, its core is the modular system storehouse in foundation and the initialization data module.
5. support system software architecture construction method as claimed in claim 4, it is characterized in that, described business module comprises one of parameter management module, schema management module, mode construction module and instance management module at least, and described data module comprises one of common parameter part, modular system storehouse and case library at least.
6. support system software architecture construction method as claimed in claim 4 is characterized in that, modular system storehouse in described foundation and the initialization data module comprises:
(61) public parameter value in the initialize mode system library comprises one of relation between MODE name, pattern, modular system topology institutional framework, pattern rank and architecture classification at least;
(62) initialize mode system basic parameter comprises one of relation between modular system title, formation pattern, pattern, modular system topology institutional framework and supplementary notes at least;
(63) the application architecture pattern that comprises at least in the initialize mode system, the functional architecture pattern that view architecture mode and business scenario architecture mode and view architecture mode comprise at least, the flow process architecture mode, the information architecture pattern, the interface architecture pattern, basic parameter in one of technical architecture pattern, to set up the described pattern in the modular system storehouse, comprise MODE name at least, the mode of constructive system structure, the problem set that the constructive system structure need solve, the solution collection of problem set correspondence, architecture component, the inter-module relation, the formation rule collection, the architecture classification, the architecture describing mode, the pattern rank, higher level's MODE name, one of replaceable MODE name.
7. support system software architecture construction method as claimed in claim 6, it is characterized in that, the application architecture pattern basic parameter of described initialize mode system library comprises the application architecture assembly at least, and described application architecture assembly comprises subsystem at least.
8. support system software architecture construction method as claimed in claim 7 is characterized in that described application architecture assembly also comprises level, classification and/or peripheral system.
9. as claim 7 or 8 described support system software architecture construction methods, it is characterized in that the application architecture pattern basic parameter of described initialize mode system library also comprises:
(91) mode of structure application architecture comprises from the application of engineering project of division, positioning subsystem making up software architecture;
(92) make up the problem set that application architecture need solve, comprise at least defining subsystem; Arrange out the hierarchical relationship of each subsystem; Subsystem is sorted out processing; With define one of interface with peripheral system;
(93) the solution collection of structure problem set correspondence comprises the tightness definition subsystem according to Function Coupling at least; Contact closely with network element device that subsystem comes lower floor, the subsystem that is closely related with client's access processing capacity comes the upper strata; According to supporting production or supporting the different disposal character of performance analysis that subsystem is sorted out; Clearly go out one of peripheral system;
(94) inter-module relation comprises that a subsystem can stride many levels; A subsystem only belongs to a kind usually; Do not belong to one of any support system classification with peripheral system;
(95) formation rule collection comprises further segmentation; Do not need further segmentation and one of following layer architecture of constructing this architecture;
(96) application architecture describing mode can be the hierarchical classification block diagram.
10. support system software architecture construction method as claimed in claim 6, it is characterized in that, the view architecture mode basic parameter of described initialize mode system library comprises the view architecture component at least, and described view architecture component comprises viewpoint at least.
11. support system software architecture construction method as claimed in claim 10 is characterized in that, described view architecture component also comprises role, concrete view architecture.
12., it is characterized in that the view architecture mode basic parameter of described initialize mode system library also comprises as claim 10 or 11 described support system software architecture construction methods:
(121) mode of structure view architecture module: comprise demand angle at least,, make up pairing groupware architecture under the different points of view for reaching purpose deep, detail knowledge system aspect characteristic from the role;
(122) make up the problem set that the view architecture module need solve, comprise at least and find out main viewpoint; Correspondence goes out the concrete view architecture under the different points of view;
(123) the solution collection of structure problem set correspondence comprises that at least some main aspect characteristic of system of paying close attention to according to needs in analysis, design, the development support system process defines viewpoint; The different correspondences of paying close attention to content and the personnel of concern classification according to each viewpoint go out the concrete view architecture under this viewpoint;
(124) formation rule collection further makes up each concrete view architecture module of lower floor according to the viewpoint dividing condition; According to the practical experience of analysis, design, development support system, related development personnel mainly pay close attention to the characteristic of one side of function at least, flow process, information, interface, the technical system of support system;
(125) the inter-module relation comprises that at least a role can be from one or more viewpoint observing systems; A role may relate to a plurality of concrete view architectures, but because the division of duty difference of different role, and the related concrete view architecture level of different role is also different generally speaking; The corresponding different concrete view architecture of different points of view, each viewpoint one of can only corresponding concrete view architectures;
(126) view architecture describing mode comprises viewpoint division figure at least.
13. support system software architecture construction method as claimed in claim 6, it is characterized in that, the functional architecture pattern basic parameter of described initialize mode system library comprises the functional architecture assembly at least, and described functional architecture assembly comprises functional module at least.
14. support system software architecture construction method as claimed in claim 13 is characterized in that described functional architecture assembly also comprises the relation between level and/or functional module.
15., it is characterized in that the functional architecture pattern basic parameter of described initialize mode system library also comprises as claim 13 or 14 described support system software architecture construction methods:
(151) mode of constructing function architecture module comprises at least from angle structure software architecture deep, detail knowledge systemic-function characteristic;
(152) the constructing function architecture module problem set that need solve comprises defining relatively independent functional module at least; The module that defines is carried out classification to be handled; And one of the incidence relation of functional module between definite level;
(153) the solution collection of structure problem set correspondence comprises according to function proximity and granularity similarity each function is sorted out, and to form relatively independent functional module, wherein, the function proximity principle of different stage may be different; According to the granularity similarity of each functional module, the functional module that granularity is close belongs to same one-level; And/or the incidence relation of each functional module between the analysis adjacent level, if higher level's functional module realizes by subordinate's functional module combination, determine that then there is incidence relation in functional module between adjacent level;
(154) formation rule collection comprises making up subordinate's functional architecture; Lowermost layer functional module to higher level's architecture is segmented, and defines the subordinate's function that realizes bottom functional module; Subordinate's function is sorted out; And/or define the incidence relation of subordinate's functional module;
(155) the inter-module relation comprises that each functional module can only be positioned at a level; And/or if higher level's functional module realizes that by subordinate's functional module combination then there is incidence relation in functional module between adjacent level;
(156) functional architecture describing mode can be functional organization figure, promptly by organization unit functional module is described, and by the classification of institutional framework and the relation of sorting out relation between functional module is described;
(157) higher level's pattern can be the view architecture.
16. support system software architecture construction method as claimed in claim 6, it is characterized in that, the flow process architecture mode basic parameter of described initialize mode system library comprises the flow process architecture component at least, and described flow process architecture component comprises between functional module/role at least and concerning.
17. support system software architecture construction method as claimed in claim 16 is characterized in that described flow process architecture component also comprises functional module/role.
18., it is characterized in that the flow process architecture mode basic parameter of described initialize mode system library also comprises as claim 16 or 17 described support system software architecture construction methods:
(181) mode of structure flow process architecture module is included as the process automation configuration purpose of realizing in the support system, from angle structure software architecture deep, detail knowledge system flow characteristic;
(182) make up the problem set that the flow process architecture module need solve, comprise the functional module or the role that relate in definite flow process; And/or define cooperation and restriction relation between each module/role;
(183) make up the solution collection of problem set correspondence, comprise in the function of reference architecture, according to granularity similarity principle or according to the actual requirements, determine the functional module or the role that relate in the overall flow about the functional module definition; And/or, locate each functional module/role's order according to the flow process sequential, define cooperation and temporal constraint relation between each module/role;
(184) formation rule collection comprises making up subordinate's flow process architecture; According to the demand of reality to the segmentation of functional module/role, about the classification and the definition of functional module, the functional module/role of higher level's architecture is segmented in the function of reference architecture, define the functional module/role of subordinate; And/or, reorientate the relation between each functional module of subordinate/role's order and each functional module/role according to the flow process sequential;
(185) the inter-module relation comprises the process according to realization certain or certain group function, determines that wherein each functional module/role gets in touch with the corresponding of various relations;
(186) flow process architecture describing mode can be sequential chart, has promptly described cooperation and restriction relation between correlation function module/role by the interactive relation of sequential chart;
(187) higher level's pattern is the view architecture.
19. support system software architecture construction method as claimed in claim 6, it is characterized in that, the information architecture pattern basic parameter of described initialize mode system library comprises the information architecture assembly at least, and described information architecture assembly comprises information field at least.
20. support system software architecture construction method as claimed in claim 19 is characterized in that described information architecture assembly also comprises information model.
21., it is characterized in that the information architecture pattern basic parameter of described initialize mode system library also comprises as claim 19 or 20 described support system software architecture construction methods:
(211) mode of structure information architecture module is included as relation between all kinds of static informations and information classification is carried out necessary constraint, from angle structure software architecture deep, detail knowledge system static information characteristic;
(212) make up the problem set that information architecture need solve, comprise marking off main information field; And/or define information model in each information field;
(213) making up the solution collection of problem set correspondence, comprise for information field at the same level, is foundation with the associating information degree, with association relatively closely information be classified as same class; And/or analyze in each information field and concern between each information, define the relevant information model;
(214) formation rule collection comprises according to the actual requirements, can further make up subordinate's information architecture; Each information field is subjected to the administration of certain function collection corresponding to certain function collection, so, but the classification of function of reference architecture is carried out classification to the corresponding information territory; And/or the segmentation of information field not necessarily produces new information, but if cause the situation of information subdivision, the new information model that produces of definition;
(215) the inter-module relation comprises that each information model generally only belongs to an information field; And/or be incidence relation information model relatively closely in the same information field;
(216) information architecture describing mode can be information model and/or information field division figure, has promptly described incidence relation between information by information model, has described the classification situation of information by information field division figure);
(217) higher level's pattern can be the view architecture.
22. support system software architecture construction method as claimed in claim 6, it is characterized in that, the interface architecture pattern basic parameter of described initialize mode system library comprises the interface architecture assembly at least, and described interface architecture assembly comprises the interface service unit at least.
23. support system software architecture construction method as claimed in claim 19 is characterized in that described interface architecture assembly also comprises the interface service unit.
24., it is characterized in that the interface architecture pattern basic parameter of described initialize mode system library also comprises interface object and/or interface mode as claim 19 or 20 described support system software architecture construction methods:
(241) make up the mode of interface architecture module, comprise at least from deeply, the angle structure software architecture of interaction characteristic between the detail knowledge system;
(242) make up the problem set that interface architecture need solve, comprise and distinguish interactive system; Define to the required interface service unit that provides of each system is provided alternately; And/or the interactive mode between the agreement object;
(243) make up the solution collection of problem set correspondence, comprise that according to the observation interface range determines the interactive system that relates to; The information content defining interface service unit that transmits or obtain to the other side according to needs in mutual purpose and the reciprocal process; And/or according to the processing power of interactive system, system performance agreement both sides' interactive mode;
(244) formation rule collection comprises according to the actual requirements, can further make up subordinate's interface architecture; Carry out classification according to the functional class docking port architecture that the classification and the interface service unit of interface service unit are realized; High-level interface architecture can be segmented to make up subordinate's interface architecture by the classification of docking port service unit, and external interface further is subdivided into management and production interface and operation information service interface; But low level interface architecture function of reference architecture is segmented to make up subordinate's interface architecture by the function that the docking port service unit is realized; And/or, determine boundary high-level, the low level interface architecture according to actual conditions;
(245) inter-module relation comprises that an interface object can provide a plurality of interface service unit, and mutual interface object is when realizing same mutual purpose, and both sides provide the interface service unit of identical type; When the interface object that interface object is different with all the other is mutual, can adopt different interactive modes; And/or an interface service unit generally only takes a kind of interactive mode, realizes same mutual purpose and when taking the distinct interaction mode, is commonly defined as different interface service unit;
(246) the interface architecture describing mode can be message sequence chart, promptly in the message sequence chart entity description interface object, the inter-entity sequence has been represented interface service unit concrete between system, information has been represented interface message in the sequence;
(247) higher level's pattern can be the view architecture.
25. support system software architecture construction method as claimed in claim 6, it is characterized in that, the technical architecture pattern basic parameter of described initialize mode system library comprises the technical architecture assembly at least, and described technical architecture assembly comprises technical parts at least.
26. support system software architecture construction method as claimed in claim 25 is characterized in that, described technical architecture assembly also comprises the technical parts location.
27., it is characterized in that the interface architecture pattern basic parameter of described initialize mode system library also comprises as claim 25 or 26 described support system software architecture construction methods:
(271) mode of constructing technology architecture module comprises at least from deep, detail knowledge back-up system and implementing and turn round employed technical parts and the orientation angle structure software architecture of parts system;
(272) the constructing technology architecture problem set that need solve comprises that distinguishing back-up system implements and the employed technical parts that turns round; And/or each parts positioned;
(273) the solution collection of structure problem set correspondence comprises the character according to all kinds of technology building blocks of system, and related tightness degree each other, and all kinds of building blocks of system are sorted out; And/or every base part is positioned according to degree of support, degree of dependence and the classification situation of each base part to all the other base parts;
(274) formation rule collection comprises according to the actual requirements, can further make up subordinate's technical architecture; Because each positioning parts is by level and classification decision, so the segmentation of and classification middle-level according to higher level's technical system can be carried out subordinate's classification to technical system; According to dependence between each technical parts and supporting relation, can carry out the level Subdividing Processing to higher level's technical system, by being segmented the dependence of remainder layer, each layer make up subordinate's technical architecture; And/or according to the similarity of function, can sort out the parts of higher level's technical system and carry out Subdividing Processing, make up subordinate's technical architecture by each classification being carried out the branch subdivision;
(275) the inter-module relation comprises that level and classification that a technical parts is in are certain, so a technical parts can only have a location, and each classification comprises each level parts;
(276) technical architecture describing mode can be the hierarchical classification structural drawing;
(277) higher level's pattern can be the view architecture.
28. support system software architecture construction method as claimed in claim 6, it is characterized in that, the business scenario architecture mode basic parameter of described initialize mode system library comprises the business scenario architecture component at least, and described business scenario architecture component comprises the role at least.
29. support system software architecture construction method as claimed in claim 28 is characterized in that described business scenario architecture component also comprises function and/or flow process.
30., it is characterized in that the business scenario architecture mode basic parameter of described initialize mode system library also comprises as claim 28 or 29 described support system software architecture construction methods:
(301) mode of structure business scenario architecture comprises that at least the dynamic cooperative operative mechanism angle of entire system from analyze professional use makes up software architecture;
(302) make up the problem set that the business scenario architecture need solve, comprise defining the assembly that participates in the scene running; And/or analyze the relation of each inter-module;
(303) the solution collection of problem set correspondence comprises user to system, for satisfying the required function of finishing of user and use is analyzed, thereby obtains the assembly that participates in the scene running; And/or to each assembly in scene mutual cooperation and mutually constraint analyze, thereby obtain each inter-module relation;
(304) inter-module relation comprises that the function that the role passes through using system realizes professional use, and the function privilege that different role can be used is different; The role finishes mutual with system by flow process; The flow process collection difference that different role can relate to; Correlation function is finished the use of whole service by the common cooperation of corresponding flow process; And/or same function related flow process difference in the different business use;
(305) formation rule collection is according to role's further segmentation and the following layer architecture of constructing this architecture of subdivision rules; And/or according to the following layer architecture of the further segmentation of the subdivision rules of functional architecture, flow process architecture with this architecture of structure;
(306) business scenario architecture describing mode can be role-function-flow process three-dimensional plot.
31. support system software architecture construction method as claimed in claim 4 is characterized in that, also comprise at least constructing system the modular system storehouse safeguard step, comprise at least increasing, optimizing and one of delete.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200410009412 CN1604099B (en) | 2004-08-06 | 2004-08-06 | Method and system for constructing software system structure of telecommunication operation support system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200410009412 CN1604099B (en) | 2004-08-06 | 2004-08-06 | Method and system for constructing software system structure of telecommunication operation support system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1604099A CN1604099A (en) | 2005-04-06 |
| CN1604099B true CN1604099B (en) | 2011-04-20 |
Family
ID=34662472
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200410009412 Active CN1604099B (en) | 2004-08-06 | 2004-08-06 | Method and system for constructing software system structure of telecommunication operation support system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1604099B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104657130A (en) * | 2015-01-14 | 2015-05-27 | ***通信集团广东有限公司 | Method for hierarchically layering business support system |
| CN104683160A (en) * | 2015-03-17 | 2015-06-03 | 浪潮通信信息***有限公司 | Scene APP palm operation and maintenance method based on mobile daily operation and maintenance process |
| CN105487908B (en) * | 2015-12-22 | 2020-05-19 | 中软信息***工程有限公司 | Safe application software ecological service method |
| CN109408031A (en) * | 2018-10-19 | 2019-03-01 | 成都信息工程大学 | A kind of Requirements Modeling process personnel evolution system and method, processor, terminal |
-
2004
- 2004-08-06 CN CN 200410009412 patent/CN1604099B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN1604099A (en) | 2005-04-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106126521B (en) | The social account method for digging and server of target object | |
| US20240037266A1 (en) | Activity-based content object access permissions | |
| CN110413707A (en) | The excavation of clique's relationship is cheated in internet and checks method and its system | |
| Akintola et al. | New BIM roles’ legitimacy and changing power dynamics on BIM-enabled projects | |
| Hislop et al. | Innovation and networks: Linking diffusion and implementation | |
| CN101013488A (en) | Method for implementing knowledge exhibition of knowledge management software | |
| CN109189844A (en) | A kind of inspection examining report business management system | |
| Qiang et al. | Dynamics of collaborative networks for green building projects: Case study of Shanghai | |
| CN110489749A (en) | Intelligent Office-Automation System Work Flow Optimizing | |
| CN1604099B (en) | Method and system for constructing software system structure of telecommunication operation support system | |
| Burghardt et al. | Relation modelling within multiple representation databases and generalisation services | |
| CN110033195A (en) | Adjust grid model splicing method to a kind of province based on CIM/CIS | |
| CN113821500A (en) | Business object construction method based on government affair service scene | |
| CN104166581B (en) | A kind of virtual method towards increment manufacturing equipment | |
| CN116415199B (en) | Business data outlier analysis method based on audit intermediate table | |
| Kokshenev et al. | A web-based decision support center for electrical energy companies | |
| Ostergaard et al. | Resistance based modeling of collaborative design | |
| CN103297538B (en) | The polymerization of models for resources and environment | |
| Petkov et al. | The analytic hierarchy process and systems thinking | |
| AT&T | JonReadesThesis.pdf | |
| Petzold et al. | Workflow management and generalisation services | |
| Bobek et al. | Intelligent agent based business intelligence | |
| Utomo et al. | Automated negotiation for non-producing management decision | |
| Furley | The BT operational support systems architecture | |
| You et al. | An integrated urban systems model with GIS |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Assignee: China Telecom Co., Ltd. Assignor: China United Communication Co., Ltd. Contract fulfillment period: 2008.7.27 to 2028.5.21 contract change Contract record no.: 2008990000845 Denomination of invention: Method and system for constructing software system structure of telecommunication operation support system License type: General permission Record date: 20081020 |
|
| LIC | Patent licence contract for exploitation submitted for record |
Free format text: COMMON LICENSE; TIME LIMIT OF IMPLEMENTING CONTACT: 2008.7.27 TO 2028.5.21; CHANGE OF CONTRACT Name of requester: CHINA TELECOMMUNICATIONS GROUP CO.,LTD. Effective date: 20081020 |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |