Software Engineering _ East Division Station _ class notes

2. Beta release
   1. Tear-resistant team "responder"
   2. Onezero team "bookkeeping book"
   3. Hit the team "arithmetic"
4. Presentation and development are equally important
   1. Input not as a demonstration of a step, the browser home page directly set to the project home
   2. Explain what you're doing while demonstrating.
   3. Demonstrate functionality in the story
   4. Function:
      1. Users need packages, do not let users choose
      2. Useless information removed
      3. Deployment time Estimate
      4. Built-in topics, default options,
      5. Service-side-to-phone evaluation time
6. Homework
   1. The line of code and the number of words in the blog are represented by a cumulative line chart.
   2. Cohesion and coupling, each of the examples
   3. Deploy test other team products
      1. Evaluation
      2. Index
      3. The relationship between indicators
      4. How to assign a value to an indicator
      5. Indicator evidence
   4. Alpha, Beta release impressions, harvesting, personal experiences (combined with knowledge points)
   5. After four weeks fork other team, then improve, add a function
   6. Team Project:
      1. Deployment Manuals
      2. Review report (refer to the "Building Law"), record the problem, everyone must write
      3. Two weeks after Real beta release, public release, 5 real users
      4. 27th before 24 o'clock, post a blog with product videos.
      5. Continuous research and development of new functions, performance load, stress testing, interface art, increase usability, testing the core functions of the dependence of special technology.
8. Same group evaluation
   1. Team leader to each team score, a total of 2*n points, not average, can have decimals.

Software Engineering _ East Division Station _ class notes