Module Descriptors
ENTERPRISE APPLICATION DEVELOPMENT
COMP60047
Key Facts
Digital, Technology, Innovation and Business
Level 6
20 credits
Contact
Leader: Philip James
Email: phillip.james@staffs.ac.uk
Hours of Study
Scheduled Learning and Teaching Activities: 14
Independent Study Hours: 186
Total Learning Hours: 200
Pattern of Delivery
- Occurrence A, Stoke Campus, UG Semester 3
- Occurrence A, Stoke Campus, UG Semester 3 to UG Semester 1
- Occurrence B, The Development Manager, UG Semester 3
- Occurrence B, The Development Manager, UG Semester 3 to UG Semester 1
Sites
- Stoke Campus
- The Development Manager
Assessment
- DESIGN DOCUMENTATION - 1500 WORDS weighted at 40%
- PRESENTATION AND VIVA - 30 MINUTE PRESENTATION weighted at 60%
Module Details
Indiciative Content
Theory & Knowledge Exchange
Enterprise Architecture Patterns
Common architectures of enterprise applications
Domain Driven Design
Messaging
Security
Design Patterns
Clean Architecture
Test Driven Development
Clean unit tests
Integration Testing
End to end testing
Microservice Testing Considerations
DevOps
Containerisation
Cloud Deployment
Technology & Resources
Video/written material will be provided in Java. Students can develop solutions in other OO languages.
Development environments: Intellij. Other IDEs considered; students can develop solutions in other development environments than those used in the lectures.
Internet to access official documentation for the language used as well as other texts recommended by the module tutor via the Staffordshire University O’Reilly library.¿
Practical Content
This module will support the development and assessment of the following Core Knowledge, Skills and Behaviours from the DTSP Apprenticeship Standard:
Knowledge
K5 A range of digital technology solution development techniques and tools.
K13 Principles of data analysis for digital and technology solutions.
K17 Reporting techniques, including how to synthesise information and present concisely, as appropriate to the target audience.
Skills
S9 Apply relevant security and resilience techniques to a digital and technology solution for example: risk assessments, mitigation strategies.
S10 Initiate, design, implement and debug a data product for a digital and technology solution.
This module will support the development and assessment of the following Specialist Route Knowledge, Skills and Behaviours from the DTSP Apprenticeship Standard:
Software Engineer
Knowledge
K21 How to operate at all stages of the software development life cycle and how each stage is applied in a range of contexts. For example, requirements analysis, design, development, testing, implementation.
K22 Principles of a range of development techniques, for each stage of the software development cycle that produce artefacts and the contexts in which they can be applied. For example, UML, unit testing, programming, debugging, frameworks, architectures.
K24 How to interpret and implement a design, compliant with functional, non-functional and security requirements including principles and approaches to addressing legacy software development issues from a technical and socio-technical perspective. For example, architectures, languages, operating systems, hardware, business change.
K25 The factors affecting product quality and approaches for how to control them throughout the development process. For example, security, code quality, coding standards.
K26 How to select and apply a range of software tools used in Software Engineering.
K27 Approaches to the interpretation and use of artefacts. For example, UML, unit tests, architecture.
Skills
S18 Use appropriate analysis methods, approaches and techniques in software engineering projects to deliver an outcome that meets requirements.
S19 Implement software engineering projects using appropriate software engineering methods, approaches and techniques.
S21 Determine, refine, adapt and use appropriate software engineering methods, approaches and techniques to evaluate software engineering project outcomes.
S22 Evaluate learning points arising from software engineering work undertaken on a project including use of methods, analysis undertaken, selection of approach and the outcome achieved to identify both lessons learnt and recommendations for improvements to future projects.
Enterprise Architecture Patterns
Common architectures of enterprise applications
Domain Driven Design
Messaging
Security
Design Patterns
Clean Architecture
Test Driven Development
Clean unit tests
Integration Testing
End to end testing
Microservice Testing Considerations
DevOps
Containerisation
Cloud Deployment
Technology & Resources
Video/written material will be provided in Java. Students can develop solutions in other OO languages.
Development environments: Intellij. Other IDEs considered; students can develop solutions in other development environments than those used in the lectures.
Internet to access official documentation for the language used as well as other texts recommended by the module tutor via the Staffordshire University O’Reilly library.¿
Practical Content
This module will support the development and assessment of the following Core Knowledge, Skills and Behaviours from the DTSP Apprenticeship Standard:
Knowledge
K5 A range of digital technology solution development techniques and tools.
K13 Principles of data analysis for digital and technology solutions.
K17 Reporting techniques, including how to synthesise information and present concisely, as appropriate to the target audience.
Skills
S9 Apply relevant security and resilience techniques to a digital and technology solution for example: risk assessments, mitigation strategies.
S10 Initiate, design, implement and debug a data product for a digital and technology solution.
This module will support the development and assessment of the following Specialist Route Knowledge, Skills and Behaviours from the DTSP Apprenticeship Standard:
Software Engineer
Knowledge
K21 How to operate at all stages of the software development life cycle and how each stage is applied in a range of contexts. For example, requirements analysis, design, development, testing, implementation.
K22 Principles of a range of development techniques, for each stage of the software development cycle that produce artefacts and the contexts in which they can be applied. For example, UML, unit testing, programming, debugging, frameworks, architectures.
K24 How to interpret and implement a design, compliant with functional, non-functional and security requirements including principles and approaches to addressing legacy software development issues from a technical and socio-technical perspective. For example, architectures, languages, operating systems, hardware, business change.
K25 The factors affecting product quality and approaches for how to control them throughout the development process. For example, security, code quality, coding standards.
K26 How to select and apply a range of software tools used in Software Engineering.
K27 Approaches to the interpretation and use of artefacts. For example, UML, unit tests, architecture.
Skills
S18 Use appropriate analysis methods, approaches and techniques in software engineering projects to deliver an outcome that meets requirements.
S19 Implement software engineering projects using appropriate software engineering methods, approaches and techniques.
S21 Determine, refine, adapt and use appropriate software engineering methods, approaches and techniques to evaluate software engineering project outcomes.
S22 Evaluate learning points arising from software engineering work undertaken on a project including use of methods, analysis undertaken, selection of approach and the outcome achieved to identify both lessons learnt and recommendations for improvements to future projects.
Additional Assessment Details
Assignment 1 - Report documenting the design, implementation and testing decisions made during the development of this solution.
learning Outcomes 1,2, 3)
Assessing the following Software Engineer Route KSBs
Knowledge
K21 How to operate at all stages of the software development life cycle and how each stage is applied in a range of contexts. For example, requirements analysis, design, development, testing, implementation.
K22 Principles of a range of development techniques, for each stage of the software development cycle that produce artefacts and the contexts in which they can be applied. For example, UML, unit testing, programming, debugging, frameworks, architectures.
Skills
S18 Use appropriate analysis methods, approaches and techniques in software engineering projects to deliver an outcome that meets requirements.
S19 Implement software engineering projects using appropriate software engineering methods, approaches and techniques.
S21 Determine, refine, adapt and use appropriate software engineering methods, approaches and techniques to evaluate software engineering project outcomes.
Assignment 2 – presentation of the development and demonstration off the finished solution - showcasing the finished application and answer questions about its construction. It will also include an evaluation of the KSBs developed during this module.
Learning Outcomes 1,2,3
Assessing the following Software Engineer Route KSBs
Knowledge
S22 Principles of a range of development techniques, for each stage of the software development cycle that produce artefacts and the contexts in which they can be applied. For example, UML, unit testing, programming, debugging, frameworks, architectures.
S25 The factors affecting product quality and approaches for how to control them throughout the development process. For example, security, code quality, coding standards.
S26 How to select and apply a range of software tools used in Software Engineering.
Skills
S18 Use appropriate analysis methods, approaches and techniques in software engineering projects to deliver an outcome that meets requirements.
S19 Implement software engineering projects using appropriate software engineering methods, approaches and techniques.
S22 Evaluate learning points arising from software engineering work undertaken on a project including use of methods, analysis undertaken, selection of approach and the outcome achieved to identify both lessons learnt and recommendations for improvements to future projects.
learning Outcomes 1,2, 3)
Assessing the following Software Engineer Route KSBs
Knowledge
K21 How to operate at all stages of the software development life cycle and how each stage is applied in a range of contexts. For example, requirements analysis, design, development, testing, implementation.
K22 Principles of a range of development techniques, for each stage of the software development cycle that produce artefacts and the contexts in which they can be applied. For example, UML, unit testing, programming, debugging, frameworks, architectures.
Skills
S18 Use appropriate analysis methods, approaches and techniques in software engineering projects to deliver an outcome that meets requirements.
S19 Implement software engineering projects using appropriate software engineering methods, approaches and techniques.
S21 Determine, refine, adapt and use appropriate software engineering methods, approaches and techniques to evaluate software engineering project outcomes.
Assignment 2 – presentation of the development and demonstration off the finished solution - showcasing the finished application and answer questions about its construction. It will also include an evaluation of the KSBs developed during this module.
Learning Outcomes 1,2,3
Assessing the following Software Engineer Route KSBs
Knowledge
S22 Principles of a range of development techniques, for each stage of the software development cycle that produce artefacts and the contexts in which they can be applied. For example, UML, unit testing, programming, debugging, frameworks, architectures.
S25 The factors affecting product quality and approaches for how to control them throughout the development process. For example, security, code quality, coding standards.
S26 How to select and apply a range of software tools used in Software Engineering.
Skills
S18 Use appropriate analysis methods, approaches and techniques in software engineering projects to deliver an outcome that meets requirements.
S19 Implement software engineering projects using appropriate software engineering methods, approaches and techniques.
S22 Evaluate learning points arising from software engineering work undertaken on a project including use of methods, analysis undertaken, selection of approach and the outcome achieved to identify both lessons learnt and recommendations for improvements to future projects.
Learning Strateiges
The module will be delivered in a Blended Learning Mode consisting of face to face, online and guided learning sessions.
Teaching sessions will blend theory and practical learning and most importantly where possible contextualised in your workplace as part of your apprenticeship. Learners will be introduced to curriculum concepts and ideas and will then be able to apply theory to practical examples. In addition, students will be provided with a range of resources for independent study such as case studies, academic papers and industry case studies. There will be a mixture of practical and theoretical formative (mock or practice) exercises which will help students build knowledge and confidence in preparation for summative (formal) assessment.
The delivery will be delivered as follows:
Module Launch week: 12 hours.
There will be a module launch session consisting of up to 12 hours face to face contact time devoted to developing your understanding of the core purpose and assessment of the module. Learners will be presented with details of how the learning will be structure and how to access to the learning materials for the remainder of the module.
Structured Learning Sessions: 15 hours
Following the module launch week you will have a further 15 hours of contact time as a class with the module team. This will typically be as 10 x 1.5-hour online classes which will be a combination of activities including lectures, demonstrations, discussions, tutorials and seminars. Some sessions are likely to be in flipped classroom style, where you will be expected to watch online recordings, read materials or respond to practical activities in preparation for active engagement with problem solving in the online session.
1:1 Progress Checks: 1 hour
As a Blended Learner understanding your progress can be a challenge so you are allocated an hour of 1:1 time with your tutor (typically 3 x 20 minute). Some of these may be in small groups if appropriate. These sessions may be used to discuss key topics, troubleshoot salutations, review working drafts etc.
Guided Independent Learning: 178 hours.
The module leader will provide resources through the virtual learning environment which will include videos and presentations as well as links to useful websites and other resources. Additional academic learning will be achieved through reading around the subject area, module tutors will suggest useful texts, though many others will be suitable and can be found in our e-library. You should also draw on the expertise in your workplace via your workplace mentor and other colleagues. If you require help understanding any of the concepts, you should contact your module tutor for assistance.
As an apprentice you are constantly developing your Digital Skills as part of your substantial role, and this applies to the development of the knowledge for your modules too. In some cases, there will be a significant cross over between the module content and in others less so, depending on the nature of your workplace duties, this will have direct impact on to the number of Independent Learning required.
Within the Independent learning time you will be expected to complete your assignments, as a guide a typical module assignment should take around 60 hours to complete.
Teaching sessions will blend theory and practical learning and most importantly where possible contextualised in your workplace as part of your apprenticeship. Learners will be introduced to curriculum concepts and ideas and will then be able to apply theory to practical examples. In addition, students will be provided with a range of resources for independent study such as case studies, academic papers and industry case studies. There will be a mixture of practical and theoretical formative (mock or practice) exercises which will help students build knowledge and confidence in preparation for summative (formal) assessment.
The delivery will be delivered as follows:
Module Launch week: 12 hours.
There will be a module launch session consisting of up to 12 hours face to face contact time devoted to developing your understanding of the core purpose and assessment of the module. Learners will be presented with details of how the learning will be structure and how to access to the learning materials for the remainder of the module.
Structured Learning Sessions: 15 hours
Following the module launch week you will have a further 15 hours of contact time as a class with the module team. This will typically be as 10 x 1.5-hour online classes which will be a combination of activities including lectures, demonstrations, discussions, tutorials and seminars. Some sessions are likely to be in flipped classroom style, where you will be expected to watch online recordings, read materials or respond to practical activities in preparation for active engagement with problem solving in the online session.
1:1 Progress Checks: 1 hour
As a Blended Learner understanding your progress can be a challenge so you are allocated an hour of 1:1 time with your tutor (typically 3 x 20 minute). Some of these may be in small groups if appropriate. These sessions may be used to discuss key topics, troubleshoot salutations, review working drafts etc.
Guided Independent Learning: 178 hours.
The module leader will provide resources through the virtual learning environment which will include videos and presentations as well as links to useful websites and other resources. Additional academic learning will be achieved through reading around the subject area, module tutors will suggest useful texts, though many others will be suitable and can be found in our e-library. You should also draw on the expertise in your workplace via your workplace mentor and other colleagues. If you require help understanding any of the concepts, you should contact your module tutor for assistance.
As an apprentice you are constantly developing your Digital Skills as part of your substantial role, and this applies to the development of the knowledge for your modules too. In some cases, there will be a significant cross over between the module content and in others less so, depending on the nature of your workplace duties, this will have direct impact on to the number of Independent Learning required.
Within the Independent learning time you will be expected to complete your assignments, as a guide a typical module assignment should take around 60 hours to complete.
Learning Outcomes
critically evaluate development approaches to solutions to enterprise applications
Design an enterprise application, critically evaluating alternatives and justifying selections.
mplement an enterprise application that includes relevant security features
Texts
All texts and electronic resources will be updated and refreshed on an annual basis and available for students via the online Study Links resource platform. All reference materials will be collated and curated and aligned to Equality, Diversity & Inclusion indicators.
Core Text/Resource:
Freeman, E. and Robson, E. (2020). ‘Head First Design Patterns’, O’Reilly Media.
Larsson, Magnus, (2021). ‘Microservices with Spring Boot and Spring Cloud’, Packt Publishing.
Musib, S. (2022). ‘Spring Boot in Practice’, Manning Publications.
Spring (2022). https://spring.io/projects/spring-boot [Last accessed 6/3/22]
Optional Text/Resource:
Gamma et al (1994). ‘Design Patterns: Elements of Reusable Object-Oriented Software’, Addison-Wesley Professional.
Kerievsky, J. (2004). ‘Refactoring to Patterns’, Addison-Wesley Professional.
Larman, C. (2004). ‘Applying UML and Patterns: An Introduction to Object Orientated Analysis and Design and Iterative Development’, Pearson Publishing.
Advanced/Supplementary Text/Resource:
Evans, E. (2003). ‘Domain Driven Design: Tackling Complexity in the Heart of Software’, Addison-Wesley Professional.
Fowler, M. (2004). ‘Patterns of Enterprise Architecture’, Addison-Wesley Professional.
Khorikov, V. (2020). ‘Unit Testing: Principles, Practices and Patterns Paperback’, Manning Publications
Martin, R. (2009). 'Clean Code. A handbook of Agile Software Craftsmenship'. Prentice Hall.
Martin, R. (2017). “Clean Architecture: A Craftsman’s Guide to Software Structure and Design’, Pearson Publishing.
Osherove, R. (2013). ‘The Art of Unit Testing’. Manning Publications.
Vernon, V. (2013). ‘Implementing Domain Driven Design’, Addison-Wesley Professional.
Core Text/Resource:
Freeman, E. and Robson, E. (2020). ‘Head First Design Patterns’, O’Reilly Media.
Larsson, Magnus, (2021). ‘Microservices with Spring Boot and Spring Cloud’, Packt Publishing.
Musib, S. (2022). ‘Spring Boot in Practice’, Manning Publications.
Spring (2022). https://spring.io/projects/spring-boot [Last accessed 6/3/22]
Optional Text/Resource:
Gamma et al (1994). ‘Design Patterns: Elements of Reusable Object-Oriented Software’, Addison-Wesley Professional.
Kerievsky, J. (2004). ‘Refactoring to Patterns’, Addison-Wesley Professional.
Larman, C. (2004). ‘Applying UML and Patterns: An Introduction to Object Orientated Analysis and Design and Iterative Development’, Pearson Publishing.
Advanced/Supplementary Text/Resource:
Evans, E. (2003). ‘Domain Driven Design: Tackling Complexity in the Heart of Software’, Addison-Wesley Professional.
Fowler, M. (2004). ‘Patterns of Enterprise Architecture’, Addison-Wesley Professional.
Khorikov, V. (2020). ‘Unit Testing: Principles, Practices and Patterns Paperback’, Manning Publications
Martin, R. (2009). 'Clean Code. A handbook of Agile Software Craftsmenship'. Prentice Hall.
Martin, R. (2017). “Clean Architecture: A Craftsman’s Guide to Software Structure and Design’, Pearson Publishing.
Osherove, R. (2013). ‘The Art of Unit Testing’. Manning Publications.
Vernon, V. (2013). ‘Implementing Domain Driven Design’, Addison-Wesley Professional.
Resources
Java IDE (e.g., Intellij)
API testing tool (e.g., Postman, Insomnia)
Cloud Service (e.g., Google Cloud, Amazon Web Service, Azure)
API testing tool (e.g., Postman, Insomnia)
Cloud Service (e.g., Google Cloud, Amazon Web Service, Azure)
Web Descriptors
In this module, you will learn and practice the theory and principles of enterprise development including DevOps, Containerisation and Cloud Deployment. You will also use industry-standard methods, tools, and frameworks to develop server-side web applications.