When password is expired, users are shown the screen below:This text does not provide the user with a clear image of the case at hand, and how to solve it:It is mentioned that the password is expired, the password needs to change, and the password is forgotten. User is asked to change the password ‘below’, while ‘below’ no fields are shown to change the password. As this function will be used often by Zeeman users (password expires everey 2 months for some 8000 users), optimization is needed. My suggestion is to change the text, or make this adaptable to customer wishes.
When the ‘forgot password’ function is used in the webGUI, a token as shown below is sent to the user by mail. This token is probably very safe, but also difficult to copy in handwriting (correctly), and the safety it provides is does not reflect the functions Zeeman provides to most users. Therefore, an option to configure a shorter/simpler token would be handy. I was thinking of a 4 digit numeric code, but a 6 digit code (provided by the forgot password function in the mobile GUI) would also be ok.
A business process diagram can be quite large, a function to zoom in and out would be helpful in maintaining overview while also enabling a view on details.
Currently, users are informed of the relative strength of the chosen password (f.e. ‘Strength 4/5’). However, they are not informed what strength is required, and how they can achieve this strength. It would be helpful to users if they are shown which features they need to add to their password to achieve the required strength (f.e.: add 2 symbols to your password, add 2 numbers, ...)
For Zeeman, a ‘first visit’ functionality is created on the loginpage. This functionality is also available in the paperplane menu (top-left button in the SF, this menu is used to logout or change password). The ‘first visit’ function is unnecessary in that menu, and might confuse users (see screenprints below) I understand that it is impossible to differentiate between the loginpage and paperplane-menu. Can this be made possible? Or is there another way to show this ‘first visit’ function on the loginpage, and not showing it where it is not needed?
At some point, Zeeman asks employees to enter their birth date. This can typed or selected in the calender. By default, the current day is selected when opening the calender. This is even so when part of the birth date is already typed in. In this case it would be nice if the selected date is some point in the past (f.e. 30 years ago, 1-1-1990), this would minimise the scrolling needed for all employees and therefore make the calender more useful.
When the ‘forgot password’ function is used in the webGUI, a token as shown below is sent to the user by mail. This token is probably very safe, but also difficult to copy in handwriting (correctly), and the safety it provides is does not reflect the functions Zeeman provides to most users. Is it possible to configure a shorter/simpler token? I was thinking of a 4 digit numeric code, but a 6 digit code (provided by the forgot password function in the mobile GUI) would also be ok.
Currently, it is possible to enter password indefinitely without inactivating the account. It appears to me that this is a safety ‘gap’, as someone with false intentions has lots of opportunities to try and hack an account. Automatically inactivating an account after a number of wrongly entered passwords in a period of time (number and time-span should be configurable) would be a nice solution. This should be accompanied by a safe manner for the account owner to de-activate his account. For Zeeman employees this could be realised by sending an email with password reset code to the mailadress that is linked to the inactivated account.
At Zeeman, employees will use their personellnumber as username. As people might forget that this is the case, we would like to provide a hint (f.e. mouse-over on the ‘username’ field) to help our users remember this. This adds to the user-friendliness at login, and reduces (unnecessary) use of the ‘Forgot username’ function
The review → business processes menu provides an option to provide feedback on business processes and requirements (in the stakeholder view). For busines processes this is called ‘Discussion’, for requirements this is called ‘Comment’. To my opinion, the function is the same. Can you explain the reason for using different terms?
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.