# US 2013/0159962 A1 · Identifying application resources through implicit application models

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0159962 A1
- Document ID: US20130159962A1
- Status: Published application
- Kind: A1
- Application number: 13/327,480
- Filed: 2011-12-15
- Published: 2013-06-20
- Earliest claimed: 2011-12-15
- Assignees: Microsoft Corporation
- Inventors: Jeremy Dunker; Eric Jewart; Derrick Timothy Isoka
- Web page: https://patentgrep.com/patent/US20130159962A1

## CPC

- G06F 8/75: Structural analysis for program understanding
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 11/3089: {Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents (software debugging using additional hardware using a specific debug interface G06F11/3656; performance evaluation by tracing or monitoring G06F11/3466)}
- G06F 8/61: Installation
- G06F 2201/865: Monitoring of software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Determining a discrete application boundary. A method includes identifying one or more initial components of an application. The method further includes identifying statically and/or dynamically related components of the one or more initial components of the application. Identifying statically related components and identifying dynamically related components is performed iteratively. The method further includes identifying a discrete boundary for the application based on statically related components and dynamically related components.

## Claims

### Claim 1

In a computing environment, a method of determining a discrete application boundary, the method comprising:
identifying one or more initial components of an application;
identifying statically related components of the one or more initial components of the application;
identifying dynamically related components of the one or more initial components of the application;
wherein identifying statically related components and identifying dynamically related components is performed iteratively; and
identifying a discrete boundary for the application based on the one or more initial components, the statically related components and the dynamically related components.

### Claim 2 (depends on 1)

The method of claim 1, wherein the discrete boundary defines components needed for a functional instance of the application.

### Claim 3 (depends on 1)

The method of claim 1, further comprising creating a redistributable package based on the discrete boundary.

### Claim 4 (depends on 1)

The method of claim 1, further comprising validating at least one of the application's correctness or completeness based on components within the discrete boundary.

### Claim 5 (depends on 1)

The method of claim 1, wherein identifying statically related components comprises examining well known extension points of an operating system or a component of an operating system.

### Claim 6 (depends on 1)

The method of claim 1, wherein identifying statically related components comprises examining well-known relationships between resources.

### Claim 7 (depends on 1)

The method of claim 1 wherein identifying dynamically related components comprises monitoring resource accesses of identified application components at runtime.

### Claim 8 (depends on 1)

The method of claim 1 further comprises blacklisting identified components to exclude components from an application boundary.

### Claim 9 (depends on 1)

The method of claim 1 wherein identifying one or more initial components of an application comprises receiving user input.

### Claim 10 (depends on 1)

The method of claim 1 wherein identifying a discrete boundary comprises receiving user input.

### Claim 11

One or more computer readable media comprising computer executable instructions that when executed by one or more processors perform the following:
identifying one or more initial components of an application;
identifying statically related components of the one or more initial components of the application;
identifying dynamically related components of the one or more initial components of the application;
wherein identifying statically related components and identifying dynamically related components is performed iteratively; and
identifying a discrete boundary for the application based on the one or more initial components, the statically related components and the dynamically related components.

### Claim 12 (depends on 10)

The one or more computer readable media of claim 10, wherein the discrete boundary defines components needed for a functional instance of the application.

### Claim 13 (depends on 10)

The one or more computer readable media of claim 10, further comprising creating a redistributable package based on the discrete boundary.

### Claim 14 (depends on 10)

The one or more computer readable media of claim 10, further comprising validating at least one of the application's correctness or completeness based on components within the discrete boundary.

### Claim 15 (depends on 10)

The one or more computer readable media of claim 10, wherein identifying dynamically related components comprises monitoring resource accesses of identified application components at runtime.

### Claim 16 (depends on 10)

The one or more computer readable media of claim 10, further comprises blacklisting identified components to exclude components from an application boundary.

### Claim 17 (depends on 10)

The one or more computer readable media of claim 10, wherein identifying one or more initial components of an application comprises receiving user input.

### Claim 18 (depends on 10)

The one or more computer readable media of claim 10, wherein identifying a discrete boundary comprises receiving user input.

### Claim 19

In a computing environment, a computing system configured to determine a complete representation of components of an application, the system comprising:
an application model generator;
a static identification module coupled to the application model generator, the static identification module configured to identifying statically related components to one or more initially identified components of the application by examining at least one of installer or uninstall data, well known extension points of an operating system, or well known extension points of server registration;
a monitoring layer coupled to the application model generator, the monitoring layer configured to identifying dynamically related components of the one or more initial components of the application by intercepting resource requests from an application;
wherein the application model generator is configured to cause identifying statically related components and identifying dynamically related components to be performed iteratively; and
wherein the application model generator is configured to identify a complete representation of components of an application based on the initially identified components, the statically related components and the dynamically related components.

### Claim 20 (depends on 19)

The computing system of claim 19, further comprising a blacklist coupled to the application model generator, the blacklist identifying components that should not be included in the complete representation of components of an application.
