ITS - Intelligent Transportation Systems Report ITS Home Page

ICMS General Requirements

3.1 Non-Functional Needs

Following the functional needs identified in the ConOp development process, the I-880 stakeholders also developed a set of non-functional needs for the ICMS.

Table 3.1 Functional Requirements

  1. NN-01 Need for interagency cooperation, communication and coordination
    1. NN-01-01 Needs for interagency cooperation agreement
    2. NN-01-02 Needs for interagency coordination and communication protocols
  2. NN-02 Need for a durable and modifiable system
    1. NN-02-01 Needs for a durable system
    2. NN-02-02 Needs for a modifiable system
  3. NN-03 Need for intuitive and easy to use designs
    1. NN-03-01 Needs for an intuitive user interface for operators
    2. NN-03-02 Needs for an intuitive user interface for travelers
  4. NN-04 Need for a reliable system
  5. NN-05 Need for a maintainable system
  6. NN-06 Need for policy and regulations for data sharing
  7. NN-07 Need for interface standards and protocols
  8. NN-08 Need for a quality information processing infrastructure
    1. NN-08-01 Performance
    2. NN-08-02 Function 7/24
    3. NN-08-03 Function 99.99% of the time
    4. NN-08-04 Process 50 concurrent operator commands
    5. NN-08-05 Process user authentication within 2 seconds
    6. NN-08-06 Provide user information storage for up to 500 users
    7. NN-08-07 Provide organization information storage up to 500 organizations
    8. NN-08-08 Provide data acquisition configuration capability for up to 500 data sources
    9. NN-08-09 Provide data publishing configuration capability for up to 500 data subscribers
  9. NN-09 Security
    1. NN-09-01 Operations center firewall
    2. NN-09-02 Only allow authorized access to data and system
    3. NN-09-03 Each ICM subsystem manages ITS own security as per security requirement of the host ITS system
  10. NN-10 Documentation
    1. NN-10-01 Maintenance documentation
    2. NN-10-02 Operator manuals
    3. NN-10-03 Administration Manuals
  11. NN-11 Training
    1. NN-11-01 Maintenance training
    2. NN-11-02 Operator training

These non-functional needs form the basis for a set of non-functional requirements which impose constraints on the design or implementation.

3.2 Non-Functional Requirements

According to the needs above and based on the technical requirements of the existing ITS systems, the I-880 ICM team developed a set of non functional requirements, documented in Table 3.2, to accompany the functional, interface and data requirements to be discussed in the next few sections. In this table, RN refers to non-functional requirements.

Table 3.2 Non-Functional Requirements
ID Requirement Traceability Comment Criticality
RN-01 The ICMS shall be available 24 hours a day, 7 days a week. NN-04   H
RN-02 The ICMS subsystems shall be designed to last 10 years. NN-02-01   H
RN-03 The ICMS subsystems and components shall be operational between -40C and 70C outdoors and between 0C and 50C indoors NN-04   H
RN-04 The ICMS shall have a MTBF.

RN-04-01 The ICMS shall have a MTBF greater than 180 days for major system failures.

RN-04-02 The ICMS shall have a MTBF greater than 60 days for minor system failures.		 NN-04   H
RN-05 The major hardware ICMS shall be replaceable through plug and play process. NN-05   H
RN-06 The software components of ICMS shall be maintainable with minimum down time. Typical maintenance down time shall not exceed 30 minutes. NN-02-02   H
RN-07 The Human-Machine Interface of ICMS shall be designed in such a way that training for new institutional user will not exceed 48 hours. NN-03-01   H
RN-07 The Human-Machine Interface of ICMS shall be designed in such a way that no training is needed for travelers in order to understand and use the system. NN-03-02   H
RN-08 The ICMS shall function 99.99% of the time (i.e., at most 60 seconds of down time per week). NN08-02   H
RN-09 The ICMS shall process 50 concurrent operator commands. NN-08-04   H
RN-10 The ICMS shall process user authentication within 2 seconds after user log in information is received. NN-08-05   H
RN-11 The ICMS shall provide user information storage up to 2Mb for 5000 users. NN-08-06   H
RN-12 The ICMS shall provide organization information storage up to 20Mb for 500 organizations. NN-08-07   H
RN-13 The ICMS shall provide data acquisition configuration capability for up to 500 data sources. NN-08-08   H
RN-14 The ICMS shall provide data publishing configuration capability for up to 500 data subscribers. NN-08-09   H
RN-15 The ICMS operations center shall have firewall for security purposes. NN-09-01   H
RN-16 The ICMS operations center shall require authentication of users NN-09-03   H
RN-17 The ICMS subsystems shall follow security requirements of the host ITS system NN-09-03   H
RN-18 The ICMS shall have documentation for maintenance. NN-10-01   H
RN-19 The ICMS shall have operator manuals. NN-10-02   H
RN-20 The ICMS shall have administration manuals. NN-10-03   H
RN-21 The ICMS shall have features allowing on-line training for maintenance personnel NN-11-01   H
RN-22 The ICMS shall have features allowing on-line training for system operators. NN-11-02   H
RN-23 The administration of the ICMS shall be performed by a lead agency with the support from other agencies. NN-01-01   H
RN-24 Communication protocols shall be developed for ICMS allowing effective communication among operators from various agencies. NN-01-01   H
RN-25 The institutional framework for operating ICMS shall be defined by a partnership agreement among all transportation agencies along the I-880 corridor. NN-01-01   H

Continue to 4: ICMS Functional Requirements ⇒