基于ASP.NET的缺陷跟踪管理系统
摘要
在目前中国的IT业中,软件外包业务占据着很大的比例,并且发展越来越迅速,规模越来越大。而软件成品的缺陷修正或者说软件维护是外包服务中的重要组成部分,这就涉及到中国的IT企业争取到软件维护类的外包业务时,如何提高自身的竞争力,做到使客户满意。
本文正是在这一背景下提出了关于做好缺陷修正类的软件外包业务理论,并着重设计了相适应的缺陷跟踪管理系统(Speedflow)。首先介绍了缺陷修正外包服务中的项目组人员配置、组成和工作性质以及详细的工作流程,这是实现Speedflow系统的需求分析的重要基础。
Speedflow是利用ASP.NET + SQL Server开发的一个用于实现缺陷跟踪的C/S结构的系统,也是项目组内部的工作流程管理系统。本文采用了面向对象的软件工程的思想,按照需求提出、分析、系统设计、对象设计、代码实现的软件开发流程,科学的实现了Speedflow系统。在系统架构的设计中,数据访问层起到了至关重要的作用,它是ASPX用户界面与数据库互访数据沟通的桥梁,是整个系统实现的核心。在系统功能的设计上,以用户权限为线索,设计了系统的各权限都具有的通用功能和特殊权限拥有的特殊功能。在XML文件中定义项目工作流程是比较新颖的,通过对此XML文件的读写操作来实现工作流程中状态的变迁。Speedflow系统界面的后台用C#语言开发,本人以类为单位,有侧重的介绍了系统的数据访问层中几个类中方法的实现。
本文还分析了几种质量控制指标。对于项目组的工作业绩,每月的缺陷修正比率是一个比较科学的评判标准。另外,从时间、成本、精确度和稳定性等四个角度分析了整个工作流程的服务质量。
Speedflow系统可以规范工作流程并使工作流程自动化,极大的提高项目组的工作效率和工作质量。在处理缺陷修正类的外包业务中,具有很大的发展潜力和广阔的发展前景。
Currently outsourcing has taken a large proportion on Chinese software industry. It is growing up very quickly and increasingly popular with today’s business. And the competition has also become very fierce. Therefore bug-fixing and maintaining for product are the main part of outsourcing, which raises some questions for current Chinese IT enterprises. That is how to improve service quality, how to satisfy with customer well, and how to promote the capability of competition.
Based on these backgrounds, this thesis brings some theories on bug-fixing in outsourcing as well as related workflow management system Speedflow. Speedflow can be named workflow management system for projects, and also can be named defect-tracking system. These theories and Speedflow system can be used for outsourcing, decrease the cost and improve the work efficiency as well as capability of competition.
This thesis analyzes the theories on software bug-fixing from two sides. The first part mainly explains the way of arranging resource allocation. The conceptions of defect generally include the following sections,which is an important technical term:
(1) Bug is a defect in a program.
(2) A function needs to be enhanced under user’s requirement.
(3) Add a new feature to upgrade the software.
Another technical term is CR (Change Request). One CR stands for one defect, which also indicates a bug-fixing task.
From outsourcing cooperation point of view, four roles are necessary for this outsourcing. The four roles are respectively: Outsourcing Manager (the interface from customer side), Submitter (person who finds and submits a defect of program), Module Owner (an original designer), and Specialist/Expert (experts of systems).
From CRT point of view, there are six roles. The responsibilities of them are in the following:
(1)Project Manager: be in charge of the team operation and allocation as well as cooperate with Outsourcing Manager.
(2)Technology Advisor: experts in CRT, which are responsible for solving difficulties.
(3)Develop Engineer: be responsible for fixing defects.
(4)Test Engineer: be responsible for testing the modified codes.
(5)Release Engineer: be responsible for version release.
(6)Project Quality Engineer: be responsible for the quality of product.
The second part describes the workflow of fixing a CR. Besides some accidents, the main workflow are: Reproducing->Designing fix->Waiting for design review->Implementing fix->Waiting for fix review ->UTC(Unit Test Complete)->Release. For no code change CR, it may be closed as user error, duplicate and not reproducible and so on. The workflow is the core part of whole team, and it can indicate the theories of defect-fixing.
The Speedflow system is aim mainly to cause the defect tracking and the project working flow automation. It is tracking the CR condition information frequently, automatically and manifests the condition according to user's choice for changing process, and records detailed information when each status is changing. Each users can query the CRs which he want to know by using the query function. Project manager can know every CR well. Each engineer needs to use his own account number to login, watch the CR task in his queue, and change the CR’s status and information belong to himself when necessary.
Speedflow’s structure is based on Browser/Server. Use the .NET Framework and ASP.NET + SQL Server 2000 to implement it. Use C# to design the background program of ASPX. The user can login it just with inputting the server address into browser. It is very convenient and speedfully.
In processing of Speedflow system, I used the object-oriented software engineering thought. According to analysis, system designing, object designing, code realization ,which is software development flow, realize the Speedflow system scientificly. In the system overhead construction design, the data accessing level played a very important role. It was the ASPX user interface and the database exchange visits data communication bridge, and was the core of overall system realization. In the system function designing, take the user jurisdiction as the clue. Designed the common function and special function for special users. It is very novel to define the project work flow in the XML document. It realizes in regarding this the work flow through the XML document read-write operation. The user interface’s background is developed by C# language. Introduce several method of classes in the data layout in the system.
This article has also analyzed the quality control target. Regarding the project team's work achievement, each month flaw revision ratio is a quite scientific judgment standard. Moreover, analyzed the entire flow grade of service from time, cost, precision and stable point of view.
The Speedflow system makes work flow standard and causes the workflow automation. It can enhance the working efficiency and quality. It has the very great potential and theprospects for development in this outsourcing field.
With the development of Chinese IT field, this kind of outsourcing will become more and more, and the competition will be also fiercer. Hopefully the theories of bug-fixing and implementation of Speedflow system can be a good reference in related field. Since the limited of my technical experience, it is not perfect and needs much more support and suggestions.
本文正是在这一背景下提出了关于做好缺陷修正类的软件外包业务理论,并着重设计了相适应的缺陷跟踪管理系统(Speedflow)。首先介绍了缺陷修正外包服务中的项目组人员配置、组成和工作性质以及详细的工作流程,这是实现Speedflow系统的需求分析的重要基础。
Speedflow是利用ASP.NET + SQL Server开发的一个用于实现缺陷跟踪的C/S结构的系统,也是项目组内部的工作流程管理系统。本文采用了面向对象的软件工程的思想,按照需求提出、分析、系统设计、对象设计、代码实现的软件开发流程,科学的实现了Speedflow系统。在系统架构的设计中,数据访问层起到了至关重要的作用,它是ASPX用户界面与数据库互访数据沟通的桥梁,是整个系统实现的核心。在系统功能的设计上,以用户权限为线索,设计了系统的各权限都具有的通用功能和特殊权限拥有的特殊功能。在XML文件中定义项目工作流程是比较新颖的,通过对此XML文件的读写操作来实现工作流程中状态的变迁。Speedflow系统界面的后台用C#语言开发,本人以类为单位,有侧重的介绍了系统的数据访问层中几个类中方法的实现。
本文还分析了几种质量控制指标。对于项目组的工作业绩,每月的缺陷修正比率是一个比较科学的评判标准。另外,从时间、成本、精确度和稳定性等四个角度分析了整个工作流程的服务质量。
Speedflow系统可以规范工作流程并使工作流程自动化,极大的提高项目组的工作效率和工作质量。在处理缺陷修正类的外包业务中,具有很大的发展潜力和广阔的发展前景。
Currently outsourcing has taken a large proportion on Chinese software industry. It is growing up very quickly and increasingly popular with today’s business. And the competition has also become very fierce. Therefore bug-fixing and maintaining for product are the main part of outsourcing, which raises some questions for current Chinese IT enterprises. That is how to improve service quality, how to satisfy with customer well, and how to promote the capability of competition.
Based on these backgrounds, this thesis brings some theories on bug-fixing in outsourcing as well as related workflow management system Speedflow. Speedflow can be named workflow management system for projects, and also can be named defect-tracking system. These theories and Speedflow system can be used for outsourcing, decrease the cost and improve the work efficiency as well as capability of competition.
This thesis analyzes the theories on software bug-fixing from two sides. The first part mainly explains the way of arranging resource allocation. The conceptions of defect generally include the following sections,which is an important technical term:
(1) Bug is a defect in a program.
(2) A function needs to be enhanced under user’s requirement.
(3) Add a new feature to upgrade the software.
Another technical term is CR (Change Request). One CR stands for one defect, which also indicates a bug-fixing task.
From outsourcing cooperation point of view, four roles are necessary for this outsourcing. The four roles are respectively: Outsourcing Manager (the interface from customer side), Submitter (person who finds and submits a defect of program), Module Owner (an original designer), and Specialist/Expert (experts of systems).
From CRT point of view, there are six roles. The responsibilities of them are in the following:
(1)Project Manager: be in charge of the team operation and allocation as well as cooperate with Outsourcing Manager.
(2)Technology Advisor: experts in CRT, which are responsible for solving difficulties.
(3)Develop Engineer: be responsible for fixing defects.
(4)Test Engineer: be responsible for testing the modified codes.
(5)Release Engineer: be responsible for version release.
(6)Project Quality Engineer: be responsible for the quality of product.
The second part describes the workflow of fixing a CR. Besides some accidents, the main workflow are: Reproducing->Designing fix->Waiting for design review->Implementing fix->Waiting for fix review ->UTC(Unit Test Complete)->Release. For no code change CR, it may be closed as user error, duplicate and not reproducible and so on. The workflow is the core part of whole team, and it can indicate the theories of defect-fixing.
The Speedflow system is aim mainly to cause the defect tracking and the project working flow automation. It is tracking the CR condition information frequently, automatically and manifests the condition according to user's choice for changing process, and records detailed information when each status is changing. Each users can query the CRs which he want to know by using the query function. Project manager can know every CR well. Each engineer needs to use his own account number to login, watch the CR task in his queue, and change the CR’s status and information belong to himself when necessary.
Speedflow’s structure is based on Browser/Server. Use the .NET Framework and ASP.NET + SQL Server 2000 to implement it. Use C# to design the background program of ASPX. The user can login it just with inputting the server address into browser. It is very convenient and speedfully.
In processing of Speedflow system, I used the object-oriented software engineering thought. According to analysis, system designing, object designing, code realization ,which is software development flow, realize the Speedflow system scientificly. In the system overhead construction design, the data accessing level played a very important role. It was the ASPX user interface and the database exchange visits data communication bridge, and was the core of overall system realization. In the system function designing, take the user jurisdiction as the clue. Designed the common function and special function for special users. It is very novel to define the project work flow in the XML document. It realizes in regarding this the work flow through the XML document read-write operation. The user interface’s background is developed by C# language. Introduce several method of classes in the data layout in the system.
This article has also analyzed the quality control target. Regarding the project team's work achievement, each month flaw revision ratio is a quite scientific judgment standard. Moreover, analyzed the entire flow grade of service from time, cost, precision and stable point of view.
The Speedflow system makes work flow standard and causes the workflow automation. It can enhance the working efficiency and quality. It has the very great potential and theprospects for development in this outsourcing field.
With the development of Chinese IT field, this kind of outsourcing will become more and more, and the competition will be also fiercer. Hopefully the theories of bug-fixing and implementation of Speedflow system can be a good reference in related field. Since the limited of my technical experience, it is not perfect and needs much more support and suggestions.
引文
[1] 郑阿奇,ASP.NET 程序设计教程,机械工业出版社,2006,第一版,1
[2] 周杰韩、蓝海洋、熊光楞,.NET框架与元模式研究,计算机工程与应用,2002 年,第 7 卷,第 23 期,141
[3] Billy Hollis,康博译,VB.NET程序设计教程,清华大学出版社,2001,第一版,35
[4] 沈阳、李勇敢,ASP.NET 程序设计教程,电子工业出版社,2006,第一版,3
[5] 王昊亮、李刚,Visual C#程序设计教程,清华大学出版社,2003,第一版,13
[6] Burton Harvey,康博译,C#程序设计教程,清华大学出版社,2001,第一版,1～10
[7] 王颖纯,.NET框架和XML Web服务,天津理工学院学报,2003,第 19 卷,第 02 期,87
[8] 王昊亮、李刚,Visual C#程序设计教程,清华大学出版社,2003,第一版,14
[9] 钱昆,C#实用编程技术,中国水利水电出版社,2002,第一版, 24～26
[10] 王欣、黎峰,新型的面向对象的编程语言—C#,计算机工程与设计,2004,第 25 卷,第 06 期,929
[11] 王宝祥,基于ADO NET的数据库访问技术研究,计算机应用与软件,2004,第 21 卷,第 02 期,120
[12] 梅中辉、经亚枝,NET中的数据访问技术—ADO.NET,微型计算机信息,2003,第 19 卷,第 01 期,89
[13] 孟现飞、李浩、孙统风,ADO.NET数据访问模型研究,微机发展,2003,第 13 卷,第S1 期,94
[14] 罗海滨、范玉顺,工作流技术综述,软件学报,2000,第 11 卷,第 07 期,899
[15] 瞿裕忠、张剑锋、陈峥、王丛刚,XML语言及相关技术综述,计算机工程,2000,第 26 卷,第 12 期,4
[16] 胡达风,大型软件缺陷修正跨国外包后的质量控制,计算机工程,2004,第 30 卷,增刊,99
[17] 郝刚、袁永刚、齐艳,ASP.NET服务器控件开发技术与实例,人民邮电出版社,2004,第一版,67
[18] Robert Lair,ASP.NET开发人员手册,电子工业出版社,2004,第一版,204
[19] 张祖葵、刘斌,数据库建设浅析,石油实验地址,1997,第12卷,第03期,145
[20] 吴扬扬、颜毛智,XML基础,高等教育出版社,2005,第一版,56
[21] 林邦杰,深入浅出 C#程序设计,中国铁道出版社,2004,第一版,98～99
[22] 王志喜、王润云,新一代程序设计语言 C#中的面向对象机制,计算机工程与应用,2003,第 7 期,108
[23] 邵维忠、杨芙清,面向对象的系统分析,清华大学出版社,1998,第一版,290
[24] 向方,ASP.NET 和 C#在 Web 数据库中的应用,安阳师范学院学报,2002,第 2 期,21
[25] 郝刚、袁永刚、齐艳,ASP.NET 服务器控件开发技术与实例,人民邮电出版社,2004,第一版,138～139
[2] 周杰韩、蓝海洋、熊光楞,.NET框架与元模式研究,计算机工程与应用,2002 年,第 7 卷,第 23 期,141
[3] Billy Hollis,康博译,VB.NET程序设计教程,清华大学出版社,2001,第一版,35
[4] 沈阳、李勇敢,ASP.NET 程序设计教程,电子工业出版社,2006,第一版,3
[5] 王昊亮、李刚,Visual C#程序设计教程,清华大学出版社,2003,第一版,13
[6] Burton Harvey,康博译,C#程序设计教程,清华大学出版社,2001,第一版,1～10
[7] 王颖纯,.NET框架和XML Web服务,天津理工学院学报,2003,第 19 卷,第 02 期,87
[8] 王昊亮、李刚,Visual C#程序设计教程,清华大学出版社,2003,第一版,14
[9] 钱昆,C#实用编程技术,中国水利水电出版社,2002,第一版, 24～26
[10] 王欣、黎峰,新型的面向对象的编程语言—C#,计算机工程与设计,2004,第 25 卷,第 06 期,929
[11] 王宝祥,基于ADO NET的数据库访问技术研究,计算机应用与软件,2004,第 21 卷,第 02 期,120
[12] 梅中辉、经亚枝,NET中的数据访问技术—ADO.NET,微型计算机信息,2003,第 19 卷,第 01 期,89
[13] 孟现飞、李浩、孙统风,ADO.NET数据访问模型研究,微机发展,2003,第 13 卷,第S1 期,94
[14] 罗海滨、范玉顺,工作流技术综述,软件学报,2000,第 11 卷,第 07 期,899
[15] 瞿裕忠、张剑锋、陈峥、王丛刚,XML语言及相关技术综述,计算机工程,2000,第 26 卷,第 12 期,4
[16] 胡达风,大型软件缺陷修正跨国外包后的质量控制,计算机工程,2004,第 30 卷,增刊,99
[17] 郝刚、袁永刚、齐艳,ASP.NET服务器控件开发技术与实例,人民邮电出版社,2004,第一版,67
[18] Robert Lair,ASP.NET开发人员手册,电子工业出版社,2004,第一版,204
[19] 张祖葵、刘斌,数据库建设浅析,石油实验地址,1997,第12卷,第03期,145
[20] 吴扬扬、颜毛智,XML基础,高等教育出版社,2005,第一版,56
[21] 林邦杰,深入浅出 C#程序设计,中国铁道出版社,2004,第一版,98～99
[22] 王志喜、王润云,新一代程序设计语言 C#中的面向对象机制,计算机工程与应用,2003,第 7 期,108
[23] 邵维忠、杨芙清,面向对象的系统分析,清华大学出版社,1998,第一版,290
[24] 向方,ASP.NET 和 C#在 Web 数据库中的应用,安阳师范学院学报,2002,第 2 期,21
[25] 郝刚、袁永刚、齐艳,ASP.NET 服务器控件开发技术与实例,人民邮电出版社,2004,第一版,138～139