JP3383457B2 - Extraction method of user interface design support information - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION [0001] BACKGROUND OF THE INVENTION The present invention relates to a user interface
The method of extracting design support information
User Interface for Developing Oriented Systems
Effective technology applied to design support information extraction method
Things. [0002] 2. Description of the Related Art Object-oriented system development
In user interface design, generally,
External specifications are defined based on the required specifications, and based on the external specifications.
To advance the design. [0003] The external specifications determined here include the system
Screen design is also included and works on the designed screen
System to be developed. In addition, object-oriented system development
In user interface design, object-oriented
In order to maximize the reusability, which is the advantage of
Consider using production (class library). [0005] Therefore, the determined external specifications and existing assets
It is necessary to proceed with development while maintaining consistency with [0006] Actually, in the external specification determined in advance,
You can make full use of already designed objects.
In some cases, browsers (based on structure)
Tool that allows you to search the source code
Class definitions and methods for each object using
Check the definition and manually match with external specifications.
Was. As such, for example, Micr
Visual C + from Microsoft (Microsoft)
+ (Visual Sea Plus Plus) class library
ClassWiz described in Reuser's Guide
ard (Class Wizard)
This is the message received on the screen or other interface
To a program called a message handler
The user can handle the message handler.
Designing the interface by creating it manually
I can. [0008] SUMMARY OF THE INVENTION The present inventor has proposed a
As a result of studying the technology, the following problems were found. A user interface using the above-mentioned prior art
In the source design, the “browser” uses
Examine class and method definitions and define manually
Organize information and ensure consistency with screens and other interfaces
However, the external specifications are related to the tasks handled by the system.
Is often determined without sufficient analysis. For this reason, verification of the user interface
When performing a search, use the search function of the "browser"
Class definitions and method definitions that need to be checked
Search is required and it takes time.
Was. Further, the class definition and the method
Since the sorting of definition information is also done manually,
Often overlook the class and method definitions
Of objects in the business area designed in advance
Analysis and design results cannot be fully utilized
There is a problem that a combination occurs. [0012] For this reason, scouring is performed based on the results of business analysis.
Screen design that reflects the model on the interface
Was left to the skills of the user. An object of the present invention is to provide a user interface
Providing technology that can reduce the time required for design
It is to be. Another object of the present invention is to provide a user interface.
When designing a business area,
Provide technology that enables accurate analysis of objects
Is to do. The above and other objects and novel features of the present invention
Features are apparent from the description of this specification and the accompanying drawings.
Will be. [0016] SUMMARY OF THE INVENTION The present invention is disclosed in the present application.
A brief description of typical inventions will be given below.
It is as follows. In the development of an object-oriented system
Information that supports the design of the user interface
User interface design support information extracted from stem
The method of extracting informationUsed by the systemclass
From the contents of the library source fileAnd saidClasla
Object class definition information in library
Mounting information, components that make up the screen, and user input
Event handler generated byScreen definition that describesEmotion
Extract information, ThatManipulating a class with extracted methods
Classify works and recognize class operation patterns on the screen
User-in that derived the correspondence between screens and classes
Extract and output interface design support informationThing
To. [0018] According to the above-mentioned means, an object-oriented system is provided.
Supports user interface design in system development
User interface for extracting information to assist from the system
In the method for extracting face design support information,System
Used byContents of class library source file
FromAnd saidObject library in class library
Class definition information, method implementation information, and screen components
Event handler generated by the product and user input
Screen definition that describesExtract information, ThatExtracted meso
Classify the class operations by
Recognize operation patterns and guide the correspondence between screens and classes
Extracting user interface design support information
By outputting, just referring to the output,Said
Object in the class libraryClass definition and
Eliminates the need to search for method definitions
Reduces the time required for user interface design
Canit can. Also, simply by referring to the output,
Analysis and design of objects in the business area
It can be used without loss and provides accurate analysis.
It becomes possible. Hereinafter, the present invention will be described together with examples.
I will tell. Incidentally, in all the drawings for explaining the embodiments, FIG.
Those having the same function are given the same reference numerals,
The description of the return is omitted. [0022] FIG. 1 is a diagram showing a user interface according to an embodiment of the present invention.
To explain how to extract interface design support information.
It is a flowchart. The user interface design support of this embodiment
As shown in FIG. 1, the method of extracting the support information is as follows.
File 300, implementation file 400, event handler implementation
File 1300, screen definition file 700, class
Referring to the class definition file 1200, the class information extraction process is performed.
Processing (step 101), method information extraction processing (step 101).
102), event handler information extraction processing (step
103), screen class corresponding processing (step 104),
To sequentially perform each process of the sex extraction process (step 105)
It is. FIG. 2 shows the user interface of the present embodiment.
Hardware configuration of the system that implements the software design support method
FIG. A system for realizing this embodiment is shown in FIG.
As shown, it has a sequential processing capability based on
1. The CPU 201 that executes each process shown in FIG.
Memory 202 capable of storing program data and a key
Pointing devices such as boards and mice;
An input equipped with a display capable of outputting the results
And an output device 203.
Object-oriented systems to which interface design is applied
Header file 300 that describes the
File 400 and event handler implementation file 1300
And screen definition file 700, and class classification
Storing the defined class classification definition file 1200
An apparatus 204 is provided. Next, the user interface of the above-described embodiment will be described.
As a system to which the face design is applied, specifically,
Picked up the database system of the library, and
Will be described. Library database system is a library business
Information about books, users, and lending
It is a system to manage. The result of the analysis of the library business
Figure 3 shows an example of an object model
Shown in The object shown in FIG.GThe figure shows
"Object-Oriented Methodology OMT" (J. Rambo et al., Wings
Based on the notation written in Eiichi Ikuta, Toppan)
It is described. The object diagram shown in FIG.
Is a model of the target business based on
Yes, an object-oriented system is constructed based on this diagram
Is done. The length divided into two or three parts shown in FIG.
Squares indicate classes. Classes have common properties
Objects that have common properties
It is. In the example shown in FIG.
(Shokan) Class 1001, Human Class 100
2. LibraryUser (user) class 100
3, Book (book) class 1004, LibraryB
book class 1005, RentalLog
(Lending record) Consists of six classes, class 1006
Have been. The top part of each class contains
The class name is described, and the second part is the object of each class.
Multiple attributes that the object holds internally are described for each line.
You. The attributes are implemented as variables. In the third part, the attributes of each class are manipulated.
Multiple methods are described for each line. In FIG. 3, simply refer to the attribute.
Methods to set values for attributes and attributes
Abbreviated. The naming standard in FIG.
Start with an uppercase letter and start the attribute or method name with a small letter.
Characters. In order to clarify the word break,
Is capitalized. Ride this rule
Take, for example, simply refer to the value of the attribute name 1041
Methods to get, getName, method to set the value
Is setName. The generalization relations 1031 and 1032 are
The class connected to the bottom side of the polygon is connected to the opposite vertex
Indicates that the attributes and methods of the following class are to be inherited.
At this time, the former class is a subclass, and the latter class is
Call it a superclass. The whole partial relationship 1033 is tangent to the rhombus.
Class that owns the class on the other side
Has a taste. Other associations 1034 to 1036
Indicates that the competitors correspond, and the black circles indicate that they correspond
Indicates that if there is no black circle, only one object corresponds
To do so. In FIG. 3, the LibraryUser
(User) Class 1003 is a LibraryBook
(Books) Class 1005 and rent (loan) 1036
It has a one-to-many relationship. Next, each process described with reference to FIG.
This will be described in detail. First, the library database system described above is used.
Class information extraction processing (step
Step 101) will be described. The class information extraction process shown in FIG.
Class 101), from the header file 300, class information
500 and generate a class information table 500a
This is the process to be performed. FIG. 4 shows a library user class 1
003 shows a header file 300. In FIG. 4, step 301 is a process in which
declaration of the raryUser class 1003 and Huma
Show that n class 1002 is a super class
I have. In step 302, the attribute userCode
313 declaration. Step 303 is a method rentBo
Ok314 declaration. Here, the information shown in FIG.
It is extracted mechanically by Ira technology and
Create the information table 500a. This compiler technology is used in computer science / software.
Software Technology Lecture 7 Theory and Realization of Compiler (Hikita Teru
Man, Kiyoshi Ishihata, Kyoritsu Shuppan Publishing) P31
This is due to the technique of sentence analysis. FIG. 5 shows the header file 30 shown in FIG.
Class information storing the class information 500 extracted by 0
It is a report table 500a. The class information table 500a shown in FIG.
Is the class name 501, super class name 502, attribute
List 503 and the items of the method list 504.
ibrary class 1001, Human class 100
2, LibraryUser class 1003, Book
Class 1004, LibraryBook Class 100
5. Information of the RentalLog class 1006 is described.
Have been. Here, the header file 30 shown in FIG.
If 0, the LibraryUser class 1003
Has Human Class 1002 as a super class
Also, userCode and numOfBook as attributes
s, and methods: rentBook, ret
have arnBook, getNumOfBooks
As shown in FIG. 5, the class information table
File 500a. Next, the method information extraction processing shown in FIG.
(Step 102) will be described. The method information extraction process (step
102) is a method information from the implementation file 400.
Report 600, and its method information table 600a.
This is the process of generating. FIG. 6 shows a library user class 1
003 method RentBook314
FIG. 3 is a diagram showing an installation file 400. In FIG. 6, step 401 is an argument
is the declaration of theBook411, and the argument theBook
ok411 is a LibraryBook class 1005
Object. In step 402, the argument t
message to the heBook object 411
412 is transmitted. Step 403 is an assignment expression, and the attribute n
umOfBooks413 is described on the left side
Indicates that the value is to be set.
Indicates that the value is to be referenced. Step 404 is a LibraryBook
The argument is included in the rent method 412 of the k class 1005.
It is not shown. Step 405 is the process of RentalLog
The object of the lath 1006 is based on the reserved word new415.
And theRentalLog object 414
Is generated. Here, the information shown in FIG.
It is extracted mechanically by the empirical technique and the meso
And creates a read information table 600a. FIG. 7 shows an example of the above-described mounting file 400.
Extracted library 1001 class
Method information table 60 storing sod information 600
0a, and here, each
r class, Library class, LibraryBo
It shows method information of the ok class. In FIG. 7, the method name 601 is
The class of the object created in the method is
In the generated class list 602, the
Lass is described in the disappearance class list 603. The change attribute list 604 stores the corresponding method.
Contains a list of attributes whose values are set in the processing of the
It is. The reference attribute list 605 has the corresponding method
List of attributes whose values are read in the process of
It is. The transmission message list 606 has a corresponding
Object passed as a message in method processing
A list of pairs of object classes and method names is stored.
You. Then, in the mounting file 400 shown in FIG.
From step 401 to step 403, the library
RentBook611 of User class 1003 is
Nu is added to the change attribute list 604 and the reference attribute list 605.
mofBook, Librar in outgoing message list
yBook and Rent are each stored as method information.
Has been delivered. Next, the event handler information shown in FIG.
The extraction process (step 103) will be described. Event handler information extraction processing shown in FIG.
103 is the event handler implementation file 1300
Then, the event handler information 800 is extracted, and the event
Processing for generating the handler information table 800a.
You. Hereinafter, the event handler implementation file 13
As an example of 00, lend a library database system
The events on the screen will be described. FIG. 8 shows the library database system of this embodiment.
FIG. 10 is a diagram showing a lending screen 1100 which is one screen of the stem.
You. As shown in FIG. 8, the lending screen 1100 displays
Book code field 1111 and title field 1
112, author field 1113, publisher field 1
114, book search button 1115, user code fee
Field 1121, user name field 1122, user search
Search button 1123, rental date field 1131, return expected
Fixed date field 1132, loan button 1141, cancel button
It comprises a tongue 1142. This is because the user of the system can read the book code file.
Enter the book code in the field 1111 and press the book search button.
Button 1115 with a pointing device such as a mouse.
The title field 1112,
Field 1113 and publisher field 1114
Display and confirm the information of the corresponding book, and
User code given in advance to the
Enter and click the user search button 1123
To display the user name in the user name field
To confirm. The rental date field 1131 includes a system
Displays the current month and day by the clock held inside
I do. In the expected return date field 1132, the system
The expected return date calculated based on the set lending period is
Is displayed. Thereafter, the user clicks the lend button 1141.
To borrow the specified book
Can be. Also, if you do not want to lend,
You can get a loan by clicking on
Can be stopped. FIG. 9 shows the lending screen 1100 shown in FIG.
Screen definition file 700 showing the screen information of
You. In the example of FIG. 9, the screen components 1111, 1
115, 1211, 1123, 1141, and 1142 are described.
Has been described. Event 'EV_UPDATE' 710
Is the event that occurs when a string is entered in the field.
Event “EV_BUTTONDOWN”
711 occurs when the screen part is clicked
Event. FIG. 10 shows the rental screen re shown in FIG.
All event handlers 721 to ntScene 1100
About mh_bookQuery 724 in 726
Is an implementation file 1800. In FIG. 10, step 1801 is a step
Pull to vent handler mh_bookQuery724
Indicates that there is no number. Further, step 1802 is executed by rentSc
book code field of ene (lending screen) 1100
Enter the book code entered in
Referenced by Code 1812, substitute for Code 1811
To enter. Step 1803 is a library
Instance myLibrary1814
The book code code1811 entered in
Sends the message queryBook618 to
Refer to the book you want to use. Further, the search results are stored in theBook1.
813. Step 1804 is the search result th.
Message getTitl for eBook1813
e1816 is transmitted, and the title of the book is referred to. Further, according to showTitle1815,
RentScene1100 title field
1112 indicates that a title is to be displayed. Here, the information shown in FIG.
It is extracted mechanically by the compiler technology and shown in FIG.
Create the event handler information table 800a. FIG. 11 shows a book to which the embodiment of the present invention is applied.
Rental screen r which is one screen of the library database system
Event handler information for entScene1100
Event handler information table 80 storing information 800
0a. The event handler name 801,
The object class created in the event handler
Is displayed in the generated class list 802.
Class is described in the disappearance class list 803.
You. The transmission message list 804 corresponds to
Passed as a message in the event handler process
List of pairs of object classes and method names
Will be delivered. FIG. 11 shows a rental screen rentSce.
event handlers 721 to 726 for ne1100
Event handler information is stored. Here, for example, the event C shown in FIG.
Event handler m shown in the handler implementation file 1800
h_bookQuery 724 is a creation and death class
There is no list and the sent message list contains Lib
Send rary (book code) to queryBook
Is stored. In this way, the event handler information
Make a table. The event handler mh_bo
okQuery 724 is a book search button in FIG.
When 1115 is clicked, the event 'E is displayed according to FIG.
V_BUTTONDOWN '711 is generated and
Corresponding event handler 'mh_bookQuer
y'724 is executed. Further, as shown in FIG.
In 'mh_bookQuery' 724, the event
Object is created / deleted in the event handler
Message to Library class 1001
queryBook 613 will be sent. Next, the screen class corresponding processing shown in FIG.
(Step 104) will be described. The screen class correspondence processing 103 shown in FIG.
Class information 500, method information 600, and event handling
Dora information 800 and screen definition file 700
To extract the screen class correspondence information 900
This is a process for generating the response information table 900a. FIG. 12 shows the screen class correspondence information table.
9A illustrates a file 900a. The screen class correspondence information table 900a is
Class of object to be generated for screen name 901
Class list 902 that collects objects, objects to be extinguished
Class list 903 that collects the classes of
A collection of classes of objects whose values can be changed
Class list 904, object referring to attribute value
The reference class list 905 that collects the classes of
It is represented by a set table. FIG. 13 shows a screen class correspondence process (step
104) is a flowchart for realizing step 104). Here, steps 1501 to 15
Step 09 for all screens by loop of 09
Steps 1502 to 1508 are repeated. Steps 1502 to 150
All event handlers on the screen by loop of 8
Steps 1503 to 1507 are repeated for
return. In step 1503, the event handler
Is added to the screen class correspondence information. Step 1504 is for the event handler.
Add the extinction class to the screen class correspondence information. Steps 1505 to 15
All the event handlers are sent by the loop of 07
Step 1506 is repeated for the message. Step 1506 is a message evaluation process.
FIG. 14 is a flowchart for realizing the processing.
Show. In FIG. 14, step 1601 is a
Prepare parameters for message evaluation processing. Concrete
Specifically, it receives the screen name, class name, and method name. In step 1602, the target class
Determines whether the method has already been processed
If not, the process proceeds to step 1603. Processed
Exits from the recursive process if it is
The price processing ends. In step 1603, the target class
Check if there is a corresponding method, if not
Goes to step 1604. Corresponding method exists
If so, the process proceeds to Step 1606, and Step 16
07 causes the method to change the attributes of the class.
Check the change attribute to see if If a change attribute exists,
Perform step 1614 to change the class
Add as Thereafter, at step 1608, the message
See if the sod references an attribute of that class
Examine attributes. If the reference attribute exists
Executes step 1615 and changes the class.
Add as a lath. Then, according to step 1609,
Screen class of the screen class corresponding to the generated class
Information, and in step 1610, the disappearance class
Add to the screen class correspondence information of the corresponding screen class and
By the loop of steps 1611 to 1613,
Message evaluation processing (scan) for all outgoing messages
Step 1612) is performed recursively. In step 1604, the super class
Check for presence, and as a result, a superclass exists
Message to the superclass
Value processing. If the super class does not exist, the
The corresponding method does not exist, and as an error
Report to user. Next, the screen name "rents" shown in FIG.
Taking cine (rental screen) 914 as an example,
The screen class correspondence processing will be specifically described. First, the screen setting of the rental screen shown in FIG.
The definition file mh_doRent721 is shown in FIG.
When the event handler information table 800a is checked,
Library class 1001 in outgoing message list
The rentBook 617 is listed. [0114] As for this rendBook 617,
When examining the method information table 600a shown in FIG.
NumofBoo in change attribute list and reference attribute list
ks, LibraryBook to send message list
The list 1006 rent 620 is listed
Have been Then, LibraryBook class 1
005 ren 620, Re is added to the generated class list.
ntalLog 1006 is listed. From these, the lending screen shown in FIG.
The screen class correspondence information table 900a of FIG.
7 in the method information table 600a
The listed RentalLog 1006 is
Listed in the generated class list,
In the list, Lib with numofBook as an attribute
Each raryUser1003 is listed.
You. Next, the characteristic extraction process shown in FIG.
Step 105) will be described. The characteristic extraction processing shown in FIG.
Response information 900 and class classification definition information 1200
Then, the designed screen is evaluated and the screen characteristic information 1900 is obtained.
Create and display the information. FIG. 15 shows the class characteristics for the screen.
Class definition information table 120 describing the conditions
0. Class classification definition information table shown in FIG.
1200 is for class classifications 1201 to 1205,
It expresses the presence or absence of the relationship 1211 to 1214 with the screen.
You. In FIG. 15, "essential" is described.
The corresponding action is performed on the screen
Items that are described as `` None ''
Means that no processing is performed in the screen
I have. In the blank, the presence or absence of the relationship is indicated by the class.
It does not affect the characteristics of. Referring to FIG. 15, for example,
1 means that the class is generated and disappears on a certain screen
Indicates a relationship. In addition, changes and references
Does not indicate that the characteristics of the class can be limited.
You. FIG. 16 shows a screen as an evaluation result of the design screen.
This is characteristic information 1900. The screen characteristic information 1900
Evaluate the class name for the screen name 1901 and its screen
The result of the edit class 1911, generation class 1912,
Destruction class 1913, Change class 1914, Reference class 1
915 is stored separately. For example, in FIG. 16, the screen name 'rentS
As a characteristic of each class with respect to “cene ′,
Contains 'RentalLog', editing class,
Class does not exist in the class
Lass has' LibraryBook ',' Boo
k ',' LibraryUser ', and' Human '
Indicates that this is the case. FIG. 17 is a flowchart for realizing the characteristic extraction processing.
The chart is shown. In FIG. 17, steps 1701 to
The loop of step 1707 causes all screens to be
Steps 1702 to 1706 are repeated. Step
By the loop from step 1702 to step 1706,
Everything described in the screen class correspondence information of the screen
Steps 1703 to 170
Repeat step 5. In step 1703, the corresponding class
Then, for all class classification definition information 1200,
Step 1704 is repeated. Step 1704 is for the target class.
Does the condition for each classification definition hold?
Investigate whether it is possible, and if
Step 17 through the loop composed of step 1705
Proceed to 08. If not, go to step 1705
move on. The step 1708 is for the established class classification.
The corresponding class is added to the classification corresponding to
Go to 9. In step 1709, the screen characteristic information 190
0 is displayed, and the characteristic extraction processing ends. FIG. 18 shows a table of the screen characteristic information 1900.
Illustrative Example 1500 is shown. In FIG. 18, the screen name field 1301 contains
The screen name 'rentScene' is displayed and generated
In the class list field 1312, 'Rental
Log ′ is displayed, and the change class list field 13 is displayed.
14, “LibraryUser” is displayed.
In the reference class list field 1315, 'Libra
ryBook ',' Book ',' LibraryUs
er 'and' Human 'are displayed. The edit class list field 1311 is turned off.
Deletion class list field 1313, Change class list
No corresponding class exists in the field 1314
Therefore, nothing is displayed. Based on these information, the designed rental image
The side (rentScene) is the rental record (Rent
alLog) only, and the user can be changed.
It is clear that other objects can only be referenced.
Be sure. [0136] This supports the examination of the designed screen.
And more, with object model and screen interface
Can be clearly maintained. In the result display, as shown in FIG.
It is also possible to display class characteristic information. FIG. 19 shows a display example 140 of class characteristic information.
0 is shown. In FIG. 19, click on the class name field.
"RentalLog" which is the name of the class is displayed and generated
The screen list field 1411 contains 'rentScen'
e 'is displayed, and the disappeared screen list field 1412 is displayed.
Displays 'logScene' and changes screen list
'BackScene' is displayed in field 1413
In the reference screen list field 1414, 'logS
Cene 'is displayed. Display of class characteristics is displayed on the screen
It is output based on the class correspondence information 900. Therefore, as described above, the object
User interface in the development of security oriented systems
A user who extracts information that supports the design of
In the method of extracting the interface design support information,
From the contents of the source file of the existing class library
Class definition of object in existing class library
Information, method implementation information, screen components, and
Extract event handler information generated by user input
Output, and generate for each screen based on the extracted information.
Extract the method corresponding to the event
Class operations by the methods
Recognizes the operation pattern of the class and the correspondence between the screen and the class
User interface design support information
By outputting and outputting, just refer to the output
That need to be referenced in the existing class library
It is not necessary to search for class definitions and method definitions sequentially.
Time for user interface design
Can be shortened. Also, simply by referring to the output,
Analysis and design of objects in the business area
It can be used without loss and provides accurate analysis.
It becomes possible. As described above, the invention made by the present inventors is described below.
Although specifically described based on the above embodiment, the present invention
The present invention is not limited to the above-described embodiment, but may deviate from the gist thereof.
Of course, various changes can be made within the
You. [0142] The present invention is a representative of the inventions disclosed in the present application.
To briefly explain the effects that can be achieved by using
It is as described. Just by referring to the output,The clasla
Object in the libraryClass definitions and methods
It is not necessary to search the definition of
・ Reducing the time required for interface designso
Wear. Also, simply by referring to the output,
Analysis and design of objects in the business area
It can be used without loss and provides accurate analysis.
It becomes possible.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a flowchart illustrating a method for extracting user interface design support information according to an embodiment of the present invention. FIG. 2 is a block diagram illustrating a hardware configuration of a system that implements a user interface design support method according to the present embodiment. FIG. 3 is an object diagram showing an example of an object model which is a result of an analysis on library work in the embodiment. FIG. 4 is a LibraryUser class 10 of the embodiment.
FIG. 3 is a diagram showing a header file 300 of FIG. FIG. 5 is a diagram illustrating a class information table 500a according to the present embodiment. FIG. 6 is a LibraryUser class 10 of the embodiment.
FIG. 13 is a diagram showing an implementation file 400 for a method rentbook 314 of FIG. FIG. 7 is a diagram illustrating a method information table 600a according to the present embodiment. FIG. 8 is a diagram showing a lending screen 1100 which is one screen of the library database system of the present embodiment. FIG. 9 is a diagram illustrating a screen definition file 700 according to the present embodiment. FIG. 10 is a diagram illustrating an implementation file 1800 according to the present embodiment. FIG. 11 is an event handler information table 8 of the embodiment.
FIG. FIG. 12 is a screen class correspondence information table 90 of the embodiment.
FIG. FIG. 13 is a flowchart for realizing a screen class corresponding process according to the present embodiment. FIG. 14 is a flowchart for realizing a message evaluation process of the embodiment. FIG. 15 shows a class classification definition information table 12 according to the embodiment.
FIG. FIG. 16 is a diagram illustrating screen characteristic information 1900 according to the present embodiment. FIG. 17 is a flowchart for realizing a characteristic extraction process according to the present embodiment. FIG. 18 is a display example 1 of the screen characteristic information 1900 according to the present embodiment.
FIG. 19 is a diagram showing a display example 1400 of class characteristic information according to the present embodiment.
FIG. [Description of Signs] 101: Class information extraction processing, 102: Method information extraction processing, 103: Event handler information extraction processing, 10
4: Screen class correspondence processing, 105: characteristic extraction processing, 20
DESCRIPTION OF SYMBOLS 1 ... CPU, 202 ... Memory, 203 ... Input / output device, 2
04 storage device, 300 header file, 400 implementation file, 500 class information, 600 method information, 700 screen definition information, 800 event handler information, 900 screen class correspondence information, 1001 Lib
rary class, 1002 ... Human class, 100
3 ... LibraryUser class, 1004 ... Boo
k class, 1005 ... LibraryBook class,
1006: RentalLog class, 1100: Screen example of library database class, 1200: Classification definition information, 1300: Event handler implementation file,
1400: Class characteristic display example 1500: Screen characteristic display example

────────────────────────────────────────────────── ─── Continuation of the front page (56) References JP-A-6-124197 (JP, A) JP-A-4-181426 (JP, A) (58) Fields investigated (Int. Cl. ⁷ , DB name) G06F 9/44

Claims (1)

(57) [Claim 1] A method for extracting user interface design support information for extracting information for supporting the design of a user interface in the development of an object-oriented system from the system , wherein the system is used. from the contents of the source file of the class library that, class definition information of the object in the class library, method implementation information, parts constituting the screen, and extracts the screen definition information describing an event handler caused by the input of the user, As a Classifying the class operation by the extracted method, recognizing the class operation pattern by the screen, and extracting and outputting the user interface design support information that derives the correspondence between the screen and the class. Extraction of interface design support information Method.