WO2017064832A1 - Service system design assistance system, service system design assistance method, and service system design assistance program - Google Patents

Abstract

Provided is a service system design assistance system which derives features to be re-examined in an architecture in relation to a change in a quality requirement which is associated with a functional requirement in connection with a change in a stakeholder requirement. This design system for a service system is provided with: a requirement separation means for accepting registration of a stakeholder requirement for a service system to be designed, separating the stakeholder requirement into a functional requirement and a quality characteristic in a classification of characteristics for quality characteristic information; a requirement quality fulfillment condition registration means for referencing architecture information and accepting registration of a combination of functions of constituent elements that contributes to achieving a quality characteristic that can be linked to a registered functional requirement; and a change assistance information derivation means for retaining associations of quality characteristics which can be changed in relation to functional requirements, and, when a registered quality characteristic is changed to another quality characteristic which can be set, referring to the quality fulfillment conditions to identify a combination of functions which has contributed to the achievement of the pre-change quality requirement so as to derive features to be reexamined in the architecture.

Description

Service system design support system, design support method, and design support program

The present invention relates to a computer system, and to a technique for supporting the derivation of a design solution that satisfies a stakeholder requirement for a service system.

IT (Information Technology) service system (hereinafter referred to as "system") development, the system architecture is designed to meet the needs of various stakeholders (stakeholders) such as customers, developers and maintenance personnel. The system architecture here indicates the configuration (structure) of the computer equipment constituting the system, the personnel allocation, the operation policy, and the like.

Stakeholder requirements for IT service systems are generally categorized as functional requirements and non-functional requirements. The function request represents a request related to a function (system behavior) provided by the system. The non-functional request represents a general request other than the function. Non-functional requirements are often requirements on system quality such as performance, availability, ease of use, and security, and are design constraints caused by technical and business reasons.

Non-functional requirements, especially quality requirements, are satisfied not only by combining the functions of individual elements such as devices, software, and Web (World Wide Web) products that make up the system, but also by appropriately combining those elements without excess or deficiency. Is done. For this reason, the system designer is required to have a high ability to verify whether non-functional requirements are properly satisfied at the design stage before the system is actually constructed and introduced.

Also, the types of non-functional requirements to be satisfied and the priority of non-functional requirements change depending on factors such as system usage conditions and linkage with external systems. For this reason, the system designer needs to design an appropriate architecture in consideration of the environment in which the system is used and future trends.

At present, in general, the relationship between non-functional requirements and the architecture to be built is not explicitly stated in the specifications such as requirement definition documents and various design documents. For this reason, in many cases, system designers interpret non-functional requirements implicitly included in requirement definitions and various design documents based on experience and customs and reflect them in the design. As a result, the derivation of the architecture design solution is influenced by the individual person in charge of development (system designer).

Patent Document 1 and Patent Document 2 can be cited as technologies related to computer system architecture design.

Patent Document 1 discloses a software design requirement extraction support method for extracting risk items and countermeasures for realizing non-functional requirements while considering functional requirements and architecture characteristics and presenting the results to the system designer. In this software design requirement extraction support method, not only functional requirements but also non-functional requirements are reflected as the basis of design, and the system designer is supported so that it can flexibly respond to changes in the required specifications.

Patent Document 2 identifies other deliverables affected by the change in accordance with a change in a software development deliverable (for example, a requirement description document, a design model, and a program code), and notifies the system designer. A development support apparatus is disclosed. This development support device retains tag information that defines the correspondence between deliverables created at each stage of the development process. Other development products affected by the modification of a certain product Software development is supported by tracing back the tag information starting from the object and identifying it retroactively.

Japanese Patent No. 3887571 JP 2007-122135 A JP 2010-066955 A

As mentioned above, at present, the relationship between non-functional requirements and the architecture to be built is not explicitly specified in specifications such as requirement definition documents and various design documents. For this reason, in many cases, system designers interpret non-functional requirements implicitly included in requirement definitions and various design documents based on experience and customs and reflect them in the design.

For example, when reusing existing architecture information in multiple projects, the ability of individual designers is demonstrated to identify the parts that should be changed due to differences in the system usage environment. Further, for example, when trying to construct and introduce a system by using existing architecture information that does not meet non-functional requirements, the designer's extraordinary ability is required. In addition, if a system is built with an architecture that does not meet non-functional requirements, a serious failure or incident may be caused. As a technique for solving these problems, it is desired to derive an architecture design solution by weakening the influence of individual designers.

Patent Document 1 and Patent Document 2 cannot solve an architecture design method based on non-functional requirements and the relationship between architectures to be constructed.

For example, in the technique of Patent Document 1, the risk items that have been extracted and the countermeasures are taken into consideration, and the final part of which part of the architecture should be changed in accordance with the process of designing the software architecture and the specification change. Judgment is personally made by the designer.

Further, in the method of Patent Document 2, although the design model affected by the modification to the requirement description document and the document itself can be traced and notified to the designer, the designer can specifically determine which part of the architecture the influence of the modification is. I can't know what happens to you.

A non-functional request identified from a stakeholder request is realized by combining various functions of system components (for example, a computer, a server, a cloud resource, and a network device). When such non-functional requirements related to quality that have a cross-sectional impact within the architecture are changed, an overall review of the architecture is required.

The inventor examines a method for automatically determining a design location that needs to be reviewed in the architecture for a change in quality requirements (quality requirements) from stakeholders that cause cross-architecture influences.

For this reason, for example, it can be expected to promote reuse of existing architecture information for projects that share the same functional requirements but have different required quality levels due to differences in the system usage environment. In addition, it can be expected that the system design using the architecture information will reduce the risk of finding a result that does not conform to the stakeholder requirements.

The present invention has been made in view of the above background, and automatically determines an architectural design point that needs to be reviewed when a quality requirement accompanying a functional requirement is changed as a stakeholder requirement is changed. It is an object to provide a service system design support system, method, and program.

A service system design support system according to an embodiment of the present invention refers to quality characteristic information indicating a list of characteristics indicating the quality of a service system, and relates to a stakeholder request input to a design target service system. Request separation means for accepting registration by dividing the function request into quality characteristics by classification for each characteristic registered in the quality characteristic information, and the function that is exhibited in the connection relation of each component of the service system and each component Each component included as an attribute in the architecture information that contributes to the realization of quality characteristics that can be linked to the function request registered by the request separation means Requirement quality satisfaction condition registration means for accepting registration of function combinations, and with design changes regarding the function requirements When the quality characteristic associated with the function request registered in the request separation unit is changed to another quality characteristic that can be set, the quality characteristic changed is maintained. , Identifying a combination of functions that contributed to the realization of the quality request before the change with reference to a list of combinations of functions of each component registered in the required quality satisfaction condition registration unit, and the function request And a change support information deriving unit for deriving a review point of the function in the architecture that satisfies the quality characteristics after the change.

A service system design support method according to an embodiment of the present invention includes a function request and a list of characteristics indicating quality of a service system prepared in advance for a stakeholder request input to a design target service system. Shows the connection characteristics of each component of the design target service system prepared in advance and the function to be exhibited in each component. Refers to the architecture information including attributes, and satisfies the quality combination of the functions of each component included as attributes in the architecture information that contributes to the realization of quality characteristics that can be linked to the registered function requirements. Accepts as a condition, and holds in advance the association of quality characteristics that can be changed with design changes with respect to the functional requirements In addition, when the quality characteristic associated with the received function request is changed to another quality characteristic that can be set, each component registered as the quality satisfaction condition is changed for the changed quality characteristic. Identify the combination of functions that contributed to the realization of the quality requirement before the change by referring to the list of function combinations possessed, and derive the location to review the function in the architecture that satisfies the function requirement and the quality characteristics after the change It is characterized by that.

A service system design support program according to an embodiment of the present invention refers to a quality characteristic information indicating a list of characteristics indicating the quality of a service system, with respect to a design target service system. For the inputted stakeholder request, a request separating means for receiving registration by dividing into a function request and a quality characteristic for each characteristic registered in the quality characteristic information, and each component of the design target service system The architecture that contributes to the realization of quality characteristics that can be linked to the function request registered by the request separation means with reference to architecture information including a connection relationship and an attribute indicating a function to be exhibited in each component unit Requirement quality satisfaction condition that accepts registration of combination of functions of each component included as attribute in information Other quality characteristics capable of setting the quality characteristics associated with the function request registered by the request separating means while holding the association between the registration means and the quality characteristics that can be changed with a design change with respect to the function request For the changed quality characteristic, it contributes to the realization of the quality requirement before the change by referring to the list of function combinations possessed by each component registered in the required quality satisfaction condition registration means. The function combination is operated as a change support information deriving unit that identifies a combination of functions that has been used and derives a function review in the architecture that satisfies the function requirements and the quality characteristics after the change.

According to the present invention, a service system design support system, method, and program for automatically discriminating an architecture design location that needs to be reviewed when a quality requirement accompanying a functional requirement is changed in accordance with a change in a stakeholder requirement Can provide.

1 is a block diagram showing a service system design support system 1 according to an embodiment of the present invention. FIG. 3 is a flowchart illustrating an operation example of the design support system 1. It is a block diagram which shows the design support system 2 of the example of 1 structure which concerns on this invention. It is explanatory drawing which shows the example of quality characteristic information. It is explanatory drawing which shows the example of architecture information. It is explanatory drawing which illustrated visually the quality satisfaction condition list used with the design support system 2 of the example of 1 structure. It is a flowchart which illustrates a change assistance information generation process. It is another flowchart which illustrates a change assistance information generation process. It is explanatory drawing which showed the example of a display screen construction which showed the additional design location using the model figure. It is explanatory drawing which showed the example of a display screen construction which showed the review location using a model figure. It is explanatory drawing which showed the example of a display screen construction which showed the additional design location and the review location using a model figure.

[Embodiment]
Embodiments of the present invention will be described with reference to the drawings. In addition, the stakeholder of the following description includes the user who uses it indirectly besides the user who uses a service system directly. Examples of stakeholders include consumer users who directly enjoy services, business departments and management of client companies that use the system, information system departments of companies that are responsible for system operation and maintenance, and ICT (system design and development). Information and Communication Technology) vendors themselves. The stakeholder request is a request or request that a vendor accepts from a stakeholder in various positions to the service system.

FIG. 1 is a block diagram showing a service system design support system 1 according to an embodiment of the present invention. As illustrated, the design support system 1 includes a request separation unit 10, a required quality satisfaction condition registration unit 20, and a change support information derivation unit 30. The design support system 1 is constructed so as to be accessible to quality characteristic information and architecture information. FIG. 1 shows an example in which an internal database that holds quality characteristic information and architecture information is used in the design support system 1. These various types of information may be managed by an external database.

Quality characteristic information is a list in which quality characteristics (for example, availability, performance, security, etc.) that can serve as an index for measuring the quality level of various functions provided by the service system are classified. The quality characteristic information is used in, for example, a quality characteristic model defined in an international standard (ISO 9126), metrics of a non-functional requirement grade table (Non-Patent Document 1), and an architecture-centered design method (Non-Patent Document 2). It is desirable to follow the classification of quality characteristics. It is desirable to share quality characteristic information among designers. By sharing quality characteristic information among multiple designers, personality can be weakened. The design support system 1 accepts quality settings from the user. Quality is a classification of quality characteristics included in the quality characteristic information, and is required for the architecture of the design target service system in order to satisfy the quality requirements related to the function requirements.

Architecture information is information that models each component (computer equipment (server, storage, network switch, etc.) and human resources) constituting the design target service system and their connection relationship. The architecture information includes a single function of each component as an effective attribute, and the attribute is associated with each component. The function alone is a design parameter in the connection relationship between each component.

The request separation unit 10 refers to the registered quality characteristic information and accepts registration of a stakeholder request input to the design target service system from the user. Stakeholder requirements are divided into functional requirements and quality characteristics associated with the functional requirements. At this time, the request separation unit 10 receives a quality request associated with the function request from the user as a classification of quality characteristics registered in the quality characteristic information. The request separation unit 10 desirably presents a list (option) of quality characteristic information associated with the function request to the user. Note that a specific stakeholder request is described as an example in a configuration example described later. When there are a plurality of function requests for registering stakeholder requests, the request separation unit 10 desirably accepts registration of quality characteristics in association with individual function requests for each function request.

Here, the user who inputs the stakeholder request is assumed to be the designer of the service system. However, the stakeholder request may be separated and classified by the customer or the related party. Even in this case, a customer or the like can select a quality characteristic from the list of quality characteristic information, thereby preventing a stakeholder request and a service system to be designed.

In this embodiment, it is assumed that the non-functional requirements included in the stakeholder requirements are decomposed into quality requirements and constraints specified for each development target project. This restriction is assumed to be common (fixed) in the system before and after the change according to the technical level at the time of designing, the business situation, legal regulations, and the like, and is not included in the information processing in this embodiment. On the other hand, it is desirable to present constraints to the designer along with the architecture.

The required quality satisfaction condition registration unit 20 uses each attribute of each component registered in the architecture information as an option, and satisfies the quality satisfaction of each quality characteristic that can be linked to the function request registered by the request separation unit 10 from the user. Registration of combinations of attributes (functions) that satisfy the conditions is accepted. The combination can be registered by the user. When there are a plurality of function requests, the required quality satisfaction condition registration unit 20 accepts registration for combinations of attributes (functions) that satisfy the quality satisfaction conditions of each quality characteristic associated with each function request. The required quality satisfaction condition registration unit 20 holds and manages each input quality satisfaction condition. Further, the required quality satisfaction condition registration unit 20 records a combination of functions possessed by each component to contribute to the realization of quality characteristics that can be linked to a function request registered by the user. At this time, the quality satisfaction condition may be recorded including the connection relationship between the components.
It is desirable that this quality satisfaction condition is databased in association with the architecture information.

The required quality satisfaction condition registration unit 20 is configured to be able to present each component included in the architecture information, the attribute of each component, and the connection relationship of each component to the user via the model diagram image. It is desirable. Further, the required quality satisfaction condition registration unit 20 presents each component included in the architecture information, the attribute of each component, and the connection relationship of each component in table information or table information and a model diagram. Also good.

As described above, in the registration of the quality satisfaction condition of each quality characteristic by the user, each quality characteristic that can be linked to the function request registered by the request separation unit 10 is assigned to the configuration (architecture) of the service system. The required number of attributes of each component for obtaining quality characteristics is selected and linked.

The change support information deriving unit 30 holds the association of quality characteristics that can be changed with a design change or the like with respect to the function request registered in the request separating unit 10. It is desirable to maintain the association between the function request and the quality characteristic for each function request included in the stakeholder request. Further, the change support information deriving unit 30 changes the quality characteristic associated with the function request registered by the request separation unit 10 from the user according to the selectable quality request option to another quality characteristic according to the request from the user. Can be changed.

The changeable quality characteristic is associated with the required quality satisfaction condition registered in the required quality satisfaction condition registration unit 20. That is, the design support system 1 retains quality characteristic options that can be associated with the function request registered by the user, and accepts the change from the user. In addition, the design support system 1 holds a required quality satisfaction condition in advance for each quality characteristic that is an option.

The change support information deriving unit 30 refers to the quality satisfaction condition when the quality characteristic associated with the function request is changed by the user, and each component in the architecture for satisfying the function request and the changed quality characteristic Derivation process of the design part of the function to be given to. In this derivation process, combinations of functions that have contributed to the realization of the quality requirement before the change are searched from the quality satisfaction conditions, and the identified functional differences are collected in the change support information. In the change support information, differences in individual functions of the respective constituent elements accompanying the change in quality characteristics appear across the architecture.

The modification support information derivation unit 30 outputs the functional difference between the structural elements related to the service system before and after the derived modification in a recognizable manner in association with the description in which the architecture information is output as a model diagram. An output unit 34 may be provided. In addition, when there are a plurality of function requests input to the service system, it is desirable that the modified attribute candidate output unit 34 visually emphasizes and outputs the overlapping portions of the functional differences in the architecture. .

Suppose that the quality characteristics associated with a functional requirement are changed to other configurable quality characteristics. At this time, the change support information derivation unit 30 refers to the list of the combinations of the functions of each component registered as the quality satisfaction condition and the connection relationship regarding the change of the quality characteristic, and the connection relationship of each component It is desirable to identify the lacking part and the extra part on the quality satisfaction condition and include them in the change support information.

This change support information is notified to the user and the design system linked with this design support system as an architecture design location (function review location, additional design location) that needs to be reviewed in accordance with the change of the stakeholder request.

Thus, the service system design support system 1 is based on the function request and the quality characteristic input from the user when the quality request accompanying the function request changes in accordance with the change of the input stakeholder request. Thus, it is possible to automatically determine an architectural design point that needs to be reviewed.

Suppose, for example, that a certain quality characteristic is changed or added to a service system due to a certain stakeholder request. At this time, even when the design part that needs to be reviewed in accordance with the change has various effects, this automatic determination makes it easy to recognize a large number of design change parts. In particular, it is convenient to recognize that an extra function can be derived in the architecture.

This makes it easier to reuse existing architecture design information for multiple projects with different system usage environments and reduces the risk of non-compliance with requirements.

In the above embodiment, it has been described that the architecture information is already registered in the database. This architecture information may be input by the user when the design is changed. For this reason, it is desirable that the design support system 1 includes an architecture information definition unit 40 that receives input of architecture information. The architecture information defining unit 40 is preferably constructed so that it can accept input of architecture information on a model basis.

Further, the architecture information definition unit 40 may be configured to correspond to available components and functions of a cloud environment that provides a service system to be designed as a part that describes the architecture. This makes it easier to understand more specifically the functions of each component and the excess or deficiency of the resource amount associated with the design change of the cloud-based service system using cloud resources.

Next, an operation example of the design support system 1 will be described. The process of generating the change support information may be performed while appropriately going through each step, and is not limited to the illustrated flow. For example, while supplementing the lack of information until the database is enriched, the service system architecture should be reviewed based on non-functional requirements, such as when obtaining stakeholder requests, when changing stakeholder requests, and when reviewing the quality of service systems. It only has to be used. By executing the following process, each component and its function that are affected by the change in the quality characteristics of the system can be read from the change support information.

FIG. 2 is a flowchart showing an operation example of the design support system 1.

First, the design support system 1 accepts registration of quality characteristic information and architecture information in the database (S101). As the architecture information, existing architecture information may be selected from the database, and may be input at this point.

Next, the design support system 1 accepts the stakeholder request input to the design target service system by dividing it into a function request and a quality characteristic associated with the function request (S102). The type of quality request is selected from characteristics classifications in quality characteristic information registered in advance in the database.

Next, the design support system 1 accepts a combination of attributes (functions) of individual components of the architecture information as a quality satisfaction condition (S103). The architecture information contributes to the realization of each quality requirement that can be linked to the registered function requirement.

The preparatory steps from S101 to S103 can save labor by using past design information (registration of quality satisfaction conditions), and can weaken the personal influence of individual designers.

Next, it is assumed that the quality characteristic associated with the received function request is changed to another settable quality characteristic. At this time, the design support system 1 refers to the list of quality satisfaction conditions (combinations of functions of each component) for the changed quality characteristics, and the combination of functions that has contributed to the realization of the quality requirement before the change. Identify The design support system 1 derives a functional difference between architectural components related to the service system before and after the change as change support information (S104).

Finally, the design support system 1 presents the content of the derived change support information to the user (S105).

One or a plurality of design points on the architecture that are affected by the common architecture (components and connection relationships) when the stakeholder request (quality request) is changed by the change support process of S104 and S105. (Components and their functions) can be derived.

As described above, according to the present embodiment, the architecture design part that needs to be reviewed when the request is changed for the stakeholder request across the architecture realized by combining the functions of the system components. It can be automatically identified and presented to the designer.

有効 Effective use of this discrimination result promotes reuse of existing architecture design information and reduces the risk of nonconformity between stakeholder requirements and new architecture.

[Configuration example]
Next, the present invention will be described with reference to one configuration example.

FIG. 3 shows a service system design support system 2 showing an example of the configuration according to the present invention. The design support system 2 is assumed to operate in parallel with the existing design system on the same computer as the design system of the existing service system.

As shown in the figure, the design support system 2 of the present configuration example is configured to include a request separation unit 10, a required quality satisfaction condition registration unit 20, a change support information derivation unit 30, and an architecture information definition unit 40. . Further, the change support information deriving unit 30 includes a settable quality characteristic defining unit 31, a request changing unit 32, an impact analyzing unit 33, and a modified attribute candidate output unit 34. Various information received and generated information are associated with each other appropriately and stored in an internal / external database. Note that the database stores in advance a list of characteristics (quality characteristic information exemplified in FIG. 4A) that serve as an index of the quality level of various functions provided by the service system.

The request separation unit 10 receives an input of a stakeholder request for the service system to be designed, and separates it into a function request representing a request for system behavior and a quality request (quality characteristic) accompanying the function request. Regarding the quality characteristics, the request separation unit 10 presents the quality system options along the category included in the quality characteristic information to the service system designer and accepts the options.

In the following, as an example of a stakeholder request, the information system design contract used in a certain company is used for explanation. In this example, consider the construction of an in-house information system having a mechanism in which meeting materials are stored in a network-connected server and can be shared among the participants of the meeting. Here, it is assumed that the system vendor gives a request that “a stored conference material can be easily browsed without going through complicated procedures” as a stakeholder request.

This stakeholder request consists of a request for the function “view meeting materials” (the system behavior of “display meeting materials on participants' PC (Personal Computer) screens)” and a request “easy”. Has been. For this reason, the quality requirement linked to the function requirement of this system is “easy”, and “usability” of the quality characteristic information is selected by the designer as the quality characteristic on the input interface and registered in the design support system 2. The

The architecture information definition unit 40 receives design information such as components constituting the service system to be designed and their connection relations and attributes (functions that can be provided as a single unit), and models them into a database as architecture information. Record.

For example, as shown in FIG. 4B, this architecture information includes presence / absence (valid / invalid) of a component having an attribute (such as a load balancer in the figure) and a connection relationship of each component, as in various existing modeling languages. You may express using and. Each component is given an attribute indicating a function that can be provided alone (for example, load balancing for a load balancer, simple file sharing for a shared DB (Data Base) server, etc.). In the figure, only representative attributes are shown.

Also, when accepting design information, it is desirable to prepare in advance the components that can be parts so that they can be drawn in the same way as in various existing modeling languages. This makes it possible to save input and reduce personal influences. In addition, it is possible to provide an easy-to-use design support system by creating an input interface for architecture information so that individual components can be visually linked.

Attribute type is a function that can be a design parameter in a certain connection relationship among the functions of each component, and is defined in the architecture information (allows the user to register). For example, the shared DB server can have a function (automatic backup function) for automatically backing up stored data at a specified date and time, like a mail server. However, in this architecture, the constituent element (such as another storage server) serving as the backup destination is not connected to the shared DB server, so the attribute “automatic backup” is not validated for this shared server. In this way, the type of attribute to be assigned to each component is determined based on the connection state of each component.

This registration input interface is pre-assigned attributes (functions) that can be used for model diagram parts that are constituent elements, and can be used to delete (gray out) attributes that cannot be used due to the connection between constituent elements. It may be configured.

The architecture information shown in FIG. 4B expresses that the simple file sharing function works effectively as an attribute (function) of the shared DB server. With this simple file sharing function, the shared DB server can provide a mechanism for sharing folders and files among a plurality of arbitrary users on the network. The authentication server also has a “single sign-on” attribute.

This function of the shared DB server allows anyone to access a specific file, so part of “easier file sharing among conference participants” that is accepted as a quality request for stakeholder requests can be realized. Similarly, since various functions can be accessed with a single authentication by the function of the authentication server, a part of “easiness of file sharing among conference participants” that is accepted as a quality request of a stakeholder request can be realized.

By connecting and using these two components, the service system can be operated by linking the simple file sharing function of the shared DB server and the single sign-on function of the authentication server.

「By using the simple file sharing function and the single sign-on function of the authentication server, it is possible to realize“ easiness of file sharing among conference participants ”that is accepted as a quality request for stakeholders.

In this way, in addition to requests that can be realized by combining the functions of a single component, it is possible to respond to stakeholder requests that require each component to be properly connected.

This mechanism makes it possible to associate stakeholder requests realized by taking an appropriate architecture for the entire service system with the architecture information of the service system.

The required quality satisfaction condition registration unit 20 allows the designer to define attribute combinations (quality dependent condition information) that contribute to the realization of settable quality characteristics. If the quality dependent condition is already registered in the database, the quality dependent condition information may be used. The required quality satisfaction condition registration unit 20 has an input interface capable of selecting attributes of individual components on the screen showing the architecture information for combinations of attributes included in the quality dependent condition information. This input interface can save labor, and the user can select a combination satisfying the quality dependency condition while referring to the connection relation of the constituent elements, so that an error hardly occurs. In addition, the user can easily understand the architecture structure and quality characteristics visually when referring to quality subordinate conditions registered in the past on the screen.

For example, the quality characteristic related to “usability” (see FIG. 4A) can be realized by the simple file sharing function of the shared DB server and the single sign-on function of the authentication server in the architecture information of FIG. 4B. Therefore, for the quality characteristic “usability”, the user selects a combination of the “simple file sharing” attribute of the shared DB server and the “single sign-on” attribute of the authentication server.

Quality satisfaction condition information can be defined as table information as shown in FIG. 5, for example. In this example, the quality satisfaction conditions are defined as separate table information for each function request. However, the quality satisfaction condition information may be formed as a set of table information, and other database formats are adopted. May be. The defined quality satisfaction conditions are preferably stored in a database for sharing.

The change support information deriving unit 30 includes a settable quality characteristic defining unit 31, a request changing unit 32, an impact analyzing unit 33, and a modified attribute candidate output unit 34.

The settable quality characteristic defining unit 31 allows a service system designer, who is a user, to define quality characteristics. The quality characteristic is attached to the function request (separated and registered by the request separation unit 10) according to the options included in the quality characteristic information.

For example, in this definition, in response to the function request “multiple users view conference materials simultaneously”, in addition to the quality requirement related to “usability”, “high speed even when multiple users access conference materials simultaneously” (2), “only a specific authenticated user”, and “at any time period excluding the company-wide intensive vacation period” can be added. If these quality requirements are received, the quality characteristics related to “performance”, “security”, and “availability” in the quality characteristic information of FIG. 4A are linked to the function requirements.

On the other hand, the above functional requirements are not related to the operational cost after system introduction, ease of maintenance, etc., and are not linked to the quality characteristic of “operational maintainability”.

The request change unit 32 receives a change input of a quality characteristic associated with an arbitrary function request from a service system designer. The input interface of the request change unit 32 is configured to be able to change the quality request of the quality characteristic included in the settable quality characteristic (defined by the settable quality characteristic definition unit 31) associated with the selected function request.

For example, for a service system constructed with the architecture information in FIG. 4B, “assuming a usage environment that is accessed from an external network to view conference materials from outside the office”. In this case, the quality characteristic is changed to “security” that should be given priority over “usability” defined in association with the function request. Note that “security” is included in the quality characteristic information that “only the conference participant (a user who has been correctly authenticated) can view the stored conference material”.

The impact analysis unit 33 extracts, for each function request, a combination of attributes (pre-change quality satisfaction conditions) that contribute to the realization of the quality characteristics before the change in the request change unit 32 from the quality satisfaction condition list. Further, the influence analysis unit 33 extracts a combination of attributes (post-change quality satisfaction condition) that contributes to the realization of the post-change quality characteristics as necessary, and determines an affected function (component attribute). The impact analysis unit 33 executes a change support information generation process, for example, as illustrated in the flowcharts of FIGS.

For example, in the flow example of FIG. 7, when the quality request associated with the function request 1 “view conference material” is changed to “security”, the quality characteristics associated with the function request before the change. Two attributes (“simple file sharing” and “single sign-on”) that have contributed to the realization of “usability” are extracted from the quality satisfaction condition (see FIG. 5). Similarly, two attributes (“encryption” and “user authentication”) that contribute to the realization of “security” after the change are extracted from the quality satisfaction condition (see FIG. 5). The functional difference between the architectural components related to the service system before and after the change is derived as change support information.

The modified attribute candidate output unit 34 refers to the change support information and visually presents the constituent elements and attributes extracted by the impact analysis unit 33 to the designer as a model diagram using the architecture information.

When the modified attribute candidate output unit 34 handles a plurality of function requests, the modified attribute candidate output unit 34 identifies the location used to realize the quality requirements before the change of all the function requests with respect to the attribute of a certain quality request changed. Present the architecture design after the change so that it can be identified. At this time, an overlapping portion of an architectural difference that may be particularly required may be visually highlighted.

FIG. 8A, FIG. 8B, and FIG. 9 are explanatory diagrams showing an example of display screen construction using a model diagram presented to the user. FIG. 8A shows a screen depiction showing the additional design location included in the change support information when the quality characteristic given to a certain function request is changed from “availability” to “security” for the architecture shown in FIG. 4B. It is shown. Similarly, FIG. 8B shows the revised parts included in the change support information when the quality characteristic given to a certain function request is changed from “availability” to “security” for the architecture shown in FIG. 4B. A screen depiction is shown. Similarly, FIG. 9 shows the design location and stakeholder requirements included in the change support information when the quality characteristic given to a certain function request is changed from “availability” to “security” for the architecture shown in FIG. 4B. A screen depiction showing is shown.

As shown in FIG. 9, it is desirable that stakeholder requirements, function requirements, and quality requirements can be presented together with the service system architecture. Also, constraints related to stakeholder requirements may be presented along with the service system architecture.

As described above, the service system design support system to which the present invention is applied automatically changes the architectural design point that needs to be reviewed when the quality requirement accompanying the functional requirement is changed in accordance with the change of the stakeholder requirement. It becomes possible to discriminate.

In addition, what is necessary is just to implement | achieve each part of a design support system using the combination of the hardware and software of a computer system. The computer system includes one or more processors, a memory, an input unit, an output unit, and a bus according to a desired configuration. In the form of this computer system, each unit has a design support program developed in the memory, and based on this program, hardware such as one or a plurality of processors is operated by an execution instruction group or a code group. Realize it. At this time, this program may realize each unit in cooperation with functions provided by software such as an operating system, a microprogram, and a driver, as necessary.

The program data developed in the memory appropriately includes an execution instruction group, a code group, a table file, content data, and the like that cause the processor to operate as one or more of the above-described units.

In addition, this computer system does not necessarily need to be constructed as a single device, and is constructed by so-called thin clients, distributed computing, or cloud computing by combining a plurality of servers / computers / virtual machines. Also good. In addition, this computer system replaces part or all of the computer system with hardware and firmware (for example, one or more LSIs: Large-Scale Integration, FPGA: Field Programmable Gate Array, a combination of electronic elements). Similarly, only a part of each unit may be replaced with hardware or firmware.

Further, this program may be recorded on a recording medium non-temporarily and distributed. The program recorded on the recording medium is read into the memory via wired, wireless, or the recording medium itself, and operates a processor or the like.

In this specification, the recording medium includes a storage medium, a memory device, a storage device, and the like having similar terms. Examples of this recording medium include an optical disk, a magnetic disk, a semiconductor memory device, a hard disk device, and a tape medium. The recording medium is desirably non-volatile. The recording medium may use a combination of a volatile module (for example, RAM: Random Access Memory) and a nonvolatile module (for example, ROM: Read Only Memory).

The above form will be described with another expression. The processor that operates as the design support system is based on the design support program expanded in the memory. The request separation means, the required quality satisfaction condition registration means, the change support information derivation means, the configurable quality characteristic definition means, the request change means, and the influence Operates as analysis means and correction attribute candidate output means. As a result, a design support system can be realized.

Similarly, to describe the above-described form in another expression, the recording medium includes a design support program that is expanded in a memory and operates on an information processing resource. By executing it, a design support system can be constructed.

Note that the present invention has been described by exemplifying embodiments and / or configuration examples. However, the specific configuration of the present invention is not limited to the above-described embodiment, and modifications within a range not departing from the gist of the present invention are included in the present invention. For example, changes such as separation / merging of block configurations and replacement of procedures in the above-described embodiments and / or examples are free as long as they satisfy the gist of the present invention and the functions described, and the above description limits the present invention. is not.

In addition, a part or all of the above-described embodiments can be described as follows. Note that the following supplementary notes do not limit the present invention.
[Appendix 1]
With reference to the quality characteristic information indicating a list of characteristics indicating the quality of the service system, regarding the stakeholder request input to the design target service system, the function request and the characteristics registered in the quality characteristic information for each characteristic. Request separation means for accepting registration divided into quality characteristics by category,
With reference to the architecture information including the connection relationship of each component of the service system and the attribute indicating the function to be exhibited in each component, the quality characteristic that can be linked to the function request registered by the request separation unit Required quality satisfaction condition registration means for accepting registration of a combination of functions of each component included as an attribute in the architecture information that contributes to realization;
The association of the quality characteristic that can be changed with the design change with respect to the function request is maintained, and the quality characteristic associated with the function request registered by the request separation unit is changed to another quality characteristic that can be set. At this time, with respect to the changed quality characteristic, the function contributing to the realization of the quality requirement before the change is referred to by referring to the list of the combinations of the functions of each component registered in the required quality satisfaction condition registration unit. Change support information deriving means for identifying a combination and deriving a function review in the architecture that satisfies the function requirements and the quality characteristics after the change;
A service system design support system comprising:

[Appendix 2]
The change support information derivation means includes:
The association of the quality characteristic that can be changed with the design change with respect to the function request is maintained, and the quality characteristic associated with the function request registered by the request separation unit is changed to another quality characteristic that can be set. At this time, with respect to the changed quality characteristic, the function that has contributed to the realization of the quality requirement after the change by referring to the list of the function combinations of each component registered in the required quality satisfaction condition registration unit Identifying combinations and deriving additional design locations for the functions in the architecture that meet the functional requirements and quality characteristics after the changes;
A service system design support system as described in the above supplementary note.

[Appendix 3]
The request separation means accepts registration of quality characteristics in association with individual function requests for each function request for registration of stakeholder requests input to the service system to be designed,
The change support information deriving means is configured to change all the function requests with respect to the changed attribute of the certain quality request when the certain quality characteristic associated with each function request is changed to another settable quality characteristic. The service system described in the above supplementary note is characterized in that the part used for realizing the quality characteristics before the change is identified, and the difference in the architectural components related to the service system before and after the change is derived. Design support system.

[Appendix 4]
A modification attribute candidate output means for recognizing in the model diagram the functional difference between the structural elements related to the service system before and after the change derived by the change support information deriving means;
The modified attribute candidate output means outputs the overlapping part of the functional difference between the structural elements in the architecture when there are a plurality of function requests input to the service system in a visually recognizable manner. A service system design support system as described in the above supplementary note.

[Appendix 5]
The change support information derivation means includes:
Settable quality characteristic defining means for accepting a quality characteristic that can be changed with a design change with respect to the function request;
Request changing means for receiving an input for changing the quality characteristic associated with the function request registered by the request separating means to another settable quality characteristic received by the settable quality characteristic defining means;
Concerning the quality characteristics changed by the requirement changing means, it contributed to the realization of quality requirements before and after the change by referring to the list of function combinations possessed by each component registered by the required quality satisfaction condition registration means An impact analysis means for identifying a combination of functions and generating information that shows a difference in function of each structural element related to the service system before and after the change as change support information;
The supplementary note is characterized in that it is composed of modified attribute candidate output means for referring to the change support information and reflecting the attribute extracted by the impact analysis means in architecture information and outputting it as a model diagram. The service system design support system described.

[Appendix 6]
The architecture information includes connection information that is a design parameter of the service system in a specific connection relationship of each component among the functions of each component,
The required quality satisfaction condition registration means includes a combination of functions of each component that contributes to the realization of quality characteristics that can be linked to the function request registered by the user, and includes a connection relationship between the components. Record satisfaction conditions,
The change support information deriving unit is configured to register each configuration registered as the quality satisfaction condition regarding the change of the quality characteristic when the quality characteristic associated with the function request is changed to another quality characteristic that can be set. Refer to the list of combinations of functions of elements and their connection relations, identify the missing parts and / or extra parts in the satisfying conditions of the connection relations of each component, and the architecture related to the service system before and after the change A service system design support system as described in the above supplementary note, wherein a difference in connection relation between the constituent elements is derived.

[Appendix 7]
The service system design support system according to the above supplementary note, further comprising architecture information defining means for accepting input of the architecture information on a model basis.

[Appendix 8]
The architecture information defining means accepts, as architecture information, a model-based component and a function performed in each component corresponding to a component and a function that can be provided in a cloud environment that provides a service system to be designed,
The change support information deriving unit derives, for the changed quality characteristic, an architectural difference related to the cloud-based service system before and after the change in correspondence with the components and functions of the cloud environment. Service system design support system described in the appendix.

[Appendix 9]
With reference to the quality characteristic information indicating a list of characteristics indicating the quality of the service system from the input unit of the computer system, the stakeholder request input to the design target service system is included in the function request and the quality characteristic information. A first input interface that accepts registration for each function request divided into quality characteristics by category for each registered characteristic;
The function registered in the first input interface with reference to the architecture information recorded in the database and including the connection relation of each component of the service system and the attribute indicating the function to be exhibited in each component A second input interface that contributes to the realization of a quality characteristic that can be associated with a request, and that accepts registration of a function combination of each component included as an attribute in the architecture information for each function request from the input unit;
A processing resource of the computer system maintains an association of quality characteristics that can be changed with a design change with respect to the function request, and a quality characteristic associated with each function request registered in the first input interface When the quality characteristic is changed to another quality characteristic that can be set, all of the changed quality characteristic is referred to with reference to a list of combinations of functions possessed by each component registered in the second input interface. Identifying the combination of functions that contributed to the realization of the quality requirements before the change of the functional requirements of the system, and deriving the review points of the functions in the architecture that satisfy the functional requirements and the quality characteristics after the change. An output interface configured to be able to output from the output unit is provided. Design support system of screws system.

[Appendix 10]
A third input interface that receives the architecture information on a model basis via the input unit;
The third input interface accepts, as the architecture information, a model-based component and a function performed in each component corresponding to a component and a function that can be provided in a cloud environment that provides a service system to be designed. The service system design support system according to the above supplementary note, which is recorded in the database.

[Appendix 11]
For the stakeholder requirements entered for the service system to be designed, the quality characteristics are classified according to the characteristics registered in the quality characteristics information indicating the list of characteristics indicating the functional requirements and the quality of the service system prepared in advance. Accepted separately,
It is possible to link to the registered function request by referring to architecture information including a connection relation of each component of the service system to be designed prepared in advance and an attribute indicating a function to be exhibited in each component. Accepts as a quality satisfaction condition a combination of functions of each component included as an attribute in the architecture information that contributes to the realization of quality characteristics, and holds in advance the association of quality characteristics that can be changed with design changes for the function requirements In addition, when the quality characteristic associated with the received function request is changed to another quality characteristic that can be set, each component registered as the quality satisfaction condition is changed for the changed quality characteristic. Identify the combination of functions that contributed to fulfilling the quality requirements before the change by referring to the list of function combinations And a service system design support method by an information processing system, wherein a function review in the architecture that satisfies the function requirements and the quality characteristics after the change is derived.

[Appendix 12]
The information processing system includes:
It retains the association of quality characteristics that can be changed with a design change with respect to the function request, and is changed when the quality characteristic associated with the registered function request is changed to another quality characteristic that can be set. With respect to the quality characteristics, the combination of functions that contributed to the realization of the quality requirement after the change is identified with reference to the list of combinations of the functions of each registered component, and the function requirement and the quality after the change A design support method for a service system as described in the above supplementary note, wherein an additional design location of a function in the architecture satisfying the characteristics is derived.

[Appendix 13]
The information processing system includes:
Regarding the registration of stakeholder requests that are input to the service system to be designed, for each function request, accept registration of quality characteristics in association with each function request,
When a certain quality characteristic associated with an individual functional requirement is changed to another configurable quality characteristic, the quality characteristic before the change of all functional requirements is realized with respect to the changed attribute of the certain quality requirement The service system design support method according to the above supplementary note, characterized in that a part used in the process is identified and a difference in architectural components related to the service system before and after the change is derived.

[Appendix 14]
The information processing system includes:
The service system design support method according to the above supplementary note, characterized in that the functional difference between the architectural components related to the service system before and after the derived change is recognizable in the model diagram.

[Appendix 15]
The information processing system includes:
The service system according to the above supplementary note, wherein when there are a plurality of function requests input to the service system, an overlapping part of a functional difference between architectural components is output in a visually recognizable manner. Design support method.

[Appendix 16]
The architecture information includes connection information that is a design parameter of the service system in a specific connection relationship of each component among the functions of each component,
The information processing system includes:
Record the quality satisfaction condition including the connection relationship between the components together with the combination of the functions that each component contributes to the realization of quality characteristics that can be linked to the function request registered by the user,
When the quality characteristic associated with the function request is changed to another quality characteristic that can be set, regarding the change of the quality characteristic, the combination of the functions of each component registered as the quality satisfaction condition and its Refer to the list of connection relationships, identify the shortage and / or extra points in the satisfaction condition of the connection relationship of each component, and the difference in the connection relationship of the architectural components related to the service system before and after the change The service system design support method according to the above supplementary note, wherein the derivation process is performed.

[Appendix 17]
The information processing system accepts input of the architecture information on a model basis via an input unit, and the service system design support method according to the above supplementary note.

[Appendix 18]
The information processing system includes:
Accepts model-based components and functions that are performed by each component as architecture information corresponding to the components and functions that can be provided in the cloud environment that provides the service system to be designed.
For the changed quality characteristics, architectural differences related to the cloud-based service system before and after the change are derived corresponding to the components and functions of the cloud environment, and the service system design support described in the above supplementary note Method.

[Appendix 19]
The processor of the information processing system,
With reference to the quality characteristic information indicating a list of characteristics indicating the quality of the service system, regarding the stakeholder request input to the design target service system, the function request and the characteristics registered in the quality characteristic information for each characteristic. Request separation means for accepting registration divided into quality characteristics by category,
It can be linked to the function request registered by the request separation means with reference to architecture information including the connection relationship of each component of the design target service system and the attribute indicating the function to be exhibited in each component unit. Required quality satisfaction condition registration means for accepting registration of a combination of functions of each component included as an attribute in the architecture information, which contributes to realizing quality characteristics;
The association of the quality characteristic that can be changed with the design change with respect to the function request is maintained, and the quality characteristic associated with the function request registered by the request separation unit is changed to another quality characteristic that can be set. At this time, with respect to the changed quality characteristic, the function contributing to the realization of the quality requirement before the change is referred to by referring to the list of the combinations of the functions of each component registered in the required quality satisfaction condition registration unit. Change support information deriving means for identifying a combination and deriving a function review in the architecture that satisfies the function requirements and the quality characteristics after the change;
A service system design support program characterized by operating as

[Appendix 20]
The change support information deriving means,
The association of the quality characteristic that can be changed with the design change with respect to the function request is maintained, and the quality characteristic associated with the function request registered by the request separation unit is changed to another quality characteristic that can be set. At this time, with respect to the changed quality characteristic, the function that has contributed to the realization of the quality requirement after the change by referring to the list of the function combinations of each component registered in the required quality satisfaction condition registration unit The service system design support program according to the above supplementary note, wherein the program is operated so as to identify a combination and derive an additional design portion of the function in the architecture satisfying the function requirement and the quality characteristic after the change.

[Appendix 21]
The request separation means accepts registration of quality characteristics in association with individual function requests for each function request for registration of stakeholder requests input to the service system to be designed,
When the change support information derivation means is changed to another quality characteristic that can set a certain quality characteristic associated with each function request, all the function requests are related to the changed attribute of the quality request. The above remark is characterized in that the part used for realizing the quality characteristic before the change of the system is identified and the difference between the architectural components related to the service system before and after the change is derived and processed. Service system design support program.

[Appendix 22]
The processor;
Operate as a modified attribute candidate output means for recognizing in the model diagram functional differences of architectural components related to the service system before and after the change derived by the change support information deriving means,
The correction attribute candidate output means operates so as to output a visually recognizable portion where there is a difference in function of an architectural component when there are a plurality of function requests input to the service system. A service system design support program as described in the above supplementary note.

[Appendix 23]
The processor;
As the change support information derivation means,
Settable quality characteristic defining means for accepting a quality characteristic that can be changed with a design change with respect to the function request;
Request changing means for receiving an input for changing the quality characteristic associated with the function request registered by the request separating means to another settable quality characteristic received by the settable quality characteristic defining means;
Concerning the quality characteristics changed by the requirement changing means, it contributed to the realization of quality requirements before and after the change by referring to the list of function combinations possessed by each component registered by the required quality satisfaction condition registration means An impact analysis means for identifying a combination of functions and generating information that shows a difference in function of each structural element related to the service system before and after the change as change support information;
According to the above description, the modification support information is operated as a modified attribute candidate output unit that refers to the change support information and reflects the attribute extracted by the influence analysis unit in the architecture information and outputs it as a model diagram. Service system design support program.

[Appendix 24]
The architecture information includes connection information that is a design parameter of the service system in a specific connection relationship of each component among the functions of each component,
The required quality satisfaction condition registration means includes a combination of functions of each component that contributes to the realization of quality characteristics that can be linked to the function request registered by the user, and includes a connection relationship between the components. Record satisfaction conditions,
When the change support information derivation means is changed to another quality characteristic that can set the quality characteristic associated with the function request, each configuration registered as the quality satisfaction condition regarding the change of the quality characteristic Refer to the list of combinations of functions of elements and their connection relations, identify the missing parts and / or extra parts in the satisfying conditions of the connection relations of each component, and the architecture related to the service system before and after the change The service system design support program according to the above supplementary note, wherein the program is operated so as to perform a derivation process for a difference in connection relation between the components.

[Appendix 25]
The service system design support program as described in the above supplementary note, wherein the processor is operated as an architecture information defining unit that accepts the input of the architecture information on a model basis.

[Appendix 26]
The architecture information definition means accepts model-based components and functions that are performed in units of components corresponding to the components and functions that can be provided in the cloud environment that provides the service system to be designed as architecture information,
The change support information deriving means operates to derive the architectural difference related to the cloud-based service system before and after the change in correspondence with the components and functions of the cloud environment for the changed quality characteristic. A service system design support program as described in the above supplementary note.

[Appendix 27]
A recording medium on which the service system design support program described above is recorded.

This application claims priority based on Japanese Patent Application No. 2015-204278 filed on Oct. 16, 2015, the entire disclosure of which is incorporated herein.

1, 2 Design support system (computer system)
10 Request separation unit (request separation means)
20 Required quality satisfaction condition registration section (Required quality satisfaction condition registration means)
30 Change support information deriving unit (change support information deriving means)
31 Settable quality characteristic definition section (Settable quality characteristic definition means)
32 Request change section (request change means)
33 Impact Analysis Department (impact analysis means)
34 Correction attribute candidate output section (correction attribute candidate output means)

Claims (10)

1. With reference to the quality characteristic information indicating a list of characteristics indicating the quality of the service system, regarding the stakeholder request input to the design target service system, the function request and the characteristics registered in the quality characteristic information for each characteristic. Request separation means for accepting registration divided into quality characteristics by category,
   Quality characteristics that can be linked to the function request registered by the request separating means with reference to architecture information including the connection relationship of each component of the service system and an attribute indicating the function to be exhibited in each component unit Required quality satisfaction condition registration means for accepting registration of a combination of functions of each component included as an attribute in the architecture information that contributes to the realization of
   The association of the quality characteristic that can be changed with the design change with respect to the function request is maintained, and the quality characteristic associated with the function request registered by the request separation unit is changed to another quality characteristic that can be set. At this time, with respect to the changed quality characteristic, the function contributing to the realization of the quality requirement before the change is referred to by referring to the list of the combinations of the functions of each component registered in the required quality satisfaction condition registration unit. Change support information deriving means for identifying a combination and deriving a function review in the architecture that satisfies the function requirements and the quality characteristics after the change;
   A service system design support system comprising:
2. The change support information derivation means includes:
   The association of the quality characteristic that can be changed with the design change with respect to the function request is maintained, and the quality characteristic associated with the function request registered by the request separation unit is changed to another quality characteristic that can be set. At this time, with respect to the changed quality characteristic, the function that has contributed to the realization of the quality requirement after the change by referring to the list of the function combinations of each component registered in the required quality satisfaction condition registration unit Identifying combinations and deriving additional design locations for the functions in the architecture that meet the functional requirements and quality characteristics after the changes;
   The service system design support system according to claim 1.
3. The request separation means accepts registration of quality characteristics in association with individual function requests for each function request for registration of stakeholder requests input to the service system to be designed,
   The change support information deriving means is configured to change all the function requests with respect to the changed attribute of the certain quality request when the certain quality characteristic associated with each function request is changed to another settable quality characteristic. 3. The difference between architectural components related to the service system before and after the change is identified by identifying a location used to realize the quality characteristic before the change of claim 1 or 2, The service system design support system described.
4. A modification attribute candidate output means for outputting a functional difference between architectural components related to the service system before and after the change derived by the change support information deriving means in a model diagram so as to be recognizable;
   The modified attribute candidate output means outputs the overlapping part of the functional difference between the structural elements in the architecture when there are a plurality of function requests input to the service system in a visually recognizable manner. A service system design support system according to any one of claims 1 to 3.
5. The change support information derivation means includes:
   Settable quality characteristic defining means for accepting a quality characteristic that can be changed with a design change with respect to the function request;
   Request changing means for receiving an input for changing the quality characteristic associated with the function request registered by the request separating means to another settable quality characteristic received by the settable quality characteristic defining means;
   Concerning the quality characteristics changed by the requirement changing means, it contributed to the realization of quality requirements before and after the change by referring to the list of function combinations possessed by each component registered by the required quality satisfaction condition registration means An impact analysis unit that identifies a combination of functions and generates information indicating change in function of each component on the architecture related to the service system before and after the change as change support information;
   The modified attribute candidate output unit that refers to the change support information and reflects the attribute extracted by the influence analysis unit in the architecture information and outputs it as a model diagram. 5. The service system design support system according to any one of 4 above.
6. The architecture information includes connection information serving as a design parameter of the service system in a specific connection relationship of each component among the functions of each component.
   The required quality satisfaction condition registration means includes a combination of functions of each component that contributes to the realization of quality characteristics that can be linked to the function request registered by the user, and includes a connection relationship between the components. Record satisfaction conditions,
   The change support information deriving unit is configured to register each configuration registered as the quality satisfaction condition regarding the change of the quality characteristic when the quality characteristic associated with the function request is changed to another quality characteristic that can be set. An architecture related to the service system before and after the change by identifying a lacking part and / or an extra part in the satisfying condition of the connection relation of each component with reference to a list of function combinations and connection relations of each element The service system design support system according to any one of claims 1 to 5, wherein a difference in connection relation between the above components is derived.
7. The service system design support system according to any one of claims 1 to 6, further comprising architecture information defining means for receiving the input of the architecture information on a model basis.
8. The architecture information defining means accepts, as architecture information, a model-based component and a function performed in each component corresponding to a component and a function that can be provided in a cloud environment that provides the service system to be designed,
   The change support information deriving means derives, for the changed quality characteristic, an architectural difference related to the cloud-based service system before and after the change corresponding to the components and functions of the cloud environment. Item 8. A service system design support system according to Item 7.
9. For the stakeholder requirements entered for the service system to be designed, the quality characteristics are classified according to the characteristics registered in the quality characteristics information indicating the list of characteristics indicating the functional requirements and the quality of the service system prepared in advance. Accepted separately,
   It is possible to link to the registered function request by referring to architecture information including a connection relation of each component of the service system to be designed prepared in advance and an attribute indicating a function to be exhibited in each component. Accepting as a quality satisfaction condition a combination of functions of each component included as an attribute in the architecture information that contributes to the realization of quality characteristics,
   The association of quality characteristics that can be changed in accordance with a design change with respect to the function request is held in advance, and is changed when the quality characteristic associated with the received function request is changed to another quality characteristic that can be set. For the quality characteristics, the combination of the functions that contributed to the realization of the quality request before the change is identified with reference to the list of the combinations of the functions of each component registered as the quality satisfaction condition, and the function request And a service system design support method by an information processing system, wherein a review point of a function in the architecture that satisfies the quality characteristics after the change is derived.
10. The processor of the information processing system,
    With reference to the quality characteristic information indicating a list of characteristics indicating the quality of the service system, regarding the stakeholder request input to the design target service system, the function request and the characteristics registered in the quality characteristic information for each characteristic. Request separation means for accepting registration divided into quality characteristics by category,
    It can be linked to the function request registered by the request separation means with reference to architecture information including the connection relationship of each component of the design target service system and the attribute indicating the function to be exhibited in each component unit. Required quality satisfaction condition registration means for accepting registration of a combination of functions of each component included as an attribute in the architecture information, which contributes to realizing quality characteristics;
    The association of the quality characteristic that can be changed with the design change with respect to the function request is maintained, and the quality characteristic associated with the function request registered by the request separation unit is changed to another quality characteristic that can be set. At this time, with respect to the changed quality characteristic, the function contributing to the realization of the quality requirement before the change is referred to by referring to the list of the combinations of the functions of each component registered in the required quality satisfaction condition registration unit. Change support information deriving means for identifying a combination and deriving a function review in the architecture that satisfies the function requirements and the quality characteristics after the change;
    A storage medium for storing a service system design support program that is operated as follows.

Images