A friend has a standard document that a friend wants me a demand because he is now responsible for a project. I said to him, my demand document is only suitable for me, it is not suitable for you. If you really want to introduce scientific management methods in the development process, calm down, carefully think about the methodology of careful learning needs, carefully think about how to fit your own itself. If you just need a good-looking template to make BOSS, then you will go to find a document to modify it, and ensure that you can live. Finally, my friend resolutely found a beautiful document. After friends, I thought for a long time. There are currently many software companies in China, but they are very problematic in management methods. What is the CMM fried boiling in the industry in the first half? It is a set of management methods suitable for software industries. This management method is not to say that you spent a lot of tickets to CMM's assessment or buying what products of Rational Corporation, but what do you really understand the essence of management. A few days ago, I looked at the article I would like to implement an ERP system, and I gave me a lot of feelings in one sentence. It said that Lenovo also has a lot of management specifications before implementing ERP, but it is the management of empty talks, the company mainly rely on "people". And the software companies we now are still in "people". The consequences of "human cure" are very serious, and it will lead to a high cost of your software. If you don't pass it, you will not be reached, and the company cannot develop rapidly. The software industry has always been famous for the profit, the profit is high, how much you think about the software's marginal cost (how much is copying a software?). However, China's software industry is not good. Look at our Taiwan compatriots, although they do not exceon their research in the software platform, it is very great in software applications. Of course, Taiwan has his historical reasons: well-affected by American culture, belonging to the main area of the US manufacturing outsourcing. The above has said a lot of nonsense, we still go back to our needs. Communication is a process that is a process, an important process in the software life cycle. In the previous one, we discussed the level of demand, the risk of demand, and the characteristics of demand. And the elements above so many demand elements have only one: communication. What is communication, saying that small is an important skill of the demand process, saying that it is a lifeline of a software company. There are many reasons for a project failure, and most of them can summarize the communication. Demand is full of communication: Demand analysts and users communicate, communication between different users, demand analysts and demand auditors communication, project managers and needs analysts. Communication to what extent is the sign of the success of the demand. When I chatted with several old classmates, I said that they went to the user to do demand research, the user reported a bunch of information, and chatted with them for a long time, they went back to start design, coding. I said that you will definitely suffer. Sure enough, the time of the project rework is almost equal to the time of the entire project. This is terrible, means that this project is very likely to lose money. Why is this so? The project is better than a building. If the designer doesn't even know how many layers don't have, what you say is to cover it. The "Software Needs" is mentioned in the book that the concept: software customer needs obligations and good rights excellent software products are based on excellent demand. High quality demand is derived from effective exchanges and cooperation between customers and developers. Typically, developers are associated with customer or customer agents, such as market employees, will become an opposite relationship. The managers of both sides only want their own interests and put on the needs of users to produce friction. In this case, they will not bring a little benefit to both sides. Only when both participants understand what they need to succeed, but also know what to successfully serve the partners to establish a relationship.
Due to project pressure and increasing increase, all risk bearers have a common goal. This is easy to be forgotten. In fact, everyone wants to develop an excellent software product that can be achieved without both business value, but also meets users. Software customer needs rights list list ten legal requirements for customers in the implementation of the project demand projects and analysts and developers. Each right corresponds to software developers, analysts' obligations. Software customer demand obligations also list ten obligations on customers in the demand process. If you prefer, you can use it as the development of the developer. Software Customer Demand Rights 1. Requires analysts to use expression in compliance with customer language habits. 2. Require analysts to understand the business and goals of the customer system. 3. Requires analysts to organize the information described during the acquisition period, and write software demand specifications. 4. Require developers explain the results of the work produced during the demand. 5. Require developers to maintain and maintain a job of cooperation throughout the exchange. 6. Require developers to provide suggestions for the implementation and demand for products, and take out your mind. 7. Describe the product to have easy-to-use, easy to use features. 8. Adjust your demand, allowing you to retrounce existing software components. 9. There is a true and credible assessment of the cost, affected, and trade-off when it is necessary to change the requirements. 10. A system that meets customer functions and quality requirements, and these requirements are agreed by developers. Software Customer Demand Officer 1. Expectation of the analysts explaining business and instructions in terms of the business. 2. Take time clearly explain the demand and constantly improve. 3. When you illustrate the system requirements, strive to be accurate. 4. Do you need to make decisions in time when needed. 5. To respect the cost estimation of developers and the feasibility analysis of demand. 6. Divide priority for single requirements, system characteristics, or use instances. 7. Review demand documents and prototypes. 8. Once you know to change the project requirements, you should contact the developer immediately. 9. When the demand change is required, it should be handled in accordance with the development process determined by the development organization. 10. Respect the process (procedure) used in the demand engineering. The rights and obligations of demand stipulate that both customers and developers should do what, both sides are working together to ensure the order of demand. However, most software companies generally implement the "customer is God" is very good. What kind of requests are available, what kind of revision of software companies do, ultimately harm the benefits of customers and their own parties. Once, I chatted with a small software company's technical director, please teach him the practice. After he experienced several salesperson to promise the pain of customer requirements, he decided to personally dispatched. In the process of contacting customers, he mastered the initiative. Judging that the customer is a "good" customer, and then decide to do this software. After a period of implementation, it was found that the effect was very good, the cost was greatly reduced, and the customer was also very satisfied. Software companies and customers are a pair of collaborators, one glory, and a loss. To achieve the situation in which the parties win-win, only can communicate with full communication. The process of demand analysis and demand management needs includes two processes, demand management and demand analysis. Like a company, it is difficult to achieve a smooth completion of the demand process. Of course, not all software companies do not have demand management, such as arrangement of the needs, is also the one hand of demand management. Most software companies do not have a science, any activity is inseparable from management, and the demand process is no exception. The activities of the demand process are divided into two kinds in demand management and demand analysis. Most people say that they don't know the difference in demand management and demand analysis, but they have been unknown in carrying out demand management and demand analysis when conducting a demand process. This kind of behavior is a bit like some small business owners, lacks scientific, system management knowledge, but you can't say he does not understand, because he has a lot of practical experience. Similarly, some lack of mature software companies are mainly experienced, and there is no verification method when performing demand analysis.
Demand analysis activities include acquisition, analysis, specification, and verification of a software project requirement. The result of typical demand analysis is the Software Requirements Specifications and related analysis models. Approved by the assessment, these documents define the marketing of the development work (Baseline). This baseline constructs an agreement for the functional requirements and non-functional needs of the customer and developers (AGREEMENT). Projects may have other conventions, such as deliverable, constraint, schedule, budget, and contractual provisions. But these are not factors that are mainly considered in the demand process. Demand conventions are bridges between demand development and demand management, and demand management includes all activities that maintain demand aggregation and accuracy during engineering progress, as shown. Demand management emphasizes: 1. Control changes to the demand baseline. 2. Maintain project plan consistent with demand. 3. Control a single need and version of the demand document. 4. Management requirements and contact chains or manage the dependencies between single needs and other projects deliverables. 5. Track the status of the demand in the baseline. As with any management activities, the purpose of demand management is to ensure that demand analysis activities are performed in accordance with established policy. CMMCMM (Capability Maturity Model) Process Maturity Model, this concept is proposed by the Institute of Software Engineering, the University of Carnegie, Pittsburgh, Pennsylvania. CMM is a model that is widely used in software development agencies to guide process improvements. This method describes five mature levels of software processing capabilities. The organization is typically managed in an informal manner in an informal manner, and it is necessary to achieve success, mainly relying on the hero epic struggle of genius from the industry and manager. Organizations in higher maturity levels combine creative, well-trained employees with software engineering and project management processes, will continue to successfully succeed. Process capacity maturity model is a useful guide for demand management. To achieve the second level of the software process capability model, organizations must have six key process areas, KEY Process Areas, KPa, which is software development and management to show the ability to achieve their goals. Demand management is one of them, and its goals are as follows: 1) Establish software requirements for software engineering and management. 2) Software plan, product and activities are consistent with software requirements. The key process of demand management does not involve collecting and analyzing project requirements. Instead, it is assumed that software needs have been collected or have given demand from higher level systems. Once the needs of the needs and documentation, the software development team and the relevant team (such as quality assurance and testing) require an evaluation document. Discovering problems should be solved with customers or other source for demand sources, the software development plan is based on confirmed demand. The development team should confirm the requirements and confirmation constraints, risk, accidental factors, and assumptions before committing a commitment to customers, market or managers. Maybe have to face a commitment to demand due to technical factors or progress reasons. However, you must never commit anything that cannot be implemented. The key to key treatment is also recommended to manage demand documents through version control and change control. Version Control ensures that you can know the version of the demand in the development and planning. Change control provides a modification of the specification to uniformly demand, and consent or oppose the recommendations based on business and technology factors. The software development plan should be updated at any time in the development of modification, increasing demand. It doesn't refer to the reality of the reality. It is necessary to emphasize that the CMM is just a recommended method, and does not say that you must use this method. Careful analysis of its own characteristics, summarizing the methods suitable for themselves. But the two goals mentioned by CMM are the goals that the demand activities should be pursued. In fact, it is not only different ways to adopt various enterprises, even in the enterprise, there is no standard mode for different projects, and there is no standard mode. Each project has its own characteristics and cannot be mandatory to use the same template.
Therefore, at the beginning of the project, the management team will formulate project plan and demand plan according to the characteristics of this project in the project feasibility. Demand Management Steps Development Organization should define the steps to execute the project group to manage their needs. Documentation Write these steps to make organizational members continue to effectively carry out the necessary project activities. Consider choosing the following topics: 1. Tools, techniques, and customary practices for controlling various demand documents and individual demand versions. 2. Suggestions, processing, negotiation, notifying new demands and changes to related functional fields. 3, how to develop a demand baseline. 4. The need to use will use, and who is allowed to make changes. 5, demand status tracking and reporting process. 6. Analyze the steps that should follow the impact of the proposed changes. 7, how the requirements change will affect the project plan and conventions. You can include all the information above in one document. Alternatively, you might like the topic, such as dividing a change control process, affecting the analysis process, status tracking process. These processes may be useful in multiple projects because they reflect the common functions that each project should follow. There are a lot of tools for demand control, you can use professional Rational's RequisistPro, you can also use some visual database management tools, or even you can just use the directory structure. What kind of tools are not particularly important, and the key is still in people. It has been said that the most important management of demand (key process domain) is version control and change management. These two aspects are closely related. An important factor in needing to control is that demand is constantly changing. Although the ocean of the document has not mentioned any specific documentation yet, most of the product of the demand process is a document. The purpose of the document is to be controlled for projects. If the document has fallen into an uncontrollable situation in order to achieve the purpose of the control project, it is a lot of astray. It is very ridiculous to imagine, but this mistake is true. There are often some fanatical technologies, in order to pursue perfect implementation project management, this project itself is not as huge. At the end, it is due to the out of control of the document leads to the out of control of the project. Even with a well known RUP (Rational Unified Process) does not advocate too much document. Control your plan to make it right for you. Demand analysts should focus on demand acquisition and analysis, rather than writing beautiful documents. Of course, if the user has this requirement, you should pay attention. The accumulated material change control process change control process changes the control process of the demand management activity can reduce the chaos caused by endless and out of control. It clarifies a method to propose, negotiate, assess a new need or change in an existing demand. Change control usually requires support for problem trace tools, but please remember that tools cannot be replaced. The Change Control Committee Process Change Control Committee (CCB) is made up of the main members of the risk bearer, which is executed on the proposed demand change decision, which is rejected, and which changes are included in each product release. The CCB process describes the composition and operation of the Change Control Committee. The main activity of CCB is the impact analysis of the proposed changes, making a decision for each change, and inform those who will be affected. Demand Change Influence Analysis List and Template Estimation The cost and impact of changes in demand changes is to determine whether or not to perform changes. Impact analysis can help CCB make the correct decision. Influence analysis lists include many self-friendly self-answering types, as: A participatory personnel work form can be used as a simple way to estimate task workloads, which will understand the complexity of confirmation. Demand Status Tracking Process Demand Management includes conditions for monitoring and reporting the status of each functional requirement. You need a database or a business demand management tool to track a large number of demand in a complex system. This process also describes the report format that outputs when you are always viewed. The demand tracking capability matrix template demand tracking capability matrix lists all functional requirements in the SRS and the process of corresponding design modules, source files, and implementation requirements, as well as test cases for verifying the correctness of the requirements.
The tracking capability matrix should also indicate the corresponding last layer user needs or system requirements. Demand Analysis Demand Analysis can be divided into four phases (analysis), analyzing, and verification, and verification. These subtries include all activities such as demand, evaluation, and writing documents in software products. Demand development activities include the following aspects: 1. Determine the user class desired by the product. 2. Get the needs of each user class. 3. Understand the actual user tasks and goals and the business needs supported by these tasks. 4. Analyze information from users to distinguish user task requirements, functional requirements, business rules, quality properties, suggestions to solve methods, and additional information. 5. Divide the needs of the system level into several subsystems and assign a part of the demand to the software components. 6. Understand the importance of relevant quality properties. 7. Discuss the division of implementation priority. 8. Write the collected user requirements into specifications and models. 9. Review demand specifications, ensuring common understanding and understanding of user needs, and understanding problems before the entire development team accepts instructions. Accumulated materials for demand development process 1) The view and range documentation of the project view and the range template project clarifies the conceptual function of the project and provides a reference for determining the priority and change. Demand view and range documentation is a concise, highly summarized new project business needs instructions. Writing a project view with a unified manner to ensure that all should be considered during the process of deciding during the project. 2) Demand Development Process This process introduces how to determine customers and get demand from customers. Projects are also described. Various demand documents and analysis models that need to be created. This process also indicates the types of information included in each requirement, such as: priority, expected stability or planning release number. At the same time, it should also be indicated in the steps of demand analysis and demand document inspection, and the step of confirming software requirements specifications and establishing a demand baseline. 3) The demand allocation process is very important to divide the high-level product demand into a number of specific subsystems, especially when the development system contains software products and software products including multiple subsystems (Nelsen 1990). Demand assignment is conducted after the system-level requirements completion and system architectures are determined, how the information contained in this process is assigned to ensure that the function is assigned to the appropriate system components, and how the allocation needs to be traced back to them. The upper two-level system needs and related needs in other subsystems. 4) Use the example template to use the instance template to provide a standard method that each user wants to use the task completed by the software system into a document. Using the instance definition includes a brief task introduction, an explanation of an abnormal condition that must be processed and an additional information describing the user task feature. Using an example can be used as a separate functional requirement as a software demand specification. Alternatively, you can also merge usage with the SRS template into a document, including both the use of the product, and includes software functional requirements. 5) Software demand specification Description Template Software Demand Specification Template provides a structured method for organized functional requirements and non-functional needs. The standard SRS template will help create a unified and high quality demand document. Multiple templates may be used to adapt to different types and scale of the organization. This reduces obstacles to the project because a "universal" template is not suitable for your project. 6) The demand priority determination process, at this time, the function of the program has to give up. We need to know which performance, the use of instances, or the lowest priority, so that we can reduce the range in any stage. 7) The formal review of the SRS and Using the Example Review list is an important measure to ensure software quality. The checklist indicates some errors found in the demand document. The list of applications in the review meeting will make your attention to the usual problem.
