Durham University
Programme and Module Handbook

Postgraduate Programme and Module Handbook 2011-2012 (archived)

Module COMP50815: SYSTEMS AND REQUIREMENTS ANALYSIS FOR INTERNET SYSTEMS

Department: Computer Science

COMP50815: SYSTEMS AND REQUIREMENTS ANALYSIS FOR INTERNET SYSTEMS

Type Tied Level 4 Credits 15 Availability Available in 2011/12 Module Cap
Tied to G5K109 and G5K114

Prerequisites

  • None.

Corequisites

  • None.

Excluded Combination of Modules

  • None.

Aims

  • The formal capture of requirements for internet-based applications is a key software engineering and business imperative. A number of current techniques exist, each having strengths and weaknesses for particular application types. The module will enable students to be confident with modern tools and techniques for requirements capture and analysis.

Content

  • Software has a component in systems; soft systems; systems definitions and boundaries; different types of model (behaviour, data, process); entities; modelling the software process
  • Requirements analysis. Lifecycle models; waterfall, raid prototype, 'timebox', etc. Formal approaches to requirements analysis and definition; traceability and representation. Elicitation; feasibility. Maintenance. Web based tools
  • Methods for undertaking systems analysis of distributed systems; non-functional aspects; industrial methods; validation and verification. Data dictionaries

Learning Outcomes

Subject-specific Knowledge:
  • Specialist knowledge: advanced knowledge of systems analysis methods (including those used in industry); relationship to lifecycle models. Advanced knowledge of requirements analysis techniques
  • Practical design skills: solving real systems and requirements analysis problems for an internet application. Supporting software tools
  • Engineering of software systems: theoretical and practical knowledge of how requirements and systems analysis impacts and supports the overall software engineering lifecycle model
  • Professional skills: understanding the link between front end lifecycle issues and software maintenance; non-functional requirements. Documentation standards
Subject-specific Skills:
    Key Skills:

      Modes of Teaching, Learning and Assessment and how these contribute to the learning outcomes of the module

      • The module comprises 1 week's intensive directed reading and laboratory exercises; 5 days of lectures, tutorials, and reading, and two weeks undertaking a major laboratory assignment. The overall workload conforms to the standard SLAT requirement of 150 hours equivalent to 15 credits.

      Teaching Methods and Learning Hours

      Activity Number Frequency Duration Total/Hours
      Lectures 10 2 per day in week 2 1 hour 10 ■
      Tutorials 4 weekly 1 hour 4 ■
      Practicals 5 daily in week 1 6 hours 30 ■
      Laboratory 10 daily in weeks 3 and 4 6 hous 60 ■
      Preparation and Reading 46
      Total 150

      Summative Assessment

      Component: Laboratory report Component Weighting: 100%
      Element Length / duration Element Weighting Resit Opportunity
      Laboratory report 100%

      Formative Assessment:

      Written drafts of chapters and feedback on software tool experiments with written feedback.

      ■ 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