JP4439947B2 - Development process support apparatus, development process support method, and development process support program - Google Patents

Description

  The present invention relates to execution support for a development process that facilitates development and management processes mainly when developing software products and managing software development processes.

FIG. 17 shows the entire configuration of a conventional development process support system.
First of all, an “organizational development process engineer” H1, who is a user of this system, develops a development process metamodel 11 corresponding to SPEM that defines a metamodel of a development process approved by an industry organization OMG (Object Management Group), for example. The starting point of This development process metamodel 11 is a metamodel shown in FIG. 18 in which elements constituting the development process (for example, concepts such as “activity” and “deliverable” for developing software) are defined. Details described in detail can be obtained from Non-Patent Document 2 on the website of the organization.

  Now, the “development process engineer” H1 uses this development process metamodel 11 as a schema, for example, a development process definition called “Workbench” (registered trademark) of “RUP” of Non-Patent Document 1 shown in FIG. The unit 21 formally defines an object-oriented model, and generates a standard development process model 12 in an organization that performs software development. Referring to FIG. 19, “organizational development process engineer” H1 sequentially arranges elements constituting the development process on the right side of the screen and designs the development process model 12. In the example on the right side of FIG. 19, the UML activity diagram is used. The black circle is "Start", the next horizontal bar is "Branch", the pentagon below it is "Activity", and the horizontal bar below is "Join" Furthermore, the double black circle at the bottom represents “end”. The development process model defined by “organizational development process engineer” H1 (hereinafter abbreviated as standard development process model) needs to be commonly applicable to many software development projects implemented by the organization. General purpose and general.

  Next, the “project development process engineer” H2 edits the standard development process model using the development process definition unit 21 and stores it in the development process model 12 for the project. The development process content 13 illustrated in FIG. 20 is created using the unit 22. This is to read and understand a formal development process model 12 that can be interpreted by a computer, and to create development process content 13 that can be read, understood and practiced by humans from the contents. The unit 22 is another creation support tool indicated by “Publisher” (registered trademark) in Non-Patent Document 1, for example.

  In this way, the development process content 13 in the specific software development project is created. Since the standard development process model is generic and general as described above, the development process content defined by the “project development process engineer” H2 depends on the characteristics of each project (project size, type of software to be developed, etc.). Depending, it needs to be concrete and optimized.

While reading the development process content 13 for the project, the “project planner” H3 assigns the task schedule of the project and the resource (person in charge) of each task using the plan definition unit 23 and assigns a specific project plan 14. create.
The plan definition unit 23 is a tool for inputting and setting project plan tasks, resources, etc. in a table format or a graphical format on a computer screen, as shown in “Microsoft Project” (registered trademark) of Non-Patent Document 3, for example. FIG. 21 shows an example of the screen.

The “developer” H5 creates a development product by executing the defined activity using the development environment unit 26 while reading the development process content 13 for the project, and stores the product in the configuration management DB 16 To do.
The development environment unit 26 is a tool group that supports modeling of a development target in an upstream process of software development, and supports source code programming and debugging in a downstream process. For example, “Rational Rose” of Non-Patent Document 4 is used. (Registered trademark).
The configuration management DB 16 is a database for managing deliverables in software development. For example, the configuration management DB 16 is shown in the IMB product “Rational Clear Case” (registered trademark) of Non-Patent Document 5.

The “development manager” H4 manages the development progress by comparing the project plan 14 and the project performance 15 using the performance monitoring unit 24 while reading the development process content 13 for the project.
The “development manager” H4 and the “developer” H5 use the record input unit 25 to register the record in the project record 15.
The result monitoring unit 24 and the result input unit 25 also allow the computer to check the difference between the plan and the actual result by inputting the project plan tasks and resources and the actual value for the plan in a table form or a graphical form on the computer screen. The tool displayed on the computer screen, for example, the tool of Non-Patent Document 3.

In the conventional development process support apparatus, the tasks and resources of the project plan and the plans and results are expressed in a tabular or graphical format on the computer screen. Therefore, the computer checks the difference between the plan and the actual result, displays it on the computer screen, and “project planner”, “development manager” and “developer” (hereinafter, these three members are abbreviated as project members) are involved in project management. Work was done interactively and graphically.
The development process model 12 is defined by object-oriented technology. Generally, there is an aspect-oriented technology as a technology that complements the object-oriented technology. As an example of an aspect-oriented language, AspectJ shown in Non-Patent Document 6 is known.
IBM product catalog "RUP". The catalog can be obtained at http://www-6.ibm.com/jp/software/rational/products/pdf/rup.pdf SPEM (Software Process Engineering Metamodel) on the OMG website. Http://www.omg.org/technology/documents/formal/spem.htm Microsoft product "Microsoft Project". Http://www.microsoft.com/office/project/prodinfo/default.mspx IBM's product, “Rational Rose”. Http://www-6.ibm.com/jp/software/rational/products/design/ IBM's product, “Rational Clear Case”. The product catalog can be obtained at http://www-6.ibm.com/software/rational/products/scm/index.html). The products and information of the AspectJ project are http://www.eclipse.org/aspectj/

The conventional development process support apparatus is configured as described above, and has the following problems for the project staff (project planner, development manager, and developer) and the development process engineer.
In other words, in order for the project staff to practice the development process (plan the project, implement the development work, and monitor the project performance), it is necessary to read and understand the contents explaining the development process. Depends on the understanding of each project member. However, the content explaining the development process has an enormous and complicated document structure, and it is a problem that the workload of the development process practice is high for the project staff.
The development process engineer first defines the activities and deliverables constituting the requirements definition, analysis, design, implementation, test, etc., which are the main processes of software development, as a class using object orientation. However, there are management tasks (progress management, configuration management, etc.) that appear in common across the activities and deliverables of the main processes described above in software development. When the development process engineer defines these management tasks only in the conventional object orientation, it is necessary to insert the definition of the management tasks for each class corresponding to a large number of various activities and deliverables constituting the main process. The method of defining such management work is a problem that the load of work for defining and maintaining the same is the same because the same contents are duplicated and distributed in the development process model.

  The present invention has been made to solve the above-mentioned problems, and aims to reduce the workload by defining / editing a development process and planning / practice / monitoring a project based on the development process. And

The development process support apparatus according to the present invention includes a procedure for describing an aspect name using an aspect-oriented technique for a development management operation that traverses activities and deliverables defined by a development process model, and a pointcut corresponding to the aspect name. A development process aspect definition unit that defines and stores an aspect as a set of the above description, and a procedure for describing a name, and a procedure for describing execution contents of advice for the pointcut,
And a static weaver unit that applies the execution contents of the advice to the location on the project plan corresponding to the saved join point of the above aspect.

  As described above, according to the present invention, since the development process aspect is provided with the static weaver unit that inserts the development process aspect into the necessary part, the management work necessary for the skeleton for the project planner is automatically added to the project plan. It is only necessary to confirm without planning from the beginning, and the load of development work is reduced.

Embodiment 1 FIG.
An apparatus for generating a skeleton of “project plan” by interpreting the relationship between activities defined by “development process model” using “development process metamodel” as a schema will be described.
That is, a procedure (line numbers 1 and 2 in FIG. 2) for setting a work field designated on the development process model based on the development process meta model as a task in the project plan, and this development process model based on the development process meta model. A procedure (Figure 7, line number 7) for obtaining the group of activities of the work field specified by interpretation and setting it as a task in the project plan, and setting the role obtained from the development process model as a resource for this task Project schedule (step 2 in FIG. 2) and a procedure for setting an order relationship between activities obtained from the development process model as links between tasks in the project plan (row numbers 25 to 6 in FIG. 2). Equipped with a "plan generation unit" that automatically generates a skeleton of a plan It is the calling process support device.
FIG. 1 is a system configuration diagram according to the present embodiment. In the figure, a plan generation unit 31, which is a new element, uses the development process metamodel 11 as a schema, interprets relationships between activities defined by the development process model 12, and generates a skeleton of the project plan 14. To do. The other components are the same as the elements with the same numbers in FIG.

Here, the terms are first explained. First, SPEM terms defined by the OMG of the industry group described in the background art will be briefly described below.
Process: The whole process including the beginning to the end of development work.
Workline (Discipline): The work and deliverables defined in the process are classified according to a common theme. Specifically, for example, business modeling, requirements, analysis / design, implementation, testing, introduction, configuration and change management, project management, and environment are applicable.
Activity: Represents the minimum unit of work performed by a person.
Deliverables (WorkProduct): Created and used in the course of executing the process, such as programs and documents.
Role (ProcessRole): represents the position of the worker.
Next, the term AspectJ of the aspectJ project described in the background art will be briefly described below.
Instance: An individual instance of a class.
Joinpoint: represents the timing at which an aspect can be interrupted by a class. Specifically, for example, the timing of class method call corresponds.
Point cut: A set of join points that actually interrupt the aspect.
Advice: Indicates the contents to be executed in the point cut.
Aspect (Aspect): A combination of pointcuts (timing to interrupt a class) and advice (contents executed by the interrupt).

FIG. 2 is a pseudo code representing a step description as a function of the new plan generation unit 31. The important steps in the figure are the steps of inserting a task into the project plan at line numbers 2, 7 and 13, the step of setting the name of the process role as the resource of the task in the project plan at line numbers 10 and 16, , A step of setting a link between tasks in the project plan at line numbers 25 and 32.
Next, the operation will be described. The “project planner” H3 uses the plan generation unit 31 via the plan definition unit 23. Then, a skeleton of “project plan” 14 is generated from “development process model” 12.

FIG. 3 is a diagram showing a detailed configuration of the plan generation unit 31. As shown in FIG. 3, the plan generation unit 31 includes a processor 301, a memory 303, and a generation program memory 302 that stores a generation program describing the flow of FIG. 2, and inputs from the development process model 12 to the input unit 305. In response to this, the output unit 304 outputs a skeleton of the project plan. At this time, the “project planner” H3 designates the discipline that he / she wants to generate.
The skeleton of the project plan 14 is generated as follows. In this figure, the first uppercase alphabetic name enclosed in “” (for example, “Discipline” in line number 1) is a metaclass name defined by “Development Process Metamodel” 11, and is an OMG of an industry group. Conforms to SPEM defined by

The generation operation performed by the plan generation unit 31 will be described below using the row numbers in FIG.
The plan generation unit 31 obtains the discipline input above by the “project planner” H3 who wants to generate a skeleton at line numbers 1 and 2 by the input unit 305 and designates it according to the definition in the development process model 12 A task is inserted into the project plan corresponding to the discipline. In line numbers 3 to 4, a list of activities included immediately below the designated discipline is acquired from the development process model 12.
The plan generation unit 31 inserts the activity included in the activity list at line numbers 5 to 19 as a task into the project plan, and sets a resource for executing the inserted task. It is important to insert a subtask in the task corresponding to Discipline in the project plan at line number 7. It is also important to set a role name as a task resource in the project plan at line number 10.
In line numbers 12 to 18, task insertion and resource setting are performed for the subWork included immediately below Activity. A dependency relation between tasks inserted at line numbers 20 to 36 is set as a link.
Furthermore, it is important to set a link from the task in the project plan of line number 25 to another task. Conventionally, this has been manually input by the project planner H3, but this means that automatic link specification between tasks is made when a skeleton is generated.
In line numbers 28 to 35, the link setting is performed for the subWork included immediately under Activity according to the definition in the development process model 12.

As described above, the plan generation unit 31 performs the “project plan” according to the procedure described above by using the definition in the “development process model” 12 that can be interpreted by the general-purpose computer in accordance with the “development process metamodel” 11. 14 skeletons are generated.
Thus, in the conventional apparatus, the development process engineer of the project creates the development process content using the development process publishing unit 22. Further, the project planner has made the project plan by sequentially setting manually by using the plan definition unit 23. However, in the present embodiment, when the project planner specifies Discipline, the plan generation unit generates a skeleton of the project plan including the specified Discipline. Comparing the conventional system, in which the project planner makes a development plan from scratch, with this embodiment, which obtains a skeleton and confirms the development plan, this embodiment greatly reduces the load, and there is a deficiency such as forgetting to set It will be resolved.

Embodiment 2. FIG.
When the management tasks that appear in common across activities and deliverables that make up software development (such as progress management and configuration management) are defined only in the conventional object-oriented manner, classes corresponding to many different activities and deliverables Each time you need to insert a definition for management work. Such management work is defined in such a manner that the same content is duplicated and distributed in the development process model, so that the load of work for defining and maintaining it is high. Therefore, an apparatus that easily and easily defines such management work will be described.
In other words, the process of describing the aspect name using the aspect-oriented technology (line number 1 in FIG. 7) and the pointcut name corresponding to the above aspect name for the development management work crossing the activities and deliverables defined by the development process model (Line number 2 in FIG. 7), a procedure for describing a join point name for a pointcut (line number 3 in FIG. 7), and a procedure for describing a pointcut name for executing advice (line number 4 in FIG. 7) And a procedure for describing the execution timing for the pointcut (line number 5 in FIG. 7) and a procedure for describing the execution content of the advice for the pointcut (line number 6 in FIG. 7). The development process support apparatus includes a “development process aspect definition unit” that stores and defines a process.
FIG. 4 is a system configuration diagram according to the present embodiment. In the figure, the development process aspect 41, which is a new element, is a management operation (progress management and configuration management) that appears in common across the class groups (individual activities, deliverables, etc.) defined by the “development process model” 12. Are defined using aspect-oriented technology. The development process aspect definition unit 32, which is a new element, is a function that allows the “organizational development process engineer” H1 or the “project development process engineer” H2 to define and edit the development process aspect 41 on the computer screen. . Other components are the same as those in the conventional system.

In the present embodiment, the aspectJ grammar is used in a pseudo manner as an example of an aspect-oriented language describing the development process aspect 41. FIG. 5 shows an example of “development process aspect” described as pseudo code of AspectJ, and FIG. 6 shows grammatical elements of the development aspect example. The content of the example of FIG. 5 shows that before starting any activity, regardless of the type of activity, the project plan needs a milestone to obtain the input artifacts necessary to start the activity. It means that. The definitions of terms described in AspectJ are as described in the first embodiment.
The development process aspect definition unit 32 will be described with reference to FIG.
The “organizational development process engineer” H1 or the “project development process engineer” H2 uses the development process aspect definition unit 32 via the development process definition unit 21 to change the development process aspect 41 shown in FIG. Input while following the grammar elements of FIG. The detailed configuration of the development process aspect definition unit 32 in the present embodiment is the same as the configuration of FIG. 3, but the program stored in the generated program memory 302 has the description content of FIG. 7, for example.

Next, the operation of the development process aspect definition unit 32 will be described with reference to FIG. FIG. 7 shows an operation for one development process aspect, and FIG. 7 is repeated when a plurality of development process aspects are defined. Line number 1 is the aspect name, line number 2 is the pointcut name, line number 3 is the join point, line number 4 is the name of the pointcut to execute advice, and line number 5 is the execution timing for the input pointcut. In line number 6, the execution contents of the advice are stored in the development process aspect 41.
As the join point of line number 3 in FIG. 7, the interrupt timing for the class stored in the “development process model” 12 can be defined. Further, an operation for the instance stored in the “project plan” can be described as “advice execution content” in line number 6 of FIG.

In the prior art, the “management work”, which had to be defined in a distributed manner in the class group in the “development process model” 12, is defined by using the aspect-oriented technology, thereby creating one development process aspect 41. Can be stored, stored, and shared.
As described above, in this embodiment, management operations that appear in common in development are organized and stored in the database, and the subsequent maintenance is facilitated.

Embodiment 3 FIG.
It is a device that prevents deficiencies in the forgetting of planning that tend to occur when a project planner adds management work to a project plan.
In other words, the procedure for describing the aspect name (line number 1 in FIG. 7) and the pointcut name corresponding to the aspect name using the aspect-oriented technology for the development management work that crosses the activities and deliverables defined by the development process model. A development process aspect that includes a description procedure (line number 2 in FIG. 7) and a procedure (line number 6 in FIG. 7) for describing the execution contents of the advice for the pointcut, and defines and saves the aspect as a set of the descriptions. A definition section and a static weaver section having a procedure (line number 5 in FIG. 9) for applying the execution contents of the advice to a location on the project plan corresponding to the stored aspect join point. Development process support device.
FIG. 8 is a system configuration diagram according to the present embodiment. In the figure, a static weaver 33 has a function of interpreting a development process aspect at the time of project planning and statically weaving the aspect into the project plan. The other components are the same as the corresponding numbered elements in the previous embodiment, FIG. FIG. 9 is a diagram describing a pseudo code string indicating the functions of the static weaver unit 33. Further, FIG. 10 is a diagram showing a project plan output by the static weaver unit 33. FIG. 11 is a diagram illustrating an example of a metaclass, a class, and an instance of the development process. Further, the detailed configuration of the static weaver unit 33 is the same as the configuration shown in FIG. 3, but the content of the program stored in the generated program memory 302 is the pseudo code string shown in FIG.

Next, the operation will be described.
The “project planner” H3 weaves the “development process aspect” to the “project plan” using the static weaver unit 33 via the plan definition unit 23. The static weaver 33 has the function of the pseudo code string of FIG. 9 for one “development process aspect”. Of these, description of applying the execution contents of the advice at a predetermined timing to the corresponding part of the project plan of line number 5 is important.
For example, the operation when the development process aspect shown in FIG. 5 is applied to the “project plan” is as follows.
First, the advice of the development process aspect 41 of FIG. 5 is activated by line number 5 of FIG. Then, according to line number 9 in FIG. 5, before the task “subsystem A design review” shown in FIG. 10A, milestone “obtain design model” “auxiliary specification” as shown in FIG. 10B. "Getting" and "Getting design guidelines" are inserted.
A similar milestone is also inserted in the “subsystem B design review”. Conventionally, to create the project plan of FIG. 10B, read development process contents 13 and remember milestones such as “Obtaining design model”, “Obtaining auxiliary specifications”, “Obtaining design guidelines”, etc. However, in this embodiment, the static weaver unit 33 inserts these milestones.

In the example of the operation performed by the static weaver 33 described above, information shown in FIG. 11 which is an example stored in the development process metamodel 11, the development process model 12, and the project plan 14 is used. In the information shown in FIG. 11, the tasks “design review of subsystem A” and “design review of subsystem B” are instances of the activity “design review”, and the input product of the activity “design review” is “design model”. It shows that it is “Supplementary Specification” and “Design Guidelines”.
As described above, the information stored in the project plan 14 is an instance of a class defined by the development process model 12, and the information stored in the development process model 12 is an instance of a metaclass defined by the development process metamodel 11. It is. Since these are formal information and can be interpreted by the computer, in the present embodiment, the management work defined in the development process aspect 41 is reflected in the project plan 14 by the static weaver unit 33. .
As described above, in the present embodiment, since necessary management work is added to the project plan, there is an effect of reducing the work load of planning the project plan based on the development process.

Embodiment 4 FIG.
It is a device that prevents deficiencies in check mistakes that tend to occur when a development manager monitors a project performance or configuration management DB.
In other words, the procedure for describing the aspect name (line number 1 in FIG. 7) and the pointcut name corresponding to the aspect name using the aspect-oriented technology for the development management work that crosses the activities and deliverables defined by the development process model. A development process aspect that includes a description procedure (line number 2 in FIG. 7) and a procedure (line number 6 in FIG. 7) for describing the execution contents of the advice for the pointcut, and defines and saves the aspect as a set of the descriptions. When a change notification is received from the definition section and the configuration management database that manages project results and deliverables (line number 1 in FIG. 13), the advice is executed at the timing specified by the pointcut having the join point corresponding to this change notification. Development characterized by comprising a dynamic weaver part having a procedure (line number 6 in FIG. 13) for applying contents It is a process support unit.
FIG. 12 is a system configuration diagram according to the present embodiment. In the figure, the dynamic weaver unit 34 monitors the “project results” 15 and the “configuration management DB” 16 at the time of project execution, and executes the advice if it corresponds to the point cut of the development process aspect 41 and executes it. This is a function of notifying the result monitoring unit 24 of the result. Other components are the same as those shown in FIGS. The detailed configuration of the dynamic weaver unit 34 is the same as that shown in FIG. 3, but the program stored in the generated program memory 302 is described in pseudo code shown in FIG. In addition, the project record 15 and the configuration management DB 16 are added with a function of notifying the dynamic weaver 34 when a change is made to its contents.

Next, the operation will be described. When the dynamic weaver 34 receives a change notification from the project record 15 or the configuration management DB 16, it interprets and executes the development process aspect 41. That is, when the dynamic weaver 34 interprets the development process aspect 41, the project plan 14, the development process model 12, and the development process metamodel 11 are referred to. The dynamic weaver unit 34 operates according to the pseudo code described in FIG. It is important to apply the content of line number 6 in FIG. 13, that is, the execution content of advice.
Hereinafter, an operation example of the dynamic weaver unit 34 will be described according to FIG. 14 which is an example of a process aspect to be developed. The grammatical elements of the development process aspect 2 shown in FIG. 14 are shown in FIG. The dynamic weaver 34 uses information shown in FIG. The information in FIG. 16 is an example stored in the development process metamodel 11, the development process model 12, the project plan 14, and the configuration management DB 16.
In the information shown in FIG. 16, the tasks “design review of subsystem A” and “design review of subsystem B” are instances of the activity “design review”, and the output product of the activity “design review” is “review sheet”. Yes, the deliverables “design review sheet for subsystem A” and “design review sheet for subsystem B” are instances of the class “review sheet”.

First, it is assumed that the dynamic weaver 34 receives the completion of the “design review of subsystem A” from the project record 15 at line number 1 in FIG. In line numbers 2 to 4 in FIG. 13, it is determined that the join point of the development process aspect 2 shown in FIG. 14 corresponds and that the development process aspect can be applied. The execution contents of the advice of the development process aspect 2 (line numbers 4 to 12 in FIG. 14) are executed by line numbers 5 to 7 in FIG. If the deliverable “subsystem A design review sheet” is not registered in the configuration management DB according to line number 10 in FIG. 14, a warning is output to the performance monitoring unit 24.
As described above, the information stored in the project plan 14 and the configuration management DB is an instance of a class defined by the development process model 12, and the information stored in the development process model 12 is stored in the development process metamodel 11. An instance of a metaclass to be defined. Since these are formal information, the dynamic weaver 34 automatically executes the management work defined by the development process aspect 41 at the time of project execution by utilizing the fact that the computer can interpret it.

  In the conventional development process support apparatus, the development manager has to manually monitor the project results and the configuration management DB periodically by hand, and the work load is high, and check mistakes cannot be prevented. In the present embodiment, since the management work defined as the development process aspect in advance is automatically executed at the time of project execution, there is an effect of reducing the workload of project execution based on the development process.

Embodiment 5 FIG.
In each of the above embodiments, the plan generation unit, the development process aspect definition unit, the static weaver unit, and the dynamic weaver unit have been described as hardware each composed of a CPU and a memory. However, the present invention is not limited thereto, and may be a method described in pseudo code in each embodiment, or such a method may be read as a program and executed by an arbitrary general-purpose computer.

BRIEF DESCRIPTION OF THE DRAWINGS It is a system configuration | structure figure in Embodiment 1 of this invention. It is the pseudo code expressing the step which the plan generation part in Embodiment 1 has as a function. It is a figure which shows the detailed structure of the plan production | generation part in each embodiment, a development process aspect definition part, a static weaver part, and a dynamic weaver part. It is a system block diagram in Embodiment 2 of this invention. 10 is an example of a development process aspect in the second embodiment. FIG. 10 is a diagram showing grammatical elements of an example of a development process aspect in the second embodiment. FIG. 10 is a diagram illustrating an operation of a development process aspect definition unit in the second embodiment. It is a system block diagram in Embodiment 3 of this invention. It is the pseudo code expressing the step which the static weaver part in Embodiment 3 has as a function. It is a figure which shows the example of a project plan after operate | moving and outputting the example of a project plan before the static weaver part in Embodiment 3 operate | moves. FIG. 20 is a diagram illustrating an example of a metaclass, a class, and an instance of a development process in the third embodiment. It is a system block diagram in Embodiment 4 of this invention. FIG. 9 is a pseudo code representing steps that the dynamic weaver unit according to the fourth embodiment has as a function. FIG. FIG. 20 is a diagram showing an example of a development process aspect in the fourth embodiment. FIG. 20 is a diagram showing grammatical elements of an example of a development process aspect in the fourth embodiment. FIG. 20 is a diagram illustrating an example of a metaclass, a class, and an instance of a development process in the fourth embodiment. It is a figure which shows the conventional development process support apparatus. It is a figure which shows the example of a development process metamodel. It is a figure which shows the example of a development process definition part and a development process model. It is a figure which shows the example of a development process content. It is a figure which shows the example of a screen of a plan definition part, a performance monitoring part, and a performance input part.

Explanation of symbols

  11 development process metamodel, 12 development process model, 13 development process content, 14 project plan, 15 project results, 16 configuration management DB, 21 development process definition unit, 22 development process publishing unit, 23 plan definition unit, 24 performance monitoring unit , 25 Results input section, 26 Development environment section, 31 Plan generation section, 32 Development process aspect definition section, 33 Static weaver section, 34 Dynamic weaver section, 41 Development process aspect, 301 processor, 302 Generated program memory, 303 memory , 304 output unit, 305 input unit.

Claims (6)

In a development process support apparatus that has a processor, a memory, and a generated program memory and supports execution of the development process,
A development process aspect definition unit that operates when the processor executes a generation program stored in the generation program memory, the development process model including information defining a plurality of activities to be executed in the development process, development management tasks to perform in common with the plurality of activities that will be defined by the information included in the development process model memory is stored, and enter the execution contents of the development management tasks from the user, the development management tasks A condition to be executed is input from the user, an aspect name indicating the combination of the execution content and the condition is input from the user, a pointcut name indicating the condition is input from the user, and the input aspect name is input . and point cut name entered corresponding to the above-mentioned aspect name, the point And run your input corresponding to the Tsu name, and the development process aspect definition section to save the conditions input corresponding to the above-mentioned point cut name as an aspect in the memory,
A static weaver unit that operates when the processor executes a generation program stored in the generation program memory, and is executed in response to an activity defined by information included in a development process model stored in the memory. A project plan including information representing one or more scheduled tasks, the project plan stored in the memory is input from the memory, and the aspect stored by the development process aspect definition unit is input from the memory and input. Based on the aspect, the information representing the task for executing the execution contents of the aspect is generated at the timing corresponding to the condition of the aspect, the information representing the generated task is inserted into the input project plan, and the generated task is Project with inserted information Plan development process support apparatus characterized by comprising a static Uiba unit to be stored in the memory. In a development process support apparatus that has a processor, a memory, and a generated program memory and supports execution of the development process,
A development process aspect definition unit that operates when the processor executes a generation program stored in the generation program memory, the development process model including information defining a plurality of activities to be executed in the development process, development management tasks to perform in common with the plurality of activities that will be defined by the information included in the development process model memory is stored, and enter the execution contents of the development management tasks from the user, the development management tasks A condition to be executed is input from the user, an aspect name indicating the combination of the execution content and the condition is input from the user, a pointcut name indicating the condition is input from the user, and the input aspect name is input . and point cut name entered corresponding to the above-mentioned aspect name, the point And run your input corresponding to the Tsu name, and the development process aspect definition section to save the conditions input corresponding to the above-mentioned point cut name as an aspect in the memory,
A dynamic weaver unit that operates when the processor executes a generation program stored in the generation program memory, and is executed in response to an activity defined by information included in a development process model stored in the memory. A project plan including information representing one or more scheduled tasks, and a change is made from the configuration management database that manages a product created by a task executed according to the project plan stored in the memory to the product. In response to the change notification indicating that there is a change, the aspect stored in the development process aspect definition part is input, and based on the change notification and the input aspect, the product managed by the configuration management database is set as the condition of the aspect. If it is determined whether it is applicable, , The development process support system which is characterized in that a dynamic Uiba unit that executes the execution contents of the aspect. In a development process support method in which a development process support apparatus having a processor, a memory, and a generated program memory supports execution of a development process,
When the processor executes the generation program stored in the generation program memory, the processor is a development process model including information defining a plurality of activities to be executed in the development process, and the development process stored in the memory development management tasks to perform in common with the plurality of activities that will be defined by the information in the model, inputting the execution contents of the development management tasks from the user,
When the processor executes the generation program stored in the generation program memory , the processor inputs a condition for executing the development management work from a user;
When the processor executes the generation program stored in the generation program memory, the processor inputs an aspect name indicating a set of the execution content and the condition from a user;
When the processor executes the generation program stored in the generation program memory, the processor inputs a pointcut name indicating the condition from the user;
When the processor executes the generation program stored in the generation program memory, the processor inputs the aspect name input, the input pointcut name corresponding to the aspect name, and the input corresponding to the pointcut name. Saving the execution content and the input condition corresponding to the pointcut name as an aspect in a database stored in the memory ;
When the processor executes the generation program stored in the generation program memory, the processor is scheduled to be executed corresponding to the activity defined by the information included in the development process model stored in the memory 1 A project plan including information representing the above tasks, the project plan stored in the memory is input from the memory, the aspect stored in the database stored in the memory is input from the memory, and based on the input aspect Then, information representing the task that executes the execution contents of the aspect is generated at a timing corresponding to the condition of the aspect, information representing the generated task is inserted into the input project plan, and information representing the generated task is inserted. Above the planned project plan Development process support method characterized by comprising the steps of storing in a memory. In a development process support method in which a development process support apparatus having a processor, a memory, and a generated program memory supports execution of a development process,
When the processor executes the generation program stored in the generation program memory, the processor is a development process model including information defining a plurality of activities to be executed in the development process, and the development process stored in the memory development management tasks to perform in common with the plurality of activities that will be defined by the information in the model, inputting the execution contents of the development management tasks from the user,
When the processor executes the generation program stored in the generation program memory , the processor inputs a condition for executing the development management work from a user;
When the processor executes the generation program stored in the generation program memory, the processor inputs an aspect name indicating a set of the execution content and the condition from a user;
When the processor executes the generation program stored in the generation program memory, the processor inputs a pointcut name indicating the condition from the user;
When the processor executes the generation program stored in the generation program memory, the processor inputs the aspect name input, the input pointcut name corresponding to the aspect name, and the input corresponding to the pointcut name. Saving the execution content and the input condition corresponding to the pointcut name as an aspect in a database stored in the memory ;
When the processor executes the generation program stored in the generation program memory, the processor executes one or more scheduled to be executed corresponding to the activity defined by the information included in the development process model stored in the memory. A project plan that includes information representing a task, and a change that represents a change in the deliverable from the configuration management database that manages the deliverable created by the task executed in accordance with the project plan stored in the memory Upon receiving the notification, the aspect stored in the database stored in the memory is input, and based on the change notification and the input aspect, whether the deliverable managed by the configuration management database satisfies the aspect condition. If it is determined to be applicable, the above Development process support method characterized by comprising the step of executing the execution contents of the spectrum. A program that can be executed by a computer having a processor and a memory, and when executed by the computer ,
The processor, in common with the plurality of activities that will be defined by the information which the memory a development process model including information defining a plurality of activities to be performed in the development process is included in the development process models stored for development management tasks to be performed, and the step of inputting the execution contents of the above-mentioned development management work from the user,
A step in which the processor inputs a condition for executing the development management work from a user;
The processor inputs an aspect name indicating a set of the execution content and the condition from a user;
The processor inputs a pointcut name indicating the condition from the user;
The processor, the aspect name entered, the pointcut name entered corresponding to the aspect name, and execution contents inputted corresponding to the pointcut name, the memory and the entered conditions corresponding to the pointcut name a step but to save as an aspect in the storage database,
The processor stores a project plan that includes information representing one or more tasks scheduled to be executed in response to an activity defined by information included in a development process model stored in the memory, the memory storing A project plan is input from the memory, an aspect stored in a database stored in the memory is input, and a task for executing the execution contents of the aspect at a timing corresponding to the condition of the aspect based on the input aspect. Generating the information to be represented, inserting the information representing the created task into the input project plan, and storing the project plan in which the information representing the created task is inserted in the memory Process support program. A program that can be executed by a computer having a processor and a memory, and when executed by the computer ,
The processor, in common with the plurality of activities that will be defined by the information which the memory a development process model including information defining a plurality of activities to be performed in the development process is included in the development process models stored for development management tasks to be performed, and the step of inputting the execution contents of the above-mentioned development management work from the user,
A step in which the processor inputs a condition for executing the development management work from a user;
The processor inputs an aspect name indicating a set of the execution content and the condition from a user;
The processor inputs a pointcut name indicating the condition from the user;
The processor, the aspect name entered, the pointcut name entered corresponding to the aspect name, and execution contents inputted corresponding to the pointcut name, the memory and the entered conditions corresponding to the pointcut name a step but to save as an aspect in the storage database,
The processor is created by a task executed in accordance with a project plan including information representing one or more tasks scheduled to be executed in response to an activity defined by information included in a development process model stored in the memory. A change notification indicating that the deliverable has been changed is received from the configuration management database that manages the deliverable, and the aspect stored in the database stored in the memory is input, and the change notification is input to the input aspect. And determining whether the product managed by the configuration management database satisfies the condition of the aspect, and executing the execution contents of the aspect when it is determined that the product is applicable Development process support program.

Images