l Quality first, the productivity is second. High quality is valuable to all users, and productivity is only meaningful to the development side. l Software engineering three basic strategy multiplexing: improve quality and productivity; divide it: decompose a complex problem into a number of simple questions, then resolve; optimization - trade-offs L-all mistakes mistake. l The manager cannot be old, and it is an official, but it should always be the main responsibility of the responsibility. l Programmer's honesty, simple (pragmatic), love is clear, work monotonous but does not have the conditions of the program manager: technical level is the highest level in the programmer team; can do the most and the most difficult Work; there is a charm; (in order to work, justice) (PS: personal thinking communication ability is the most important) l Programmer will be programmed after the manager; the software company's manager is both master technology, but also know Manage, but many technicians are working in how to manage. l Project Plan: Knowing yourself and knowing each other: There are resources available for projects, which can be reused soft and hardware environments. Progress arrangement: The project plan should be dynamic, with the changes in customer demand. The schedule should be discussed by the development group and pass, so that several milestones must be established; the schedule must establish a certain buffer time for time arrangements in the schedule; (this is to pay attention to in the future) L Quality Management - Advocate "Zero Defect Quality Management"; two cores are: High goals: Only high goals can only achieve high quality levels. Executable specification: Good specification must be capable of executive; no norms lead to disorder and chaos; too strict specification is easy to kill programmers vibrant. Creativity. L Software Quality Factors - Simplified To the following: The correctness and accuracy (primary consideration, expandable to fault tolerance and reliability) Performance and efficiency can be appreciated and complainable with simpleness Expansion L Quality Check: Quality check should be performed in each practical link, corresponding to schedule, perform quality check is relatively reasonable when each milestone arrives. The contents of the inspection include: making an assessment and advice. l Feasibility analysis of feasibility analysis: economic: cost gain analysis; short-term long-term income analysis. Technical: Whether it can be completed within the specified time; whether the expected quality standard can be achieved; whether it can achieve the expected productivity. Social Environment: Market Analysis of Products; Products and Markets are affected by policy. The difficulty of demand analysis of people (team) l is that the customer is unclear; the demand itself changes frequently; analyzers or customers are incorrect. l In the core problem of demand analysis: what should be understood: from the main arrival, by macro to micro. How to use: communicate with customers; ask your hipster; analyze the excellent and failed software in the same industry;
