By Laurence Hart – Many organizations are adopting the content services approach to solving enterprise content management challenges. When organizations implement content services properly, business requirements are embedded in the back end and user experience evolves independently from the platform. This division of labor makes both users and business owners happy.

However, developers also need to consider nonfunctional requirements — such as security, auditing, reporting and accessibility — early in the development process in order for content services to be successful.

Have you ever gone to release an application and had to wait because a security scan fails? Nobody ran the scan until the team was almost done building the application, because it would be pointless to scan an application for security holes when it isn’t complete. You wouldn’t test the security of a half-built house, would you?

Moreover, the security team wants to scan a relatively complete version of the final application to save time. The problem with this approach is that waiting to address security requirements late in the process makes them harder to fix. Read more: