본 포스트는 개인 스터디 용으로 작성된 Ian Sommerville의 Software Engineering, 8/E의 요약본입니다.1. S/W inspections
- These involve people examining the source representation with the aim of discovering anomalies and defects
- not require system execution(used before implementation)
- are applied to any representation of the system(requirements, design, configuration data, test data, etc.)
2. Inspection and testing
- They are complementary and not opposing verification techniques
- Both should be used during the V&V process
- Inspections can check conformance with a specification but not conformance with the customer's real requirements
- Inpections cannot check non-functional characteristics such as performance, usability, etc.
3. Program inspections
- Formalised approach to document reviews
- intended explicitly for defect detection (not correction)
- Defects may be logical errors, anomalies in the code
4. Inspection process
- Planning -> Overview ->Individual preparation -> Inspection meeting -> Rework ->Follow-up
5. Inspection procedure
- System overview presented to inspection team
- Code and associated documents are distributed to inspection team in advance
- Inspection takes place and discovered errors are noted
- Modifications are made to repair discovered errors
- Re-inspection may or may not be required
6. Inspection roles
- Author or owner : The programmer responsible for producing the program or document, fixing defects discovered
- Inspector : Find errors, ommisions and inconsistencies in programs and documents
- Reader : Presents the code or document at an inspection meeting
- Scribe : Records the results of the inspection meeting
- Chairman or moderator : Manages the process and reports process result to chief moderator
- Chief moderator : Responsible for inspection process imporvements, checklist updating, standards development, etc.
7. Inspection checklists
- Checklist of common errors should be used to drive the inspection
- prone to depend on programming language
- The 'weaker' the type checking, the larger the checklist
- e.g. Initialisation, constant naming, loop termination, array bounds, etc.
8. Inspection rate
- 500 statements/hour during overview
- 90 ~ 125 statements/hour can be inspected
- Inspecting 500 lines(overview) costs about 4 man/hours effort
- Inspection is therefore an expensive process
9. Automated static analysis
- Static analysers are S/W tools for source text processing
- They parse the program text and try to discover potentially erroneus conditions
- Very effective as an aid to inspections but not a replacement for inspections
10. Fault class that static analysis checks
- data faults, control faults, I/O faults, Interface faults, storage management faults
11. Use of static analysis
- More cost-effective for WEAK TYPING language(like C), less for STRONG TYPE CHECKING language(like JAVA)
'digging IT 인프라 > 소프트웨어공학' 카테고리의 다른 글
| V&V : Software Testing 1/2 (0) | 2008/04/06 |
|---|---|
| V&V : Verification and validation 3/3 (0) | 2008/04/05 |
| V&V : Verification and validation 2/3 - Inspection (0) | 2008/04/05 |
| V&V : Verification and validation 1/3 (2) | 2008/04/05 |
| Design : Object-oriented Design (0) | 2008/04/04 |
| Design : Application Architectures (0) | 2008/03/31 |
