Clinical and Scientific Computing for the Physical Sciences 1 (SBI121)

20 credits

Aim of this module

This module provides the trainee with the knowledge that underpins the specialist module in for the Physical Sciences and gives the trainee the tools to undertake work-based learning. It will provide the trainee with in-depth experience of the project life cycle by implementing a project or range of projects within the context of a formal project management methodology.

  1. Implement an innovation and development project within the context of a formal project management methodology.
  2. Agree the clinical need for the project with other scientists, clinicians, patients and/or service users.
  3. Evaluate the current state of the art and limitations of existing solutions.
  4. Develop a specification of requirements for the project.
  5. Develop, critically evaluate and deliver novel (ICT) projects within the Physical Sciences.
Number Work-based learning outcome Title Knowledge
1 1

Devise a plan using an appropriate project management methodology to successfully deliver an innovation and development project, controlling the quality, timing and costs of activities.

2 2,4

Work with users to develop a detailed specification of requirements for an innovation and development project.

3 3,4

Design a solution to meet the previous point by formulating various options and critically appraising them, taking into account the requirements specification, appropriateness of development tools and sustainability in the proposed operational environment.

4 5

Develop and critically evaluate the solution, establishing its appropriateness and limitations, including signal processing, decision support, mathematical modelling and choice of development platform.

5 5

Develop and undertake a validation plan.

6 5

Develop and undertake a verification plan.

7 5

Develop user documentation and training.

8 5

Develop technical documentation.

9 5

Follow the requirements of an appropriate development methodology.

10 1,5

Manage a project within the framework of a formal project management methodology.

11 5

Manage security, safety and business risk throughout the development.

12 5

Apply risk analysis iteratively to improve and redefine a design.

13 5

Perform end-stage review.

You must complete
3 Case-based discussion(s)
4 of the following DOPS / OCEs
Assessment Title Type
Participate in an MDT meeting where clinical software requirements are discussed and agreed OCE
Lead a post implementation review of a completed project, including the benefits realisation DOPS
Propose the initiation of a project by constructing a Project Initiation Document DOPS
Present a completed project, describing the life cycle and management methodologies, to a scientific audience who did not take part in its implementation DOPS
Produce a prototype of a clinical application DOPS
Observe a clinical service which involves a Clinical Scientist working in Clinical and Scientific Computing for the Physical Sciences and present a benefits assessment to senior management. NB this should include areas where the benefit could be enhanced DOPS

Important information

The academic parts of this module will be detailed and communicated to you by your university. Please contact them if you have questions regarding this module and its assessments. The module titles in your MSc may not be exactly identical to the work-based modules shown in the e-portfolio. Your modules will be aligned, however, to ensure that your academic and work-based learning are complimentary.

Learning Outcomes

  1. Describe the use of software engineering techniques on projects in the workplace.
  2. Explain and critically justify the need to apply engineering design principles to novel clinical measurement and software design solutions.
  3. Explain the use of project management methodologies in developing novel clinical measurement and software design projects.
  4. Discuss and evaluate the project life cycle, including specification, design, implementation, validation and verification in the context of a novel software design solution.

Indicative Content

Software engineering

  • The importance of engineering discipline in developing software
  • Operating systems
  • Overview of process models and their importance
  • Comparison of process models
  • System design methods
  • Structured development methods (e.g. Waterfall, Agile)
  • The software development cycle, including:
    • Requirements
    • Specification
    • Design
    • Implementation
    • language selection
    • software coding and coding management
    • procedural, object-oriented and functional programming.
    • real-time system programming
    • embedded system programming
    • Validation and verification

Software development

  • Strategies for web development, including:
    • Hosting
      • Programming for the web with reference to current standards and programming tools, including:
    • Web programming
    • Forms and data
    • Limiting access
    • Developing dynamic content
    • Interfacing with a database
      • Security and privacy
        • Public and private key encryption

 Software quality assurance

  • Configuration management and change control
  • Software tools
  • Standards
  • Documentation

Safety cases

  • The purpose of a safety case
  • The structure of a safety case, to include:
  • Claims
    • reliability and availability
    • security
    • functional correctness
    • time response
    • maintainability and modifiability
    • useability
    • fail-safety
    • accuracy
  • Evidence
    • design
    • development documentation
    • simulation experience
    • previous field experience
  • Argument
    • deterministic
    • probabilistic
    • qualitative
  • Inference
  • Implementation of a safety case
  • Design for assessment
  • The safety case life cycle
  • The contents of a safety case