SIPA Template

Document Type
IMPLEMENTATION PROPOSAL
1(20)
File
305368205.doc
Prepared (also subject responsible, if other)
Document Number
Name
n/260 52-GDQ aaa bbbb/c Oen
Document responsible/Approved
Checked
Date
Revision
Document Class
Name
(Name)
2005-09-15
Confidential
XXX System
Implementation Proposal (Template)
Abstract: This document covers the system architecture for the XXX System
Table of Contents
1
INTRODUCTION.............................................................................................................4
1.1
1.2
TECHNICAL SOLUTION...............................................................................................5
2.1
2.2
2.3
2.4
2.5
2.6
2.7
PLATFORM TECHNOLOGY CHOICES.............................................................................7

SYSTEM FUNCTIONS....................................................................................................7
PORTABILITY................................................................................................................7
CO-LOCATION..............................................................................................................8
DEVELOPMENT ENVIRONMENT.............................................................................8
4.1
4.2
4.3
4.4
SYSTEM ARCHITECTURE..............................................................................................5
DATA MODEL...............................................................................................................5
TRAFFIC.......................................................................................................................5
LEGAL REGULATIONS..................................................................................................5
CHARGING / ACCOUNTING...........................................................................................6
OPERATION, ADMINISTRATION, MAINTENANCE..........................................................6
INTERNAL PROTOCOLS................................................................................................7
PLATFORM IMPACTS...................................................................................................7
3.1
3.2
3.3
3.4
SCOPE..........................................................................................................................4
DESIGN BASE...............................................................................................................4
GENERAL.....................................................................................................................8
LANGUAGES.................................................................................................................8
TOOLS..........................................................................................................................8
APPLICATION IMPLEMENTATION..................................................................................8
SECURITY IMPACTS.....................................................................................................9
5.1
5.2
5.3
5.4
5.5
APPLICATION ACCESS SECURITY.................................................................................9

OPERATING SYSTEM SECURITY...................................................................................9
DATABASE SECURITY..................................................................................................9
MIDDLEWARE SECURITY.............................................................................................9
TOOLS SECURITY.......................................................................................................10
Mobile Arts AB 2016 This document contains confidential information that remains the property of Mobile Arts AB, and may
not be copied, circulated, or distributed without prior written consent of Mobile Arts AB.
Date
Revision
2005-09-15
2(20)
Document Number
CHARACTERISTICS IMPACTS.................................................................................10
6.1
6.2
6.3
6.4
6.5
6.6
SUPPORTED CONFIGURATION TYPES.........................................................................10

AVAILABILITY / REDUNDANCY..................................................................................10
LOAD BALANCING AND PRIORITY.............................................................................10
CAPACITY..................................................................................................................10
RESPONSE TIMES.......................................................................................................10
CAPABILITIES.............................................................................................................11
HANDLING IMPACTS..................................................................................................11
7.1
7.2
7.3
7.4
7.5
BACKUP AND RECOVERY...........................................................................................11

COMPATIBILITY INFORMATION...................................................................................11
OPTIONS.....................................................................................................................11
ADAPTATIONS............................................................................................................11
INSTALLATION AND UPGRADES.................................................................................12
CUSTOMISATION POSSIBILITIES..........................................................................12
INTELLECTUAL PROPERTY RIGHTS....................................................................12
10
COMPETENCE DEVELOPMENT..........................................................................12
10.1
10.2
11
TRAINING...................................................................................................................12
PROTOTYPING............................................................................................................12
COSTS..........................................................................................................................13
11.1
11.2
11.3
11.4
12
DEVELOPMENT COSTS...............................................................................................13
SYSTEM TEST COSTS.................................................................................................13
DOCUMENTATION COSTS...........................................................................................14
EQUIPMENT COSTS....................................................................................................16
DOCUMENT INFORMATION................................................................................17
12.1
12.2
GLOSSARY.................................................................................................................17
REVISION INFORMATION............................................................................................17
13
REFERENCES............................................................................................................18
14
STATUS INFORMATION.........................................................................................19
14.1
14.2
14.3
STATEMENT OF COMPLIANCE....................................................................................19
OPEN QUESTIONS......................................................................................................20
RISK ANALYSIS..........................................................................................................20
Date
Revision
2005-09-15
3(20)
Document Number
List of Figures
Error! No table of figures entries found.
List of Tables
Table 1, Development Costs.....................................................................................................13
Table 2, System Test Costs........................................................................................................13
Table 3, Marketing Document Costs.........................................................................................14
Table 4, Specification Document Costs....................................................................................15
Table 5, Testing Document Costs..............................................................................................15
Table 6, Operation Document Costs.........................................................................................16
Table 7, Statement Of Compliance...........................................................................................19
Date
Revision
2005-09-15
Document Number
1 Introduction
1.1
Scope
Define shortly the scope for the implementation proposal e.g. in terms
of:
- Which parts of a system are covered and which are not
- The type of functionality and/or characteristics covered and not
covered
- The intended level of implementation detail provided
1.2
Design Base
Identify the version(s) of upon which the implementation has been

placed including:
- Existing own products
- Sourced products
- Shareware/Freeware
4(20)
Date
Revision
2005-09-15
Document Number
2 Technical Solution
2.1
System Architecture
Describe the architecture e.g. in terms of:

- System internal components
- The overall allocation of functionality upon the components
- System internal protocols between the components
- System internal principles
2.2
Data Model
Describe the data model e.g. in terms of:

- The overall allocation of static and dynamic data upon the components
2.3
Traffic
Describe the traffic interwork e.g. in terms of:

- The cross-component interwork for important traffic cases e.g. by
means of sequence diagrams, flowcharts,
pseudo-code, text, etc.
- Functionality
- Use of Options
- Optimisations
2.4
Legal Regulations
Describe the allocation of regulatory support e.g. in terms of:

- The cross-component interwork for important traffic cases e.g. by
- Functionality
- Use of Options
- Optimisations
5(20)
Date
Revision
2005-09-15
Document Number
2.5
Charging / Accounting
Describe the allocation of charging/accounting support e.g. in terms of:

- Charging / Accounting interwork for important traffic cases e.g. by
- Charging / Accounting parties
- Tariffs
- Volume/Time-based
- Discounts
- Hot Billing
- Real Time Billing (e.g. Pre-Paid or Advice-of-charge)
- Output
- Parallel Output
- Network Signalling Support
- Billing Gateway functionality
- Billing System functionality
- Use of Options
- Optimisations
2.6
Operation, Administration, Maintenance
Describe the allocation of OAM support e.g. in terms of:

- OAM interfaces provided
- Remote Access
- License Management
- Operator Management (Roles/Rights/Identities)
- Configuration Management
- Provisioning
- Crypto Management
- Fault Management (Alarms, Logs, Restarts)
- Performance Management
- Upgrades
- GUI (Type, Usability, On-line Help)
- External Agents
Where applicable for each item above, include aspects of:
supported interfaces, file handling, automatisation, use of options,
optimisations
6(20)
Date
Revision
2005-09-15
Document Number
2.7
Internal Protocols
Describe the protocol principles e.g. in terms of:

- Related standard/base protocol
- Used protocol bearer
- Parameter coding
- Addressing principles
- Seizure and release of sessions
- Important messages and parameters
- Compatibility mechanisms
- Protocol timers
- Protocol documentation
3 Platform Impacts
3.1
Platform Technology Choices
Define the impacts on the platform, e.g. in terms of new/existing:

- Processors
- Operating Systems
- Databases
- Disk Systems
- Protocol Stacks
- Terminal Servers
- Load Balancers
- Firewalls
- Web Servers
3.2
System Functions
Describe the impacts on the system functions e.g. with respect to

new/existing:
- System start/restart
- Configuration support
- Capacity licensing
- Time synchronization
3.3
Portability
Describe the portability possibilities/changes, e.g. regarding:

- SW between different processors and operating system environments
- HW between different system environments
- Tools
7(20)
Date
Revision
2005-09-15
Document Number
3.4
Co-location
Describe the co-location possibilities/changes e.g. regarding other:

- Applications
- Systems (e.g. mechanics)
4 Development Environment
4.1
General
Describe any general impacts on the development environment, e.g.

with respect to:
- Design
- Function Test
- System Test
- Installation
- Support
- Maintenance
4.2
Languages
Describe new languages used e.g. regarding:

- Documentation
- GUI
- Programming
4.3
Tools
Describe the impacts on tools, e.g. with respect to new/existing:

- External interfaces
- Load generators
- Simulators (Clients and/or Servers)
- Monitors
4.4
Application Implementation
Describe any application level implementation constraints, e.g. in terms

of:
- Optimisations
- New Design Rules / Patterns
8(20)
Date
Revision
2005-09-15
Document Number
5 Security Impacts
5.1
Application Access Security
Describe new/changed application access related security measures,

e.g. in terms of:
- Security Zones /Firewalls
- Encryption
- Authentication, e.g. Account & Password structures and rules
- Authorization, e.g. operator rights and roles, authority handling
- Auditing / Access Logging
- Seizure Time Supervision
- Destructive access discovery / Denial of Service attacks
- Safe Storage
5.2
Operating System Security
Describe new/changed OS related security measures, e.g. in terms of:

- Remote Access
- OAM Terminal Connection
- Authentication (Account & Password: structure, rules)
- Authorization (rights/roles, handling)
- Anonymous and Group Users
- User Data (start-up/other files)
- System Data (start-up/device/other files, services)
- Network Utilities (remote/tool/network access, file system export)
- Auditing/Access Logging (events, data, log handling)
- Used Services
5.3
Database Security
Describe new/changed DB related security measures, e.g. in terms of:

- Remote Access
- Authentication (Account & Password: structure, rules)
- Authorization (rights/roles, handling)
- Anonymous and Group Users
- Auditing/Logging (events, data, log handling)
5.4
Middleware Security
9(20)
Date
Revision
2005-09-15
Document Number
Describe new/changed Middleware related security measures, e.g. in

terms of:
- Internal communication/distribution (machine authentication,
encryption)
- Policing / Screening
5.5
Tools Security
Describe new/changed Tools related security measures, e.g. in terms of:

- Operator availability
6 Characteristics Impacts
6.1
Supported Configuration Types
Describe the supported configuration types, e.g. in terms of:

- Horizontal / Vertical Scalability
- Allocation of auxiliary equipment e.g. Firewalls, SSL Accelerators,
Load Balancers, Terminal Servers, etc.
6.2
Availability / Redundancy
Describe new /modified principles for availability used in the system e.g.
regarding:
- Redundancy
- Fail-over and fail-back
6.3
Load Balancing and Priority
Describe new /modified principles for load balancing used in the system
e.g. regarding:
- Load balancing criteria
- Overload protection
- Priority considerations within and between protocols
6.4
Capacity
For each applicable configuration type using a given Default Traffic

Model provide estimates for new /modified:
- Supported capacity, e.g. as number of transaction or requests
- Impact on the surrounding, e.g. on the core network
10(20)
Date
Revision
2005-09-15
Document Number
6.5
Response Times
Using stated assumptions, provide estimates any new /modified:

- Internal processing times
- The total transaction times, e.g. the time between reception of request
and supply of result
11(20)
Date
Revision
2005-09-15
Document Number
6.6
Capabilities
Describe new /modified system limits in the system e.g. regarding

amount of:
- Operators, Subscribers, Clients
- Memory
- Accuracy
- Stability
7 Handling Impacts
7.1
Backup and Recovery
Describe new /modified principles for backup and recovery used in the
system e.g. regarding:
- Robustness
- Export/import mechanisms
7.2
Compatibility Information
Describe any backward/forward compatibility issues in the system e.g.

regarding:
- Functional compatibility
- Protocol compatibility
- Operational compatibility
7.3
Options
Describe how each new/modified option is handled in the system e.g. by

means of:
- SW keys
- Optional SW
- Optional HW
- Optional documentation
7.4
Adaptations
Describe each new/modified adaptation possibility towards the physical

environment e.g. for different:
- Signalling standards and versions
- Web browsers
12(20)
Date
Revision
2005-09-15
Document Number
7.5
Installation and Upgrades
Describe new /modified principles for how to perform installation and

upgrades of the system e.g. regarding:
- Data conversion
- Service interruption
- Upgrade tools
13(20)
Date
Revision
2005-09-15
Document Number
8 Customisation Possibilities
Describe the customisation possibilities (by means of additional
development) that have been considered in the architecture, e.g. in
terms of:
- Adaptations to existing protocols e.g. new messages or parameters, or
market variations thereof
- Additional data items within an existing record structure
9 Intellectual Property Rights

Describe any possibilities/risks regarding:
- Creation of new own patents
- Infringements on existing patents
- Licensing of freeware, shareware and sourced products
10 Competence Development
10.1 Training
Identify any training needs within the organization, e.g. in terms of:
- Methodology
- Tools
- Programming languages
- Operating systems
- Databases
- Signalling
- Hardware
- Application specifics
10.2 Prototyping
Identify any prototyping needed for early verification of e.g.:
- System concepts
- Characteristics
14(20)
Date
Revision
2005-09-15
15(20)
Document Number
11 Costs
11.1 Development Costs
List each impacted product, and for each impacted product, list the
impacts on high level and estimate the cost for each such impact.
Product Name
(& Number if needed):
Impacts (high-level):
Cost (mh)
per impact:
Table 1, Development Costs

11.2 System Test Costs
List each tested system, and for each tested system, list the testes on
high level and estimate the cost for each such test.
System Name
Cost (mh)
per impact:
Table 2, System Test Costs
Date
Revision
2005-09-15
16(20)
Document Number
11.3 Documentation Costs

11.3.1 Marketing Documents
List each impacted marketing document, and for each impacted

document, list the impacts on high level and estimate the cost for each
such impact, e.g. for:
- Product Sheet
- Product Description
- Signalling Sequence Diagram (high-level)
- Statement Of Compliance
- Dimensioning Guideline
Document Name
Cost (mh)
per impact:
Table 3, Marketing Document Costs
Date
Revision
2005-09-15
17(20)
Document Number

11.3.2 Specification Documents
List each impacted specification document, and for each impacted

- Signalling Sequence Diagram (detailed)
- Mapping Diagram
- Management Information Base
- Protocol Specification
- Application Developers Guide
- Design Rule
- System Architecture Description
- Concepts and Abbreviations
- Traffic Model Specification
- Characteristics Specification
Document Name
Cost (mh)
per impact:
Table 4, Specification Document Costs

11.3.3 Testing Documents
List each impacted testing document, and for each impacted document,
list the impacts on high level and estimate the cost for each such
impact, e.g. for:
- Function Test Specification
- System Test Specification
- Acceptance Test Instruction
Document Name
Cost (mh)
per impact:
Date
Revision
2005-09-15
Document Number
Table 5, Testing Document Costs

11.3.4 Operation Documents
List each impacted operation document, and for each impacted

- Planning, Deployment and Provisioning Guide
- Installation and Configuration Guide
- Operation and Maintenance Guide
- Configuration File Description
- Configuration File Template
- Log List
- Alarm List
- Process List
- Application, Right and Credential List
- MIB List
- Measurement Data Report
- Accounting Data Report
- License List
- Training Course
Table 6, Operation Document Costs

11.4 Equipment Costs
Describe the equipment cost, e.g. with respect to:
- Capacity
- Capabilities
- Redundancy
- Sourced products
- Auxiliary equipment
18(20)
Date
Revision
2005-09-15
Document Number
12 Document Information
12.1 Glossary
12.1.1 Used Concepts
List and describe each concept used.

WORD
MS-spelling of WORLD
12.1.2 Suggested New/Modified Standard Concepts
List and describe each concept suggested to be included as a

new/modified standard concept.
WORLD
Standard spelling of WORLD
12.1.3 Used Abbreviations
List and describe each abbreviation used.

TBD
To BE Defined
12.1.4 Suggested New/Modified Standard Abbreviations
List and describe each abbreviation suggested to be included as a

new/modified standard abbreviation.
TBD
Too Bleeding Difficult
12.1.5 Legend
Describe the legend used in figures etc.

12.2 Revision Information
12.2.1 Revision History
For each new revision: State the revision date and document status, and
describe on high-level the modifications.
Revision: Date:
Current status and principal changes since previous revision:
19(20)
Date
Revision
2005-09-15
Document Number
13 References
List the name, number and revision for each document reference.
[1] Document Name, Revision, Number
http://www.document_source.nu
20(20)
Date
Revision
2005-09-15
Document Number
14 Status information
14.1 Statement Of Compliance
List each requirement item covered by the implementation proposal and
give a statement of compliance to each.
Item
refers to the corresponding requirement (sub-)item in the Requirement Specification. Includes
also all related requirement (sub-)items unless otherwise specified.
Modified
defines whether the item has been changed by means of a change request which is not
reflected by the Requirement Specification. The following changes are indicated:
1. Removed = Requirement removed by a Change Request (CR)
2. Changed = Requirement changed by a CR
Details are given by the Comment.
Status
Defines the level of compliance to the item including any changes as specified by Modified.
The following compliance status are used:
1. FC = Fully Compliant
2. PC = Partly Compliant, see Comment for specification of requirement deviations
3. NC = Not Compliant, see Comment for details.
4. NA = Not Applicable, requirement removed by CR or covered by another project,
see Comment for details.
5. Open = Further information/investigations needed in order to define the level of
compliance to the requirement.
Drop
refers to the increment(s) where part/full functionality is included; see Comment for details.
Contact
refers to the initials for the requirement (sub-)item responsible person. Includes also all
related requirement (sub-)items unless otherwise specified.
Comment
includes details with respect to CRs, Non Compliance, contents in drop etc.
Item
Modified Status Drop
Contact Comment
Table 7, Statement Of Compliance
21(20)
Date
Revision
2005-09-15
Document Number
14.2 Open Questions

List and describe on high-level the open questions that remains to be
resolved.
14.3 Risk Analysis
List and describe on high-level any risks identified with respect to the
development project.
State also for each risk possible actions to minimise the risk.
22(20)

SIPA Template

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SIPA Template

Uploaded by

Copyright:

Available Formats

Document Type

n/260 52-GDQ aaa bbbb/c Oen

PLATFORM TECHNOLOGY CHOICES.............................................................................7

APPLICATION ACCESS SECURITY.................................................................................9

n/260 52-GDQ aaa bbbb/c Oen

SUPPORTED CONFIGURATION TYPES.........................................................................10

BACKUP AND RECOVERY...........................................................................................11

INTELLECTUAL PROPERTY RIGHTS....................................................................12

n/260 52-GDQ aaa bbbb/c Oen

n/260 52-GDQ aaa bbbb/c Oen

Identify the version(s) of upon which the implementation has been

n/260 52-GDQ aaa bbbb/c Oen

Describe the architecture e.g. in terms of:

Describe the data model e.g. in terms of:

Describe the traffic interwork e.g. in terms of:

Describe the allocation of regulatory support e.g. in terms of:

n/260 52-GDQ aaa bbbb/c Oen

Describe the allocation of charging/accounting support e.g. in terms of:

Operation, Administration, Maintenance

Describe the allocation of OAM support e.g. in terms of:

n/260 52-GDQ aaa bbbb/c Oen

Describe the protocol principles e.g. in terms of:

Platform Technology Choices

Define the impacts on the platform, e.g. in terms of new/existing:

Describe the impacts on the system functions e.g. with respect to

Describe the portability possibilities/changes, e.g. regarding:

n/260 52-GDQ aaa bbbb/c Oen

Describe the co-location possibilities/changes e.g. regarding other:

Describe any general impacts on the development environment, e.g.

Describe new languages used e.g. regarding:

Describe the impacts on tools, e.g. with respect to new/existing:

Describe any application level implementation constraints, e.g. in terms

n/260 52-GDQ aaa bbbb/c Oen

Application Access Security

Describe new/changed application access related security measures,

Operating System Security

Describe new/changed OS related security measures, e.g. in terms of:

Describe new/changed DB related security measures, e.g. in terms of:

n/260 52-GDQ aaa bbbb/c Oen

Describe new/changed Middleware related security measures, e.g. in

Describe new/changed Tools related security measures, e.g. in terms of:

Supported Configuration Types

Describe the supported configuration types, e.g. in terms of:

Load Balancing and Priority

For each applicable configuration type using a given Default Traffic

n/260 52-GDQ aaa bbbb/c Oen

Using stated assumptions, provide estimates any new /modified:

n/260 52-GDQ aaa bbbb/c Oen

Describe new /modified system limits in the system e.g. regarding

Backup and Recovery

Describe any backward/forward compatibility issues in the system e.g.

Describe how each new/modified option is handled in the system e.g. by

Describe each new/modified adaptation possibility towards the physical

n/260 52-GDQ aaa bbbb/c Oen

Installation and Upgrades

Describe new /modified principles for how to perform installation and

n/260 52-GDQ aaa bbbb/c Oen

9 Intellectual Property Rights

n/260 52-GDQ aaa bbbb/c Oen

Table 1, Development Costs

Table 2, System Test Costs

n/260 52-GDQ aaa bbbb/c Oen

11.3 Documentation Costs