CN109634562A - Demand management method and requirement management systems - Google Patents
Demand management method and requirement management systems Download PDFInfo
- Publication number
- CN109634562A CN109634562A CN201910094225.0A CN201910094225A CN109634562A CN 109634562 A CN109634562 A CN 109634562A CN 201910094225 A CN201910094225 A CN 201910094225A CN 109634562 A CN109634562 A CN 109634562A
- Authority
- CN
- China
- Prior art keywords
- demand
- requirement
- event
- life cycle
- managed object
- 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.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
Abstract
The invention discloses a kind of demand management method and requirement management systems.Demand management method includes: to obtain the rules of life cycle of managed object；The requirement templet of managed object is established according to rules of life cycle.The demand management method and requirement management systems of embodiment of the present invention, according to the rules of life cycle of managed object, the requirement templet of managed object is established, requirement profile, the templating, digitlization of managed object can be made, is conducive to the efficiency for improving demand management.
Description
Technical field
The present invention relates to field of computer technology more particularly to a kind of demand management methods and requirement management systems.
Background technique
In the related art, computer system is generally built by following five steps: client proposes crucial requirement；
Demand analysis personnel deeply carry out requirement investigation；Set up IT project team；System design, exploitation and test；Online implementing, fortune
Dimension.However, encounter new client or new project every time, require to repeat above step, though client be same industry or
Business similarity is high, even being applied to the different clients of same scene.In this way, causing in computer system construction very
More problems, these problems become the significant obstacle that the traditional forms of enterprises makes the transition to Digital Enterprise, bring to enterprise in every aspect
Different degrees of negative effect.For example, Business Data Standard and format disunity, business are isolated；Support service response slow,
Business can not be carried out effectively to precipitate.
Summary of the invention
The present invention provides a kind of demand management method and requirement management systems.
The demand management method of embodiment of the present invention includes:
Obtain the rules of life cycle of managed object；
The requirement templet of the managed object is established according to the rules of life cycle.
The demand management method of embodiment of the present invention, according to the rules of life cycle of managed object, foundation is managed
The requirement templet of object can make requirement profile, the templating, digitlization of managed object, be conducive to raising demand pipe
The efficiency of reason.
In some embodiments, before the rules of life cycle for obtaining managed object, the demand management side
Method includes:
The managed object is registered in requirement management systems.
In some embodiments, the requirement templet of the managed object is established according to the rules of life cycle, is wrapped
It includes:
The managed object is abstracted in the object event of each life stage according to the rules of life cycle；
Determine the managed object in the demand and number of each life stage according to the object event of abstract
Demand described in word；
The requirement templet is established according to the digitized demand.
In some embodiments, the object event includes the event and the quilt that the managed object passively occurs
Manage at least one of the event that object actively occurs.
In some embodiments, the managed object is abstracted in each life stage according to the rules of life cycle
Object event, comprising:
The object event is determined according to the rules of life cycle；
Abstract operation is carried out to the object event.
In some embodiments, the demand includes main demand, according to the determination of the object event of abstract
Managed object each life stage demand and digitize the demand, comprising:
The main demand is determined according to the object event of abstract and digitizes the main demand.
In some embodiments, the feature of the main demand include object identity mark, object type, Obj State,
Event category, event code, event title, event sequence, preposition event, planned start time, planned end time, Life Cycle
One or more of age phase, pre-set time and abnormal alarm time.
In some embodiments, the demand includes the extension demand of the main demand, according to the described right of abstract
As event determines the managed object in the demand of each life stage and digitizes the demand, comprising:
The extension demand is determined according to the object event of abstract and digitizes the extension demand.
In some embodiments, the feature of the extension demand includes object identity mark, main demand mark, operation
One or more of people, place and required resource, the required resource include article, fund, system, collaboration people and collaboration pair
One or more of as.
In some embodiments, the demand management method includes:
The example that the managed object is instantiated to obtain the managed object；
The example demand of the example of the managed object is determined according to the requirement templet；
Store the example demand.
In some embodiments, the example demand is stored, comprising:
By example demand storage to demand database.
In some embodiments, the demand management method includes:
Track and manage the example demand.
The requirement management systems of embodiment of the present invention, including object management module and requirement templet management module, it is described
Object management module includes Object Life Cycle component, and the Object Life Cycle component is used to obtain the life of managed object
Periodic law, the requirement templet management module are used to establish the demand of the managed object according to the rules of life cycle
Template.
The requirement management systems of embodiment of the present invention, according to the rules of life cycle of managed object, foundation is managed
The requirement templet of object can make requirement profile, the templating, digitlization of managed object, be conducive to raising demand pipe
The efficiency of reason.
In some embodiments, the object management module includes object registration component, and the object registration component is used
In in the requirement management systems registration managed object.
In some embodiments, the object management module includes object event definitions component, and the object event is fixed
Adopted component is used to abstract the managed object in the object event of each life stage according to the rules of life cycle；It is described
Requirement templet management module is used to determine the managed object in each life rank according to the object event of abstract
The demand of section simultaneously digitizes the demand；And for establishing the requirement templet according to the digitized demand.
In some embodiments, the object event definitions component is used to determine the object according to the life cycle
Event；And for carrying out abstract operation to the object event.
In some embodiments, the demand includes main demand, and the requirement templet management module is used for according to abstract
The object event changed determines the main demand and digitizes the main demand.
In some embodiments, the demand includes the extension demand of the main demand, and the requirement templet manages mould
Block is for determining the extension demand according to the object event of abstract and digitizing the extension demand.
In some embodiments, the requirement management systems include demand pond module, and demand pond module is for real
Example of the exampleization managed object to obtain the managed object；And for determining the quilt according to the requirement templet
Manage the example demand of the example of object；And for storing the example demand.
In some embodiments, demand pond module is used for example demand storage to demand database.
In some embodiments, the requirement management systems include requirement tracking management module, the requirement tracking pipe
Reason module is for tracking and managing the example demand.
The requirement management systems of embodiment of the present invention, including processor and memory, the memory are stored with one
Or multiple programs, described program realize the demand management method of any of the above-described embodiment when being executed by the processor.
Additional aspect and advantage of the invention will be set forth in part in the description, and will partially become from the following description
Obviously, or practice through the invention is recognized.
Detailed description of the invention
Above-mentioned and/or additional aspect and advantage of the invention is from combining in description of the following accompanying drawings to embodiment by change
It obtains obviously and is readily appreciated that, in which:
Fig. 1 is the flow diagram of the demand management method of embodiment of the present invention；
Fig. 2 is the module diagram of the requirement management systems of embodiment of the present invention；
Fig. 3 is the capture demand schematic diagram of the life cycle based on people of embodiment of the present invention；
Fig. 4 is the capture demand schematic diagram of the life cycle based on animal of embodiment of the present invention；
Fig. 5 is the capture demand schematic diagram of the life cycle based on plant of embodiment of the present invention；
Fig. 6 is the capture demand schematic diagram of the life cycle space-based of embodiment of the present invention；
Fig. 7 is the capture demand schematic diagram of the life cycle based on affairs of embodiment of the present invention；
Fig. 8 is the capture demand schematic diagram of the life cycle based on object of embodiment of the present invention；
Fig. 9 is the capture demand schematic diagram of the life cycle based on wealth of embodiment of the present invention；
Figure 10 is the capture demand schematic diagram of the life cycle based on system of embodiment of the present invention；
Figure 11 is the flow diagram of the demand management method of another embodiment of the present invention；
Figure 12 is the module diagram of the requirement management systems of another embodiment of the present invention；
Figure 13 is the flow diagram of the demand management method of a further embodiment of this invention；
Figure 14 is the module diagram of the requirement management systems of a further embodiment of this invention；
Figure 15 is the flow diagram of the demand management method of a further embodiment of the present invention；
Figure 16 is the flow diagram of the demand management method of another embodiment of the present invention；
Figure 17 is the flow diagram of the demand management method of a further embodiment of this invention；
Figure 18 is the flow diagram of the demand management method of a further embodiment of the present invention；
Figure 19 is the module diagram of the requirement management systems of a further embodiment of the present invention；
Figure 20 is the flow diagram of the demand management method of another embodiment of the present invention；
Figure 21 is the flow diagram of the demand management method of a further embodiment of this invention；
Figure 22 is the module diagram of the requirement management systems of another embodiment of the present invention；
Figure 23 is the structural schematic diagram of the requirement management systems of embodiment of the present invention.
Main element symbol description:
Requirement management systems 100, object management module 10, object registration component 11, Object Life Cycle component 12, object
Event definitions component 13, requirement templet management module 20, demand pond module 30, demand database 32, requirement tracking management module
40, processor 50 and memory 60.
Specific embodiment
Embodiments of the present invention are described below in detail, the example of the embodiment is shown in the accompanying drawings, wherein from beginning
Same or similar element or element with the same or similar functions are indicated to same or similar label eventually.Below by ginseng
The embodiment for examining attached drawing description is exemplary, and for explaining only the invention, and is not considered as limiting the invention.
In the description of the present invention, term " first ", " second " are used for description purposes only, and should not be understood as instruction or dark
Show relative importance or implicitly indicates the quantity of indicated technical characteristic.The feature of " first ", " second " is defined as a result,
It can explicitly or implicitly include one or more feature.In the description of the present invention, the meaning of " plurality " is
Two or more, unless otherwise specifically defined.
In the description of the present invention, it should be noted that unless otherwise clearly defined and limited, term " installation ", " phase
Even ", " connection " shall be understood in a broad sense, for example, it may be being fixedly connected, may be a detachable connection, or be integrally connected；It can
To be mechanical connection, it is also possible to be electrically connected or can mutually communicate；It can be directly connected, it can also be by between intermediary
It connects connected, can be the connection inside two elements or the interaction relationship of two elements.For the ordinary skill of this field
For personnel, the specific meanings of the above terms in the present invention can be understood according to specific conditions.
In the present invention unless specifically defined or limited otherwise, fisrt feature second feature "upper" or "lower"
It may include that the first and second features directly contact, also may include that the first and second features are not direct contacts but pass through it
Between other characterisation contact.Moreover, fisrt feature includes the first spy above the second feature " above ", " above " and " above "
Sign is right above second feature and oblique upper, or is merely representative of first feature horizontal height higher than second feature.Fisrt feature exists
Second feature " under ", " lower section " and " following " include that fisrt feature is directly below and diagonally below the second feature, or is merely representative of
First feature horizontal height is less than second feature.
Following disclosure provides many different embodiments or example is used to realize different structure of the invention.In order to
Simplify disclosure of the invention, hereinafter the component of specific examples and setting are described.Certainly, they are merely examples, and
And it is not intended to limit the present invention.In addition, the present invention can in different examples repeat reference numerals and/or reference letter,
This repetition is for purposes of simplicity and clarity, itself not indicate between discussed various embodiments and/or setting
Relationship.
The present invention provides a kind of demand management method and requirement management systems 100.
Referring to Fig. 1, the demand management method of embodiment of the present invention includes:
Step S12: the rules of life cycle of managed object is obtained；
Step S13: the requirement templet of managed object is established according to rules of life cycle.
Referring to Fig. 2, the requirement management systems 100 of embodiment of the present invention, including object management module 10
(ObejctManagement) it is wrapped with requirement templet management module 20 (RequirementTemplate), object management module 10
It includes Object Life Cycle component 12 (ObjectLifeCircle), Object Life Cycle component 12 is for obtaining managed object
Rules of life cycle, requirement templet management module 20 are used to establish the requirement templet of managed object according to rules of life cycle.
The demand management method and requirement management systems 100 of embodiment of the present invention, according to the Life Cycle of managed object
Phase rule, establishes the requirement templet of managed object, can make requirement profile, the templating, digitlization of managed object,
Be conducive to improve the efficiency of demand management.
Specifically, managed object includes but is not limited to people, animal, plant, space, affairs, object, wealth, system etc..By pipe
The rules of life cycle of reason object refers to that managed object necessarily follows within the period since life to end of life
Rule.
Referring to Fig. 3, in one example, managed object is people, people necessarily undergo birth, infancy, infancy, on
The stages such as term, work phase, endowment phase, last life termination.In each stage, it is anticipated that people has corresponding demand.Example
Such as, the demand of people at birth includes but is not limited to Birth Registration and vaccinates, and includes but is not limited in the demand of infancy
It lactation and vaccinates, includes but is not limited to children education and upper kindergarten etc. in the demand in infancy, include in the demand of last term
But it is not limited to the demand of going to school such as at primary school and in the middle school, includes but is not limited to choose a job and go to work in the demand of work phase, supports parents
The demand of phase includes but is not limited to select endowment place and retirement etc..These demands can be to need by step S13 abstract expression
It seeks template.It is listed to note that the division in stage is not limited only in Fig. 3, iteration can be supplemented, form the Life Cycle of complete people
Phase.
Referring to Fig. 4, in another example, managed object is animal, animal necessarily undergoes birth, mother to accompany
Phase is detached from the stages such as mother's growth stage, the phase of growing up to and breeding period, last life termination.In each stage, it is anticipated that animal is
There is corresponding demand.For example, the demand of animal at birth includes but is not limited to Birth Registration and vaccinates, accompanied in mother
The demand of phase includes but is not limited to lactation (for mammal) and wean (for mammal) etc., is being detached from mother's growth stage
Demand include but is not limited to child care and be bred as etc., include but is not limited to choose seeds and turn group etc. in the demand for growing up to the phase, breeding
The demand of phase includes but is not limited to heat, breeding, farrowing (or laying eggs) etc..These demands can pass through step S13 abstract expression
For requirement templet.It is listed to note that the division in stage is not limited only in Fig. 4, iteration can be supplemented, form the life of complete animal
Order the period.
Referring to Fig. 5, managed object is plant in another example, plant necessarily undergoes sowing, germination period, children
Seedling stage terminates with the stages such as phase, last life is grown up to.In each stage, it is anticipated that plant has corresponding demand.For example, planting
The demand of object at seeding time includes but is not limited to apply fertilizer and clean etc., includes but is not limited to pouring and nursing in the demand of germination period
Deng including but is not limited to illumination and provisions etc. in the demand of Seedling Stage, include but is not limited to pollinate and transfer in the demand for growing up to the phase
It connects.These demands can be requirement templet by step S13 abstract expression.It note that the division in stage is not limited only in Fig. 5
It is listed, iteration can be supplemented, the life cycle of complete plant is formed.
Referring to Fig. 6, managed object is space in further example, space necessarily undergoes birth and discovery, transformation
Phase, the finishing stages such as phase and validity period, last life termination.In each stage, it is anticipated that the mankind are to have corresponding need to space
It asks.For example, space includes but is not limited to exploration and exploration registration etc. being born with demand when discovery, in the demand of transformation phase
Including but not limited to planning and designing and construction etc. include but is not limited to Decoration Design and finishing etc. in the demand of finishing phase, make
It include but is not limited to enabling and personage etc. with the demand of phase.These demands can be requirement templet by step S13 abstract expression.
It is listed to note that the division in stage is not limited only in Fig. 6, iteration can be supplemented, form the life cycle in complete space.
Referring to Fig. 7, in another example, managed object is affairs, affairs necessarily undergo generation, plan, execution,
The stages such as tracking and improvement, last life termination.In each stage, it is anticipated that the mankind have corresponding demand to affairs.Example
Such as, demand of the affairs when generating includes but is not limited to idea and brainstorming etc., and the demand in plan includes but is not limited to
It decomposes and layout etc., demand when being executed includes but is not limited to do and put into resource etc., and the demand when tracking includes but not
It is limited to check and finds the problem, the demand when improving includes but is not limited to problem analysis and finds solution etc..These
Demand can be requirement templet by step S13 abstract expression.It is listed to note that the division in stage is not limited only in Fig. 7, it can be with
Iteration is supplemented, the life cycle of complete affairs is formed.
Referring to Fig. 8, managed object is object in another example, object necessarily undergoes generation, storage phase, logistics phase
It terminates with stages, last life such as stage of exhaustion.In each stage, it is anticipated that the mankind have corresponding demand to object.For example, object
Demand when generating includes but is not limited into member record and label etc., includes but is not limited to be put in storage and go out in the demand of storage phase
Library etc. includes but is not limited to be packaged and entrucking etc. in the demand of logistics phase, the demand of stage of exhaustion include but is not limited to receive and
Maintenance etc..These demands can be requirement templet by step S13 abstract expression.It note that the division in stage is not limited only to Fig. 8
In it is listed, iteration can be supplemented, form the life cycle of complete object.
Referring to Fig. 9, in further example, managed object is wealth, and wealth necessarily undergoes generation, acquisition phase, using turning
The stages such as change phase and stage of exhaustion, last life termination.In each stage, it is anticipated that the mankind have corresponding demand to wealth.Example
Such as, demand of the wealth when generating includes but is not limited to issue and valuation etc., the demand of the phase of acquisition include but is not limited to take in and
Present etc. is received, includes but is not limited to save and investment etc. in the demand using transition phase, includes in the demand of stage of exhaustion but not
It is limited to pay and present etc..These demands can be requirement templet by step S13 abstract expression.It note that the division in stage
Listed by being not limited only in Fig. 9, iteration can be supplemented, the life cycle of complete wealth is formed.
Referring to Fig. 10, in another example, managed object is system, system includes software systems and hardware system
System.System necessarily undergoes the stages such as project verification phase, demand analysis phase, design period, implementation phase and O&M phase, last life termination.?
Each stage, it is anticipated that system has corresponding demand.For example, demand of the system in the project verification phase includes but is not limited to Shen of setting up the project
It include but is not limited to requirement investigation, interview record and demand analysis etc. in the demand of demand analysis phase please with project verification examination & approval etc.,
The demand of design period includes but is not limited to Outline Design, detailed design and design review etc., includes in the demand of the phase of implementation but not
Be limited to exploitation, test and be packaged etc., it include but is not limited to run monitoring and troubleshooting etc. in the demand of O&M phase.These demands
It can be requirement templet by step S13 abstract expression.It is listed to note that the division in stage is not limited only in Figure 10, can mend
Iteration is filled, the life cycle of complete system is formed.
In step s 12, the rules of life cycle of managed object can be in managed object typing requirement management systems
While 100, it is stored in requirement management systems 100, it can also be in the requirement templet for needing to establish managed object, from cloud
End obtains the rules of life cycle of managed object.Concrete mode not to the rules of life cycle for obtaining managed object herein
It is defined.
In addition, requirement templet management module 20 includes the function such as requirement definition, requirement templet generation, demand acquisition condition editor
Can, it can be by demand very high level conceptual.
Figure 11 is please referred to, in some embodiments, before step S12, demand management method includes:
Step S11: managed object is registered in requirement management systems 100.
Figure 12 is please referred to, in some embodiments, object management module 10 includes object registration component 11
(ObjectRegister), object registration component 11 is used to register managed object in requirement management systems 100.
Managed object is registered in requirement management systems 100 in this way, realizing.It is appreciated that due to demand management system
It is usually the managed object for being not intended to management in system 100 before being managed to managed object.Therefore, it is obtaining
It takes the rules of life cycle of managed object and is established before the requirement templet of managed object accordingly, needed in demand management system
100 registration managed object of system, then could carry out the foundation and management of requirement templet to managed object.Certainly, other
In embodiment, registered before can also change the data of picture, new demand is established to picture to after change
Template.
Specifically, when requirement management systems 100 register managed object, the life cycle of managed object can be advised
Restrain typing requirement management systems 100 together.
Figure 13 is please referred to, in some embodiments, step S13 includes:
Step S131: managed object is abstracted in the object event of each life stage according to rules of life cycle；
Step S132: demand and digitlization of the managed object in each life stage are determined according to the object event of abstract
Demand；
Step S133: requirement templet is established according to digitized demand.
Figure 14 is please referred to, in some embodiments, object management module 10 includes object event definitions component 13
(ObjectEventDefinition), object event definitions component 13 is used to be managed pair according to rules of life cycle abstract
As the object event in each life stage；Requirement templet management module 20 is used for: being determined according to the object event of abstract by pipe
Object is managed in the demand of each life stage and digitizes demand, and for establishing requirement templet according to digitized demand.
In this way, realizing the requirement templet for establishing managed object according to rules of life cycle.Specifically, object event can be with
Refer to that object has to the event occurred based on its rules of life cycle in the different phase of life cycle or required does to it
Event.In other words, object event includes the event that managed object passively occurs and the event that managed object actively occurs
At least one of.
Referring to Fig. 3, when managed object is people, object event include people birth, infancy, infancy, on
The stages such as term, work phase, endowment phase have to the event or the required event done to it occurred, such as carry out birth and step on
Remember, vaccinate, people can be captured in the demand of each life stage according to object event by lactation and upper kindergarten etc..
Referring to Fig. 4, when managed object is animal, object event includes that animal is being born, mother's company phase, is taking off
The event or the required event done to it occurred is had to from stages such as mother's growth stage, the phase of growing up to and breeding periods, such as is gone out
Life is registered, is vaccinated, can capture animal in the demand of each life stage according to object event by lactation and wean etc..
Referring to Fig. 5, when managed object is plant, object event includes plant in sowing, germination period, Seedling Stage
Event or the required event done to it for occurring, such as fertilising, removal of impurities, pouring, nursing etc. are had to the stages such as phase are grown up to.
According to object event, plant can be captured in the demand of each life stage.
Referring to Fig. 6, when managed object is space, object event include space be born with discovery, the transformation phase,
The stages such as finishing phase and validity period have to the event or the required event done to it occurred, such as explore, exploration registration, rule
Delineate meter and build etc..According to object event, space can be captured in the demand of each life stage.
Referring to Fig. 7, when managed object is affairs, object event include affairs generation, plan, execution, with
The stages such as track and improvement have to the event occurred or the required event done to it, such as idea, brainstorming, decomposition etc..
According to object event, affairs can be captured in the demand of each life stage.
Referring to Fig. 8, when managed object is object, object event includes object in generation, storage phase, logistics phase and disappears
The stages such as consumption phase have to the event or the required event done to it occurred, such as at member record, label, storage and outbound
Deng.According to object event, can catches each life stage demand.
Referring to Fig. 9, when managed object is wealth, object event include wealth in generation, the acquisition phase, utilize transition phase
The event or the required event done to it that occur, such as distribution, valuation, income and savings are had to stages such as stage of exhaustion
Deng.According to object event, wealth can be captured in the demand of each life stage.
Referring again to Figure 10, when managed object is system, object event include system the project verification phase, the demand analysis phase,
The stages such as design period, implementation phase and O&M phase have to the event or the required event done to it occurred, such as application of setting up the project,
Project verification examination & approval and requirement investigation etc..According to object event, can capture systems each life stage demand.
Figure 15 is please referred to, in some embodiments, step S131 includes:
Step S1311: object event is determined according to rules of life cycle；
Step S1312: abstract operation is carried out to object event.
In some embodiments, object event definitions component 13 is used to determine object event according to life cycle；And
For carrying out abstract operation to object event.
Managed object is abstracted in the object event of each life stage according to rules of life cycle in this way, realizing.Specifically
Ground can carry out longitudinal decomposition according to life stage to rules of life cycle, so that it is determined that each life rank in step S1311
The object event of section；The rules of life cycle of different managed objects can also be subjected to lateral comparison, so that it is determined that each
The object event of managed object.Do not determine that the concrete mode of object event is defined to according to rules of life cycle herein.
In step S1312, abstract operation can be carried out to object event by the way that the feature of object time is arranged.Example
Such as, object event (can be included into article, fund, system, collaboration people, association with time, place, personage, object, required resource
With object etc.), trigger condition, one or several in the features such as preposition event describe, and by these features with digitized
Template abstract expression comes out.
Further, the time can use the format digitised expression of " year-month-day "；Place can use " state-province-city-area "
Format abstract expression；The particular content of personage, object, required resource, trigger condition, preposition event can be classified,
And corresponding coding is set for one kind of each feature.For example, personage is corresponding to be encoded to 10, personage includes administrator and holds
Office staff, the corresponding coding of administrator is 11, and the corresponding coding of executor is 12；Object is animal, and object is corresponding to be encoded to 20,
Object includes pig and sheep, and the corresponding coding of pig is 21, and the corresponding coding of sheep is 22 ... and so on.Note that the above is only
Example does not represent the limitation of the concrete mode to abstract operation.
Figure 16 is please referred to, in some embodiments, demand includes main demand, and step S132 includes:
Step S1321: main demand is determined according to the object event of abstract and digitizes main demand.
In some embodiments, demand includes main demand, and requirement templet management module 20 is used for pair according to abstract
As event determines main demand and digitizes main demand.
In this way, realizing digitlization managed object in the demand of each life stage.Referring to Fig. 4, animal is being born
When demand include but is not limited to Birth Registration and to vaccinate, it includes but is not limited to that lactation (is directed to that the demand of phase is accompanied in mother
Mammal) and wean (be directed to mammal), it include but is not limited to child care and incubation in the demand for being detached from mother's growth stage,
The demand for growing up to the phase includes but is not limited to choose seeds and turn group, includes but is not limited to heat, breeding, farrowing in the demand of breeding period
(or laying eggs).The demand can be main demand, can also only have one or several for main demand in the demand.?
This, is not defined the quantitative relation of demand and main demand.
Similarly, main demand can be digitized by the way that the feature of main demand is arranged.In some embodiments, main demand
Feature include object identity mark, object type, Obj State, event category, event code, event title, event sequence,
One in preposition event, planned start time, planned end time, life cycle age, pre-set time and abnormal alarm time
Kind is several.
Referring to Fig. 4, in this example, for the main demand of farrowing, object type is animal, object identity
Identifying corresponding coding is 20.Obj State be it is normal, it is corresponding to be encoded to 01.Event category is late incident, corresponding class
It Bian Ma not be respectively 05.Event entitled breeding period, corresponding event code are 051.Event sequence is corresponding to be encoded to 5.Before
Setting event is to grow up to the phase, corresponding to be encoded to 042.Planned start time is 2018-01-01, planned end time 2018-
01-02.The life cycle age is age in days 114.Pre-set time is 2017-12-20 to 2017-12-31.The abnormal alarm time is
Before 2017-12-20.It note that the above is only examples, do not represent the limitation to the concrete mode for digitizing main demand.
Figure 17 is please referred to, in some embodiments, demand includes the extension demand of main demand, and step S132 includes:
Step S1322: determining extension demand according to the object event of abstract and digitizes extension demand.
In some embodiments, demand includes the extension demand of main demand, and requirement templet management module 20 is used for basis
The object event of abstract determines extension demand and digitizes extension demand.
In this way, realizing digitlization managed object in the demand of each life stage.Specifically, the extension demand of main demand can
To be the details of main demand, for example, main demand is farrowing, extension demand is parent production and filial generation physical examination.
Certainly, an object event may include multiple demands, and a portion is main demand, and another part is main demand
Extension demand.For example, main demand is farrowing, extension demand is heat and breeding.
The extension demand of main demand and main demand can be one-to-many relationship.Certainly, the extension of main demand and main demand
Demand is also possible to one-to-one relationship.
The quantitative relation of the concrete form to extension demand and main demand and extension demand is not defined herein.
Similarly, extension demand can be digitized by the way that the feature of extension demand is arranged.In some embodiments, expand
The feature of exhibition demand includes one or more of object identity mark, main demand mark, operator, place and required resource,
Required resource includes article, fund, system, collaboration one or more of people and collaboration objects.Digitize the tool of extension demand
Body process is similar with the detailed process of the main demand of above-mentioned digitlization, and to avoid redundancy, details are not described herein.
Figure 18 is please referred to, in some embodiments, demand management method includes:
Step S14: example of the instantiation managed object to obtain managed object；
Step S15: template determines the example demand of the example of managed object according to demand；
Step S16: storage example demand.
Figure 19 is please referred to, in some embodiments, requirement management systems 100 include demand pond module 30
(RequirementPool), the example that demand pond module 30 is used to instantiate managed object to obtain managed object；And it uses
The example demand of the example of managed object is determined in template according to demand；And for storing example demand.
In this way, realizing the storage of example demand.Specifically, the example of managed object is the specific case of managed object
Example.In other words, the example of managed object is being embodied for managed object.In one example, managed object is
Object, the example of managed object are to live in the pig of some breeding house.In another example, managed object is plant, quilt
The example for managing object is to be planted in the pakchoi in certain block vegetable plot.According to the requirement templet of animal, the breeding house can be determined
The example demand of pig, such as eat pannage.According to the requirement templet of plant, the example that can determine the pakchoi in the vegetable plot is needed
It asks, such as deinsectization.
Figure 20 is please referred to, in some embodiments, step S16 includes:
Step S161: by example demand storage to demand database 32.
In some embodiments, demand pond module 30 is used for example demand storage to demand database 32.
In this way, realizing the storage of example demand, when needing to call example demand, need to only be read from database, it can
To improve the efficiency of demand management.Specifically, demand pond module can be with support structure database or unstructured database.?
This is not defined the concrete form of demand database 32.
Figure 21 is please referred to, in some embodiments, demand management method includes:
Step S17: tracking and admin instance demand.
Figure 22 is please referred to, in some embodiments, requirement management systems 100 include requirement tracking and management module 40
(RequirementTracking), requirement tracking management module 40 is used for tracing management example demand.
In this way, realizing that the dynamic of example demand updates.Specifically, requirement tracking management module 40 can be based on being managed pair
As the line map of life cycle carries out requirement tracking management.In this way while improving the efficiency of tracing management, it can to adopt
The data of data and the history acquisition collected are easier to integrate.
It is possible to further track whether example demand can satisfy managed object, example demand can be tracked with true
It is fixed whether to need to be adjusted example demand preferably to meet managed object, or example demand can be tracked with determination
Whether there are also the example demands for managed object.Then example demand is managed and is adjusted according to the result of tracking.
Figure 23, the requirement management systems 100 of embodiment of the present invention, including processor 50 and memory 60 are please referred to, is deposited
Reservoir 60 is stored with one or more programs, and program realizes the demand management of any of the above-described embodiment when being executed by processor 50
Method.
The requirement management systems of embodiment of the present invention, according to the rules of life cycle of managed object, foundation is managed
The requirement templet of object can make requirement profile, the templating, digitlization of managed object, be conducive to raising demand pipe
The efficiency of reason.
In summary, demand management method and requirement management systems provided by the invention, can be with effective solution computer
System and internet industry are for many years inadequate to the assurance of demand, the problem of so as to cause application system repeated construction.Also evidence
This, which has found a kind of scheme, can constantly accumulate standardization, templating, digitized demand knowledge base to build, and have according to these
The knowledge base of value can rapidly build out corresponding IT application system.
In the description of this specification, reference term " embodiment ", " certain embodiments ", " schematically implementation
The description of mode ", " example ", " specific example " or " some examples " etc. means embodiment or example is combined to describe specific
Feature, structure, material or feature are contained at least one embodiment or example of the invention.In the present specification, right
The schematic representation of above-mentioned term is not necessarily referring to identical embodiment or example.Moreover, the specific features of description, knot
Structure, material or feature can be combined in any suitable manner in any one or more embodiments or example.Although
Through embodiments of the present invention have shown and described, it will be understood by those skilled in the art that: it is of the invention not departing from
A variety of change, modification, replacement and modification, the scope of the present invention can be carried out to these embodiments in the case where principle and objective
It is defined by the claims and their equivalents.
Claims (22)
1. a kind of demand management method, which is characterized in that the demand management method includes:
Obtain the rules of life cycle of managed object；
The requirement templet of the managed object is established according to the rules of life cycle.
2. demand management method as described in claim 1, which is characterized in that in the life cycle for obtaining managed object
Before rule, the demand management method includes:
The managed object is registered in requirement management systems.
3. demand management method as described in claim 1, which is characterized in that establish the quilt according to the rules of life cycle
Manage the requirement templet of object, comprising:
The managed object is abstracted in the object event of each life stage according to the rules of life cycle；
Demand and digitlization of the managed object in each life stage are determined according to the object event of abstract
The demand；
The requirement templet is established according to the digitized demand.
4. demand management method as claimed in claim 3, which is characterized in that the object event includes the managed object
At least one of the event that the event passively occurred and the managed object actively occur.
5. demand management method as claimed in claim 3, which is characterized in that according to rules of life cycle abstract
Object event of the managed object in each life stage, comprising:
The object event is determined according to the rules of life cycle；
Abstract operation is carried out to the object event.
6. demand management method as claimed in claim 3, which is characterized in that the demand includes main demand, according to abstract
The object event determine the managed object in the demand of each life stage and digitize the demand, comprising:
The main demand is determined according to the object event of abstract and digitizes the main demand.
7. demand management method as claimed in claim 6, which is characterized in that the feature of the main demand includes object identity mark
When knowledge, object type, Obj State, event category, event code, event title, event sequence, preposition event, plan start
Between, planned end time, life cycle age, one or more of pre-set time and abnormal alarm time.
8. demand management method as claimed in claim 6, which is characterized in that the demand includes that the extension of the main demand needs
It asks, the managed object is determined in the demand of each life stage according to the object event of abstract and digitizes institute
State demand, comprising:
The extension demand is determined according to the object event of abstract and digitizes the extension demand.
9. demand management method as claimed in claim 8, which is characterized in that the feature of the extension demand includes object identity
One or more of mark, main demand mark, operator, place and required resource, the required resource include article, money
Gold, system, collaboration one or more of people and collaboration objects.
10. demand management method as described in claim 1, which is characterized in that the demand management method includes:
The example that the managed object is instantiated to obtain the managed object；
The example demand of the example of the managed object is determined according to the requirement templet；
Store the example demand.
11. demand management method as claimed in claim 10, which is characterized in that store the example demand, comprising:
By example demand storage to demand database.
12. demand management method as claimed in claim 10, which is characterized in that the demand management method includes:
Track and manage the example demand.
13. a kind of requirement management systems, which is characterized in that described right including object management module and requirement templet management module
As management module includes Object Life Cycle component, the Object Life Cycle component is used to obtain the Life Cycle of managed object
Phase rule, the requirement templet management module are used to establish the demand mould of the managed object according to the rules of life cycle
Plate.
14. requirement management systems as claimed in claim 13, which is characterized in that the object management module includes object registration
Component, the object registration component are used to register the managed object in the requirement management systems.
15. requirement management systems as claimed in claim 14, which is characterized in that the object management module includes object event
Definitions component, the object event definitions component are used to abstract the managed object each according to the rules of life cycle
The object event of life stage；The requirement templet management module is used to determine the quilt according to the object event of abstract
Object is managed in the demand of each life stage and digitizes the demand；And for being built according to the digitized demand
Found the requirement templet.
16. requirement management systems as claimed in claim 15, which is characterized in that the object event definitions component is used for basis
The life cycle determines the object event；And for carrying out abstract operation to the object event.
17. requirement management systems as claimed in claim 15, which is characterized in that the demand includes main demand, the demand
Template management module is for determining the main demand according to the object event of abstract and digitizing the main demand.
18. requirement management systems as claimed in claim 17, which is characterized in that the demand includes the extension of the main demand
Demand, the requirement templet management module is for determining the extension demand according to the object event of abstract and digitizing
The extension demand.
19. requirement management systems as claimed in claim 13, which is characterized in that the requirement management systems include demand pond mould
Block, the example that demand pond module is used to instantiate the managed object to obtain the managed object；And it is used for root
The example demand of the example of the managed object is determined according to the requirement templet；And for storing the example demand.
20. requirement management systems as claimed in claim 19, which is characterized in that demand pond module is used for the example
Demand is stored to demand database.
21. requirement management systems as claimed in claim 19, which is characterized in that the requirement management systems include requirement tracking
Management module, the requirement tracking management module is for tracking and managing the example demand.
22. a kind of requirement management systems, which is characterized in that including processor and memory, the memory be stored with one or
Multiple programs, described program realize demand management side described in any one of claims 1 to 12 when being executed by the processor
Method.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910094225.0A CN109634562A (en) | 2019-01-30 | 2019-01-30 | Demand management method and requirement management systems |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910094225.0A CN109634562A (en) | 2019-01-30 | 2019-01-30 | Demand management method and requirement management systems |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109634562A true CN109634562A (en) | 2019-04-16 |
Family
ID=66064372
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910094225.0A Pending CN109634562A (en) | 2019-01-30 | 2019-01-30 | Demand management method and requirement management systems |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109634562A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090192852A1 (en) * | 2008-01-29 | 2009-07-30 | Intelliwave Technologies Inc. | Method of tracking the lifecycle of a product |
| CN105303324A (en) * | 2015-11-10 | 2016-02-03 | 中国建设银行股份有限公司 | Information system parameter management method and device |
| CN105590157A (en) * | 2014-12-25 | 2016-05-18 | 中国银联股份有限公司 | Data management based on data lifecycle management template |
| US20180052898A1 (en) * | 2016-08-22 | 2018-02-22 | Oracle International Corporation | System and method for dynamic, incremental recommendations within real-time visual simulation |
| CN107943457A (en) * | 2017-11-17 | 2018-04-20 | 中山大学 | A kind of workflow modeling method and system of service-oriented object |
| CN108089843A (en) * | 2018-01-18 | 2018-05-29 | 福建省农村信用社联合社 | A kind of intelligentized banking establishments grade requirement management systems |
-
2019
- 2019-01-30 CN CN201910094225.0A patent/CN109634562A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090192852A1 (en) * | 2008-01-29 | 2009-07-30 | Intelliwave Technologies Inc. | Method of tracking the lifecycle of a product |
| CN105590157A (en) * | 2014-12-25 | 2016-05-18 | 中国银联股份有限公司 | Data management based on data lifecycle management template |
| CN105303324A (en) * | 2015-11-10 | 2016-02-03 | 中国建设银行股份有限公司 | Information system parameter management method and device |
| US20180052898A1 (en) * | 2016-08-22 | 2018-02-22 | Oracle International Corporation | System and method for dynamic, incremental recommendations within real-time visual simulation |
| CN107943457A (en) * | 2017-11-17 | 2018-04-20 | 中山大学 | A kind of workflow modeling method and system of service-oriented object |
| CN108089843A (en) * | 2018-01-18 | 2018-05-29 | 福建省农村信用社联合社 | A kind of intelligentized banking establishments grade requirement management systems |
Non-Patent Citations (1)
| Title |
|---|
| 吴智涌: "4.2.2面向对象的需求分析步骤", 《软件工程与WINDOWS16BIT人类》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110033185A (en) | Task management method and task management system | |
| Amirova et al. | Complex development of a digital platform of the agricultural economy | |
| Richards et al. | Seed systems for African food security: linking molecular genetic analysis and cultivator knowledge in West Africa | |
| Notenbaert et al. | Classifying livestock production systems for targeting agricultural research and development in a rapidly changing world | |
| CN111461554A (en) | Intellectual property flow management visualization method, device, storage medium and equipment | |
| Medennikov et al. | Formation of the Digital Platform for Precision Farming with Mathematical Modeling. | |
| Novikov et al. | Conceptual approaches to information transformation (digitalization) of an agricultural enterprise. | |
| CN113469800B (en) | Agricultural credit system based on blockchain | |
| Nemchenko et al. | Digital transformation of agricultural production: regional aspect | |
| Medeiros | Grand research challenges in computer science in brazil | |
| Vargas-Canales et al. | Trends in science, technology, and innovation in the agri-food sector | |
| Budzko et al. | Mathematical modeling of evaluating the effectiveness of using RSD data in precision farming | |
| CN109634562A (en) | Demand management method and requirement management systems | |
| Seidel et al. | Estimating a dual value function as a meta-model of a detailed dynamic mathematical programming model | |
| Shamsuddoha et al. | Sustainability process innovations resulting in new value-added byproducts: principal lessons from second-order system-dynamics engineering (SOSDE) | |
| Lescourret et al. | Modelling an information system using the MERISE method for agricultural research: the example of a database for a study on performances in dairy cows | |
| KR20200057440A (en) | Shipment forecasting system based on swine growth condition platform, and method thereof | |
| Kirillova et al. | Priority directions for the development of the agrarian economy in the context of the digitalization of the agro-industrial complex | |
| Wang | Research on construction and management of intelligent agriculture cloud platform | |
| Getmantsev et al. | Competitive Advantages of the Innovative University Ecosystem as the Source of the Competitiveness of Small Innovative Enterprises | |
| AU2021100096A4 (en) | Ai-based crop recommendation system for smart farming towards agriculture 5.0 | |
| Setianto et al. | Modeling smallholder beef farming: a systems thinking’s step by step approach | |
| Rabhi et al. | Digital transformation metamodel in smart farming: Crop classification prediction based on recurrent neural network | |
| Kokenova et al. | DIGITAL TRANSFORMATION OF AGRICULTURE IN THE REPUBLIC OF KAZAKHSTAN | |
| Khalatur et al. | Methodological bases of innovation model formation of the agricultural sector of the national economy |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190416 |
|
| RJ01 | Rejection of invention patent application after publication |