Module Database Search
| MODULE DESCRIPTOR | |||
|---|---|---|---|
| Module Title | |||
| Software Engineering | |||
| Reference | CM2708 | Version | 2 |
| Created | August 2020 | SCQF Level | SCQF 8 |
| Approved | June 2017 | SCQF Points | 30 |
| Amended | September 2020 | ECTS Points | 15 |
| Aims of Module | |||
|---|---|---|---|
| To provide a context for software engineering within the work-based learning environment that includes software models, tools and design patterns that satisfies industry standards for the delivery of software projects in a business environment. | |||
| Learning Outcomes for Module | |
|---|---|
| On completion of this module, students are expected to be able to: | |
| 1 | Create appropriate models for the structure and behaviour of software products. |
| 2 | Organise, prioritise and validate requirements per criteria such as feasibility, clarity, testable, freedom from ambiguity, etc. in order to meet customer requirements. |
| 3 | Work in an agile manner and produce relevant documentation on an iterative basis to satisfy a project brief. |
| 4 | Be aware of common pitfalls and mitigations of software engineering and software architecture for business. |
| Indicative Module Content |
|---|
| A review of different software development lifecycles, contrasting the activities performed in each phase. An introduction to tools used in software engineering (e.g. activity diagrams and flowcharts) as well as types of project plans (e.g. Gantt charts, sprint backlogs) including working in an agile manner (e.g. user stories, acceptance tests, scrums). Real world case studies from business. |
| Module Delivery |
|---|
| This module uses the following delivery modes: Guided study (lectures, tutorials, and other learning materials delivered through VLE + bibliography), mentored practical work undertaken in the workplace, project work in the workplace including a design brief, personal study, group reflective sessions via VLE and at RGU Key concepts are introduced and illustrated through lectures (physical and virtual). Theory is put into practice in the workplace guided by a mentor. The understanding of students is tested and further enhanced through virtual interactive labs and tutorials. |
| Indicative Student Workload | Full Time | Part Time |
|---|---|---|
| Contact Hours | 30 | N/A |
| Non-Contact Hours | 30 | N/A |
| Placement/Work-Based Learning Experience [Notional] Hours | 240 | N/A |
| TOTAL | 300 | N/A |
| Actual Placement hours for professional, statutory or regulatory body | 240 |
| ASSESSMENT PLAN | |||||
|---|---|---|---|---|---|
| If a major/minor model is used and box is ticked, % weightings below are indicative only. | |||||
| Component 1 | |||||
| Type: | Coursework | Weighting: | 100% | Outcomes Assessed: | 1, 2, 3, 4 |
| Description: | Written coursework. | ||||
| MODULE PERFORMANCE DESCRIPTOR | |
|---|---|
| Explanatory Text | |
| The calculation of the overall grade for this module is based on 100% weighting of C1. An overall minimum grade of D is required to pass the module. | |
| Module Grade | Minimum Requirements to achieve Module Grade: |
| A | The student needs to achieve an A in C1. |
| B | The student needs to achieve a B in C1. |
| C | The student needs to achieve a C in C1. |
| D | The student needs to achieve a D in C1. |
| E | The student needs to achieve an E in C1. |
| F | The student needs to achieve an F in C1. |
| NS | Non-submission of work by published deadline or non-attendance for examination |
| Module Requirements | |
|---|---|
| Prerequisites for Module | Successful completion of Stage 1 or equivalent. |
| Corequisites for module | None. |
| Precluded Modules | None. |
| INDICATIVE BIBLIOGRAPHY | |
|---|---|
| 1 | SOMMERVILLE, I., 2015. Software Engineering. 10th edition. Pearson |
| 2 | PRESSMAN, R.S., 2014. Software Engineering: A Practitioner's Approach. 8th edition. McGraw-Hill Higher Education. |
| 3 | Seacord, R., Plakosh, D., Lewis, G. A., 2003, Modernizing Legacy Systems: Software Technologies, Engineering Process and Business Practices, Addison-Wesley Longman Publishing Co., Inc. Boston, MA, USA |
| 4 | BASS, L., CLEMENTS, P. and KAZMAN, R., 2012. Software Architecture in Practice. Addison Wesley. |
| 5 | BOURQUE, P. AND FAIRLEY, R.E., 2014. Guide to the software engineering body of knowledge (SWEBOK (R)): Version 3.0. IEEE Computer Society Press. |
| 6 | BRAUDE, E.J. AND BERNSTEIN, M.E., 2016. Software engineering: modern approaches. Waveland Press. |