This is the development plan schedule that I founded from the Internet (I don't know if I have a controversy using the real name. I think it is a learning, I think it is a learning. I translated it. I hope to learn from, some of some of the software technology details do not affect the understanding of the development plan, so there is no translation, given that the English level is limited, there may be errors. Although the development plan is different, this document is revealed for the development of the standard. The word "Note:" is added to the translator. I can't give it a source, I have to stick it in the original.
Translator's note
The following is actual content
XXX '97 development plan
David updated in February 1997
Introduction
This document is a schedule developed by XXX'97. It is used to develop three part content services in the "Development Mode": XXX'97 development document and its OLE control for YY2.0, a service package for DTP And a separate browser.
The xxx'97 and xxx'97j (Far East) will be used as a call-tuneless drawing component service, an information exchange carrier between Office'96 and Publisher'96.
This schedule uses the Office Series Excel macro assembly to generate readability and strong reports, including weekly progress, if the schedule can be used on the network, do not have to print jobs.
XXX'97.xls - includes establishing all relevant document parts.
XXX'97j.xls - including all relevant document parts for the Far East version. Three developers will be specified after the XXX'97 non-Far East is completed.
In the development phase, the schedule will be updated weekly. Each month, the programmers must re-signature and summarize to David at the Daiwei, and the David Control Schedule schedule.
Regarding the details of this project, please contact the person in charge HO, he will guide you to find the relevant available document, such as: this project development specification.
Target date and stage
The development of each stage of this schedule is based primarily on schedule, although it is also largely affected by other clients: such as browser, yy2.0, etc.
Development consists of two main phases, the first phase: information can be delivered to its callback service integrated environment; the second phase: The remaining code is completed. The design of the project document will also follow these phases.
After completing the XXX'97, three developers will be immediately assigned to the XXX'97J Far East Engineering section.
The following table is the date of the expected important goal.
Table 1: Target schedule
5/1/96 The final motion and schedule end, the first phase begins (14 weeks) 7/31/96 The first phase code is completed. Improve the start (4 weeks) 8/15/96 The first available program submits 8/28/96 2 (14 weeks) 11/27/96 The second phase ends, the code is completed. 1/20/97 starts XXX'97J version development, three developers will mainly complete the Far East version released and compiled in the MIPS platform (12 weeks) 2/15/97 official version xxx'97 release, it includes ( ...) 4/15/97 xxx'97j version of the code completed 6/15/97 official version xxx'97j release
Details of each stage
Each stage includes 14 weeks of development, followed by 4 weeks, and perfect period. There are still 4 weeks of perfection period in the final stage.
Each development section is a paragraph in 47 days, including 14 days of internal improvement of working days, 6 days of disease, holidays, and 2.5-day code inspections.
The following table shows how many days are allocated at each stage. (Note: This algorithm is calculated 5 days per week)
Table 2: Stage definition
Main stage development period - 70 days
Schedule 47 days (67%)
Internal perfect period 14 days (20%)
(This consolidation phase is counted in major phases to encourage developers to immediately repair new errors, so that the program components have been stable.) Sick holidays, holidays, etc. (8.5%)
Normal situation The next stage each developer can have 1 day disease
In the project, (Note: The date relationship is concerned, considering the statutory holidays in the stage), there are 2 holidays in the first stage, and there are 3 holidays in the second stage, and there is 1 holiday during the J version.
Developers can catch up with 3 or 4 holidays per stage.
Perfect internal perfect - code review for 2.5 days (3.5%)
Each stage has a 2.5-day code inspection. This number is much more than a few programmers.
The buffer, consolidation and improvement period - 20 days.
The stage is perfect, and the error correction time has occupied 22% of 90 days as a major phase. All perfect, consolidated, buffered time (including 14 days of each phase) occupy a 38% engineering time, relative to the 47-day development task schedule, with 34 days of buffering and consolidation time.
When the test of XXX'97 is completed, this perfect stage is really ending. (Note: This means that although you have so much perfect time, or spend so much time, but if you don't have passed the test, then it is not finished.)
Main work item
Introduction ...
figure 1:
....
figure 2:
....
Development Resources
Main members of the development group: David (main person in charge and code division) AA (client interface) ... xxx (xxx)
Will get from other tasks from other tasks from other tasks to the members M1 (...), M2 (...)
The J version will be completed by J1 (... ...) J2 (...) J3 (...)
Table <
