Academic Handbook BSc (Hons) Applied Digital and Technology Solutions (online)
Software Engineering Course Descriptor
Last modified on March 13th, 2023 at 5:24 pm
Course Title | Software Engineering | Faculty | EDGE, Innovation Unit (London) |
Course code | NCHNAL6121 | Teaching Period | This course will typically be delivered over a 6-week period. |
Credit points | 15 | Date approved | March 2021 |
FHEQ level | 6 | ||
Compulsory/ Optional |
Compulsory for Business Analyst Specialism | ||
Pre-requisites | None | ||
Co-requisites | None |
Course Summary
This course covers the foundations of software engineering, including software development life cycle models (e.g., waterfall, spiral, agile); requirements analysis; user-centred design; software design principles and patterns; testing (functional testing, structural testing, testing strategies); code refactoring and debugging; software architecture and design; and integration and deployment.
Course Aims
- Train learners in the design principles of software engineering.
- Provide learners with the tools to engage with software project management.
- Train learners to understand risk management, software testing, professional practice and documentation.
Learning Outcomes
On successful completion of the course, learners will be able to:
Knowledge and Understanding
K1c | Have critical knowledge and understanding of the design principles behind software development and be able to describe and comment on the state-of-the art developments in the discipline. |
K2c | Have a systematic understanding of the principles behind effective software project management, including planning, requirements gathering, cost-time analysis, resource constraints, regulations, scale-up, deployment, organisation goals and working in teams. |
K3c | Critically understand the role of verification and validation in software engineering. |
Subject Specific Skills
S1c | Apply effective design principles for the development of analytical algorithms and/or software systems and be able to critically evaluate a design approach. |
S2c | Apply in-depth knowledge and understanding to plan, evaluate, test and document a software design. |
S3c | Devise and sustain arguments to solve problems and apply professional project management techniques to plan a project, including people, cost, resources and risk management. |
Transferable and Professional Skills
T1c | Demonstrate project management skills and a professional approach. |
T2c | Effectively communicate to a range of stakeholders through professional documentation. |
T3c | Exercise initiative and personal responsibility to analyse a problem specification and design a solution. |
T3c | Display an advanced level of technical proficiency in written English and competence in applying scholarly terminology, so as to be able to apply skills in critical evaluation, analysis and judgement effectively in a diverse range of contexts. |
Teaching and Learning
This is an e-learning course, taught throughout the year.
This course can be offered as a standalone short course.
Teaching and learning strategies for this course will include:
- On-line learning
- On-line discussion groups
- On-line assessment
Course information and supplementary materials will be available on the College’s Virtual Learning Environment (VLE).
Students are required to attend and participate in all the formal and timetabled sessions for this course. Students are also expected to manage their self-directed learning and independent study in support of the course.
The course learning and teaching hours will be structured as follows:
- Learning and teaching (6 days x 8 hours) = 48 hours
- Independent study = 102 hours
Indicative total learning hours for this course: 150 hours
Assignments (see below) will be completed as part of private study.
Assessment
Formative
Learners will be formatively assessed during the course by means of set assignments. These will not count towards the final degree but will provide learners with developmental feedback.
Summative
AE | Assessment Type | Weighting | Online submission | Duration | Length |
1 | Report (workplace case study) | 60% | Yes | – | 2,000 words +/- 10%, excluding data tables |
2 | Written Assignment | 40% | Yes | – | 1,500 words +/- 10%, excluding data tables |
Feedback
Learners will receive formal feedback in a variety of ways: written (via email or VLE correspondence) and indirectly through online discussion groups. Learners will also attend a formal meeting with their Academic Mentor (and for apprentices, including their Line Manager). These bi- or tri-partite reviews will monitor and evaluate the learner’s progress.
Feedback is provided on summatively assessed assignments and through generic internal examiners’ reports, both of which are posted on the VLE.
Indicative Reading
Note: Comprehensive and current reading lists for courses are produced annually in the Course Syllabus or other documentation provided to learners; the indicative reading list provided below is used as part of the approval/modification process only.
Books
- Sommerville, I., (2010), Software Engineering, Wokingham: Addison-Wesley
- Pezze, M., and Young, M., (2007), Software Testing and Analysis: Process, Principles and Techniques, Hoboken, N.J.: Wiley
- Fairclough, J., (1996), Software engineering, London; New York : Prentice Hall
Journals
Learners are encouraged to consult relevant journals on software engineering.
Electronics Resources
Learners are encouraged to consult relevant electronic resources on software engineering.
Indicative Topics
- Software design principles
- Software project management
- Software documentation
Title: NCHNAL6121 Software Engineering Course Descriptor
Approved by: Academic Board Location: Academic Handbook/Programme Specifications and Handbooks/Mobility Courses |
|||||
Version number | Date approved | Date published | Owner | Proposed next review date | Modification (As per AQF4) & category number |
2.0 | December 2022 | March 2023 | Scott Wildman | March 2026 | Category 3: Change to Teaching and Learning Strategy; Change to English Proficiency Learning Outcome.
Category 1: Corrections/clarifications to documents which do not change approved content or learning outcomes. |
1.0 | March 2021 | March 2021 | Scott Wildman | March 2026 |