3, B program because I was bitter ape Microsoft platform, so I am going to use is Microsoft

1/2, decided to start the project, the first step is to prepare the product group needs to sort out the requirements document. The requirements document is the need to negotiate a number of meetings summed. In the early demand for the product group can play for free, to any request for products qld car registration listed in detail as possible, qld car registration the full details of the column does not it does not matter, but for the final product showing the effect of the direction of large, have a completely clear description, because this may be directly related to the product architecture design; then into the mid-demand, this time we must introduce the main technical manager and technical, from a technical perspective needed to assess the feasibility and cost-effective demand, which makes the technology sector can be a basic understanding of the big architecture qld car registration direction (I once had encountered a project, due to product group in the United States, the development group in the country, the product group in the absence of thorough communication and development group, put the needs and customers to reach a consensus, after which allows Our technical department is very passive, the result is not the line in the specified time, the loss is small, qld car registration in front of customers dishonesty is big);! Finally, late in demand, you can issue a draft demand project, the draft requires product groups according to the time requirements and customer requirements , prioritize, and is divided into several modules, each assigned to a development manager to develop Story or backlog, let development manager subdivided task, assigned to each program ape, from the perspective of time, the need to set Sprint, assigned to each individual story and Sprint, and a Sprint cycle is usually two weeks (10 days), special qld car registration circumstances may be extended to three weeks. This process, the most critical is how planning Sprint, this time, for estimating story time is very critical. We used to program and product managers who ape sitting qld car registration together, one by one estimate the time for each story. For example, a story is completed by two individuals, two individuals certainly need to understand the needs in advance, and then in the other party does not know the circumstances, estimates of the two individuals qld car registration were completed story takes a number of days / times, if two people close to the time, it to a larger number of days as the estimate of the time, such a person is estimated three days, a man estimated two days, then the total estimated time for this story is 3 days / person * 2 = 6 days; If a large gap between the two people qld car registration , such as a person estimates the two days, in addition to individual assessment for 10 days, then there is need to explain why two people in the exclusion of the confounding factors, the estimates again, and finally arrive at a reasonable time. Project managers need to estimate the total time to arrange qld car registration Sprint qld car registration in the story.
3, B program because I was bitter ape Microsoft platform, so I am going to use is Microsoft's tools. First, there must be a code version control qld car registration software, I want to say here is that TFS. Microsoft TFS has two versions, one called Team Foundation qld car registration Server, called Team Foundation Service, younger brother have used, so to illustrate the difference between the following two: Server Edition requires companies to use their own servers to deploy, more suitable for the development of the LAN project, of course, can also be deployed in the public network, the advantage is you can maximize customize; qld car registration Service Edition is deployed in the Microsoft cloud, hosted by Microsoft, more suitable for small and medium sized companies across the region (the lack of hardware support), the advantage of convenience, and office365 account binding, you can also access the public network, the disadvantage qld car registration is you can not customize process templates. Other features are the same. In fact, regardless of the version of TFS, features are very powerful, fully meet the needs of agile development projects. I have heard some people complain to the program only ape with TFS, the project team not loaded VS, do not use it to open the task ah, open bug or something, and then buy a JIRA project team dedicated to what used to process control tools In fact, not necessary, TFS has a service portal, similar to sharepoint site, you can use it to give the project team used two versions are very easy to use. Of course, JIRA is very good, we had also used the two together, JIRA in a custom process qld car registration above is still quite good, we do use JIRA deployment process control and process control operation and maintenance associated with the code itself is not deep process control.
Then we can adopt rules to force the check in the code when binding task / bug / issue, and forced to write comment and check in notes, which are very important. Of course, the code can not casually be able to check in, ah, need to have the best personal review, this time, we can first Shelve code, then you can designate a person to give you review the code, review qld car registration code who comes through TFS comparison tool, the differences between shelve code and among the latest code, you can write code snippets to comment, a final decision can be submitted and the need to fight back, re-shelve. Some people may think that this is good trouble ah, will not affect the progress. I want to say is that if there is no such link, perhaps you can very quickly complete the development, but do not forget, even if the code is not finished, the quality of the code is very important, no one wanted to project into the test session because Should a problem occur and affect round of testing, but also do not want the line after the project because of performance issues, again review all of the code and find performance bottlenecks ......
By the way test, test developers easily than the general test is divided qld car registration into smoke test, regression test, fuzz test, load test / performance test, security test. The first two much to say, very familiar qld car registration with the back three are easily overlooked, but very important. There is a truth: any software, there will always bug, any kind of tests are not able to find out all the bug! Therefore, we need in the testing phase will simply find all the obvious bug out as much as possible, so that the rest of the bug will only occur under certain special circumstances. smoke test and regression test is simple and clear in order to find the bug, and fuzz, load, security, and so the test is used to find the bug in particular situations. fuzz can well Chengdu robust verification software, internal and output it to deal with any disorder through random input test system; load can make the system stable performance under a stress test systems, in order to assess the system / software How many people use, how many servers, as well as identify performance bottlenecks, thus optimizing code; safety testing can test the system, Microsoft has a complete set of safety process called SDL, not detailed. We've always wanted to do automated qld car registration testing company, fuzz and load can be automated, but do automated functional testing more difficult, VS has its own project templates for automated testing of web services, are interested can learn next. But personally feel that the ideal is not the kind of automation. Anyway, there are a large number of test sister, fully automated, and the company does a lot less sister, qld car registration ha ha, pull away. . .
Besides next release, published in a distributed system, more headaches, from QA to UAT, in the Staging and Production, various circumstances may require different configuration parameters, especially SOA systems, when deployed in a distributed, Configure the service address is usually a headache, the easiest method is to use automatic conversion profiles, they also have their own configuration management tools, but also moved the configuration database. Personally think that conditions can develop their own set of configuration tools for their own, but I, as a doctrine from simple, and I for SOA systems, my approach is this: First, a cluster of servers in each environment among engage in a machines designed to do internal DNS servers qld car registration us on dns server for each service qld car registration definition requires a distributed deployment of an internal domain, then in the configuration file, all these pre-defined internal domain name, if required local testing, you can modify their machines host file, map to 127.0.0.1 qld car registration or specific LAN IP address, including the address of the database also can do (this method Azure SQL invalid), then publish to any one environment does not need to change the address associated with the configuration; associated with the environment for some other application configuration, qld car registration I recommend stored qld car registration in the database, or make a special configuration services. qld car registration When the test is completed and released qld car registration Staging, Production would not have released, IP addresses bound to achieve through the exchange switch, specifically how to implement an IT thing here is not to say.
After 5, when the product line, will certainly encounter many specific situations arise bug, in order to find bug, have a monitoring system, which is a big topic, temporarily skipped, then found the problem, we should be able to reproduce, and then need to assess the severity of the problem, and then based on the results, decide whether to immediately repair or fix into the next release cycle, if it is needed to be done immediately repaired hotfix, open maintainence window, walked UAT-> Staging-> Production process, QA can not go, because there may have been developed in the next phase of the QA test, if the next stage of development has been in the UAT, then so anxious hotfix does not make sense, if already in the next stage UAT, prod appeared consequences can not run, then the production will be cut again before the staging version of it. On the database, staging and prod should need tools to synchronize.