Miser-C MISRA-C Compliance Checker

1
Miser-CMISRA-C Compliance Checker

• Ian Biller, Phillippe Dass,
• Bryan Eldridge, Jon Senchyna,
• Tracy Thomas

2
Summary

• Client US Food and Drug Administration
• MISRA-C Compliance Checker
• Intended Use
• Medical Device Industry
• Open Source Community
• System Output

3
Scope

• Parse compilable C code  
• Checkable vs. Uncheckable Rules
• Prioritization of rules
• Open Source Release

4
Context

• Design/Implementation Constraints
• Language restricted to Java
• Restricted to freely available components
• Final product is stand-alone system
• Operating Environment
• Java Virtual Machine (JVM)
• Support Java 1.4 or higher

5
Features

• Check C Source-Code Files for Violations
• XML Output of Violations and Consequences
• XML Error Report
• Configuration of Rules Subset
• Configuration of Acceptable File Extensions

6
Technologies

• ANTLR
• Lexer/parser generator
• Runtime library
• C Grammars
• Java

7
Process Methodology

• Bits and Pieces of Scrum
• Only have 20 weeks for Senior Project
• Time-boxed software development
• 30 day sprints need to be 14 day sprints
• 6 releases planned
• Backlog
• High transparency

8
Process Methodology

• Metrics being tracked used for size of sprint
• If too much time per rule, cut scope of
  successive releases

9
Schedule

• Software release 1 scheduled for end of week 1
• Subsequent software releases every two weeks.
• Implementing backlog will depend on results of
  metrics.

10
Requirements Elicitation

• Four Phases
• Domain Analysis
• Brainstorming
• Interview
• Review
• Low Volatility

11
Requirements

• Documentation
• Software Requirements Specification
• Use-Case Specification
• Product Backlog
• Sprint Backlog

12
Design Process

• Documentation
• Model Diagrams
• Activity Diagram
• Class Diagram
• Modeling Languages
• UML

13
Current State of Design

• Completed
• Activity Diagram
• In Progress
• Class Diagram

14
Task Estimation

• New domain/technology
• Complexity and size
• Track actual time spent
• Update estimates based on metrics

15
Metrics

• Individual Effort
• Team Effort
• Effort per Task
• Number of Rules Met
• Development Time per Rule

16
Risks

• Risk Management
• High-impact Risks
• Research takes too long
• Incorrect estimates
• No suitable C grammar available

17
Versioning Tradeoffs

• Use version 2
• GNU C Grammar written in Version 2
• Less work up front
• Convert to version 3
• ANTLRWorks
• Other ANTLR features
• More testing required

18
Current Project Status

• Completed Tasks
• Website
• Process Methodology
• Project Plan
• Software Requirements Specification
• ANTLR Research
• MISRA Rule Prioritization
• Prototype

19
Current Project Status

• Tasks In Progress
• Grammar Design
• Software Architecture Design

20
Planned for Spring Quarter

• Completion of Architecture Design
• Incremental Releases of Rules
• Testing Plan
• User Documentation
• Configuration Utilities

21
Lessons Learned

• Importance of Methodology
• Transparency greatly increases productivity
• Allow for adequate review time
• Set concrete goals

22
Demo

• (Link to demo)

23
Questions?