(NASIS) Requirements Definition Document - Bureau of Indian ...

NASIS Requirements Definition Document (RDD)
Version 1.0
17 February 2006
• Student and School Services. There are many student/school information system solutions and
many of these are generally consistent with OIEP requirements.
2.2 Environment
2.2.1 Equipment Environment
• The BIA and Department of the Interior have standardized on Intel/AMD servers, so the NASIS
processing environment will be consistent with those standards.
• The core NASIS components will be located together in an industry best practices data center
facility.
• The data center will be secured to ensure only authorized individuals are allowed access to the
facility.
• The data center critical operational parameters will be monitored on a 24x7 basis.
• The majority of the OIEP schools and student population are in Arizona and New Mexico. South
and North Dakota are next largest student concentrations, but are substantially smaller the New
Mexico and Arizona areas. Physical proximity to the user population is advantageous.
2.2.2 Software Environment
• BIA and the Department of the Interior have standardized on Microsoft and Oracle software
products, therefore the core NASIS components will be consistent with these standards.
• Users will access NASIS using a Web browser
• NASIS will employ XML compliant data structures.
2.3 Performance
2.3.1 Response Time
Assuming negligible network delays, screens, when selected, will display with minimal delay and will not
be an encumbrance to performing functions. Reports will be sent to the chosen printer within a timeframe
that is measured in seconds as opposed to minutes. Response time for queries and updates should be
almost immediate. The system should be able to meet user needs for handling transactions.
2.3.2 System Availability
The system must be available to users 24 hours a day, seven days a week, year round. Additionally, a separate
Service Level Agreement (SLA) must be established that will clarify the System Availability, Recoverability,
and Performance. This will be developed in coordination with the provider and OIEP.
Routine system maintenance and upgrades must be scheduled in advance and proper notice must be given
before a scheduled system outage. Proper notice is defined as one week.
2.3.3 Data Currency
Once data is entered, the information shall be available immediately.
10