This is an archived handbook for a previous year. The current undergraduate and postgraduate handbooks can be viewed using the links above.
Postgraduate Handbook 2012-2013 (archived)
Module COMP50815: SYSTEMS AND REQUIREMENTS ANALYSIS FOR INTERNET SYSTEMS
Department: Computer Science
COMP50815: SYSTEMS AND REQUIREMENTS ANALYSIS FOR INTERNET SYSTEMS
| Type | Level | Credits | Availability | Module Cap | Location |
|---|---|---|---|---|---|
| Tied | 4 | 15 | Available in 2012/2013 | Durham |
Tied To
- G5K109 and G5K114: (programme not found)
Pre-requisites
- None.
Corequisites
- None.
Excluded Combinations
- 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 | Attendance Monitored |
|---|---|---|---|---|---|
| Lectures | 10 | 2 per day in week 2 | 1 hour | 10 | Yes |
| Tutorials | 4 | weekly | 1 hour | 4 | Yes |
| Practicals | 5 | daily in week 1 | 6 hours | 30 | Yes |
| Laboratory | 10 | daily in weeks 3 and 4 | 6 hous | 60 | Yes |
| Preparation and Reading | 46 | ||||
| Total | 150 |
Summative Assessment
| Component | Component Weighting | Element | Length/Duration | Element Weighting | Resit Opportunity |
|---|---|---|---|---|---|
| Laboratory report | 100% | Laboratory report | 100% |
Formative Assessment
Written drafts of chapters and feedback on software tool experiments with written feedback.
Students who do not attend monitored activities shown under Teaching Methods
and Learning Hours, or who fail to complete the summative or formative
assessment(s) specified above, may be subject to the Academic Progress
procedures defined in the University's General Regulation V, and may be
required to leave the University.