File Download
  Links for fulltext
     (May Require Subscription)
Supplementary

Article: Formal or informal, practical or impractical: towards integrating formal methods with informal practices in software engineering education

TitleFormal or informal, practical or impractical: towards integrating formal methods with informal practices in software engineering education
Authors
Issue Date1993
PublisherElsevier BV.
Citation
Ifip Transactions A: Computer Science And Technology, 1993 A-40, p. 189-197 How to Cite?
AbstractTwo conflicting schools of thought have been dominating software engineering education. One school stresses on the popular software development methodologies, but horror stories on poorly designed systems are not uncommon. The other school advocates formal methods, but most practitioners regard them as impractical. We recommend that we should bridge the gap between the formal and informal by bringing theory to existing practice. The formalism should be used as a working tool behind popular software development methodologies. Students should not be trained as craftsmen who consider software development as an art and learn only from past mistakes. Nor should they be trained as mathematicians who are more comfortable with theory than applications. Software engineers must be educated as real 'engineers' who are competent with industrial practices as well as the mathematical foundation directly supporting them.
Persistent Identifierhttp://hdl.handle.net/10722/43693
ISSN

 

DC FieldValueLanguage
dc.contributor.authorTse, THen_HK
dc.date.accessioned2007-03-23T04:52:34Z-
dc.date.available2007-03-23T04:52:34Z-
dc.date.issued1993en_HK
dc.identifier.citationIfip Transactions A: Computer Science And Technology, 1993 A-40, p. 189-197en_HK
dc.identifier.issn0926-5473en_HK
dc.identifier.urihttp://hdl.handle.net/10722/43693-
dc.description.abstractTwo conflicting schools of thought have been dominating software engineering education. One school stresses on the popular software development methodologies, but horror stories on poorly designed systems are not uncommon. The other school advocates formal methods, but most practitioners regard them as impractical. We recommend that we should bridge the gap between the formal and informal by bringing theory to existing practice. The formalism should be used as a working tool behind popular software development methodologies. Students should not be trained as craftsmen who consider software development as an art and learn only from past mistakes. Nor should they be trained as mathematicians who are more comfortable with theory than applications. Software engineers must be educated as real 'engineers' who are competent with industrial practices as well as the mathematical foundation directly supporting them.en_HK
dc.format.extent67982 bytes-
dc.format.extent161620 bytes-
dc.format.mimetypeapplication/pdf-
dc.format.mimetypeapplication/pdf-
dc.languageengen_HK
dc.publisherElsevier BV.en_HK
dc.relation.ispartofIFIP Transactions A: Computer Science and Technologyen_HK
dc.rightsCreative Commons: Attribution 3.0 Hong Kong License-
dc.titleFormal or informal, practical or impractical: towards integrating formal methods with informal practices in software engineering educationen_HK
dc.typeArticleen_HK
dc.identifier.openurlhttp://library.hku.hk:4550/resserv?sid=HKU:IR&issn=0926-5473&volume=40&spage=189&epage=197&date=1993&atitle=Formal+or+informal,+practical+or+impractical:+towards+integrating+formal+methods+with+informal+practices+in+software+engineering+educationen_HK
dc.identifier.emailTse, TH: thtse@cs.hku.hken_HK
dc.identifier.authorityTse, TH=rp00546en_HK
dc.description.naturepostprinten_HK
dc.identifier.scopuseid_2-s2.0-0027757990en_HK
dc.identifier.issueA-40en_HK
dc.identifier.spage189en_HK
dc.identifier.epage197en_HK
dc.publisher.placeNetherlandsen_HK
dc.identifier.scopusauthoridTse, TH=7005496974en_HK

Export via OAI-PMH Interface in XML Formats


OR


Export to Other Non-XML Formats