Loading…
High-level design for user and component interfaces
Component-based software architecture is very important for current software engineering practice because (a) it is the basis for re-use of software at the component level, and (b) in distributed systems, the physical distribution of an application over separate computers represents a decomposition...
Saved in:
Published in: | Knowledge-based systems 2004-12, Vol.17 (7), p.303-310 |
---|---|
Main Author: | |
Format: | Article |
Language: | English |
Subjects: | |
Citations: | Items that this one cites Items that cite this one |
Online Access: | Get full text |
Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
cited_by | cdi_FETCH-LOGICAL-c337t-b6a0f63972d8ee47b1e600672b9203a23240a24707e8e0c8cbc63337bedf8d163 |
---|---|
cites | cdi_FETCH-LOGICAL-c337t-b6a0f63972d8ee47b1e600672b9203a23240a24707e8e0c8cbc63337bedf8d163 |
container_end_page | 310 |
container_issue | 7 |
container_start_page | 303 |
container_title | Knowledge-based systems |
container_volume | 17 |
creator | Bochmann, Gregor v. |
description | Component-based software architecture is very important for current software engineering practice because (a) it is the basis for re-use of software at the component level, and (b) in distributed systems, the physical distribution of an application over separate computers represents a decomposition of the application. Typical e-commerce applications consist of various components sometimes belonging to different organizations, and presenting different user interfaces to various categories of users. We review in this paper the current trend in standards for inter-component communication in distributed systems, including various forms of remote procedure calls (RPC) and message passing, and paradigms for describing and implementing user interfaces in the Web environment. We discuss whether the user interface can also be described, at an abstract level, by RPC primitives. In the second part of the paper, we discuss the importance of indicating which party is responsible for making certain decisions for selecting control flow alternatives and certain parameter values. This leads to some guidelines for describing system behavior scenarios at the requirements level. We also discuss how this approach can be integrated with screen-oriented behavior definitions. |
doi_str_mv | 10.1016/j.knosys.2004.07.005 |
format | article |
fullrecord | <record><control><sourceid>proquest_cross</sourceid><recordid>TN_cdi_proquest_miscellaneous_57629039</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><els_id>S0950705104000486</els_id><sourcerecordid>57629039</sourcerecordid><originalsourceid>FETCH-LOGICAL-c337t-b6a0f63972d8ee47b1e600672b9203a23240a24707e8e0c8cbc63337bedf8d163</originalsourceid><addsrcrecordid>eNp9kLFOwzAURS0EEqXwBwyZ2BKe7cROFiRUQYtUiQVmy7FfiktqFzut1L8nVZiZ7nLPle4h5J5CQYGKx23x7UM6pYIBlAXIAqC6IDNaS5bLEppLMoOmglxCRa_JTUpbAGCM1jPCV27zlfd4xD6zmNzGZ12I2SFhzLS3mQm7ffDoh8z5AWOnDaZbctXpPuHdX87J5-vLx2KVr9-Xb4vndW44l0PeCg2d4I1ktkYsZUtRAAjJ2oYB14yzEjQrJUisEUxtWiP4SLZou9pSwefkYdrdx_BzwDSonUsG-157DIekKilYA7wZi-VUNDGkFLFT--h2Op4UBXU2pLZqMqTOhhRINRoasacJw_HE0WFUyTj0Bq2LaAZlg_t_4BcSv3Bm</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>57629039</pqid></control><display><type>article</type><title>High-level design for user and component interfaces</title><source>Library & Information Science Abstracts (LISA)</source><source>ScienceDirect Journals</source><creator>Bochmann, Gregor v.</creator><creatorcontrib>Bochmann, Gregor v.</creatorcontrib><description>Component-based software architecture is very important for current software engineering practice because (a) it is the basis for re-use of software at the component level, and (b) in distributed systems, the physical distribution of an application over separate computers represents a decomposition of the application. Typical e-commerce applications consist of various components sometimes belonging to different organizations, and presenting different user interfaces to various categories of users. We review in this paper the current trend in standards for inter-component communication in distributed systems, including various forms of remote procedure calls (RPC) and message passing, and paradigms for describing and implementing user interfaces in the Web environment. We discuss whether the user interface can also be described, at an abstract level, by RPC primitives. In the second part of the paper, we discuss the importance of indicating which party is responsible for making certain decisions for selecting control flow alternatives and certain parameter values. This leads to some guidelines for describing system behavior scenarios at the requirements level. We also discuss how this approach can be integrated with screen-oriented behavior definitions.</description><identifier>ISSN: 0950-7051</identifier><identifier>EISSN: 1872-7409</identifier><identifier>DOI: 10.1016/j.knosys.2004.07.005</identifier><language>eng</language><publisher>Elsevier B.V</publisher><subject>Component-based development ; Design ; Requirements modeling ; Screen-oriented interface ; Software engineering ; User interface</subject><ispartof>Knowledge-based systems, 2004-12, Vol.17 (7), p.303-310</ispartof><rights>2004 Elsevier B.V.</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c337t-b6a0f63972d8ee47b1e600672b9203a23240a24707e8e0c8cbc63337bedf8d163</citedby><cites>FETCH-LOGICAL-c337t-b6a0f63972d8ee47b1e600672b9203a23240a24707e8e0c8cbc63337bedf8d163</cites></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><link.rule.ids>314,780,784,27924,27925,34136</link.rule.ids></links><search><creatorcontrib>Bochmann, Gregor v.</creatorcontrib><title>High-level design for user and component interfaces</title><title>Knowledge-based systems</title><description>Component-based software architecture is very important for current software engineering practice because (a) it is the basis for re-use of software at the component level, and (b) in distributed systems, the physical distribution of an application over separate computers represents a decomposition of the application. Typical e-commerce applications consist of various components sometimes belonging to different organizations, and presenting different user interfaces to various categories of users. We review in this paper the current trend in standards for inter-component communication in distributed systems, including various forms of remote procedure calls (RPC) and message passing, and paradigms for describing and implementing user interfaces in the Web environment. We discuss whether the user interface can also be described, at an abstract level, by RPC primitives. In the second part of the paper, we discuss the importance of indicating which party is responsible for making certain decisions for selecting control flow alternatives and certain parameter values. This leads to some guidelines for describing system behavior scenarios at the requirements level. We also discuss how this approach can be integrated with screen-oriented behavior definitions.</description><subject>Component-based development</subject><subject>Design</subject><subject>Requirements modeling</subject><subject>Screen-oriented interface</subject><subject>Software engineering</subject><subject>User interface</subject><issn>0950-7051</issn><issn>1872-7409</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2004</creationdate><recordtype>article</recordtype><sourceid>F2A</sourceid><recordid>eNp9kLFOwzAURS0EEqXwBwyZ2BKe7cROFiRUQYtUiQVmy7FfiktqFzut1L8nVZiZ7nLPle4h5J5CQYGKx23x7UM6pYIBlAXIAqC6IDNaS5bLEppLMoOmglxCRa_JTUpbAGCM1jPCV27zlfd4xD6zmNzGZ12I2SFhzLS3mQm7ffDoh8z5AWOnDaZbctXpPuHdX87J5-vLx2KVr9-Xb4vndW44l0PeCg2d4I1ktkYsZUtRAAjJ2oYB14yzEjQrJUisEUxtWiP4SLZou9pSwefkYdrdx_BzwDSonUsG-157DIekKilYA7wZi-VUNDGkFLFT--h2Op4UBXU2pLZqMqTOhhRINRoasacJw_HE0WFUyTj0Bq2LaAZlg_t_4BcSv3Bm</recordid><startdate>20041201</startdate><enddate>20041201</enddate><creator>Bochmann, Gregor v.</creator><general>Elsevier B.V</general><scope>AAYXX</scope><scope>CITATION</scope><scope>E3H</scope><scope>F2A</scope></search><sort><creationdate>20041201</creationdate><title>High-level design for user and component interfaces</title><author>Bochmann, Gregor v.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c337t-b6a0f63972d8ee47b1e600672b9203a23240a24707e8e0c8cbc63337bedf8d163</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2004</creationdate><topic>Component-based development</topic><topic>Design</topic><topic>Requirements modeling</topic><topic>Screen-oriented interface</topic><topic>Software engineering</topic><topic>User interface</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Bochmann, Gregor v.</creatorcontrib><collection>CrossRef</collection><collection>Library & Information Sciences Abstracts (LISA)</collection><collection>Library & Information Science Abstracts (LISA)</collection><jtitle>Knowledge-based systems</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Bochmann, Gregor v.</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>High-level design for user and component interfaces</atitle><jtitle>Knowledge-based systems</jtitle><date>2004-12-01</date><risdate>2004</risdate><volume>17</volume><issue>7</issue><spage>303</spage><epage>310</epage><pages>303-310</pages><issn>0950-7051</issn><eissn>1872-7409</eissn><abstract>Component-based software architecture is very important for current software engineering practice because (a) it is the basis for re-use of software at the component level, and (b) in distributed systems, the physical distribution of an application over separate computers represents a decomposition of the application. Typical e-commerce applications consist of various components sometimes belonging to different organizations, and presenting different user interfaces to various categories of users. We review in this paper the current trend in standards for inter-component communication in distributed systems, including various forms of remote procedure calls (RPC) and message passing, and paradigms for describing and implementing user interfaces in the Web environment. We discuss whether the user interface can also be described, at an abstract level, by RPC primitives. In the second part of the paper, we discuss the importance of indicating which party is responsible for making certain decisions for selecting control flow alternatives and certain parameter values. This leads to some guidelines for describing system behavior scenarios at the requirements level. We also discuss how this approach can be integrated with screen-oriented behavior definitions.</abstract><pub>Elsevier B.V</pub><doi>10.1016/j.knosys.2004.07.005</doi><tpages>8</tpages></addata></record> |
fulltext | fulltext |
identifier | ISSN: 0950-7051 |
ispartof | Knowledge-based systems, 2004-12, Vol.17 (7), p.303-310 |
issn | 0950-7051 1872-7409 |
language | eng |
recordid | cdi_proquest_miscellaneous_57629039 |
source | Library & Information Science Abstracts (LISA); ScienceDirect Journals |
subjects | Component-based development Design Requirements modeling Screen-oriented interface Software engineering User interface |
title | High-level design for user and component interfaces |
url | http://sfxeu10.hosted.exlibrisgroup.com/loughborough?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-02T14%3A30%3A01IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_cross&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=High-level%20design%20for%20user%20and%20component%20interfaces&rft.jtitle=Knowledge-based%20systems&rft.au=Bochmann,%20Gregor%20v.&rft.date=2004-12-01&rft.volume=17&rft.issue=7&rft.spage=303&rft.epage=310&rft.pages=303-310&rft.issn=0950-7051&rft.eissn=1872-7409&rft_id=info:doi/10.1016/j.knosys.2004.07.005&rft_dat=%3Cproquest_cross%3E57629039%3C/proquest_cross%3E%3Cgrp_id%3Ecdi_FETCH-LOGICAL-c337t-b6a0f63972d8ee47b1e600672b9203a23240a24707e8e0c8cbc63337bedf8d163%3C/grp_id%3E%3Coa%3E%3C/oa%3E%3Curl%3E%3C/url%3E&rft_id=info:oai/&rft_pqid=57629039&rft_id=info:pmid/&rfr_iscdi=true |