Sie sind auf Seite 1von 8

B E YON D T R U S T

P R O P R I E TARY

A N D

C O N F I D E N T I A L

Technical
Specification
File: /var/www/apps/conversion/tmp/scratch_3/280841427.doc

PROJECT <PROJECT_NAME_AND_RELEASE>

Technical Specification
Author: <name>
Date: <date>
Revision: 1

Reviewed by:
Development: ____________________________ Date: _____________________
QA: ____________________________

Date: _____________________

Product Management: _________________________ Date:


_____________________
Approved by: ___________________________ Date: _____________________

BeyondTrust Software, Inc.

8/24/2015

Auto-Import Library Functional Specification: Rev 1

B E YON D T R U S T

P R O P R I E T AR Y

A N D

C O N F I D E N T I A L

Summary of Revisions
Revision Number

8/24/2015

By Whom

Date

Changes

Initial

280841427.doc: Rev 1

Page iii

B E YON D T R U S T

P R O P R I E T AR Y

A N D

C O N F I D E N T I A L

Table of Contents
1.

INTRODUCTION.................................................................................................................................5
1.1 Summary of the new feature Or Description of the issue to fix..............................................................5
1.2 Glossary...................................................................................................................................................5
1.3 References...............................................................................................................................................5

2.

FEATURE SPECIFIATION................................................................................................................6

3.

DEVELOPMENT SPECIFICATION.................................................................................................7
3.1 Estimated Effort......................................................................................................................................7
3.2 Programming...........................................................................................................................................7
3.3 Resources and Files.................................................................................................................................7
3.4 Unit testing..............................................................................................................................................7

4.

QA IMPACT..........................................................................................................................................8
4.1 Testing Recommendations......................................................................................................................8
4.2 Regression Risk Assessment and Backward Compatibility Issues.........................................................8
4.3 QA Test case Review by development and test case modification suggestions if any............................8

5.

SUPPORT IMPACT.............................................................................................................................8

6.

DOCUMENTATION IMPACT...........................................................................................................8

8/24/2015

PBUL Technical Specification: Rev 1

Page iv

1.

Introduction

1.1 Summary of the new feature Or Description of the issue to fix


Describe the new feature, how it fits into the product, and how it
improves the product.
Or
Describe the problem to fix and how it impacts the functionality of the
product.
1.2 Glossary
List below definitions, acronyms and abbreviations used in this
document.
1.3 References
List references to other documents or links.

8/24/2015

Auto-Import Library Functional Specification: Rev 1

B E YON D T R U S T

2.

P R O P R I E T AR Y

A N D

C O N F I D E N T I A L

Feature Specification

This section is to describe the feature added or the issue to fix. Include
sections such as:

Architecture of the feature

Sample Flow/Execution Diagram from User Perspective

Design Limitation and Assumptions

Platform Dependent Issues

Installation or Setup Issues

Migration Issues

8/24/2015

PBUL Technical Specification: Rev 1

Page 6

B E YON D T R U S T

3.

P R O P R I E T AR Y

A N D

C O N F I D E N T I A L

Development Specification

This section is to describe the programming details of the feature.


3.1 Estimated Effort
Estimate the effort to code and test the component ready for hand over
to QA and Technical Writers.
3.2 Programming
List procedures, modules and programs to be written, changed or
deleted to meet the feature specifications. Create as many sub-sections
as needed for each module/program that is affected.
3.3 Resources and Files
List of files and resources changed during implementation of this feature.
Including database changes, message changes or additions, changes to
man pages.
3.4 Unit testing
List of tests done during development cycle, Include any test program, or
script that was used.

8/24/2015

PBUL Technical Specification: Rev 1

Page 7

B E YON D T R U S T

4.

P R O P R I E T AR Y

A N D

C O N F I D E N T I A L

QA Impact

4.1 Testing Recommendations


Look at the component from the QA point of view. Suggest any special
tests that will stress the component. Think how to make the component
NOT work and what special tests should be performed on this
component. This is a guideline to the QA testing procedures. Suggest
additional function tests that are necessary. Special test requirements,
for example: the security levels, hardware or software configurations,
multi-system issues. Note anything that cannot be tested which might
require field tests.
4.2 Regression Risk Assessment and Backward Compatibility Issues
What would be the implications of failure in the component? Is the code
complex? What is the potential for destabilizing existing functions?
What other areas of the product interact with this module?
How this feature will affect backward compatibility with previous
releases of the product.
4.3 QA Test case Review by development and test case modification
suggestions if any
Put here the test cases provided by QA, and suggestions from
development to these test cases.

5.

Support Impact

What impact this issue might have on Support? Will this relieve some
existing problem in the product?
Detail any diagnostics or trace facilities built in to the component, or
facilities built into other components that would be used to gather
information about what is happening. Note anything that may make the
component difficult to diagnose (for example: no tracing facility), difficult
to service, unreliable (for example: External Risks. List any workarounds.

6.

Documentation Impact

List changes to documentation for this new feature.

8/24/2015

PBUL Technical Specification: Rev 1

Page 8