{"title":"Teaching a capstone subject in computing science- a variety engineering approach","authors":"Brian Lederer, V. Plekhanova, C. Jay","doi":"10.1109/ACSC.2000.824392","DOIUrl":null,"url":null,"abstract":"Software Development Case Study is a capstone subject in the BSc (Computing) degree at the University of Technology, Sydney. Its purpose is to give students as realistic an experience as possible of working in an IT industry environment on software development. At the same time we are trying to ensure that certain educational aims, such as students being exposed to programming in the large and having a sense of engaging with this task and completing it, are met. In analysing the way we run the course we use Ashby's concept of requisite variety: that for a system's essential variables (subject coordinator) must be able to deploy enough variety (or manoeuvres) to match that of the system being regulated (class). In our case the regulatory variety relates to the type and complexity of the projects on offer as well as to the project roles; this has to match the variety of vocational needs and interests brought to us by the students. We give examples of how conflicts, e.g. between educational and industrial aims, can trigger the emergence of new regulatory variety (such as specialised approaches to the task). We also describe how the coordinator's regulatory variety is amplified by involving the students: e.g. in the framing of the project requirements, where we solicit input from the students via proposals: or in the running of the teams, where the students manage themselves but with monitoring by liaison officers. This student-centred approach is designed to promote project ownership and team responsibility. Although it also produces greater task uncertainty than the students are used to it provides them with greater opportunities for exploration and creativity.","PeriodicalId":304540,"journal":{"name":"Proceedings 23rd Australasian Computer Science Conference. ACSC 2000 (Cat. No.PR00518)","volume":"185 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2000-01-31","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"4","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings 23rd Australasian Computer Science Conference. ACSC 2000 (Cat. No.PR00518)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ACSC.2000.824392","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 4
Abstract
Software Development Case Study is a capstone subject in the BSc (Computing) degree at the University of Technology, Sydney. Its purpose is to give students as realistic an experience as possible of working in an IT industry environment on software development. At the same time we are trying to ensure that certain educational aims, such as students being exposed to programming in the large and having a sense of engaging with this task and completing it, are met. In analysing the way we run the course we use Ashby's concept of requisite variety: that for a system's essential variables (subject coordinator) must be able to deploy enough variety (or manoeuvres) to match that of the system being regulated (class). In our case the regulatory variety relates to the type and complexity of the projects on offer as well as to the project roles; this has to match the variety of vocational needs and interests brought to us by the students. We give examples of how conflicts, e.g. between educational and industrial aims, can trigger the emergence of new regulatory variety (such as specialised approaches to the task). We also describe how the coordinator's regulatory variety is amplified by involving the students: e.g. in the framing of the project requirements, where we solicit input from the students via proposals: or in the running of the teams, where the students manage themselves but with monitoring by liaison officers. This student-centred approach is designed to promote project ownership and team responsibility. Although it also produces greater task uncertainty than the students are used to it provides them with greater opportunities for exploration and creativity.
软件开发案例研究是悉尼科技大学(University of Technology, Sydney)理学士(计算机)学位的一个顶点课程。它的目的是给学生提供尽可能真实的在IT行业环境中从事软件开发工作的经验。与此同时,我们也在努力确保某些教育目标得到满足,比如让学生接触到大量的编程,并有一种参与这项任务并完成它的感觉。在分析我们运行课程的方式时,我们使用了阿什比的必要多样性概念:对于一个系统的基本变量(主体协调者),必须能够部署足够的多样性(或策略),以匹配被调节的系统(类)。在我们的案例中,监管的多样性与所提供项目的类型和复杂性以及项目角色有关;这与学生给我们带来的各种职业需求和兴趣相匹配。我们举例说明冲突,例如教育和工业目标之间的冲突,如何引发新的监管品种的出现(例如对任务的专门方法)。我们还描述了如何通过学生的参与来扩大协调员的监管多样性:例如,在项目要求的框架中,我们通过提案征求学生的意见;或者在团队的运行中,学生管理自己,但由联络官监督。这种以学生为中心的方法旨在促进项目所有权和团队责任。虽然它也产生了比学生习惯的更大的任务不确定性,但它为他们提供了更多的探索和创造的机会。