10 pages paper
workprovider1
project.pdf
Project in Software Safety
Com S 515, Spring, 2014
R. Lutz
Deadlines. 1. Project Proposal: Working title and ~200-‐word proposal (similar to a paper’s abstract) describing your project. Due at beginning of class, Thursday, March 25.
2. Paper, due Monday, April 21 (15%).
3. Presentations, as assigned, on April 22, 24, 29, and May 1 (10%), and participation in other students’ presentations. You will give a 20-‐minute presentation to your classmates. The goal is to share, in a way understandable to others, your results. Similarly, attendance at others’ presentation will be required.
Project. The project is an original contribution that you make to software safety. Your project will report on, and/or make progress toward, solving a problem in software system safety that needs to be solved.
The project is an individual effort. The work reported must not have been done previously either by yourself or by others, and your project report may be submitted to iThenticate to check this. There are no page limits, but 10 pages single column is fairly typical.
I won't assign you a topic (learning to select problems to attack is an important part of becoming a researcher), but I’ll try to help you find a problem you’ll enjoy solving. Read Mary Shaw’s mini-‐tutorial, “Writing Good Software Engineering Research Papers” http://www.cs.cmu.edu/~Compose/shaw-‐icse03.pdf
You have two choices:
1. Option 1: Report on your original research in this area. The project is a paper you write on your new, original work that extends current knowledge in some aspect of software safety. This option is often preferred by students already engaged in research as it can be in an area where your thesis research overlaps software safety, dependability, security or high-‐integrity topics. I’ll be happy to help you scope out a right-‐sized piece of work that fits the time you have to do the project if you prefer this option.
2. Option 2: Report on others’ research in this area. The project is an expository paper that describes the state of research others have done on some topic in software safety and provides an insightful account of a remaining open problem. This option may be preferred by students who are in their first year and/or not yet engaged in their own research. Note that should neither quote nor paraphrase extensively from the paper you choose or from other sources. If someone wanted to read this paper, they should find it useful to read your report first in order to better understand this paper.
(a) Email me with your selection of one of the following papers, or talk to me about additional ideas.
Only one student can do each paper, so I’ll give it to the earliest email that I receive after 11:00 March 25. Analysis of Safety-‐Critical Computer Failures in Medical Devices http://www.computer.org/csdl/mags/sp/2013/04/msp2013040014-‐abs.html Fault Injection for Software Certification http://ieeexplore.ieee.org/xpl/articleDetails.jsp?reload=true&arnumber=6517431
Verifying Safety-‐critical interactions in cyber-‐physical systems http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=6531612&url=http%3A%2F%2Fieeexplore.i eee.org%2Fiel7%2F8013%2F6573290%2F06531612.pdf%3Farnumber%3D6531612 A Safety-‐Case Approach For Certifying Adaptive Systems http://www.csl.sri.com/users/rushby/papers/aiaa09.pdf Model-‐Based Quantitative Safety Analysis of Matlab Simulink / Stateflow Models https://kops.ub.uni-‐konstanz.de/xmlui/bitstream/handle/urn:nbn:de:bsz:352-‐ 244936/Beer_244936.pdf?sequence=3
Variability-‐aware safety analysis using delta component fault diagrams http://dl.acm.org/citation.cfm?id=2500721
Experimental Security Analysis of a Modern Automobile http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=5504804&url=http%3A%2F%2Fieeexplore.i eee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D5504804
(b) Paper as paradigm: Classify the paper you’ve selected, according to Shaw’s categories: • What is the type of SE question (See Table 1) addressed by the paper? • What is the type of research (See Table 3) addressed by the paper? • What is the type of validation (see Table 5) addressed by the paper? Paper as source of research question(s): • Describe an open problem discussed in the paper that merits investigation (see Table 1 for some
generic examples). Describe the open problem in enough detail that someone who hasn't taken 515 could readily understand it. You will probably need to read some other papers to understand the open problem enough to explain it this clearly. Don’t assume the reader has prior knowledge of the problem.
• Describe an approach to solving or answering this open problem (see Table 3 for some generic examples). Describe the approach in enough detail that someone who hasn't taken 515 could understand it. You will probably need to read some other, more recent papers to understand the approach enough to explain it clearly and to see what others have done in this regard since the paper appeared.
Grading. The project will be judged on the following criteria:
·∙ Is the project related to & significant for software safety? ·∙ Is there a discussion of related work and why previous efforts to solve the problem are
unsatisfactory? ·∙ Is the proposed approach promising for solving the problem? ·∙ Does the work done here contribute to a solution? ·∙ Is it indicated how the results will be/can be evaluated?
