| Module title: |
Advanced Software Engineering Teamworking
|
| SCQF level: |
11: |
| SCQF credit value: |
40.00 |
| ECTS credit value: |
20
|
| Module code: |
SET11516 |
| Module leader: |
MRS SALLY SMITH |
| School |
Computing |
| Subject area group: |
Software Engineering |
|
Prerequisites
|
|
SOC10101 - Honours Project
|
|
|
 2013/4, Trimester 1, Face-to-Face, Napier University
| Occurrence: | 001 | | Primary mode of delivery: | Face-to-Face | | Location of delivery: | NAPIER | | Member of staff responsible for delivering module: | MRS SALLY SMITH | | Module Organiser: | | | Learning, Teaching and Assessment (LTA) Approach: |
Learning & teaching methods including their alignment to LOsThis module is the culmination of the software engineering practical theme with teams investigating business ideas or competitive application development [LO 1] while independently investigating appropriate business models for ensuring business sustainability [LO 2]. The teams will apply agile software engineering techniques to develop professional applications [LO 3] and critically evaluate their application and individual contribution [LO 4]. The module emphasises teamwork in software development projects with team members talking on specific roles as identified in current professional practice. Account will be taken of individual contributions with the engineering logbook being a significant artefact in assessment [LO 4]. Students will also be coached/ mentored by an existing graduate to evaluate then enhance their graduate attributes [LO 5].Embedding of employability/ PDP/ scholarship skillsStudents will build up a graduating portfolio based on their application development from this module. It will also be linked to the MEng Mentoring Scheme whereby each student has a mentor, normally a previous graduate of the course. Current project development practice will feed into their application development.Assessment (formative and summative)Assessment (formative and summative)The first assessment will be a business plan and will be assessed by a pitch for a contract and a report (LO1,2). The second assessment will be a requirements specification (LO2,3) for the application the team will develop. Extensive feedback will be given to ensure that the team is on track for the design and development of the application. The final assessment (LO3,4,5) will be the application itself and an evaluation of it – the evaluation would be peer review, online reviews for marketed applications or competition judges. The individual element of the assessment would be a completed log book (LO3) containing a full description of their ongoing notes, designs, actions, key findings which must be written up as the project progresses, combined with a critical appraisal of their contribution. In this way individuals will have a chance to make an excellent individual contribution regardless of any issues with their team functioning effectively, if this is outwith their control.Research/ teaching linkagesThe School’s research in software engineering has resulted in Proof of Concept projects, Knowledge Transfer Projects and a spin-out company. The spin-out will be used to demonstrate entrepreneurial success and routes to commercialisation.Supporting equality and diversityThe module will require sensitivity when allocating students to teams to ensure the principles of equality of opportunity are adhered to. There will a large individual element to the assessment to ensure that each student has an opportunity to develop their full potential. InternationalisationTeam interactions will be explored in different cultural contexts to ensure that roles and responsibilities are appropriate and well understood before the work commences. The confident futures team will work with the teams to establish good working relationships. The applications will be developed for an international audience.
| | Student Activity (Notional Equivalent Study Hours (NESH)) | | Mode of activity | Learning & Teaching Activity | NESH (Study Hours) | | FACE TO FACE | Lecture | 12 | | Independent Learning | Individual Learning Activities | 358 | | FACE TO FACE | Other | 30 | | Total Study Hours | 400 | | Expected Total Study Hours for Module | 400 |
| Assessment | | Type of Assessment | Weighting % | LOs covered | Week due | Length in Hours/Words | | OTHER Business Plan and Pitch | 15 | 1,2 | 5 | HOURS= 20 WORDS= | | OTHER Requirements Specification | 15 | 2,3 | 12 | HOURS= 20 WORDS= | | OTHER Application, Evaluation of Pro | 60 | 3,4,5 | 25 | HOURS= 40 WORDS= | | OTHER Log Book | 10 | 3 | 25 | HOURS= 30 WORDS= | | Component 1 subtotal: | 100 | | | Component 2 subtotal: | 0 | | | | | Module subtotal: | 100 | | | |
2012/3, Trimester 2, Face-to-Face, Napier University
| Occurrence: | 002 | | Primary mode of delivery: | Face-to-Face | | Location of delivery: | NAPIER | | Member of staff responsible for delivering module: | MRS SALLY SMITH | | Module Organiser: | | | Learning, Teaching and Assessment (LTA) Approach: |
Learning & teaching methods including their alignment to LOsThis module is the culmination of the software engineering practical theme with teams investigating business ideas or competitive application development [LO 1] while independently investigating appropriate business models for ensuring business sustainability [LO 2]. The teams will apply agile software engineering techniques to develop professional applications [LO 3] and critically evaluate their application and individual contribution [LO 4]. The module emphasises teamwork in software development projects with team members talking on specific roles as identified in current professional practice. Account will be taken of individual contributions with the engineering logbook being a significant artefact in assessment [LO 4]. Students will also be coached/ mentored by an existing graduate to evaluate then enhance their graduate attributes [LO 5].Embedding of employability/ PDP/ scholarship skillsStudents will build up a graduating portfolio based on their application development from this module. It will also be linked to the MEng Mentoring Scheme whereby each student has a mentor, normally a previous graduate of the course. Current project development practice will feed into their application development.Assessment (formative and summative)The first assessment will be a business plan and will be assessed by a pitch for a contract and a report. The second assessment will be a requirements specification for the application the team will develop. Extensive feedback will be given to ensure that the team is on track for the design and development of the application. The final assessment will be the application itself and an evaluation of it – the evaluation would be peer review, online reviews for marketed applications or competition judges. The individual element of the assessment would be a completed log book containing a full description of their ongoing notes, designs, actions, key findings which must be written up as the project progresses, combined with a critical appraisal of their contribution. In this way individuals will have a chance to make an excellent individual contribution regardless of any issues with their team functioning effectively, if this is outwith their control.Research/ teaching linkagesThe School’s research in software engineering has resulted in Proof of Concept projects, Knowledge Transfer Projects and a spin-out company. The spin-out will be used to demonstrate entrepreneurial success and routes to commercialisation.Supporting equality and diversityThe module will require sensitivity when allocating students to teams to ensure the principles of equality of opportunity are adhered to. There will a large individual element to the assessment to ensure that each student has an opportunity to develop their full potential. InternationalisationTeam interactions will be explored in different cultural contexts to ensure that roles and responsibilities are appropriate and well understood before the work commences. The confident futures team will work with the teams to establish good working relationships. The applications will be developed for an international audience.
| | Student Activity (Notional Equivalent Study Hours (NESH)) | | Mode of activity | Learning & Teaching Activity | NESH (Study Hours) | | FACE TO FACE | Lecture | 12 | | Independent Learning | Individual Learning Activities | 358 | | FACE TO FACE | Individual Learning Activities | 30 | | Total Study Hours | 400 | | Expected Total Study Hours for Module | 400 |
| Assessment | | Type of Assessment | Weighting % | LOs covered | Week due | Length in Hours/Words | | OTHER Business Plan and Pitch | 15 | 1,2 | 5 | HOURS= 20 WORDS= | | OTHER Requirements Specification | 15 | 2,3 | 12 | HOURS= 20 WORDS= | | OTHER Application, Evaluation of Pro | 60 | 3,4,5 | 25 | HOURS= 40 WORDS= | | OTHER Log Book | 10 | 3 | 25 | HOURS= 30 WORDS= | | Component 1 subtotal: | 100 | | | Component 2 subtotal: | 0 | | | | | Module subtotal: | 100 | | | |
|
What you will learn and what this module is about:
|
|
Advanced Software Engineering Teamworking aims to develop your graduate attributes through a combination of investigation, competitive software development, graduate mentoring and teamworking. Graduate attributes include: familiarity with advanced techniques and skills, originality in the application of knowledge and the ability to deal with complex issues and make sound judgements in the absence of complete data.The aim is to work in a team to design, develop and test a professional application which could be published, sold or entered into a competition with a view to you demonstrating the graduate attributes identified above while equipping you with employability skills and evidence of achievement.
|
|
Description of module content:
|
|
The module will span two trimesters. In the first trimester there will be a seminar series on teamworking skills which will draw on expertise both from within the School of Computing and outwith the school. Where possible, the school’s entrepreneur in residence will contribute, along with the confident futures team. Each team will investigate a suitable application, develop a business model and engineer its requirements.The second trimester of study will involve design, development, testing and delivery of the application. The delivery could be a presentation at a student conference, an upload to an online market or submission to a competition such as Dare to be Digital or Google’s Summer of Code. Depending on the timescales, the competition may be internally judged.
|
|
Learning Outcomes for module:
|
|
On completion of this module, students will be able to:LO1: Research new and existing markets for software development business ideas or application areasLO2: Develop an appropriate business model to sustain the application development processLO3: Synthesise programme outcomes to work effectively in a team on a complex software development project LO4: Critically evaluate work by incorporating feedback from research or business communities into process and application evaluationLO5: Critically evaluate their graduate attributes and work with a mentor/coach to enhance them
|
|
Indicative References and Reading List - URL:
|
|
T1: Growing Software: Proven Strategies for Managing Software Engineers: Big Strategies for Managing Software Companies, Testa, 2009, 978-1-593-27183-1T2: Agile Software Engineering, Hassan, Dubinsky, 2008, Springer, ISBN-13 978-1848001985
Click here to view this module's reading list. |
|