| Semester 1 Credit Value: | 30 |
| ECTS Credits: | 15.0 |
N/A
| Code | Title |
|---|---|
| CSC1031 | Fundamentals of Computing |
| CSC1032 | Computer Systems Design and Architectures |
| CSC1033 | Foundations of Data Science |
In this module students will apply, material covered in the co-requisites in a practical situation using synoptic assessment. As such it will provide coherence to all material covered in Stage 1.
By the end of this module students will have gained, at an introductory level, experience in, and a knowledge of the basic concepts of all stages of the software engineering lifecycle, namely requirements analysis, design, coding, testing and maintenance. Particular emphasis will be placed on the development of programming skills. An active learning, problem-based approach will be adopted. Students will be given a series of practical problems that relate to various stages of the software engineering lifecycle. Supplementary lectures and online materials will introduce the topics to be tackled, and how to tackle them. Topics will be selected broadly from across computing, thus giving students practical enrichment of that material, and/or to specialisms that can be studied at Stages 2 and 3 (HCI, Security, Bio, Trends in Pervasive Computing, Games, Software Engineering, Data Analytics). Students will have gained awareness of the legal, social, ethical and professional aspects of being a practising software engineer.
• An introduction to all stages of the software engineering lifecycle.
• An introduction to general principles of programming languages and their realisation in a representative
language.
• An introduction to the legal, social, ethical and professional aspects of being a software engineer.
After completing this module students will be able to articulate, at a basic level, the wider engineering context that applies to developing complex software system and will be able to:
• Explain fundamental programming constructs such as assignments, conditionals, loops and functions
• Describe appropriate style rules for formatting and documenting legible and maintainable software
• Assess the suitability of software structures for an application
• Describe the software engineering lifecycle and identify its stages.
• Recognise the legal, social, ethical and professional issues arising in real situations.
• Identify and select online sources of supporting material relevant to their project work
• Report on the processes involved in developing software
After completing this module students will, at a fundamental level, be able to tackle all aspects of the software engineering lifecycle. They will be able to:
• Analyse a problem in order to identify, in a succinct way, a user’s requirements
• Prepare a specification meeting a set of requirements
• Produce a design from their own and other suitable specifications
• Translate a design into a well formatted and documented piece of software
• Develop and deploy an appropriate testing strategy
• Choose and use appropriate techniques to debug an existing software system
• Modify an existing software system to extend its functionality.
• Appraise and employ online sources at all stages of the software engineering lifecycle
| Category | Activity | Number | Length | Student Hours | Comment |
|---|---|---|---|---|---|
| Scheduled Learning And Teaching Activities | Lecture | 22 | 1:00 | 22:00 | Lectures |
| Guided Independent Study | Assessment preparation and completion | 22 | 3:00 | 66:00 | Practical follow up, includes time for formative exercises |
| Structured Guided Learning | Lecture materials | 22 | 1:00 | 22:00 | Lecture Follow up |
| Guided Independent Study | Assessment preparation and completion | 3 | 20:00 | 60:00 | The Software Artefacts |
| Scheduled Learning And Teaching Activities | Practical | 22 | 2:00 | 44:00 | Practicals |
| Guided Independent Study | Independent study | 1 | 86:00 | 86:00 | Background reading and/or optional drop-in sessions |
| Total | 300:00 |
Lectures materials will be used to introduce each project, and aspects of software engineering, particularly programming. During their independent study time, students will review online materials providing further support for development of programming skills. They will also use this time to attempt the problems set.
For each topic/problem students will provide a software artefact that contributes to their portfolio of evidence of the activities they have undertaken.
The lectures and practical sessions will provide support for developing the skills.
The format of resits will be determined by the Board of Examiners
| Description | Semester | When Set | Percentage | Comment |
|---|---|---|---|---|
| Case study | 1 | M | 100 | Three Software Artefacts equivalent to 3000 words |
| Description | Semester | When Set | Comment |
|---|---|---|---|
| Prob solv exercises | 1 | M | Practical/Tutorial exercises (not submitted) |
Students will produce a portfolio of evidence demonstrating that they have mastered practical skills in software development applied to a variety of problems chosen to reflect real world applications but targeted at the skill level of the students when the work is set.
Three software artifacts equivalent to 3000 words total will be required. Each artefact will also contain a reflective report on the skills gained.
Students will be given a range of formative exercises to introduce them to relevant tools, develop their understanding of programming concepts and provide them with the opportunity to gain experience through practical application.
N/A
Disclaimer: The information contained within the Module Catalogue relates to the 2023/24 academic year. In accordance with University Terms and Conditions, the University makes all reasonable efforts to deliver the modules as described. Modules may be amended on an annual basis to take account of changing staff expertise, developments in the discipline, the requirements of external bodies and partners, and student feedback. Module information for the 2024/25 entry will be published here in early-April 2024. Queries about information in the Module Catalogue should in the first instance be addressed to your School Office.