
<script type="text/javascript">
<!--
document.write('<div id="oa_widget"></div>');
document.write('<script type="text/javascript" src="https://www.openaire.eu/index.php?option=com_openaire&view=widget&format=raw&projectId=undefined&type=result"></script>');
-->
</script>Security is a contentious issue for Web applications, with developers and administrators sharing overall responsibility, while still focusing on their specialist abilities. As a developer, you need to consider tasks such as user authentication, authorization, and impersonation; you also need to produce a model that the administrators can use when the application goes live. Among other duties, administrators will be responsible for configuring Web server security, applying security patches and fixes, and assigning users to the different groups, roles, or access levels that you’ve defined. As you can imagine, these two sets of responsibilities are closely interwoven; so, it makes sense for both teams to work together when planning and designing security features, and subsequently, for them to maintain a good rapport as the application is developed and deployed.
| citations This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).  | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.  | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).  | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.  | Average | 
