fujian_water_biz_doc/output/01_System_Overview.html

299 lines
11 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<meta name="author" content="系统设计团队" />
<title>福建水务营收系统-系统概述</title>
<style>
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
div.columns{display: flex; gap: min(4vw, 1.5em);}
div.column{flex: auto; overflow-x: auto;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
/* The extra [class] is a hack that increases specificity enough to
override a similar rule in reveal.js */
ul.task-list[class]{list-style: none;}
ul.task-list li input[type="checkbox"] {
font-size: inherit;
width: 0.8em;
margin: 0 0.8em 0.2em -1.6em;
vertical-align: middle;
}
.display.math{display: block; text-align: center; margin: 0.5rem auto;}
</style>
<link rel="stylesheet" href="output/document_style.css" />
<meta charset="UTF-8"><meta name="viewport" content="width=device-width, initial-scale=1.0">
</head>
<body>
<header id="title-block-header">
<h1 class="title">福建水务营收系统-系统概述</h1>
<p class="author">系统设计团队</p>
<p class="date">2024年12月19日</p>
</header>
<nav id="TOC" role="doc-toc">
<ul>
<li><a href="#福建水务营收系统系统概述"
id="toc-福建水务营收系统系统概述"><span
class="toc-section-number">1</span> 福建水务营收系统系统概述</a>
<ul>
<li><a href="#文档定位" id="toc-文档定位"><span
class="toc-section-number">1.1</span> 1. 文档定位</a></li>
<li><a href="#项目背景与建设目标" id="toc-项目背景与建设目标"><span
class="toc-section-number">1.2</span> 2. 项目背景与建设目标</a>
<ul>
<li><a href="#项目背景" id="toc-项目背景"><span
class="toc-section-number">1.2.1</span> 2.1 项目背景</a></li>
<li><a href="#建设目标" id="toc-建设目标"><span
class="toc-section-number">1.2.2</span> 2.2 建设目标</a></li>
</ul></li>
<li><a href="#系统范围与边界" id="toc-系统范围与边界"><span
class="toc-section-number">1.3</span> 3. 系统范围与边界</a>
<ul>
<li><a href="#范围内" id="toc-范围内"><span
class="toc-section-number">1.3.1</span> 3.1 范围内</a></li>
<li><a href="#范围外" id="toc-范围外"><span
class="toc-section-number">1.3.2</span> 3.2 范围外</a></li>
</ul></li>
<li><a href="#涉众与角色" id="toc-涉众与角色"><span
class="toc-section-number">1.4</span> 4. 涉众与角色</a></li>
<li><a href="#术语与缩略语概要层" id="toc-术语与缩略语概要层"><span
class="toc-section-number">1.5</span> 5. 术语与缩略语(概要层)</a>
<ul>
<li><a href="#业务术语" id="toc-业务术语"><span
class="toc-section-number">1.5.1</span> 5.1 业务术语</a></li>
<li><a href="#技术术语" id="toc-技术术语"><span
class="toc-section-number">1.5.2</span> 5.2 技术术语</a></li>
</ul></li>
<li><a href="#关联文档" id="toc-关联文档"><span
class="toc-section-number">1.6</span> 6. 关联文档</a>
<ul>
<li><a href="#本目录文档" id="toc-本目录文档"><span
class="toc-section-number">1.6.1</span> 6.1 本目录文档</a></li>
<li><a href="#跨目录主文档" id="toc-跨目录主文档"><span
class="toc-section-number">1.6.2</span> 6.2 跨目录主文档</a></li>
<li><a href="#对齐与核对资料" id="toc-对齐与核对资料"><span
class="toc-section-number">1.6.3</span> 6.3 对齐与核对资料</a></li>
</ul></li>
<li><a href="#阅读路径建议" id="toc-阅读路径建议"><span
class="toc-section-number">1.7</span> 7. 阅读路径建议</a></li>
<li><a href="#维护要求" id="toc-维护要求"><span
class="toc-section-number">1.8</span> 8. 维护要求</a></li>
</ul></li>
</ul>
</nav>
<h1 data-number="1" id="福建水务营收系统系统概述"><span
class="header-section-number">1</span> 福建水务营收系统系统概述</h1>
<h2 data-number="1.1" id="文档定位"><span
class="header-section-number">1.1</span> 1. 文档定位</h2>
<p>本文档用于说明福建水务营收系统的建设背景、目标、范围边界、涉众角色与基础术语,作为总体设计层的导览入口。<br />
详细的模块设计、接口定义、数据结构与部署实现,以主文档和专项文档为准,不在本文重复展开。</p>
<h2 data-number="1.2" id="项目背景与建设目标"><span
class="header-section-number">1.2</span> 2. 项目背景与建设目标</h2>
<h3 data-number="1.2.1" id="项目背景"><span
class="header-section-number">1.2.1</span> 2.1 项目背景</h3>
<p>福建水务营收系统面向水务企业营收管理与客户服务全流程,覆盖抄表、开账、收费、账务、工单、表务、报装与渠道服务。<br />
项目目标是将分散业务统一到可评审、可交付、可持续维护的体系下,支撑集团化与多组织协同。</p>
<h3 data-number="1.2.2" id="建设目标"><span
class="header-section-number">1.2.2</span> 2.2 建设目标</h3>
<ul>
<li>建立统一平台能力,支撑认证、权限、组织、参数、租户与审计监控。</li>
<li>建立营收业务主链路,覆盖客户、计量、收费、账务与客服服务。</li>
<li>建立独立业务子系统,支撑移动抄表、工单、表务与报装场景。</li>
<li>建立基础服务子系统,统一发票、支付结算、消息能力。</li>
<li>满足安全合规、国产化适配与持续交付要求。</li>
</ul>
<h2 data-number="1.3" id="系统范围与边界"><span
class="header-section-number">1.3</span> 3. 系统范围与边界</h2>
<h3 data-number="1.3.1" id="范围内"><span
class="header-section-number">1.3.1</span> 3.1 范围内</h3>
<table>
<thead>
<tr>
<th>分类</th>
<th>范围说明</th>
</tr>
</thead>
<tbody>
<tr>
<td>平台能力</td>
<td>统一认证、权限、租户、组织、参数、监控</td>
</tr>
<tr>
<td>核心业务</td>
<td>客户资料、抄表开账、营业收费、账务处理、发票、催缴、统计</td>
</tr>
<tr>
<td>业务子系统</td>
<td>手机抄表 APP、微网厅、工单管理、表务管理、报装业务</td>
</tr>
<tr>
<td>基础服务</td>
<td>发票服务、支付与银行结算、消息服务</td>
</tr>
<tr>
<td>外部集成</td>
<td>银行、第三方支付、短信/邮件/站内信、物联网、CA 能力</td>
</tr>
</tbody>
</table>
<h3 data-number="1.3.2" id="范围外"><span
class="header-section-number">1.3.2</span> 3.2 范围外</h3>
<table>
<thead>
<tr>
<th>分类</th>
<th>说明</th>
</tr>
</thead>
<tbody>
<tr>
<td>代码实现细节</td>
<td>具体类设计、SQL、接口字段定义</td>
</tr>
<tr>
<td>运维脚本实现</td>
<td>启停脚本、部署脚本、监控规则细项</td>
</tr>
<tr>
<td>测试用例细节</td>
<td>测试步骤、断言口径、执行结果</td>
</tr>
</tbody>
</table>
<h2 data-number="1.4" id="涉众与角色"><span
class="header-section-number">1.4</span> 4. 涉众与角色</h2>
<table>
<thead>
<tr>
<th>角色</th>
<th>关注重点</th>
</tr>
</thead>
<tbody>
<tr>
<td>项目管理与评审人员</td>
<td>范围边界、建设目标、交付范围</td>
</tr>
<tr>
<td>架构与开发人员</td>
<td>子系统职责、总体边界、协同关系</td>
</tr>
<tr>
<td>测试与运维人员</td>
<td>系统分层、部署原则、安全与可运维约束</td>
</tr>
<tr>
<td>甲方技术人员</td>
<td>交付口径一致性、可追溯性、后续维护可行性</td>
</tr>
</tbody>
</table>
<h2 data-number="1.5" id="术语与缩略语概要层"><span
class="header-section-number">1.5</span> 5. 术语与缩略语(概要层)</h2>
<h3 data-number="1.5.1" id="业务术语"><span
class="header-section-number">1.5.1</span> 5.1 业务术语</h3>
<table>
<thead>
<tr>
<th>术语</th>
<th>说明</th>
</tr>
</thead>
<tbody>
<tr>
<td>营收业务系统SYS-002</td>
<td>核心营收业务承载子系统</td>
</tr>
<tr>
<td>微网厅SYS-004</td>
<td>面向外部客户服务的线上渠道</td>
</tr>
<tr>
<td>表务管理SYS-006</td>
<td>水表设备与库存相关管理域</td>
</tr>
<tr>
<td>报装业务SYS-007</td>
<td>新装/改装/流程办理相关业务域</td>
</tr>
</tbody>
</table>
<h3 data-number="1.5.2" id="技术术语"><span
class="header-section-number">1.5.2</span> 5.2 技术术语</h3>
<table>
<thead>
<tr>
<th>术语</th>
<th>说明</th>
</tr>
</thead>
<tbody>
<tr>
<td>SSO</td>
<td>单点登录能力</td>
</tr>
<tr>
<td>RBAC</td>
<td>基于角色的访问控制</td>
</tr>
<tr>
<td>OAuth2.0 + CAS</td>
<td>统一认证与单点登录协议组合</td>
</tr>
<tr>
<td>IF- 编号</td>
<td>接口编号前缀,用于与模块编号区分</td>
</tr>
</tbody>
</table>
<h2 data-number="1.6" id="关联文档"><span
class="header-section-number">1.6</span> 6. 关联文档</h2>
<h3 data-number="1.6.1" id="本目录文档"><span
class="header-section-number">1.6.1</span> 6.1 本目录文档</h3>
<ul>
<li>系统架构说明:<code>02_System_Architecture.md</code></li>
<li>概要设计主文档(单一真源):<code>03_Summary_Design.md</code></li>
<li>总体图谱文档:<code>04_System_Diagrams.md</code></li>
</ul>
<h3 data-number="1.6.2" id="跨目录主文档"><span
class="header-section-number">1.6.2</span> 6.2 跨目录主文档</h3>
<ul>
<li>详细设计主文档:<code>../02_Detailed_Design/01_Detailed_Design.md</code></li>
<li>数据库设计主文档:<code>../03_Technical_Design/01_Database_Design.md</code></li>
<li>接口设计主文档:<code>../03_Technical_Design/03_Interface_Design.md</code></li>
<li>安全设计主文档:<code>../03_Technical_Design/04_Security_Design.md</code></li>
<li>部署设计主文档:<code>../03_Technical_Design/05_Deployment_Design.md</code></li>
</ul>
<h3 data-number="1.6.3" id="对齐与核对资料"><span
class="header-section-number">1.6.3</span> 6.3 对齐与核对资料</h3>
<ul>
<li>后端现状:<code>../../guides/BACKEND_CURRENT_STATUS.md</code></li>
<li>后端表映射:<code>../../guides/BACKEND_TABLE_MAPPING.md</code></li>
<li>历史资料归档:<code>../04_Appendix/Archive/</code></li>
</ul>
<h2 data-number="1.7" id="阅读路径建议"><span
class="header-section-number">1.7</span> 7. 阅读路径建议</h2>
<ol type="1">
<li>先阅读 <code>03_Summary_Design.md</code>,建立统一口径。</li>
<li>再阅读
<code>02_System_Architecture.md</code>,理解总体边界和架构原则。</li>
<li>对照 <code>04_System_Diagrams.md</code>,核对图文一致性。</li>
<li>按需进入详细设计、数据库和接口主文档。</li>
</ol>
<h2 data-number="1.8" id="维护要求"><span
class="header-section-number">1.8</span> 8. 维护要求</h2>
<ul>
<li>本文档仅维护“概述级”信息,不引入实现细节。</li>
<li>出现与 <code>03_Summary_Design.md</code>
不一致时,以主文档为准并及时修正。</li>
<li>修改后至少执行:
<ul>
<li><code>make validate-file FILE=docs/design/01_Overview/01_System_Overview.md</code></li>
<li><code>make check-links</code></li>
</ul></li>
</ul>
</body>
</html>