Theory & Knowledge Exchange

Pillars of Object Orientation: Abstraction, Encapsulation, Inheritance and Polymorphism

Anonymous and inner classes

Dependency Inversion

Dependency Injection

Enumerators

Collections

Exceptions

Reflection

Database

UML diagrams including class and sequence.

Clean Code - continuation

Code Smells

SOLID principles

GRASP patterns

API Patterns

Security considerations

Clean Unit Testing

API Testing



Technology & Resources

Whilst Video/written material will be provided in the preferred language, 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.

¿

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

S4 Initiate, design, code, test and debug a software component for a digital and technology solution.

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.

Behaviour

B1 Has a strong work ethic and commitment to meet the standards required.

B5 Interacts professionally with people from technical and non-technical backgrounds. Presents data and conclusions in an evidently truthful, concise and appropriate manner.



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.

K27 How to select and apply a range of software tools used in Software Engineering.

K28 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.

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.

The demonstration will allow the apprentice to showcase their finished application and answer questions about its construction. The student will also submit supporting images and documentation to highlight the design, implementation and testing decisions made during the development of this solution.

Learning outcomes 1, 2 and 3.





Assessing the following Software Engineer Route KSBs

Knowledge

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.

We will provide lecture material which will be available to you from the launch of the module. This material will be provided by Staffordshire University in addition to material which is provided by AWS Academy.



We will also provide you with access to the AWS environment where you can develop your skills and use the technology which we are discussing.



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.

1. apply analysis techniques to define logical solutions to problems

2. Follow a systematic approach to design, implement and test an object-oriented solution.

3. Apply suitable testing techniques to ensure that the requirements have been met.

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:

Musib, S. (2022). ‘Spring Boot in Practice’, Manning Publications.

Sierra, K. and Bates, B. (2021). ‘Head First Java’. O’Reilly Media, Inc.

Spring (2022) https://spring.io/projects/spring-boot [Last accessed 6/3/22]

Zimmerman et al (2022). ‘Patterns for API Design’, Addison-Wesley Professional.



Optional Text/Resource:

Miles, R. and Hamilton, K. (2006), ‘Learning UML 2.0’, O’Reilly.

Schildt, H. (2018), ‘Java: The Complete Reference, 11th edition’, McGraw-Hill.

Weisfeld, M. (2019). ‘The Object Orientated Thought Process’, Addison-Wesley Professional.



Advanced/Supplementary Text/Resource:

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.

McConnell, S. (2004). 'Code Complete. 2nd Edition'. Microsoft Publishing.

Osherove, R. (2013). ‘The Art of Unit Testing’. Manning Publications.

Java IDE (e.g., Intellij)

API testing tool (eg. Postman, Insomnia)

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.¿

In this module, you will further develop your knowledge and skills of software development by learning about Object Orientated Programming; that is how to design, develop and test these types of applications as well as learn associated good practice. Your knowledge, skills and behaviours will be evidenced through the development of a server-based application.