Infrastructure Software Vs Application Software. Systems vs Applications Systems can have a user interface but are primarily intended to provide services to other systems and applications. In general the user interacts with application sofwares.
Depending on the application and vendor application infrastructure can include whatever components are necessary to support an application. So since the user will consume the application the application will consume infrastructure resources. In general the user does not interact with system software because it works in the background.
Manage softwareinfrastructure dependencies and design for performance and failure.
The most common examples of infrastructure software are database programs email and other communication software and security applications. Provided by the manufacturers of computing hardware. Yesterday I outlined my current understanding of Application Architecture and the Model-View-Controller MVC approach to content delivery. Providing more self-management capability based on agreed standards could be the answer.