Link to University of Stirling home page Link to Computing Science and Mathematics home page
Link to University of Stirling home page
University | Computing Science | Modules | CSCU9P6 | Syllabus
CSCU9P6 Software Engineering II Spring 2017
menu CSCU9P6 Spring 2017
Software Engineering II

Home

Organisation

Reference

 

Syllabus

Lecturers

Dr Savi Maharaj (Coordinator), Room 4B68, Email:

Dr Simon Jones, Room 4B63, Email:

Prerequisites: CSC9P5 or CSCU9P5: understanding the basic software life-cycle, the role of requirements analysis, specification and design

Credits: 20 credits at SCQF level 10

Learning Outcomes

Students should be able to apply techniques for:

  • Software Implementation;
  • Formal Specification.

Students should be aware of current ideas and good practice regarding Project Management and Quality Assurance, in the context of software development.

Students will be required to demonstrate the ability to apply theory and techniques to unseen problems without reference to notes, and to work independently and under a time constraint.

Transferable Skills

  • An understanding of the problems of teamwork, and how to work effectively in a team;
  • Skills in the design and implementation of systems;
  • An understanding of the management of engineering complex systems;
  • The ability to formulate problems at an appropriate level of abstraction.

Contents
  • Software Implementation (10 lectures, 4 practicals)
    • Detailed implementation: associations, use case, sequence and state diagrams;
    • Refactoring designs;
    • Using design patterns;
    • The MVC architecture;
    • Build control, version control, collaborative working;
    • Testing, debugging;

  • Software Engineering Mathematics and Specification (10 lectures, 6 practicals)
    • Mathematical modelling;
    • Sets, relations and sequences;
    • Logic;
    • Formal specification with Alloy.

  • Project Management and Quality Assurance (4 seminars)
    • Topics may include Software quality assurance, Process and project metrics, Project Planning, Risk analysis, Risk management, Scheduling and tracking.

Assessment
  • Group project (35%)
  • Practical checkpoints (15%)
  • Examination (50%)
Requirements

In order to be eligible to pass the module, students must:

  • Participate in the group project and submit all required components.
  • Give the seminar presentation
  • Attend the examination

Coursework extensions

Students who can show good cause may be permitted extensions to coursework deadlines. "Good cause" may include illness, for which a medical certificate or other evidence will be required. Students must request an extension by contacting the module coordinator, supplying relevant evidence, no later than seven days after the published assignment deadline. Extensions will be granted for acceptable reasons only, and will not normally be beyond such time as solutions and feedback are returned to the rest of the class. [See Section 6.2.6 of the Academic Policy Handbook]

Late submission of coursework

Coursework that is submitted late will be accepted up to seven days after the published deadline (or expiry of any agreed extension) but the mark will be lowered by three marks per day or part thereof. After seven days the piece of work will be deemed a non-submission. [See paragraph 66-68 of the Undergraduate Regulations on Assessment]

Repeat assessments

Students who fulfil the module requirements but obtain an overall fail mark (0-39) are eligible for repeat assessment. Repeats are not permitted for laboratory checkpoints or group work. The mark following any repeat assessment is capped at 40 and will not be lower than the original mark.

Discretionary repeat assessments

In exceptional circumstances, a student who has not met all the module requirements, following the Main examination period, may be permitted a discretionary repeat. Repeats are not permitted for laboratory checkpoints or group work. The mark following any repeat assessment is capped at 40. If you are granted a discretionary repeat assessment but do not attempt it, you will be awarded grade X for the module.

In deciding whether to grant a discretionary repeat, the Examiners will consider your record of attendance and engagement in the module. Students with a poor attendance record will not normally be permitted a discretionary repeat.

Deferred examinations

If a student is unable to attend the main examination, he/she must apply for a deferred examination, using the link on the Student Portal. If a deferred examination is not granted and the student does not attend the main examination, he/she will be deemed not to have met the module requirements. [See http://www.stir.ac.uk/registry/studentinformation/exams/deferredexams/]

Textbooks

  • Software Engineering (9th edition, 2010), I Sommerville. Pearson, ISBN 0-137-05346-0 (recommended).
  • Using UML: Software Engineering with Objects and Components (2nd edition), P Stevens, Addison-Wesley, 2006, ISBN 0-321-26967-5 (recommended).
  • UML Distilled, 3rd Edition, Martin Fowler, Addison Wesley 2003, ISBN13: 9780321193681, ISBN10: 0321193687
  • Software Abstractions, 2nd edition, D Jackson, MIT Press, 2011, ISBN 0262017156 (recommended)
  • Software Project Management, 5th or 4th edition, Hughes and Cotterell, McGraw-Hill (highly recommended)

Email savi@cs.stir.ac.uk - Web www.cs.stir.ac.uk/~sma - Tel 01786 467445 - Fax 01786 464551
Mail Computing Science and Mathematics, University of Stirling, Stirling, Scotland, FK9 4LA
Contact Details