Module Details
Module Code: |
ELTR6030 |
Title: |
Smart Products Requirements
|
Long Title:
|
Smart Products Requirements Engineering
|
NFQ Level: |
Fundamental |
Valid From: |
Semester 2 - 2021/22 ( January 2022 ) |
Field of Study: |
5230 - Electronic Engineering
|
Module Description: |
This module will develop in the student an understanding of the methodologies and techniques used in requirements engineering, to allow the student to develop requirements for a smart product.
|
Learning Outcomes |
On successful completion of this module the learner will be able to: |
# |
Learning Outcome Description |
LO1 |
Identify and prioritise the key market-driven requirements for a particular new product or service. |
LO2 |
select the appropriate methodology for capturing and developing requirements in relevant domains for a smart product or service. |
LO3 |
engage with and communicate effectively with representative stakeholders in each requirements field/domain. |
LO4 |
capture and accurately document the requirements for a smart product or service in domain relevant laguage. |
LO5 |
identify testing methodology and test approaches to determine if a completed product or subsystem satisfies its requirements. |
Dependencies |
Module Recommendations
This is prior learning (or a practical skill) that is strongly recommended before enrolment in this module. You may enrol in this module if you have not acquired the recommended learning but you will have considerable difficulty in passing (i.e. achieving the learning outcomes of) the module. While the prior learning is expressed as named MTU module(s) it also allows for learning (in another module or modules) which is equivalent to the learning specified in the named module(s).
|
|
Incompatible Modules
These are modules which have learning outcomes that are too similar to the learning outcomes of this module. You may not earn additional credit for the same learning and therefore you may not enrol in this module if you have successfully completed any modules in the incompatible list.
|
No incompatible modules listed |
Co-requisite Modules
|
No Co-requisite modules listed |
Requirements
This is prior learning (or a practical skill) that is mandatory before enrolment in this module is allowed. You may not enrol on this module if you have not acquired the learning specified in this section.
|
No requirements listed |
Indicative Content |
Requirement attributes
Clear, unambiguously defined, Complete, Credible or technically possible, Consistent with no conflict with other requirements, Verifiable with measurable attributes and Necessary
|
Managing requirements
Categorisation (business, functional, user, external interface and data requirements). Prioritisation using product prioritization frameworks (RICE, Value vs Effort, KONA etc.)
|
Documentation
Product requirements documentation frameworks. Initial capture, refinement and extension of requirements.
|
Market and product requirements alignment
Market requirements developed and documented in domain-relevant terminology as systems engineering specifications accounting for commercial, technical, regulatory and environmental constraints.
|
Validation
User validation, technical validation and test validation including cybersecurity penetration consideration
|
Module Content & Assessment
|
Assessment Breakdown | % |
Coursework | 100.00% |
Assessments
No End of Module Formal Examination |
Reassessment Requirement |
Coursework Only
This module is reassessed solely on the basis of re-submitted coursework. There is no repeat written examination.
|
The University reserves the right to alter the nature and timings of assessment
Module Workload
Workload: Full Time |
Workload Type |
Contact Type |
Workload Description |
Frequency |
Average Weekly Learner Workload |
Hours |
Lecture |
Contact |
Theory and Application incl discussions |
Every Week |
2.00 |
2 |
Lab |
Contact |
Practical exercises and project development |
Every Week |
2.00 |
2 |
Independent & Directed Learning (Non-contact) |
Non Contact |
Reading materials, exercises, project and research development |
Every Week |
3.00 |
3 |
Total Hours |
7.00 |
Total Weekly Learner Workload |
7.00 |
Total Weekly Contact Hours |
4.00 |
Workload: Part Time |
Workload Type |
Contact Type |
Workload Description |
Frequency |
Average Weekly Learner Workload |
Hours |
Lecture |
Contact |
Theory and Application incl discussions |
Every Week |
1.00 |
1 |
Lab |
Contact |
Practical exercises and project development |
Every Week |
2.00 |
2 |
Independent & Directed Learning (Non-contact) |
Non Contact |
Reading Materials, exercises, project and research development |
Every Week |
3.00 |
3 |
Total Hours |
6.00 |
Total Weekly Learner Workload |
6.00 |
Total Weekly Contact Hours |
3.00 |
Module Resources
|
Supplementary Book Resources |
---|
-
George Koelsch. (2016), Requirements Writing for System Engineering, 1. APress, p.428, [ISBN: 9781484220993].
| Supplementary Article/Paper Resources |
---|
-
William Brace, Vincent Cheutet. (2012), A Framework to Support Requirements
Analysis in Engineering Design, Journal of Engineering Design, 23 (12), p.52.
| Other Resources |
---|
-
Website, medium-analysts-corner,
-
Website, inflectra-ideas-whitepaper,
-
Website, roadmunk-guides-product-prioritization,
|
|