Application Level Software vs. Enterprise Level Software

While the left side should be valued; the right side should
be added to reach to higher level of maturity and realize the
efficiency, effectiveness, predictability and consistency of every project.

Application Level Software	Enterprise Level Software
Business rules are being internalized and imbed in the code	Business rules are externalized and can be deployed to and shared by multiple application building blocks
Emphasize implementability	Emphasize extensibility and reusability
Solve the problems at hands within a project	Solve the problems at hands within the context of enterprise
Often modulize code at function,class, and component levels	Modulize code to reach to service and building blocks levels
Tend to not to respect the boundaries	Follow the service and building blocks boundaries
Only the project related domainas it domain background	The entire business segment as its domain background
Focus on code syntax optimization	Focus on service/component boundary setting
Pieces on hands are the big picture	Emphasize how smaller pieces fit into the big picture
Often treat every project as its own	Treat every project as an integration project
Loosely following industry standards such as LDAP forsecurity repository	Empasize using industry standards
The barriers among transactional, operational, integrational,analytical, and batch modules are high	The barriers among transactional, operational, integrational, analytical, and batch modules are broken
Often use the project name as boundary setter, for example, com.companyname.projectname	Use business architecture blocks as the boundary setter, for example, com.companyname. businesssegmentname. businessrule
Skillset tend to be generic	The right mixture of specialists and generalists at building blocks level
Often take a project view	Take portfolio view
Often dive into nitty-gritty line of code optimization	Emphasize the code organization
Starting from project specific requirement	Starting from business architecture
The lines among business rules, business processes, business events, business data, business contents, business intelligence and etc. are blurred	The lines among those are intentionally defined and well integrated using controlled ways
On time delivery, under budget and work as being intended with less bugs for that project are main successful indicators	Scalable, extensible and evolvable with ease and costing less are added