12.11.2014 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>NASIS</strong> <strong>Requirements</strong> <strong>Definition</strong> <strong>Document</strong> (RDD)<br />

Version 1.0<br />

17 February 2006<br />

Section 2: System, Technical, and Operational <strong>Requirements</strong><br />

2.1 General Architectural <strong>Requirements</strong><br />

In order to: 1) minimize system support needs, system cost, 2) enhance security and the user experience,<br />

and 3) position the system for future technological developments, <strong>NASIS</strong> will embody these<br />

characteristics and employ the best <strong>of</strong> available and proven technology, to include:<br />

• Centralized, Web-based system<br />

• Web browser-based user interface<br />

• Windows-based user interface<br />

• Open standards and open source solutions<br />

• School Interoperability Framework (SIF) compliance<br />

• Open database connectivity (ODBC) compliance<br />

• Online analytical processing (OLAP) tools<br />

• Data warehouse for student and school information<br />

• Data analysis tools for multi-dimensional data analyses and reports<br />

• Messaging for staff, students, and parents<br />

<strong>NASIS</strong> may be delivered as either a government owned and operated system, a government owned and<br />

contractor operated system, or as a service from an application service provider (ASP). The high level<br />

architectural components are:<br />

• Core <strong>NASIS</strong> Platform. BIA and the Department <strong>of</strong> the Interior have standardized on Micros<strong>of</strong>t<br />

and Oracle s<strong>of</strong>tware products and Intel/AMD-based server platforms, therefore the core <strong>NASIS</strong><br />

components should be consistent with these standards. Should the government select an ASP<br />

solution, the government is neutral on the platform as long as other requirements can be satisfied.<br />

• Network Service. Users will communicate with the core <strong>NASIS</strong> platform over TCP/IP based<br />

networks. Schools employ the Educational Native American Network -2 (ENAN-2) for external<br />

connectivity, including access to the Internet.<br />

• End-user Platform. The end-user will access <strong>NASIS</strong> via a Web browser. <strong>NASIS</strong> will<br />

accommodate multiple browsers, but as a minimum will support Micros<strong>of</strong>t Internet Explorer.<br />

<strong>NASIS</strong> will support two primary functional needs. Implicit in fulfilling these requirements is a data<br />

warehouse with OLAP tools. More information on functional needs may be found in subsequent sections<br />

<strong>of</strong> this document and in the appendices.<br />

• Federal and State Reporting. The foremost requirement <strong>of</strong> <strong>NASIS</strong> is to support the reporting<br />

requirements levied on OIEP by the US Department <strong>of</strong> Education and the State education<br />

agencies. OIEP is distinct from many other school systems in that it operates in 23 states and<br />

must exchange data with the states, including the required reports. Because vendors design<br />

school information systems to operate at the school level up to the state level, there do not appear<br />

to be solutions on the market that can readily accommodate OIEP’s needs, although the technical<br />

feasibility exists.<br />

9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!