We are now in design mode. As such we need to take an in-depth look at the users, the security plan, and the design screens.
Step 1 – Define Screens – Before designing the screens, we need to define the screens. These can be simply done by naming the screens and each screen will have a title. So let’s show some examples.
- Landing Page (not logged in)
- User Login Screen
- User Registration Screen
- Home Page (logged in user)
- Data Entry Screen for Item (Edit or Update)
- Display for System Status
Please note that these screens are examples of types of screens that might be in your application. Think about and define all of the screens that will be in the application and how the application will flow to these screens (menu, links from the home page, etc…). The next step is defining the user type. You can have administrators, regular users, editors, proxy users, and more. Give it some real thought.
The last step of defining security is to define who has access to what. Does the admin have access t other data entered by a user? You need to specify this. The table format below will work well and help you define all of this before starting the designs.
| Screen | User | Access Leve |
| Enter profile information | All users | Data entered by the user |
| Enter profile information | Administrator | View all users |
| Every screen | Every User |
Submission Guidelines
The security plan will be added to your documentation. It should contain the full list of screens you expect in your application design, the user list which will likely be user roles, and the full security plan on who can do what.
Previous Week: Week 2 Assignment
Next Week: Week 4 Assignment