Pages
- Bugs and Progrems need to be managed separately
- Bugs gather and settle in the bug nest
- Chat room other than soft quality
- inquiry
- Precautions when outsourcing software development
- Precautions when using purchase or free software
- privacy policy
- Process quality is important to business
- Release judgment is the most important matter to guarantee the quality of software
- Site Map
- Testing is the only way to guarantee software quality
- The ability of the development contractor is cut off by software development audit
- The profile of Gutara father in Kobe
- The quality of embedded software is guaranteed by release judgment, development audit and testing
- To improve the product quality of software
- What is needed for a software development organization
- What is required for software development technology
Category
- Release Judgment
- Overview・Four criteria for release judgment
- Overview・Four mechanisms for release judgment
- Release judgment criteria・The amount of test is measured by test density
- Release judgment criteria・Check the test execution rate when judging the amount of test
- Release judgment criteria・The first type of test is abnormal and semi-normal
- Release judgment criteria・The second type of test is stability and robustness
- Release judgment criteria・The third type of test is the RAS function
- Release judgment criteria・The fourth type of test is the version upgrade function
- Release judgment criteria・The fifth type of test is confirmation of past defects
- Release judgment criteria・Test implementation status based on progress confirmation
- Release judgment criteria・See the status of bug detection for evaluate of testing
- Release judgment criteria・Bug is considered separately to potential bugs and obvious bug
- Release judgment criteria・Estimate how many potential bugs remain
- Release judgment criteria・Remaining bug 0 is not a mandatory condition
- Release judgment criteria・The reliability growth curve is reasonably usableThe reliability growth curve is reasonably usable
- Release judgment criteria・The importance of residual bugs is judged from the degree of impact on service provision
- Release judgment criteria・Estimate the number of call center calls from the remaining bugs
- Release judgment criteria・Estimate the number of call center calls from the remaining bugs(2-nd)
- Release judgment criteria・Estimate the number of call center calls from the remaining bugs(3-rd)
- Release judgment criteria・To check the product quality, first check the design quality
- Release judgment criteria・Check the code quality to check the product quality
- Release judgment criteria・Confirmation of process quality is based on development practice and development
- Release judgment criteria・To check the development management, first look at the development plan
- Release judgment criteria・Check the development management process by the design, implementation, and test plan
- Release judgment criteria・See also concern and risk management and baseline management
- Release judgment criteria・Is the maintenance system and contract clear?
- Release judgment criteria・Also check the implementation status of the gate process
- Release judgment mechanism・Two types of software releases, one for external and the other for internal
- Release judgment mechanism・External releases are subject to release judgment
- Release judgment mechanism・Release judgment is made by QA-Manager or Dev.-Manager or the president
- Release judgment mechanism・The best way to determine the release is the official review
- Release judgment mechanism・Release judgment is also possible two-department meeting or individual judgment
- Release judgment mechanism・Keep a record of the release judgment result in the checklist
- Release judgment others・Software may be released by special adoption
- Release judgment others・Special recruitment is judged by test status, latent bugs and residual bugs
- Release judgment others・Annoying relationship between testing and bugs
- Release judgment others・Product quality is important for software quality
- Release judgment is the most important matter to guarantee the quality of software
- Test qualityy
- Overview・Software test objectives and test types
- Overview・Items to write in the software test plan
- Overview・Items to write in the software test report
- Overview・Useful test for quality assurance of embedded software
- Test type・Unit tests, integration test and system test
- Test type・Normal test, abnormal test and semi-normal test
- Test type・Semi-normal test in communication protocol processing
- Test type・Semi-normal test in state transition
- Test type・Semi-normal test with hardware control
- Test type・Functional testing of RAS
- Test type・Security test
- Test type・System Testing Category in The Art of Software Testing
- Test type・Function/Large amount of data/High load/Usability/Security/Performance/Storage area
- Test type・Configuration/compatibility/installation/reliability
- Test type・Abnormal recovery/maintainability/documentation/runbook
- Test type・Is the test for debugging or for quality assurance?
- Test plan・The plan writes the test policy first
- Test plan・Test Goal (Part 1) Delivery time, cost and product quality
- Test plan・Test Goal (Part 2) Process Quality, Work Quality and Test Management
- Test plan・Sharing of tests (Part 1) Design, implementation, recording and reproduction
- Test plan・Sharing of tests (Part 2) Primary isolation and debugging of defects
- Test plan・Test metrics (Part 1): Schedule and Deliverable Progress Management
- Test plan・Test metrics (Part 2): Test result management
- Test plan・Test environment and environment preparation
- Test plan・Decide how to classify defects and bugs and the items to be recordp
- Test plan・Definition of bugs and bug states is important for managing bugs and
- Test plan・Priority and track bugs and bugs
- Test report・Bugsmust must be prioritized and tracked
- Test report・Estimating latent bugs by reliability growth curve
- Test report・Test evaluation begins with an evaluation of the test content
- Test report・Write an evaluation of the test schedule in the evaluation of the test plan
- Test report・Write an evaluation of test efficiency in the evaluation of the test plan
- Test example・Memory leak test
- Test example・Non-memory dynamic resource leak test
- Test example・Rollover test of timers and counters
- Test example・Simultaneous execution test of multiple functions
- Test example・Add semi-normal and abnormal test to the startup
- Test example・Deterioration test of secondary storage devices such as flash memory and HDD
- Test example・Aging test under high load
- Test example・Aging test on poor quality channels
- Testing is the only way to guarantee software quality
- Audit for soft-Develop..
- Soft Audit overview・Purpose 1: Audit to determine development capability
- Soft Audit overview・Purpose 2: Audit to improve development capacity
- Soft Audit overview・Purpose 3: Audit to confirm the quality of bug-fixed software
- Soft Audit overview・Target 1: Audit the development process
- Soft Audit overview・Target 2: Audit the test technology
- Soft Audit overview・Target 3: Audit the ability to grasp requirements
- Soft Audit overview・Target 4: Auditing design / implementation capabilities (1/2)
- Soft Audit overview・Target 5: Auditing design / implementation capabilities (2/2)
- Soft Audit overview・Method 1: Soft audit is process audit + technical ability audit
- Soft Audit overview・Method 2: The process audit procedure is IS9001
- Soft Audit overview・Method 3: CMMI is the confirmation item for process audit
- Soft Audit overview・Method 4: Add ISO9001 and CMMI and divide by 2
- Soft audit practice・Preparation 1: Explanation of audit plan
- Soft audit practice・Preparation 2: Obtaining materials and understanding the organization
- Soft audit practice・Preparation 3: Pre-filling the checklist
- Soft audit practice・Audit day 1: 3 Realism is important for soft auditing
- Soft audit practice・Audit day 2: First of all, the opening meeting
- Soft audit practice・Audit day 3: Understanding the outline and scale of the organization (1/2)
- Soft audit practice・Audit day 4: Understanding the outline and scale of the organization (2/2)
- Soft audit practice・Audit day 5: Functions required for software development and department in charge (1/2)
- Soft audit practice・Audit day 6: Functions required for software development and department in charge (2/2)
- Soft audit practice・Audit day 7: Points to check the development process
- Soft audit practice・Audit day 8: Requirements management check points
- Soft audit practice・Audit day 9: Points for checking test technology
- Soft audit practice・Audit day 10: Points to check design and mounting technology
- Soft audit practice・Audit Day 11: Preparation of Audit Report (1/2)
- Soft audit practice・Audit Day 12: Preparation of Audit Report (2/2)
- Soft audit practice・Audit Day 13: Closing Meeting and Follow-up
- Soft audit Checklist・No1: Requirements management process
- Soft audit Checklist・No2: Planning management process
- Soft audit Checklist・No3: Tracking process
- Soft audit Checklist・ No4: Quality Assurance Process (1/2)
- Soft audit Checklist・No5: Quality Assurance Process (2/2)
- Soft audit Checklist・No6: Configuration management process
- Soft audit Checklist・No7: Outsourcing management process
- Soft audit Checklist・No8: Requirements management technology (general)
- Soft audit Checklist・No9: Reliability/Availability Requirements Management Technology
- Soft audit Checklist・No10: Maintainability requirements management
- Soft audit Checklist・No11: Security Requirements Management Technology
- Soft audit Checklist・No12: Acceptance condition management technology
- Soft audit Checklist・No13: Development management technology (general)
- Soft audit Checklist・No14: Test management technology (1/2)
- Soft audit Checklist・No15: Test Management Technology (2/2)
- Soft audit Checklist・No16: Test technology
- Soft audit Checklist・No17: Design/Cording Technology (Overview)
- Soft audit Checklist・No18: Technology for using purchased software
- Soft audit Checklist・No19: OSS/Free software usage technology
- Soft audit Checklist・No20: In-house software design/implementation technology (1/2)
- Soft audit Checklist・No21: In-house software design/implementation technology (2/2)
- The ability of the development contractor is cut off by software development audit
- Bug's nest
- Other topics
- Value of information
- The quality of the software is only one item, so it is difficult to understand
- No Silver Bullet
- Risks and concerns
- Normal test, abnormal test and semi-normal test
- Two concrete examples of quantitatively managing the progress of software development and testing
- Do you have your motto
- Informal communication
- Is it OK to wash the mask and reuse it?
- その他のお話