Page tree
Skip to end of metadata
Go to start of metadata

Item

Priority

Requirement description

Cat Type

1

1

Tool must function in English

Look & Feel

2

1

There must be an accessible history of submissions, both with regard to the request themselves and also any subsequent comment on the request.

Audit

3

1

The tool must support multiple synchronous users.

Performance

4

1

Full and appropriate user documentation must be available

User Guide Documentation

5

1

To support the distributed working environment it must be possible to undertake all of the above processes from multiple locations and on WWW

Non Functional

6

1

The application should be available 24 hours per day, 7 days per week.

Non Functional

7

1

Failure of the application should result in correction within 24 hours

Non Functional

8

1

The tool should provide sub-second response times (including at the commit stage)

Non Functional

9

1

The technical architecture must be scalable but initially should support adequate numbers of concurrent users both from an 'add new request' perspective and from a 'view existing requests' perspective. Adequate is initially defined as being up to 50 concurrent users

Non Functional

10

1

There must be provision for the long-term maintenance of the application and for management of change requests to improve functionality i.e. from the perspective of the tooling architecture itself and technical support provision.

Non Functional

11

1

The tool should provide the ability to record and track both requests for change and issues.

Workflow, Reporting

12

1 (a manual process may be required to support)

The tool must include submission-checking processes to reduce the possibility of multiple potentially duplicate submissions. Criteria must be established to determine confirmation of duplication.

De- duplicated

13

1 (a manual process may be required to support)

Workflow aspects should be incorporated into the tool so that reports can be generated and workload allocation can be supported.

Workflow, Reports

14

2

The tool must be simple to use and configurable by submitters to allow requests to be submitted with the minimum of effort with instructions included in tutorials for new users

User Guide

15

2

There must be provision to allow administrators to set permissions for making changes to submissions e.g. some fields should be locked and not editable by the submitter

Role Based Access

16

2

It must be possible to add or edit or delete users and user profiles and manage a hierarchy of users

User Management ( IMS – Service)

17

2

It must be possible to group users according to their association with different organisations and groups

User Management ( IMS – Service)

18

2

Workflow aspects should be incorporated into the tool to support the approval process defined in the Content Change Management Process.

Workflow

19

2

The tool should be capable and ready to interface seamlessly with associated tools such as the editing environment and tools, which enable submitters to effectively browse the content of SNOMED CT. This integration should include, but not be limited to the ability to view the current editing environment workflow status within the request submission tool, as requests are being actioned.

Workflow

20

2

Full and appropriate documentation must be available - with regard to application specifications

User Guide Documentation

21

2

There must be a 'Help' facility which must be context-specific (to screen)

User Guide Documentation

22

2

There should be a 'wizard' to guide inexperienced users for the most common tasks.

User Guide Documentation

23

2

Keyboard shortcuts should be available for commonly performed tasks.

Look & Feel

24

2

The tool should provide the option to save unfinished submissions and work plus all configurable features between sessions.

Saving Session State

25

2

The application must conform to national and international accessibility guidelines e.g. W3C

Look & Feel

26

2

The tool must provide an interface to authoring tools to facilitate rapid processing of well-structured high-quality submissions (Accepting fully modeled content)

Workflow, Integration

27

3

Once a user is familiar with the default functions of the tool, they must be able to learn about additional features with ease. E.g. use of interactive documentation and help features.

User Guide

28

3

The tool must have the ability to accept input in multiple languages and translate view into English

Look & Feel (Mulit Lingual)

 

 

 

  • No labels