CN110968298A - Management system and method applied to instantiation requirements - Google Patents
Management system and method applied to instantiation requirements Download PDFInfo
- Publication number
- CN110968298A CN110968298A CN201811166146.8A CN201811166146A CN110968298A CN 110968298 A CN110968298 A CN 110968298A CN 201811166146 A CN201811166146 A CN 201811166146A CN 110968298 A CN110968298 A CN 110968298A
- Authority
- CN
- China
- Prior art keywords
- requirement
- user
- demand
- requirements
- end module
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to the field of software development, in particular to a management system and a method applied to instantiation requirements, which comprise a front-end module used for interacting with a user, a requirements storage service for storing original requirements submitted by users in a requirements system database and storing requirements specifications compiled by technicians writing instantiated requirements specifications in a requirements system database, the system is used for composing the requirements submitted by the users and the corresponding event information generated in the application software in the specific service field into a proper data structure according to a certain sequence, and presenting the requirements and the event query service to the technical personnel by the front-end module, the demand system data access module is used for managing the access and the access of a demand system database, and is used for realizing a time-light machine interface which needs to be integrated with a demand management system and a time-light machine of application software in a specific service field; the technical scheme provided by the invention can overcome the defect that a great deal of time and resources are consumed for making a good instantiation requirement specification.
Description
Technical Field
The invention relates to the field of software development, in particular to a management system and a management method applied to instantiation requirements.
Background
The instantiation requirement is a set of software development process modes, and can ensure that correct products are effectively delivered and change of software products is assisted. As used herein, the term "correct product" means that the software is capable of meeting the business needs of the user or achieving a predetermined business goal; meanwhile, the method has certain flexibility, and can accept subsequent improvement with relatively stable investment in the future.
A "live document" is the end product of an instantiated requirement. By "live documents" it is meant that the documents track the functionality of the system in real time, and that verification of these requirements is automated through acceptance testing and is often performed, so that we can believe that the behavior of the system conforms to the requirements and the functionality that the testing refers to.
When looking at the existing instantiation requirement/BDD tools in the market, it can be seen that they all put the emphasis on how to automatically execute and verify the requirement specifications (i.e. acceptance test) after the instantiation requirement specifications are written. But how to help the software development team write a good instantiation requirement description is not the focus of their attention. For complex business applications, obtaining a good instantiation requirement specification is a time and resource consuming task.
The patent provides a system and a method for online collaborative formulation of instantiation requirement specifications. The starting point of the collaboration flow is to provide a requirement submitting function on a specific application with a definite state, and an end user can submit an original requirement by using the function and trigger the collaborative writing, improving and refining activities of subsequent requirement descriptions.
Two preconditions are required for the system and method to operate effectively.
One precondition is: there is already software that can work. This seems to be a significant limitation, which otherwise would benefit from the agile software development movements that have emerged over the last two decades. The "agile software development declaration" believes that such an appreciation of value should be established: software that works higher than exhaustive documentation; customer cooperation is higher than contract negotiation; response changes are higher than on schedule. With the practice and improvement of agile software development methodologies and related tools, it has become easier and easier for a software development team to develop a workable software, even an MVP (Minimum usable Product) as soon as possible.
Another precondition is: the application (software system) should be able to recover to the state at any point in time in the past. It is not as difficult for an application to implement this precondition as many people imagine, and one implementation is to build the application in an Event Sourcing (ES) mode. In addition, this precondition can also be implemented by a binary log provided by the database.
Disclosure of Invention
Technical problem to be solved
In view of the above disadvantages in the prior art, the present invention provides a management system and method applied to instantiation requirements, which can effectively overcome the above-mentioned defect that it takes a lot of time and resources to formulate a good instantiation requirement specification.
(II) technical scheme
In order to achieve the purpose, the invention is realized by the following technical scheme:
a management system applied to instantiation requirements comprises a front-end module used for interacting with a user, a requirement storage service used for storing original requirements submitted by the user into a requirement system database and storing requirement descriptions edited by technicians compiling the instantiation requirement descriptions into the requirement system database, a requirement system data access module used for combining the requirements submitted by the user and corresponding event information generated in application software in a specific service field into a proper data structure according to a certain sequence, a requirement and event query service presented to the technicians by the front-end module, a requirement system data access module used for managing the access and the access of the requirement system database, a time-light machine interface used for realizing the integration of the requirement management system and the application software in the specific service field, and a time-light machine used for realizing the integration of the requirement management system and the application software in the specific service field.
Preferably, partial functions of the front-end module of other applications can be embedded in the front-end module to support direct submission of requirements in other applications.
Preferably, the demand and event query service composes the demands submitted by the users and the corresponding event information occurring in the system into a timeline data structure according to the occurrence time sequence.
A method for instantiating a requirements management system, comprising the steps of:
s1, when the user clicks the requirement submitting button in the application software in the specific service field, the front-end module presents a corresponding form to the user;
s2, the user fills the requirement description in the requirement submitting form, and when the user clicks the confirmation button to submit the requirement, the front-end module calls the requirement storage service to store the original requirement submitted by the user;
s3, the front-end module calls a demand and event query service to obtain a time sequence of user submitted demands and application software events in a specific business field for technical staff to check;
s4, when the technician confirms that the application software in the specific service field needs to be 'backed' to the state that the user submits the requirement, the front-end module takes the time that the user submits the requirement as a parameter, and calls the time machine interface to realize the 'backing' of the application software in the specific service field;
s5, according to the requirement information submitted by the user, a technician logs in the application software in the specific service field by testing the user account, enters the corresponding page of the application software in the specific service field, and observes the state of the page when the user submits the requirement;
s6, the technician edits the requirement specification, and at the moment, the front-end module presents an editing form to the technician;
and S7, when the technician confirms the updating requirement description, the front-end module calls a requirement storage service to update the requirement description in the requirement system database.
Preferably, the corresponding form presented to the user by the front-end module is a demand submission form.
Preferably, the edit form presented to the technician by the front-end module is a professional instantiation requirement specification edit form.
(III) advantageous effects
Compared with the prior art, the management system and the method applied to the instantiation requirement, provided by the invention, put the following concerns: how to help the whole team to efficiently make a good instantiation requirement description, namely the first half of the instantiation requirement, and make up for the function blank of the existing instantiation requirement/BDD tool in the market;
the system and method provide an innovative collaborative way to make instantiation requirements online, first put the end user of the application software (possibly the client who made the requirements, business stakeholder, domain expert, etc.) into a workable software (a state-specific application context) to inspire the user to make preliminary requirements, then, by providing an online requirement specification editing and cooperating function, the team is helped to manage, improve and refine the requirement specification, therefore, the team does not need to gather related personnel together and discuss the related personnel face to face in the process of making the requirement specification by using the system and the method, the related personnel can remotely and asynchronously discuss the related personnel, the method has the advantages that the good instantiation requirement explanation is efficiently obtained with the help of the requirement management system, and the development and maintenance cost of the complex business application software is greatly reduced by improving the efficiency of the work.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the invention, and that for a person skilled in the art, other drawings can be derived from them without inventive effort.
FIG. 1 is a schematic diagram of the system of the present invention;
FIG. 2 is a schematic flow chart of the method of the present invention;
FIG. 3 is a schematic diagram of a user submitting a request to a request management system in accordance with the present invention;
FIG. 4 is a schematic diagram of a requirements submission form of the present invention;
FIG. 5 is a schematic diagram of a front-end module acquiring a time sequence of user submission requirements and application software events in a specific service domain according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention. It is to be understood that the embodiments described are only a few embodiments of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
A management system applied to instantiation requirements is disclosed, as shown in figure 1, and comprises a front end module used for interacting with a user, a requirement storage service used for storing original requirements submitted by the user into a requirement system database and storing requirement specifications edited by technicians compiling the instantiation requirement specifications into the requirement system database, a requirement system data access module used for composing the requirements submitted by the user and corresponding event information generated in application software in a specific service field into a proper data structure according to a certain sequence, providing requirements and event query services presented to the technicians by the front end module, managing the access and access of the requirement system database, and a time-optical machine interface used for realizing integration with a requirement management system and the time-optical machine implementation of the application software in the specific service field.
Partial functions of other application front-end modules can be embedded in the front-end module to support direct submission of requirements in other applications.
The demand and event query service combines the demands submitted by the users and the corresponding event information generated in the system into a timeline data structure according to the time sequence of the occurrence.
A method applied to instantiate a demand management system, as shown in fig. 2, includes the following steps:
s1, when the user clicks the requirement submitting button in the application software in the specific service field, the front-end module presents a corresponding form to the user;
s2, the user fills the requirement description in the requirement submitting form, and when the user clicks the confirmation button to submit the requirement, the front-end module calls the requirement storage service to store the original requirement submitted by the user;
s3, the front-end module calls a demand and event query service to obtain a time sequence of user submitted demands and application software events in a specific business field for technical staff to check;
s4, when the technician confirms that the application software in the specific service field needs to be 'backed' to the state that the user submits the requirement, the front-end module takes the time that the user submits the requirement as a parameter, and calls the time machine interface to realize the 'backing' of the application software in the specific service field;
s5, according to the requirement information submitted by the user, a technician logs in the application software in the specific service field by testing the user account, enters the corresponding page of the application software in the specific service field, and observes the state of the page when the user submits the requirement;
s6, the technician edits the requirement specification, and at the moment, the front-end module presents an editing form to the technician;
and S7, when the technician confirms the updating requirement description, the front-end module calls a requirement storage service to update the requirement description in the requirement system database.
The corresponding form presented to the user by the front-end module submits the form for demand.
The edit form presented by the front-end module to the technician is a professional instantiation requirement specification edit form.
Assume that there is now an online mall software system (hereinafter referred to simply as a mall system) that can run. Note that although the mall system is exemplified below, any application software that implements the preconditions required by the system and method may be integrated with the demand management system described in this embodiment.
Assume that there is some credit related functionality already in the mall system. Such as:
each time a consumer user in a shopping mall purchases a commodity, the consumer user obtains corresponding points, for example, 1000 points can be obtained by purchasing 1000 yuan of commodities;
the user shares the links of the commodities to other social platforms, such as microblog and WeChat, and then certain points … … can be obtained
Now, the software development and implementation team delivers the mall system to the customer, and the customer is tested with the identity of the customer user.
Assuming that a customer (i.e., a test user) logs in a mall with a test user account called Liqu, and sees 400 points on his own in the My points page, he thinks of a requirement: it is better to be able to do credit gifts here.
At this time, the customer may click on the plus button on the user interface to submit the requirements to the requirements management system, as shown in FIG. 3.
In the requirements submission form popped up at the interface, the test user fills in and submits the requirements in natural language, as shown in FIG. 4.
At a glance, those with knowledge of instantiation requirement/BDD will appreciate that the above natural language description is far from a qualified instantiation requirement specification.
Assume, next, that the test user (lee four) after submitting this demand, has tested the "share goods to WeChat friends" feature provided by the mall system, and has earned a reward of 50 points. The integrated balance of lie four is now 450 points.
Next, the test user has performed additional tests … … on the mall system
And finally, the customer finishes testing the mall system. During the testing process, the customer submits the thought requirements online.
Now, the technician (probably tester, developer) in the software development implementation team who is responsible for writing the instantiated requirement specification opens the mall system and the requirement management system, and can see that the current system state is:
in the mall system, the current credit balance of lie four is 450 points;
in the demand system, the demand content submitted by the customer (the test account number LiIV) is as follows: i want to remit my 300 points to Zhang III. When I finish the operation, my score is left 100 points, and the score of Zhang three is increased by 300 points.
If the technician can only see these two pieces of information, it is not for doubt:
how are the remaining points after Li IV awards 300 points to Zhang III?
Where 50 points of missing go?
What is meant by a handicapped customer is that is the bonus awarded a certain percentage of the commission fee deducted?
To resolve the confusion of technicians, it is necessary to make them see the status of the mall system at the moment when the customer (test account number LiIV) submits the demand, i.e. see that "the score of LiIV is 400 minutes" at that time.
To solve this problem we need:
1) marking a time stamp on each time of submitting the demands, namely recording the time point of submitting each demand;
2) the online mall system can restore the state to that point in time at which each demand was submitted.
The demand system described by the system and the method presents important events occurring in the system at each time point to a technician writing a demand specification in a time line (list) mode.
In the above example, the requirements system lists the available functions for the form and presentation on the user interface provided for the technician, as shown in FIG. 5. The technician can click the triangle "rollback" button in the interface to rollback the mall system to the state when the customer submitted the demand.
The technician can then log into the mall system via the "Liqu" account, enter the "my points" page, and view the points of "Liqu" upon submitting the demand (i.e., see the situation shown in FIG. 3).
With the illustration of FIG. 3 in mind, the technician can easily understand the original requirements submitted by the customer, and convert the content of the requirements submitted by the customer (i.e., the testing customer Liqu) into a substantially qualified instantiated requirement specification. The technician-written requirements specification results may be such that:
feature points donation
As a member of the market operator,
to increase the liveness of users and the growth of users,
i wish to add a bonus point transfer function.
Scenario successful bonus points
Given a Given user lie four has a 400 point score,
and three is a new user, his integral is 0,
when leen plum gives 300 credits in four directions,
the integral of Then lie four is 100 points,
the integral of And three is 300 points.
The meaning of the english keyword in the above example:
feature: function, characteristic.
Scenario: and (4) scene. A function may be described in multiple scenarios, such as a scenario with possible success and a scenario with failure.
Given: it is assumed. Preconditions for the tested scene.
And an d: and also.
When: when the temperature is higher than the set temperature. May be used to describe the user's input actions.
The method comprises the following steps: then. The output of the system is generally described herein.
As long as we understand these several keywords, we can see that such a requirement specification written in Gherkin (a domain specific language) is very close to natural language.
Based on this instantiation requirement specification, a developer (or development testing engineer with development skills) can write acceptance test code against it (some BDD tools are called step definitions). The skeleton code of the test code (step definition) can be generated generally using existing BDD tools.
The management system and the method applied to the instantiation requirement put the attention points on: how to help the whole team to efficiently make a good instantiation requirement description, namely the first half of the instantiation requirement, and make up for the function blank of the existing instantiation requirement/BDD tool in the market;
the system and method provide an innovative collaborative way to make instantiation requirements online, first put the end user of the application software (possibly the client who made the requirements, business stakeholder, domain expert, etc.) into a workable software (a state-specific application context) to inspire the user to make preliminary requirements, then, by providing an online requirement specification editing and cooperating function, the team is helped to manage, improve and refine the requirement specification, therefore, the team does not need to gather related personnel together and discuss the related personnel face to face in the process of making the requirement specification by using the system and the method, the related personnel can remotely and asynchronously discuss the related personnel, the method has the advantages that the good instantiation requirement explanation is efficiently obtained with the help of the requirement management system, and the development and maintenance cost of the complex business application software is greatly reduced by improving the efficiency of the work.
The above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions.
Claims (6)
1. A management system applied to instantiation requirements, characterized in that: the system comprises a front-end module used for interacting with a user, a demand storage service used for storing original demands submitted by the user into a demand system database and storing demand descriptions edited by technicians compiling instantiated demand descriptions into the demand system database, a demand system data access module used for forming a proper data structure by the demands submitted by the user and corresponding event information generated in application software in a specific service field according to a certain sequence, a demand and event query service presented to the technicians by the front-end module, a demand system data access module used for managing the access and the access of the demand system database, and a time-optical machine interface used for realizing the integration of the demand management system and the specific service field application software through a time-optical machine.
2. The management system applied to instantiation requirements according to claim 1, wherein: partial functions of other application front-end modules can be embedded into the front-end module so as to support direct submission of requirements in other applications.
3. The management system applied to instantiation requirements according to claim 1, wherein: the demand and event query service combines the demands submitted by the users and the corresponding event information generated in the system into a timeline data structure according to the time sequence of the occurrence.
4. The method of claim 1 applied to instantiating a demand management system, wherein: the method comprises the following steps:
s1, when the user clicks the requirement submitting button in the application software in the specific service field, the front-end module presents a corresponding form to the user;
s2, the user fills the requirement description in the requirement submitting form, and when the user clicks the confirmation button to submit the requirement, the front-end module calls the requirement storage service to store the original requirement submitted by the user;
s3, the front-end module calls a demand and event query service to obtain a time sequence of user submitted demands and application software events in a specific business field for technical staff to check;
s4, when the technician confirms that the application software in the specific service field needs to be 'backed' to the state that the user submits the requirement, the front-end module takes the time that the user submits the requirement as a parameter, and calls the time machine interface to realize the 'backing' of the application software in the specific service field;
s5, according to the requirement information submitted by the user, a technician logs in the application software in the specific service field by testing the user account, enters the corresponding page of the application software in the specific service field, and observes the state of the page when the user submits the requirement;
s6, the technician edits the requirement specification, and at the moment, the front-end module presents an editing form to the technician;
and S7, when the technician confirms the updating requirement description, the front-end module calls a requirement storage service to update the requirement description in the requirement system database.
5. The method of claim 4 applied to instantiating a demand management system, wherein: and the front-end module submits the corresponding form presented to the user as a requirement submission form.
6. The method of claim 4 applied to instantiating a demand management system, wherein: the edit form presented to the technician by the front-end module is a professional instantiation requirement description edit form.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811166146.8A CN110968298B (en) | 2018-09-30 | 2018-09-30 | Management system and method applied to instantiation requirements |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811166146.8A CN110968298B (en) | 2018-09-30 | 2018-09-30 | Management system and method applied to instantiation requirements |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110968298A true CN110968298A (en) | 2020-04-07 |
| CN110968298B CN110968298B (en) | 2023-03-10 |
Family
ID=70028245
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811166146.8A Active CN110968298B (en) | 2018-09-30 | 2018-09-30 | Management system and method applied to instantiation requirements |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110968298B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1399443A (en) * | 2001-07-26 | 2003-02-26 | 华为技术有限公司 | Graphical representation method of topological structure of network notes |
| CN102096871A (en) * | 2011-01-21 | 2011-06-15 | 吉林大学 | Intelligent self-service search and payment system for global commodities based on Internet of things |
| CN102129426A (en) * | 2010-01-13 | 2011-07-20 | 腾讯科技（深圳）有限公司 | Method and device for showing character relations |
| WO2015171099A1 (en) * | 2014-04-23 | 2015-11-12 | Alixpartners, Llp | Generating radial hierarchical network charts to convey organizational structures and associated performance data |
| CN106055527A (en) * | 2016-05-24 | 2016-10-26 | 华为技术有限公司 | Data processing method and apparatus |
| WO2017063092A1 (en) * | 2015-10-17 | 2017-04-20 | Rubikloud Technologies Inc. | System and method for computational analysis of the potential relevance of digital data items to key performance indicators |
| CN107911834A (en) * | 2017-12-28 | 2018-04-13 | 西安电子科技大学 | Lifetime optimal DAG building methods in data-centered wireless sensor network |
| CN108228874A (en) * | 2018-01-18 | 2018-06-29 | 北京邮电大学 | World knowledge collection of illustrative plates visualization device and method based on artificial intelligence technology |
| CN108345647A (en) * | 2018-01-18 | 2018-07-31 | 北京邮电大学 | Domain knowledge map construction system and method based on Web |
-
2018
- 2018-09-30 CN CN201811166146.8A patent/CN110968298B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1399443A (en) * | 2001-07-26 | 2003-02-26 | 华为技术有限公司 | Graphical representation method of topological structure of network notes |
| CN102129426A (en) * | 2010-01-13 | 2011-07-20 | 腾讯科技（深圳）有限公司 | Method and device for showing character relations |
| CN102096871A (en) * | 2011-01-21 | 2011-06-15 | 吉林大学 | Intelligent self-service search and payment system for global commodities based on Internet of things |
| WO2015171099A1 (en) * | 2014-04-23 | 2015-11-12 | Alixpartners, Llp | Generating radial hierarchical network charts to convey organizational structures and associated performance data |
| WO2017063092A1 (en) * | 2015-10-17 | 2017-04-20 | Rubikloud Technologies Inc. | System and method for computational analysis of the potential relevance of digital data items to key performance indicators |
| US20170132553A1 (en) * | 2015-10-17 | 2017-05-11 | Rubikloud Technologies Inc. | System and method for computational analysis of the potential relevance of digital data items to key performance indicators |
| CN106055527A (en) * | 2016-05-24 | 2016-10-26 | 华为技术有限公司 | Data processing method and apparatus |
| CN107911834A (en) * | 2017-12-28 | 2018-04-13 | 西安电子科技大学 | Lifetime optimal DAG building methods in data-centered wireless sensor network |
| CN108228874A (en) * | 2018-01-18 | 2018-06-29 | 北京邮电大学 | World knowledge collection of illustrative plates visualization device and method based on artificial intelligence technology |
| CN108345647A (en) * | 2018-01-18 | 2018-07-31 | 北京邮电大学 | Domain knowledge map construction system and method based on Web |
Non-Patent Citations (3)
| Title |
|---|
| 刘晓平;卫兴武;王恩柱;: "可视化并行编程平台中进程拓扑图的自动调整" * |
| 杨溢;林煜明;邹文静;: "基于图模型的海量商品知识表示与管理" * |
| 蒋秉川;万刚;徐锐;: "网络空间剖分机理与可视化方法研究" * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110968298B (en) | 2023-03-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Nelson | IT project management: Infamous failures, classic mistakes, and best practices. | |
| Langer | Guide to software development | |
| Stol et al. | Competition-based crowdsourcing software development: a multi-method study from a customer perspective | |
| O'Connor et al. | An innovative approach to the development of an international software process lifecycle standard for very small entities | |
| Coleman Sr | The customer-driven organization: Employing the Kano model | |
| Sauer et al. | Fit, failure, and the house of horrors: toward a configurational theory of IS project failure | |
| DePalma et al. | Project management for crowdsourced translation: How user-translated content projects work in real life | |
| Podeswa | UML for the IT Business Analyst | |
| US20070038754A1 (en) | Open-innovation network | |
| Gillies | Managing software engineering: CASE studies and solutions | |
| Lins et al. | PACAs: process-aware conversational agents | |
| Swatman et al. | Formal specification–an analytic tool for (management) information systems | |
| Götz et al. | The (Go) SMART way to agility: managing a Scrum subproject in a waterfall environment | |
| CN110968298B (en) | Management system and method applied to instantiation requirements | |
| Matsubara et al. | Buying time in software development: how estimates become commitments? | |
| Schubert et al. | Development of a token design framework | |
| Amland | Software quality and software testing in internet times | |
| US20220391797A1 (en) | Distributed platform for the development of attracting and scaling innovation | |
| Cochran et al. | Business-driven information systems change: establishing an alternate lens for understanding the change process | |
| Tunzira et al. | Analyzing and Verification of Web Service Composition | |
| O'Connor et al. | An innovative approach to the development of an international software process lifecycle standard for very small entities | |
| Arfman | The Japanese software industry: a comparative analysis of software development strategy and technology of selected corporations | |
| Luckham et al. | Modeling and causal event simulation of electronic business processes | |
| Rousta | A human-centric service approach for architecting and reengineering global system | |
| CN115545627A (en) | Approval task processing method and device, storage medium and electronic equipment |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |