University of Minnesota
Software Engineering Center
/

You are here

Anitha Murugesan

Anitha Murugesan
Student/Research Assistant
Office Location: 
6-248 Keller Hall
Education: 
Phd - Computer Science (Expected 2015) University of Minnesota

Master of Technology - Computer Science (2004) Vellore Institute of Technology, India

Bachelors of Engineering - Electrical and Electronics, University of Madras, India
Biography: 
Anitha Murugesan received B.E Degree in Electrical and Electronics Engineering from Madras University, India (2002) and M.Tech Degree in Computer Science and Engineering from Vellore Institute of Technology, India (2004). She has worked as a Software Engineer with Honeywell Technology Solutions, India (2004-2010). She is currently pursuing Ph.D in the area of Software Engineering at University of Minnesota. Her research interests are Requirements Engineering and Modeling for cyber physical systems.
Research: 
Critical Systems Requirements and Modeling
Interests: 
Software Engineering; Requirements; Model based development

Recent Publications

Design Considerations for Modeling Modes in Cyber–Physical Systems

Safety critical systems such as cruise control in automotive systems and variable rate bolus in medical device infusion pumps introduce complexity and reduce the flexibility of incremental code modifications. This paper proposes a generic pattern to structure the mode logic such that additions, modifications, and removal of behaviors could be done in a quick and localized fashion without losing model integrity.

Hierarchical Multi-Formalism Proofs of Cyber-Physical Systems

To manage design complexity and provide verification tractability, models of complex cyber-physical systems are typically hierarchically organized into multiple abstraction layers. High-level analysis explores interactions of the system with its physical environment, while embedded software is developed separately based on derived requirements. This separation of lowlevel and high-level analysis also gives hope to scalability, because we are able to use tools that are appropriate for each level. When attempting to perform compositional reasoning in such an

Are We There Yet? Determining the Adequacy of Formalized Requirements and Test Suites

Structural coverage metrics have traditionally categorized code as either covered or uncovered. Recent work presents a stronger notion of coverage, checked coverage, which counts only statements whose execution contributes to an outcome checked by an oracle. While this notion of coverage addresses the adequacy of the oracle, for Model-Based Development of safety critical systems, it is still not enough; we are also interested in how much of the oracle is covered, and whether the values of program variables are masked when the oracle is evaluated.

Pages