Non-Functional Features

Be sure to consider all these non-functional aspects of an information system before purchasing.

 

Ease of Use

How easy is it for a new user to figure out basic actions like putting a file in a repository or finding information about a meeting.  Also, how easy is it for an administrator to add a workspace or change a calendar?  Should be such that the vast majority of end user actions and most administrator actions can be figured out without resorting to a manual.



Security

Encryption of passwords, and/or all data transfers between the user and the server, and or all data on the server.

 

Scalability

Number of user accounts on the system, number of users simultaneously using (loading) the system. Numbers of workspaces, file types, documents, etc. Amount of data that will be stored on system - it grows quickly!

 

Maturity – popularity

Length of time application has been available
Availability of off-the-shelf add-in and supplemental products,
Platform popularit, and likelihood that its customer base will grow
Availability and cost of support & maintenance
State of user (customer) communities
Size of developer communities and popularity of Development Tools

 

Extensibility

Ability of the system to be extended or customized with new functions or features from either add-on software products or moving up to the next level system. This capability must be inherent in the system's architecture.

 

Interoperability

Extent of interoperability is related to software system standards to which the system conforms and which enable the system to easily (or not) exchange data with other systems in your or partner company

Does the System need to interoperate (interface) with existing applications in your or partners’ organizations? How about applications that will be coming in the near future?

 

Performance

The application or system should deliver responses to user inputs quickly enough that users do not 'wait' on the sytem, even when system is experiencing a heavy load (lot of users online). Fast responding systems are a minimum requirement to enhance the productivity of users.

 

Cost - software

  • Annual license fee, based on # of users,
  • Plus a flat fee per user
  • Annual maintenance & support fee (can be a percent of license)

Cost - Custom Development

  • None of the packaged applications come ready to be deployed. Initial customization will be driven by the decisions and prioritizations made by the KM Team.
  • A custom or open-source solution will have significant development costs up front, with a likelihood of lower ongoing costs, since annual license payments should be lower or non-existent.
  • Further customization of a proprietary, custom, or OSS application will grow out of identified needs, vetted by the KM Team.
  • Cost of initial development is small relative to the overall resource requirements of the program.

Configurability

Non-technical end users should be able to configure and reconfigure as needed, and initiate new groups at their security level.

 

Content