Pub Date : 1900-01-01DOI: 10.1109/ACSC.2000.824403
H. Purchase
Peer assessment is recognised as a useful learning activity, not merely as a means by which assignments can be marked. In a design subject such as human-computer interaction, peer-assessment offers a unique opportunity for students to be exposed to a wide range of different designs in an environment that ensures that they reflect on these designs. However, it is important that the marking criteria are well specified and unambiguous. This paper reports on the use of peer-assessment as an appropriate learning activity for revealing the wide range of design issues and dimensions in interface design, where formal marking is based on clear, functional criteria. Subjective consideration of the interfaces is encouraged through a ranking system and the subsequent elicitation of interface design principles. The successful implementation and acceptance of this scheme demonstrates its benefits both as a learning activity and as an opportunity for student reflection.
{"title":"Peer assessment: encouraging reflection on interface design","authors":"H. Purchase","doi":"10.1109/ACSC.2000.824403","DOIUrl":"https://doi.org/10.1109/ACSC.2000.824403","url":null,"abstract":"Peer assessment is recognised as a useful learning activity, not merely as a means by which assignments can be marked. In a design subject such as human-computer interaction, peer-assessment offers a unique opportunity for students to be exposed to a wide range of different designs in an environment that ensures that they reflect on these designs. However, it is important that the marking criteria are well specified and unambiguous. This paper reports on the use of peer-assessment as an appropriate learning activity for revealing the wide range of design issues and dimensions in interface design, where formal marking is based on clear, functional criteria. Subjective consideration of the interfaces is encouraged through a ranking system and the subsequent elicitation of interface design principles. The successful implementation and acceptance of this scheme demonstrates its benefits both as a learning activity and as an opportunity for student reflection.","PeriodicalId":304540,"journal":{"name":"Proceedings 23rd Australasian Computer Science Conference. ACSC 2000 (Cat. No.PR00518)","volume":"26 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125004643","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1900-01-01DOI: 10.1109/ACSC.2000.824408
Graeme Smith
The stepwise development of a program using refinement requires that the original abstract specification is realisable, i.e., an implementation exists with identical functionality. In some situations, this may not be desirable or even possible, and an ideal specification which is only approximated by the final implementation is used. For these specifications, an informal step, based on the developer's knowledge and experience, is typically used during the refinement process in order to transform the specification to one which is realisable. This paper introduces a formal approach to such specification transformations called realisation. It enables a specification to be transformed to another with different functionality and, at the same time, allows properties of the new specification to be derived from those of the original.
{"title":"Stepwise development from ideal specifications","authors":"Graeme Smith","doi":"10.1109/ACSC.2000.824408","DOIUrl":"https://doi.org/10.1109/ACSC.2000.824408","url":null,"abstract":"The stepwise development of a program using refinement requires that the original abstract specification is realisable, i.e., an implementation exists with identical functionality. In some situations, this may not be desirable or even possible, and an ideal specification which is only approximated by the final implementation is used. For these specifications, an informal step, based on the developer's knowledge and experience, is typically used during the refinement process in order to transform the specification to one which is realisable. This paper introduces a formal approach to such specification transformations called realisation. It enables a specification to be transformed to another with different functionality and, at the same time, allows properties of the new specification to be derived from those of the original.","PeriodicalId":304540,"journal":{"name":"Proceedings 23rd Australasian Computer Science Conference. ACSC 2000 (Cat. No.PR00518)","volume":"26 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123122126","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}