Product requirements need to define boundaries, because resources are limited. The requirement without boundaries will lead to confusion of project objectives, extension of construction period, and increase of development cost.
1. Define the smallest business unit
Generally speaking, it is impossible to make a large and complete product, and it needs to have its own exclusive business market. From the user's point of view, if you want this function, you also want that function, and there are more and more user needs. But we need to grasp a principle to selectively restrict user needs within a certain range. This principle is the smallest business unit.
Before we design products, we need to clarify our own business boundaries, which are key businesses, which are auxiliary businesses, and which businesses are restricted areas, etc. We need to identify the core business process, satisfy the core process, eliminate interference, and ensure that the user's attention can be Focus on critical links, not let them scatter.
2. Define business roles
We need to clarify business roles, define who is responsible for each product function, and to what extent, etc., and determine the division of process responsibilities in the entire business chain. The carrier for expressing this method is the swim lane diagram.
In the swimlane diagram, the horizontal swimlanes are several stages of a complete business, generally in the order from beginning to end; the vertical swimlanes are the roles involved in the business. The white box corresponding to the role and the stage is what the role needs to do at this stage, generally corresponding to the function.
3. Sorting out business process standards
Business process standardization, that is, enterprise business SOP, refers to describing the standard operating steps and requirements of a certain event in a unified format, which is used to guide and standardize daily work.
That is to refine and quantify the key control points in a program, which helps to shorten the time for new members of the project to learn things, and just follow the steps to avoid mistakes and negligence. If a template is made for the activity operation, it belongs to the category of SOP to avoid unnecessary mistakes and improve operational efficiency.
4. Define field boundaries
Product functions are carried in the form of field information, and the aggregation of fields forms a page. The number of pages is usually determined by the functional boundary, and the information of the page is determined by the field boundary, that is, how many fields and information levels are required to clearly define this step.
A commonly used definition method for field boundaries is an entity relationship diagram, which is a graph that represents the relationship between entities and the attributes of entities. It mainly consists of entities, relationships and attributes. Entities are generally information, attributes of entities are generally fields that define entities, and relationships are levels of information. After the entity relationship is sorted out, the structure of the page is clear.
For example, if there are two test questions on the commodity quotation page, commodity and price, one commodity corresponds to multiple prices. Commodity attributes include commodity ID, category, brand, attribute, and attribute value, etc., and price attributes include price ID, price type, price, and validity period.
In order to further improve the quality of requirements analysis, CoCode requirements analysis tool uses AI, through requirements testing and consistency detection, it can quickly analyze user requirements defects in a few minutes, such as ambiguity, repetition, omission, inconsistency and complexity, etc., and accurately lock them Requirement problems, so as to modify defects more efficiently. In addition, the tool can automatically generate UML diagrams to provide a basis for design.
At present, CoCode has released a series of AI development tools: Co-Project intelligent project management tool (requirement itemization, automatic generation of test cases), demand analysis tool, review analysis tool, and story point estimation tool. Among them, the Co-Project project management platform has released 4 major versions, free trial for 30 days; and released a series of CMMI efficient implementation tools to achieve full coverage of the CMMI standard process and fully support the implementation of CMMI3-5 levels.