Font Size: a A A

Change Management System Research And Implement

Posted on:2010-07-26Degree:MasterType:Thesis
Country:ChinaCandidate:Z Q LiuFull Text:PDF
GTID:2178360302966122Subject:Software engineering
Abstract/Summary:PDF Full Text Request
With the rapid development of society, the demands to software development increase higher and higher. The number and frequency of Software requirements change grow rapidly followed, which required the team of project, under considerable pressure, fast response the change and deal with it. At the same time, as the scale of software projects expanses, the number of the designers, developers, testers also continue to grow, to be spent on the cost of repairing defects are also soared. At this point, the ability of project team to efficiently track and manage the software project changes is the key to the success of software projects.Change management, as a key element of software development life cycle, to track and record the evolutionary process of software products. Through the change management system, development manager to ensure the controllability of code changes, and binding the team members in implementing changes to permissions. Developers can easily record and find changes reasons, time and influence of the source code and all kinds of documents, and reflect the efficiency and progress. Project managers can keep abreast of the changes, defects of the software project, so as to estimate the infection to the progress and quality of software project. After the end of the project, provides basic data for evaluating the quality of software products.In the different stages of the software development life cycle, change manages owes the following processes and requirements:Change proposed: Record the details of change. When didn' t audited pass and passed it back to be re-submitted.Change Audit: Audit the first time and fill in audit opinions. Didn' t audit pass and the change will be refused to the presenter.Change approve: Approve the change and fill in the opinions. Didn' t Approve pass and the change will be returned to the presenter.Implement Change: Implement the change. When identified didn' t the changes and refused it, the change will be returned to the approval people.Confirm Change: confirm the changes have been implemented and confirmed the changes don' t affect other function modules. If confirmation didn' t pass, the change can be returned to the Responsible person and require re-implement the changes.Access Control: Only the current handler of record can deal with their own records, other people can not deal with it.Integrity Control: Control deletes permissions if do need to delete the incorrect submission of records, must submit data change request, after administrator approval, by the system administrator to implement delete operation.E-mail notification: Where the current handler of the record change, via e-mail notice the current handle to process the change timely.The project of R & D center, after establishment of project in the entire development process, the project will be through unit testing, system testing, acceptance testing at all stages of production, in the process, software defects and functions changes which the testers, requirements personnel, acceptance personnel discovered, must be track and manage in the change management system. In this paper, trials the more commonly Change Management Product at home and abroad, the selection with a strong, flexible, rapid development of the Rational ClearQuest product basis to develop the Change Management System for the R & D center of a commercial bank. To consider the scale of very large project development, organizational structure and require 7 * 24 uninterrupted services, we have deployed in Oracle Database AIX of platform, 4 sets of Windows 2003 Server as application server to deploy Clear Quest Service, Through the F5 load balancing allocate each users on the application servers based on the load density of servers. F5 will not continue to allocate user to the server, when is inform not available through the detection mechanism. Through F5' s load-balancing and a strong AIX database server to ensure the Change Management System provides 7 * 24 stable and reliable services.This paper focuses on the design process of the Change Management System: the part of the database design, most functionality of the change process design.The goal of Change Management System design is to achieve change management of the entire software life cycle:1) The self-test record of unit test phase: the project development process, manage problems which developers founded in unit test the, known as self-test records; due to the testing and development are within the project team, which Changes not subject to audit and approval. Self- Tester communicates the developers to resolve it.2) The system test phase of the System Test record: manage problems when the testing department implement system test to the software product; the proposed records must be audit by the test manager and approve by the development manager before they are allowed to change.3) Acceptance and commissioning phase of the patch records: manage production problems, which found by the user or project team, after the project put into production environment. Since the patch record will have a direct impact on the existing functions of the system and the departmental assess, must be made through approved by the testing department and development department before implementation.4) The system test phase of the versions update request: manage update request the version of the application, for the project team to solve System Test record and patch records, update the revised version of the program to the integrated test environment, for testers confirm the modified program. Before the versions updates, the request must be approved through the development department and testing departments in order to avoid affected the existing work. In this paper, the Management System achieve change in the unit testing, system testing, commissioning and acceptance phase of the software life cycle, through the ClearQuest Designer , we can quickly change and improve the change process itself. Through the deployment of multiple application servers, F5 load balancing, stable AIX database to ensure provide 7 * 24 stable and reliable services.
Keywords/Search Tags:software engineering, software development life cycle, change management, ClearQuest
PDF Full Text Request
Related items