Patents by Inventor Sean Sandys

Sean Sandys has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).

  • Patent number: 8312415
    Abstract: Various technologies and techniques are disclosed that allow project requirements to be associated with underlying code elements. A particular software project is analyzed to generate a list of code elements contained in the particular software project. Input is received from a user of a requirements management application to associate one or more project requirements to one or more of the code elements. The project requirements and an association with the one or more code elements are stored in a data store for later retrieval. These associations are used to determine when changes that potentially affect the project requirement are made to the underlying code elements. A software development application is operable to interact with the data store and provide a notice to a user of the software development application that a change to a particular code element of the software project will impact one or more project requirements.
    Type: Grant
    Filed: April 17, 2007
    Date of Patent: November 13, 2012
    Assignee: Microsoft Corporation
    Inventors: Gabriel Marius, Sean Sandys
  • Publication number: 20090144698
    Abstract: An exemplary method includes receiving source code having a plurality of code segments, providing a desired level of quality for the source code, analyzing the source code to assign a complexity measure to each of the plurality of code segments and assigning a level of code coverage to each of the plurality of code segments based at least in part on the desired level of quality and the complexity measures. An exemplary system prioritizes quality improvements to source code based, in part, on a quality assessment. Such a system can improve code quality by assigning higher test coverage levels to modules with higher complexity.
    Type: Application
    Filed: November 29, 2007
    Publication date: June 4, 2009
    Applicant: Microsoft Corporation
    Inventors: Michael C. Fanning, Nachiappan Nagappan, Thomas J. Ball, Sean Sandys
  • Publication number: 20080263504
    Abstract: Various technologies and techniques are disclosed that allow project requirements to be associated with underlying code elements. A particular software project is analyzed to generate a list of code elements contained in the particular software project. Input is received from a user of a requirements management application to associate one or more project requirements to one or more of the code elements. The project requirements and an association with the one or more code elements are stored in a data store for later retrieval. These associations are used to determine when changes that potentially affect the project requirement are made to the underlying code elements. A software development application is operable to interact with the data store and provide a notice to a user of the software development application that a change to a particular code element of the software project will impact one or more project requirements.
    Type: Application
    Filed: April 17, 2007
    Publication date: October 23, 2008
    Applicant: Microsoft Corporation
    Inventors: Gabriel Marius, Sean Sandys
  • Publication number: 20070226690
    Abstract: Upon accessing binary that was generated by a compiler using corresponding source code, a potential reportable problem in the binary is identified. The binary includes a compiler transformed indication that the potential reportable problem is to be suppressed at least under some circumstances. The transformed indication is generated by the compiler using a corresponding untransformed indication in the corresponding source code. The transformed indication is then used to decide that the potential reportable problem should not be reported. Thus, artifacts within the source code itself may ultimately direct what problems are not to be reported on when the corresponding binary is analyzed after the compile phase.
    Type: Application
    Filed: February 8, 2006
    Publication date: September 27, 2007
    Applicant: Microsoft Corporation
    Inventors: Sean Sandys, Jeffrey van Gogh, Michael Fanning, Nicholas Guerrera
  • Publication number: 20070180429
    Abstract: Embodiments provided a formalized set of intermediate analysis contexts that are relevant for analysis checks of target code. Such intermediate analysis context may include, but are not limited to, the development phase of targeted code, the type or state of the targeted code, a source manipulating the targeted code, a purpose for the targeted code, or other development or runtime requirements. Accordingly, embodiments dynamically identify a current analysis context under which targeted code is being developed and can then execute rules based on knowledge of what contexts the rule(s) may apply. More specifically, analysis rules can describe (e.g., via metadata) those context conditions under which a rule can run. Based on such description and the current context, those rules that have been configured to apply to such context conditions can be executed.
    Type: Application
    Filed: January 30, 2006
    Publication date: August 2, 2007
    Applicant: Microsoft Corporation
    Inventors: Jeffrey Gogh, Michael Fanning, Sean Sandys