Undergraduate Programme and Module Handbook 2011-2012 (archived)
Module ENGI4291: COMPUTER SYSTEMS
Department: Engineering
ENGI4291: COMPUTER SYSTEMS
Type | Tied | Level | 4 | Credits | 20 | Availability | Available in 2011/12 | Module Cap | None. | Location | Durham |
---|
Tied to | H130 |
---|---|
Tied to | H610 |
Tied to | H640 |
Prerequisites
- ( ENGI3361 Electronics, and ENGI3321 Software Engineering and Communications) OR ( MEng(Overseas))
Corequisites
- None.
Excluded Combination of Modules
- None.
Aims
- This module is for students intending to fulfil the requirements of the MEng streams in Electronic Engineering (H610), Computer Engineering (H130) and Communications Engineering (H640).
- The module will provide graduates with advanced knowledge and understanding of Computer Architecture and Software Engineering.
- The module is complemented by the 60 credit MEng Research and Development project module or by the 40 credit Technical Project where the final year MEng student has the opportunity to apply the material taught in this module in a large scale project.
- The module provides a firm foundation for a broad range of careers in Electronics, Computer Systems, Communications and General Engineering through an appropriate combination of core and optional modules.
Content
- Elements of embedded computer systems
- Current processor characteristics and designs
- Memory Systems
- Instruction set design
- Collaborative software development and tools
- Universal Modelling Language (UML)
- Trustworthy software, reliability and safety critical system
- Critical systems development and assurance
- Verification, Validation and testing
- Distributed systems, architectures and web services
Learning Outcomes
Subject-specific Knowledge:
- The ability to understand the operation of computer hardware for embedded systems, and a technical understanding and evaluation of the various options.
- Detailed understanding of the operation of a range of current processors required for advanced systems programming.
- An understanding of the complex performance issues of current computers, and the selection of processors for specific applications
- An understanding of how tools such as CVS can support team work in software production.
- An understanding of how UML is used to design software, and the facilities UML tools can provide.
Subject-specific Skills:
- The ability to understand the operation of computer hardware for embedded systems, and a technical understanding and evaluation of the various options.
- Detailed understanding of the operation of a range of current processors required for advanced systems programming.
- An understanding of the complex performance issues of current computers, and the selection of processors for specific applications
- An understanding of how tools such as CVS can support team work in software production.
- An understanding of how UML is used to design software, and the facilities UML tools can provide.
- An in-depth knowledge and understanding of specialist and advanced technical and professional skills, an ability to perform critical assessment and review and an ability to communicate the results of their work effectively.
Key Skills:
- Capacity for independent self-learning within the bounds of professional practice.
- Highly specialised hardware and software skills appropriate to computer engineers.
- Highly specialised skills to design large scale hardware and software systems.
Modes of Teaching, Learning and Assessment and how these contribute to the learning outcomes of the module
- The courses in Computer Architecture and Software Engineering are covered in lectures and are reinforced by design based problem sheets, leading to the required design and problem solving capability.
- Students are able to make use of staff ‘Tutorial Hours’ to discuss any aspect of the module with teaching staff on a one-to-one basis.
- Written timed examinations are appropriate because of the wide range of in-depth technical material covered in this module and to demonstrate the ability to solve advanced problems independently.
Teaching Methods and Learning Hours
Activity | Number | Frequency | Duration | Total/Hours | |
---|---|---|---|---|---|
Lectures | 38 | 2 per week | 1 Hour | 38 | |
Seminars | 2 | 2 per week (week 20) | 1 Hour | 2 | |
Tutorials | 4 | 8 per module | up to 1 hour | 4 | |
Reading and work on set problem | 156 | ||||
Total | 200 |
Summative Assessment
Component: Examination | Component Weighting: 100% | ||
---|---|---|---|
Element | Length / duration | Element Weighting | Resit Opportunity |
Computer Architecture | 2 hours | 50% | no |
Software Engineering | 2 hours | 50% | no |
Formative Assessment:
None
■ Attendance at all activities marked with this symbol will be monitored. Students who fail to attend these activities, or to complete the summative or formative assessment specified above, will be subject to the procedures defined in the University's General Regulation V, and may be required to leave the University