KR102130774B1 - Internal property based software asset architecture creation system - Google Patents

Abstract

The present invention relates to an IP-based software asset architecture generation system that enables to automatically draw and visualize and express an architecture through each layer of software to be developed and modules corresponding to the layer.

Description

IP-based software asset architecture creation system {Internal property based software asset architecture creation system}

The present invention relates to an architecture creation system, and more particularly, to an IP-based software asset architecture generation system that enables to automatically draw and visualize and express an architecture through each layer of a software to be developed and a module corresponding to the layer.

Architecture is a structure or structure of a system that expresses the relationship between the components and the components of the software components and the elements that are exposed to the outside, and the properties and connections of each element when developing various electronic devices equipped with hardware and software The necessary information for information exchange between relationships and elements is functionally illustrated.

When designing such an architecture, modeling the architecture configuration using existing architecture configuration references and performing analysis on the modeled architecture verification and design are generally conducted based on the designer's individual skills and experience to diversify the experience. , The quality of the architecture, which is the design output, varies depending on the depth of the related work knowledge and individual inclination.

In particular, when constructing an architecture using modeling tools, such as PowerPoint or Excel, when constructing an architecture, there is no problem in a simple architecture with a small number of components, but there are no significant problems, but the association between components in a complex and diverse information device environment There have been many problems in modeling the properties of relationships and components.

In addition, the existing software architecture creation tools are limited in their functions, and many different tools are used to create the architecture according to distributed work through various teams and subcontractors, and they are not compatible with each other. The architecture drawings, internal Layer, SubSystem, and Module information were written separately, and there were many difficulties in the continuous modification and improvement of the architecture.

In addition, in the process of using the existing architecture configuration reference, even when trying to refer to the best practices, it is not integrated and stored, and its form cannot be used in various ways, and it is difficult to extract and analyze information related to architecture.

Development of a dedicated tool has been attempted to solve this problem, but due to the invisible nature of the software, the tool for drawing the existing software architecture can express only the diagram of the software architecture and develop each module (IP: Internal Property). When developing IP units (features, schedules, resources, defects) for scope (internal IP and 3rd party IP) and development management (including outsourcing management), various tools are finally used for each purpose. There were difficulties in integrated project management such as management and defect tracking.

Publication Patent Publication No. 10-2009-0092203 (2009.08.31.)

The present invention was created to solve the above problems, and the object of the present invention is an IP-based software asset architecture that enables efficient architecture management by automatically visualizing the architecture configuration and the configured layers when developing software. It is to provide a generation system.

In particular, by supplementing the limited functions of the tools for creating the existing architecture, this system can be used to create a complete architecture through a single tool, and the layers, subsystems, and module information created in the architecture can be saved to create other project architectures. In order to provide a reusable IP-based software asset architecture creation system.

For the above-mentioned purposes, the present invention is an architecture creation system capable of creating and managing architecture through a central server and a client terminal that can access the central server through a network, the layer constituting the architecture located on the central server And a database in which subsystems and modules are stored for each project and layer; A project management unit that receives a project name and duration, and manages the number of layers, subsystems, modules, and resources added therein; It operates in the client terminal and provides an interface for creating a project architecture in connection with the database, but a layer management unit that provides a layer add function including a layer identification code and a name and description, and a lower layer corresponding to the layer identification code. A subsystem management unit providing a subsystem addition function including a sub-identification code and a name and description, and a module addition function including a sub-module identification code, name, description and IP characteristics and resources corresponding to the sub-identification code. An architecture creation unit including a module management unit including an interworking unit for storing the added layers, subsystems, and modules in the database in real time through respective layer identification codes, sub identification codes, and module identification codes; The resource includes a person in charge, a department, and a position, but a resource management unit that manages a module's modification, duration, and progress creation authority in response to each resource; It is characterized by consisting of.

At this time, the error management unit outputs the module status by dividing it into good, warning, and bad levels by reflecting the test results through the defect management system of the project; It is preferable to further include.

In addition, the IP characteristics are preferably divided into a new IP that is newly added, a reused IP that has been modified to an existing state, and a third-party IP that is performed through outsourcing.

Through the present invention, a process of creating an architecture required for a software development process is facilitated, and as the created architecture is stored as a single file, easy and convenient management is possible. Also, it is possible to modify the architecture with one tool while the project is in progress, and layers, subsystems, and modules of the current project can be reused in other projects.

In addition, when developing software, according to the characteristics of various business domains of each company, different units of architecture, module (IP) expression, and project and resource, defect management methods and tools are different, and systematic visualization of project management (Layered, Subsystem, IP, Features, Resources, Schedule) and defect traceability can be integrated and visualized.

1 is a conceptual diagram of the present invention,
Figure 2 is a block diagram showing the configuration and connection relationship according to an embodiment of the present invention,
3 is a configuration diagram of a database according to an embodiment of the present invention,
4, 5, and 6 are screens of an architecture generation system according to an embodiment of the present invention,
7 is a conceptual diagram showing the structure of the OSI 7 Layer and the TCP/IP 4 Layer.

Hereinafter, the configuration of the IP-based software asset architecture generation system of the present invention will be described in detail with reference to the accompanying drawings.

1 is a conceptual diagram of the present invention, Figure 2 is a block diagram showing the configuration and connection relationship according to an embodiment of the present invention, the present invention is basically a central server (1) for creating an IP-based software asset architecture, individual work, That is, it is composed of a client terminal and a network for the creation and management of the architecture, and each worker performs the main task through the client terminal 2, and the results of the operation are real-time in the database 11 provided in the central server. It is implemented in the form of saving as, and has a detailed configuration of the project management unit 21, the architecture creation unit 22, the resource management unit 23, and the error management unit 12 according to the function.

In the database 11 located in the central server 1, basically, layers, subsystems, and modules constituting the architecture are stored for each project and layer. In the present invention, the layer of the layer-subsystem-module order is provided under the software development design project, and the layers may be defined in various ways, but mainly the criteria for logical deployment and physical execution of software in the entire company can be defined. Can. The criteria for grouping software development and design tasks into layers include visual elements for users, specially designated application modules, common service levels, operating system interface levels, operating systems, and hardware. It is determined whether to combine to form a layer, and a role is assigned to each layer, and a sub-system is assigned to each layer.

A subsystem is a partial system that constitutes a lower layer of a layer, which is subdivided through lower modules, and manages the division of duties for each department, position, and person in charge.

7 is a conceptual diagram showing the structure of the OSI 7 Layer and the TCP/IP 4 Layer, and shows an example according to the standards of the layer and the lower layer.

As shown in FIG. 7, the 4th layer (Application) part of TCP/IP serves as the 5th to 7th layer of OSI 7th layer, and the 1st layer (Network Access) part of TCP/IP serves as the OSI 1st to 2nd layer. .

At this time, the difference between OSI 7 Layer and TCP/IP 4 Layer is that OSI 7 Layer is an internationally recognized standard, except that it is not a TCP/IP 4 Layer.

Although the current international standard is OSI, it actually uses a lot of TCP/IP standards. That is, both standards are used. Layers and sub-systems, etc. may be different depending on the classification by this standard. Therefore, there is no choice but to confuse each other in the development area if there is no clear visualization of the architecture during software development.

For example, the developer has only developed the contents of the Data-Link area according to the OSI standard, but in reality, if the project complies with the TCP/IP standard, the development of the physical area cannot be met.

In other cases, development was conducted in the area of Network Access in accordance with the TCP/IP standard, but it actually results in invading other development areas because it conforms to the OSI standard.

In order to prevent such problems, it is necessary to clearly separate development areas through visualization and avoid confusion.

The project management unit 21 receives the project name and period, which are a large unit of software development and design, so that it can start and manage architecture creation tasks according to the projector, but later layers and subsystems, modules, and modules created through architecture generation It manages the number of resources.

As described below, a project that has been opened includes a plurality of subsystems and multiple modules, including one or more layers, depending on its size, so that the overall status is visualized as an architecture, and the work organization is compared with resources allocated to each module. It makes it easy to grasp the progress of each detailed task module, the position of each worker in the entire task, and the size and the whole period.

The architecture creation unit 22 operates at each client terminal and basically provides an interface for project architecture creation in connection with the database 11, so that a person in charge of each department creates an architecture according to his/her department and his/her duties In order to support this, the detailed configuration of the layer management unit 221, the subsystem management unit 222, the module management unit 223, and the linkage unit 224 is provided.

The layer management unit 221 is a configuration for adding a layer required for a project or managing a generated layer, and provides a layer addition function including a layer identification code and a name and description, and may modify or delete the created layer. .

The subsystem management unit 222 is a configuration for adding a required subsystem to a selected layer or managing a generated subsystem, and adding a subsystem including a sub-identification code and a name and description corresponding to the layer identification code. It provides functions, and it is possible to modify and delete the created subsystem. At this time, the assigned sub-identification code is assigned to correspond to the upper layer identification code, so that even if multiple layers are inserted, the position and hierarchical relationship of the added subsystem are easily visualized.

The module management unit 223 is a configuration for adding a module required for a selected subsystem or managing a generated module, and includes a module identification code and a name, description, and IP characteristics and resources below the sub-identification code. It includes a module addition function, and you can also modify and delete the created module. At this time, the assigned module identification code is assigned to correspond to the upper subword identification code, so that even if there are multiple subsystems in the layer, the position and hierarchical relationship of the added module are easily visualized.

Since these modules become basic business units for the entire project, they include IP characteristics and resources, and in addition, the IP characteristics are newly added IP, reused IP modified in an existing state, and outsourced work. It is preferred to be divided into three-character IPs to be performed. In addition, the resource includes the person in charge, department, and job title. As such, as the IP characteristics and resources are assigned, the resource management unit manages the module modification and the period and progress creation authority in response to each resource, and the module by the person in charge. Make content management possible.

In addition, in the description of these modules, basically, the date of completion and progress of the work, and whether or not a defect has occurred are entered.

The interworking unit 224 is configured to store the added layers, subsystems, and modules in the database 11 in real time through respective layer identification codes, sub-identification codes, and module identification codes. Through this, architecture work through multiple client terminals is managed through a central server, so that not only architecture creation but also integrated management and job-specific defect tracking can be easily performed.

Normally, these projects are tested through a defect management system, so the error management unit 12 classifies the module status into good, warning, and bad levels by reflecting the results of the combined management system and progress against the overall process period. It is output, and preferably, it is intuitively displayed through the color of each object as shown in FIGS. 4 to 6.

3 is a configuration diagram of a database according to an embodiment of the present invention, expressing the logical configuration of the database 11 as information engineering (IE), contents of a project, resources allocated to the project, and registered layers, It is composed of modules of each layer.

Basically, the main process of the IP-based software asset architecture creation system is to sequentially allocate layers, modules, and resources to the project when the user creates a new project on the client. In addition, while the project is in progress, it is continuously managed and the overall management of the project is performed. Upon completion of the project, the process is terminated.

4, 5, and 6 are screens of an architecture generation system according to an embodiment of the present invention, and FIG. 4 shows a main screen of an IP-based software asset architecture generation system.

By creating a new project, adding layers, subsystems, and modules, and visualizing the added contents, the hierarchy menu of the entire project on the left is expressed in the order of Project> Layer> SubSystem> Module, and in the case of Module without SubSystem It is allocated under (EmptySub).

5 is a module detail screen that appears when one of the modules added by the user is selected, the name of the module and the current state (good, warning, defect) and classification (New IP, Reuse IP, 3rd Party IP), assigned You can check resources, progress, detailed module description, development deadline, key features, and defect list.

6 is a screen for checking the Feature List and the Defect List, respectively, on the detailed screen, and it is possible to check all of the features and defects of the corresponding module.

Although the present invention has been described with reference to the accompanying drawings and preferred embodiments, it is apparent that those skilled in the art can make various modifications without departing from the scope of the present invention. Accordingly, the scope of the invention should be construed by the claims set forth to cover these many variations.

1: Central server 11: Database
2: Client terminal 21: Project management department
22: Architecture creation unit 221: Layer management unit
222: subsystem management unit 223: module management unit
224: linkage 23: resource management
12: Error management department

Claims (3)

An architecture creation system capable of creating and managing an architecture through a central server (1) and a client terminal (2) connectable to the central server (1) via a network,
A database 11 located in the central server 1 and storing layers, subsystems, and modules constituting an architecture for each project and layer;
A project management unit 21 that receives a project name and duration, and manages the number of layers, subsystems, modules, and resources added therein;
A layer management unit 221 that operates on the client terminal 2 and provides an interface for creating a project architecture in connection with the database 11, but provides a layer addition function including a layer identification code and a name and description, The subsystem management unit 222 provides a subsystem addition function including a sub-identification code and a name and a description corresponding to the layer identification code, and a module identification code and a name and description of the module corresponding to the sub-identification code. The module management unit 223 including a module add function including IP characteristics and resources, and the added layer, subsystem, and module in real time through the layer identification code, sub identification code, and module identification code. An architecture creation unit 22 having a linkage unit 224 to store in 11);
The resource includes a person in charge, a department, and a position, but a resource management unit 23 that manages module modification, duration, and progress creation authority in response to each resource; And
An error management unit (12) that outputs in different colors by classifying the status of each module into good, warning, and bad levels by reflecting the test results through the project's defect management system and progress against the entire process period of the project; Including,
The characteristics of the IP are divided into a new IP that is newly added, a reused IP that has been modified to an existing state, and a 3-character IP that is performed through outsourcing,
The central server,
While providing the visualization of the architecture structure in the order of layers, subsystems, and modules stored for each project by the interlocking unit, compare resources, IP characteristics, and module status assigned to each module, and compare the work organization, work scale, and overall period. An IP-based software asset architecture creation system characterized by managing and providing the progress of each module assigned to a detailed task, a person in charge of each module, and the module status. delete delete

Images