Transfer Macro about demand analysis:
Customers and developers have a good way. The following recommendations 20 rules, customers and developers can reach the following contents through review. If you encounter a difference, it will be reached by negotiation to achieve mutual understanding of your respective obligations, in order to reduce the future friction (such as one request and the other party is not willing or not satisfying the requirements). 1. Analysts to use the expression demand in accordance with customer language habits to focus on business needs and tasks, so terms should be used. Customers should teach analysts for analyzes related terms (eg, pricing, printing goods, etc.), and customers do not have to understand the terminology of the computer industry. 2. Analysts must understand the business and goals of our customers Only analyst better understand the customer's business, in order to better meet the needs. This will help developers to design outstanding software that truly meets customers and achieves expectations. To help develop and analyzers, customers can consider inviting them to observe their workflow. If you are switching a new system, development and analysts should use the current legacy system, which is conducive to how the current system works, and its process is available. S 3, analysts must write software requirements report analysts should be organized from all the information obtained from customers to distinguish business needs and specifications, functional requirements, quality objectives, solutions, and other information. Through these analysis, customers can get a "demand analysis report", which reaches an agreement between developers and customers to develop product content. The report should be prepared in a way that customers think is easy to read and understand. Customers should review this report to ensure that the contents of the report have accurately express their needs. A high quality "demand analysis report" helps developers to develop genuine products. 4, the explanation of the results of the demand work may adopt a plurality of charts as a supplementary description of the textual "demand analysis report", because the work chart can clearly describe certain aspects of system behavior, so each report The chart has a very high value; although they are not difficult to understand, customers may not be familiar with this, so customers can ask analysts to explain the role of each chart, the meaning of the symbol, and how to develop work, how to Check the chart has no error and inconsistency. 5. Developers must respect customers' opinions If users and developers cannot understand each other, the discussion about the demand will be obstacted. Common cooperation can make everyone "listen to it". Customers who participated in the demand development process have the right to request developers to respect them and cherish their time for success. Similarly, customers should also demonstrate their efforts to develop people's common goals for the project. 6. Developers should make recommendations and solutions to demand and product implementation. Usually, the customer's "demand" is already a practical implementation plan, and analysts should try their best to understand the real business needs from these solutions. It should be found that the existing system does not match the current business to ensure that the product will not be ineffective or inefficient; after thorough understanding things in the business sector, analysts can propose considerable improvement methods, experience and creation The analyst person can also propose some of the valuable system characteristics that some users have not found. 7. Describe the product usage characteristics Customers can require analysts to pay attention to software easier, because these ease of characteristics or quality properties make customers more accurate and efficiently. For example, customers sometimes require the product to "interface friendship" or "robust" or "high efficiency", but for developers, it is too subjective. The correct approach is that analysts understand which features have a negative impact on which characteristics is negatively influenced by inquiring and surveying the customer's "friendly, strong, efficient, and the specific characteristics included in the customer." Doing weighing to ensure reasonable payment.
8, allowing reusability of existing software components to usually have certain flexibility, analysts may find that some software components are very similar to customer description, in which case analysts should provide some modification requirements In order to develop the development costs and time saving time of the new system, it is not necessary to develop in accordance with the original needs. So, if you want to use some existing business common components in our products, they are not fully fitted with the features you need, and the flexibility of a certain extent is extremely important. 9. It is required to provide a real and reliable assessment of the cost of change. At this point, it is necessary to evaluate the impact of demand changes to help business decision-making. Therefore, the customer has the right to develop a true and credible assessment by analyzing the development personnel, including impact, cost and loss. Developers cannot exaggerate assessment costs because they do not want to implement changes. 10. Everyone who meets the customer's function and quality requirements, everyone wants the project to succeed, but this not only requires customers to clearly inform the developer's "what" what is required to "do", but also ask developers to understand It must clearly explain your assumptions and potential expectations, otherwise developers can not satisfy you. 11. Explain your business analyst to explain your business analyst to the business concept and terminology, but customers cannot count on experts will become experts in the field, but they can only understand your problems and goals; don't expect analysts Grasping the microscopic potential of customer business, they may not know "common sense" for customers. 12. Take the time clearly, and improve the demand customers are very busy, but no matter how customers are necessary to draw the time to participate in the "Mental Peak Conference" discussion, accept interviews or other activities to obtain demand. Some analysts may first understand your point of view, and afterwards find you still need your explanation, please patiently treat some demand and demand refining process, because it is a natural phenomenon in people's communication, not to mention This is extremely important for the success of software products. 13. It is difficult to prepare a clear and accurate demand document in detail. Since the problem of processing details is not only annoying and time consuming, it is easy to leave ambiguous demand. However, during the development process, this kind of fuzziness and inaccuracy must be solved, and the customer is precisely the best candidate to solve these problems. Otherwise, there is only to rely on the developer to correctly guess. This is a method for temporarily adding the "to-pending" flag in the demand analysis. This flag can indicate which is where it is necessary to further discuss, analyze or increase information, and sometimes it is also a "to be determined" because it is difficult to resolve or not handle it. Customers should try to explain the contents of each demand so that analysts can accurately write them into the Software Demand Report. If the customer does not accurately expresses, it is usually required to use prototype technology. Through prototype development, customers can repeatedly modify them with developers, and constantly improve the demand definition. 14. Timely decision analysis will require customers to make some choices and decisions, including processing methods raised from multiple users or select compromise in quality characteristics conflicts and information accuracy. Customers who have the right to make decisions must actively treat this, do it as soon as possible, do decide, because developers usually only wait for customers to make decisions to act, and this wait will delay the progress of the project. 15. Respecting the feasibility of developers and cost assessment of all software features have their own cost. Certain product features of customers may not be in technology, or implement it to pay high cost, and some demand tries to achieve performance that is impossible to achieve in the operating environment, or attempts to get some fundarated data. . Developers will have a negative evaluation of this, and customers should respect their opinions. 16. The priority of division needs Most items do not have enough time or resource implementation of each detail.
