Loading…

Deriving objects from use cases in real-time embedded systems

In recent years, a number of use case-driven processes have emerged for the development of real-time embedded systems. In these processes, once requirements have been defined by use cases, the next step is usually to identify from that use cases, the central objects in the system and describing how...

Full description

Saved in:
Bibliographic Details
Published in:Information and software technology 2005-06, Vol.47 (8), p.533-541
Main Authors: Kimour, Mohamed T., Meslati, Djamel
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-c364t-5af7bcb05a86f508890f8bf9497820c65dbbefd817997768038556d6f3e708273
cites cdi_FETCH-LOGICAL-c364t-5af7bcb05a86f508890f8bf9497820c65dbbefd817997768038556d6f3e708273
container_end_page 541
container_issue 8
container_start_page 533
container_title Information and software technology
container_volume 47
creator Kimour, Mohamed T.
Meslati, Djamel
description In recent years, a number of use case-driven processes have emerged for the development of real-time embedded systems. In these processes, once requirements have been defined by use cases, the next step is usually to identify from that use cases, the central objects in the system and describing how they interact with one another. However, identifying objects/classes from the requirements is both a critical and hard task. This is mainly due to the lack of pragmatic technique that steers such a task. In this article, we present a systematic approach to identify objects from the use case model for the real-time embedded systems. After hierarchically decomposing the system into its parts, we first transform the use case structured-text style into an activity diagram, which may be reused in the next development activities. Second, we use the derived activity diagram for identifying objects. With the behavioural model, an object model can be viewed as a first cut at a design model, and is thus an essential input when the system is shaped in design and design implementation.
doi_str_mv 10.1016/j.infsof.2004.10.003
format article
fullrecord <record><control><sourceid>proquest_cross</sourceid><recordid>TN_cdi_proquest_miscellaneous_57630017</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><els_id>S0950584904001478</els_id><sourcerecordid>826994281</sourcerecordid><originalsourceid>FETCH-LOGICAL-c364t-5af7bcb05a86f508890f8bf9497820c65dbbefd817997768038556d6f3e708273</originalsourceid><addsrcrecordid>eNp9kEtLxEAQhAdRcF39Bx6CB2-JPUnmkYOC-IYFL3oekkmPTMhjnc4u7L83IZ48eGooqoquj7FLDgkHLm-axPeOBpekAPkkJQDZEVtxrbJYQiqO2QoKAbHQeXHKzogaAK4ggxW7fcTg977_ioaqQTtS5MLQRTvCyJaEFPk-Cli28eg7jLCrsK6xjuhAI3Z0zk5c2RJe_N41-3x--nh4jTfvL28P95vYZjIfY1E6VdkKRKmlE6B1AU5XrsgLpVOwUtRVha7WXBWFUlJDpoWQtXQZKtCpytbseundhuF7hzSazpPFti17HHZkhJLZPGkyXv0xNsMu9NNvhhcyT1PgYjLli8mGgSigM9vguzIcDAczAzWNWYCaGeisTkCn2N0Sw2np3mMwZD32FmsfJnKmHvz_BT9UCH7g</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>196422015</pqid></control><display><type>article</type><title>Deriving objects from use cases in real-time embedded systems</title><source>Library &amp; Information Science Abstracts (LISA)</source><source>ScienceDirect Freedom Collection 2022-2024</source><creator>Kimour, Mohamed T. ; Meslati, Djamel</creator><creatorcontrib>Kimour, Mohamed T. ; Meslati, Djamel</creatorcontrib><description>In recent years, a number of use case-driven processes have emerged for the development of real-time embedded systems. In these processes, once requirements have been defined by use cases, the next step is usually to identify from that use cases, the central objects in the system and describing how they interact with one another. However, identifying objects/classes from the requirements is both a critical and hard task. This is mainly due to the lack of pragmatic technique that steers such a task. In this article, we present a systematic approach to identify objects from the use case model for the real-time embedded systems. After hierarchically decomposing the system into its parts, we first transform the use case structured-text style into an activity diagram, which may be reused in the next development activities. Second, we use the derived activity diagram for identifying objects. With the behavioural model, an object model can be viewed as a first cut at a design model, and is thus an essential input when the system is shaped in design and design implementation.</description><identifier>ISSN: 0950-5849</identifier><identifier>EISSN: 1873-6025</identifier><identifier>DOI: 10.1016/j.infsof.2004.10.003</identifier><language>eng</language><publisher>Amsterdam: Elsevier B.V</publisher><subject>Activity diagram ; Embedded systems ; Object model ; Object oriented programming ; Real-time embedded system ; Software ; Studies ; UML ; Use case</subject><ispartof>Information and software technology, 2005-06, Vol.47 (8), p.533-541</ispartof><rights>2004 Elsevier B.V.</rights><rights>Copyright Elsevier Science Ltd. Jun 1, 2005</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c364t-5af7bcb05a86f508890f8bf9497820c65dbbefd817997768038556d6f3e708273</citedby><cites>FETCH-LOGICAL-c364t-5af7bcb05a86f508890f8bf9497820c65dbbefd817997768038556d6f3e708273</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>Kimour, Mohamed T.</creatorcontrib><creatorcontrib>Meslati, Djamel</creatorcontrib><title>Deriving objects from use cases in real-time embedded systems</title><title>Information and software technology</title><description>In recent years, a number of use case-driven processes have emerged for the development of real-time embedded systems. In these processes, once requirements have been defined by use cases, the next step is usually to identify from that use cases, the central objects in the system and describing how they interact with one another. However, identifying objects/classes from the requirements is both a critical and hard task. This is mainly due to the lack of pragmatic technique that steers such a task. In this article, we present a systematic approach to identify objects from the use case model for the real-time embedded systems. After hierarchically decomposing the system into its parts, we first transform the use case structured-text style into an activity diagram, which may be reused in the next development activities. Second, we use the derived activity diagram for identifying objects. With the behavioural model, an object model can be viewed as a first cut at a design model, and is thus an essential input when the system is shaped in design and design implementation.</description><subject>Activity diagram</subject><subject>Embedded systems</subject><subject>Object model</subject><subject>Object oriented programming</subject><subject>Real-time embedded system</subject><subject>Software</subject><subject>Studies</subject><subject>UML</subject><subject>Use case</subject><issn>0950-5849</issn><issn>1873-6025</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2005</creationdate><recordtype>article</recordtype><sourceid>F2A</sourceid><recordid>eNp9kEtLxEAQhAdRcF39Bx6CB2-JPUnmkYOC-IYFL3oekkmPTMhjnc4u7L83IZ48eGooqoquj7FLDgkHLm-axPeOBpekAPkkJQDZEVtxrbJYQiqO2QoKAbHQeXHKzogaAK4ggxW7fcTg977_ioaqQTtS5MLQRTvCyJaEFPk-Cli28eg7jLCrsK6xjuhAI3Z0zk5c2RJe_N41-3x--nh4jTfvL28P95vYZjIfY1E6VdkKRKmlE6B1AU5XrsgLpVOwUtRVha7WXBWFUlJDpoWQtXQZKtCpytbseundhuF7hzSazpPFti17HHZkhJLZPGkyXv0xNsMu9NNvhhcyT1PgYjLli8mGgSigM9vguzIcDAczAzWNWYCaGeisTkCn2N0Sw2np3mMwZD32FmsfJnKmHvz_BT9UCH7g</recordid><startdate>20050601</startdate><enddate>20050601</enddate><creator>Kimour, Mohamed T.</creator><creator>Meslati, Djamel</creator><general>Elsevier B.V</general><general>Elsevier Science Ltd</general><scope>AAYXX</scope><scope>CITATION</scope><scope>7SC</scope><scope>8FD</scope><scope>JQ2</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope><scope>E3H</scope><scope>F2A</scope></search><sort><creationdate>20050601</creationdate><title>Deriving objects from use cases in real-time embedded systems</title><author>Kimour, Mohamed T. ; Meslati, Djamel</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c364t-5af7bcb05a86f508890f8bf9497820c65dbbefd817997768038556d6f3e708273</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2005</creationdate><topic>Activity diagram</topic><topic>Embedded systems</topic><topic>Object model</topic><topic>Object oriented programming</topic><topic>Real-time embedded system</topic><topic>Software</topic><topic>Studies</topic><topic>UML</topic><topic>Use case</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Kimour, Mohamed T.</creatorcontrib><creatorcontrib>Meslati, Djamel</creatorcontrib><collection>CrossRef</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>ProQuest Computer Science Collection</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts – Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><collection>Library &amp; Information Sciences Abstracts (LISA)</collection><collection>Library &amp; Information Science Abstracts (LISA)</collection><jtitle>Information and software technology</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Kimour, Mohamed T.</au><au>Meslati, Djamel</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Deriving objects from use cases in real-time embedded systems</atitle><jtitle>Information and software technology</jtitle><date>2005-06-01</date><risdate>2005</risdate><volume>47</volume><issue>8</issue><spage>533</spage><epage>541</epage><pages>533-541</pages><issn>0950-5849</issn><eissn>1873-6025</eissn><abstract>In recent years, a number of use case-driven processes have emerged for the development of real-time embedded systems. In these processes, once requirements have been defined by use cases, the next step is usually to identify from that use cases, the central objects in the system and describing how they interact with one another. However, identifying objects/classes from the requirements is both a critical and hard task. This is mainly due to the lack of pragmatic technique that steers such a task. In this article, we present a systematic approach to identify objects from the use case model for the real-time embedded systems. After hierarchically decomposing the system into its parts, we first transform the use case structured-text style into an activity diagram, which may be reused in the next development activities. Second, we use the derived activity diagram for identifying objects. With the behavioural model, an object model can be viewed as a first cut at a design model, and is thus an essential input when the system is shaped in design and design implementation.</abstract><cop>Amsterdam</cop><pub>Elsevier B.V</pub><doi>10.1016/j.infsof.2004.10.003</doi><tpages>9</tpages></addata></record>
fulltext fulltext
identifier ISSN: 0950-5849
ispartof Information and software technology, 2005-06, Vol.47 (8), p.533-541
issn 0950-5849
1873-6025
language eng
recordid cdi_proquest_miscellaneous_57630017
source Library & Information Science Abstracts (LISA); ScienceDirect Freedom Collection 2022-2024
subjects Activity diagram
Embedded systems
Object model
Object oriented programming
Real-time embedded system
Software
Studies
UML
Use case
title Deriving objects from use cases in real-time embedded systems
url http://sfxeu10.hosted.exlibrisgroup.com/loughborough?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-30T20%3A56%3A19IST&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=Deriving%20objects%20from%20use%20cases%20in%20real-time%20embedded%20systems&rft.jtitle=Information%20and%20software%20technology&rft.au=Kimour,%20Mohamed%20T.&rft.date=2005-06-01&rft.volume=47&rft.issue=8&rft.spage=533&rft.epage=541&rft.pages=533-541&rft.issn=0950-5849&rft.eissn=1873-6025&rft_id=info:doi/10.1016/j.infsof.2004.10.003&rft_dat=%3Cproquest_cross%3E826994281%3C/proquest_cross%3E%3Cgrp_id%3Ecdi_FETCH-LOGICAL-c364t-5af7bcb05a86f508890f8bf9497820c65dbbefd817997768038556d6f3e708273%3C/grp_id%3E%3Coa%3E%3C/oa%3E%3Curl%3E%3C/url%3E&rft_id=info:oai/&rft_pqid=196422015&rft_id=info:pmid/&rfr_iscdi=true