Module Code - Title:
CS6201
-
REQUIREMENTS ENGINEERING FOR HEALTH INFORMATICS
Year Last Offered:
2025/6
Hours Per Week:
Grading Type:
Prerequisite Modules:
Rationale and Purpose of the Module:
Syllabus:
The Requirements Process: Requirements in the Software Life Cycle; Requirements and Design; Requirements and Testing; Requirements Engineering.
The elicitation and discovery of requirements: The sources of requirements; the roles of stakeholders; Discovering and inventing requirements, elicitation techniques: prototyping and scenarios; task analysis; joint techniques; requirements workshops; facilitation techniques; user-centred requirements elicitation; requirements situations.
The analysis of requirements: Uses of modelling; models, descriptions and specifications; data requirements; analysis patterns; problem domain descriptions; goals, constraints and proposed solutions in requirements documentation.
Requirements documentation: Standards and templates; documentation styles; domain level and product level task descriptions; glossaries and data dictionaries; domain-level requirements; product-level requirements, requirements templates: IEEE-830 and Volere. Writing non-functional requirements; quality factors and quality requirements; making requirements measurable.
Requirements validation: Verification and validation of requirements; reviews and walkthroughs: the quality of requirements; requirements defects; requirements inspection techniques; negotiation and agreement of requirements; organisational and social issues.
Learning Outcomes:
Cognitive (Knowledge, Understanding, Application, Analysis, Evaluation, Synthesis)
Outline the drivers for business intelligence within health care organisations.
Define key performance indicators and models that can assist in performance evaluation.
Present various models that can be leveraged to support strategic planning of IT systems adoption within health care settings.
Compare and contract implementation approaches to information systems adoption.
Compare and contrast systems acquisition approaches.
Affective (Attitudes and Values)
Demonstrate an appreciation of the value and the need for involvement of all kinds of stakeholders in the software requirements process.
Demonstrate a recognition of the importance of social and organisational issues in the software requirements process.
Demonstrate an awareness of the inherent difficulty of achieving an ideal software requirements specification.
Psychomotor (Physical Skills)
N/A
How the Module will be Taught and what will be the Learning Experiences of the Students:
Research Findings Incorporated in to the Syllabus (If Relevant):
Prime Texts:
Lauesen, S (2002)
Software Requirements, Styles and Techniques
, Addison Wesley
Beyer, H. and Holtzblatt, K. (1998)
Contextual Design: Defining Customer Centred Systems
, San Francisco, Morgan Kaufmann
Robertson S and Robertson J (2000)
Mastering the Requirements Process
, Addison Wesley
Other Relevant Texts:
Gottesdiener E. (2005)
The Software Requirements Memory Jogger
, GOAL/QPC
Gause, D.C. and Weinberg G.M. (1989)
Exploring Requirements: Quality before Design
, New York, Dorset House
Kovitz, B.L. (1997)
Practical Software Requirements: A Manual of Content and Style
, New York, Manning
Programme(s) in which this Module is Offered:
Semester(s) Module is Offered:
Module Leader:
katie.crowley@ul.ie