JPH08263276A - Software specification preparation support system - Google Patents

Abstract

PURPOSE: To provide a preparation software specification support system to be used for preparing specifications which is shown to a customer by SE. CONSTITUTION: Inputted customer's information and project information are accumulated in a specification file 201 in the shape of the document of a fixed format. A word list data base which is not shown in figure is attached to this system. Each word in the word list data base is given a category to which the word belongs to. From this word list data base, a word which belongs to the category is segmented and stored in a word list data base 203 for customers. Through the use of the segmented word list data base for customers, the system executes picture layout design, slip layout design and file layout design. After designing, they are inputted to the specification file. Words corrected by the word list data base 203 for customers are merged in the word list data base.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software specification creation support system using a computer, which is used when creating a software specification necessary for developing an application program.

[0002]

2. Description of the Related Art Conventionally, a support system for developing an application program is CASE (Computer Ai
ded Software Engineering), various systems have been developed. However, most of them were used for detailed design, coding, debugging, and testing of software directly related to programming. Up to now, the support system for specification creation for program creation, which is the upstream part of software, has not been developed so far.

[0003]

The creation of the software specifications has been handled by the work that is the object of system development and the SE (System Engineer) who is familiar with software development. However, the number of skilled SEs is very small compared to the number of application programs to be developed, and the labor cost of skilled SEs is very high. For this reason, a software specification creation support system in which skilled SE know-how is systematized is desired.

[0004] Now, the most problematic issue when creating a specification is how to grasp the business system intended by the customer and to quickly create a specification that incorporates a request for it. If this specification is not fixed, the actual system construction work (for example, program creation) cannot be started. This requires sufficient discussions with customers, but lacks knowledge of computer systems and lack of SEs who are familiar with the business that is the subject of system development. It was a meeting with an SE who had insufficient business knowledge, and often the specifications were not fixed or the specifications were changed just before completion.

With respect to business software specifications, if a document including mainly a file structure and a display screen can be created, there is often no difference in specifications between the customer and the customer.

[0006] In particular, the form is a product of the software for the business, and it is necessary to perform it especially while confirming the intention of the customer. Until now, such confirmations have often been made by handwritten documents or, at best, created by a word processor. For this reason, it took time to confirm the specifications, and the confirmation materials could not be directly used for programming.

An object of the present invention is to provide this software specification creation support system.

An object of the present invention is to provide a software specification creation support system in which business requirements are taken in, SE know-how is accumulated, and the system becomes an expert while being used during software development. .

Further, the present invention provides a software specification creation support system that can easily create a prototype of a program and that leads to automatic creation of a program.

[0010]

To achieve the above object, the present invention provides a word list database storing data items classified into categories, a specification file storing specifications in the form of a document, and a customer-specific file. A word list database, an FD management database for customers, and a project management file, means for inputting customer information and project information, and storing in the specification file and the project management file; and the inputted customer information and project A category is defined from the information, and means for storing the data items classified into the category from the word list database in the customer word list database, and the customer word list database are used.
A means for creating a screen layout, a form layout, and a file layout, and storing it in a specification file and a customer FD management database, and a function diagram as an input / output between the created screen, form, and file, and creating the function diagram. A software specification creation support system having means for storing in a specification file and a project management file.

[0011]

By using the software specification creation support system of the present invention, even a SE with little experience can easily and quickly create specifications for use in a meeting with a customer regarding the work content to be developed. , Based on this, we can discuss about the system to be fully developed.

Therefore, the specifications can be solidified quickly,
In addition, there are few changes in specifications. Moreover, based on the screen layout created during the specification creation, the form layout, etc., it is possible to output a code or the like that can be used for subsequent program creation and the like.

[0013]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a functional schematic diagram for explaining the function of the software specification creation support system of the present invention.
In the software specification creation support system of the present invention, first, information about a customer who develops is input (10
1). At that time, enter a general category of the customer.
The category input at this time is, for example, the type of business to which this customer belongs (retail business (supermarket, clothes, etc.), wholesale business, etc.). Also, at this time, various information of the customer (organization, etc.)
Can also be entered.

Next, the outline of the project (purpose, development period,
(Budget, etc.) and the work of the customer who is the target of systematization are specified (121). This is purchasing / inventory management, financial management, sales management, etc. The tasks subject to this systemization are also part of the category.

Data to be systematized from the word list (WL) / database (DB) attached to this specification creating system using the category of the business type and the category of the business to be systematized that were input earlier. A word as an item is cut out (122). This database and words will be explained in detail later.

Now, the system definition will be described. This is the so-called SE, which is the main function of creating specifications. First, the hardware / software configuration, which is a prerequisite for system development, is determined (132). Here, what kind of hardware (mainframe, workstation, personal computer, etc.)
Decide whether to proceed with system development under the conditions of. Also,
The OS (UNIX, DOS, Windows, etc.), the language used (FORTRAN, COBOL, C, etc.), and the compiler are also determined here.

Next, the functions, screen layouts,
Decide the form layout and file layout (13
4-137). When creating screen layouts and form layouts, also output in a format that can be used for program creation. These will be described in detail later.

As described above, by inputting the items required for preparing the specification sheet in order, the specification sheet in a proper format can be prepared. Based on this, by having meetings with the customer repeatedly, it becomes easy to grasp the customer's intention, the specification is solidified quickly, and the specification is not changed.

Next, the software specification creation support system of the present invention will be described in detail with reference to FIGS. FIG. 2 is a diagram illustrating the configuration of the software specification creation support system. In this software specification creation support system, the input customer information and project information are accumulated in the specification file 201 in the form of a document of a fixed format, and the version is controlled, and the latest version is the same for all persons in charge of this project. Can be viewed. Then, the project information that does not fit in the specification file of this fixed format is input to the project management file 204 and managed. Data for budget management, project progress management, project personnel management, and the like are input to the project management file. Access to this file is restricted and can only be accessed by each administrator.

Now, the specification creation based on the word list, which is the central function of the software specification creation support system of the present invention, will be described. Although not shown in FIG. 2, the wordlist database described below is attached to the system. Then, each word in the word list database is given a category to which the word belongs. This category is determined by the type of business and business for which the system is developed. A category is automatically determined by inputting the customer's business type and system development target business into this system, and words belonging to that category are cut out from this word list database, and the customer word list database (203)
Stored in. This word corresponds to the data item to be processed in the system to be developed. In this word, normal attributes (numbers, letters, etc.) and the number of digits are also defined by default. What's more, this word also has an alphabetic name that can be used in the program by default.

By using the cut-out customer word list database, screen layout design, form layout design, and file layout design are performed. These can be easily done because they are designed using the terms prepared in the word list. This will be described with reference to FIG. FIG. 3 illustrates a case where screen layout is performed. In this figure, when a screen layout is performed, the screen layout is used as an input screen. Then, select from the customer word list and select each item (for example, date,
Paste the product number etc. on the screen. Then, the screen as shown in FIG. 3A can be created by the attribute of each item.
This screen configuration is stored in the customer FD management database 202 and the specification file 201. At the same time, as the code that can be used for the program that represents this screen configuration,
What is shown in FIG. 3B can also be output. This is also stored in the customer FD management database. this is,
It can be used when creating a program. FIG.
Although (b)) shows an example of COBOL, it can be output in a designated programming language. The specification file 201 can be stored only in the display format of the screen itself.

In this way, the form layout and file layout can also be created. All of these layouts are stored in the customer FD management database and the specification database. Next, the function is determined by defining these screens, forms, and input / output between files.
This is shown in the functional diagram 211. This also uses the defined screens, forms, and files on the screen to display the functions between the input and output in the form of a tree. This display form can be set to nourishment. Then, it is possible to add or modify the display form as it is. Each function thus defined is also stored in the specification file in a fixed format.

By automatically setting the word list in this way, even if you are not familiar with the work in charge of development, you can make a draft of the specifications used for meetings with customers. From such meetings, detailed system decisions can be made. By modifying this draft, the specifications are created while modifying the customer word list, the customer FD management database, the specification file, and the like. Then, when the meeting with the customer is finally completed, the final specifications are completed. In this way, since the meeting is conducted while looking at the actual screen and the form, the specifications are set quickly, and moreover,
There is no change in specifications. The specification file allows all project personnel to view the specifications online, which is useful for communication among project personnel. In addition, the screen layout created at the stage of creating specifications can be output in a format that can be used for creating programs.

Now, maintenance of the word list database will be described with reference to FIG. When the specifications for the system corresponding to each customer are decided, the word list corresponding to the customer is completed in the customer word list database. It needs to be merged into the original wordlist database. By doing this, the word list database is enriched as the word list database is developed in various systems, and the next system development becomes easy. Of course, the function of registration correction necessary for normal maintenance of this word list database is naturally provided.

[0026]

As described above, when the software specification creation support system of the present invention is used, even for an SE with little experience, the specifications for using the software specification creation support system can be provided even when the customer has a meeting with the customer. It can be easily and quickly created, and on the basis of this, a sufficiently developed system can be discussed.

Therefore, specifications can be solidified quickly,
In addition, there are few changes in specifications. Moreover, based on the screen layout created during the specification creation, the form layout, etc., it is possible to output a code or the like that can be used for subsequent program creation and the like.

[Brief description of drawings]

FIG. 1 is a functional explanatory diagram of a software specification creation support system of the present invention.

FIG. 2 is a diagram illustrating a configuration of a software specification creation support system.

FIG. 3 is a diagram illustrating a screen layout design and its output.

FIG. 4 is a diagram for explaining maintenance of a word list database used in the present invention.

Claims (1)

[Claims] 1. A word list database storing data items classified into categories, a specification file storing specifications in the form of a document, a customer word list database, a customer FD management database and project management. A means for inputting customer information and project information and storing them in the specification file and the project management file; and defining a category from the inputted customer information and project information, and selecting the category from the word list database. Create a screen layout, form layout, and file layout using the word list database for customers and the means for storing the data items classified into categories in the customer word list database, and use it for the specification file and customer FD management data Software specification creation characterized by having means for storing in the base and means for creating a functional diagram as input / output between the created screen, form, and file, and storing it in a specification file and project management file Support system.