Show simple item record  

dc.contributor.authorBowen, Judy
dc.contributor.authorReeves, Steve
dc.date.accessioned2013-11-26T20:15:52Z
dc.date.available2013-11-26T20:15:52Z
dc.date.copyright2008-06-16
dc.date.issued2008
dc.identifier.citationBowen, J., & Reeves, S. (2008). Formal models for user interface design artefacts. Innovations in Systems and Software Engineering, 4(2), 125-141.en_NZ
dc.identifier.urihttps://hdl.handle.net/10289/8239
dc.description.abstractThere are many different ways of building software applications and of tackling the problems of understanding the system to be built, designing that system and finally implementing the design. One approach is to use formal methods, which we can generalise as meaning we follow a process which uses some formal language to specify the behaviour of the intended system, techniques such as theorem proving or model-checking to ensure the specification is valid (i.e., meets the requirements and has been shown, perhaps by proof or other means of inspection, to have the properties the client requires of it) and a refinement process to transform the specification into an implementation. Conversely, the approach we take may be less structured and rely on informal techniques. The design stage may involve jotting down ideas on paper, brainstorming with users etc. We may use prototyping to transform these ideas into working software and get users to test the implementation to find problems. Formal methods have been shown to be beneficial in describing the functionality of systems, what we may call application logic, and underlying system behaviour. Informal techniques, however, have also been shown to be useful in the design of the user interface to systems. Given that both styles of development are beneficial to different parts of the system we would like to be able to use both approaches in one integrated software development process. Their differences, however, make this a challenging objective. In this paper we describe models and techniques which allow us to incorporate informal design artefacts into a formal software development process.en_NZ
dc.language.isoenen_NZ
dc.publisherSpringeren_NZ
dc.relation.ispartofInnovations in Systems and Software Engineering
dc.relation.urihttp://link.springer.com/article/10.1007%2Fs11334-008-0049-0en_NZ
dc.subjectformal methodsen_NZ
dc.subjectuser-centred designen_NZ
dc.subjectrefinementen_NZ
dc.subjectuser interfacesen_NZ
dc.titleFormal models for user interface design artefactsen_NZ
dc.typeJournal Articleen_NZ
dc.identifier.doi10.1007/s11334-008-0049-0en_NZ
dc.relation.isPartOfInnovations in Systems and Software Engineeringen_NZ
pubs.begin-page125en_NZ
pubs.editionJuneen_NZ
pubs.elements-id32992
pubs.end-page141en_NZ
pubs.issue2en_NZ
pubs.volume4en_NZ


Files in this item

FilesSizeFormatView

There are no files associated with this item.

This item appears in the following Collection(s)

Show simple item record