% :- [combine1, cost1]
> cd('c:/my_directory/').
> [main].
> [defs/arch_def, defs/arch_def_utils].
> go(goodness of system).
> tar2(arch_def).
> tar2 arch_def > arch_def.out
> tar2 -r arch_def > arch_def_r.out
> xval tar2 arch_def 10
User needs to provide a textual softgoal framework definition file in a special format to be fed to the interpreter. Sample framework definition file can be found under the defs folder.
Softgoals, claims, and stakeholders can be seen as nodes within the softgoal graph, and should be defined as follows:
Rules can be viewed as the edges in the softgoal graph, and are defined in the following manner:
softgoal coherence of system is critical.
softgoal deletability of system is veryCritical.
claims c1.
claims 'do not exceed space limit'.
stakeholder eliza.
stakeholder rule1.
Note that there must be only one softgoal sitting at the top of the softgoal graph.
eliza says goodness of system if
modifiability of system
any_of comprehensibility of system
ref "L Chung's book" keywords [chung].
rule1 says performance of system if
helped by c1
any_of modifiability of process
any_of modifiability of dataRep
any_of modifiability of function
ref "L Chung's book" keywords [chung].
User is required to customize the scoring function of the softgoal graph. Sample scoring functions for combination rules and costs can be found in the defs_score folder.
The names and number of desired classes is defined in a util files associated with the softgoal graph. Sample utils files can be found under the defs folder.
:- [your_directory/your_cost_file, your_directory/your_combine_file].
> cd('c:/my_directory/').
> [main].
> [your_directory/graph_def, your_directory/graph_def_utils].
> go(the name of the top softgoal).
> tar2_write_name_file('the_name_of_your_graph'),
make_results(the name of the top softgoal, 10000, 'the_name_of_your_graph'),
tar2_analyse_pl('the_name_of_your_graph'),
tar2_write_data_file('the_name_of_your_graph').