SEVEN WAYS TO MAKE A HYPERTEXT PROJECT FAIL

SEVEN WAYS TO MAKE A HYPERTEXT PROJECT FAIL

Hypertext is an exciting concept, but designing and developing hypertext applications of practical scale is hard. "Hypertext engineers" must overcome seven problems to make a project feasible and successful: 1. Developing realistic expectations in the face of hypertext hype 2. Assembling a...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:Technical communication (Washington) 1992-05, Vol.39 (2), p.226-230
1. Verfasser: Glushko, Robert J.
Format: Artikel
Sprache:eng
Schlagworte:
Analysis
Computer software
Copyright infringement
Database design
Design engineering
Design evaluation
Hyperlinks
Hypertext
Management
Multimedia materials
Optical character recognition
Technology
Usability
Word processing
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
container_end_page 230
container_issue 2
container_start_page 226
container_title Technical communication (Washington)
container_volume 39
creator Glushko, Robert J.
description Hypertext is an exciting concept, but designing and developing hypertext applications of practical scale is hard. "Hypertext engineers" must overcome seven problems to make a project feasible and successful: 1. Developing realistic expectations in the face of hypertext hype 2. Assembling a multidisciplinary project team 3. Establishing and following design guidelines 4. Dealing with installed base constraints 5. Obtaining usable source files 6. Finding appropriate software technology and methods 7. Overcoming legal uncertainties about intellectual property concerns.
format Article
fullrecord <record><control><sourceid>gale_proqu</sourceid><recordid>TN_cdi_proquest_journals_220980256</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><galeid>A12388893</galeid><jstor_id>43090278</jstor_id><sourcerecordid>A12388893</sourcerecordid><originalsourceid>FETCH-LOGICAL-g1946-b22670167222829eb075122c1d1300c4998c1738ecc9e019dd669daf2bed81213</originalsourceid><addsrcrecordid>eNpt0E1Lw0AQBuBFFKzVnyAsngQb2J3Nx-4xhPRDoylt1PYUtptNSEmTNklB_70L9VLozGHg5WEG5goNqGDcYq5YXaMBIbawGHWcW3TXdVtiihNngF6W4Vf4gb_99RInMX7330Ls4-l6Hi6ScJXg-SJ-DYMEj_1ZdI9ucll1-uF_DtHnOEyCqRXFk1ngR1ZBhe1aGwDXI9T1AICD0BviORRA0YwyQpQtBFfUY1wrJTShIstcV2Qyh43OOAXKhujptHffNoej7vp02xzb2pxMAYjgBBzXoNEJFbLSaVnnTd9KVehat7Jqap2XJvYpMM65YIZbF7jpTO9Kdck_n3lDev3TF_LYdSmfRGd0dImqpqp0oVPzmiA-448nvu36pk33bbmT7W9qMyIIeJz9AVz-fRQ</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>220980256</pqid></control><display><type>article</type><title>SEVEN WAYS TO MAKE A HYPERTEXT PROJECT FAIL</title><source>JSTOR Archive Collection A-Z Listing</source><creator>Glushko, Robert J.</creator><creatorcontrib>Glushko, Robert J.</creatorcontrib><description>Hypertext is an exciting concept, but designing and developing hypertext applications of practical scale is hard. "Hypertext engineers" must overcome seven problems to make a project feasible and successful: 1. Developing realistic expectations in the face of hypertext hype 2. Assembling a multidisciplinary project team 3. Establishing and following design guidelines 4. Dealing with installed base constraints 5. Obtaining usable source files 6. Finding appropriate software technology and methods 7. Overcoming legal uncertainties about intellectual property concerns.</description><identifier>ISSN: 0049-3155</identifier><identifier>EISSN: 1938-369X</identifier><identifier>CODEN: TLCMBT</identifier><language>eng</language><publisher>Washington: Society for Technical Communication</publisher><subject>Analysis ; Computer software ; Copyright infringement ; Database design ; Design engineering ; Design evaluation ; Hyperlinks ; Hypertext ; Management ; Multimedia materials ; Optical character recognition ; Technology ; Usability ; Word processing</subject><ispartof>Technical communication (Washington), 1992-05, Vol.39 (2), p.226-230</ispartof><rights>Copyright © 1992 Society for Technical Communication</rights><rights>COPYRIGHT 1992 Society for Technical Communication</rights><rights>COPYRIGHT 1992 Society for Technical Communication</rights><rights>Copyright Society for Technical Communication May 1992</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktopdf>$$Uhttps://www.jstor.org/stable/pdf/43090278$$EPDF$$P50$$Gjstor$$H</linktopdf><linktohtml>$$Uhttps://www.jstor.org/stable/43090278$$EHTML$$P50$$Gjstor$$H</linktohtml><link.rule.ids>314,780,784,803,58015,58248</link.rule.ids></links><search><creatorcontrib>Glushko, Robert J.</creatorcontrib><title>SEVEN WAYS TO MAKE A HYPERTEXT PROJECT FAIL</title><title>Technical communication (Washington)</title><addtitle>Technical Communication</addtitle><description>Hypertext is an exciting concept, but designing and developing hypertext applications of practical scale is hard. "Hypertext engineers" must overcome seven problems to make a project feasible and successful: 1. Developing realistic expectations in the face of hypertext hype 2. Assembling a multidisciplinary project team 3. Establishing and following design guidelines 4. Dealing with installed base constraints 5. Obtaining usable source files 6. Finding appropriate software technology and methods 7. Overcoming legal uncertainties about intellectual property concerns.</description><subject>Analysis</subject><subject>Computer software</subject><subject>Copyright infringement</subject><subject>Database design</subject><subject>Design engineering</subject><subject>Design evaluation</subject><subject>Hyperlinks</subject><subject>Hypertext</subject><subject>Management</subject><subject>Multimedia materials</subject><subject>Optical character recognition</subject><subject>Technology</subject><subject>Usability</subject><subject>Word processing</subject><issn>0049-3155</issn><issn>1938-369X</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>1992</creationdate><recordtype>article</recordtype><recordid>eNpt0E1Lw0AQBuBFFKzVnyAsngQb2J3Nx-4xhPRDoylt1PYUtptNSEmTNklB_70L9VLozGHg5WEG5goNqGDcYq5YXaMBIbawGHWcW3TXdVtiihNngF6W4Vf4gb_99RInMX7330Ls4-l6Hi6ScJXg-SJ-DYMEj_1ZdI9ucll1-uF_DtHnOEyCqRXFk1ngR1ZBhe1aGwDXI9T1AICD0BviORRA0YwyQpQtBFfUY1wrJTShIstcV2Qyh43OOAXKhujptHffNoej7vp02xzb2pxMAYjgBBzXoNEJFbLSaVnnTd9KVehat7Jqap2XJvYpMM65YIZbF7jpTO9Kdck_n3lDev3TF_LYdSmfRGd0dImqpqp0oVPzmiA-448nvu36pk33bbmT7W9qMyIIeJz9AVz-fRQ</recordid><startdate>19920501</startdate><enddate>19920501</enddate><creator>Glushko, Robert J.</creator><general>Society for Technical Communication</general><scope>8GL</scope><scope>E3H</scope><scope>F2A</scope></search><sort><creationdate>19920501</creationdate><title>SEVEN WAYS TO MAKE A HYPERTEXT PROJECT FAIL</title><author>Glushko, Robert J.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-g1946-b22670167222829eb075122c1d1300c4998c1738ecc9e019dd669daf2bed81213</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>1992</creationdate><topic>Analysis</topic><topic>Computer software</topic><topic>Copyright infringement</topic><topic>Database design</topic><topic>Design engineering</topic><topic>Design evaluation</topic><topic>Hyperlinks</topic><topic>Hypertext</topic><topic>Management</topic><topic>Multimedia materials</topic><topic>Optical character recognition</topic><topic>Technology</topic><topic>Usability</topic><topic>Word processing</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Glushko, Robert J.</creatorcontrib><collection>Gale In Context: High School</collection><collection>Library &amp; Information Sciences Abstracts (LISA)</collection><collection>Library &amp; Information Science Abstracts (LISA)</collection><jtitle>Technical communication (Washington)</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Glushko, Robert J.</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>SEVEN WAYS TO MAKE A HYPERTEXT PROJECT FAIL</atitle><jtitle>Technical communication (Washington)</jtitle><addtitle>Technical Communication</addtitle><date>1992-05-01</date><risdate>1992</risdate><volume>39</volume><issue>2</issue><spage>226</spage><epage>230</epage><pages>226-230</pages><issn>0049-3155</issn><eissn>1938-369X</eissn><coden>TLCMBT</coden><abstract>Hypertext is an exciting concept, but designing and developing hypertext applications of practical scale is hard. "Hypertext engineers" must overcome seven problems to make a project feasible and successful: 1. Developing realistic expectations in the face of hypertext hype 2. Assembling a multidisciplinary project team 3. Establishing and following design guidelines 4. Dealing with installed base constraints 5. Obtaining usable source files 6. Finding appropriate software technology and methods 7. Overcoming legal uncertainties about intellectual property concerns.</abstract><cop>Washington</cop><pub>Society for Technical Communication</pub><tpages>5</tpages></addata></record>
fulltext fulltext
identifier ISSN: 0049-3155
ispartof Technical communication (Washington), 1992-05, Vol.39 (2), p.226-230
issn 0049-3155
1938-369X
language eng
recordid cdi_proquest_journals_220980256
source JSTOR Archive Collection A-Z Listing
subjects Analysis
Computer software
Copyright infringement
Database design
Design engineering
Design evaluation
Hyperlinks
Hypertext
Management
Multimedia materials
Optical character recognition
Technology
Usability
Word processing
title SEVEN WAYS TO MAKE A HYPERTEXT PROJECT FAIL
url https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-09T22%3A36%3A57IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-gale_proqu&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=SEVEN%20WAYS%20TO%20MAKE%20A%20HYPERTEXT%20PROJECT%20FAIL&rft.jtitle=Technical%20communication%20(Washington)&rft.au=Glushko,%20Robert%20J.&rft.date=1992-05-01&rft.volume=39&rft.issue=2&rft.spage=226&rft.epage=230&rft.pages=226-230&rft.issn=0049-3155&rft.eissn=1938-369X&rft.coden=TLCMBT&rft_id=info:doi/&rft_dat=%3Cgale_proqu%3EA12388893%3C/gale_proqu%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=220980256&rft_id=info:pmid/&rft_galeid=A12388893&rft_jstor_id=43090278&rfr_iscdi=true