When deploying applications in System Center 2012 Configuration Manager (SCCM 2012), requirement rules are often used to determine what deployment type are to be used in the current scenario. But even if the application only have a single deployment type, I still recommend to use requirement rules to reduce the risk of deployment failure. An example could be if a new client OS hasn’t been tested yet, or the lack of resources like disk space or memory.
All applications has their own specific requirements, but most likely you can easy define a minimum requirement that defines a standard for what you test all company applications on. This will help you to reduce the risk of blowing up a client, and make the user unhappy.
Normally I recommend customers to create a baseline for all common deployment scenarios. For example one for Servers and one for Workstations.