Bank information system product management method

Abstract

The invention discloses a bank information system product management method, which comprises links of product planning and design, detailed function design and development, multi-dimensional test and product release, product exit and resource management and full life cycle data management, and defines business value and technical feasibility evaluation standards. The test, approval and resource management requirements are standardized, product full-life-cycle standardized digital and intelligent management is achieved, a computer program of the storage medium comprises a product catalog and function management module, an information retrieval display module and a transaction cockpit module, and SLA index retrieval, user-defined analysis and information change notification are supported. According to the method, the problems of lack of product management whole-process specifications, dispersion of directory platforms, insufficient decision data support and lack of service quality management and control are solved, product whole-process standardized management is realized, cross-department cooperation efficiency is improved, data support is provided for decision, product service quality is guaranteed, and the method has remarkable application value.

Description

Technical Field

[0001] This invention relates to the field of banking information system technology, specifically to a banking information system product management method and storage medium, for realizing digital and intelligent management and efficient operation of banking information system products throughout their entire lifecycle. Background Technology

[0002] In the IT infrastructure development of commercial banks, various information systems have been built, including customer service systems for customers, comprehensive management service platforms for internal employees, and intelligent marketing management platforms. To improve IT governance efficiency, the requirements management department has formulated a full-chain management procedure for IT requirements, covering all stages from requirement submission, review, implementation, testing, and deployment. A supporting integrated IT requirements service system has also been developed, achieving online closed-loop management of key requirements stages and improving requirement response efficiency. However, existing technologies have the following significant shortcomings:

[0003] 1. Lack of product management strategy: Although full-process demand management has been achieved, management standards covering the entire life cycle of system products have not been established, and there is a lack of a continuous operation mechanism for products from design to delisting, resulting in idle and wasted system resources and high communication and collaboration costs between departments.

[0004] 2. Lack of a catalog management platform: The bank's internal information system has a wide range of product business and diverse departmental needs. It adopts a decentralized management model and lacks an integrated platform to centrally manage and display product resources. Employees find it difficult to quickly obtain complete product information, and cross-departmental collaboration efficiency and resource sharing capabilities are limited.

[0005] 3. Insufficient data support for decision-making: The lack of multi-dimensional and multi-scenario analysis tools for product operation, transactions and user usage makes it difficult to accurately grasp the product operation status, resulting in a lack of scientific data support for product management decisions.

[0006] 4. Insufficient service quality control: A standardized product service level management mechanism has not been established, and service indicators such as product availability and response time lack clear definition and monitoring, which affects the user experience. Summary of the Invention

[0007] This invention aims to overcome the shortcomings of existing technologies and provide a product management method for bank information systems. By establishing a management strategy covering the entire product lifecycle, it clarifies the specific requirements for each stage of product design, development, release, and delisting, achieving standardized and intelligent management of the entire product process. Through the construction of an integrated product catalog management platform, it integrates product information and functional item information, supports precise retrieval, and improves the efficiency of product information management and cross-departmental collaboration. It provides multi-dimensional and multi-scenario product operation analysis tools, combined with Service Level Agreement (SLA) indicators, to provide comprehensive data support for product management decisions. Finally, by establishing a standardized product service level management mechanism, it clarifies and monitors product service indicators, ensuring product service quality.

[0008] To achieve the above objectives, the present invention is implemented through the following technical solution:

[0009] This invention discloses a product management method for a bank information system, the method comprising the following steps:

[0010] Step 1) Product Planning and Design: The requirements coordination team receives requirement requests, analyzes the application scenarios, data scope, and target user groups of the requirements, conducts product planning, clarifies the product identifier, product name, responsible department, person in charge, and deployment platform, and evaluates the business value and technical feasibility; if it can be integrated with existing product functions, the relationship between the requirements and existing products is established and the requirements are submitted for approval.

[0011] Assessing business value includes projected revenue growth rate and percentage improvement in business efficiency; assessing technical feasibility includes the support capabilities of the existing technical architecture and resource matching.

[0012] Step 2) Detailed Functional Design and Development: Based on requirements and product definition, developers design functional solutions, clarify functional modules and technical paths, establish mapping relationships between functional items and the product, compile functional design documents including input / output formats, processing logic flow, and interface specifications, and begin development work;

[0013] Step 3) Multi-dimensional Testing and Product Release: Conduct functional, performance, security, and compatibility tests; after testing, the request initiator submits a launch application, and the requirements coordination team evaluates the system test pass rate, user acceptance test results, and production preparation status (including production plan, rollback plan, and training plan). After approval, the product is released; the test pass rate must reach over 95%; production preparation status includes production plan, rollback plan, and training plan;

[0014] Step 4) Product Exit and Resource Management: The requesting party submits a decommissioning application including the reasons and scope of impact; the request coordination team conducts a business impact assessment, a technical risk assessment, and reviews alternative solutions. After approval, the product or function is delisted, and resource release and data archiving are carried out; the business impact assessment includes the results of customer satisfaction surveys; the technical risk assessment includes system compatibility risks and data integrity risks;

[0015] Step 5) Product lifecycle data management: Through the product catalog and function management module, realize the automated collection of product information and function item information, version iteration management and metadata asset accumulation; metadata assets include requirement documents, test reports and production records.

[0016] Preferably, in step 1), product planning also includes determining a product service level agreement (SLA) that specifies that the product availability is ≥99.9% and the response time is ≤2 seconds.

[0017] Preferably, in step 2), the detailed functional design also includes performing coupling analysis of functional modules to ensure low coupling and high cohesion between modules.

[0018] Preferably, in step 3), the compatibility test includes testing the product's operation on Windows and Linux operating systems, Chrome and Firefox browsers, and mobile phones and tablets.

[0019] Preferably, in step 4), the business impact assessment includes a survey on the impact on customer satisfaction, with a sample size of no less than 500.

[0020] Preferably, in step 5), the product metadata assets include the full-process document information associated with the product, the technical parameters of functional items, and the product service level agreement (SLA) indicators.

[0021] The present invention provides a storage medium for implementing the product management method of the bank information system, wherein a computer program is stored thereon, and when the computer program is executed by a processor, the various steps of the method are implemented.

[0022] Preferably, the computer program further includes a system product information retrieval and display module, which supports the retrieval of product service level agreement (SLA) indicators, including availability and response time.

[0023] Preferably, the product transaction dashboard module of the computer program also supports custom indicator analysis. Users can configure personalized product operation analysis indicators, including function usage rate and user complaint rate.

[0024] Preferably, the product catalog and function management module of the computer program also has a product information change notification function, which automatically sends an email notification to relevant personnel when product information changes.

[0025] Beneficial effects:

[0026] Standardized management throughout the entire product lifecycle: By clearly defining the specific requirements for each stage (such as business value assessment standards, test pass rate thresholds, review content, etc.), closed-loop control of products from planning to delisting can be achieved, improving product operation efficiency and reducing resource waste and communication costs.

[0027] Integrated catalog and precise search: The product catalog and function management module centrally manages product information, while the system's product information search and display module supports precise search based on multiple conditions (including SLA indicators), significantly improving cross-departmental collaboration efficiency and resource sharing capabilities.

[0028] Data-driven scientific decision-making: The product transaction dashboard combines multi-dimensional and multi-scenario data with SLA indicators, supports customized analysis, and provides scientific support for decisions such as product optimization, resource allocation, and service level adjustment, thereby improving the accuracy of decision-making.

[0029] Effective Service Quality Assurance: By establishing and monitoring Product Service Level Agreements (SLAs), we clarify indicators such as product availability and response time, ensuring user experience and improving customer and internal user satisfaction. Attached Figure Description

[0030] Figure 1 This is a product management strategy diagram for the information system of this invention.

[0031] Figure 2 This is a schematic diagram of the product transaction dashboard interface of the Zhejiang Provincial Information System of this invention. Detailed Implementation

[0032] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0033] Invention content / principle:

[0034] This invention provides a product management method for a bank information system, covering core aspects such as product planning and design, detailed functional design and development, multi-dimensional testing and product release, product exit and resource management, and product lifecycle data management. Simultaneously, this invention also provides a storage medium on which computer programs are stored, including a product catalog and functional management module, a system product information retrieval and display module, and a product transaction dashboard module, to support the implementation of the product management method.

[0035] Meaning of Service Level Agreement (SLA): A Service Level Agreement (SLA) is a formal agreement that clarifies the service quality, service scope, and division of responsibilities between a service provider and a user. In the management of bank information system products, it is mainly used to define the core service indicators of the product, such as: Availability: The percentage of time the product operates normally within a specified period (e.g., ≥99.9%, meaning that the annual downtime does not exceed approximately 8.76 hours); Response Time: The time it takes for the product to return a result after a user initiates a request (e.g., ≤2 seconds, ensuring the smoothness of business operations); Fault Recovery Time: The maximum time it takes for the product to return to normal operation after a fault (e.g., ≤4 hours, reducing the impact of business interruption).

[0036] Example 1: Implementation Method of Bank Information System Product Management

[0037] Step 1: Product Planning and Design Requirements Coordination Team receives requirement requests from business departments, technology departments, or other channels. They conduct in-depth analysis of the application scenarios (e.g., personal finance, corporate finance, interbank business), data scope (customer data, account data, transaction data, etc.), and target user groups (external customers, internal employees, partner institutions, etc.). Based on the analysis results, product planning is carried out, defining fundamental elements such as product identifier (a unique code, which can be set using a combination of letters and numbers as needed), product name (e.g., Intelligent Corporate Deposit Management System), responsible department (e.g., Corporate Finance Department), responsible person (e.g., Product Manager), and deployment platform (e.g., the bank's internal business systems, cloud computing platforms, and other existing technology platforms commonly used by the bank). Simultaneously, business value is assessed, including projected revenue growth (e.g., projected annual growth of 10%) and percentage improvement in business efficiency (e.g., 30% improvement in operational efficiency); technical feasibility is assessed, including the support capabilities of the existing technical architecture (e.g., microservice architecture can support high concurrency requirements) and resource matching (e.g., server and storage resources can meet the requirements). A Product Service Level Agreement (SLA) is determined, specifying product availability (≥99.9%) and response time (≤2 seconds). If it is found that the requirement can be integrated with the bank's existing products, such as adding a smart reconciliation function to the existing corporate account management to meet the requirement and achieve the integration of the added functional modules, then the relationship between the requirement and the existing products is established. Subsequently, the requirement and related information are submitted to the requirement approval stage. After approval by the business, technology and risk control departments, it will proceed to the next process.

[0038] Step Two: Detailed Functional Design and Development Requirements After the requirements are reviewed and approved, the development team receives the development tasks and designs functional solutions based on the requirements and product definition. The functional modules covered by the requirements are clearly defined, such as account opening, deposit management, and reconciliation modules. For each functional module and its sub-modules, the technical implementation path is determined, for example, using a microservice architecture to achieve independent deployment and expansion of the module. Simultaneously, a mapping relationship between functional items and the product is established, clarifying the product to which each functional item belongs. The development team conducts coupling analysis of the functional modules to ensure low coupling and high cohesion between modules, facilitating subsequent maintenance and upgrades. A functional design document is compiled, detailing the input and output formats of each functional item (e.g., interface request parameters are in JSON format, and the returned results include fields such as transaction status, amount, and time), processing logic flow (e.g., transaction processing requires verification, accounting, and notification steps), and interface specifications (e.g., API uses the RESTful protocol, and the call address is set). After completing the design, the development phase begins, and code development proceeds according to the functional design document.

[0039] Step 3: Multi-dimensional Testing and Product Release After development is complete, the system undergoes multi-dimensional testing. Functional testing verifies whether the functions meet design requirements; performance testing verifies the system's performance under high concurrency (e.g., simulating 1000 concurrent users) and large data volumes (e.g., millions of transaction data); security testing verifies the system's vulnerabilities (e.g., SQL injection, XSS attacks) and data protection capabilities; compatibility testing includes testing the product on Windows 10, Linux CentOS operating systems, Chrome 110, Firefox 109 browsers, and Android and Apple tablet devices. Once system testing is completed and the pass rate reaches over 95%, and user acceptance testing results are satisfactory, the request initiator submits a launch application. The launch application must include a test report, a production plan (clearly specifying the launch date (year, month, and day), and steps including environment preparation, program deployment, and verification), a rollback plan (rolling back to the pre-launch version in case of problems), and a training plan (setting two training sessions for user departments, each lasting 2 hours). After the requirements coordination team accepts the launch application, it evaluates the launch conditions. Upon approval, the product is officially released and put into actual operation.

[0040] Step Four: Product Exit and Resource Management When a product or its functional modules are to be discontinued due to business strategy adjustments, technical architecture iterations, or other reasons, the requesting party submits a decommissioning application. The application must specify the reasons for discontinuation or removal, the scope of impact (number of customers and business departments involved), and the proposed discontinuation time. The requirements coordination team reviews the decommissioning application. The business impact assessment includes a customer satisfaction survey with a sample size of at least 500 responses, analyzing the degree of impact on customer satisfaction. The technical risk assessment includes system compatibility risks (e.g., whether it affects other related systems) and data integrity risks (e.g., whether data can be completely migrated or archived). The alternative solution review includes whether there are alternative products or functions that meet business needs, and the maturity of the alternative solutions (e.g., the alternative product has been running for 3 months without major failures). After approval, the relevant product or function is officially decommissioned and ceases operation. Subsequently, system resource release (reclaiming server CPU, memory, and storage resources) and data archiving (storing product-related data to an archive server according to an archiving strategy, with a retention period that can be set to 5 years) are carried out.

[0041] Step 5: Product Lifecycle Data Management. Through the product catalog and function management modules, automated collection of product and function information is achieved, including requirement documents, design documents, test reports, and production records generated at each stage of product design, development, testing, release, and delisting. The module supports product version iteration management; when product functions are updated, version change information is automatically recorded, such as version number, change content (e.g., adding intelligent reconciliation function), and change time (year, month, day). Simultaneously, product metadata assets are accumulated. These metadata assets include product-related full-process document information, technical parameters of function items (e.g., reconciliation function processing time ≤ 1 minute), and product service level agreement (SLA) indicators (availability, response time), providing a data foundation for subsequent information retrieval and data analysis.

[0042] Implementation of the storage medium and functional modules of the present invention:

[0043] The storage medium of the present invention stores a computer program, which, when executed by a processor, implements the various steps of the above-described bank information system product management method. The computer program also includes the following functional modules.

[0044] Functional Module 1: Product Catalog and Function Management Module

[0045] Product information management and product function item management functions have been built, and they are seamlessly integrated with the bank's integrated IT service system (such as...). Figure 1 As shown, this achieves the linkage between the requirement process and the product management process, realizing closed-loop control of the entire product lifecycle. Standardized product access: Product creation requires the submission of product planning documents, SLA agreements, and other materials, which must be reviewed and approved by the business, technology, and risk control departments before creation. Product release requires approval through an online application; product delisting requires approval through a delisting application, ensuring the standardization of the entire product lifecycle management. Dynamic association and version management: Developers can maintain the association between products and functional items in the system. When product functions are iterated, the system automatically collects change information of functional items and generates version iteration records. The module also has a product information change notification function. When product information (such as responsible persons, SLA indicators) changes, it automatically sends email notifications to relevant responsible departments and personnel. Metadata asset accumulation: Documents and data from the entire product process are collected and stored to form a product metadata asset library, including product-related full-process document information, functional item technical parameters, product SLA indicators, etc., providing data support for other modules.

[0046] Functional Module Two: System Product Information Retrieval and Display Module

[0047] This module prioritizes user experience and includes a wealth of pre-defined product attribute tags, such as product type, deployment platform, applicable region, and Service Level Agreement (SLA) metrics (availability, response time). Users can precisely locate product information by selecting combinations of these attribute tags. The system's user interface supports keyword search, attribute tag search, and combined search. Search results intuitively display product information (identifier, name, responsible department, SLA metrics, etc.), function details (descriptions and technical parameters of each function), access points (system login address, function operation path), and operation guides (user manual, training video links), significantly improving the efficiency of users obtaining product information.

[0048] Functional Module 3: Product Transaction Dashboard (e.g.) Figure 2 The image shown is the product transaction dashboard for the Zhejiang Provincial Information System.

[0049] This presentation showcases and compares the operational transactions and user usage of various products from multiple dimensions and scenarios. Multi-dimensional analysis includes: From a product perspective, it displays transaction volume, transaction amount, user base, in-bank user coverage, and SLA compliance for each product (availability ≥ 99.9%, response time ≤ 2 seconds); from a product function perspective, it displays the usage frequency, transaction amount, and number of failures for each function; from a product type perspective, it compares transaction data and SLA metrics for different product types (e.g., deposits, loans, intermediary services); from a deployment platform perspective, it compares product usage across different platforms (e.g., mobile banking, branch counters, corporate online banking); from the transaction initiator's region perspective, it displays the product transaction distribution across different regions; and from the transaction initiation channel perspective, it displays transaction data for different channels such as branch counters and electronic channels. Multi-scenario analysis: From the product management unit scenario, it displays the transaction volume, transaction amount, number of products, product coverage, and SLA compliance rate of the products managed by each management unit; from the actual transaction institution scenario, it displays the product transaction status and SLA execution status of each branch; from the historical transaction trend scenario, it displays the historical trends of indicators such as product transaction volume, transaction amount, and SLA compliance rate. Simultaneously, it supports user-defined indicator analysis, allowing users to configure personalized product operation analysis indicators, such as the function utilization rate of specific products (reconciliation function utilization rate), user complaint rate (monthly complaint rate ≤ 0.5%), etc. Users can comprehensively grasp the operation, usage, and service quality of each product through the dashboard, providing data support for management decisions such as product optimization, resource allocation, and service level adjustments.

[0050] Connection relationships between the modules of this invention:

[0051] The product catalog and function management module forms the core data layer: it seamlessly integrates with the bank's unified IT service system (e.g., ...). Figure 1As shown, information about the entire product lifecycle (such as product design, feature development, launch, and delisting) is collected from the requirements process and transformed into product metadata assets (including basic product information, functional item relationships, version iteration records, etc.).

[0052] The system's product information retrieval and display module serves as the information interaction layer. Based on the metadata assets of the product catalog and function management module, it provides users with accurate product information retrieval and display functions through preset product attribute tags (such as product type, SLA indicators, deployment platform, etc.), enabling business departments to efficiently obtain product information. The product transaction dashboard module serves as the decision support layer. Also relying on the metadata of the product catalog and function management module, it combines actual product operation transaction data (such as transaction volume, user volume, transaction amount, etc.) to conduct data analysis and visualization from multiple dimensions (product, function item, region, channel, etc.) and multiple scenarios (management unit, transaction institution, historical trends, etc.), providing data support for product management decisions.

[0053] Therefore, the product catalog and function management module is the data hub, connecting downwards to collect all information from the demand process, and providing data fuel for the information retrieval module and transaction dashboard module upwards. The three form a closed loop of data collection, information interaction, and decision support, realizing the full-link digitalization of bank information system products from management to operation.

[0054] Finally, it should be noted that the present invention is not limited to the above embodiments, and many variations are possible. All variations that can be directly derived or conceived by those skilled in the art from the disclosure of the present invention should be considered within the scope of protection of the present invention.

Claims

1. A method for managing bank information system products, characterized in that, The method includes the following steps: Step 1) Product Planning and Design: The requirements coordination team receives requirement requests, analyzes the application scenarios, data scope, and target user groups of the requirements, conducts product planning, clarifies the product identifier, product name, responsible department, person in charge, and deployment platform, and evaluates the business value and technical feasibility; if it can be integrated with existing product functions, the relationship between the requirements and existing products is established and the requirements are submitted for approval. Assessing business value includes projected revenue growth rate and percentage improvement in business efficiency; assessing technical feasibility includes the support capabilities of the existing technical architecture and resource matching. Step 2) Detailed Functional Design and Development: Based on requirements and product definition, developers design functional solutions, clarify functional modules and technical paths, establish mapping relationships between functional items and the product, compile functional design documents including input / output formats, processing logic flow, and interface specifications, and begin development work; Step 3) Multi-dimensional Testing and Product Release: Conduct functional, performance, security, and compatibility tests; after testing, the request initiator submits a launch application, and the requirements coordination team evaluates the system test pass rate, user acceptance test results, and production preparation status (including production plan, rollback plan, and training plan). After approval, the product is released; the test pass rate must reach over 95%; production preparation status includes production plan, rollback plan, and training plan; Step 4) Product Exit and Resource Management: The requesting party submits a delisting application including the reasons and scope of impact; the request coordination team conducts business impact assessment, technical risk assessment, and reviews alternative solutions. After approval, the product or function is delisted, and resource release and data archiving are carried out; the business impact assessment includes the results of customer satisfaction surveys. Step 5) Product lifecycle data management: Through the product catalog and function management module, realize the automated collection of product information and function item information, version iteration management and metadata asset accumulation; metadata assets include requirement documents, test reports and production records.

2. The method for managing bank information system products according to claim 1, characterized in that, In step 1), product planning also includes determining the product service level agreement (SLA), specifying that the product availability is ≥99.9% and the response time is ≤2 seconds.

3. The method for managing bank information system products according to claim 1, characterized in that, In step 2), the detailed functional design also includes performing coupling analysis of functional modules to ensure low coupling and high cohesion between modules.

4. The method for managing bank information system products according to claim 1, characterized in that, In step 3), compatibility testing includes testing the product's performance on Windows and Linux operating systems, Chrome and Firefox browsers, and mobile and tablet devices.

5. A method for managing bank information system products according to claim 1, characterized in that, In step 4), the business impact assessment includes a survey on the impact on customer satisfaction, with a sample size of no less than 500.

6. The method for managing bank information system products according to claim 1, characterized in that, In step 5), the product metadata assets include the full-process document information associated with the product, the technical parameters of functional items, and the product service level agreement (SLA) indicators.

7. A storage medium for implementing the product management method of a bank information system according to any one of claims 1-6, wherein a computer program is stored thereon, characterized in that, When the computer program is executed by the processor, it implements the various steps of the method.

8. The storage medium according to claim 7, characterized in that, The computer program also includes a system product information retrieval and display module, which supports the retrieval of product service level agreement (SLA) indicators, including availability and response time.

9. The storage medium according to claim 7, characterized in that, The product transaction dashboard module of the computer program also supports custom indicator analysis. Users can configure personalized product operation analysis indicators, including function usage rate and user complaint rate.

10. The storage medium according to claim 7, characterized in that, The product catalog and function management module of the computer program also has a product information change notification function, which automatically sends email notifications to relevant personnel when product information changes.

Images