Software development project management
1. Types of software development
1. Software products (software products)
1.1 mostly horizontal markets (horizontal market) development. More users for personal, and the number of arbitrary, irregular capacity
1.2 provides functionality (features and functionalities) are applied to solve a specific problem or need
130 functional requirements (requirement) from the developer market development and sales force (marketing & sales), or users of the previous generation product feedback
1.4 examples: office software, single-function applications, games, etc.
2. Software system (software systems)
Most of the 2.1 vertical markets (vertical market) Development: users of a customer's specialized staff and departments team and limited in number, know in advance, and the ability to specialized training
2.2 offers most of the functions of a series to address specific customer business operations or operational problems or external services to meet customer needs
2.3 functional requirements from the customer's specific requirements and the operation of your business: its existing systems, processes limitations
2.4 examples: business operations software systems, automatic control systems, etc.
2. Preparation procedures must be carried out before the work
L understanding and the use of the programme, confirmed (User Scenario)
L detailed summary of the functional requirements and user audit confirmed
L design through functional integrity of the design specifications (Design Specification) to express
L to design specifications and is the basis for formulating the framework design (Architecture), the Development Programme (Implementation Plan)
L prior develop software test plans and test criteria for qualified (Exit Criteria)
3. Development project planning and management from the development team to take, and from the estimate on the time, to avoid artificial and unreasonable speculation
L development of the formulation of a concrete timetable for the development of functional tasks, and a few days for the measurement units
L throughout the development process to intermittent milestone to track
L conduct periodic review progress, make the necessary adjustments
L "spread function" (Feature Creep) strict control and management of four. Development and management
4.1 writing before any procedures must first have the design of the structure is zoned
4.2 any complex system architecture design procedures have first book
4.2.1 components of the system have a clear definition of the function.
4.2.2 interface for the design of the components prior and complete records.
4.2.3 architecture design of the framework by development engineers or designers of the leading staff to write.
4.2.4 architecture design book by project managers and testers, examine and approve, the preparation process can begin.
4.3 establishing procedures for the submission of the original code, and the establishment of a complete code of the original submission process management system
4.3.1 source code changes to allow only one person. Changes before the submission of the first application for the original code. Later admitted to the changes.
4.3.2 End first change in the development of the machine compiler engineers, together with the other components of the operation, confirmed no fatal flaws, the original code can be sent to the library.
In the 4.3.4 release of the product, the entire library is locked, only approved repair defects before it is submitted to the original code into the library.
4.4 establishing peer review of source code management system software development engineer times each wrote the original code has less to more than one of my colleagues in the review process.
4.5 The establishment of the original code-writing software development engineers each norms should be in accordance with the norms of program design, including the preparation of style, format, the standard interface components, the author of commentaries, and so on.
Five test management structure is zoned according to the design of the written test plan
5.1.1 test plan to ask project managers and development engineers are reviewed together.
5.1.2 testing program with the list of all the testing programme will be written.
5.1.3 each specific to the implementation of the testing programme are free, and to record the results of each test programme. Any deficiencies are recorded.
5.2 testing and development in parallel
In the latter part of the preparation of the components for the development of testing tools.
5.3 test in the implementation of the plan for attention
5.3.1 from the testing found that the defective development engineers to modify FEC.
5.3.2 revised from an initial testers to verify the quality (Smoke Test), can be passed by the development engineers sent to the submission of the original code.
5.3.4 any impact on each other components of error-correcting procedure changes, not only through changes in the procedure to re-test, may be affected by any other components or procedures must also be re-measured (Regression Test).
5.3.5 before issuing a full test (Full Test Pass).
5.4 test: 1. Determine the priority level 2 testing. Function Module 3. Function modules
5.5 test results: 1. Bug the number of (an average of one out of every 50 firms) 2. Code coverage (code implementation of the road)
Less than 5.6 test to the wrong place unknown to deal with mistakes
Six key to the implementation of
Design, earlier in the post-coding
No design specifications not write his book Programming Code
have all the coding of each other between the staff audit
all the coding before joining the compilation of the overall development engineers must first compile machines
"eat your own Goushi": the release of the product before the team members have yet to perfect their own products, and to report defects.
specialized team responsible for the compilation of the entire product and the construction of a daily compilation. The failure of any resulting compilation of this program must be written procedures for engineers to immediately amend Forward Error Correction (Fix Bug).
use of the entire company all team uniform defect reporting database tool. Each team take control of its own database. Any problems through the database to track defects.
has been modified to resolve the deficiencies (Fixed Bug) must find defects from the person (usually test) verification. be changed after the defect has been resolved through further testing must also be verified revised code does not create any new pests.
all the pest was classified into three grades and the gravity of the Three Laws of the level of priority. Team all staff must be asked in addition to the high level of pests.
some team implementation of "pests Prison" (Bug Jail) system: pest figures over five more engineers in the development of the former pest End closed except for the functions of the new code.
all key pests in products of issue must be decided by "the three" (Triage Meeting - PM, Dev, QA) in addition to discussion to decide whether to order changes.
before the release of the product team held regular "pre-war meeting" (War Meeting), a leading member of the audit team all pests.
each after the completion of a functional programming, all the team members as "grasping pest clean-up" (Bug Bash): each person within the time specified in the use of new features, will find the pest report in a timely fashion. Clean-up after the end of grasping the pest Statistics report to the team.
I participated in this paper is teched2003 Luan Yue teachers software after collating the project management
Tags: project management, software, software development
0 Comments to “Software development project management”
No Comments. Send your comment.
Leave a Reply
You must be logged in to post a comment.