CN108984415A - A kind of product use-case persistence maintenance system and management method - Google Patents
A kind of product use-case persistence maintenance system and management method Download PDFInfo
- Publication number
- CN108984415A CN108984415A CN201810834645.3A CN201810834645A CN108984415A CN 108984415 A CN108984415 A CN 108984415A CN 201810834645 A CN201810834645 A CN 201810834645A CN 108984415 A CN108984415 A CN 108984415A
- Authority
- CN
- China
- Prior art keywords
- file
- case
- user
- management
- change
- 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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The present invention provides a kind of product use-case persistence maintenance system and management method, including user management module, project management module, demand and use-case change management module and use-case version library module, and the interaction between each module passes through Rest authorization and certification；User management module, for being managed to user, the user includes product owner, test owner, program member, system manager；Project management module, for being managed to item related information, item related information includes the initial demand passed through after project name, relevant documentation of approving and initiate a project, the project cycle, project correlation participant, project appraisal and use-case；Demand and use-case change management module, for being managed to demand and use-case change；Use-case version library module, for storing use-case, document and change record.
Description
Technical field
The present invention relates to test case management technical fields, and in particular to a kind of product use-case persistence maintenance system and management
Method.
Background technique
In project development and product issuing process, demand change or product up-gradation maintenance etc. due to, exploitation and
It requires to update or increase a large amount of test case in upgrade package test, in the period that production life cycle lasts several years, if not having
The maintenance use case of the management tool specification of one system is easy confusion in maintenance and late problems retrospect or the management of product, has
When can not can clearly increase newly or the corresponding use-case of change request.It is badly in need of exploration project case management platform to improve and existing not advise
Model and demand and the incomplete situation of use-case.
Summary of the invention
In order to overcome the deficiencies in the prior art described above, the present invention provides a kind of product use-case persistence maintenance system and management
Method, to solve the above technical problems.
The technical scheme is that
A kind of product use-case persistence maintenance system, including user management module, project management module, demand and use-case change
Management module and use-case version library module, the interaction between each module pass through Rest authorization and certification；
User management module, for being managed to user, the user includes product owner, test owner, item
Mesh member, system manager；
Project management module, for being managed to item related information, item related information includes project name, project
The initial demand and use-case passed through after project verification relevant documentation, the project cycle, project correlation participant, project appraisal；
Demand and use-case change management module, for being managed to demand and use-case change；
Use-case version library module, for storing use-case, document and change record.
Use-case version library module is equipped with basic modular unit, software storage and secondary storage.
Further, user management module has permission to access and management system all items for system manager to be arranged
And all functional modules, it is responsible for creation role, creates user, creation or examination & approval creation project, the permissions such as Maintenance Significant Items member；
Product owner is set and has permission to access functional module relevant with management current project, initiates demand and changes Shen
Please, maintenance items demand, each functional module maintenance of project, the permissions such as management project version repository；
Test owner is set and has permission to access current project management module, needs to evaluate demand, initiates use-case and evaluates Shen
Please, the permissions such as maintenance items use-case；Program member is set and has permission to access current project management module, demand and evaluation can be evaluated
Use-case.
Further, demand and use-case change management module, including demand applications management unit and use-case change management list
Member；
Demand applications management unit, the change request application initiated in the project for receiving product owner, setting option
Mesh member can receive demand modification application, evaluate change request and propose evaluation problem；
Use-case change management unit, creation change sequence after passing through for evaluation, and record change record.
Product owner can initiate change request application in the project, and program member can receive demand modification application, comment
It examines change request and proposes evaluation problem.Application needs to provide: version number, imprint, former demand and change request etc. are necessary
Document data.Creation change sequence after evaluation passes through, entering database documents includes: demand after version number, imprint, update, is updated
Preceding demand and change record etc..Project testing responsible person needs to provide corresponding use-case according to change request and initiates to evaluate, and uses
Example evaluation is submitted in change road after passing through, and entering database documents should include: use-case before changing, use-case after becoming new, use-case change record
Deng.
Further, use-case version library module includes change library and newest library；
Changing library includes document, change record after document, change before changing；Wherein, before changing document include former demand and
Former use-case；Document includes change request and change use-case after change；Change record includes demand change record and use-case change note
Record；
Newest library includes newest demand and newest use-case, that is, demand and use-case after change after changing.Change library and newest library
Name is consistent with change version number；After use-case evaluation passes through, change use-case is updated into newest library, the database documents that enter of use-case are answered
It include: demand after changing, use-case after change.
First class catalogue is change library in use-case version library module, can retrieval and inquisition according to change version name.Modification application
It can record which demand is this change version mainly update in order detail in detail；
First class catalogue is newest library in newest library, according to change version name+newly can retrieval and inquisition.It is product in newest library
Newest and most full demand and use-case.
Technical solution of the present invention also provides a kind of management method of product use-case persistence maintenance system, includes the following steps:
Rest authorization and certification, which is arranged, makes interacting between each module of system；
Administration authority is judged；
Version repository file handling procedure is managed.
Further, step setting Rest is authorized and certification makes interacting between each module of system, comprising:
S11: the username and password for receiving user's input generates and the one-to-one token of User ID through basic module；
S12: when calling Rest API with token, purview certification module obtains user by token from authentication module
Authentication information, it is ensured that be the user logged in；
S13: after user authentication passes through, go in the RBAC permission of certificate server whether obtain this user by User ID
There is the permission for calling this api interface.
Further, step judges administration authority, including；
S21: User ID user_id, file identification software_id, operation code operation_code are obtained
S22: whether operation code is upload, if it is S23 is executed, otherwise executes S24；
S23: whether user is administrator, if it is true is returned, otherwise returns to false；The administrator includes system
Administrator, domain administrator, organization administrator；
S24: whether operation code is modification, deletes, one of portfolio operations, if it is S25 is executed, otherwise returns to false；
S25: whether user is administrator, if it is S26 is executed, otherwise returns to false；
S26: the affiliated level s_level and level ID s_ of file is obtained according to file identification software_id
level_id；
S27: the affiliated level u_level and level ID u_level_id of user is obtained；
S28: judging s_level==u_level&&s_level_id==u_level_id, returns if it is true
Otherwise true returns to step S29；
S29: judge whether user is system manager or the affiliated level u_level of user is that tissue belonging to file corresponds to
Domain, if it is return to true, otherwise return to false.
Further, step is managed version repository file handling procedure, searching and managing and file solution including file
Pressure pipe reason；
The searching and managing of file, specific steps:
S301: query interface is called, file name to be checked is passed to；
S302: inquiry meets the file of the title from database；
S303: query result is returned；
Wherein, user can be according to the file in its listed files of the name query of file, and organization administrator can incite somebody to action this
Any file-sharing under constituent act catalogue is to its hetero-organization under same domain；Domain administrator can will be under this domain file catalogue
Any file-sharing to other domains in system；Ordinary user not can be carried out sharing operation；Customized shared, i.e. selection will be total to
The file enjoyed；It is all shared, i.e., the All Files under administrator's respective file catalogue are shared away.
File decompression management, specific steps:
S311: judging whether user has the permission of decompressing files, if there is carrying out S312, otherwise returns；
S312: decompressing files, the file object set after returning to decompression；
S313: the file object after traversal decompression calls saveDir method by the directory information if object is catalogue
It is stored to use-case version repository, saveFile method is otherwise called, the file information is stored to use-case version repository.
Wherein, the user of administrator's identity (i.e. system manager, domain administrator) can decompress Zip compression in server end
File.
Further, step is managed version repository file handling procedure, comprising: to the upload management of file and file
Download management；
The upload management of file, specific steps:
S321: User ID is obtained；
S322: judge whether the user there are upload permissions according to User ID；
S323: the root that customer documentation uploads to is obtained；
S324: the file information of upload, including title, description, uplink time are obtained；
S325: the opposite road specified according to the file repository root of the corresponding use-case version repository of hierarchy of users and user
Transmitting file on diameter；
S326: the file information after upload is stored in use-case version repository；
Wherein, file is uploaded to the file directory of system by system manager；File is uploaded to the text in domain by domain administrator
Part catalogue；File is uploaded to the file directory of tissue by organization administrator, and ordinary user cannot go up transmitting file, file both can more than
Passing under the root of corresponding file directory can also upload in some subdirectory under the catalogue, and subdirectory can be according to need
It voluntarily to create.
The download management of file, specific steps:
S331: user calls downloading file interface；
S332: otherwise the length of file name in judgement executes S334 if length is 1 execution S333；
S333: downloading single file, without squeeze operation；
S334: downloading multiple files and file, and compression is packaged downloading.
Wherein, after user logs on to the file management page, any file under the page in listed files can be downloaded.It can be same
The multiple files of Shi Xuanzhong and file are packaged downloading.
Further, step is managed version repository file handling procedure, including the modification management to file, file
Delete management and file modification management；
The modification management of file, specifically includes:
S341: user information and the file information to be modified are obtained；
S342: judge whether user has modification authority to this document；
S343: it if had permission, modifies and submits modified information；
S344: judging whether the file name after submitting meets rule, i.e., cannot be with the alternative document name under same catalogue
Claim identical；
S345: modifying local file title if meeting, and by modified information update to use-case version repository；
Wherein, the user of administrator's identity (i.e. system manager, domain administrator or organization administrator) can modify it
Any the file information under affiliated file directory, the information such as title, description including modification file.It is required that modified title
Cannot be of the same name with the alternative document under same catalogue, and the symbol in addition to point number cannot be included；Ordinary user cannot modify
The file information.
The deletion management of file, specifically includes:
S351: user information and the file information to be deleted are obtained；
S352: judge whether user has deletion permission to this document；
S353: if had permission, physics deletes file；
S354: use-case version repository information is updated；
Wherein, the user of administrator's identity (i.e. system manager, domain administrator or organization administrator) can delete it
Any file under affiliated file directory, and be that physics is deleted；Ordinary user cannot delete file.
File modification management, includes the following steps:
S361: user information and folder information to be modified are obtained；
S362: judge whether user has modification authority to this document；
S363: it if had permission, modifies and submits modified information；
S364: judge whether the folder name after submitting meets rule and cannot press from both sides with the alternative document under same catalogue
Title is identical；
S365: modifying local folders title if meeting, and by modified information update to use-case version repository.
Wherein, system manager can create file, Delete Folder under the file directory belonging to oneself and repair
Change folder name etc.；Domain administrator can create file, Delete Folder under the file directory belonging to oneself and repair
Change folder name etc.；Organization administrator can create under the file directory belonging to oneself file, Delete Folder and
Modify folder name etc.；Ordinary user not can be carried out portfolio operations；Folder name under same catalogue cannot repeat, together
Folder name under one catalogue can not be identical with file name.
As can be seen from the above technical solutions, the invention has the following advantages that providing a sustainable maintenance items correlation
The platform that demand and use-case upgrading update, can realize that demand is synchronous with use-case more in product function escalation process by this platform
New and maintenance, is conducive to the tracing and positioning of product full dose demand and use-case, while also achieving the function of each upgrade package of product
With the one-to-one tracking and maintenance of demand.Be conducive to be promoted the normalization of R & D of complex and the validity of demand exploitation.More into one
Step improves the coverage rate of test.
In addition, design principle of the present invention is reliable, structure is simple, has very extensive application prospect.
It can be seen that compared with prior art, the present invention have substantive distinguishing features outstanding and it is significant ground it is progressive, implementation
Beneficial effect be also obvious.
Detailed description of the invention
Fig. 1 is a kind of product use-case persistence maintenance system module block diagram；
Fig. 2 is change database documents structural schematic diagram；
Fig. 3 is newest database documents structural schematic diagram；
Fig. 4 is to carry out judgement flow diagram to administration authority.
Specific embodiment
The present invention will be described in detail with reference to the accompanying drawing and by specific embodiment, and following embodiment is to the present invention
Explanation, and the invention is not limited to following implementation.
Embodiment one
As shown in Figure 1, a kind of product use-case persistence maintenance system, including user management module, project management module, demand
With use-case change management module and use-case version library module, the interaction between each module passes through Rest authorization and certification；
User management module, for being managed to user, the user includes product owner, test owner, item
Mesh member, system manager；
Project management module, for being managed to item related information, item related information includes project name, project
The initial demand and use-case passed through after project verification relevant documentation, the project cycle, project correlation participant, project appraisal；
Demand and use-case change management module, for being managed to demand and use-case change；
Use-case version library module, for storing use-case, document and change record.
Use-case version library module is equipped with basic modular unit, software storage and secondary storage；
User management module, it is functional for system manager's permission to access and management system all items and institute to be arranged
Module is responsible for creation role, creates user, creation or examination & approval creation project, the permissions such as Maintenance Significant Items member；
Product owner is set and has permission to access functional module relevant with management current project, initiates demand and changes Shen
Please, maintenance items demand, each functional module maintenance of project, the permissions such as management project version repository；
Test owner is set and has permission to access current project management module, needs to evaluate demand, initiates use-case and evaluates Shen
Please, the permissions such as maintenance items use-case；Program member is set and has permission to access current project management module, demand and evaluation can be evaluated
Use-case.
Demand and use-case change management module, including demand applications management unit and use-case change management unit；
Demand applications management unit, the change request application initiated in the project for receiving product owner, setting option
Mesh member can receive demand modification application, evaluate change request and propose evaluation problem；
Use-case change management unit, creation change sequence after passing through for evaluation, and record change record.
Product owner can initiate change request application in the project, and program member can receive demand modification application, comment
It examines change request and proposes evaluation problem.Application needs to provide: version number, imprint, former demand and change request etc. are necessary
Document data.Creation change sequence after evaluation passes through, entering database documents includes: demand after version number, imprint, update, is updated
Preceding demand and change record etc..Project testing responsible person needs to provide corresponding use-case according to change request and initiates to evaluate, and uses
Example evaluation is submitted in change road after passing through, and entering database documents should include: use-case before changing, use-case after becoming new, use-case change record
Deng.
As shown in Figure 2 and Figure 3, use-case version library module includes change library and newest library；
Changing library includes document, change record after document, change before changing；Wherein, before changing document include former demand and
Former use-case；Document includes change request and change use-case after change；Change record includes demand change record and use-case change note
Record；
Newest library includes newest demand and newest use-case, that is, demand and use-case after change after changing.Change library and newest library
Name is consistent with change version number；After use-case evaluation passes through, change use-case is updated into newest library, the database documents that enter of use-case are answered
It include: demand after changing, use-case after change.
First class catalogue is change library in use-case version library module, can retrieval and inquisition according to change version name.Modification application
It can record which demand is this change version mainly update in order detail in detail；
First class catalogue is newest library in newest library, according to change version name+newly can retrieval and inquisition.It is product in newest library
Newest and most full demand and use-case.
Embodiment two
A kind of management method of product use-case persistence maintenance system, includes the following steps:
Rest authorization and certification, which is arranged, makes interacting between each module of system；
Administration authority is judged；
Version repository file handling procedure is managed.
Step setting Rest is authorized and certification makes interacting between each module of system, comprising:
S11: the username and password for receiving user's input generates and the one-to-one token of User ID through basic module；
S12: when calling Rest API with token, purview certification module obtains user by token from authentication module
Authentication information, it is ensured that be the user logged in；
S13: after user authentication passes through, go in the RBAC permission of certificate server whether obtain this user by User ID
There is the permission for calling this api interface.
As shown in figure 4, step judges administration authority, including；
S21: User ID user_id, file identification software_id, operation code operation_code are obtained；
S22: whether operation code is upload, if it is S23 is executed, otherwise executes S24；
S23: whether user is administrator, if it is true is returned, otherwise returns to false；The administrator includes system
Administrator, domain administrator, organization administrator；
S24: whether operation code is modification, deletes, one of portfolio operations, if it is S25 is executed, otherwise returns to false；
S25: whether user is administrator, if it is S26 is executed, otherwise returns to false；
S26: the affiliated level s_level and level ID s_ of file is obtained according to file identification software_id
level_id；
S27: the affiliated level u_level and level ID u_level_id of user is obtained；
S28: judging s_level==u_level&&s_level_id==u_level_id, if so, true is returned, it is no
Then return to step S29；
S29: judge whether user is system manager or the affiliated level u_level of user is that tissue belonging to file corresponds to
Domain, if it is return to true, otherwise return to false.
Step is managed version repository file handling procedure, searching and managing and file decompression management including file；
The searching and managing of file, specific steps:
S301: query interface is called, file name to be checked is passed to；
S302: inquiry meets the file of the title from database；
S303: query result is returned；
Wherein, user can be according to the file in its listed files of the name query of file, and organization administrator can incite somebody to action this
Any file-sharing under constituent act catalogue is to its hetero-organization under same domain；Domain administrator can will be under this domain file catalogue
Any file-sharing to other domains in system；Ordinary user not can be carried out sharing operation；Customized shared, i.e. selection will be total to
The file enjoyed；It is all shared, i.e., the All Files under administrator's respective file catalogue are shared away.
File decompression management, specific steps:
S311: judging whether user has the permission of decompressing files, if there is carrying out S312, otherwise returns；
S312: decompressing files, the file object set after returning to decompression；
S313: the file object after traversal decompression calls saveDir method by the directory information if object is catalogue
It is stored to use-case version repository, saveFile method is otherwise called, the file information is stored to use-case version repository.
Wherein, the user of administrator's identity (i.e. system manager, domain administrator) can decompress Zip compression in server end
File.
Step is managed version repository file handling procedure, comprising: to the downloading pipe of the upload management and file of file
Reason；
The upload management of file, specific steps:
S321: User ID is obtained；
S322: judge whether the user there are upload permissions according to User ID；
S323: the root that customer documentation uploads to is obtained；
S324: the file information of upload, including title, description, uplink time are obtained；
S325: the opposite road specified according to the file repository root of the corresponding use-case version repository of hierarchy of users and user
Transmitting file on diameter；
S326: the file information after upload is stored in use-case version repository；
Wherein, file is uploaded to the file directory of system by system manager；File is uploaded to the text in domain by domain administrator
Part catalogue；File is uploaded to the file directory of tissue by organization administrator, and ordinary user cannot go up transmitting file, file both can more than
Passing under the root of corresponding file directory can also upload in some subdirectory under the catalogue, and subdirectory can be according to need
It voluntarily to create.
The download management of file, specific steps:
S331: user calls downloading file interface；
S332: otherwise the length of file name in judgement executes S334 if length is 1 execution S333；
S333: downloading single file, without squeeze operation；
S334: downloading multiple files and file, and compression is packaged downloading.
Wherein, after user logs on to the file management page, any file under the page in listed files can be downloaded.It can be same
The multiple files of Shi Xuanzhong and file are packaged downloading.
In the present embodiment, step is managed version repository file handling procedure, including the modification management to file, file
Deletion management and file modification management；
The modification management of file, specifically includes:
S341: user information and the file information to be modified are obtained；
S342: judge whether user has modification authority to this document；
S343: it if had permission, modifies and submits modified information；
S344: judging whether the file name after submitting meets rule, i.e., cannot be with the alternative document name under same catalogue
Claim identical；
S345: modifying local file title if meeting, and by modified information update to use-case version repository；
Wherein, the user of administrator's identity (i.e. system manager, domain administrator or organization administrator) can modify it
Any the file information under affiliated file directory, the information such as title, description including modification file.It is required that modified title
Cannot be of the same name with the alternative document under same catalogue, and the symbol in addition to point number cannot be included；Ordinary user cannot modify
The file information.
The deletion management of file, specifically includes:
S351: user information and the file information to be deleted are obtained；
S352: judge whether user has deletion permission to this document；
S353: if had permission, physics deletes file；
S354: use-case version repository information is updated；
Wherein, the user of administrator's identity (i.e. system manager, domain administrator or organization administrator) can delete it
Any file under affiliated file directory, and be that physics is deleted；Ordinary user cannot delete file.
File modification management, includes the following steps:
S361: user information and folder information to be modified are obtained；
S362: judge whether user has modification authority to this document；
S363: it if had permission, modifies and submits modified information；
S364: judge whether the folder name after submitting meets rule and cannot press from both sides with the alternative document under same catalogue
Title is identical；
S365: modifying local folders title if meeting, and by modified information update to use-case version repository.
Wherein, system manager can create file, Delete Folder under the file directory belonging to oneself and repair
Change folder name etc.；Domain administrator can create file, Delete Folder under the file directory belonging to oneself and repair
Change folder name etc.；Organization administrator can create under the file directory belonging to oneself file, Delete Folder and
Modify folder name etc.；Ordinary user not can be carried out portfolio operations；Folder name under same catalogue cannot repeat, together
Folder name under one catalogue can not be identical with file name.
A project case management platform is provided using cloud computing system, function all in product development process is changed
Data and record are accomplished to manage and record, the demand and use-case of the continuous renewal of management projects of system well.
Description and claims of this specification and term " first ", " second ", " third " " in above-mentioned attached drawing
The (if present)s such as four " are to be used to distinguish similar objects, without being used to describe a particular order or precedence order.It should manage
The data that solution uses in this way are interchangeable under appropriate circumstances, so as to the embodiment of the present invention described herein can in addition to
Here the sequence other than those of diagram or description is implemented.In addition, term " includes " and " having " and their any deformation,
It is intended to cover and non-exclusive includes.
The foregoing description of the disclosed embodiments enables those skilled in the art to implement or use the present invention.
Various modifications to these embodiments will be readily apparent to those skilled in the art, as defined herein
General Principle can be realized in other embodiments without departing from the spirit or scope of the present invention.Therefore, of the invention
It is not intended to be limited to the embodiments shown herein, and is to fit to and the principles and novel features disclosed herein phase one
The widest scope of cause.
Claims (10)
1. a kind of product use-case persistence maintenance system, which is characterized in that including user management module, project management module, demand
With use-case change management module and use-case version library module, the interaction between each module passes through Rest authorization and certification；
User management module, for being managed to user, the user include product owner, test owner, project at
Member, system manager；
Project management module, for being managed to item related information, item related information includes project name, approves and initiate a project
The initial demand and use-case passed through after relevant documentation, the project cycle, project correlation participant, project appraisal；
Demand and use-case change management module, for being managed to demand and use-case change；
Use-case version library module, for storing use-case, document and change record.
2. a kind of product use-case persistence maintenance system according to claim 1, which is characterized in that user management module is used
It is had permission to access and management system all items and all functional modules, responsible creation role, creation in setting system manager
User, creation or examination & approval creation project, the permissions such as Maintenance Significant Items member；
Product owner is set and has permission to access functional module relevant with management current project, initiates demand modification application, dimension
Protect product demand, each functional module maintenance of project, the permissions such as management project version repository；
Test owner is set and has permission to access current project management module, needs to evaluate demand, initiates use-case evaluation application, dimension
Protect the permissions such as product use-case；Program member is set and has permission to access current project management module, demand and evaluation use-case can be evaluated.
3. a kind of product use-case persistence maintenance system according to claim 1, which is characterized in that demand and use-case change pipe
Manage module, including demand applications management unit and use-case change management unit；
Demand applications management unit, the change request application initiated in the project for receiving product owner, setting project at
Member can receive demand modification application, evaluate change request and propose evaluation problem；
Use-case change management unit, creation change sequence after passing through for evaluation, and record change record.
4. a kind of product use-case persistence maintenance system according to claim 3, which is characterized in that use-case version library module packet
Include change library and newest library；
Changing library includes document, change record after document, change before changing；Wherein, document includes former demand and former use before changing
Example；Document includes change request and change use-case after change；Change record includes demand change record and use-case change record；
Newest library includes newest demand and newest use-case, that is, demand and use-case after change after changing.
5. a kind of management method of product use-case persistence maintenance system, which comprises the steps of:
Rest authorization and certification, which is arranged, makes interacting between each module of system；
Administration authority is judged；
Version repository file handling procedure is managed.
6. a kind of management method of product use-case persistence maintenance system according to claim 5, which is characterized in that step is set
Setting Rest authorization and certification makes interacting between each module of system, comprising:
S11: the username and password of user's input is received through generating and the one-to-one token of User ID；
S12: when calling Rest API with token, purview certification module obtains recognizing for user by token from authentication module
Demonstrate,prove information, it is ensured that be the user logged in；
S13: it after user authentication passes through, goes in the RBAC permission of certificate server to obtain whether this user has tune by User ID
With the permission of this api interface.
7. a kind of management method of product use-case persistence maintenance system according to claim 5, which is characterized in that step pair
Administration authority judged, including；
S21: User ID user_id, file identification software_id, operation code operation_code are obtained
S22: whether operation code is upload, if it is S23 is executed, otherwise executes S24；
S23: whether user is administrator, if it is true is returned, otherwise returns to false；The administrator includes system administration
Member, domain administrator, organization administrator；
S24: whether operation code is modification, deletes, one of portfolio operations, if it is S25 is executed, otherwise returns to false；
S25: whether user is administrator, if it is S26 is executed, otherwise returns to false；
S26: the affiliated level s_level and level ID s_level_id of file is obtained according to file identification software_id；
S27: the affiliated level u_level and level ID u_level_id of user is obtained；
S28: judging s_level==u_level&&s_level_id==u_level_id, returns to true if it is true,
Otherwise S29 is returned to step；
S29: judge whether user is system manager or the affiliated level u_level of user is that tissue belonging to file is corresponding
Domain if it is returns to true, otherwise returns to false.
8. a kind of management method of product use-case persistence maintenance system according to claim 5, which is characterized in that step pair
Version repository file handling procedure is managed, searching and managing and file decompression management including file；
The searching and managing of file, specific steps:
S301: query interface is called, file name to be checked is passed to；
S302: inquiry meets the file of the title from database；
S303: query result is returned；
File decompression management, specific steps:
S311: judging whether user has the permission of decompressing files, if there is carrying out S312, otherwise returns；
S312: decompressing files, the file object set after returning to decompression；
S313: the file object after traversal decompression calls saveDir method to be stored to the directory information if object is catalogue
Otherwise use-case version repository calls saveFile method, the file information is stored to use-case version repository.
9. a kind of management method of product use-case persistence maintenance system according to claim 5, which is characterized in that step pair
Version repository file handling procedure is managed, comprising: to the download management of the upload management and file of file；
The upload management of file, specific steps:
S321: User ID is obtained；
S322: judge whether the user there are upload permissions according to User ID；
S323: the root that customer documentation uploads to is obtained；
S324: the file information of upload, including title, description, uplink time are obtained；
S325: on the relative path specified according to the file repository root of the corresponding use-case version repository of hierarchy of users and user
Transmitting file；
S326: the file information after upload is stored in use-case version repository；
The download management of file, specific steps:
S331: user calls downloading file interface；
S332: otherwise the length of file name in judgement executes S334 if length is 1 execution S333；
S333: downloading single file, without squeeze operation；
S334: downloading multiple files and file, and compression is packaged downloading.
10. a kind of management method of product use-case persistence maintenance system according to claim 5, which is characterized in that step
Version repository file handling procedure is managed, including modification management, the deletion management of file and the file modification to file
Management；
The modification management of file, specifically includes:
S341: user information and the file information to be modified are obtained；
S342: judge whether user has modification authority to this document；
S343: it if had permission, modifies and submits modified information；
S344: judging whether the file name after submitting meets rule, i.e., cannot be with the alternative document title phase under same catalogue
Together；
S345: modifying local file title if meeting, and by modified information update to use-case version repository；
The deletion management of file, specifically includes:
S351: user information and the file information to be deleted are obtained；
S352: judge whether user has deletion permission to this document；
S353: if had permission, physics deletes file；
S354: use-case version repository information is updated；
File modification management, includes the following steps:
S361: user information and folder information to be modified are obtained；
S362: judge whether user has modification authority to this document；
S363: it if had permission, modifies and submits modified information；
S364: judge whether the folder name after submitting meets rule and cannot press from both sides title with the alternative document under same catalogue
It is identical；
S365: modifying local folders title if meeting, and by modified information update to use-case version repository.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810834645.3A CN108984415A (en) | 2018-07-26 | 2018-07-26 | A kind of product use-case persistence maintenance system and management method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810834645.3A CN108984415A (en) | 2018-07-26 | 2018-07-26 | A kind of product use-case persistence maintenance system and management method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108984415A true CN108984415A (en) | 2018-12-11 |
Family
ID=64551415
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810834645.3A Pending CN108984415A (en) | 2018-07-26 | 2018-07-26 | A kind of product use-case persistence maintenance system and management method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108984415A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110086813A (en) * | 2019-04-30 | 2019-08-02 | 新华三大数据技术有限公司 | Access right control method and device |
| CN110852701A (en) * | 2019-10-18 | 2020-02-28 | 京东数字科技控股有限公司 | Product demand management method, device and system |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110054968A1 (en) * | 2009-06-04 | 2011-03-03 | Galaviz Fernando V | Continuous performance improvement system |
| CN102096693A (en) * | 2009-12-11 | 2011-06-15 | 鸿富锦精密工业（深圳）有限公司 | Documentation change tracking system and method |
| CN102385506A (en) * | 2010-08-30 | 2012-03-21 | 鸿富锦精密工业（深圳）有限公司 | User data version conversion system and user data version conversion method |
| CN102521697A (en) * | 2011-12-13 | 2012-06-27 | 广东电网公司信息中心 | Power grid informatization evaluating lab management system |
| CN104283875A (en) * | 2014-09-28 | 2015-01-14 | 深圳市中科无软件有限公司 | Cloud disk authority management method |
| CN104572449A (en) * | 2014-12-23 | 2015-04-29 | 中国移动通信集团广东有限公司 | Automatic test method based on case library |
| CN105068809A (en) * | 2015-08-13 | 2015-11-18 | 上海斐讯数据通信技术有限公司 | PyQt-based platform for implementing automation project management and case execution |
| CN105354141A (en) * | 2015-11-16 | 2016-02-24 | 北京用友政务软件有限公司 | EMT test case management system and method |
| CN107315950A (en) * | 2017-05-03 | 2017-11-03 | 北京大学 | Automation division methods and access control method that a kind of cloud computing platform administrator right is minimized |
| CN107368683A (en) * | 2017-07-19 | 2017-11-21 | 郑州云海信息技术有限公司 | One kind is based on cloud management platform case history storehouse shared system |
-
2018
- 2018-07-26 CN CN201810834645.3A patent/CN108984415A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110054968A1 (en) * | 2009-06-04 | 2011-03-03 | Galaviz Fernando V | Continuous performance improvement system |
| CN102096693A (en) * | 2009-12-11 | 2011-06-15 | 鸿富锦精密工业（深圳）有限公司 | Documentation change tracking system and method |
| CN102385506A (en) * | 2010-08-30 | 2012-03-21 | 鸿富锦精密工业（深圳）有限公司 | User data version conversion system and user data version conversion method |
| CN102521697A (en) * | 2011-12-13 | 2012-06-27 | 广东电网公司信息中心 | Power grid informatization evaluating lab management system |
| CN104283875A (en) * | 2014-09-28 | 2015-01-14 | 深圳市中科无软件有限公司 | Cloud disk authority management method |
| CN104572449A (en) * | 2014-12-23 | 2015-04-29 | 中国移动通信集团广东有限公司 | Automatic test method based on case library |
| CN105068809A (en) * | 2015-08-13 | 2015-11-18 | 上海斐讯数据通信技术有限公司 | PyQt-based platform for implementing automation project management and case execution |
| CN105354141A (en) * | 2015-11-16 | 2016-02-24 | 北京用友政务软件有限公司 | EMT test case management system and method |
| CN107315950A (en) * | 2017-05-03 | 2017-11-03 | 北京大学 | Automation division methods and access control method that a kind of cloud computing platform administrator right is minimized |
| CN107368683A (en) * | 2017-07-19 | 2017-11-21 | 郑州云海信息技术有限公司 | One kind is based on cloud management platform case history storehouse shared system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110086813A (en) * | 2019-04-30 | 2019-08-02 | 新华三大数据技术有限公司 | Access right control method and device |
| CN110852701A (en) * | 2019-10-18 | 2020-02-28 | 京东数字科技控股有限公司 | Product demand management method, device and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Chacko et al. | Why do my blockchain transactions fail? a study of hyperledger fabric | |
| CN103595730B (en) | A kind of ciphertext cloud storage method and system | |
| CN100527129C (en) | Infrastructure for performing file operations by a database server | |
| CN114365133A (en) | System or method for implementing forgotten rights on metadata driven blockchains with secret sharing and consensus on reads | |
| CN104967620B (en) | A kind of access control method based on attribute access control strategy | |
| CN100550010C (en) | Be used for application program and system and method based on the storage platform interface of item | |
| CN100570549C (en) | The system and method that is used for the data modeling of project-based storage platform | |
| CN113454619A (en) | Relational data management and organization using distributed ledger techniques | |
| US20090234880A1 (en) | Remote storage and management of binary object data | |
| CN104142930A (en) | Universal Delta data loading technology | |
| Magrahi et al. | NFB: a protocol for notarizing files over the blockchain | |
| Wang et al. | Ess: An efficient storage scheme for improving the scalability of bitcoin network | |
| CN108984415A (en) | A kind of product use-case persistence maintenance system and management method | |
| CN100565505C (en) | System and method by intermediary's file system or device synchronization computer system | |
| CN1739093B (en) | Systems for the implementation of a synchronization schemas | |
| Tolia et al. | Improving mobile database access over wide-area networks without degrading consistency | |
| CN1716247B (en) | System and method for synchronously providing conflict processing for information managing unit by hardware/software interface system | |
| CN104639599A (en) | System and method for downloading files in bulk | |
| CN112130894B (en) | Gray scale release management system, method and equipment applying characteristic switch | |
| JP6720613B2 (en) | Information processing system and information processing program | |
| CN111861117A (en) | Musical instrument evaluation data sharing method and system based on alliance chain | |
| CN110321462A (en) | Information dynamic updating method, device, computer equipment and storage medium | |
| Sanchez et al. | Restmule: enabling resilient clients for remote apis | |
| Li et al. | An efficient, secure and reliable search scheme for dynamic updates with blockchain | |
| CN109034664A (en) | A kind of road event management system based on B/S framework |
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: 20181211 |
|
| RJ01 | Rejection of invention patent application after publication |