CN110888626A - Software integration project matrix type process management system - Google Patents
Software integration project matrix type process management system Download PDFInfo
- Publication number
- CN110888626A CN110888626A CN201911167518.3A CN201911167518A CN110888626A CN 110888626 A CN110888626 A CN 110888626A CN 201911167518 A CN201911167518 A CN 201911167518A CN 110888626 A CN110888626 A CN 110888626A
- Authority
- CN
- China
- Prior art keywords
- project
- module
- generating
- management
- software
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 73
- 230000008569 process Effects 0.000 title claims abstract description 73
- 239000011159 matrix material Substances 0.000 title claims abstract description 25
- 230000010354 integration Effects 0.000 title claims abstract description 15
- 238000007726 management method Methods 0.000 claims description 102
- 238000012360 testing method Methods 0.000 claims description 72
- 230000008859 change Effects 0.000 claims description 48
- 230000007547 defect Effects 0.000 claims description 40
- 238000012552 review Methods 0.000 claims description 37
- 238000013461 design Methods 0.000 claims description 30
- 238000012790 confirmation Methods 0.000 claims description 24
- 238000004458 analytical method Methods 0.000 claims description 22
- 238000012423 maintenance Methods 0.000 claims description 20
- 238000012549 training Methods 0.000 claims description 17
- 238000005259 measurement Methods 0.000 claims description 13
- 238000000275 quality assurance Methods 0.000 claims description 12
- 238000011156 evaluation Methods 0.000 claims description 8
- 238000005516 engineering process Methods 0.000 claims description 7
- 239000000463 material Substances 0.000 claims description 7
- 238000012544 monitoring process Methods 0.000 claims description 7
- 238000002360 preparation method Methods 0.000 claims description 7
- 238000011835 investigation Methods 0.000 claims description 6
- 238000013439 planning Methods 0.000 claims description 6
- 238000012545 processing Methods 0.000 claims description 6
- 238000011160 research Methods 0.000 claims description 6
- 230000035515 penetration Effects 0.000 claims description 5
- 238000012550 audit Methods 0.000 claims description 4
- 238000012986 modification Methods 0.000 claims description 3
- 230000004048 modification Effects 0.000 claims description 3
- 230000003442 weekly effect Effects 0.000 claims description 3
- 238000011161 development Methods 0.000 abstract description 10
- 230000001105 regulatory effect Effects 0.000 abstract description 2
- 230000001276 controlling effect Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 238000007689 inspection Methods 0.000 description 4
- 238000012384 transportation and delivery Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 238000012937 correction Methods 0.000 description 2
- 238000012854 evaluation process Methods 0.000 description 2
- 230000008676 import Effects 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 238000012356 Product development Methods 0.000 description 1
- 230000000739 chaotic effect Effects 0.000 description 1
- 238000005520 cutting process Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000009472 formulation Methods 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000000149 penetrating effect Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000012502 risk assessment Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a software integration project matrix type process management system, which adopts a matrix management mode of horizontal and vertical staggering and organically combines a software engineering process, project management and a software life cycle, so that the interior of a complex development process is clearly visible, the progress, quality, range and cost of a project are tracked and regulated at any time and any place, and the appearance of the project management is obviously changed towards the standardization direction.
Description
Technical Field
The invention relates to the technical field of software management, in particular to a software integration project matrix type process management system.
Background
With the continuous penetration of computer software in various fields of social economy, the number of small and medium-sized software enterprises and integrated software projects is greatly increased; with the higher and higher requirements of customers on the integrated project, the competition among enterprises is more and more intense, and the enterprises need to strictly control the project cost while delivering the project according to the quality guarantee, so that the procedural management of the software integrated project is imperative. However, the software development process of small and medium-sized software enterprises is often chaotic and unordered, and the inside of the process is invisible.
By the software integration project matrix type process management system, small and medium-sized software enterprises can automatically manage and control the internal process of a standardized software integration project; organically combining an engineering process, a management process and a support process in the longitudinal direction, and organically connecting and managing software life cycles of project negotiation, project definition, project development, product confirmation and maintenance in the transverse direction; therefore, the cost is effectively reduced, the rework is reduced, the project period is shortened, and simultaneously, the quality of software products and the satisfaction degree of users are improved.
Disclosure of Invention
The invention provides a software integration project matrix type process management system, which aims to overcome the technical problems.
The invention relates to a software integration project matrix type process management system, which comprises:
the system comprises a contract signing module, a requirement investigation module, a hardware management module, a requirement analysis module, a software design module, a coding and self-testing module, an integrated testing module and a program release module;
the contract signing module is used for generating a project contract, a project task entrusting sheet, a project appointed book and a project category definition book according to project requirements and storing the project contract, the project task entrusting sheet, the project appointed book and the project category definition book to a cloud server;
the requirement research module is used for acquiring and sorting user requirements; generating a user requirement specification and a requirement confirmation sheet, and storing the user requirement specification and the requirement confirmation sheet to a cloud server;
the hardware management module is used for purchasing, receiving, installing and checking hardware and network equipment; generating a hardware equipment purchase requisition, an equipment receiving confirmation and an equipment acceptance order;
the requirement analysis module is used for converting the user requirement into a system service model and determining the project requirement of the software to be developed;
the software design module is used for generating an interface prototype, a database design report, a summary design specification and a detailed design specification according to a system service model and the project requirements;
the coding and self-testing module is used for generating a software program, a version updating record, a database updating record, a unit test report and a software operation and use instruction for an interface prototype, a database design, a summary design instruction and a detailed design instruction output by the software design module;
the integrated test module is used for integrating and testing each module corresponding to the software program output by the self-test module and encoding the software program, and verifying the service logic; generating an integrated test case, an integrated test application table, a test BUG result, an integrated test report and a tested program package;
and the program release module is used for releasing a notice of the program war/rar package and the version generated by the software product which passes the test.
Further, still include:
the data initialization module is used for importing the project original data into a database of a software product to be developed and generating an initialization data range confirmation list and an initialization data confirmation list;
the system training module is used for determining the generated training sign-in sheet, the generated examination sign-in sheet and the generated examination score sheet;
the system test module is used for compiling a system test case according to the user requirement specification and the requirement confirmation list of the requirement investigation module and carrying out system comprehensive test on the software program which is released by the program; generating a system test case, a system test application table, a system test report and a stable program package;
the trial operation module is used for supervising and managing data backup and system rollback preparation work before trial operation and generating a trial operation maintenance record table;
and the project acceptance module is used for generating a project acceptance application book and a project acceptance report.
Further, still include:
the system maintenance module is used for tracking the follow-up problem and demand modification of the software system and generating a system maintenance form;
the demand management module is used for establishing and maintaining a demand tracking matrix and controlling the change of the demand; generating a demand tracking matrix and a product service data document record table;
and the defect management module is used for standardizing the defect processing flow, recording the defects, evaluating the influence of the modified defects on the associated contents and closing and tracking the defects, and generating a defect management table.
Further, still include:
the project planning module is used for generating a project material tool list, a project plan, a project implementation plan and a user-defined process description according to the work task;
the project starting module is used for starting the holding of the conference and the project formal starting notification work and generating a starting conference summary;
the project monitoring module is used for periodically tracking the progress condition of the project plan and generating a weekly report and a milestone report;
and the project ending module is used for project ending management and generating a project summary report, a personnel performance assessment table and a project summary conference record.
Further, still include:
the change control module is used for judging the change type, changing the application, writing and submitting the change application, confirming the change, implementing the change and verifying the change, and generating a change application form, a change confirmation form and a change tracking form;
the risk management module is used for performing the risk management process of all the implementation projects and generating a risk tracking record table and a risk management asset library;
the quality assurance module is used for generating a quality assurance plan, a process check list, a process penetration matrix and a project process quality scoring table;
the measurement analysis module is used for generating a measurement analysis table according to project progress, quality, workload and stability;
the configuration management module is used for making a configuration management plan, managing the configuration management, controlling the version and changing the baseline, and generating a configuration management plan, a baseline state report, a configuration audit report and a signature and seal paper document record table;
the technical review module is used for stipulating and managing the technical review process of the engineering process and generating a technical review defect list;
and the management evaluation module is used for managing the milestone node evaluation process in the project process and generating a management evaluation record.
The software integration project process management system adopts a matrix management mode of horizontal and vertical staggering, and organically combines the software engineering process, the project management and the software life cycle, so that the interior of a complex development process is clearly visible, the project progress, quality, range and cost are tracked and regulated at any time and any place, and the appearance of the project management is obviously changed towards the standardization direction.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a block diagram of the software system architecture of the present invention;
FIG. 2 is a diagram of a software module matrix according to the present invention;
FIG. 3 is a flow diagram of a hardware management module of the present invention;
FIG. 4 is a flow diagram of a data initialization module of the present invention;
FIG. 5 is a flow chart of a training module of the system of the present invention;
FIG. 6 is a flow chart of a commissioning module of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The integrated project matrix type process management system adopts a B/S structure deployment mode of a cloud server, can be accessed through browsers of a microcomputer, a smart phone or other intelligent terminals, simplifies access parties and improves the management work efficiency of integrated projects. As shown in fig. 1, the system specifically includes a contract signing module, a requirement research module, a hardware management module, a requirement analysis module, a software design module, a coding and self-testing module, an integration test module, a program release module, a data initialization module, a system training module, a system test module, a trial run module, a project acceptance module, a system maintenance module, a requirement management module, a defect management module, a project planning module, a project starting module, a project monitoring module, a project ending module, a change control module, a risk management module, a quality assurance module, a metric analysis module, a configuration management module, a technical review module, and a management review module.
As shown in fig. 2, the system adopts a matrix mode of horizontal and vertical staggering, and organically combines engineering, management and life cycle, so that the granularity of software integration project management is more flexible, and the effectiveness and controllability are greatly guaranteed; from the perspective of software engineering, dividing the project into five stages of project negotiation, project definition, project development, product confirmation and maintenance according to the project life cycle in the transverse direction; dividing the process into three types longitudinally according to engineering process, management process and support process; five software project life cycle stages and three types of processes are divided into 27 software modules such as a formal contract signing module, a requirement investigation module, a hardware management module and a requirement analysis module. In the engineering process:
the contract signing module 201 is used for entrusting a production department to carry out project implementation and defining a project responsible person; the data and information of the generated project contract, project task order, project manager appointed book and project category definitional book are stored on the cloud server. In the specific project implementation process, once the software integration project wins the bid, the project bid document is used as the input of the contract signing module. The module outputs a project formal contract, a project task order, a project manager appointed book and a project category definition book.
The requirement research module 202 is used for acquiring and sorting user requirements from a client; because the requirement research belongs to the project definition stage, the accuracy, the quality and the cost of the project are high, and the direct relation project scope, the cost and the progress are low; and storing the data and the information of the generated user requirement specification and the requirement confirmation list on the cloud server.
As shown in fig. 3, the hardware management module 203 is used for purchasing, receiving, installing and checking hardware and network devices required by the software product to be developed; the field implementation working progress and quality are managed and controlled in real time, the field risk occurrence rate is reduced, and rework is reduced; and storing the data and the information of the generated equipment purchase order, the equipment delivery confirmation order and the equipment acceptance order on the cloud server.
The requirement analysis module 204 converts the user requirements into a system service model, and determines the project requirements of the software to be developed; the project requirements comprise the requirements of the software to be developed such as functions, performances, data, interfaces and the like; the data and information of the generated requirement specification are stored on the cloud server.
The software design module 205 is used for generating an interface prototype design, a database design report, a summary specification and a design specification according to a system business model and the project requirements; the data and information of the generated interface prototype design, database design report, summary design specification and detailed design specification are stored on the cloud server through the steps of overall structure design, user interface design, data storage design, input/processing process/output design and the like.
The coding and self-testing module 206 is used for generating software programs, version updating records, database updating records, unit test reports and software operation and use specifications from the interface prototype, the database design, the summary design specification and the detailed design specification output by the software design module; the generated data and information such as the software program, the version updating record and the like are stored on the cloud server.
The integrated test module 207 is used for compiling an integrated test case according to the output of the software design module, integrating and testing each module of the output software program of the coding and self-test module, and verifying the service logic; and the generated integrated test case, the integrated test application table, the test BUG result, the integrated test report and the data and information of the tested program package are stored on the cloud server.
The program release module 208 is used for releasing the software products which have undergone the integration test; and the generated program war/rar package and the data and information of the version release notice are stored on the cloud server.
As shown in fig. 4, the data initialization module 209 is configured to import the client-side raw data into a database of the software product to be developed, so as to ensure normal operation of the software product to be developed; and the generated initialization data range confirmation list and the data and information of the initialization data confirmation list are stored on the cloud server. Compared with other software project management systems, the system comprises a data initialization module, and as important data of a client side is involved, the part of work needs to be implemented on the site of the client side, and the client provides diversified business data forms and modes, great difficulty and risk are brought to project management; the module summarizes and standardizes the derivative data flow, automatically processes different service data forms and modes, manages and controls data initialization work in real time, greatly improves data accuracy, and ensures the implementation quality and progress of the whole project.
As shown in fig. 5, the system training module 210 is configured to generate a training sign-in sheet, an examination sign-in sheet, and an examination score sheet, and store these data and information on the cloud server; the system comprises a system training module and an automatic and standardized training process, so that the operation and use of a software system by a client are effectively guided, the later work of project members is greatly reduced, and the project cost is effectively reduced.
In order to ensure the continuous progress of the project, after software development, hardware network and business data import are completed and before the project trial run, a stable program package and a software operation instruction are used as system training module input, and after the specific steps of training mode confirmation, training plan formulation, training data preparation, training execution, effect feedback and examination, a training plan, a training attendance sheet and an examination result sheet are output.
The system test module 211 is used for compiling test cases according to the user requirement specification and the requirement specification, and combining software programs issued by the programs, computer hardware, peripheral equipment, networks and other factors to carry out comprehensive test on the information system; and the generated system test case, the system test application table, the system test report and the data and information of the stable program package are stored on the cloud server. After the program is released to a client environment, hardware and a network are finished, the program is used as input to carry out comprehensive test on a software product through a system test module, and the system test case, the system test report and a stable program package are output through specific steps of building a client actual operation test environment, compiling a system test case, executing a test, modifying a defect and carrying out a regression test; and when the BUG appears in the system test process, triggering the defect management module 216.
As shown in fig. 6, the commissioning module 212 is configured to supervise and manage data backup and system rollback preparation before commissioning, deliver a software product to a client for trial use, identify a software system defect/a software function different from an actual service, further perform defect correction/demand change, and determine whether the associated content influence is fully considered after commissioning; and the data and the information of the generated commissioning maintenance record table are stored on the cloud server.
The product is delivered to a client for trial by a trial operation module, the defects of a software system are identified, the service function of the software is verified, and a trial operation maintenance record table is output through the specific steps of system backup, rollback preparation, external interface and data inspection and trial operation execution; the system defect occurs in the trial run process to trigger the defect management module 216, and the user proposes the service change triggering change control module 221 in the trial run process.
The software integration project matrix type process management system comprises a trial operation module, system backup and rollback work are guaranteed to be carried out orderly, external interfaces and data correctness of the system are guaranteed, the module automatically takes countermeasures when the system goes wrong, and software products are guaranteed to be carried out orderly in trial operation, so that customer satisfaction is greatly improved.
The project acceptance module 213 is used for ending work of the whole software project, representing formal ending of contract responsibility and periodic ending of the project/project; and the data and the information of the generated project acceptance application book and the project acceptance report are stored on the cloud server. After the project trial operation is finished, project acceptance checking work is carried out with a client side; and the project acceptance module outputs a project acceptance application book and a project acceptance report after the specific functional steps of checking the delivery, submitting an acceptance application, formally accepting and handing over the project.
The system maintenance module 214 is used for modifying subsequent problems and requirements of the software system; and the generated data and information of the system maintenance form are stored on the cloud server. Entering a maintenance period stage after the project is checked and accepted, and managing the software system by a system maintenance module for maintenance work in a warranty period (short period) and outside the warranty period (long period); if the defect maintenance is carried out, outputting a maintenance record table through the specific steps of recording problems, confirming the problems, modifying the problems and releasing programs; and if the new demand maintenance is required, outputting a maintenance record table through specific processes of demand investigation, feasibility analysis, software production and product confirmation.
The requirement management module 215 is used for establishing and maintaining a requirement tracking matrix, establishing common understanding of requirements between the client and the developer, maintaining the consistency of the requirements and other work results, and controlling the change of the requirements; and the generated data and information of the demand tracking matrix and the product service data document record table are stored on the cloud server. In order to realize software productization, each project requirement management runs through the whole life cycle, user requirement specifications, requirement specification specifications, design documents, codes and test cases which pass through technical review are used as requirement management module input, and after specific steps of establishing a requirement tracking matrix, searching for inconsistency, finding out the inconsistency and eliminating the inconsistency and a plan, the requirement tracking matrix is output.
The defect management module 216 is used for standardizing the flow of defect processing to ensure that the defect correction is correctly carried out; the defect detection system is responsible for recording the discovered defects, evaluating the influence of the modified defects on the associated content and closing and tracking the defects; the data and information of the generated defect management table are stored on the cloud server. The defect management runs through the whole life cycle of a software project, the defect management is triggered by technical review, integrated test and system test of requirements, design, coding and testing, technical review articles and software defects are used as the input of the defect management module 216, and a BUG management table is output through the specific steps of recording defects, modifying defects, tracking defects and closing.
In the management process:
the project planning module 217 is used for project managers to receive work tasks, know work ranges, know client conditions, make work plans, organize related personnel and the like for early-stage work; the generated data and information of the project material tool list, the project plan, the project implementation plan and the custom process description are stored on the cloud server. Once the basic information such as project name, scope, implementation cycle, delivery criteria, principal, category, etc. is determined, it is used as input to the project planning module 217, which outputs project materials tool list, project plan, project implementation plan, custom process description, configuration management plan, via the steps of reading project contracts, preparing project materials tools, making project plans, project management support and internal review, customer validation flow.
The project starting module 218 is used for starting the holding of the conference and the project formal starting notification work; the generated data and information for starting the conference summary are stored on the cloud server. After the project planning is finished, the project plan, the project implementation plan, the user-defined process description and the configuration management plan are used as the input of a project starting module, after meeting time, meeting places and personnel are determined, and a project starting conference is held by the two parties, the project is formally started, and meanwhile a conference starting summary is output. The project monitoring module 219 is used for periodically (usually, one day/week/phase) tracking various parameters of the project plan, such as progress, workload, quality, resources, work results, and the like, and continuously knowing the progress of the project, so that corrective measures can be taken in time when the actual progress of the project deviates significantly from the plan; the data and information of the generated weekly reports and milestone reports are stored on the cloud server. Before the project is accepted after the project is formally started, the progress, quality, resources and the like of the whole project need to be managed and monitored, various data parameters of the project plan are periodically (usually one day/week/stage) tracked through the project monitoring module 219, and monitoring is realized through summarizing and analyzing the project condition, finding deviation, analyzing the deviation reason, correcting and adjusting the deviation.
The project ending module 220 is used for project ending management, not only summarizing and evaluating the project, but also evaluating the project performance of project participants and filing the project; the generated data and information of the project summary report, the personnel performance assessment table and the project summary meeting record are stored on the cloud server. Project development documents, product development documents and management documents generated in the project implementation process are used as project conclusion modules to be input, and project conclusion reports, personnel performance assessment tables and project conclusion conference records are output after compiling conclusion reports, holding up conclusion conferences, performance assessment and project archiving processes.
In the support process:
the change control module 221 is used for judging the type of change, applying for the change, writing and submitting a change application form, confirming the change, implementing the change and verifying the change; and storing the data and information of the generated change application form, change confirmation form and change tracking form on the cloud server. The whole process of project implementation is triggered to change the control module once the range, the progress, personnel and other production elements are changed; the execution criteria are as follows: according to the change influence and property, the change is graded, and different grades of items are controlled by different approval authorities; according to the urgency of change, different change processing flows are carried out through step cutting, and the efficiency is improved by using batch processing/priority division and other modes; and outputting a change application form and a change tracking table after the steps of change application, change verification, change implementation and verification.
The risk management module 222 is used for all risk management processes of the implemented project, including risk identification, risk analysis, risk tracking, and risk management; and the generated risk tracking record table and the data and information of the risk management asset library are stored on the cloud server. Risks can occur at any time and place in the project implementation process, and risk identification, analysis, tracking and management are carried out in real time through a risk management module, so that risk hazards are eliminated, avoided, transferred or relieved in a planned mode, and a risk tracking record table and a risk management asset library are output.
The quality assurance module 223 is used for quality assurance processes of all implementation projects, provides an effective personnel organization form and management method, and realizes continuous quality improvement through objective inspection and monitoring of 'process quality' and 'product quality'; and storing the data and information of the generated quality assurance plan, the process inspection list, the process penetration matrix and the project process quality scoring table on the cloud server. After the project is formally started, the quality assurance personnel objectively check and monitor the process quality through the quality assurance module, and continuously improve and organize the process quality through the steps of formulating a quality assurance plan, checking the process, penetrating the process, grading the project and collecting a process improvement suggestion; and outputting a quality assurance plan, a process inspection list, a process penetration matrix and a process quality scoring table.
The measurement analysis module 224 is used for establishing, updating and maintaining project measurement data such as project progress, quality, workload, stability and the like, and qualitatively measuring the health condition of the project; the data and information of the generated metric analysis table are stored on the cloud server. Measurement analysis is needed every week after the project is formally started, a project implementation plan, a defect management table, a change tracking table and a risk tracking recording table are used as input of a measurement analysis module, and a measurement analysis table is output through the specific steps of collecting project measurement data, summarizing and analyzing the measurement data, issuing measurement results and periodically evaluating a measurement system.
The configuration management module 225 is used to ensure the integrity and traceability of all configuration items by performing version control, change control, etc., and using configuration management software; the system is responsible for making a configuration management plan, managing the configuration library, controlling the version and controlling the baseline change; and storing the data and information of the generated configuration management plan, the baseline status report, the configuration audit report and the signature and seal paper document record table on the cloud server. The configuration management activity runs through the whole implementation process of the project, the configuration management module effectively protects the project work result, and the configuration management plan, the baseline state report, the configuration audit report and the document record sheet are output through the specific steps of determining a configuration accountant, determining a configuration management plan, examining and approving the configuration management plan, creating a configuration library, setting the project catalog authority, controlling the version and managing delivery.
The technical review module 226 is used for specifying the technical review process of the engineering process, and aims to control the effectiveness of review activities and ensure that problems and defects are found as early as possible, so that the cost is effectively reduced, rework is reduced, the project cycle is shortened, and the product quality is improved; and 5-10% of the workload in the project workload arrangement should be used for peer review; and the data and the information of the generated BUG management table are stored on the cloud server.
The technical review module is responsible for technical review processes of core engineering processes such as requirement research, requirement analysis, software design and the like, and comprises the steps of determining a review group, distributing review materials and problem record sheets, determining a review mode, executing review concrete steps, and outputting technical review records and a BUG management table. The system comprises four technical evaluation processes: (1) the output of the demand investigation module, namely user demand specification, is used as the input of the demand analysis module after technical evaluation; (2) the output of the demand analysis module, namely a demand specification, is used as the input of the software design module after technical evaluation; (3) the output of the software design module, such as detailed design instruction, prototype design and the like, is used as the input of the coding and self-testing module after technical evaluation; (4) and the program code of the output material of the coding and self-testing module is used as the input of the integrated testing module after technical evaluation.
The management review module 227 is used for reviewing the milestone nodes in the process of managing the project, and aims to standardize the management review process and ensure the feasibility of management review, including preparation before review, decision of review modes, review execution and review record sorting; and the generated data and information of the management review record are stored on the cloud server. In the stages of milestone node-project negotiation, project definition, project development and product confirmation of the project transverse life cycle, the project can enter the next stage after being managed and reviewed, and a management review record sheet is output after the specific steps of review preparation, review mode decision, review execution, review record arrangement and follow-up tracking of the management review module 227.
The implementation steps of the present invention are described above by way of an exemplary item, which is not intended to limit the applicability of the present invention. The technical personnel can adopt an iteration and increment development mode to carry out the actual project process, and the iteration development model and the increment development model are standard development model extensions. The life cycle of the project is selected according to the principles of waterfall, increment and iteration, and the increment and the iteration are preferably performed 3 to 4 times in principle.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (5)
1. A software integration project matrixed process management system, comprising:
the system comprises a contract signing module, a requirement investigation module, a hardware management module, a requirement analysis module, a software design module, a coding and self-testing module, an integrated testing module and a program release module;
the contract signing module is used for generating a project contract, a project task entrusting sheet, a project appointed book and a project category definition book according to project requirements and storing the project contract, the project task entrusting sheet, the project appointed book and the project category definition book to a cloud server;
the requirement research module is used for acquiring and sorting user requirements; generating a user requirement specification and a requirement confirmation sheet, and storing the user requirement specification and the requirement confirmation sheet to a cloud server;
the hardware management module is used for purchasing, receiving, installing and checking hardware and network equipment; generating a hardware equipment purchase requisition, an equipment receiving confirmation and an equipment acceptance order;
the requirement analysis module is used for converting the user requirement into a system service model and determining the project requirement of the software to be developed;
the software design module is used for generating an interface prototype, a database design report, a summary design specification and a detailed design specification according to a system service model and the project requirements;
the coding and self-testing module is used for generating a software program, a version updating record, a database updating record, a unit test report and a software operation and use instruction for an interface prototype, a database design, a summary design instruction and a detailed design instruction output by the software design module;
the integrated test module is used for integrating and testing each module corresponding to the software program output by the self-test module and encoding the software program, and verifying the service logic; generating an integrated test case, an integrated test application table, a test BUG result, an integrated test report and a tested program package;
and the program release module is used for releasing a notice of the program war/rar package and the version generated by the software product which passes the test.
2. The system of claim 1, further comprising:
the data initialization module is used for importing the project original data into a database of a software product to be developed and generating an initialization data range confirmation list and an initialization data confirmation list;
the system training module is used for determining the generated training sign-in sheet, the generated examination sign-in sheet and the generated examination score sheet;
the system testing module is used for compiling a system testing case according to the user requirement specification and the requirement confirmation list and carrying out system comprehensive testing on the software program issued by the program; generating a system test case, a system test application table, a system test report and a stable program package;
the trial operation module is used for supervising and managing data backup and system rollback preparation work before trial operation and generating a trial operation maintenance record table;
and the project acceptance module is used for generating a project acceptance application book and a project acceptance report.
3. The system of claim 2, further comprising:
the system maintenance module is used for tracking the follow-up problem and demand modification of the software system and generating a system maintenance form;
the demand management module is used for establishing and maintaining a demand tracking matrix and controlling the change of the demand; generating a demand tracking matrix and a product service data document record table;
and the defect management module is used for standardizing the defect processing flow, recording the defects, evaluating the influence of the modified defects on the associated contents and closing and tracking the defects, and generating a defect management table.
4. The system of claim 1, further comprising:
the project planning module is used for generating a project material tool list, a project plan, a project implementation plan and a user-defined process description according to the work task;
the project starting module is used for starting the holding of the conference and the project formal starting notification work and generating a starting conference summary;
the project monitoring module is used for periodically tracking the progress condition of the project plan and generating a weekly report and a milestone report;
and the project ending module is used for project ending management and generating a project summary report, a personnel performance assessment table and a project summary conference record.
5. The system of claim 1, further comprising:
the change control module is used for judging the change type, changing the application, writing and submitting the change application, confirming the change, implementing the change and verifying the change, and generating a change application form, a change confirmation form and a change tracking form;
the risk management module is used for performing the risk management process of all the implementation projects and generating a risk tracking record table and a risk management asset library;
the quality assurance module is used for generating a quality assurance plan, a process check list, a process penetration matrix and a project process quality scoring table;
the measurement analysis module is used for generating a measurement analysis table according to project progress, quality, workload and stability;
the configuration management module is used for making a configuration management plan, managing the configuration management, controlling the version and changing the baseline, and generating a configuration management plan, a baseline state report, a configuration audit report and a signature and seal paper document record table;
the technical review module is used for stipulating and managing the technical review process of the engineering process and generating a technical review defect list;
and the management evaluation module is used for evaluating the milestone nodes in the project management process and generating management evaluation records.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911167518.3A CN110888626A (en) | 2019-11-25 | 2019-11-25 | Software integration project matrix type process management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911167518.3A CN110888626A (en) | 2019-11-25 | 2019-11-25 | Software integration project matrix type process management system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110888626A true CN110888626A (en) | 2020-03-17 |
Family
ID=69748689
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911167518.3A Pending CN110888626A (en) | 2019-11-25 | 2019-11-25 | Software integration project matrix type process management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110888626A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111401853A (en) * | 2020-03-24 | 2020-07-10 | 上海捷规建筑工程咨询有限公司 | Intelligent construction project management system based on BIM |
| CN111553664A (en) * | 2020-05-11 | 2020-08-18 | 重庆金美通信有限责任公司 | Method for realizing intelligent management of design and production of communication equipment based on 5G technology |
| CN112148252A (en) * | 2020-09-03 | 2020-12-29 | 杭州云徙科技有限公司 | Software research and development requirement-based full life cycle management system and tracking method |
| CN116301760A (en) * | 2023-05-22 | 2023-06-23 | 深圳市长亮科技股份有限公司 | Application design system for software development |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106327152A (en) * | 2016-08-11 | 2017-01-11 | 宁波亦道信息科技有限公司 | Integrated iteration software development process control system and method |
| WO2017122285A1 (en) * | 2016-01-13 | 2017-07-20 | 三菱電機株式会社 | Development progress management device and development progress management method |
| CN108537503A (en) * | 2018-03-26 | 2018-09-14 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | software development management system |
| CN108932589A (en) * | 2018-07-05 | 2018-12-04 | 武汉科技大学 | A kind of IT application in enterprises project implementation management system |
-
2019
- 2019-11-25 CN CN201911167518.3A patent/CN110888626A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017122285A1 (en) * | 2016-01-13 | 2017-07-20 | 三菱電機株式会社 | Development progress management device and development progress management method |
| CN106327152A (en) * | 2016-08-11 | 2017-01-11 | 宁波亦道信息科技有限公司 | Integrated iteration software development process control system and method |
| CN108537503A (en) * | 2018-03-26 | 2018-09-14 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | software development management system |
| CN108932589A (en) * | 2018-07-05 | 2018-12-04 | 武汉科技大学 | A kind of IT application in enterprises project implementation management system |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111401853A (en) * | 2020-03-24 | 2020-07-10 | 上海捷规建筑工程咨询有限公司 | Intelligent construction project management system based on BIM |
| CN111553664A (en) * | 2020-05-11 | 2020-08-18 | 重庆金美通信有限责任公司 | Method for realizing intelligent management of design and production of communication equipment based on 5G technology |
| CN111553664B (en) * | 2020-05-11 | 2022-10-14 | 重庆金美通信有限责任公司 | System for realizing intelligent management of communication equipment design and production based on 5G technology |
| CN112148252A (en) * | 2020-09-03 | 2020-12-29 | 杭州云徙科技有限公司 | Software research and development requirement-based full life cycle management system and tracking method |
| CN112148252B (en) * | 2020-09-03 | 2024-02-09 | 广东云徙智能科技有限公司 | Management system and tracking method based on full life cycle of software development requirements |
| CN116301760A (en) * | 2023-05-22 | 2023-06-23 | 深圳市长亮科技股份有限公司 | Application design system for software development |
| CN116301760B (en) * | 2023-05-22 | 2023-09-05 | 深圳市长亮科技股份有限公司 | Application Design System for Software Development |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110888626A (en) | Software integration project matrix type process management system | |
| Lewis et al. | Software testing and continuous quality improvement | |
| US8606548B2 (en) | Energy facility control system | |
| WO2015187808A1 (en) | Information integration system and methodology | |
| US20040167790A1 (en) | Method of conducting business in a system requiring frequency up-dates and corrections | |
| Larsson et al. | Revisiting the challenges in aligning RE and V&V: Experiences from the public sector | |
| Wong et al. | A systematic approach to software quality assurance: the relationship of project activities within project life cycle and system development life cycle | |
| Özdağoğlu et al. | Monitoring the software bug‐fixing process through the process mining approach | |
| Ambartsoumian et al. | Implementing quality gates throughout the enterprise it production process | |
| Tariq et al. | Requirements Engineering process for Software-as-a-Service (SaaS) cloud environment | |
| JP2004192125A (en) | Project management system, data structure used therefor, and project management method | |
| Kivinen | Applying QFD to improve the requirements and project management in small-scale project | |
| Cleveland et al. | Toward a Model for Customer-Driven Release Management. | |
| Scheck et al. | The SAP Activate Method and Corresponding SPICE Models | |
| Das et al. | Using ISO 90003 for software “design and development” in large virtual teams | |
| Kurtel | Measuring and monitoring software maintenance services: An industrial experience | |
| Sai et al. | Driving component selection through actor-oriented models and use cases | |
| TW201421386A (en) | Continuously data quality controlling and auditing system | |
| Suryaman et al. | Enterprise Resource Planning System Design Project System Module Using SAP Application With SAP Activate Methodology in PT XYZ | |
| Rearden et al. | Quality Assurance Plan for the SCALE Code System | |
| Dean et al. | Cots workshop: continuing collaborations for successful cots development | |
| Helstrom et al. | Information Technology Asset Management | |
| Korolev et al. | Instruments of Configuration Management in Nuclear Power Plant Projects | |
| Kneuper et al. | Selected Current Trends in Software Processes | |
| Kajko-Mattsson et al. | Lesson learned from attempts to implement daily build |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200317 |
|
| RJ01 | Rejection of invention patent application after publication |