Abstract: Disclosed herein are glass pharmaceutical vials having sidewalls of reduced thickness. In embodiments, the glass pharmaceutical vial may include a glass body comprising a sidewall enclosing an interior volume. An outer diameter D of the glass body is equal to a diameter d1 of a glass vial of size X as defined by ISO 8362-1, wherein X is one of 2R, 3R, 4R, 6R, 8R, 10R, 15R, 20R, 25R, 30R, 50R, and 100R as defined by ISO 8362-1. However, the sidewall of the glass pharmaceutical vial comprises an average wall thickness Ti that is less than or equal to 0.85*s1, wherein s1 is a wall thickness of the glass vial of size X as defined by ISO 8362-1 and X is one of 2R, 3R, 4R, 6R, 8R, 10R, 15R, 20R, 25R, 30R, 50R, and 100R as defined by ISO 8362-1.

Abstract: Disclosed herein are glass pharmaceutical vials having sidewalls of reduced thickness. In embodiments, the glass pharmaceutical vial may include a glass body comprising a sidewall enclosing an interior volume. An outer diameter D of the glass body is equal to a diameter d1 of a glass vial of size X as defined by ISO 8362-1, wherein X is one of 2R, 3R, 4R, 6R, 8R, 10R, 15R, 20R, 25R, 30R, 50R, and 100R as defined by ISO 8362-1. However, the sidewall of the glass pharmaceutical vial comprises an average wall thickness Ti that is less than or equal to 0.85*s1, wherein s1 is a wall thickness of the glass vial of size X as defined by ISO 8362-1 and X is one of 2R, 3R, 4R, 6R, 8R, 10R, 15R, 20R, 25R, 30R, 50R, and 100R as defined by ISO 8362-1.

Abstract: A project analysis system and method is described to allow for automated generation of scalable bootable applications and downloadable applications, preferably in connection with an integrated development environment (IDE). The project analysis system and method includes facilities for automatically identifying and including software components in application development projects based on symbol dependencies and component dependencies. The project analysis system and method also includes facilities for automatically identifying and removing software components in application development projects where no symbol dependencies or component dependencies exist, thereby removing unused code. A graphical user interface is provided for user display and selection of includable and excludable components.

Abstract: A method and system are disclosed for autoscaling, i.e., determining if an application program or an operating system within a system project uses components that are not already included within the system project (“needed components”). A user of a project facility is shown these needed components and allowed to select the components that are to be added to the system project. Autoscaling may also determine the components that are not used by the application program or the operating system (“deadwood components”) but still present in the system project. These deadwood components are displayed to the user and the user is allowed to remove them from the system project.

Abstract: A method and system are disclosed for autoscaling, i.e., determining if an application program or an operating system within a system project uses components that are not already included within the system project (“needed components”). A user of a project facility is shown these needed components and allowed to select the components that are to be added to the system project. Autoscaling may also determine the components that are not used by the application program or the operating system (“deadwood components”) but still present in the system project. These deadwood components are displayed to the user and the user is allowed to remove them from the system project.

Abstract: A project analysis system and method is described to allow for automated generation of scalable bootable applications and downloadable applications, preferably in connection with an integrated development environment (IDE). The project analysis system and method includes facilities for automatically identifying and including software components in application development projects based on symbol dependencies and component dependencies. The project analysis system and method also includes facilities for automatically identifying and removing software components in application development projects where no symbol dependencies or component dependencies exist, thereby removing unused code. A graphical user interface is provided for user display and selection of includable and excludable components.