KR20110138885A - Integrated management system and method for software development - Google Patents

Abstract

PURPOSE: An integration management tool for developing software and method thereof are provided to enable developers to effectively manage development by providing information about the state and development progress to the developers. CONSTITUTION: A user interface unit(110) receives a management request from a user terminal. A control unit(120) manages the document categories by creating structure information which indicates a correlation between document categories and the content. A storage unit(130) stores the content and the structure information and software development stages.

Description

Integrated management tools and methods for software development {INTEGRATED MANAGEMENT SYSTEM AND METHOD FOR SOFTWARE DEVELOPMENT}

It is related to systems and methods that support integrated management of document for development and source code for software development, and more specifically, history management according to the software development flow (configuration management: software configuration manager). A system and method for providing SCM).

The software integrated development tool provides progress and history information about the code related to the development during the development of the software in which a large number of members, such as a manager, a request proposer, a designer, and a developer, participate.

Therefore, the web-based integrated software development tool saves cost and time in software development.

In software development, documents for software development have a mutually organic relationship that cannot be managed independently from the source code. Thus, the ability to establish and manage these organic relationships should be provided. Thus, in addition to the source code that has been the subject of history management in conventional development, documents that correlate with the development or the source code also need to be integrated history management. For example, a request for proposal (RFP), a software requirement specification (SRS), a detailed software requirement specification (DSRS), a software design specification (SDS), an interface Document information of the type of software development stage may be provided, including;

The above documents are horizontally related in the order of listing, and have different components for each type of step.

The above documents are divided into detailed document items, and each of these document items needs to be managed separately.

In addition, if there is a correlation between document items of both documents belonging to different types of software development stages, the software configuration management system needs to provide a setting of such an association and a trace function according to the association. have.

According to one aspect of the present invention, a user interface for receiving a management request from a user's terminal, a plurality of types of software development steps to form a sequential relationship according to the received management request, each of the software development step types included in Generating structure information indicating a correlation between a plurality of document items, contents of the plurality of document items, and document items of a previous step type and document items of a next step type among the plurality of software development step types, A software configuration management system is provided that includes a control unit for controlling an item to be managed and a storage unit for storing the plurality of software development step types, the plurality of document items, the content, and the structure information.

The control unit may generate a step type document integrating contents of a plurality of document items included in one development step type into one, and the storage unit may store the generated step type document.

When access to the document item is detected from the terminal of the second user, the controller searches for the document item associated with the accessed item from the storage unit according to the structure information of the accessed document item, and the associated document item. Tracking information on the document item accessed by the terminal of the second user may be provided to the terminal of the third user accessing the terminal.

The storage unit may further store a template having a structured structure used in the plurality of development step types, and the user interface unit may receive the management request according to a form of the template.

According to another aspect of the invention, the step of receiving a management request from the user's terminal, generating a plurality of types of software development step to form a sequential relationship according to the management request, the respective software in accordance with the management request Generating a plurality of document items included in the type of development step, generating contents of the plurality of document items according to the management request, and items of the previous step type among the plurality of software development step types according to the management request And generating structure information indicative of associations between items of a later step type.

Meanwhile, according to another aspect of the present invention, an input unit for receiving management request data from a user, a plurality of software development step types for forming a sequential relationship, and each of the software development step types Processing into a management request for generating structure information indicating an association between a plurality of document items, contents of the plurality of document items, and a plurality of document items of a previous step type or a document item of a next step type among the plurality of document development step types. A control unit and a communication unit for transmitting the management request to the configuration management system through a communication network is provided.

Provides configuration management for all development documents and source code used for software development.

Through the relationship according to the development stage of the software to provide all the information on the progress and status of the development of the software, and to facilitate the development.

1 is a configuration diagram of a software configuration management system and a terminal according to an embodiment of the present invention.
2 is a structural diagram of a data object for software configuration management according to an embodiment of the present invention.
3 is a structural diagram of a tree of a step type document according to an embodiment of the present invention.
4 is a structural diagram of a data object representing a document item according to an embodiment of the present invention.
5 shows a procedure of generating a step type document according to an embodiment of the present invention.
6 is a structural diagram of a data object representing structural information of an association according to an embodiment of the present invention.
7 is a flowchart illustrating a software configuration management method according to an embodiment of the present invention.
8 is a configuration diagram of a user terminal according to an embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited or limited by the embodiments. Like reference numerals in the drawings denote like elements.

1 is a configuration diagram of a software configuration management system and a user terminal according to an embodiment of the present invention.

The software shape management system 100 (hereinafter, abbreviated as system) includes a user interface unit (hereinafter, abbreviated as an interface unit), a controller 120 and a storage unit 130.

The user terminal 150 (hereinafter, abbreviated to terminal) is a device used by a user to access the system 100.

A user performs an input operation required for software configuration management through the terminal 150, and the terminal 150 generates a management request based on the input and transmits it to the system 100.

The management request is an integrated management request for documents and codes managed by the system 100 and includes a configuration management request.

The integrated management is management of document structure, association, and the like, and includes shape management.

The terminal 150 may be connected to the system 100 through a communication network as shown, or may be locally connected to the system 100.

Alternatively, the terminal 150 may be the same hardware as the system 100. In this case, the terminal 150 may refer to a program, a thread, or a module operating in the hardware.

A plurality of terminals 150 may be connected to the system 100.

The terminal 150 may be a dedicated device for working with the system 100, may include a dedicated program mounted on a general purpose device, or a general program such as a web browser. It could be using (program). When the terminal 150 uses a general-purpose program, the terminal 150 may receive data necessary for operating as a terminal of the configuration management system from the system 100.

The communication network includes a wired or wireless communication network. The terminal 150 and the system 100 may communicate with each other based on wired / wireless communication protocols of various layers such as TCP / IP, HTTP, and CDMA.

The interface unit 110 provides interface data for accessing the system to the terminal 150 and receives a request for software configuration management from the terminal 150. In addition, the interface unit 110 receives the interface data from the control unit 120 and transmits the request to the control unit 120.

The controller 120 receives a management request from the interface unit 110 and performs a task required to process the request. In addition, the controller 120 transmits the interface data and data necessary for interaction with other users to the interface unit 110 or receives from the interface unit 110.

The control unit 120 writes data necessary for the processing to the storage unit 130 or reads from the storage unit 130.

The storage unit 130 stores the data transmitted by the control unit 120 and transmits the stored data to the control unit 120 at the request of the control unit 120.

The storage unit 130 may physically store data in the system 100. In this case, the storage unit 130 may be a file system or a database including a storage medium such as a random access memory and a hard disk.

In addition, the storage unit 130 may be an input / output interface for storing data in another external storage server or a database. In this case, the storage unit and the server (or the database) are connected to each other through a communication network.

2 is a structural diagram of a data object for software configuration management according to an embodiment of the present invention.

The system 100 includes a plurality of software development step types (abbreviated as step types hereinafter), such as the first step type 210, the second step type 230, the third step type 250 and the fourth step. Provide type 270.

The type of step of the system 100 may be a series of development steps that a relevant person, such as a developer, needs to work in during a software development process. The plurality of step types have a temporal or logical back and forth relationship with each other.

However, the temporal or logical back and forth relationship does not necessarily mean that work on the post step type should be performed after completion of the work on the previous step type.

For example, a request for proposal (RFP), a system requirement specification (SRS), a detailed SRS, a software design specification (SDS), an interface, and code The plurality of step types may be configured.

Exemplary step types described above are described in Table 1 below.

Step type Explanation Request for Proposal (RFP) Provide the software requirements to be developed. Requirements Specification (SRS) A complete description of the behavior of the software to be developed.
That is, it defines the requirements that the software must meet. Detailed Requirements
(detailed SRS) The requirements are further refined. Software design
(SDS) The requirements and detailed requirements define algorithms, detailed logic, data operations, etc., to be performed as software. Interface Defines an interface for accessing code. Code Define the code of the software.

The system 100 may provide a plurality of sets of step types. Each set of step types includes a plurality of step types, and each set of step types is managed or controlled independently of each other. Each set of step types provided by the system 100 is referred to as a project 200.

The project 200 may include related information about the project itself, such as a project name, a project period, an annotation, and user authority information.

The step types 210, 230, 250, and 270 have step type documents 212, 232, 252, and 262, respectively.

A step type document is a document used by each person in each step type.

For example, step type documents for exemplary step types in the software development described above are described in Table 2 below.

Step type Step type document Request for Proposal (RFP) Proposal request Requirements Specification (SRS) Requirements Specification Detailed SRS Detailed Requirements Software Design (SDS) Software design Interface Interface specification of the software Code Full code of software

The step type document may be text composed of alpha-numeric characters. For example, if the step type is a code, the code step type document for the code step type may be a document in plain text format.

In addition, the step type document may be a rich text format such as a font, a rich text format, an HTML document, an XML document, or the like.

In addition, the step type document may include multimedia objects such as images, motion pictures, voices, sounds, flashes, and links as components. And may include program code to be provided to users such as C, C ++, and JAVA.

The step type includes a plurality of document items for constructing a step type document.

The format of the document item included in the same step type may be determined by the format of the step type document.

For example, if the step type document is a general document such as a proposal request, the document item of the proposal request may be a specific chapter or section of the proposal request. If the step type document is an interface specification, the document item of the interface specification may be an interface definition file in a specific unit. In addition, if the step type document is a code, the document item of the code may be computer program code in a specific unit.

If the step type document is an interface specification, the document item of the interface specification includes an interface or declaration, such as a specific variable, constant, function, structure, or class. It can contain interfaces or declarations based on code files. In addition, if the step type document is a code, the document item of the proposal request may include a definition of a specific variable, constant, function, structure or class, etc., and may include a code file.

A plurality of document items in a step type document may have a hierarchical structure such as a tree.

3 is a structural diagram of a tree constituted by the first step type document according to an embodiment of the present invention.

For example, when the first step type document 212 is a general document such as a request for proposal, the document item 1 214 representing the first chapter includes the document item 1-1 216 and the first document representing the first chapter. It can have document items 1-2 (218) representing Chapter 1, Section 2 as child document items.

Further, document item 1 214 representing the first chapter and document item 2 220 representing the second chapter are siblings to each other.

In this case, the first step type document 212 is the root of a tree consisting of the document items 214, 216, 218 and 220 that will make up the first step type document 212. can see. In addition, the document items 214, 216, 218 and 220 constitute a node of the tree.

The document item includes content that is the content of the document item.

For example, when the document item is a document item of a general document such as a proposal request, the content of the document item may be content of a specific chapter or section of the proposal request. If a document item is an item in an interface specification, the content of the document item may be an interface or declaration, such as a specific variable, constant, function, structure, or class. It may be an interface or declaration based on a code file.

One document item may include a plurality of contents which are distinguished by a title of the document item, a body of the document item, and the like.

The content may be text composed of alpha-numeric characters. In addition, the content may be a rich text format (HTML), an XML document, or a PDF format document supported by formatting such as a font, and may include multimedia objects such as images, videos, voices, sounds, and links. can do.

The contents of a plurality of document items included in one step type are combined to form a step type document. For example, a first step type document 212 may include document item 1 214, document item 1-1 216, document item 1-2 218, and document item 2 220, in which the content of document item 212 is determined. , 214, 216, and 218).

Document items belonging to different step types may be correlated.

The association may be a dependency between document items.

For example, if one document item of the requirement step type is changed, the document item of the detailed requirement step type corresponding to the document item needs to be changed accordingly. Or if one document item of the code step type, ie the code, is changed, the interface of the code, ie the corresponding document item of the interface step type, needs to be changed accordingly.

In other words, when access to one document item can have some effect on other document items of the type before or after the document type to which the document item belongs, an association relationship between both step types can be established.

In this case, the document item of the previous step type is called a source item, and the document item of the next step type is called a target item.

The first link 212 of FIG. 2 is structure information indicating an association between document items 1-1 216 of the first step type 210 and document item 1 234 of the second step type 230.

The structural information of the association stores information about the association, for example, identification information of both document items forming the association.

A document item belonging to the second step type may have an association relationship with a document item of a first step type that is a previous step type, and may be associated with a document item of a third step type that is a next step type. In this case, an indirect association is also established between the document item of the first step type and the document item of the third step type.

One document item may be associated with a plurality of prestep type document items and may be associated with a plurality of post step type document items. An n: m association between a plurality of document items may be established.

For example, document item 3-1 254 of third step type 250 is a document item for an interface of a specific function, and document item 3-1 274 of fourth step type 270, document item 3- If two (276) and document items 3-3 (278) are the code of the function or the code of a function that calls the function, respectively, then the document item 3- of the interface, that is, the third step type 250, If 1 254 is changed, document item 3-1 274, document item 3-2 276, and document item 3-3 278 of the fourth step type 270 may be affected.

Thus, document item 3-1 254 of the third step type 250 is document item 3-1 274, document item 3-2 276, and document item 3 of the fourth step type 270. Each has an association with -3 (278).

In addition, document items 3-1 254 and document items 3-2 256 of the third step type 250 are document items for the interface of a specific function, respectively, and document items 3-1 of the fourth step type 250 274 is the code of a function that calls the functions, if the interface, i.e., document item 3-1 254 or document item 3-2 (256) of the third step type 250 is changed, the fourth Document item 3-1 274 of step type 270 may be affected.

If an association between the step types is established, the system 100 provides the first user with a second user accessing a second document item associated with the first document item when the first document item is accessed by a first user. It can provide a trace of the access of a document item.

The tracking may include information such as the content before and after the change of the document item and the contents of the document item, the reason for the change, the person who performed the change, whether or not the tracking is confirmed, and the date and time of the change.

The tracking can be configured as a plurality of steps. For example, the system 100 may determine that document item 2 220 of the first step type 210 has been accessed when document item 2 220 of the second step type 230 is associated with document item 2 220. 236 may be provided to the user accessing the document item 3-1 (256) or document item 3-2 (256) of the third step type 250 associated with the document item 3 (236). You can also provide tracking to accessing users.

The tracking enables forward tracking from the previous step type to the next step type and backward tracking from the post step type to the previous step type.

The system 100 provides tracking for all step type documents, for example via an association from requirements to source code.

Therefore, the system 100 facilitates management such as verification of the software by providing information on the development progress and status of the software to development personnel, and supports the synchronization of software-related documents and codes in the development of cooperation among several people. do.

In addition, the system 100 may provide the user with the association visually, and may provide a link for the user to perform a task according to the association.

If document types are added in a project that has already been created, the handling of associations becomes an issue.

If the document type to be added is the first one or the last one, the document type can be simply added to the project just by creating it in the project.

On the other hand, if the added document type is between two existing document types, and there is an association relationship between the two existing document types, processing of the association relationship is problematic.

As a processing method, it is possible to delete the association first, and then reestablish a new association that reflects the addition of a new document type by the user. It also copies document items of the previous or subsequent document type to the inserted document type, and automatically creates a new association corresponding to the existing association between the copied document item and the previous document type and the subsequent document type. How is it possible?

The content of the document item and the structure information of the association relationship in which the document item is associated may be separated and controlled independently and stored.

That is, the system 100 can access and control the content of the document item without affecting the structural information associated with the document item, and the structure information related to the document item without affecting the content of the document item. Can be accessed and controlled.

The step type document may have a certain specification according to the step type and may have a formal structure. In the standardized structure, the configuration of the step type document may be divided and managed through a template. The body of the step type document may not be subject to the template.

The step type may have one or more templates, and the step type document may include the one or more templates in addition to the text.

The template may be configured to have basic document rules defined by an institution such as IEEE. For example, IEEE Standard 830-1998 defines the format of the requirements document.

A user of the system 100 may create, modify, and delete a template of a step type.

When the content of the document item is input through the terminal 150, the content of the document item or the step type document is provided through the display of the terminal 150 and the content of the document item or the step type document. The template may be used in the case of publication.

The above-described users have positions such as project manager, system administrator, approval manager, general user, etc. according to their respective roles. The system 100 may set management authority for a project, a step type, a step type document, a document item, and an association relationship of the system 100 for each user or each user's position.

The management includes create, delete, modify, copy, cut, paste, and access control of the object. Jobs, print jobs, save jobs, and load jobs.

In addition, the authority may be set separately for each project, step type, step type document, document item or association relationship.

The user interface 110 receives a management request from the terminal 150. The management request includes management requests for user accounts, user rights, projects, step types, step type documents, document items, and associations.

The control unit 120 manages and controls the above-described project, step type, step type document, document item, and related relationship according to the management request.

The controller 120 may determine whether to approve the management request according to the authority granted to the user. When the information on the authority is transmitted to the terminal 150 of the user, the authority approval may also be made in the terminal 150 of the user.

The control unit 120 stores the data necessary for the management in the storage unit 130 and performs input / output operations of the data to the storage unit 130.

In addition, the control unit 120 provides the management result to the user interface unit 110, and the user interface unit 110 transmits the result to the user terminal 150.

The storage unit 130 stores data on the above-described project, step type, step type document, document item, association relationship, user information, user authority information, and the like.

4 is a structural diagram of a data object representing a document item according to an embodiment of the present invention.

The document item 400 includes an identifier (ID) 410, a parent ID 420, a sibling ID 430, a child ID 440, a content 470, authority information 470, and access to a document item. Information 480 and other information 490.

The content 470 includes a title 452 and a body 454. The content may further include a multimedia object.

The identifier uniquely identifies the document item within the system 100, the project 200, or the development stage type.

The parent ID 420 points to the parent node of the document item 400, i.e., the parent document item, in a tree composed of document items in the aforementioned step types. That is, the value of the parent ID 420 is the ID of the parent document item.

In the case of the highest level document item, the parent ID 420 may have a null value or an ID value of the step type.

The sibling ID 430 points to the right sibling of the document item 400 in the tree. If there is no sibling of the document item 400 or if the document 400 item is the rightmost sibling, the value of the sibling ID 430 may be a null value.

The child ID 440 indicates the leftmost child of the document item 400 in the tree. If the document item 400 has no children, the value of the child ID 440 may be a null value.

The content 450 includes data or multimedia objects that make up the content 450.

The title 452 is a title of the content 450 and may be a title of each chapter, a title of each section, an interface name or a code name in the document.

The body 454 is a body of the content 450 and may be a body of each chapter, a body of each section, an interface body or a code body of the document.

The multimedia object (not shown) is an object such as an image, a video, a voice, a sound, a flash, and a link included in the content.

The authority information 470 stores data for determining an access authority for the document item. For example, the data may be configured in the form of a list of accessible users, a method for determining access permission, an access control field for each user, and the like.

The access information 480 stores an access history for the document item. For example, the access user, the type of access, the reason for the access, the change before and after the access, the access time, the number of accesses, and the like may be contents of the history.

The authority information 470 and the access information 480 may not be stored for each document item 400. For example, all authority information or access information on the system 100 or the project 200 may be stored in one table or database. In this case, each entry in the table or database may include an identifier for identifying the project, the step type item and the document item.

5 illustrates a step type document generation procedure according to an embodiment of the present invention.

Document items having the structure as shown in FIG. 4 are used to generate the step type document. As mentioned above, the document items form a tree structure.

In the above procedure, the node that is the target of the current processing, that is, the document item, is called the current node.

First, the root of the tree is set to the current node (S510). Here, the root is a node having the highest leftmost document item among the document items as a child. The root node may be the step type or may be an additional document item data structure set up to be a root within the step type.

Next, it is checked whether there is a child node of the current node (S520). If there is a child node, the child node is processed first.

If the current node has a child node, it is checked whether there is a sibling node of the current node (S530).

If there is a sibling node, the shape nodes are pushed to the stack (S532) to be processed after processing of the child node (S532) and the next step 534 proceeds. If there is no sibling node, the next step 534 proceeds immediately.

Next, the child node is appended to the step type document being created (S534).

That is, the child node, that is, the content of the document item is added to the end of the content of the step type document being generated.

Next, the child node is set as the current node (S536), and processing of the new current node (S520) is performed.

If the current node has no child node, it is checked whether there is a sibling node of the current node (S540).

If there is the sibling node, the sibling node is added to the step type document being created (S542).

Next, the sibling node is set as the current node (S536), and processing of the new current node (S520) is performed.

If the current node does not have a sibling node, it is checked whether there is a node stored in the stack (S550).

If there is a node stored in the stack, the node popped out of the stack is set as the current node (S552), and the processing step (S520) of the new current node proceeds.

If no node is stored in the stack, the procedure ends because all nodes have been processed.

Through the above procedure, the contents of all the document items in the step type are traversal in a depth-first manner and added to the step type document in the order of the traversal.

6 is a structural diagram of a data object representing structural information of an association according to an embodiment of the present invention.

The structure information 600 includes information on both document items that are associated with each other. The information includes an ID 610 of the step type to which the previous document item belongs, an ID 612 of the previous document item, an ID 620 of the step type to which the next document item belongs, and an ID 622 of the post step type. do.

In addition, the structure information 600 includes authority information 630 and access information 640 for the structure information 600 as described with reference to FIG. 5.

The structure information 600 includes tracking information 650 for providing a tracking function.

The tracking information 650 may include information on whether a user accessing a document item after the previous document item has been notified, or vice versa, a list of users to be tracked, and whether the user confirms tracking. , Tracking information provision period, and the like.

The authority information 630, the access information 640, and the tracking information 650 may not be stored for each of the structure information 600. For example, all authority information, access information, or tracking information on the system 100 or on the project 200 may be stored in one table or database. In this case, each entry of the table or database may include an identifier for identifying the project and the structure information.

As shown in FIGS. 4 and 5, the specific document item 400 and the structural information 600 of the association associated with the document item may be managed and stored independently of each other as separate data objects. Thus, it is possible for both the content 450 and the association of the document item 400 to be managed and controlled independently from each other.

7 is a flowchart illustrating a software configuration management method according to an embodiment of the present invention.

First, the project 200 is generated (S710).

As the project 200 is generated, a basic step type and a template of the step type may be generated.

In addition, other operations on the project 200 according to the above-described embodiment of the present invention may be performed in the step S710.

Next, the step type is generated (S720).

In addition, other operations for the step type according to the embodiment of the present invention described above may be performed in the step (S720).

When the step type is generated, the document item belonging to the step type, the association relation of the document item, and the template of the step type may be generated (S730, S740, and S750).

In addition, other operations on the document item, the association relationship of the document item, and the template of the step type according to the above-described embodiment of the present invention may be performed in the steps S730, S740, and S750.

When the creation of the document item and the association is completed, the step type document of the step type is generated (S760).

In addition, other operations on the step type document according to the above-described embodiment of the present invention may be performed in the step S760.

Next, the step type document is generated, and when the template is generated, the step type document is published (S770).

The above procedures S710 to S770 may be performed step by step according to a management request through the user terminal S150.

8 is a configuration diagram of a terminal according to an embodiment of the present invention.

The terminal 150 includes an input unit 810, a control unit 820, and a communication unit 830.

The input unit 150 receives management request data from a user.

The controller 820 processes the received management request data into a management request.

The management request is a request for managing and controlling structure information indicating the step type, the document item, the content of the document item, and the association.

The communication unit 830 transmits the management request to the system 100 through the communication network.

Interworking between the system 100 and a software test is possible.

When the user generates a test (test case, test procedure, test code, etc.) necessary for each document item, the test writing module associated with the document item may operate.

The system 100 may include a function of checking connectivity with a test, receiving a test result, and checking the result.

For example, the item may be visualized in green when the test on a specific document item is successful, and the item may be visualized in red when the test on a specific document item fails.

In addition, when an association is established between specific document items, such an association may also be applied to a test. That is, the test includes an acceptance test, a system test, an integration test, a component test, and a unit test, and the relationship between the tests is described above. There is a similar relationship to the association between the document items of the step type.

In addition, a test result for a specific document item may be provided to a user accessing a document item associated with the specific document item as part of the above-described tracking function.

According to this visualization, the user can immediately recognize the result of the test execution and can perform an operation on the document item according to the result.

Method according to an embodiment of the present invention is implemented in the form of program instructions that can be executed by various computer means may be recorded on a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. Program instructions recorded on the media may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks, such as floppy disks. Magneto-optical media, and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

As described above, the present invention has been described by way of limited embodiments and drawings, but the present invention is not limited to the above embodiments, and those skilled in the art to which the present invention pertains various modifications and variations from such descriptions. This is possible.

Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the claims below but also by the equivalents of the claims.

100: software configuration management system
110: user interface part
120: control unit
130: storage unit
150: user terminal

Claims (13)

A user interface unit for receiving a management request from a user terminal;
According to the received management request, a plurality of software development step types constituting a sequential relationship, a plurality of document items included in each of the software development step types, the contents of the plurality of document items and the plurality of software development steps A control unit for generating structure information indicating an association between a document item of a previous step type and a document item of a next step type among types, and controlling the document item to be managed; And
A storage unit for storing the plurality of software development step types, the plurality of document items, the contents, and the structure information
Including, the software configuration management system. The method of claim 1,
The control unit generates a step type document integrating contents of a plurality of document items included in one development step type into one;
And the storage unit stores the generated step type document. The method of claim 1,
When access to the document item is detected from the terminal of the second user, the controller searches for the document item associated with the accessed item from the storage unit according to the structure information of the accessed document item, and the associated document item. And providing tracking information on the document item accessed by the terminal of the second user to the terminal of the third user who accesses the terminal through the user interface unit. The method of claim 1,
The storage unit further stores a template having a structured structure used in the plurality of development stage types,
And the user interface unit receives the management request in accordance with the form of the template. The method of claim 1,
And the control unit controls the document item to be managed while the content and the structure information are separated from each other independently. The method of claim 1,
The pre-step type document item is associated with a plurality of post step type document items, and the post step type document item is associated with a plurality of pre step type document items. . The method of claim 1,
The software development step type may include at least one of a request for proposal, a requirement specification, a detailed requirement specification, a software design, an interface, and code.
Including, the software configuration management system. Receiving a management request from a user's terminal;
Generating a plurality of software development step types forming a sequential relationship according to the management request;
Generating a plurality of document items included in each type of software development step according to the management request;
Generating contents of the plurality of document items according to the management request; And
Generating structure information indicating an association relationship between an item of a previous step type and an item of a next step type among the plurality of software development step types according to the management request;
Comprising a software configuration management method. The method of claim 8,
A step of integrating the contents of a plurality of document items included in one of the development step types into one; generating a type document
The software configuration management method further comprising. The method of claim 8,
If access to the document item is detected from a terminal of a second user, retrieving a document item associated with the accessed item according to structure information of the accessed document item; And
Providing tracking information for the document item accessed by the terminal of the second user to the terminal of the third user accessing the associated document item;
The software configuration management method further comprising. The method of claim 8,
Providing a template having a structured structure used in a plurality of types of development steps to the user's terminal
Further comprising:
And wherein said management request is in the form of said template. A computer-readable recording medium containing a program for performing the software shape management method according to any one of claims 8 to 11. An input unit to receive management request data from a user;
A plurality of software development step types for sequential relationship of the received management request data, a plurality of document items included in each of the software development step types, contents of the plurality of document items, and the plurality of software development step types A control unit for processing into a management request for generating structure information indicating an association relationship between a document item of a previous step type or a document item of a next step type among the following; And
Communication unit for transmitting the management request to the configuration management system through a communication network
Including, the terminal.

Images