毕业设计(论文)
中小企业OA系统的设计与实现
论文作者姓名: 申请学位专业: 申请学位类别: 指导教师姓名(职称): 论文提交日期:
中小企业
OA系统的设计与实现 摘 要
随着全球经济一体化进程的加快和信息技术的飞速发展,Internet技术及其应用给人们的日常生活和工作等各个方面带来了深刻的影响。网络应用技术的不断提高,企业对于相互之间的通讯能力提出了更高的要求。许多企业都具有一定信息化基础,有一定数量的信息设备和信息源,有相互连通的接口,需要实现消息的无缝传递。因此,为了创造出一个集成化的办公环境,提高办公效率和办公质量,就提出了办公自动化(Office Automation),简称OA。
本课题设计并开发了中小企业OA系统的公文流转模块,包括用户管理、收文批阅、发文批阅以及查阅历史文件等功能模块,系统基于B/S架构,采用C#.NET和SQL Server2000技术进行开发。
关键词:OA;收文批阅;发文批阅
Design and implement of OA system for mid- and
Small-scale enterprise
Abstract
Along with the global economy to accelerate the process of integration of information technology and the rapid development, the internet technology and its application has brought the profound influence on people's daily life and the work. With the unceasing enhancement of the network application technology,enterprises for mutual communication between the capacity of a higher demand. Many enterprises all have the certain information foundation, and have the certain quantity of the information equipments, the sources, and the joints which mutually connect. And it needs to realize the news seamless transmission. Therefore, in order to create an integrated work environment, enhance the office efficiency and the work quality, the office automation appears(Office Automation), called OA.
This topic designed and developed a document processing model of mid- and small-scale enterprises' OA system, including the function models like user management, reviewing the received document, the outgoing message reviews and consulting history file. The system is based on the B/S construction and is developed with C#. NET and SQL the Server2000 technology .
Key words: OA; Review the receiving document; Review the outgoing
document
目 录
论文总页数:19页
1引言................................................................................................................................................ 1 1.1课题背景 ....................................................................................................................................... 1 1.2研究现状分析 .............................................................................................................................. 1 1.3研究方法 ....................................................................................................................................... 1 2结构环境论述 ................................................................................................................................ 1 2.1开发环境及语言 .......................................................................................................................... 1 2.2 C#介绍 .......................................................................................................................................... 2 3系统分析 ........................................................................................................................................ 2 3.1系统需求分析 .............................................................................................................................. 2 3.2系统流程 ....................................................................................................................................... 3 4系统模块划分 ................................................................................................................................ 4 5系统的实现 .................................................................................................................................... 4 5.1数据库设计 ................................................................................................................................... 4 5.2模块设计 ....................................................................................................................................... 5 5.2.1用户管理 ............................................................................................................................... 5 5.2.2收文批阅 ............................................................................................................................... 6 5.2.3发文批阅 ............................................................................................................................... 9 5.2.4历史文件查阅 ..................................................................................................................... 12 5.2.5个人信息 ............................................................................................................................. 15 结 论 ......................................................................................................................................... 16 参考文献 ......................................................................................................................................... 17 致 谢 ......................................................................................................................................... 18 声 明 ........................................................................................................................................... 0
1引言
1.1课题背景
现代办公自动化系统被要求成为有效地信息采集和管理的平台,是以开放、
先进的Intranet技术及消息传递和工作流管理技术为核心的新一代全方位办公信息服务系统,成为一个资源中心和通信中心。它需要改进企业内部的通讯水平,将传统的办公模式发展为一个具有跨地域通讯能力、能够协同工作,并保持一致的办公环境,消除传统办公方式下的信息存储、管理和分布的障碍,充分实现信息共享、资源共享。通过建立OA系统,可以提高人们协同工作的效率,减少人工操作的重复操作和复杂程度;消除在传统办公中信息存储、分发、管理和分布的障碍,提高日常办公管理水平;为各级领导进行宏观管理提供高效便利的服务,并为科学决策提供有效的参考依据;改善企业内部的办公环境,便于办公人员及时掌握、管理各方信息,改善办公条件,规范办公流程,使管理水平进一步科学化和现代化。
1.2研究现状分析
网络办公已是现代化企业发展的大势所趋,传统的手工办公方式已经无法满足现代办公的需要,收发文管理系统为提高工作效率,规范办公制度,增强办公的透明性,实现信息、资源、文档的统一管理。是为方便领导决策,逐步实现无纸化办公的重要工具,越来越受到人们的重视。
1.3研究方法
本课题选择了B/S三层结构,后台数据库采SQL SERVER2000,WBE服务器运行微软的IIS,以及C#.NET作为开发工具,客户端用IE浏览器。B/S结构是在TCP/IP的支持下,以HTTP为传输协议,客户端通过Browser访问WEB服务器,以及与之相连的后台数据库的技术及体系结构,它由浏览器、Web服务器、应用服务器和数据库服务器组成。B/S模式突破了传统的文件共享及C/S模式,实现了更大程度的信息共享,任何用户只要通过浏览器即可访问数据库。B/S结构的工作原理是:客户端的浏览器通过URL访问Web服务器,Web服务器请求数据库服务器,并将获得的结果以HTML形式返回客户端浏览器。
2结构环境论述
2.1开发环境及语言
Microsoft® Windows™ XP Professional
Microsoft® Visual Studio 2003(C Sharp)
Microsoft® Developer Network for Visual Studio.NET 2003
2.2 C#介绍
C#是微软公司专门为.NET量身订制的新一代程序开发语言,它充分吸收了过去几十年中计算机科学发展的经验教训,体现了当前最新程序设计技术的功能和精华,从C#的身上可看到最突出的优点是:现代、简单、面向对象和类型安全。使用C#开发基于.NET的应用程序,具有良好的安全性和跨平台性。C#用途广泛,可以开发Windows、ASP.NET和Web服务,甚至是Windows底层的各种不同类型的应用程序。C#的程序可以通过XML交换数据信息。因为XML是纯文本的信息,这就为通过C#开发的应用程序的跨平台性能提供了强大的保障。C#的程序运行方式也是独特的,其应用程序完全在.NET平台的管理下运行,这就大大地增加了应用程序的稳定性和安全性。
3系统分析
3.1系统需求分析
根据对OA公文流转系统的分析,系统功能包括:用户注册(包括注册用户名、姓名、密码和选择用户权限);用户登录;个人信息栏(可修改个人密码、看到用户自己的权限);收文批阅;发文批阅;查看历史文件记录等。
1)对于一个系统来说,用户管理必不可少,对于一个完整的OA系统,企业增加新员工也是必需的,针对用户需求,设计出了用户登录、用户注册页面。
2)本系统主要是针对OA的核心内容OA公文流转进行设计。
3)为了方便用户能够查阅已经进行了收发文件的批阅,设置了一个历史文件查询页面,针对有用户权限的用户进行查看。
3.2系统流程
有 判断 收发 图1 系统流程图
4系统模块划分
根据系统设计,可分为以下几个模块,如图所示:
图2 系统模块划分
用户注册 用户登录 收文批阅 发文批阅 查询收发文记录 用户管理 中小企业OA系统(OA公文流转)
5系统的实现
5.1数据库设计
根据对系统所需的模块分析,把数据库设计为三个表:用户表、收文表、发文表。具体内容如下图所示:
表1 用户表
名称
用户名(主键)
姓名 密码 权限
数据类型 varchar varchar varchar varchar
大小 50 50 50 50
是否为空 不为空 允许为空 允许为空 允许为空
表2 收文表
名称
顺序号(主键) 来文机关 来文ID 来文时间 事由 拟办单位 拟办人
数据类型 char varchar char datetime varchar varchar char
大小 9 50 10 8 50 50 10
是否为空 不为空 允许为空 允许为空 不为空 允许为空 允许为空 允许为空
填写处理签人 拟办日期 处理意见 处理意见填写人 领导意见 领导意见填写人 办理结果 办理结果填写人 char datetime varchar char varchar char varchar char 10 8 50 10 50 10 50 10 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空
表3发文表
名称
发文号(主键)
发文单位 拟稿人 审核人 会签 核发 签发 事由 送发单位 打字员 校对员 分发人
数据类型 char varchar char char varchar char char varchar varchar char char char
大小 9 50 10 10 50 10 10 50 50 10 10 10
是否为空 不为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空
5.2模块设计
5.2.1用户管理
用户管理模块包括用户登录、用户注册界面 5.2.1.1功能描述
如果某个用户想成为系统的合法用户,就必须通过用户注册功能申请合法帐号,且必须通过注册成功后才能使用。用户登录是系统重要组成部分,也是用户进入系统的唯一选择。
5.2.1.2用户注册和用户登录界面
5.2.2收文批阅 5.2.2.1功能描述
图3 注册登录界面图
收文处理是由办公室从网站上下载发布的公文、或者接收上级邮寄或者外来单位等形式发布的公文,为该公文填写收文笺,辅助进行收文过程的流转和收文资料的归档管理。处理过程有:填写处理签、填写处理意见、领导会签、部门会签。
5.2.2.1基本信息
表4处理笺信息表 数据项 来文机关 来文ID 来文时间 顺序ID 发送公文的上级机关名称 来文的编号,这是上级机关对公文的编号 公文发布时间 内部对公文的编号,由系统自动生成,为‘第XXXXXXXXX号’,其中的编号为9位数,当编号不到9位数时前面不允许用0填充,如:第1号,第100000001号 公文的名称,及其它信息 目前仅限办公室 由办公室文员拟办 接受并开始拟办公文的时间 由办公室主任填写,内容为需要哪些领导批示(会签意见),需要哪些部门阅处(阅读并会签意见,另外完成有关本部门的工作) 各个领导的会签意见汇总 各个部门的会签意见汇总 由办公室主任填写,内容为需要哪些领导批示(会签意见),需要哪些部说明 事由 拟办单位 拟办人 拟办时间 处理意见 领导批示 办理结果 处理意见 领导意见 办理结果 门阅处(阅读并会签意见,另外完成有关本部门的工作) 各个领导的会签意见汇总 各个部门的会签意见汇总
5.2.2.2流程
表5流程描述表 涉及对象 概述 办公室文员、办公室主任、相关领导、相关部门 收文处理是由办公室填写收文笺,办公室主任填写处理意见,并交由相关领导和部门阅读处理,最后由办公室归档。 步骤名称 办公室填写处理笺 办公室主任填写处理意见 分管领导会签 相关部门会签
办理人员 办公室文员 说明 文员得到公文,并填写《来文(电)处理用笺》,需要填写收文基本信息中的来文机关、来文ID、来文时间、事由、拟办人、拟办时间 办公室主任 填写处理意见,内容为需要哪些领导批示(会签意见),需要哪些部门阅处(阅读并会签意见,另外完成有关本部门的工作) 办公室文员、文员根据办公室主任的处理意见,向相关领导发出会相关领导 签请求,并汇总会签意见到收文基本信息中的领导批示 办公室文员、文员根据办公室主任的处理意见,向相关部门发出会相关部门 签请求,并汇总会签意见到收文基本信息中的办理结果 处理步骤 5.2.2.3收文笺样式
经收集整理,系统有一种收文笺,样式如下:
表6来文(电)处理用笺 来文 机关 来文2007-5-23 时间 事 由 拟办单位 拟办人 来文ID 顺序号 第100000001 号 拟办时间 处理意见 领导意见 办理结果 5.2.2.4代码实现 实现步骤如下所示:
private void caozuoqueren_Click(object sender, System.EventArgs e) {
string str;
if(Session[“CaoZuoQuanXian”].ToString().IndexOf(“填写处理笺”)!=-1)//填写处理意见,作判断 {
str=”insert into 收文表(顺序号,来文机关,来文ID,来文时间,事由,拟办单位,拟办人,填写处理笺人,拟办日期,处理意见填写人,领导意见填写人,办理结果填写人)”;
str+=”values
(‘”+bianhaoID+”’,’”+this.laiwenjiguan.Text+”’,’”
+this.laiwenbianhao.Text+”’,’”+this.laiwenshijian.Text+”’,’” +this.shiyou.Text+”’,”;
str+=”’” +this.nibandanwei.Text+”’,’”
+this.nibanren.Text+”’,’”+this.tianxieren.Text+”’,’”+this.nibanshijian.Text+”’,’’,’’,’’)”;
}//为生成一条sql语句并向收文表中插入一条消息 else {
str=”update 收文表 set “;
str+=”处理意见=’” +this.chuliyijian.Text+”’,处理意见填写人=’” +this.chuliyijianren.Text+”’,”;
str+=”领导意见=’” +this.lingdaoyijian.Text+”’,领导意见填写人=’” +this.lingdaoyijianren.Text+”’,”;
str+=”办理结果=’” +this.banlijieguo.Text+”’,办理结果填写人=’” +this.banlijieguoren.Text+”’ where 顺序号=’” +bianhaoID+”’”;
}//为生成一条sql语句,这个语句为了更新数据库收文表中的某一项 if(sql.UpdateDate(str))//通过上面生成的sql语句访问数据库 {
this.zhuangtai.Text=”操作成功”; this.caozuoqueren.Visible=false; this.quxiaocaozuo.Text=”返回主页”; } else
this.zhuangtai.Text=”操作失败,请注意数据完整性和格式,时间请用2007-4-20格式”; }
}
}
private void quxiaocaozuo_Click(object sender, System.EventArgs e) {
Response.Redirect(“main.aspx”); }
5.2.2.5收文签界面
5.2.3发文批阅 5.2.3.1功能描述
图4 收文签界面图
辅助各个部门拟发文稿,进行发文过程的流转和发文资料的归档管理。是一个单位对具有约束能力文件形成过程的一种管理。处理过程有:打字员、校对人、审核人、核发人、签发人、分发人。
5.2.3.2基本信息
表7发文笺信息表 数据项 发文单位 拟稿人 审核人 会签 核发 签发 事由 说明 拟发文稿的部门名称 拟发文稿的工作人员名称 发文单位(见上)的部门负责人签名 相关领导会签意见汇总 办公室主任签名 主要领导签名 发文的名称,以及发文的目的 送发单位 发文号 需要接受该发文的部门名称列表 由系统自动生成编号 打字员 校对员 分发人 发文内容的打字员,为打印室工作人员 发文内容的校对员,为办公室的文员 完成公文发放的人员,为办公室的文员
5.2.3.3流程
表8发文笺流程描述
涉及对象 概述 办公室文员、办公室主任、相关领导 由工作人员拟稿,交办公室核稿后,提交领导签发,如果需要再交相关领导会签,然后交办公室编号、打印室打印、办公室校稿,最后再分发。 步骤名称 拟稿 审稿 办公室主任核稿 分管领导核发 处理步骤 主要领导签发 编号 文件打印 分发 领导为签发人 办公室文员 打印员 办公室文员 办理人员 工作人员为打字员 负责人为校对员 办公室主任为审核人 核发人 说明 草拟发文的内容 检查并修改发文的内容 检查发文内容是否有错误 文员向分管领导发出核发请求,并汇总会签意见 签字 生成发文号 打印文件 文员检查打印员打印出的文档是否符合要求,不满足交打印员重新打印,分发公文
5.2.3.4发文稿样式
表9发文稿 主办单位及拟稿人 审 核 签 发 核 发 会 签 事 由 送 发 单 位 发文号 打 字 校 对 分 发 5.2.3.5代码实现 实现步骤如下:
private void caozuoqueren_Click(object sender, System.EventArgs e) {
string str;
if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"打字员\")!=-1)//判断进行这个操作的人是打字员还是其它人 {
str=\"insert into 发文表(会签,事由,送发单位,打字员,拟稿人,发文号,发文单位,校对员,审核人,核发,签发,分发人)\";
str+=\" values ('\"+this.huiqian.Text+\"','\"
+this.shiyou.Text+\"','\" +this.songfadanwei.Text+\"','\" +this.dazi.Text+\"',\"; str+=\"'\" +this.nigaoren.Text+\"','\" +bianhaoID+\"','\" +this.fawendanwei.Text+\"','','','','','')\";
}//生成一个sql语句,并向数据库发文表中插入一条新的数据 else {
str=\"update 发文表 set \";
str+=\"审核人='\" +this.shenhe.Text+\"',\"; str+=\"会签='\" +this.huiqian.Text+\"',\"; str+=\"核发='\" +this.hefa.Text+\"',\"; str+=\"签发='\" +this.qianfa.Text+\"',\"; str+=\"事由='\" +this.shiyou.Text+\"',\";
str+=\"送发单位='\" +this.songfadanwei.Text+\"',\"; str+=\"打字员='\" +this.dazi.Text+\"',\"; str+=\"校对员='\" +this.xiaodui.Text+\"',\"; str+=\"分发人='\" +this.fenfa.Text+\"'\"; str+=\" where 发文号='\" +bianhaoID+\"'\"; }//生成sql语句,用于更新数据库发文表中的记录
if(sql.UpdateDate(str))//通过上面的sql语句访问数据库 {
this.zhuangtai.Text=\"操作成功\"; this.caozuoqueren.Visible=false;
}
}
}
this.quxiaocaozuo.Text=\"返回主页\"; } else
this.zhuangtai.Text=\"请注意数据格式和完整性\";
private void quxiaocaozuo_Click(object sender, System.EventArgs e) {
Response.Redirect(\"main.aspx\"); }
5.2.3.6发文稿界面 如下图所示:
5.2.4历史文件查阅
图5 发文稿界面图
历史文件查阅主要针对具有收文和发文权限的用户查阅自己以前所做的一些工作,方便用户浏览以前的相关信息。
5.2.4.1功能描述
具有收文或者发文权限的用户所能查看到的工作记录。 5.2.4.2代码实现
实现步骤如下:
private void Page_Load(object sender, System.EventArgs e) {
this.time.Text=\"查询时刻:\"+System.DateTime.Now.ToString();//在界面上显示系统时间
if(Session[\"UserID\"].ToString()==\"admin\")//判断Session中的用户id是否为admin,如果是就进行下面的操作 {
this.dt1.DataSource=sql.SelectData(\"select * from 收文表\").Tables[0];
this.dt1.DataBind();
this.dt2.DataSource=sql.SelectData(\"select * from 发文表\").Tables [0];
this.dt2.DataBind (); }
if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"打字员\")!=-1)//打字员
{
fawenqx=\"打字员\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"校对员\")!=-1)//校对员 {
fawenqx=\"校对员\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"审核人\")!=-1)//审核人 {
fawenqx=\"审核人\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"核发人\")!=-1)//核发人 {
fawenqx=\"核发\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"签发人\")!=-1)//签发人 {
fawenqx=\"签发人\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"分发人\")!=-1)//分发人 {
fawenqx=\"分发人\"; }
else {
fawenqx=\"无发文查看权限\"; }
//下面也是判断相应的收文权限
if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"填写处理笺\")!=-1)//填写处理笺 {
shouwenqx=\"填写处理笺人\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"填写处理意见\")!=-1)//填写处理意见 {
shouwenqx=\"处理意见填写人\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"领导会签\")!=-1)//领导会签 {
shouwenqx=\"领导意见填写人\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"部门会签\")!=-1)//部门会签 {
shouwenqx=\"办理结果填写人\"; } else {
shouwenqx=\"无收文查看权限\"; }
//根据上面的第二个if-else if-else结构获得的权限信息,查询数据库,获得相应权限内收文表中的信息,并把数据库绑定到dt1中 try {
this.dt1.DataSource=sql.SelectData(\"select * from 收文表 where \"+shouwenqx+\"='\"+Session[\"UserID\"]+\"'\").Tables[0]; this.dt1.DataBind();
this.Label3.Text=\"
this.dt1.Visible=false;
this.Label3.Text=\"
//根据上面第一个if-else if-else结构,获得发文权限信息,查询数据库,把发文表中相应权限的信息查出来,绑定到dt2上 try {
this.dt2.DataSource=sql.SelectData(\"select * from 发文表 where \"+fawenqx+\"='\"+Session[\"UserID\"]+\"'\").Tables[0]; this.dt2.DataBind();
this.Label4.Text=\"
}
} catch {
this.dt2.Visible=false;
this.Label4.Text=\"
5.2.4.3收发文历史数据查询 界面如下图所示:
1) 具有发文权限的用户查询
图6发文历史数据查询
2) 具有收文权限的用户查询
5.2.5个人信息 5.2.5.1功能描述
图7收文签历史数据查询
在登录过程中,在此页面中用户可以查看到自己的权限分配以及修改个人密码。
5.2.5.2个人信息界面 如下图所示: 1)
具有收文权限的个人信息页面
图8收文信息界面
2) 具有发文权限的个人信息页面
图9发文信息界面
结 论
通过对整个基于B/S结构OA公文流转的设计与实现证明,本课题通过分析完成了中小企业公文流转的核心功能,包括用户管理模块中的用户注册、用户登录,收文批阅、发文批阅以及具有用户权限的用户所拥有的查阅收发文历史记录等。但本系统也存在些许的不足,比如说员工的权限分配应该是由上级分配,系统中的权限都公布给了所有用户为方便注册。这些问题希望能在今后的工作学习中进一步完善。对于一个完整的OA公文流转系统来说这仅仅是其中的一部分,接下来的功能扩展希望能够加强用户管理,增强用户信息一块。另外对于扩展部门功能也是重中之重。
参考文献
[1] 范玉顺.工作流管理技术基础[M].北京:清华大学出版社,1998。 [2] 张海藩.软件工程导论[M].北京:清华大学出版社,1998。
[3] 梁军.模型驱动的体系结构与元信息系统[M].北京:清华大学出版社,1998。
[4] Marco Bellinaso, Brady Gaster, Kevin Hoffman.高效掌握ASP.NET编程篇[M].北京:清华大学出版社,2002。
[5] 张友生,陈松乔.计算机工程与应用[M].西安:科学出版社,2002。
[6] 曹斌,韩中孝.ASP.NET数据库系统项目开发实践[M].西安:科学出版社,2005。 [7] 陈志泊.ASP.NET数据库应用程序开发[M].南京:人民邮电出版社,2005。 [8] 陈宗兴,杜国梁.网络系统开发[M].北京:中国水利水电出版社,2005。
致 谢
本文是在王敏老师的热情关心和指导下完成的,她渊博的知识和严谨的治学作风使我受益匪浅,对顺利完成本课题起到了极大的作用。在此向她表示我最衷心的感谢!
在论文完成过程中,本人还得到了很多老师和我们毕业设计小组同学的热心帮助,本人向他们表示深深的谢意!
最后向在百忙之中评审本文的各位专家、老师表示衷心的感谢!
作者简介:
姓 名:张涛 性别:女 出生年月:1985年3月 民族:汉 E-mail: peachchang2003@yahoo
声 明
本论文的工作是 2007年 2月至 2007年6月在成都信息工程学院网络工程系完成的。文中除了特别加以标注地方外,不包含他人已经发表或撰写过的研究成果,也不包含为获得成都信息工程学院或其他教学机构的学位或证书而使用过的材料。除非另有说明,本文的工作是原始性工作。
关于学位论文使用权和研究成果知识产权的说明:
本人完全了解成都信息工程学院有关保管使用学位论文的规定,其中包括: (1)学校有权保管并向有关部门递交学位论文的原件与复印件。 (2)学校可以采用影印、缩印或其他复制方式保存学位论文。 (3)学校可以学术交流为目的复制、赠送和交换学位论文。 (4)学校可允许学位论文被查阅或借阅。
(5)学校可以公布学位论文的全部或部分内容(保密学位论文在解密后遵守此规定)。
除非另有科研合同和其他法律文书的制约,本论文的科研成果属于成都信息工程学院。 特此声明!
作者签名:
毕业设计(论文)
中小企业OA系统的设计与实现
论文作者姓名: 申请学位专业: 申请学位类别: 指导教师姓名(职称): 论文提交日期:
中小企业
OA系统的设计与实现 摘 要
随着全球经济一体化进程的加快和信息技术的飞速发展,Internet技术及其应用给人们的日常生活和工作等各个方面带来了深刻的影响。网络应用技术的不断提高,企业对于相互之间的通讯能力提出了更高的要求。许多企业都具有一定信息化基础,有一定数量的信息设备和信息源,有相互连通的接口,需要实现消息的无缝传递。因此,为了创造出一个集成化的办公环境,提高办公效率和办公质量,就提出了办公自动化(Office Automation),简称OA。
本课题设计并开发了中小企业OA系统的公文流转模块,包括用户管理、收文批阅、发文批阅以及查阅历史文件等功能模块,系统基于B/S架构,采用C#.NET和SQL Server2000技术进行开发。
关键词:OA;收文批阅;发文批阅
Design and implement of OA system for mid- and
Small-scale enterprise
Abstract
Along with the global economy to accelerate the process of integration of information technology and the rapid development, the internet technology and its application has brought the profound influence on people's daily life and the work. With the unceasing enhancement of the network application technology,enterprises for mutual communication between the capacity of a higher demand. Many enterprises all have the certain information foundation, and have the certain quantity of the information equipments, the sources, and the joints which mutually connect. And it needs to realize the news seamless transmission. Therefore, in order to create an integrated work environment, enhance the office efficiency and the work quality, the office automation appears(Office Automation), called OA.
This topic designed and developed a document processing model of mid- and small-scale enterprises' OA system, including the function models like user management, reviewing the received document, the outgoing message reviews and consulting history file. The system is based on the B/S construction and is developed with C#. NET and SQL the Server2000 technology .
Key words: OA; Review the receiving document; Review the outgoing
document
目 录
论文总页数:19页
1引言................................................................................................................................................ 1 1.1课题背景 ....................................................................................................................................... 1 1.2研究现状分析 .............................................................................................................................. 1 1.3研究方法 ....................................................................................................................................... 1 2结构环境论述 ................................................................................................................................ 1 2.1开发环境及语言 .......................................................................................................................... 1 2.2 C#介绍 .......................................................................................................................................... 2 3系统分析 ........................................................................................................................................ 2 3.1系统需求分析 .............................................................................................................................. 2 3.2系统流程 ....................................................................................................................................... 3 4系统模块划分 ................................................................................................................................ 4 5系统的实现 .................................................................................................................................... 4 5.1数据库设计 ................................................................................................................................... 4 5.2模块设计 ....................................................................................................................................... 5 5.2.1用户管理 ............................................................................................................................... 5 5.2.2收文批阅 ............................................................................................................................... 6 5.2.3发文批阅 ............................................................................................................................... 9 5.2.4历史文件查阅 ..................................................................................................................... 12 5.2.5个人信息 ............................................................................................................................. 15 结 论 ......................................................................................................................................... 16 参考文献 ......................................................................................................................................... 17 致 谢 ......................................................................................................................................... 18 声 明 ........................................................................................................................................... 0
1引言
1.1课题背景
现代办公自动化系统被要求成为有效地信息采集和管理的平台,是以开放、
先进的Intranet技术及消息传递和工作流管理技术为核心的新一代全方位办公信息服务系统,成为一个资源中心和通信中心。它需要改进企业内部的通讯水平,将传统的办公模式发展为一个具有跨地域通讯能力、能够协同工作,并保持一致的办公环境,消除传统办公方式下的信息存储、管理和分布的障碍,充分实现信息共享、资源共享。通过建立OA系统,可以提高人们协同工作的效率,减少人工操作的重复操作和复杂程度;消除在传统办公中信息存储、分发、管理和分布的障碍,提高日常办公管理水平;为各级领导进行宏观管理提供高效便利的服务,并为科学决策提供有效的参考依据;改善企业内部的办公环境,便于办公人员及时掌握、管理各方信息,改善办公条件,规范办公流程,使管理水平进一步科学化和现代化。
1.2研究现状分析
网络办公已是现代化企业发展的大势所趋,传统的手工办公方式已经无法满足现代办公的需要,收发文管理系统为提高工作效率,规范办公制度,增强办公的透明性,实现信息、资源、文档的统一管理。是为方便领导决策,逐步实现无纸化办公的重要工具,越来越受到人们的重视。
1.3研究方法
本课题选择了B/S三层结构,后台数据库采SQL SERVER2000,WBE服务器运行微软的IIS,以及C#.NET作为开发工具,客户端用IE浏览器。B/S结构是在TCP/IP的支持下,以HTTP为传输协议,客户端通过Browser访问WEB服务器,以及与之相连的后台数据库的技术及体系结构,它由浏览器、Web服务器、应用服务器和数据库服务器组成。B/S模式突破了传统的文件共享及C/S模式,实现了更大程度的信息共享,任何用户只要通过浏览器即可访问数据库。B/S结构的工作原理是:客户端的浏览器通过URL访问Web服务器,Web服务器请求数据库服务器,并将获得的结果以HTML形式返回客户端浏览器。
2结构环境论述
2.1开发环境及语言
Microsoft® Windows™ XP Professional
Microsoft® Visual Studio 2003(C Sharp)
Microsoft® Developer Network for Visual Studio.NET 2003
2.2 C#介绍
C#是微软公司专门为.NET量身订制的新一代程序开发语言,它充分吸收了过去几十年中计算机科学发展的经验教训,体现了当前最新程序设计技术的功能和精华,从C#的身上可看到最突出的优点是:现代、简单、面向对象和类型安全。使用C#开发基于.NET的应用程序,具有良好的安全性和跨平台性。C#用途广泛,可以开发Windows、ASP.NET和Web服务,甚至是Windows底层的各种不同类型的应用程序。C#的程序可以通过XML交换数据信息。因为XML是纯文本的信息,这就为通过C#开发的应用程序的跨平台性能提供了强大的保障。C#的程序运行方式也是独特的,其应用程序完全在.NET平台的管理下运行,这就大大地增加了应用程序的稳定性和安全性。
3系统分析
3.1系统需求分析
根据对OA公文流转系统的分析,系统功能包括:用户注册(包括注册用户名、姓名、密码和选择用户权限);用户登录;个人信息栏(可修改个人密码、看到用户自己的权限);收文批阅;发文批阅;查看历史文件记录等。
1)对于一个系统来说,用户管理必不可少,对于一个完整的OA系统,企业增加新员工也是必需的,针对用户需求,设计出了用户登录、用户注册页面。
2)本系统主要是针对OA的核心内容OA公文流转进行设计。
3)为了方便用户能够查阅已经进行了收发文件的批阅,设置了一个历史文件查询页面,针对有用户权限的用户进行查看。
3.2系统流程
有 判断 收发 图1 系统流程图
4系统模块划分
根据系统设计,可分为以下几个模块,如图所示:
图2 系统模块划分
用户注册 用户登录 收文批阅 发文批阅 查询收发文记录 用户管理 中小企业OA系统(OA公文流转)
5系统的实现
5.1数据库设计
根据对系统所需的模块分析,把数据库设计为三个表:用户表、收文表、发文表。具体内容如下图所示:
表1 用户表
名称
用户名(主键)
姓名 密码 权限
数据类型 varchar varchar varchar varchar
大小 50 50 50 50
是否为空 不为空 允许为空 允许为空 允许为空
表2 收文表
名称
顺序号(主键) 来文机关 来文ID 来文时间 事由 拟办单位 拟办人
数据类型 char varchar char datetime varchar varchar char
大小 9 50 10 8 50 50 10
是否为空 不为空 允许为空 允许为空 不为空 允许为空 允许为空 允许为空
填写处理签人 拟办日期 处理意见 处理意见填写人 领导意见 领导意见填写人 办理结果 办理结果填写人 char datetime varchar char varchar char varchar char 10 8 50 10 50 10 50 10 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空
表3发文表
名称
发文号(主键)
发文单位 拟稿人 审核人 会签 核发 签发 事由 送发单位 打字员 校对员 分发人
数据类型 char varchar char char varchar char char varchar varchar char char char
大小 9 50 10 10 50 10 10 50 50 10 10 10
是否为空 不为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空 允许为空
5.2模块设计
5.2.1用户管理
用户管理模块包括用户登录、用户注册界面 5.2.1.1功能描述
如果某个用户想成为系统的合法用户,就必须通过用户注册功能申请合法帐号,且必须通过注册成功后才能使用。用户登录是系统重要组成部分,也是用户进入系统的唯一选择。
5.2.1.2用户注册和用户登录界面
5.2.2收文批阅 5.2.2.1功能描述
图3 注册登录界面图
收文处理是由办公室从网站上下载发布的公文、或者接收上级邮寄或者外来单位等形式发布的公文,为该公文填写收文笺,辅助进行收文过程的流转和收文资料的归档管理。处理过程有:填写处理签、填写处理意见、领导会签、部门会签。
5.2.2.1基本信息
表4处理笺信息表 数据项 来文机关 来文ID 来文时间 顺序ID 发送公文的上级机关名称 来文的编号,这是上级机关对公文的编号 公文发布时间 内部对公文的编号,由系统自动生成,为‘第XXXXXXXXX号’,其中的编号为9位数,当编号不到9位数时前面不允许用0填充,如:第1号,第100000001号 公文的名称,及其它信息 目前仅限办公室 由办公室文员拟办 接受并开始拟办公文的时间 由办公室主任填写,内容为需要哪些领导批示(会签意见),需要哪些部门阅处(阅读并会签意见,另外完成有关本部门的工作) 各个领导的会签意见汇总 各个部门的会签意见汇总 由办公室主任填写,内容为需要哪些领导批示(会签意见),需要哪些部说明 事由 拟办单位 拟办人 拟办时间 处理意见 领导批示 办理结果 处理意见 领导意见 办理结果 门阅处(阅读并会签意见,另外完成有关本部门的工作) 各个领导的会签意见汇总 各个部门的会签意见汇总
5.2.2.2流程
表5流程描述表 涉及对象 概述 办公室文员、办公室主任、相关领导、相关部门 收文处理是由办公室填写收文笺,办公室主任填写处理意见,并交由相关领导和部门阅读处理,最后由办公室归档。 步骤名称 办公室填写处理笺 办公室主任填写处理意见 分管领导会签 相关部门会签
办理人员 办公室文员 说明 文员得到公文,并填写《来文(电)处理用笺》,需要填写收文基本信息中的来文机关、来文ID、来文时间、事由、拟办人、拟办时间 办公室主任 填写处理意见,内容为需要哪些领导批示(会签意见),需要哪些部门阅处(阅读并会签意见,另外完成有关本部门的工作) 办公室文员、文员根据办公室主任的处理意见,向相关领导发出会相关领导 签请求,并汇总会签意见到收文基本信息中的领导批示 办公室文员、文员根据办公室主任的处理意见,向相关部门发出会相关部门 签请求,并汇总会签意见到收文基本信息中的办理结果 处理步骤 5.2.2.3收文笺样式
经收集整理,系统有一种收文笺,样式如下:
表6来文(电)处理用笺 来文 机关 来文2007-5-23 时间 事 由 拟办单位 拟办人 来文ID 顺序号 第100000001 号 拟办时间 处理意见 领导意见 办理结果 5.2.2.4代码实现 实现步骤如下所示:
private void caozuoqueren_Click(object sender, System.EventArgs e) {
string str;
if(Session[“CaoZuoQuanXian”].ToString().IndexOf(“填写处理笺”)!=-1)//填写处理意见,作判断 {
str=”insert into 收文表(顺序号,来文机关,来文ID,来文时间,事由,拟办单位,拟办人,填写处理笺人,拟办日期,处理意见填写人,领导意见填写人,办理结果填写人)”;
str+=”values
(‘”+bianhaoID+”’,’”+this.laiwenjiguan.Text+”’,’”
+this.laiwenbianhao.Text+”’,’”+this.laiwenshijian.Text+”’,’” +this.shiyou.Text+”’,”;
str+=”’” +this.nibandanwei.Text+”’,’”
+this.nibanren.Text+”’,’”+this.tianxieren.Text+”’,’”+this.nibanshijian.Text+”’,’’,’’,’’)”;
}//为生成一条sql语句并向收文表中插入一条消息 else {
str=”update 收文表 set “;
str+=”处理意见=’” +this.chuliyijian.Text+”’,处理意见填写人=’” +this.chuliyijianren.Text+”’,”;
str+=”领导意见=’” +this.lingdaoyijian.Text+”’,领导意见填写人=’” +this.lingdaoyijianren.Text+”’,”;
str+=”办理结果=’” +this.banlijieguo.Text+”’,办理结果填写人=’” +this.banlijieguoren.Text+”’ where 顺序号=’” +bianhaoID+”’”;
}//为生成一条sql语句,这个语句为了更新数据库收文表中的某一项 if(sql.UpdateDate(str))//通过上面生成的sql语句访问数据库 {
this.zhuangtai.Text=”操作成功”; this.caozuoqueren.Visible=false; this.quxiaocaozuo.Text=”返回主页”; } else
this.zhuangtai.Text=”操作失败,请注意数据完整性和格式,时间请用2007-4-20格式”; }
}
}
private void quxiaocaozuo_Click(object sender, System.EventArgs e) {
Response.Redirect(“main.aspx”); }
5.2.2.5收文签界面
5.2.3发文批阅 5.2.3.1功能描述
图4 收文签界面图
辅助各个部门拟发文稿,进行发文过程的流转和发文资料的归档管理。是一个单位对具有约束能力文件形成过程的一种管理。处理过程有:打字员、校对人、审核人、核发人、签发人、分发人。
5.2.3.2基本信息
表7发文笺信息表 数据项 发文单位 拟稿人 审核人 会签 核发 签发 事由 说明 拟发文稿的部门名称 拟发文稿的工作人员名称 发文单位(见上)的部门负责人签名 相关领导会签意见汇总 办公室主任签名 主要领导签名 发文的名称,以及发文的目的 送发单位 发文号 需要接受该发文的部门名称列表 由系统自动生成编号 打字员 校对员 分发人 发文内容的打字员,为打印室工作人员 发文内容的校对员,为办公室的文员 完成公文发放的人员,为办公室的文员
5.2.3.3流程
表8发文笺流程描述
涉及对象 概述 办公室文员、办公室主任、相关领导 由工作人员拟稿,交办公室核稿后,提交领导签发,如果需要再交相关领导会签,然后交办公室编号、打印室打印、办公室校稿,最后再分发。 步骤名称 拟稿 审稿 办公室主任核稿 分管领导核发 处理步骤 主要领导签发 编号 文件打印 分发 领导为签发人 办公室文员 打印员 办公室文员 办理人员 工作人员为打字员 负责人为校对员 办公室主任为审核人 核发人 说明 草拟发文的内容 检查并修改发文的内容 检查发文内容是否有错误 文员向分管领导发出核发请求,并汇总会签意见 签字 生成发文号 打印文件 文员检查打印员打印出的文档是否符合要求,不满足交打印员重新打印,分发公文
5.2.3.4发文稿样式
表9发文稿 主办单位及拟稿人 审 核 签 发 核 发 会 签 事 由 送 发 单 位 发文号 打 字 校 对 分 发 5.2.3.5代码实现 实现步骤如下:
private void caozuoqueren_Click(object sender, System.EventArgs e) {
string str;
if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"打字员\")!=-1)//判断进行这个操作的人是打字员还是其它人 {
str=\"insert into 发文表(会签,事由,送发单位,打字员,拟稿人,发文号,发文单位,校对员,审核人,核发,签发,分发人)\";
str+=\" values ('\"+this.huiqian.Text+\"','\"
+this.shiyou.Text+\"','\" +this.songfadanwei.Text+\"','\" +this.dazi.Text+\"',\"; str+=\"'\" +this.nigaoren.Text+\"','\" +bianhaoID+\"','\" +this.fawendanwei.Text+\"','','','','','')\";
}//生成一个sql语句,并向数据库发文表中插入一条新的数据 else {
str=\"update 发文表 set \";
str+=\"审核人='\" +this.shenhe.Text+\"',\"; str+=\"会签='\" +this.huiqian.Text+\"',\"; str+=\"核发='\" +this.hefa.Text+\"',\"; str+=\"签发='\" +this.qianfa.Text+\"',\"; str+=\"事由='\" +this.shiyou.Text+\"',\";
str+=\"送发单位='\" +this.songfadanwei.Text+\"',\"; str+=\"打字员='\" +this.dazi.Text+\"',\"; str+=\"校对员='\" +this.xiaodui.Text+\"',\"; str+=\"分发人='\" +this.fenfa.Text+\"'\"; str+=\" where 发文号='\" +bianhaoID+\"'\"; }//生成sql语句,用于更新数据库发文表中的记录
if(sql.UpdateDate(str))//通过上面的sql语句访问数据库 {
this.zhuangtai.Text=\"操作成功\"; this.caozuoqueren.Visible=false;
}
}
}
this.quxiaocaozuo.Text=\"返回主页\"; } else
this.zhuangtai.Text=\"请注意数据格式和完整性\";
private void quxiaocaozuo_Click(object sender, System.EventArgs e) {
Response.Redirect(\"main.aspx\"); }
5.2.3.6发文稿界面 如下图所示:
5.2.4历史文件查阅
图5 发文稿界面图
历史文件查阅主要针对具有收文和发文权限的用户查阅自己以前所做的一些工作,方便用户浏览以前的相关信息。
5.2.4.1功能描述
具有收文或者发文权限的用户所能查看到的工作记录。 5.2.4.2代码实现
实现步骤如下:
private void Page_Load(object sender, System.EventArgs e) {
this.time.Text=\"查询时刻:\"+System.DateTime.Now.ToString();//在界面上显示系统时间
if(Session[\"UserID\"].ToString()==\"admin\")//判断Session中的用户id是否为admin,如果是就进行下面的操作 {
this.dt1.DataSource=sql.SelectData(\"select * from 收文表\").Tables[0];
this.dt1.DataBind();
this.dt2.DataSource=sql.SelectData(\"select * from 发文表\").Tables [0];
this.dt2.DataBind (); }
if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"打字员\")!=-1)//打字员
{
fawenqx=\"打字员\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"校对员\")!=-1)//校对员 {
fawenqx=\"校对员\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"审核人\")!=-1)//审核人 {
fawenqx=\"审核人\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"核发人\")!=-1)//核发人 {
fawenqx=\"核发\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"签发人\")!=-1)//签发人 {
fawenqx=\"签发人\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"分发人\")!=-1)//分发人 {
fawenqx=\"分发人\"; }
else {
fawenqx=\"无发文查看权限\"; }
//下面也是判断相应的收文权限
if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"填写处理笺\")!=-1)//填写处理笺 {
shouwenqx=\"填写处理笺人\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"填写处理意见\")!=-1)//填写处理意见 {
shouwenqx=\"处理意见填写人\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"领导会签\")!=-1)//领导会签 {
shouwenqx=\"领导意见填写人\"; }
else if(Session[\"CaoZuoQuanXian\"].ToString().IndexOf(\"部门会签\")!=-1)//部门会签 {
shouwenqx=\"办理结果填写人\"; } else {
shouwenqx=\"无收文查看权限\"; }
//根据上面的第二个if-else if-else结构获得的权限信息,查询数据库,获得相应权限内收文表中的信息,并把数据库绑定到dt1中 try {
this.dt1.DataSource=sql.SelectData(\"select * from 收文表 where \"+shouwenqx+\"='\"+Session[\"UserID\"]+\"'\").Tables[0]; this.dt1.DataBind();
this.Label3.Text=\"
this.dt1.Visible=false;
this.Label3.Text=\"
//根据上面第一个if-else if-else结构,获得发文权限信息,查询数据库,把发文表中相应权限的信息查出来,绑定到dt2上 try {
this.dt2.DataSource=sql.SelectData(\"select * from 发文表 where \"+fawenqx+\"='\"+Session[\"UserID\"]+\"'\").Tables[0]; this.dt2.DataBind();
this.Label4.Text=\"
}
} catch {
this.dt2.Visible=false;
this.Label4.Text=\"
5.2.4.3收发文历史数据查询 界面如下图所示:
3) 具有发文权限的用户查询
图6发文历史数据查询
4) 具有收文权限的用户查询
5.2.5个人信息 5.2.5.1功能描述
图7收文签历史数据查询
在登录过程中,在此页面中用户可以查看到自己的权限分配以及修改个人密码。
5.2.5.2个人信息界面 如下图所示: 3)
具有收文权限的个人信息页面
图8收文信息界面
4) 具有发文权限的个人信息页面
图9发文信息界面
结 论
通过对整个基于B/S结构OA公文流转的设计与实现证明,本课题通过分析完成了中小企业公文流转的核心功能,包括用户管理模块中的用户注册、用户登录,收文批阅、发文批阅以及具有用户权限的用户所拥有的查阅收发文历史记录等。但本系统也存在些许的不足,比如说员工的权限分配应该是由上级分配,系统中的权限都公布给了所有用户为方便注册。这些问题希望能在今后的工作学习中进一步完善。对于一个完整的OA公文流转系统来说这仅仅是其中的一部分,接下来的功能扩展希望能够加强用户管理,增强用户信息一块。另外对于扩展部门功能也是重中之重。
参考文献
[1] 范玉顺.工作流管理技术基础[M].北京:清华大学出版社,1998。 [2] 张海藩.软件工程导论[M].北京:清华大学出版社,1998。
[3] 梁军.模型驱动的体系结构与元信息系统[M].北京:清华大学出版社,1998。
[4] Marco Bellinaso, Brady Gaster, Kevin Hoffman.高效掌握ASP.NET编程篇[M].北京:清华大学出版社,2002。
[5] 张友生,陈松乔.计算机工程与应用[M].西安:科学出版社,2002。
[6] 曹斌,韩中孝.ASP.NET数据库系统项目开发实践[M].西安:科学出版社,2005。 [7] 陈志泊.ASP.NET数据库应用程序开发[M].南京:人民邮电出版社,2005。 [8] 陈宗兴,杜国梁.网络系统开发[M].北京:中国水利水电出版社,2005。
致 谢
本文是在王敏老师的热情关心和指导下完成的,她渊博的知识和严谨的治学作风使我受益匪浅,对顺利完成本课题起到了极大的作用。在此向她表示我最衷心的感谢!
在论文完成过程中,本人还得到了很多老师和我们毕业设计小组同学的热心帮助,本人向他们表示深深的谢意!
最后向在百忙之中评审本文的各位专家、老师表示衷心的感谢!
作者简介:
姓 名:张涛 性别:女 出生年月:1985年3月 民族:汉 E-mail: peachchang2003@yahoo
声 明
本论文的工作是 2007年 2月至 2007年6月在成都信息工程学院网络工程系完成的。文中除了特别加以标注地方外,不包含他人已经发表或撰写过的研究成果,也不包含为获得成都信息工程学院或其他教学机构的学位或证书而使用过的材料。除非另有说明,本文的工作是原始性工作。
关于学位论文使用权和研究成果知识产权的说明:
本人完全了解成都信息工程学院有关保管使用学位论文的规定,其中包括: (1)学校有权保管并向有关部门递交学位论文的原件与复印件。 (2)学校可以采用影印、缩印或其他复制方式保存学位论文。 (3)学校可以学术交流为目的复制、赠送和交换学位论文。 (4)学校可允许学位论文被查阅或借阅。
(5)学校可以公布学位论文的全部或部分内容(保密学位论文在解密后遵守此规定)。
除非另有科研合同和其他法律文书的制约,本论文的科研成果属于成都信息工程学院。 特此声明!
作者签名:
sounds that were a lot like laughter. 'You think it's funny, huh?' Weary inquired. He walked around to Billy's back. Billy's jacket and shirt and undershirt had been hauled up around his shoulders by the violence, so his back was naked. There, inches from the tips of Weary's combat boots, were the pitiful buttons of Billy's spine.
Weary drew back his right boot, aimed a kick at the spine, at the tube which had so many of Billy's important wires in it. Weary was going to break that tube.
But then Weary saw that he had an audience. Five German soldiers and a police dog on a leash were looking down into the bed of the creek. The soldiers' blue eyes were filled with bleary civilian curiosity as to why one American would try to murder another one so far from home, and why the victim should laugh. Three
The Germans and the dog were engaged in a military operation which had an amusingly self-explanatory name, a human enterprise which is seldom described in detail, whose name alone, when reported as news or history, gives many war enthusiasts a sort of post-coital satisfaction. It is, in the imagination of combat's fans, the divinely listless loveplay that follows the orgasm of victory. It is called 'mopping up.' The dog, who had sounded so ferocious in the winter distances, was a female German shepherd. She was shivering. Her tail was between her legs. She had been borrowed that morning from a farmer. She had never been to war before. She had no idea what game was being played. Her mine was Princess.
Two of the Germans were boys in their early teens. Two were ramshackle old me droolers as toothless as carp. They were irregulars, armed and clothed fragmentarily with junk taken from real soldiers who were newly dead. So it goes. They were farmers from just across the German border, not far away.
Their commanander was a middle-aged corporal-red-eyed., scrawny, tough as dried beef, sick of war. He had been wounded four times-and patched up, and sent back to war. He was a very good soldier-about to quit, about to find somebody to surrender to. His bandy legs were thrust into golden cavalry boots which he had taken from a dead Hungarian colonel on the Russian front. So it goes. Those boots were almost all he owned in this world. They were his home. An anecdote: One time a recruit was watching him bone and wax those golden boots, and he held one up to the recruit and said, 'If you look in there deeply enough, you'll see Adam and Eve.'
Billy Pilgrim had not heard this anecdote. But, lying on the black ice there, Billy stared into the patina of the corporal's boots, saw Adam and Eve in the golden depths. They were naked. They were so innocent, so vulnerable, so eager to behave decently. Billy Pilgrim loved them.
Next to the golden boots were a pair of feet which were swaddled in rags. They were crisscrossed by canvas straps, were shod with hinged wooden clogs. Billy looked up at the face that went with the clogs. It was the face of a blond angel of fifteen-year-old boy. The boy was as beautiful as Eve.
Billy was helped to his feet by the lovely boy, by the heavenly androgyne. And the others came forward to dust the snow off Billy., and then they searched him for weapons. He didn't have any. The most dangerous thing they found on his person was a two-inch pencil stub.
Three inoffensive bangs came from far away. They came from German rifles. The two scouts who had ditched Billy and Weary had just been shot. They had been lying in ambush for Germans. They had been discovered and shot from behind. Now they were dying in the snow, feeling nothing, turning the snow to the color of raspberry sherbet. So it goes. So Roland Weary was the last of the Three Musketeers.
And Weary, bug-eyed with terror, was being disarmed. The corporal gave Weary's pistol to the pretty boy. He marveled at Weary's cruel trench knife, said in German that Weary would no doubt like to use the knife on him, to tear his face off with the spiked knuckles, to stick the blade into his belly or throat. He spoke no English, and Billy and Weary understood no German. 'Nice playthings you have, the corporal told Weary, and he handed the knife to an old man. 'Isn't that a pretty thing? Hmmm?
He tore open Weary's overcoat and blouse. Brass buttons flew like popcorn. The corporal reached into Weary's gaping bosom as though he meant to tear out his pounding heart, but he brought out Weary's bulletproof Bible instead.
A bullet-proof Bible is a Bible small enough to be slipped into a soldier's breast pocket, over his heart. It is sheathed in steel.
The corporal found the dirty picture of the woman and the pony in Weary's hip pocket. 'What a lucky pony, eh?' he said. \"Hmmmm? Hmmmm? Don't you wish you were that pony?' He handed the picture to the other old man. 'Spoils of war! It's all yours, you lucky lad.'
Then he made Weary sit down in the snow and take off his combat boots, which he gave to the beautiful boy. He gave Weary, the boy's clogs. So Weary and Billy were both without decent military footwear now' and they had to walk for miles and miles, with Weary's clogs clacking, with Billy bobbing up-and-down, up-and-down, crashing into Weary from time to time. 'Excuse me,' Billy would say, or 'I beg your pardon.'
They were brought at last to a stone cottage at a fork in the road. It was a collecting point for prisoners of war. Billy and Weary were taken inside, where it was warm and smoky. There vas a fire sizzling and popping in the fireplace. The fuel was furniture. There were about twenty other Americans in there, sitting on the floor with their backs to the wall, staring into the flames-thinking whatever there was to think, which was zero.
Nobody talked. Nobody had any good war stories to tell.
Billy and Weary found places for themselves, and Billy went to sleep with his head on the shoulder of an unprotesting captain. The captain was a chaplain. He was a rabbi. He had been shot through the hand.
Billy traveled in time, opened his eyes, found himself staring into the glass eyes of a jade green mechanical owl. The owl was hanging upside down from a rod of stainless steel. The owl was Billy's optometer in his office in Ilium. An optometer is an instrument for measuring refractive errors in eyes-in order that corrective lenses may be prescribed.
Billy had fallen asleep while examining a female patient who was m a chair on the other side of the owl. He had fallen asleep at work before. It had been funny at first. Now Billy was starting to get worried about it, about his mind in general. He tried to remember how old he was, couldn't. He tried to remember what year it was. He couldn't remember that, either. 'Doctor,' said the patient tentatively. 'Hm?' he said. 'You're so quiet.' 'Sorry.'
'You were talking away there-and then you got so quiet' 'Um.'
'You see something terrible?' 'Terrible?'
'Some disease in my anslated by David Lewis
The elderly man stroked the dogpillar's head. \"This fellow here, I wonder what he was called before he became a dogpillar.\" \"No calling a dogpillar by its original name,\" I said. \"Isn't that a strange law?\"
The man gave me a quick glance, then replied casually. \"Didn't they just extend the laws concerning people to dogs? That's why they lose their names when they become dogpillars.\"
He nodded while scratching the dogpillar's jaw. \"Not only the old names, but you can't give them new names, either. That's because there are no proper nouns for plants.\" Why, of course, I thought.
He Looked at my envelope with MANUSCRIPT ENCLOSED written on it. \"Excuse me,\" he said. \"Are you a writer?\" I was a little embarrassed. \"Well. yes. Just trivial little things.\"
\"So that's it.\" After looking at me closely, the man returned to stroking the dogpillar's head. \"I also used to write things.\" He managed to suppress a smile.
\"How many years is it now since I stopped writing? It feels like a long time.\"
I stared at the man's profile. Now that he said so, it was a face I seemed to have seen somewhere before. I started to ask his name, hesitated, and fell silent. The elderly man said abruptly, \"It's become a hard world to write in.\"
I lowered my eyes, ashamed of myself, who still continued to write in such a world. \"It certainly has...\" The man apologized in a bit of a flurry discerning my sudden depression. \"That was rude. I'm not criticizing you. I'm the one who should feel ashamed.\"
\"No,\" I told him, after looking quickly around us, \"I can't give up writing because I haven't the courage. Giving up writing! Why, after all, that would be a gesture against society.\" The elderly man continued stroking the dogpillar. After a long while he spoke.
\"It's painful, suddenly giving up writing. Now that it's come to this, I would have been better off if I'd gone on boldly writing social criticism and had been arrested. There are even times when I think that.
But I was just a dilettante, never knowing poverty, craving peaceful dreams. I wanted to live a comfortable life. As a person strong in self- respect, I couldn't endure being exposed to the eyes of the world, ridiculed. So I quit writing, A sorry tale.\"
He smiled and shook his head. \"No no, let's not talk about it. You never know where someone might be listening.\" \"You're right.\" I changed the subject. \"Do you live near here?\"
\"Do you know the beauty parlor on the main street? You turn in there. My name is Hiyama.\" He nodded at me. \"Come on over sometime. There's no one home but my wife.\" \"Thank you
very much.\" I gave him my own name. I didn't remember any writer named Hiyama. No doubt he wrote under a pen name. I had no intention of visiting his house. This is a world where even two or three writers getting together is considered illegal assembly. \"It's time for the mail truck to come.\" Talking pains to look at my watch, I stood up. \"I'm afraid I'd better go,\" I said.
He turned a sadly smiling face toward me and bowed slightly. After stroking the dogpillar's head a little, I left the park.
Standing Woman(2)---
I came out on the main street, there were a lot of cars on the road but few pedestrians. A cattree about thirty to forty centimeters high was planted next to the sidewalk. Sometimes I come across a catpillar that has just been planted and still hasn't become a cattree.
New catpillars look at my face and meow or cry, but the ones where all four limbs planted in the ground have vegetized, with their greenish faces stiffly set and their eyes shut tight, only move their ears now and then.
Then there are catpillars that grow branches from their bodies and put out handfuls of leaves.
The mental condition of there seems to be completely vegetized •| they don't even move their ears. Even if you can still make out a cat's face, it may be better to call these cattrees.
Maybe. I thought, it's better to make dogs into dogpillars. When their food runs out, they get vicious and even turn on people. But why did they have to turn cats into catpillars? Too many strays? To improve the food situation even a little? Or perhaps for the greening of the city ...
Next to the big hospital on the corner where the roads cross are two mantrees, and ranged alongside these trees is a manpillar. This manpillar wears a postman's uniform, and you can't tell how far its legs have vegetized because of its trousers. It is male, thirty-five or thirty-six years old, tall, with a bit of a stoop. I approached him and held out my envelope as always. \"Registered mail, special delivery, please.\"
The manpillar, nodding silently, accepted the envelope and took stamps and a registered mail slip from his pocket.
I looked around quickly after paying the postage. There was no one else there. I decided to try speaking to him. I had been giving him mail every three days, but I still hadn't had an opportunity chance for a leisurely talk.
\"What did you do?\" I asked in a low voice.
The manpillar looked at me in surprise. Then, after running his eyes around the area, he answered with a sour look, \"Won't do to go saying unnecessary things to me. Even me, I'm not supposed to answer.\" ways been, the wonted way of things.
Spitz was a practiced fighter. From Spitzbergen through the Arctic, and across Canada and the Barrens, he had held his own with all manner of dogs and achieved to mastery over them. Bitter rage was his, but never blind rage. In passion to rend and destroy, he never forgot that his enemy was in like passion to rend and destroy. He never rushed till he was prepared to receive a rush; never attacked till he had first defended that attack.
In vain Buck strove to sink his teeth in the neck of the big white dog. Wherever his fangs struck for the softer flesh, they were countered by the fangs of Spitz. Fang clashed fang, and lips were cut and bleeding, but Buck could not penetrate his enemy's guard. Then he warmed up and enveloped Spitz in a whirlwind of rushes. Time and time again he tried for the snow-white throat, where life bubbled near to the surface, and each time and every time Spitz slashed him and got away. Then Buck took to rushing, as though for the throat, when, suddenly drawing back his head and curving in from the side, he would drive his shoulder at the shoulder of Spitz, as a ram by which to overthrow him. But instead, Buck's shoulder was slashed down each time as Spitz leaped lightly away.
Spitz was untouched, while Buck was streaming with blood and panting hard. The fight was growing desperate. And all the while the silent and wolfish circle waited to finish off whichever dog went down. As Buck grew winded, Spitz took to rushing, and he kept him staggering for footing. Once Buck went over, and the whole circle of sixty dogs started up; but he recovered himself, almost in mid air, and the circle sank down again and waited.
But Buck possessed a quality that made for greatness--imagination. He fought by instinct, but he could fight by head as well he rushed, as though attempting the old shoulder trick, but at the last instant swept low to the snow and in. His teeth closed on Spitz's left fore leg. There was a crunch of breaking bone, and the white dog faced him on three legs. Thrice he tried to knock him over, then repeated the trick and broke the right fore leg. Despite the pain and helplessness, Spitz struggled madly to keep up. He saw the silent circle, with gleaming eyes, lolling tongues, and silvery breaths drifting upward, closing in upon him as he had seen similar circles close in upon beaten antagonists in the past. Only this time he was the one who was beaten.
There was no hope for him. Buck was inexorable. Mercy was a thing reserved for gentler climes. He maneuvered for the final rush. The circle had tightened till he could feel the breaths of the huskies on his flanks. He could see them, beyond Spitz and to either side, half-crouching for the spring, their eyes fixed upon him. A pause seemed to fall. Every animal was motionless as though turned to stone. Only Spitz quivered and bristled as he staggered back and forth, snarling with horrible menace, as though to frighten off impending death. Then Buck sprang in and out; but while he was in, shoulder had at last squarely met shoulder. The dark circle became a dot on the moon flooded snow as Spitz disappeared from view. Buck stood and looked on, the successful champion, the dominant primordial beast who had made his
kill and found it good. away.
At the Pelly one morning, as they were harnessing up, dolly, who had never been conspicuous for anything, went suddenly mad. She announced her condition by a long, heart-breaking wolf howl that sent every dog bristling with fear, then sprang straight for Buck. He had never seen a dog go mad, nor did he have any reason to fear madness; yet he knew that here was horror, and fled away from it in a panic. Straight away he raced, with Dolly, panting and frothing, one leap behind; nor could she gain on him, so great was his terror, nor could he leave her, so great was her madness. He plunged through the wooded breast of the island, flew down to the lower end, crossed a back channel filled with rough ice to another island, gained a third island, curved back to the main river, and in desperation started to cross it. And all the time, though he did not look, he could hear her snarling just one leap behind. Francois called to him a quarter of a mile away and he doubled back, still one leap ahead, gasping painfully for air and putting all his faith in that Francois would save him. the dog-driver held the axe poised in his hand, and as Buck shot past him the axe crashed down upon mad Dolly's head.
Buck staggered over against the sled, exhausted, sobbing for breath, helpless. This was Spitz's opportunity. He sprang upon Buck, and twice his teeth sank into his unresisting foe and ripped and tore the flesh to the bone. Then Francois' lash descended, and Buck had the satisfaction of watching Spitz receive the worst whipping as yet administered to any of the team. \"One devil, dat Spitz,\" remarked Perrault. \"Some dam day him kill dat Buck.\"
\"Dat Buck two devils,\" was Francois's rejoinder. \"All de time I watch dat Buck I know for sure. Lissen: some dam fine day him get mad like hell and den him chew dat Spitz all up and spit him out on de snow. Sure, I know.\"
From then on it was war between them. Spitz, as lead-dog and acknowledged master of the team, felt his supremacy threatened by this strange Southland dog.F And strange Buck was to him, for of the many Southland dogs he had known, not one had shown up worthily in camp and on trail. They were all too soft, dying under the toil, the frost, and starvation. Buck was the exception. He alone endured and prospered, matching the husky in strength, savagery, and cunning.E Then he was a masterful dog, and what made him dangerous was the fact that the club of the man in the red sweater had knocked all blind pluck and rashness out of his desire for mastery. He was preeminently cunning, and could bide his time with a patience that was nothing less than primitive. PART 3
Mulan: Okay, okay, how 'bout this? Ahem, [in her manly voice] excuandanother man picking out dirt from between his toes with chopsticks] Beautifulisn't it? Mulan [making a face of disgust and continuing to walk]: They're disgusting.
Mushu: No, they're men. And you're going to have to act just like them, sopay attention. [Mulan stops and watches Yao, Ling, Chien-Po and Tattoo Soldier]
Tattoo Soldier [showing the dragon tattoo on his chest and belly]: Look, thistattoo will protect me from harm. [Yao thi
Shang: What's your name?
Mulan [stumbling]: Ahh, I, uhhh, I, uh--
Chi Fu [stepping into Mulan's face]: Your commanding officer just asked you a question. Mulan: Uhh, I've got a name. Huh. And it's a boys name too. Mushu [from the back of Mulan]: Ling, How 'bout Ling?
Mulan [to Mushu motioning with her head to Ling]: His name's Ling. Shang: I didn't ask for his name. I asked for yours. Mushu: Try, uh, ahh, Chu! Mulan: Ah Chu. Shang: Ah Chu?
Mushu: Gesundheit. He He, I kill myself. Mulan [whispering over her shoulder]: Mushu. Shang: Mushu? Mulan: No.
Shang: Then what is it!
Mushu: Ping! Ping was my best friend growing up!
Mulan: It's Ping. Shang: Ping.
Mushu: Of course Ping DID steal my gir-[Mulan reaches back and grabs holds Mushu's mouth together] Mulan: Yes, my name is Ping.
Shang: Let me see your conscription notice. [Takes the notice from Mulan] Fa Zhou, *the* Fa Zhou? Chi Fu: I didn't know Fa Zhou had a son.
Mulan: Um, he...doesn't talk about me much. [Mulan tries to hawk up a loogie and spit but the saliva just runs from her mouth. Therecruits laugh] Chi Fu: I can see why, the boy's an absolute lunatic.
Shang [to the recruits]: Okay gentlemen, thanks to your new friend Ping, you'll spend tonight picking up every single grain of rice. Andtomorrow, the real work begins. [All recruits growl at Mulan]
Mushu [Popping out the front of Mulan's armor]: You know, we have to work on your people skills. [Cut to Mulan sleeping in her tent. Mushu winds up Cri-Kee's wings. Cri-Kee rings like an alarm clock] S - GLAUCON
AND thus, Glaucon, after the argument has gone a weary way, the true and the false philosophers have at length appeared in view. I do not think, he said, that the way could have been shortened.
I suppose not, I said; and yet I believe that we might have had a better view of both of them if the discussion could have been confined to this one subject and if there were not many other questions awaiting us, which he who desires to see in what respect the life of the just differs from that of the unjust must consider. And what is the next question? he asked.
Surely, I said, the one which follows next in order. Inasmuch as philosophers only are able to grasp the eternal and unchangeable, and those who wander in the region of the many and variable are not philosophers, I must ask you which of the two classes should be the rulers of our State? And how can we rightly answer that question?
Whichever of the two are best able to guard the laws and institutions of our State --let them be our guardians. Very good.
Neither, I said, can there be any question that the guardian who is to keep anything should have eyes rather than no eyes? There can be no question of that.
And are not those who are verily and indeed wanting in the knowledge of the true being of each thing, and who have in their souls no clear pattern, and are unable as with a painter's eye to look at the absolute truth and to that original to repair, and having perfect vision of the other world to order the laws about beauty, goodness, justice in this, if not already ordered, and to guard and preserve the order of them --are not such persons, I ask, simply blind?
Truly, he replied, they are much in that condition.
And shall they be our guardians when there are others who, besides being their equals in experience and falling short of them in no particular of virtue, also know the very truth of each thing? There can be no reason, he said, for rejecting those who have this greatest of all great qualities; they must always have the first place unless they fail in some other respect. Suppose then, I said, that we determine how far they can unite this and the other excellences. By all means.
In the first place, as we began by observing, the nature of the philosopher has to be ascertained. We must come to an understanding about him, and, when we have done so, then, if I am not mistaken, we shall also acknowledge that such an union of qualities is possible, and that those in whom they are united, and those only, should be rulers in the State. What do you mean?
Let us suppose that philosophical minds always love knowledge of a sort which shows them the eternal nature not varying from generation and corruption. Agreed.
And further, I said, let us agree that they are lovers of all true being; there is no part whether greater or less, or more or less honourable, which they are willing to renounce; as we said before of the lover and the man of ambition. True.
And if they are to be what we were describing, is there not another quality which they should also possess? What quality?
Truthfulness: they will never intentionally receive into their mind falsehood, which is their detestation, and they will love the truth. Yes, that may be safely affirmed of them.
'May be,' my friend, I replied, is not the word; say rather 'must be affirmed:' for he whose nature is amorous of anything cannot help loving all that belongs or is akin to the object of his affections. Right, he said.
And is there anything more akin to wisdom than truth? How can there be?
Can the same nature be a lover of wisdom and a lover of falsehood? Never.
The true lover of learning then must from his earliest youth, as far as in him lies, desire all truth? Assuredly.
But then again, as we know by experience, he whose desires are strong in one direction will have them weaker in others; they will be like a stream which has been drawn off into another channel. True.
He whose desires are drawn towards knowledge in every form will be absorbed in the pleasures of the soul, and will hardly feel bodily pleasure --I mean, if he be a true philosopher and not a sham one. That is most certain.
Such an one is sure to be temperate and the reverse of covetous; for the motives which make another man desirous of having and spending, have no place in his character. Very true.
Another criterion of the philosophical nature has also to be considered. What is that?
There should be no secret corner of illiberality; nothing can more antagonistic than meanness to a soul which is ever longing after the whole of things both divine and human. Most true, he replied.
Then how can he who has magnificence of mind and is the spectator of all time and all existence, think much of human life? He cannot.
Or can such an one account death fearful?
因篇幅问题不能全部显示,请点此查看更多更全内容
Copyright © 2019- oldu.cn 版权所有 浙ICP备2024123271号-1
违法及侵权请联系:TEL:199 1889 7713 E-MAIL:2724546146@qq.com
本站由北京市万商天勤律师事务所王兴未律师提供法律服务