> ![](media/image1.png){width="3.5590277777777777in" height="1.45625in"}

Simplified Non-competing Award Process Scope Document

Version 1.0 -- 01/01/02

Prepared for:

National Institutes of Health

Office of Extramural Research

Extramural Research Administration

Bethesda Maryland

Prepared by:

Micro Technologies Plus, Inc.

5002 Camelback Lane

Frederick, Maryland 21703

Revision History

  ------------ --------------- ----------------------------------- -----------------
  ***Date***   ***Version***   ***Description of Change***         ***Author***

  12/06/01     .8              Draft                               R. Reifsnider
  ------------ --------------- ----------------------------------- -----------------

[1 Introduction 5](#introduction)

[1.1 Purpose 5](#purpose)

[1.2 Scope 5](#scope)

[1.3 Definitions, Acronyms and Abbreviations
6](#definitions-acronyms-and-abbreviations)

[1.4 References 6](#references)

[2 Positioning 6](#positioning)

[2.1 Business Opportunity/Scope 6](#business-opportunityscope)

[3 Stakeholder and User Descriptions
7](#stakeholder-and-user-descriptions)

[3.1 Stakeholder Summary 7](#stakeholder-summary)

[3.2 User Summary 8](#user-summary)

[3.3 User Environment 9](#user-environment)

[3.4 Stakeholder Profiles 9](#stakeholder-profiles)

[3.5 User Profiles 10](#user-profiles)

[3.5.1 Extramural User Profiles 10](#extramural-user-profiles)

[4 Product Overview 12](#product-overview)

[4.1 Product Perspective 12](#product-perspective)

[4.2 Summary of Capabilities 13](#summary-of-capabilities)

[4.3 Assumptions and Dependencies 14](#assumptions-and-dependencies)

[4.4 Cost and Pricing 14](#cost-and-pricing)

[4.5 Licensing and Installation 14](#licensing-and-installation)

[5 Product Features 14](#product-features)

[5.1 IMPAC 2 (IM2) Features 14](#impac-2-im2-features)

[5.2 System (SYS) Features 14](#system-sys-features)

[5.3 Security (SEC) Features 14](#security-sec-features)

[5.4 Professional Profile (PPF) Features
15](#professional-profile-ppf-features)

[5.5 Institutional Profile (IPF) Features
15](#institutional-profile-ipf-features)

[5.6 SNAP Features (SNAP) Features 15](#snap-features-snap-features)

[5.7 Audit (AUD) Features 16](#audit-aud-features)

[5.8 Status (STATUS) Features 17](#status-status-features)

[6 Constraints 17](#constraints)

[7 Quality Ranges 17](#quality-ranges)

[8 Precedence and Priority 17](#precedence-and-priority)

[9 Other Product Requirements 18](#other-product-requirements)

[10 Documentation Requirements 18](#documentation-requirements)

[10.1 User Manual 18](#user-manual)

[10.2 On-line Help 18](#on-line-help)

[10.3 Installation Guides, Configuration, Read Me File
18](#installation-guides-configuration-read-me-file)

[11 Appendix A -- Organizational Hierarchy
19](#appendix-a-organizational-hierarchy)

[Figure 1: Commons 12](#__RefHeading___Toc534505495)

# Introduction

In the spirit of the Federal government's reinvention initiatives, the
NIH developed a streamlined process for the submission of information
necessary to receive a non- competing award. Before the streamlining, a
progress report and four financial documents were required for each
grant budget year. This streamlining action

eliminated, where nonessential, two of those financial documents that
were part of the non-competing continuation application kit (PHS 2590):
a budget for the next budget period and an estimated report of
expenditures for the current budget period. The basic principle of SNAP
is that at the time of the competing award, the Grants Management
Officer negotiates the direct costs for the entire competitive segment,
thus eliminating the need to engage in annual direct cost negotiations.
As part of that negotiation, NIH staff

assures that proposed costs are allowable, allocable, reasonable, and
necessary for the project. Since the budget is negotiated for all years
of the competitive segment at the time of the initial competing award,
requirements for documentation are

streamlined in that only an annual programmatic Progress Report, the
Federal Cash Transactions Report, and a final Financial Status Report
are required to enable NIH staff to monitor the scientific and financial
aspects of the project. Within the Progress Report, the grantee
specifies (a) whether there has been any change in the other support of
key personnel since the last reporting period, (b) whether there will be
a significant change in the level of effort for key personnel in the
next budget period, and (c) if it is anticipated that as estimated
unobligated balance will be greater than 25% of the current year's total
budget.

This document describes the requirements of a Simplified Non-competing
Award Process (SNAP) entry and reporting system that will serve the
needs of the NIH staff and the grantees. Since the SNAP process serves
both grantees and NIH staff, this system will integrate both the Commons
and IMPAC II systems using new web based technologies to integrate both
communities of users.

## Purpose

The purpose of this Scope document is to collect, analyze, and define
high-level needs and features of the SNAP system. It focuses on the
capabilities needed by the stakeholders and the target users and why
these needs exist. The details of how the SNAP system fulfills these
needs are detailed in the Use Cases and Supplementary Specification.

## Scope

The NIH eRA Commons is a mission-critical application that functions as
an electronic mall where the extramural community can conduct
grant-related business with the NIH. In effect, the Commons serves as a
front end for the NIH Enterprise System, IMPAC II. The NIH eRA
Management has decided to reengineer its existing enterprise system and
the Commons using the Java 2 Enterprise Edition (J2EE) specification.
The SNAP Version 2.0 will be implemented as a Component of the Commons
Version 2.0.

Current IMPAC II applications will need to incorporate the SNAP data
into their applications and business processes.

## Definitions, Acronyms and Abbreviations

AO Administrative Official

Asst Assistant to PI

BOG Board of Governors

BPR Business Process Reengineering

CRUD Create, Update, Delete

CWG Commons Working Group

DEIS Division of Extramural Information Systems

ERA Electronic Research Administration

FAQ Frequently Asked Questions

GM Grants Management

J2EE Java 2 Enterprise Edition

IMPAC Information for Management, Planning, Analysis, and Coordination

IT Information Technology

NGA Notice of Grant Award

NIH National Institutes of Health

OER Office of Extramural Research

PDF Portable Document Format

PI Principal Investigator

RUP Rational Unified Process

SC Steering Committee

SNAP Simplified Non-competing Award Process

SO Signing Official

WIP Work in Progress

## References

-   [ERA Commons Supplementary Specification]{.underline}, Logicon
    Federal Data, 7/2/2001

-   [ERA J2EE Commons Scope Document]{.underline}, Logicon Federal Data,
    07/31/2001

-   [eRA Project Software Development Cost and Schedule Estimating
    Guidelines]{.underline}, 11/6/2001, Soza

-   [e-SNAP Business Plan]{.underline}, 11/23/2001, Gerald Stuck

-   [Non-Competing Grant Process (PHS 2590)]{.underline}, 05/01

# Positioning

## Business Opportunity/Scope

In Fiscal Year 1995, the NIH implemented SNAP (Simplified Non-competing
Award Process). Non-competing awards represent the largest percentage of
the grants workload for NIH program and grants management staff. The
e-SNAP module of the NIH Commons started as a pilot in July 1999 and
concluded in March 2001. Since that time, further recommendations have
been made for improving the SNAP business process. The initial
recommendations resulted from extensive discussions at the May 2001
meeting of the Commons Working Group among CWG members, the NIH Commons
Group Advocate, and NIH grants policy representatives. The CWG
recommendations were then vetted through the eRA Program Users Group
(ePUG), the Grants Management Advisory Committee (GMAC), and the Project
Officers/Program Officials Forum (POPOF). After recommendations from the
NIH committees were incorporated, the [Consensus Proposed Changes to
SNAP Business
Process](http://era.nih.gov/docs/consensus_proposed_changes_to_snap_business_process.htm)
matrix received final approval at the July 18 meeting of the Extramural
Program Management Committee (EPMC). With the agreement on these
business process improvements, it is appropriate to begin full
development and deployment of E-SNAP as part of the eRA application
portfolio.

# Stakeholder and User Descriptions

## Stakeholder Summary

This section presents a summary list of all stakeholders, including what
they represent with respect to the development of SNAP, and the role
they play in the development.

  --------------------- ------------------ -------------------------------
  **Name**              **Represents**     **Role**

  NIH eRA Management    NIH                Liaison to NIH Steering
                                           Committee (SC) and Board of
                                           Governors (BOG); ensures that
                                           project activities are
                                           coordinated across ICs, and
                                           that the project stays within
                                           budget and schedule.

  Coordinator of        Development        Ensure that the requirements
  Commons Activities                       correctly articulate user
                                           expectations; development is
                                           completed on time and within
                                           budget, and that the delivered
                                           system meets all requirements.

  Division of           Development        Ensure that the requirements
  Extramural                               correctly articulate user
  Information Systems                      expectations; development is
  (DEIS)                                   completed on time and within
                                           budget, and that the delivered
                                           system meets all requirements.

  Commons Working Group Extramural         Ensure that the project meets
  (CWG)                 Community          the expectations of the
                                           extramural user community.

  Group Advocates       Business Area      Ensure that the project meets
                                           the expectations of the user
                                           community

  NIH Office of         NIH Extramural     Ensure that the project meets
  Extramural Research   Research Policy    the expectations of the NIH
  (OER)                                    grants community.

  NIH User Support      User Support       Ensure that the project has
                                           adequate help desk and user
                                           support resources.

  NIH Grants Management NIH business       Controls NIH Internal processes
                        processes          and systems related to Grants
                                           management.
  --------------------- ------------------ -------------------------------

## User Summary

This section presents a summary list of all users of the Commons SNAP
subsystem, including their description and stakeholder representation.

  ------------------ --------------------------------- -------------------
  **Name**           **Description**                   **Stakeholder**

  SO                 Signing Official                  CWG

  AO                 Administrative Official           CWG

  PI                 Principal Investigator            CWG

  Asst               Assistant to PI                   CWG
  ------------------ --------------------------------- -------------------

## User Environment

The SNAP user community is divided into two users groups: extramural
users and NIH users. For purposes of this document, it is assumed that
all users have access to personal computers and the Internet.

The Grantee User Community is a large, sophisticated, university-based
community that demands the flexibility and response time that an on-line
grant award mechanism can provide. The users are educated, computer
literate, and in most cases use personal computers in their homes and
offices.

## Stakeholder Profiles

This section describes in detail the stakeholders' profiles, in terms of
their roles, responsibilities, success criteria, and involvement in the
development effort.

  --------------------------------------------------------------------------------------------------
  **Stakeholder**   **Representative**   **Profile**            
  ----------------- -------------------- ---------------------- ------------------------------------
  NIH eRA           J.J. McGowan, PhD.   **Description**        Manages all IT resources and
  Management                                                    priorities.

                                         **Type**               Project Manager.

                                         **Responsibilities**   Responsible for all aspects of eRA:
                                                                Liaison with SC and BOG: ensures
                                                                that Project activities are
                                                                coordinated across ICs; ensures that
                                                                the project stays within budget and
                                                                schedule

                                         **Success Criteria**   Delivered system meets the
                                                                expectations of the user community,
                                                                and Project completion is within
                                                                approved budget and schedule.

                                         **Involvement**        Project guidance and review.

                                         **Deliverables**       ERA system

                                         **Comments**           None.

  DEIS              Jim Cain             **Description**        Manages IT resources

                                         **Type**               Implementation Manager

                                         **Responsibilities**   Manages development team; monitors
                                                                cost and schedule

                                         **Success Criteria**   Project completion within approved
                                                                budget and schedule; delivered
                                                                system meets the expectations of the
                                                                user community.

                                         **Involvement**        Project guidance and review.

                                         **Deliverables**       ERA System

                                         **Comments**           None.

  NIH Commons       Jerry Stuck          **Description**        Manages IT resources
  Management                                                    

                                         **Type**               Implementation Manager

                                         **Responsibilities**   Manages development team; monitors
                                                                cost and schedule

                                         **Success Criteria**   Project completion within approved
                                                                budget and schedule; delivered
                                                                system meets the expectations of the
                                                                user community.

                                         **Involvement**        Project guidance and review.

                                         **Deliverables**       ERA System

                                         **Comments**           None.

  Commons Working   George Stone, PhD.   **Description**        Policy and IT representation from
  Group                                                         the extramural user community.

                                         **Type**               Subject matter experts and expert
                                                                users.

                                         **Responsibilities**   Communicates needs of the extramural
                                                                community to the SNAP project team.
                                                                Validates project requirements.

                                         **Success Criteria**   Project meets the expectations of
                                                                the extramural community.

                                         **Involvement**        Provides feedback on direction and
                                                                scope of project efforts. Serves as
                                                                Beta testers.

                                         **Deliverables**       None.

                                         **Comments**           None.

  Group Advocates   George Stone, PhD,   **Description**        Representatives of the user
                    Marcia Hahn                                 community

                                         **Type**               Subject matter experts

                                         **Responsibilities**   Provides guidance to the development
                                                                team with respect to scope,
                                                                usability, and planning. Coordinates
                                                                requirements with the user
                                                                community.

                                         **Success Criteria**   Project meets the expectations of
                                                                the user community.

                                         **Involvement**        Reviews artifacts. Provides feedback
                                                                from user community

                                         **Deliverables**       Review Record Artifacts

                                         **Comments**           None.

  NIH User Support  Tim Twomey           **Description**        Provides support to the user
                                                                communities

                                         **Type**               User Support Staff.

                                         **Responsibilities**   Provides user support and help desk
                                                                resources for the project.

                                         **Success Criteria**   SNAP system is fully integrated with
                                                                other business processes supported
                                                                by the User Support Branch.

                                         **Involvement**        Review Record Artifacts

                                         **Deliverables**       None.

                                         **Comments**           None.
  --------------------------------------------------------------------------------------------------

## User Profiles

This section details the profile of each SNAP user in terms of its
roles, responsibilities, success criteria, and involvement in the SNAP
system development effort.

### Extramural User Profiles

+----------+---------+-----------+-----------------------------------+
| **User** | **Repr  | **        |                                   |
|          | esented | Profile** |                                   |
|          | By**    |           |                                   |
|          |         |           |                                   |
|          | **(     |           |                                   |
|          | Stakeho |           |                                   |
|          | lder)** |           |                                   |
+----------+---------+-----------+-----------------------------------+
| A        | CWG     | **Desc    | Assistant to Grant Applicant      |
| ssistant |         | ription** |                                   |
| (Asst)   |         |           |                                   |
+----------+---------+-----------+-----------------------------------+
|          |         | **Type**  | The Asst is typically a           |
|          |         |           | university employee who is        |
|          |         |           | familiar with the requirements of |
|          |         |           | the grant proposal to be          |
|          |         |           | submitted.                        |
+----------+---------+-----------+-----------------------------------+
|          |         | **        | Assisting the PI in completing    |
|          |         | Responsib | the grant proposal application to |
|          |         | ilities** | be submitted to NIH.              |
+----------+---------+-----------+-----------------------------------+
|          |         | **Success | System provides the capability to |
|          |         | C         | edit and save a grant proposal.   |
|          |         | riteria** |                                   |
+----------+---------+-----------+-----------------------------------+
|          |         | **Invo    | Assistant.                        |
|          |         | lvement** |                                   |
+----------+---------+-----------+-----------------------------------+
|          |         | **Deliv   | None.                             |
|          |         | erables** |                                   |
+----------+---------+-----------+-----------------------------------+
|          |         | **C       | None.                             |
|          |         | omments** |                                   |
+----------+---------+-----------+-----------------------------------+
| P        | CWG     | **Desc    | Grant applicant.                  |
| rincipal |         | ription** |                                   |
| Inve     |         |           |                                   |
| stigator |         |           |                                   |
| (PI)     |         |           |                                   |
+----------+---------+-----------+-----------------------------------+
|          |         | **Type**  | The Principal Investigator is     |
|          |         |           | typically a university faculty    |
|          |         |           | member who is highly qualified in |
|          |         |           | the area of research for which    |
|          |         |           | the grant application is          |
|          |         |           | submitted.                        |
+----------+---------+-----------+-----------------------------------+
|          |         | **        | Person at the extramural          |
|          |         | Responsib | institution who is responsible    |
|          |         | ilities** | for the scientific or technical   |
|          |         |           | aspects of the grant and for      |
|          |         |           | day-to-day management of the      |
|          |         |           | project or program.               |
+----------+---------+-----------+-----------------------------------+
|          |         | **Success | System provides the capability to |
|          |         | C         | successfully submit SNAPs.        |
|          |         | riteria** |                                   |
+----------+---------+-----------+-----------------------------------+
|          |         | **Invo    | Product reviewer. Pilot           |
|          |         | lvement** | participant.                      |
+----------+---------+-----------+-----------------------------------+
|          |         | **Deliv   | None.                             |
|          |         | erables** |                                   |
+----------+---------+-----------+-----------------------------------+
|          |         | **C       | None.                             |
|          |         | omments** |                                   |
+----------+---------+-----------+-----------------------------------+
| Admini   | CWG     | **Desc    | Business Official at the          |
| strative |         | ription** | extramural organization.          |
| Official |         |           |                                   |
| (AO)     |         |           |                                   |
+----------+---------+-----------+-----------------------------------+
|          |         | **Type**  | User with authority to monitor    |
|          |         |           | submitted grant applications for  |
|          |         |           | the external organization.        |
+----------+---------+-----------+-----------------------------------+
|          |         | **        | Reviews all grant applications    |
|          |         | Responsib | submitted on behalf of their      |
|          |         | ilities** | organization.                     |
+----------+---------+-----------+-----------------------------------+
|          |         | **Success | The system provides the           |
|          |         | C         | capability to review and signoff  |
|          |         | riteria** | on SNAPs submitted to NIH.        |
+----------+---------+-----------+-----------------------------------+
|          |         | **Invo    | Product reviewer. Pilot           |
|          |         | lvement** | participant.                      |
+----------+---------+-----------+-----------------------------------+
|          |         | **Deliv   | None.                             |
|          |         | erables** |                                   |
+----------+---------+-----------+-----------------------------------+
|          |         | **C       | None.                             |
|          |         | omments** |                                   |
+----------+---------+-----------+-----------------------------------+
| Signing  | CWG     | **Desc    | Business Official                 |
| Official |         | ription** |                                   |
| (SO)     |         |           |                                   |
+----------+---------+-----------+-----------------------------------+
|          |         | **Type**  | User with authority to provide    |
|          |         |           | signature approval of the         |
|          |         |           | submissions, and monitor activity |
|          |         |           | for the extramural organization   |
+----------+---------+-----------+-----------------------------------+
|          |         | **        | Reviews and authorizes all        |
|          |         | Responsib | submissions on behalf of their    |
|          |         | ilities** | institution                       |
+----------+---------+-----------+-----------------------------------+
|          |         | **Success | System provides the capability to |
|          |         | C         | review and signoff on SNAPs       |
|          |         | riteria** | submitted to NIH                  |
+----------+---------+-----------+-----------------------------------+
|          |         | **Invo    | Product reviewer. Pilot           |
|          |         | lvement** | Participant.                      |
+----------+---------+-----------+-----------------------------------+
|          |         | **Deliv   | None                              |
|          |         | erables** |                                   |
+----------+---------+-----------+-----------------------------------+
|          |         | **C       | None                              |
|          |         | omments** |                                   |
+----------+---------+-----------+-----------------------------------+

# Product Overview

This section provides a high-level view of the SNAP Version 2.0
capabilities, interfaces to extramural users, Federal agency users, the
NIH eRA Commons system and the IMPAC II system.

## Product Perspective

The NIH eRA Commons is an application that serves as a front end for the
NIH Enterprise System, IMPAC II. The Commons provides a modular
framework and infrastructure for building application-related components
associated with specific types of grant processing. The SNAP Version 2.0
will be implemented as a component of the Commons Version 2.0.

![](media/image2.png)

[]{#__RefHeading___Toc534505495 .anchor}Figure 1: Commons

## Summary of Capabilities

  -------------------------------- --------------------------------------
  **Grantee Customer Benefit**     **Supporting Features**

  Electronic submission of SNAP s  SNAP WWW interface for entry of SNAP
                                   information and submission to NIH

  Receives an electronic tickler   The IMPAC 2 system will send an e-mail
                                   notification of Progress Report 45
                                   days prior to due date

  PI can delegate updating of PPF  Commons will allow PIs to delegate the
                                   PPF update to an authorized user

  Electronic routing for           SNAPs can be routed to authorizing
  extramural review                officials for review and approval

  Streamlining Benefits of BPR     CWG has authorized SNAP modifications
                                   to further simplify the SNAP

  Authorized user can streamline   An authorized user can delegate
  submission authorizations        'release' and 'submit' capabilities
  -------------------------------- --------------------------------------

## Assumptions and Dependencies

-   All Commons Version 2.0 infrastructure development efforts,
    including Account Administration and Profile Administration, must
    have been completed successfully before the SNAP "Construction
    Phase" (as defined by the Rational Unified Process - RUP) can begin.

-   All SNAP BPR efforts are complete.

## Cost and Pricing

SNAP costs will be derived using the "eRA Project Software Development
Cost and Schedule Estimating Guidelines" developed by Soza, Inc.,
11/6/2001.

## Licensing and Installation

There are no licensing requirements with respect to the extramural
users, as their interface is Web-based.

# Product Features

SNAP is a component or subsystem of the Commons Version 2.0. All system,
security, audit, and profile features of the Commons Version 2.0 as
defined in the "ERA J2EE Commons Scope Document," dated 07/31/2001 apply
to SNAP as well. Any system, security, audit, and profile features
defined herein shall be considered SNAP-specific enhancements to the
Commons Version 2.0 features.

## IMPAC 2 (IM2) Features

FEAT 1.1 The IMPAC2 system shall create a SNAP shell and populate with
data from the previous submission. The IMPAC2 system shall set the
Status of the SNAP shell to "NEW" (or something that the Commons shall
interpret as NEW).

FEAT1.2 The IMPAC2 system shall generate an e-mail notification to the
extramural official 120 days prior to the budget start date of the SNAP.

FEAT1.3 The IMPAC2 system shall replicate the SNAP shell to the Commons
120 days prior to the budget start date of the SNAP.

## System (SYS) Features

FEAT2.1 The Commons shall provide a 'demo' site instance of the SNAP
process. This SNAP demo capability shall be fully functional with the
exception that the capability to 'submit' the data to NIH shall be
disabled.

FEAT2.2 The Commons shall provide a capability to purge dated SNAP
materials from the Commons.

## Security (SEC) Features

FEAT3.1 An authorized SNAP user shall be an authorized user of the
Commons.

## Professional Profile (PPF) Features

FEAT4.1 The system shall provide the capability for a PI to authorize
another user to edit their PPF.

(\*This is an outcome of the BPR and represents a change from the
current process.)

## Institutional Profile (IPF) Features

FEAT5.1\* The Commons system shall provide a capability for an
authorized user to view or edit the Assurance and Certifications, and
the date that each requirement was assured.

FEAT5.2\* The Commons system shall require that all institutional
Assurances and Certifications contained in the IPF indicate compliance
before accepting a proposal submission.

FEAT5.3\* The Commons system shall provide the capability for an
authorized user to define their organizational structure within the IPF.
The organizational structure shall identify hierarchical components as
defined in Appendix A.

FEAT5.4\* The Commons system shall provide the capability for an
authorized user to modify the Department name, Division name, and School
name.

(\*This is an outcome of the BPR and represents a change from the
current process.)

## SNAP Features (SNAP) Features

The features identified below shall apply to both the demo and
operational components unless otherwise noted.

FEAT6.1 The SNAP Component shall include on-line help with
context-sensitive FAQs.

FEAT6.2 The SNAP Component shall provide a capability for an authorized
user to edit a SNAP prior to submission to NIH. All updates made by the
user shall be visually highlighted when displayed or printed. The system
shall allow only one user at a time to open a proposal with edit
privileges.

FEAT6.3 The SNAP Component shall have a capability to validate the SNAP
data.

FEAT6.4\* The SNAP Component shall provide a capability for a SNAP to be
released (routed) through an extramural review process consisting of an
AO and SO prior to submission to NIH.

FEAT6.5 The SNAP Component shall notify the PI via e-mail if the
submission is rejected by an extramural reviewer.

FEAT6.6 The SNAP Operational Component shall notify the PI via e-mail
when the data are submitted to NIH by an extramural reviewer.

FEAT6.7\* With respect to Research Accomplishments and Other Significant
Changes, the SNAP Component shall provide a separate input data field
for Science Highlights and other Significant Changes.

FEAT6.8\* With respect to Citations, the SNAP Component shall provide a
capability for the authorized user to provide a link to on-line
journals. The SNAP component shall also provide a capability for the
authorized user to import the Citations from the PPF.

FEAT6.9\* The SNAP Component shall provide a capability for a PI to
grant another user read/write access to a specific SNAP.

FEAT6.10 The SNAP Component shall provide a capability for an authorized
user to include a Progress Report and Research Accomplishments that are
formatted in PDF.

FEAT6.11 If an authorized user modifies the PPF information within SNAP,
the SNAP Component shall provide a capability for the user to update the
PPF accordingly.

FEAT6.12 The SNAP Component shall provide a capability for an authorize
user to create a printer-friendly copy of the SNAP.

FEAT6.13 The SNAP Component shall provide a capability for an authorized
user to save a SNAP as a Work in Progress (WIP).

FEAT6.14 The SNAP Operational Component shall provide a capability for
an authorized user to 'withdrawal' a SNAP, if it has been less than 60
minutes since its submission to NIH.

FEAT6.15\* The Commons system shall provide the capability for an
authorized user to specify that a PI is permitted to submit a SNAP
without further review by extramural administrators. In this case, the
SNAP Component shall send an e-mail to the AO and SO that identifies the
SNAP that was submitted to NIH.

FEAT6.16 The SNAP Operational Component shall provide a capability for
an authorized user to submit the proposal electronically to NIH.

(\*This is an outcome of the BPR and represents a change from the
current SNAP process.)

## Audit (AUD) Features

FEAT7.2 The Commons shall audit the following SNAP activities:

-   arrival of a NEW SNAP proposal shell

-   'edit' access to proposal

-   proposal release for extramural review

-   proposal submission to NIH

-   proposal withdrawal

-   delegation of access to a proposal

-   delegation of proposal release

-   delegation of proposal submission

-   SNAP deletion by system.

FEAT7.2 If a user is delegated edit PPF privileges, all auditable events
shall record the userID of the person accessing the PPF.

## Status (STATUS) Features

FEAT8.1 The Status subsystem shall display the number of days remaining
before budget start date of the SNAP.

# Constraints

The SNAP subsystem shall be developed using a Rational Unified Process
(RUP) that has been tailored to NIH's specific information dissemination
needs and project-level signoffs.

The current users of the system have certain expectations of the system,
and the Group Advocates best understands these expectations. Therefore
any modification to the SNAP functionality (including new functionality)
shall require the approval of the Group Advocate.

# Quality Ranges

SNAP is a component or subsystem of the Commons Version 2.0. All Quality
Ranges of the Commons Version 2.0 as defined in the "ERA J2EE Commons
Scope Document," dated 07/31/2001, and the "ERA Commons Supplementary
Specification," date 07/02/2001, apply to SNAP.

# Precedence and Priority

This section defines the priority of the system features. The priorities
associated with each category are described in the following table.

  ---------------------- ------------------------------------------------
  **Feature Category**   **Precedence and Priority**

  Security               These features are critical to maintain the
                         operation of the system. They must be
                         implemented in conjunction with all other
                         features.

  Audit Features         The features are critical to maintain security
                         and data integrity

  Professional Profile   These features are key to the extramural user
  Features               community.

  SNAP Features          The features are critical to the functionality
                         of this effort.

  Institutional Profiles This feature is required for e-SNAP.

  System                 The feature will be useful for mitigating the
                         learning curve for Extramural Community.

  Status                 This feature will be useful to members to the
                         extramural user community
  ---------------------- ------------------------------------------------

# Other Product Requirements

SNAP is a component or subsystem of the Commons Version 2.0. All Other
Product Requirements as defined in the "ERA J2EE Commons Scope
Document," dated 07/31/2001, and the "ERA Commons Supplementary
Specification," dated 7/2/2001, apply to SNAP.

# Documentation Requirements

SNAP is a component or subsystem of the Commons Version 2.0. All
Documentation Requirements as defined in the "ERA J2EE Commons Scope
Document," dated 07/31/2001 apply to SNAP. SNAP-specific documentation
requirements are itemized below.

## User Manual

None required.

## On-line Help

Context-sensitive on-line help shall be available to the user for each
system function. Each context-sensitive on-line help topic shall link to
the relevant on-line Frequently Asked Questions (FAQ).

## Installation Guides, Configuration, Read Me File

Release Notes

# Appendix A -- Organizational Hierarchy

![](media/image3.wmf)

#   {#section .unnumbered}