Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

what documentation should be done from security perspective in Blue print

Former Member

‎08-13-2009 1:23 PM

0 Kudos

We're implementing Enterprise Compensation Management in HCM module. Would like to know what documentation should be done from security perspective in Blue print phase

2 REPLIES 2

Former Member

‎08-13-2009 5:17 PM

0 Kudos

What do you have already?

You need to think about stuff like your strategy & approach, technical build standards (SU24, naming etc), your detailed design docs, user management principles, compliance & control touch points with security etc.

Former Member

‎08-13-2009 9:58 PM

0 Kudos

There is a lot of "interface stuff" which you will need to consider. For example there are typically a lot of horridly complex legacy "systems".

Often the policies and even legislation is so complex and constantly changing and riddled with exceptions that it is difficult to code it (with customzing extentions to the programs) and manage changes that way.

This opens a myriad of security considerations during the design phase. They are not all bad, but there are some traps.

Cheers,

Julius