Skip to end of metadata
Go to start of metadata

Related Issues:

http://jira.openfisma.org/browse/OFJ-1677

http://jira.openfisma.org/browse/OFJ-1686

http://jira.openfisma.org/browse/OFJ-1686

http://jira.openfisma.org/browse/OFJ-1642

http://jira.openfisma.org/browse/OFJ-1678

Objectives:

  • Simplify administration by consolidating point of contacts with users, a point of contact will be a user with no access
  • Update the dashboards to provide useful information to points of contact who have no access to other systems
  • Enhance access management by allowing users to have access to other users, this will allow managers access to all subordinates
  • Update the dashboards to allow managers to view the findings of the people they manage
  • Consolidate dashboards, summaries, graphs, into one unified screen for all users
  • Default points of contact should be associated with systems so there is always someone accountable for new findings
  • The point of contact list should be customizable, the administrator should have the ability to disable which users show up in the point of contact list
  • Email alerts should be distributed when individuals are assigned as a point of contact

Research

  • Over 65% of users in the application currently have access to less than 5 systems, as more users of systems are added this number will increase, therefore we need to build dashboards suited to this style of user

Dashboard Mockups

Currently there are multiple dashboards, summaries, and other items on separate screens which is confusing to users, we need to consolidate all graphics and metrics into one dashboard that allows the user to select the view that is most appropriate to their role. This will allow the users to easily explore and click through the various options. 

POC View with No Access

In this scenario, a user is assigned as a point of contact for 33 findings but has been given no access to any information system. Therefore the user cannot see all of the findings associated with the system but the can see the findings for which they have been assigned as the point of contact for. The user has acces to the Findings menu and User preferences menu.

 

Filter Options

User with Access to 1 - 5 Systems

In this scenario, a user is assigned as a point of contact for 33 findings and has access to see four systems along with the points of contact assigned to findings associated with those systems. The user has acces to the Findings menu and User preferences menu.

 

Manager who is responsible for 10+ people and systems

In this scenario, a user is assigned as a point of contact for 33 findings but has been given no access to any information system. Therefore the user cannot see all of the findings associated with the system but the can see the findings for which they have been assigned as the point of contact for. The user has acces to the Findings menu and User preferences menu.

User View

Workflow View

User Management

Labels:
  1. Jan 31, 2012

    If I'm a POC:

    • I want to know what is assigned to me so we should have a screen dedicated to POC or items assigned to the POC
    • Probably not concerned with the workflow status
    • I should be able to quickly prioritize by threat level and be able to click through to the actual items assigned to me

    Screen Layout:

    • POC View
      • If you are a POC you will only see items associated with yourself
      • If you are a manager you will see all people associated with your organization
  2. Feb 14, 2012

    Instead of havinng a link with " more" have a slider to see all information at the same ime

    rolling average should be at least 6 months preferrably a year

    User tab for admin should only show organizational units instead of individual users, this will simplify long term administration

    Use existing H M L colors

    Look into pie chart issue

  3. Mar 15, 2012

    We can't have 4 different Jira tickets for one requirements documents. Please clarify which requirements go with each ticket (i.e. reduce the # of tickets or break up requirements into multiple files).

    As it stands right now, this ticket is not actionable.