COM4013 - Introduction to Software Development

Objectives:

Assessment tasks are designed to enable students to demonstrate the Learning and Employability outcomes for the relevant level of study. Level Learning Outcomes are embedded in the assessment task(s) at that level. This enables a more integrated view of overall student performance at each level.

Content:

This is a practice-based module that introduces the fundamentals required to develop software artefacts fit for real-world organisational or commercial purposes. The module will explore three stages of software development: problem specification, programming and architectural design. In the first stage, students are shown how to analyse computing problems, introducing requirements analysis and domain analysis. The second stage covers the design and coding of the software solution, using clear readable code, and processes of behaviour and unit testing. In the final stage, students begin to explore foundational principles of development practices (standards, software components and protocols) and software architecture (architectural analysis, architectural styles, and agile software development), which will start to prepare them for tackling larger scale software projects.

The content covers:
• trends in coding frameworks and elements;
• problem decomposition and programming;
• mathematical algorithms and computing problems;
• writing modular code and adopting relevant stylistic conventions;
• testing in project planning and implementation.

Learning and Teaching Information:

Workshops
Hours: 60
Intended Group Size: Cohort

Guided independent study
Hours: 240

Further details relating to assessment
Portfolio: Students evidence progression on the module in the form of an e-portfolio of computer programs, such as games and utilities, composed of polished, documented and extended versions of exercises started during the sessions.
Project: Students are presented with a problem for which they must find an algorithmic solution and implement that solution in code. Furthermore, the problem will be presented in the context of a real-world application. Hence, a secondary aim of the project will be to integrate their algorithmic solution within an existing software application. The application may be one they have developed in COM4003 Introduction to Tech Stack. The problem should require the application of basic mathematics. Finally, a third aim will be to devise an appropriate strategy for testing the behaviour and/or performance of the algorithm, both in isolation from the rest of the application codebase and after its integration.

Project report: The report documents the student’s problem-solving process and should detail any relevant theory.

Suggested structure:
A statement of how the software artefact design provides an effective solution to the given computing problem including mathematical notation where applicable.
An account of the development and implementation of the software artefact.
Evidence of a testing strategy.
A critical evaluation of the development process and resulting software artefact, including its design and workability.

Unseen/closed book Examination: The alternative assessment outlined above is for use by overseas franchises partners that require an unseen/closed book exam option. In this instance, the exam should assess the students’ general knowledge of topics covered on the module as well as facilitating their critical analysis of approaches taken in their project work. A combination of multiple choice and essay-based questions is included.

Formative assessment will be used to support the skills that contribute to the assessment. Formative assessment may include coding labs, design and modelling tasks, case study presentations, short quizzes, or specific research tasks. Formative feedback will be an ongoing process within class sessions.

Full details are available in the Module Handbook.

For students studying at Leeds Trinity campus, there are variations to the Taught Programme Academic Regulations, as required by the accrediting body, and these variations are contained within Additional Regulations.

Assessment:

001 Portfolio; artefact (1,500-word equivalent); mid semester 2 20%
002 Project; artefact (3,000-word equivalent); end of semester 2 60%
003 Project report; 1.500 words; end of semester 2 20%
200 Project; artefact (3,000-word equivalent); end of semester 2 70%
201 Project report; 1.500 words; end of semester 2 30%

Fact File

Module Coordinator - Jim Diokou
Level - 4
Credit Value - 30
Pre-Requisites - NONE
Semester(s) Offered - 4YL

Click here to go back to previous page