blob: eb49ca7463361d31dde187f7444a9de1f1e7bf98 [file] [log] [blame]
Aric Gardner9ad5c042019-10-22 13:42:10 -04001.. This work is licensed under a Creative Commons Attribution 4.0 International License.
Lott, Christopher (cl778h)e706e852019-11-08 10:10:17 -05002.. SPDX-License-Identifier: CC-BY-4.0
3.. Copyright (C) 2019 YOUR-ORGANIZATION-NAME
Aric Gardner9ad5c042019-10-22 13:42:10 -04004
weichen300706e2019-11-04 10:13:57 -05005
weichenf0de3c32019-11-06 02:52:29 -05006User Guide
weichen300706e2019-11-04 10:13:57 -05007==========
8
weichenf0de3c32019-11-06 02:52:29 -05009This is the user guide of OSC <COMPONENT>.
10
Aric Gardner9ad5c042019-10-22 13:42:10 -040011.. contents::
12 :depth: 3
13 :local:
14
15.. a user guide should be how to use the component or system; it should not be a requirements document
16.. delete this content after edittng it
17
18
19Description
weichen300706e2019-11-04 10:13:57 -050020-----------
Aric Gardner9ad5c042019-10-22 13:42:10 -040021.. Describe the traget users of the projcet, for example, modeler/data scientist, ORAN-OSC platform admin, marketplace user, design studio end user, etc
22.. Descirbe how the target users can get use of a O-RAN SC component.
23.. If the guide contains sections on third-party tools, is it clearly stated why the O-RAN-OSC platform is using those tools? Are there instructions on how to install and configure each tool/toolset?
24
weichenf0de3c32019-11-06 02:52:29 -050025Feature Introduction
weichen300706e2019-11-04 10:13:57 -050026--------------------
Aric Gardner9ad5c042019-10-22 13:42:10 -040027.. Provide enough information that a user will be able to operate the feature on a deployed scenario. content can be added from administration, management, using, Troubleshooting sections perspectives.
28
29
30
31
32