Đang chuẩn bị liên kết để tải về tài liệu:
Lecture Formal methods in software engineering - Lecture 32

Không đóng trình duyệt đến khi xuất hiện nút TẢI XUỐNG Tải xuống

Lecture Formal methods in software engineering - Lecture 32: Adding formal methods to a project. This chapter presents the following content: Adding formal methods to a project, best use of formal methods, management considerations, technical considerations, types of analysis/formal methods, level of rigor for formal methods,. | Formal Methods in Software Engineering Adding Formal Methods to a Project Lecture 32 Adding Formal Methods to a Project Remember using formal methods is not an all or nothing process The level of rigor used should be tailored to fit the specific project with respect to system criticality level budget schedule technical environments Best Use of Formal Methods New system components adaptive or corrective maintenance Poorly understood requirements perfective maintenance Highly critical system components preventative maintenance Management Considerations - part 1 Project staff expertise Formal Methods Expert (seeks to match applications with appropriate methods, tools, and techniques) Project Domain Expert (evaluates candidate application and identifies the best to experiment with) Project scale best to only try applying formal methods on 1 or 2 components the first time out can be viewed as a training exercise demonstrate value of formal methods with low risk Management Considerations - part 2 Project training use existing staff with formal methods expertise provide in-house, hands-on training with formal methods languages and support tools outside experts provide training and advice in early project stages Process integration strategy few changes needed if requirements analysis procedure are well-defined formal methods can complement existing process steps Management Considerations - part 3 Project guidelines and standards writing formal specifications requires guidelines similar to those found in existing configuration management procedures coding style guidelines documentation standards Guidelines will have the greatest impact on the project if they are in place before the project or training begins Technical Considerations - part 1 Type of application applications with greater complexity will benefit more from formal methods use than simple applications logic and discrete math applications benefit more than numerical applications Size of | Formal Methods in Software Engineering Adding Formal Methods to a Project Lecture 32 Adding Formal Methods to a Project Remember using formal methods is not an all or nothing process The level of rigor used should be tailored to fit the specific project with respect to system criticality level budget schedule technical environments Best Use of Formal Methods New system components adaptive or corrective maintenance Poorly understood requirements perfective maintenance Highly critical system components preventative maintenance Management Considerations - part 1 Project staff expertise Formal Methods Expert (seeks to match applications with appropriate methods, tools, and techniques) Project Domain Expert (evaluates candidate application and identifies the best to experiment with) Project scale best to only try applying formal methods on 1 or 2 components the first time out can be viewed as a training exercise demonstrate value of formal methods with low risk Management