CSCU9P5 - Software Engineering I
20 credits at SCQF level 10
The student will have:
- a practical understanding of the software engineering life-cycle
- a knowledge of how software projects are planned and managed
- practical skills in methods and tools for software design and testing, with particular reference to object-oriented development using UML for information and system modelling
- an understanding of the issues and consequences of being a professional software engineer, including aspects related to risk and safety
- to demonstrate the ability to apply theory and techniques to unseen problems without reference to notes, to work independently and under a time constraint.
- understanding and use of CASE tools
- planning and managing a software project
- team working
- document preparation.
Systems and Software Engineering: Overall strategy, system and software life-cycles, introduction to modelling, introduction to project management and risk analysis, management tools, small group working.
Requirements Capture and Analysis: general principles, requirements capture methods, notations and methods for requirements modelling.
Object-Oriented Development: general principles, UML (Unified Modelling Language) for Object-Oriented Analysis, Modelling and Development (including: use-cases diagrams, class diagrams, sequence diagrams, state diagrams), use of CASE tools.
Agile Methods: An alternative, iterative approach to software engineering, including Agile and Extreme Programming principles and practical aspects, and testing.
Professional Issues: professional societies, social responsibilities and ethical aspects, professional development, legislation.
- Assignment 1. Individual project, 0% (The assignment does not contribute to the final grade, but submission is required and feedback will be provided);
- Assignment 2. Group project: analysis and high level design (System development - group work 50%; Presentation - individual work 30%; Agile challenge - groupwork 20%) 50%;
- Examination 50%.
In assessing a student's grade for the module, the Examiners require that a student must:
- Submit all items of assessed work.
- Non-submission of any single item of assessed coursework will result in the award of No Grade for the module as a whole.
Assignment 1 is formally included in the set of assessed work, although it will not be graded and will not contribute to the overall grade for the module. Assignment 1 must be submitted in order to get a Pass grade for the module as a whole.
Assessed coursework submitted late will be accepted up to five days after the submission date (or expiry of any agreed extension) but the grade will be lowered by one grade point per day or part thereof. After five days the piece of work will be deemed a non-submission, and will result in the award of No Grade for the module as a whole. This rule may be relaxed for students who can show good cause for failure to submit. ‘Good cause’ may include illness (for which a medical certificate or other evidence will be required).
- Attend the examination and obtain a grade of 4C or higher in it. If a student does not achieve at least 4C in the exam, the overall module grade will be capped at 4A.
- If a student is unable to attend the Main examination, he/she must apply to the Student Programmes Office for a Deferred examination. If a Deferred examination is not granted, then the Examiners may allow a Repeat examination. A student who attends neither the main exam nor the Repeat/Deferred exam will be awarded No Grade for the module as a whole.
The grade awarded following a Repeat examination is capped at 3C.
Attendance by all the components to the group project meetings with a project monitoring officer is required, unless good cause for missing those classes can be shown. Responsibility for showing good cause lies with the student.
Further information and teaching materials for this module.