KR100341393B1 - System and method for object oriented ERP project implementation - Google Patents

Abstract

In the present invention, in the development of an object-oriented enterprise resource management project, five views representing different functional, non-functional, and organizational perspectives are gathered, integrated, and checked for consistency through computer control. It is intended to better represent all the macro and micro requirements of an enterprise resource management system. According to an embodiment of the present invention, a first step of selecting a method, a parameter, and a property desired by a user by performing a consistency test by receiving operation requirement definition data, analysis data, and design data to be tested; A second step of performing a simulation on data consistency based on the result selected in the first step; A third step of deriving an inconsistent portion based on rules of data names to be calculated and mutual consistency; A fourth step of correcting the mismatched parts derived in the third step; A fifth step of storing the data modified in the fourth step in a database storage; A sixth step of receiving the modified data from the fifth step and performing schedule planning, quality control, project management, and education management in a project control management unit; And a seventh step of processing data according to the event when a user generates a specific event by receiving data stored in the database storage unit, a process execution result of the project control management unit, and new data. An object-oriented enterprise resource management project development method is provided.

Description

System and method for object oriented ERP project implementation

The present invention relates to a system and method for developing an object-oriented enterprise resource management project. In particular, five views representing different functional, non-functional and organizational perspectives are gathered and integrated by computer control. The present invention relates to a system and method for developing an object-oriented enterprise resource management project that can more accurately express all the macro and micro requirements of the enterprise resource management system through the inspection process.

To develop a successful information system in a rapidly changing business environment, a methodology with reasonable and diverse modeling expressive power must be provided. This development methodology is an important tool for building an enterprise-wide resource management system, but it must be benchmarked with other methodologies to be differentiated for the environment.

Therefore, the development methodology should have a high expressive power in various work areas based on the basic structure, have a reasonable and flexible application principle for the work-oriented approach, and have a case tool and a supporting tool for systematic documents.

In the past, the outputs and guidelines for each stage of the development process leading to such requirements analysis, design, implementation, and testing have not been systematically used, and have used foreign methodologies, and have experienced huge foreign currency outflow due to its license fee. There was a problem that the reusability, standardization, and modeling power were not very good due to the development of non-object-oriented information engineering method.

The present invention has been made to solve the problems of the prior art as described above, based on the basic structure has a high expressive power for a variety of work areas, the application principle to the task-oriented approach should be reasonable and flexible, case tools and The purpose is to provide an object-oriented enterprise resource management project development system and method for providing systematic documents.

1 is a block diagram of a computer-controlled control system of the object-oriented enterprise resource management project development method according to an embodiment of the present invention,

2 is a flowchart illustrating an operation process of a computer-controlled control system of the object-oriented enterprise resource management project development method illustrated in FIG. 1;

3 is a view showing the overall configuration of the object-oriented enterprise-wide resource management project development methodology according to an embodiment of the present invention,

4 is a detailed configuration diagram of the schedule plan shown in FIG. 3,

5 is a detailed configuration diagram of the education and change management shown in FIG.

6 is a detailed configuration diagram of the project management shown in FIG.

7 is a detailed configuration diagram of the quality control shown in FIG.

8 is a detailed configuration diagram of the requirements definition shown in FIG.

9 is a detailed configuration diagram of the requirements specification shown in FIG.

10 is a detailed configuration diagram of the analysis step illustrated in FIG. 3,

11 is a detailed configuration diagram of the design specification shown in FIG.

12 is a detailed configuration diagram of the implementation step illustrated in FIG. 3,

FIG. 13 is a detailed configuration diagram of the test step shown in FIG. 3.

According to the present invention for achieving the object as described above, the test line for inputting the operational requirements definition data, analysis data and design data to be tested to perform a consistency test to select a method, parameters and properties desired by the user With the government; A simulator configured to perform a simulation on data integrity based on the result selected by the test selector; A non-matching part deriving unit for deriving a non-matching part based on the rules of the data names to be calculated and the mutual correlation; A corrector for correcting the mismatched parts derived from the mismatched part deriving unit; A database storage unit for storing the data modified by the correction unit in itself; A project control management unit which receives the modified data from the database storage unit and performs schedule planning, quality management, and project management and education management; And an implementation progress unit configured to process data according to the event when a user generates a specific event by receiving data stored in the database storage unit, a process execution result of the project control management unit, and new data. An object-oriented enterprise resource management project development system is provided.

In addition, a first step of selecting a method, parameters and attributes desired by the user by receiving the operation requirement definition data, analysis data and design data to be tested and perform a consistency test; A second step of performing a simulation on data consistency based on the result selected in the first step; A third step of deriving an inconsistent portion based on the rules of data names to be calculated and the correlations between them; A fourth step of correcting the mismatched parts derived in the third step; A fifth step of storing the data modified in the fourth step in a database storage; A sixth step of receiving the modified data from the fifth step and performing schedule planning, quality control, project management, and education management in a project control management unit; And a seventh step of processing data according to the event when a user generates a specific event by receiving data stored in the database storage unit, a process execution result of the project control management unit, and new data. An object-oriented enterprise resource management project development method is provided.

In the following, with reference to the accompanying drawings, a preferred embodiment according to the present invention will be described in detail.

The enterprise resource management development process goes through several development cycles and a system is developed. This development process is characterized by the fact that, at any point in time, an ongoing enterprise resource management project is simultaneously analyzing, designing, and implementing the present invention. The present invention provides five views that represent several different functional, non-functional, and organizational perspectives. Through the process of gathering, integrating, and checking the consistency of the computer control, all macro and micro requirements of the enterprise resource management system can be represented more accurately.

In addition to the development and activity procedures required for object-oriented requirements analysis, implementation, and testing, a project, quality control management activities, and input / output calculation methods should be provided.

This is a way of starting a new development cycle to define the functionality of the system, designing the system accordingly, and creating a continuous version up of the system by completing a new development cycle if there is a deficiency in one development cycle. The advantage of this development process is that the complexity of the software can be partitioned and solved on a cycle-by-cycle basis, but not completely software, but by quickly creating software that can be viewed by the customer, it can reflect the actual customer's opinion.

1 is a block diagram of a computer-based control system of the object-oriented enterprise resource management project development method according to an embodiment of the present invention, the control system is an input unit 11, a test selection unit 12, a simulator unit 13 ), A non-matching part derivation unit 14, a correction unit 15, a database storage unit 16, a project control management unit 17, and an implementation progress unit 18.

This will be described in detail as follows.

First, when operation requirement definition data, analysis data, and design data to be tested are input from the input unit 11 to the test selector 12, a consistency test is performed to select a method, parameter, and property desired by a user. The data is transmitted to the simulator unit 13.

The simulator unit 13 performs a simulation on data consistency based on the rules of data names to be calculated in each processing process and the correlation between them, and the unmatched part protrusion 14 protrudes the unmatched part so that the user and Show developers the problems of how to develop enterprise resource planning projects.

Problems protruding through the mismatched portion protrusion 14 are corrected in the correction unit 15, and the data after the correction is stored in a repository of the database storage unit 17, and thus the project control management unit ( In 16), a series of tasks such as schedule planning will be processed.

At the same time, the implementation progress unit 18 performs the implementation according to the data stored in the repository of the database storage unit 17.

FIG. 2 is a flowchart illustrating an operation process of a computer-controlled control system of the object-oriented enterprise resource management project development method illustrated in FIG. 1.

First, in step S101 and step S102, if the requirements definition data and the requirements specification data are input, in step S103, a consistency test is performed and stored.

Then, in step S104 and step S105, when the analysis data and the design data are input, in step S106, a data consistency test is performed and stored.

Subsequently, in step S107, if implementation data is input, it is determined whether the implementation data are properly controlled by a computer, and if not, the process returns to the step S101, and if it is properly controlled, step S108 and step In S111, schedule planning data, project management data, training / change management data, and quality management data are received and data integrity check is performed and stored therein.

Next, in step S112, the complete modeling is calculated using the data stored after the consistency check (S103, S106, S108 to S111).

3 is a diagram showing the overall configuration of the object-oriented enterprise-wide resource management project development methodology according to an embodiment of the present invention.

The development methodology composition is largely divided into the project control management area 151 and the system development procedure area 101.

The project control management area 151 includes a schedule plan 152 for the tasks and outputs of the members participating in the project, project management according to the performance of the project performance plan 153, education system execution and change management 154. And quality management 155 to guarantee the quality of the outputs of each stage of the project.

The schedule planning 152 and the project management 153 may define an activity definition, an ordering, an estimation of an activity duration, a Gantt Chart-based schedule, and the like, so that the project can be completed at a predetermined time point. Control critical paths.

The quality management 155 is a management function for determining quality policy, purpose, and responsibility through quality planning, control, assurance, and improvement, and is performed in view of functionality, reliability, usability, efficiency, conservability, and portability.

The training and change management 154 is performed in the technical and functional aspects in parallel with the flow improvement (BPR) and enterprise resource management system building activities. In particular, the change management is analyzed for change items occurring throughout the project. And to respond.

FIG. 4 is a detailed configuration diagram of the schedule plan 152 shown in FIG. 3, wherein the schedule plan 152 includes a participant schedule 201, a monthly task report 202, and a weekly task report 203.

The participant schedule 201 means schedule management for the task of the member participating in the project.

The monthly business report 202 seeks to check the progress against the plan performance and the solution to the problem through the monthly report on the project execution.

The weekly business report 203 is a weekly report on the project performance, and checks the progress against the plan and the solution for the problem.

FIG. 5 is a detailed configuration diagram of the training and change management 154 shown in FIG. 3, wherein the training and change management 154 includes the training status 301, the change request 302, and the change request result notification 303. It is composed.

The training status 301 summarizes the training status for skills acquisition or related training that may be helpful in project execution.

The change request 302 proceeds from the initial phase of development through the operational support phase of the system throughout the project. At this time, the change request should be executed after approval of the change of the relevant manager and guarantee the change status of the changes.

The change request result notification 303 is an approval process of the corresponding manager for the change request document presented for each task and guarantees the change state of the changes.

FIG. 6 is a detailed configuration diagram of the project management 153 shown in FIG. 3, wherein the project management 153 includes a project check 401, a check and benchmark 402, a check 403 at an analysis step, and a design step. Checks 404, checks at the development stage 405, and checks at the testing stage 406.

The project check 401 evaluates whether the project can be carried out smoothly, the check and benchmarking 402 performs the maintenance of the analysis data for the advanced products for the system of the field, the check in the analysis step 403 checks the current task and the requirements of the development system accordingly, and checks at the design stage 404 model the functions of the development system. And checking the accuracy evaluation and the output, the check in the development stage 405 performs the evaluation of the implementation and conversion of the execution history of the modules defined in the system design stage into the program, 406 implements each program, then implements and integrates all of the evaluation programs in each independent state. It is carried out.

7 is a detailed configuration diagram of the quality management 155 illustrated in FIG. 3, wherein the quality management 155 includes a quality review organization 501, a quality review meeting 502, a quality review minutes 503, and a quality review. And a checklist 504 and a quality review request result 505.

The quality review organization 155 is an organization chart for managing whether or not project development outputs of each stage comply with the development procedure specified in the contract requirements and the project quality management plan.

Conducting the quality review meeting (502) manages the entire project by preparing a plan for conducting a quality review meeting for each stage in advance for schedule management, project management, and output management at each stage before the project is started. Is written to. At this time, the quality review meeting may be conducted by a plan, and may be made available from time to time if necessary.

The quality review minutes 503 creates a meeting content for the quality review meeting to ensure the content of the meeting.

The quality review checklist 504 prepares the main check items to confirm whether the issues determined at the quality review meeting are properly reflected.

The quality correction request result 505 executes a quality review meeting to prepare a correction request detail and notify the department in charge. The department in charge will take corrective action on the corrective action and provide the quality control team with the corrective action. The quality control team checks that corrective actions have been taken and, if required, terminates the request for correction and, if not, makes a correction request until corrective action is taken. In addition, to maintain the quality level and to assure quality, prepare a result report of quality correction.

In addition, the system development procedure area 101 is divided into requirements definition 102, requirements specification 103, analysis 104, design 105, implementation 106, and test 107, which are described in detail. Is as follows.

FIG. 8 is a detailed configuration diagram of the requirements definition 102 shown in FIG. 3, wherein the requirements definition 102 includes a development summary 601, a development schedule 602, a participant work division 603, and a target company. The analysis schedule 604, the target company organization chart 605, the target company process flow chart definition 606, and the target company business flow chart definition 607.

The development summary 601 describes the purpose and necessity of the research and development task to be performed, and is briefly described about the implementation plan, and is performed for the purpose of grasping the overall contents of the research task.

The development schedule 602 is intended to determine the performance compared to the plan by creating the entire project schedule centered on the main activities.

The participant work division of duties 603 is to grasp the role and division of duties of members participating in the project to efficiently manage.

The target company analysis schedule 604 prepares a business analysis schedule and analysis content of a target company to which the enterprise resource management system is to be applied in a narrative form and in a modified form.

The target company organization chart 605 is an act of creating a target company organization chart in order to grasp the organization structure of the target application company.

The target company process flow chart definition 606 is created to identify the process flow related to the production of the product of the target applying company and to know the process of manufacturing and producing the product.

The target company business flow definition 607 is created to grasp the business processing procedure and payment line of the target applied company.

FIG. 9 is a detailed schematic diagram of the requirement specification 103 shown in FIG. 3. The requirement specification 103 includes a system overview 701, a system function classification 702, a system function 703, and other requirements. 704, Difference Analysis 705, Process Hierachy Diagram 706, Process Thread Diagram 707, Use Case List 708, Use Case Specification 1 709 And use case specification 2 (710).

The system overview 701 aims to grasp the overall contents of the system by briefly describing the meaning, purpose, scope of the system, and introduction effects when applying the company.

The system function classification 702 is created to distinguish whether a function of a system is directly processed by a user, processed in an system, or processed as an option item, and used as a classification method for a function in a system function.

The system function 703 divides a task into minimum units so as not to overlap with other functions and makes each function a single object.

The other requirements 704 describe additional requirements or prerequisites with respect to the system.

The difference analysis document 705 defines the function of the system and then describes in detail the difference in analyzing the business process of the target application company.

The process hierarchy diagram 706 is intended to describe a process hierachy diagram (PHD), and the PHD list includes a PHD file name, a PHD name, a PHD level, and a remark.

The process thread diagram 707 is for describing a process thread diagram (PTD), and the PTD list includes a PTD file name, a PTD name, and a remark.

The use case list 708 is intended to describe and manage use cases existing for each subsystem.

The use case specification 1 709 is composed of actors, purposes, outlines, types, and reference functions related to the use case, describes the purpose and behavior of the use case, and then serves as a guide for creating a procedure diagram.

The use case specification 2 710 sequentially describes the process of processing the interaction between the actor and the use case in a step prior to preparing the procedure diagram, and serves as a guide for creating the procedure diagram.

FIG. 10 is a detailed schematic diagram of the analysis step 104 shown in FIG. 3, which is composed of an object and attribute list 801, a conceptual model 802, and an interface specification 803.

The object and attribute list 801 performs a supplementary work while repeatedly performing a task, and simultaneously creates a conceptual model. At this time, iterative task number enables mutual verification of object and attribute list and conceptual model.

The conceptual model 802 uses a conceptual model to express a relationship between a class and a class, and has an object of creating an overall conceptual model rather than a unit task.

The interface specification 803 is composed of an item, an outline, parameters, processing contents, a reference task, and the like, and has an object of schematically describing the contents of each interface.

11 is a detailed configuration diagram of the design specification 105 shown in FIG. 3, wherein the design specification 105 includes a class list 901, a class specification 902, a sequence diagram 903, and a state diagram ( 904, Collaboration Diagram 905, Interface Class Diagram 906, Deployment Diagram 907, Deployment Diagram, Interface Class Diagram Specification 908, Input / Output Form List 909 Form List), form cover / design sheet (910, Lag Cover / Design Sheet), code design book (911), detailed code design (912) and message list (913).

The class list 901 is composed of a class ID (ID), a name, and a remark, and its purpose is to describe a class diagram.

The class specification 902 describes an attribute, a type, a length, and an attribute content of an attribute in the class diagram to manage the contents of the class diagram.

The procedure diagram 903 consists of an SD ID, a name, and a remark, and shows a dynamic cooperation among several objects. An important feature of the diagram is that it shows the order in which messages are sent between objects.

The state diagram 904 typically serves to complement the description of the class. At the time of writing, all possible states that an object of a class can have are created.

The collaboration diagram 905 shows a dynamic cooperation situation, and further shows a change in the message. When writing, you set up objects and their relationships.

The interface class diagram 906 consists of the ID, name, and remarks of the interface class diagram.

The layout diagram 907 shows the physical structure of the hardware and software of the system and creates the actual computer and device (node).

In the interface class diagram specification 908, when an actor performs a task on the screen, the input data is displayed as an item and the button click is displayed as an operation. The interface class diagram is a diagram of the behavior required to control these screens. It is the basis for writing real programs.

The input / output form list 909 includes a form name, ID, and remarks. Its purpose is to describe an input / output form.

The form cover / design design book 910 is designed to design a screen based on an interface class diagram, attach the designed screen to a form, and use it to consider the screen interface and to be useful for creating an actual program.

The code design book 911 has an object of facilitating management of data by creating a scheme and a grant rule for codeable data used in an entire system.

The detailed code design 912 is written to improve the efficiency of program implementation and processing by describing and managing data on a code system.

The message list 913 is prepared in order to improve work efficiency by writing an error message or recommendation in advance when a developer develops a program or a user uses the system.

12 is a detailed schematic diagram of the implementation step 106 shown in FIG. 3, wherein the implementation step 106 includes a method list 1001, a method specification 1002, a table list 1003, and a table layout plan 1004. , A view table list 1005, a program list 1006, and a program coverr 1007.

The method list 1001 is composed of an object name and a remark, and its purpose is to describe the object.

The method specification 1002 is written to make details of objects in a class and to modify only those objects when the business process logic is changed afterwards.

The table list 1003 is composed of a table ID, a name, and a remark, and its purpose is to describe and manage the table.

The table layout book 1004 has an object of describing and managing an item ID, an item name, a data type, a data length, a data key, and the like.

The view table list 1005 is composed of a view table ID and contents, and has a purpose to describe and manage the view table.

The program list 1006 is composed of a program ID, a name, and a remark, and its purpose is to describe and manage the program.

The program coverr 1007 sequentially describes a process of processing data internally when a user inputs data or generates an event during system operation, and outputs the processed data on a screen. Write so that users can perform their tasks efficiently.

FIG. 13 is a detailed configuration diagram of the test step 107 shown in FIG. 3, wherein the test step 107 includes a test plan 1101, a unit test 1102, an integration test 1103, and an integration test. It consists of test results 1104.

The test plan 1101 is a check on the whole process of user requirements, design and implementation, and is written to test a systematic software system.

The unit test 1102 is written in advance to test the program each time the program is completed.

The integration test 1103 is performed when the entire system development is completed and the unit test 1102 is completed.

The test result 1104 is to test the software quality, record the result, determine the date of modification for rejected matters, and follow-up management of the modified matters.

As described in detail above, if the present invention is inadequate during one development cycle, a new development cycle is started to define the functionality of the system, and if designed, the complexity of the software is achieved by completing the necessary implementation and upgrading the system continuously. This can be solved by dividing by period.

The technical spirit of the present invention has been described above with reference to the accompanying drawings, but this is by way of example only and not by way of limitation to the present invention. In addition, it is obvious that any person having ordinary skill in the art may make various modifications and applications without departing from the scope of the technical idea of the present invention.

Claims (13)

A test selector configured to receive operation requirement definition data, analysis data, and design data to be tested, and perform a consistency test to select a desired method, parameter, and property; A simulator configured to perform a simulation on data integrity based on the result selected by the test selector; A non-matching part deriving unit for deriving a non-matching part based on the rules of the data names to be calculated and the mutual correlation; A corrector for correcting the mismatched parts derived from the mismatched part deriving unit; A database storage unit for storing the data modified by the correction unit in itself; A project control management unit which receives the modified data from the database storage unit and performs schedule planning, quality management, and project management and education management; And, And an implementation progress unit which processes data according to the event when a user generates a specific event by receiving data stored in the database storage unit, a process execution result of the project control management unit, and new data. Enterprise resource management project development system. delete delete A first step of selecting a method, a parameter, and an attribute desired by a user by performing a consistency test by receiving operation requirement definition data, analysis data, and design data to be tested; A second step of performing a simulation on data consistency based on the result selected in the first step; A third step of deriving an inconsistent portion based on the rules of data names to be calculated and the correlations between them; A fourth step of correcting the mismatched parts derived in the third step; A fifth step of storing the data modified in the fourth step in a database storage; A sixth step of receiving the modified data from the fifth step and performing schedule planning, quality control, project management, and education management in a project control management unit; And, And a seventh step of processing data according to the event when a user generates a specific event by receiving data stored in the database storage unit, a process execution result of the project control management unit, and new data. To develop a global enterprise resource management project. delete delete The method of claim 2, The first step is, An object-oriented enterprise resource management project development method comprising creating an organization chart, a task flow chart, and a process flow chart by referring to a task analysis schedule and contents of an object to which an enterprise resource management system is to be applied, and designating it as the operation requirement definition data. The method of claim 2, The first step is, A method of developing an object-oriented enterprise resource management project, comprising: creating a conceptual model according to a list of objects and attributes to be analyzed and designating the conceptual model as the analysis data. The method of claim 2, The first step is, A method of developing an object-oriented enterprise resource management project, which comprises creating a class list and a procedure diagram of an object to be designed, creating a scheme and a grant rule for data that can be coded, and designating it as design data. The method of claim 2, In the sixth step of schedule planning, an object-oriented enterprise resource management project development method characterized in that after checking the progress of the performance compared to the plan when the project is executed, the solution is solved monthly and weekly. The method of claim 2, In the sixth step of quality management, if the project development outputs of each stage do not comply with the development procedure, the method for outputting the object-oriented enterprise-wide resource management project comprises performing a predetermined corrective process and outputting it. The method of claim 2, The project management of the sixth step is an object-oriented enterprise resource management project development method characterized in that the analysis of the requirements of the development system, modeling it, to evaluate the accuracy and confirm the output, and then convert it to a program for testing. delete