Module title: Error with Module:
System.NullReferenceException: Object reference not set to an instance of an object. at ModuleCatalogue.Napier.MC.Occurrences.Occurrences.GetOccurrenceStudentActivities(StringBuilder plh, String strModuleID, String strOccID, String PSLCode, String AYRCode) at ModuleCatalogue.Napier.MC.Occurrences.Occurrences.CreateAccordionContent(OccurranceDetails cls, String strModuleID) at ModuleCatalogue.Napier.MC.Occurrences.Occurrences.SelectModuleOccurrences(String strModuleID, Accordion ac) at ModuleCatalogue.WebForm2.setupdetails(String ModuleID, String SearchText)


SCQF level: 11:
SCQF credit value: 40.00
ECTS credit value: 20

Module code: SET11516
Module leader: Sally Smith
School School of Computing
Subject area group: Software Engineering
Prerequisites

SOC10101

Timetables
2018/9, Trimester 1, Face-to-Face, Edinburgh Napier University
Occurrence: 001
Primary mode of delivery: Face-to-Face
Location of delivery: MERCHISTON
Partner: Edinburgh Napier University
Member of staff responsible for delivering module: Sally Smith
Module Organiser:


Learning, Teaching and Assessment (LTA) Approach:
This 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].
Assessment (formative or summative)
The first assessment will be a business plan and will be assessed by a pitch for a contract and a report (LOs 1 and 2). The second assessment will be a requirements specification (LOs 2 and 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 (LOs 3, 4 and 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 out with their control.

Formative Assessment:
The University is currently undertaking work to improve the quality of information provided on methods of assessment and feedback. Please refer to the section on Learning and Teaching Approaches above for further information about this module’s learning, teaching and assessment practices, including formative and summative approaches.

Summative Assessment:
The University is currently undertaking work to improve the quality of information provided on methods of assessment and feedback. Please refer to the section on Learning and Teaching Approaches above for further information about this module’s learning, teaching and assessment practices, including formative and summative approaches.

Student Activity (Notional Equivalent Study Hours (NESH))
Mode of activityLearning & Teaching ActivityNESH (Study Hours)
Face To Face Lecture 12
Independent Learning Guided independent study 358
Face To Face Centrally Time Tabled Examination 30
Total Study Hours400
Expected Total Study Hours for Module400


Assessment
Type of Assessment Weighting % LOs covered Week due Length in Hours/Words
Oral Presentation 20 1,2 8 HOURS= 20, WORDS= 0
Project - Written 28 3, 4, 5 28 HOURS= 80, WORDS= 0
Component 1 subtotal: 48
Component 2 subtotal: 0
Module subtotal: 48

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 out with 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:

Upon completion of this module you will be able to

LO1: Research new and existing markets for software development business ideas or application areas

LO2: Develop an appropriate business model to sustain the application development process

LO3: 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 evaluation

LO5: Critically evaluate their graduate attributes and work with a mentor/coach to enhance them

Indicative References and Reading List - URL:

Core - TESTA (2009) GROWING SOFTWARE: PROVEN STRATEGIES FOR MANAGING SOFTWARE ENGINEERS: BIG STRATEGIES FOR MANAGING SOFTWARE COMPANIES, 2009th ed. - ISBN: 9781593271831
Core - HASSAN, DUBINSKY (2008) AGILE SOFTWARE ENGINEERING: SPRINGER, 2008th ed. - ISBN: 1397818480019
Click here to view the LibrarySearch.