Software

Requirements
Definition
Extractor V15.00

Template Software Requirements Definition v 1.00 p 1/9

When printed out, this document shall be considered as “uncontrolled”
 Document DPE_Template_Software Requirements
Reference Definition.doc
Date 19/10/04

Author(s) DPE-ken

Template Software Requirements Definition v 1.00 p 2/9

When printed out, this document shall be considered as “uncontrolled”
Document Control Information
Document Name SRD_Extractor_V15_00.doc
Document Version 1.0
Author TVD
Date of Release 21/02/05
Total Pages 8
Review Period
Distribution

Release Information
Action Responsibility Date Name
Released by
Reviewed by
Approved by

Revision History
Version Issue Reason for change Description of change
date
0.1 16/02/05 First draft
1.0 21/02/05 Initial Version

Template Software Requirements Definition v 1.00 p 3/9

When printed out, this document shall be considered as “uncontrolled”
Table of Contents

1. Introduction......................................................................... ..........5
1.1 Purpose...............................................................................................5
1.2 Scope........................................................................................... ........5
1.3 References...........................................................................................5
1.4 Definitions, Acronyms and Abbreviations...............................................5
2. ANALYSIS “AS IS”............................................... ............................6
2.1 Overview of Current System..................................................................6
2.2 Limitations of the Current System.........................................................6
2.3 Conclusion............................................................................................6
3. ANALYSIS “TO BE”............................................................. .............7
3.1 Objectives............................................................................................7
3.2 Requirements.......................................................................................7
3.3 System Attributes.................................................................................9

Template Software Requirements Definition v 1.00 p 4/9

When printed out, this document shall be considered as “uncontrolled”
1.Introduction

1.1Purpose
This document will describe the requirements for Extractor version 15.00. This is a
version that will be compatible with the new features introduced in TIF15/ NCS15.

1.2Scope
Only the influence of the new NCS15 features will be described. Any bug fixes or feature
request that should also be solved in Extractor V15.00 will be described and
communicated via BugZilla or MKS. See the specific project instructions to know where to
find these.

1.3References
A detailed description of the TIF15 data model can be found on TAIP.

1.4Definitions, Acronyms and Abbreviations

Template Software Requirements Definition v 1.00 p 5/9

When printed out, this document shall be considered as “uncontrolled”
2.ANALYSIS “AS IS”

2.1Overview of Current System

Not applicable.

2.2Limitations of the Current System

Not applicable.

2.3Conclusion
Not applicable.

Template Software Requirements Definition v 1.00 p 6/9

When printed out, this document shall be considered as “uncontrolled”
3.ANALYSIS “TO BE”

3.1Objectives
The objective of this Extractor version is to contain support for the features introduced in
TIF 15. In the table below, the new features are listed and an indication is given to what
extent the features have an influence on the Extractor tool.

Lane Information No influence

Has Influence on the
3D Landmarks algorithm
Warning Signs No influence
Speed Cameras No influence
Toll gate No influence
Passport control No influence
Bus Terminal No influence
Miscellaneous No influence

Only the “3D landmarks” feature has an influence on Extractor. All other features are
generic, i.e. they only require adaptation of ini files, not related to the tools. For
supporting the other features, no changes must be made to Extractor.

3.2Requirements

3.2.1Functional Requirements

Only the requirements regarding the “3D landmarks” feature will be described, for the
other features there are no extra requirements.

For a POI of type “3D Landmark”, the VRML file will be stored “in” the TIF database. The
path to this file is stored as an EAT attribute in the database. The specification of the
path to this file can be found on TAIP. The consistency software will check if all VRML files
referenced by a 3D Landmark POI actually exist.

It will be possible to indicate if the VRML files for 3D landmarks should be copied.

• In case the VRML files should be copied

If a POI of type “3D Landmark” is part of the area that should be extracted, the
VRML file has to part of the resulting extracted dataset. The path in the EAT
attribute of the resulting POI will refer to a VRML file having the same content as
the one the original POI referred to. Providing there are no consistency errors
related to VRML files before the extraction, no consistency errors related to VRML
files may exist after the extraction.
• In case the VRML files should not be copied
The resulting (extracted) dataset may not contain any VRML files. Any consistency
error regarding VRML files existing after the extraction may be ignored.

Template Software Requirements Definition v 1.00 p 7/9

When printed out, this document shall be considered as “uncontrolled”
3.2.2Data Requirements
N/A

3.2.3Performance Requirements
If no VRML files should be copied to the extracted dataset, the performance of the
software should be as good as the performance of Extractor V14.00.
In case VRML files should be copied to the extracted dataset, a performance decrease of
maximum 1% can be accepted.

3.2.4Interface Requirements

The caption of the main interface should be updated to be able to identify the version of
the tool as 15.00.

The interface should provide an option to switch the copying of VRML files on or off. An
extra groupbox should be added to the options tab sheet. The groupbox should be called
External file options, containing (for now) only a checkbox for switching on or off the
copying of 3D landmark VRML files. If checked, the software will copy the VRML files,
otherwise not. See the image below for an example of the interface design.
By default, the copying of VRML files should be switched on in all Exchange profiles.

3.2.5Testing Requirements

General
Regression tests regarding the functionality and performance of the tool should be
performed.
Specific tests should be performed if new NCS-15 features other than 3D landmarks are
extracted correctly.

3D landmarks
For 3D landmarks, tests should be performed to check if the behaviour of the tool is
correct according to the settings in the interface. Tests should be performed if all VRML
files are correctly transferred if they have to be transferred. It should also be tested if
there are indeed no VRML files in the resulting dataset when the option is switched off.

Performance
Tests should be performed to check if the above-mentioned performance criteria are met.

Template Software Requirements Definition v 1.00 p 8/9

When printed out, this document shall be considered as “uncontrolled”
3.2.6Other Requirements
None

3.3System Attributes

3.3.1Reliability
N/A

3.3.2Availability
N/A

3.3.3Security
N/A

3.3.4Portability
N/A

Template Software Requirements Definition v 1.00 p 9/9

When printed out, this document shall be considered as “uncontrolled”