77
CONFIDENTIAL
Page 39 of 220
NamLITS-NCA User Requirements Specification
Tinka Consultancy & Investments cc
ID
Requirement
Priority
Software
Release
B57. Multi-select Users for modification – Allow access to User modification functions
described in this section for the results of a search for one or more Users meeting
criteria, so that multiple Users meeting criteria can be modified without performing
multiple searches.
Nice to
Have
Release 1
B58. View User Details – Display User details, including all User information by clicking
on any of the rows returned in the search results.
Allow modification of User information from here.
Must
Have
Release 1
B59. View User Audit Trail – Display User Audit Trail details, including but not limited
to:
! Login date & time
! Logout date & time
! Function used & associated record accessed date & time
! Associated records captured or modified
Details will be confirmed in a Detailed Requirements Specification to be developed by the
Contracted Consultant.
Allow the Audit Trail to be filtered between a defined date range.
Must
Have
Release 2
B60. Print User Details – Print User details, including all User information and User
Audit Information.
Nice to
Have
Release 1
CAPTURE ACCESS CONTROL PROFILES
ID
Requirement
Priority
Software
Release
B61. Capture Access Control Profiles – Allow the definition of multiple Access Control
Profiles that each determine what Users who are allocated that Access Control
Profile are able to perform in the system.
Must
Have
Release 1
B62. Access Control Profiles define low level Functions that can be performed –
Each Access Control Profile should determine each of the functions that can be
accessed. Functions should be defined at the lowest possible level (i.e. at least the
level of the requirements defined in this document) and not simply at the highest
level ‘menu option’ level. This is a lower level that is currently supported in the
Existing NamLITS system.
Note that this must not be implemented through a large number of low level menu
options. Multiple system functions may be accomplished in one screen – access to
relevant tabs, buttons and areas of the screen should be determined by the function
associated with the tab, button or area and the users access rights as defined in their
linked Access Control Profile.
For example, it should be possible to define an Access Control Profile which allows
access to view Establishment Information and perform a Livestock Observation, but
prevents Establishment Information from being updated, even though all of these
functions are accessed from the same Menu option.
Must
Have
Release 1
B63. Access Control Profiles define which Establishment Types can be created and
maintained – Each Access Control Profile should determine which Establishment
Types can be added and maintained.
For example, it should be possible to define an Access Control Profile which allows
access to create or modify Establishments which are Farms or Grazing Areas but
Must
Have
Release 1
How to C#: Basic SDK Concept of XDoc.PDF for .NET example, you may easily create, load, combine, and split PDF file(s), and add, create, insert, delete, re-order, copy, paste, cut, rotate, and save PDF page(s
how to rotate one page in a pdf file; rotate pdf page permanently
81
CONFIDENTIAL
Page 40 of 220
NamLITS-NCA User Requirements Specification
Tinka Consultancy & Investments cc
ID
Requirement
Priority
Software
Release
does not allow access to create or modify Establishments which are Auction Agents
or Abattoirs.
B64. Access Control Profiles define which Traditional Authority Types can be
created and maintained – Each Access Control Profile should determine which
Traditional Authority Types can be added and maintained.
Must
Have
Release 1
MAINTAIN ACCESS CONTROL PROFILES
ID
Requirement
Priority
Software
Release
B65. Maintain Access Control Profiles – Allow the modification of Access Control
Profiles.
Must
Have
Release 1
B66. Modify low level Functions that can be performed – Allow the low level
Functions that can be performed to be added or removed from a given Access
Control Profile
Must
Have
Release 1
B67. Modify Establishment Types that can be created and maintained – Allow the
Establishment Types that can be created or modified to be added or removed from a
given Access Control Profile.
Must
Have
Release 1
B68. Modify Traditional Authority Types can be created and maintained – Allow the
Traditional Authority Types that can be created or modified to be added or removed
from a given Access Control Profile.
Must
Have
Release 1
QUERY AND VIEW ACCESS CONTROL PROFILES
ID
Requirement
Priority
Software
Release
B69. Search for individual Access Control Profiles – Identify individual Users by a
number of means, including but not limited to:
! Access Control Profile
Search criteria will be confirmed in a Detailed Requirements Specification to be developed by the
Contracted Consultant.
Must
Have
Release 1
B70. Search for one or more Access Control Profiles meeting criteria – Identify and
list one or more of Access Control Profiles which meet criteria, including but not
limited to:
! Function that can be performed
! Function that can not be performed
! Establishment Type that can be created or modified
! Traditional Authority that can be created or modified
Allow one, more or all of the above criteria be used simultaneously to identify Access
Control Profiles.
Search criteria will be confirmed in a Detailed Requirements Specification to be developed by the
Contracted Consultant.
Nice to
Have
Release 1
B71. Display number of Access Control Profiles meeting Criteria – Show the total
number of Access Control Profiles that met the search criteria.
Nice to
Have
Release 1
B72. Display summary information for each Access Control Profile meeting criteria Nice to
Release 1
58
CONFIDENTIAL
Page 41 of 220
NamLITS-NCA User Requirements Specification
Tinka Consultancy & Investments cc
ID
Requirement
Priority
Software
Release
– Display pertinent summary information for each Access Control Profile that meets
the search criteria. Access Control Profile fields should be displayed in columns, with
a row for each of the Access Control Profiles that met the search criteria.
Paginate rows so as to not exceed a user defined number of rows on each page, but
to ensure that all returned rows can be accessed.
Have
B73. Export summary Access Control Profile information to Excel – Allow the
displayed Access Control Profile columns and rows to be exported to Microsoft
Excel format.
Nice to
Have
Release 1
B74. Export summary Access Control Profile information to .PDF – Allow the
displayed Access Control Profile columns and rows to be exported to Adobe PDF
format.
Nice to
Have
Release 2
B75. Export summary Access Control Profile information to Email – Allow the
displayed Access Control Profile columns and rows to be exported to an agreed
Email word processor format.
Nice to
Have
Release 2
B76. Print summary Access Control Profile information– Allow the displayed Access
Control Profile columns and rows to be printed.
Should
Have
Release 1
B77. Multi-select Access Control Profiles for modification – Allow access to Access
Control Profile modification functions described in this section for the results of a
search for one or more Access Control Profiles meeting criteria, so that multiple
Access Control Profiles meeting criteria can be modified without performing multiple
searches.
Nice to
Have
Release 1
B78. View Access Control Details – Display Access Control Profile details, including all
Access Control Profile information by clicking on any of the rows returned in the
search results.
Allow modification of Access Control information from here.
Must
Have
Release 1
B79. Print Access Control Details – Print Access Control Profile details, including all
Access Control Profile information.
Should
Have
Release 1
67
CONFIDENTIAL
Page 42 of 220
NamLITS-NCA User Requirements Specification
Tinka Consultancy & Investments cc
C. MANAGE TRADITIONAL AUTHORITIES
The user requirements for this major function are as follows:
CAPTURE TRADITIONAL AUTHORITY DETAILS
ID
Requirement
Priority
Software
Release
C1. Capture Traditional Authorities – Capture details of the each of Traditional
Authority that is a stakeholder in Livestock Identification and Tracking.
Must
Have
Release 1
C2. Restrict ability to Capture Traditional Authorities based on Office Hierarchy –
Only the following users are able to capture Traditional Authorities:
! Users linked to Office Level 1 (NamLITS HQ) with an Access Profile that
allows Capture of Traditional Authorities
! User linked to Office Level 2 (NamLITS North HQ or NamLITS South HQ)
with an Access Profile that allows Capture of Traditional Authorities
Users linked to Office Level 3 (SVO) with an Access Profile that allows Capture of
Traditional Authorities can only capture Traditional Authorities that are linked to
their own SVO Jurisdiction.
Users linked to Office Level 4 may not capture any Traditional Authorities even if
they are linked to an Access Profile that allows this function.
Should
Have
Release 1
C3. Traditional Authority Hierarchy & Type – There is a three level hierarchy of
Traditional Authorities:
! Level 1 – Recognised Chief (responsible for a large area)
! Level 2 – Senior Headman (responsible for multiple villages)
! Level 3 – Headman (typically responsible for 1-3 villages)
The system should support the capture of this hierarchical relationship between
Traditional Authorities.
Traditional Authority Type is synonymous with the level in the hierarchy.
These values will be confirmed in a Detailed Requirements Specification to be developed by the
Contracted Consultant.
Must
Have
Release 1
C4. Traditional Authority Status – Support Traditional Authority Status’s including, but
not limited to:
! Active – Traditional Authority is active and is issuing Traditional Authority
Movement Permits
! Suspended – Traditional Authority is temporarily suspended from issuing
Traditional Authority Movement Permits
! Inactive – Traditional Authority is not active in Livestock Identification and
Traceability.
A Traditional Authority may only have an Inactive status if no Establishments are
linked to it.
These values will be confirmed in a Detailed Requirements Specification to be developed by the
Contracted Consultant.
Must
Have
Release 1
C5. Traditional Authority Unique IDs – Support a unique Identifier for each
Traditional Authority.
Must
Have
Release 1
C6. Traditional Authority GPS Points – Support the geographical definition of
Should
Release 1
73
CONFIDENTIAL
Page 43 of 220
NamLITS-NCA User Requirements Specification
Tinka Consultancy & Investments cc
ID
Requirement
Priority
Software
Release
Traditional Authorities as points (using a longitude and latitude GPS co-ordinate pair) Have
C7. Traditional Authority Details – Capture Traditional Authority details including, but
not limited to:
! Traditional Authority Name
! Traditional Authority Status
! Traditional Authority Unique ID
! Traditional Authority GPS Points
! Parent Traditional Authority (only the Recognized Chiefs should have no parent)
! Traditional Authority Type
! Traditional Authority Physical Address
! Traditional Authority Postal Address
! Traditional Authority Mobile Number
! Traditional Authority Telephone Number
! Traditional Authority Fax Number
! Traditional Authority Email Address
! Traditional Authority Region
! Traditional Authority Magisterial District
! Traditional Authority Surveyor General Registration Division
! Traditional Authority Constituency
These details will be confirmed in a Detailed Requirements Specification to be developed by the
Contracted Consultant.
Must
Have
Release 1
C8. Link Traditional Authority to one or more SVO Jurisdictions – Allow the
Traditional Authority to be linked to one or more Level 3 Office (State Veterinary
Office), where that Traditional Authority is serviced by the SVO Jurisdiction.
Must
Have
Release 1
C9. Link Traditional Authority to Establishments – Allow Traditional Authorities to
be linked to one or more Establishments, where the Traditional Authority has
authority over Livestock Keepers that use the Establishment.
Must
Have
Release 1
C10.
Propagate Authority up the Traditional Authority Hierarchy – Where a given
Traditional Authority is linked to an Establishment to indicate authority over
Livestock Keepers that use that Establishment, then the parent Traditional Authority
and the parent of the parent Traditional Authority (if applicable) are also deemed to
have authority over that Livestock Keepers that use that Establishment.
Should
Have
Release 1
MAINTAIN TRADITIONAL AUTHORITY DETAILS
ID
Requirement
Priority
Software
Release
C11.
Modify Traditional Authority Details – Allow the modification of all information
captured against a Traditional Authority.
Must
Have
Release 1
C12.
Restrict ability to Modify Traditional Authorities based on Office Hierarchy –
Only the following users are able to modify Traditional Authorities:
! Users linked to Office Level 1 (NamLITS HQ) with an Access Profile that
Should
Have
Release 1
77
CONFIDENTIAL
Page 44 of 220
NamLITS-NCA User Requirements Specification
Tinka Consultancy & Investments cc
ID
Requirement
Priority
Software
Release
allows Modification of Traditional Authorities
! User linked to Office Level 2 (NamLITS North HG or NamLITS South HQ)
with an Access Profile that allows Modification of Traditional Authorities
Users linked to Office Level 3 (SVO) with an Access Profile that allows Modification
of Traditional Authorities can only modify Traditional Authorities that are linked to
their own SVO Jurisdiction.
Users linked to Office Level 4 may not modify any Traditional Authorities even if
they are linked to an Access Profile that allows this function.
C13.
Modify Traditional Authority Status – Allow Traditional Authority Status to be
changed:
A Traditional Authority may only have an Inactive status if no Establishments are
linked to it.
Must
Have
Release 1
C14.
Capture Traditional Authority Suspension Reason – When changing the status of
a Traditional Authority to Suspended, capture details including, but not limited to:
! Traditional Authority Suspension Reason, including but not limited to:
o Suspended from serving
o Previous deceased not yet replaced
o Other values will be confirmed in a Detailed Requirements Specification to be
developed by the Contracted Consultant.
! User performing Suspension
! Date & Time of Suspension
These details will be confirmed in a Detailed Requirements Specification to be developed by the
Contracted Consultant.
Should
Have
Release 2
C15.
Modify SVO Jurisdictions – Allow the modification of the SVO Jurisdictions that
service the Traditional Authority.
Must
Have
Release 2
C16.
Modify Traditional Authority Hierarchy – Allow the Traditional Authority
Hierarchy to be modified by changing the administering parent for any given
Traditional Authority.
For example it should be possible to “promote” a Senior Headman to a Recognised
Chief or “demote” a Senior Headman to a Headman, etc.
Must
Have
Release 1
C17.
Modify Traditional Authority-Establishment Links – Allow the addition and
deletion of Traditional Authority-Establishment Links.
Must
Have
Release 1
QUERY &VIEW TRADITIONAL AUTHORITIES
ID
Requirement
Priority
Software
Release
C18.
Search for individual Traditional Authorities – Identify individual Traditional
Authorities by a number of means including, but not limited to:
! Traditional Authority Unique ID
! Child Traditional Authority (i.e. find the Traditional Authority which is the level
above a given Traditional Authority)
! Establishment which the Traditional Authority has authority over
Must
Have
Release 1
Documents you may be interested
Documents you may be interested
