[vc_empty_space][vc_empty_space]
Information system design based on the result of organization Goal-Oriented requirements engineering process
Adikara F.a,b, Wijaya P.D.a, Hendradjaya B.b, Sitohang B.b
a Information System, Esa Unggul University, Jakarta, Indonesia
b School of Electrical Engineering and Informatics, Institute Technology of Bandung, Bandung, Indonesia
[vc_row][vc_column][vc_row_inner][vc_column_inner][vc_separator css=”.vc_custom_1624529070653{padding-top: 30px !important;padding-bottom: 30px !important;}”][/vc_column_inner][/vc_row_inner][vc_row_inner layout=”boxed”][vc_column_inner width=”3/4″ css=”.vc_custom_1624695412187{border-right-width: 1px !important;border-right-color: #dddddd !important;border-right-style: solid !important;border-radius: 1px !important;}”][vc_empty_space][megatron_heading title=”Abstract” size=”size-sm” text_align=”text-left”][vc_column_text]© Springer Science+Business Media Singapore 2016.In the previous research[1, 2], the use of Key Performance Indicators (KPIs) was proposed as a controlling tool for IT goal, which extracted from organization goal. The goals are the analysis and refinement using Case Based Reasoning (CBR) methods to get more qualified system requirements. This paper aims to illustrate the use of the IT goals and KPIs in the requirement engineering process that produced a Goal Tree Model, which would subsequently be used in an information system design using the Unified Modeling Language (UML). Through requirement engineering process with KPIs as the system’s success parameter in achieving the goals derived from the organization goals, this paper seeks to demonstrate the improvement in the quality of the designed system. Also included in this research is how the results of the requirement engineering process produces a system that fulfill the KPIs without basing the system’s requirements on the user, to reduce the risk of the occurrence of user’s needs in the process of requirement elicitation. We have applied the proposed process to a development of an information system as a case study.[/vc_column_text][vc_empty_space][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][vc_empty_space][megatron_heading title=”Author keywords” size=”size-sm” text_align=”text-left”][vc_column_text]Casebased reasonings (CBR),Goal-oriented requirements engineering,Key performance indicators,Requirement elicitation,Requirement engineering process,System requirements,Tree modeling[/vc_column_text][vc_empty_space][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][vc_empty_space][megatron_heading title=”Indexed keywords” size=”size-sm” text_align=”text-left”][vc_column_text]Goal-oriented requirement elicitation,Information system design,Key performance indicators,Software engineering[/vc_column_text][vc_empty_space][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][vc_empty_space][megatron_heading title=”Funding details” size=”size-sm” text_align=”text-left”][vc_column_text][/vc_column_text][vc_empty_space][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][vc_empty_space][megatron_heading title=”DOI” size=”size-sm” text_align=”text-left”][vc_column_text]https://doi.org/10.1007/978-981-10-0557-2_104[/vc_column_text][/vc_column_inner][vc_column_inner width=”1/4″][vc_column_text]Widget Plumx[/vc_column_text][/vc_column_inner][/vc_row_inner][/vc_column][/vc_row][vc_row][vc_column][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][/vc_column][/vc_row]