PRODUCT IMPLEMENTATION Chapter 8 Tawatchai Iempairote September 23, 2041
Jan 18, 2016
PRODUCT IMPLEMENTATION
Chapter 8Tawatchai Iempairote
September 23, 2041
AGENDA
Design Completion Criteria Implementation Standards Implementation Strategy Reviews and Inspections Implementation Process
Implementation Process
Design Completion CriteriaFor large systems, high-level design often requires several stages:
At the first level, you subdivide the system into subsystems, components, or modules. DES1, DESn
If these subsystems are reasonably large, repeat the high-level design process for each subsystem or component;
At the end, you should have the external specifications for each subsystem, component, or module and should also have the detailed design of the highest level logic for the system.
Implementation Standards
The implementation standards add to and extend the standards defined during the design phase
Standards review Naming, interface, and message
standards Coding standards Size standards Defect standards Defect prevention
Implementation Standards:Standards Review Review the name, interface and message
standards developed during the design phase
Check that the list of the reusable routines is complete and that all the team members are using it
Review the name glossary: complete & used
Check the component and subelement names and review the shared variable, parameter and file names for consistency
Check the standard interfaces and messages.
Start with reasonable draft
Known & used by all team members
Implementation Standards:Coding Standards
Same language, same standards. Ensured that the entire team agree to
use the same standard. The commenting practices => speed
code review + enhance + code sharing
REUSE
Implementation Standards:Size Standards Some product elements might need size
measures.
Requirements (SRS) (count text page, paragraph, shall statement)
High-Level Design (templates pages, txt lines, use cases)
Detailed design (pseudocode txt lines, LOC) Screens & Reports Databases Messages Text scripts & test materials
Implementation Standards:Defect Prevention
Pick the defect types that seem to be causing the most trouble. These defects may waste the most test time, be hardest to diagnose and fix, or otherwise be most annoying.
Examine a number of defects of this type to identify particular defect causes and divide which ones to address.
When you see a defect you think you can prevent, make a process change to prevent it.
Assuming this action is effective, start looking for the next defect category and handle it the same way.
(initialize variable => coding standards)An understanding of defect causes can help in defect prevention
Implementation Strategy
The implementation strategy should generally conform to the design strategy.
Review (detail => big picture) Reuse (use standard comment) Testing
Reviews and Inspections Many implementation defects are simple
transcription mistakes that result from random keystroke errors.
Finding some of these errors in test can be exceptionally hard.
Reviews and inspections can consider all the paths and data values for a logical program segment.
That is why reviews and inspections are much more efficient than testing .
Design Inspections
It is hard to find sophisticated design defects when doing a review or inspection of a source program.
To produce quality programs, you must produce thorough and complete design documents and then review, inspect, and fix them before you start coding.
Implementation ProcessEntry Criteria
A completed development strategy and plan
Completed, reviewed and updated SRS and SDS specifications
A defined and documented coding standard Available copies of routine functional
specification list, name glossary, and all the other standards the team has adopted.
Implementation Planning
The development manager leads the work to Define and plan the implementation tasks ( SUMP, SUMQ).
Task Allocation
The team leader allocates the tasks among the team members and obtains commitments for when they will complete these tasks.
Detailed Design and Design Review
The engineers produce the detailed design.
Do a design review using thorough design review methods.
Complete forms LOGD and LOGT.
Unit Test Plan
The engineers produce the unit test plans.
The engineers follow script UT to develop the unit test cases, test procedures and test data.
Detailed-Design Inspection
The quality/process manager leads the team in a DLD inspection of each component.
Complete forms LOGD and INS.
Detailed-Design Inspection
The quality/process manager leads the team in a DLD inspection of each component.
Complete forms LOGD and INS.
Coding and Code Review The engineers produce the component source
code.
Do a code review using a personal checklist.
Compile and fix the code until it compiles without error.
Complete forms LOGD and LOGT.
Code Inspection
The quality/process manager leads the team in a code inspection of each component.
Complete forms INS, LOGD and LOGT.
Unit Test
The engineers, following script UT
Conduct the unit tests.
Complete forms LOGD and LOGT.
Component Quality Review
The quality/process manager reviews each component’s data to determine if component quality meets established team criteria.
If so, the component is accepted for integration testing.
If not, the quality/process manager recommends Either that the product be re-inspected and
reworked Or that it be scrapped and redeveloped.
Component Release
When the components are satisfactorily implemented and inspected, the engineers release them to the support manager.
The support manager enters the components in the configuration management system.
Exit Criteria
Completed, reviewed, and inspected components.
Completed INS/LOGD forms for the design and code inspections.
Updated SUMP, SUMQ, SUMS, LOGT LOGD.
Updated project notebook.