Module: Systems Analysis

Module Specifications.

Current Academic Year 2024 - 2025

All Module information is indicative, and this portal is an interim interface pending the full upgrade of Coursebuilder and subsequent integration to the new DCU Student Information System (DCU Key).

As such, this is a point in time view of data which will be refreshed periodically. Some fields/data may not yet be available pending the completion of the full Coursebuilder upgrade and integration project. We will post status updates as they become available. Thank you for your patience and understanding.

Date posted: September 2024

Module Title	Systems Analysis
Module Code	CA214 (ITS) / CSC1020 (Banner)
Faculty	Engineering & Computing	School	Computing
Module Co-ordinator	Hyowon Lee
Module Teachers	-
NFQ level	8	Credit Rating	5
Pre-requisite	Not Available
Co-requisite	Not Available
Compatibles	Not Available
Incompatibles	Not Available

Repeat examination
Group assessment: 45% Individual assessment: 55% Given the large number of class size (150-200), doing 55% individual grading to be manageable for the lecturer is challenging but use of in-class activities and weekly automatic Loop quizzes and reflective journal entries were used to make this possible.

Description

Module Description: The module will introduce students to the state-of-the-art for research & practice in requirements analysis using the standards and concepts of system and requirement engineering (RE). This will include the stages of gathering requirements by use cases and documenting it by creating a software requirements specification (SRS) document. In addition, this module will examine the role of RE in software and systems engineering current techniques, notations, methods, processes and tools used in RE.

Learning Outcomes

1. Describe the challenges at initial stages of software development life cycle
2. Explain the best practices for requirements elicitation process
3. Explain the object orientation techniques for system modelling
4. Assess, analyze and specify system & software requirements.
5. Apply use cases to gather requirements of a software project.
6. Manage requirement problems
7. Demonstrate their technical understanding by filling an SRS (Software Requirement Specification) document

*Type*	*Hours*	*Description*
Workload	Full-time hours per semester
Lecture	24	Presentation of tools and techniques
Group work	48	SRS Case Study
Independent Study	56	Projects and reading
Total Workload: 128

All module information is indicative and subject to change. For further information,students are advised to refer to the University's Marks and Standards and Programme Specific Regulations at: http://www.dcu.ie/registry/examinations/index.shtml

Indicative Content and Learning Activities

Introduction to Software Engineering and the role of Requirements Engineering
Discussion of issues.

Introduction to Requirements Engineering
Developing Natural Language Requirements

OO Modelling and Systems Analysis
Coverage of core technique and diagrams.

Stakeholder and Goal Models
Coverage of core technique and diagrams.

System Vision Model
Coverage of core technique and diagrams.

Usage Model
UML use cases and templates

Domain Models
UML class and object diagrams.

Non-Functional Requirements and Requirements Quality
Similarities and differences.

Scaling Requirements Engineering
Tailoring to different project sizes and methodologies

Requirements Elicitation
Techniques and tools

Assessment Breakdown
Continuous Assessment	100%	Examination Weight	0%

Type	Description	% of total	Assessment Date
Course Work Breakdown
Digital Project	Conduct personal research into a software engineering topic and create a video for the class.	15%	Week 3
Group project	SRS Assignment Part 1. Initial deliverable with approximately 70% of material drafted.	15%	Week 7
Group project	SRS Assignment Part 2. Full SRS delivered.	30%	Week 11
Presentation	Individual video presentation assignment: Self reflection report on group project and presentation of project to a stakeholder	20%	Week 12
Loop Quiz	Weekly in-class quizzes on course topics	10%	Every Week
Reflective journal	Self-assessment of own participation and learning from in-class exercises.	5%	Every Week
Participation	In-class activities (individual or paired) to apply what was learned during the class	5%	Every Week

Reassessment Requirement Type
Resit arrangements are explained by the following categories: Resit category 1: A resit is available for both* components of the module. Resit category 2: No resit is available for a 100% continuous assessment module. Resit category 3: No resit is available for the continuous assessment component where there is a continuous assessment and examination element.
* ‘Both’ is used in the context of the module having a Continuous Assessment/Examination split; where the module is 100% continuous assessment, there will also be a resit of the assessment
This module is category 1

Indicative Reading List

Ian Sommerville: 2016, Software Engineering, Global Edition, 10, Pearson, 1292096136

Other Resources

None