1 Educators providing Software Architecture courses in Birmingham

LTE Backhaul training course description This course provides a concise insight into the LTE backhaul. Key parts of the course are detailed looks at the transport of messages and the S1 and X2 protocols. What will you learn Describe the overall architecture of LTE. Explain how data and signalling messages are transported in LTE. Describe the S1 protocol. Describe the X2 protocol. LTE Backhaul training course details Who will benefit: Anyone working with LTE. Prerequisites: Mobile communications demystified Duration 2 days LTE Backhaul training course contents Introduction In the first section of the course, we review LTE and its hardware and software architecture. Requirements and key features of LTE. LTE Architecture and capabilities of the UE. Architecture of the E-UTRAN, functions of the eNB. EPC architecture, and functions of the MME, SGW, PGW and PCRF. System interfaces and protocol stacks. Example information flows. Dedicated and default bearers. EMM, ECM and RRC state diagrams. Architecture of the radio access network In this section, we look in more detail at the architecture of the evolved UMTS terrestrial radio access network (E-UTRAN). Logical and physical architecture of the E-UTRAN. Numbering, addressing and identification. E-UTRAN functions. E-UTRAN protocol stacks. Timing and frequency synchronisation in LTE. Transport of data and signalling in LTE Here, we look in more detail at the techniques and protocols that are used to transport data and signalling messages across the evolved UMTS terrestrial radio access network and the evolved packet core. Quality of service in LTE. The GPRS tunnelling protocol. Differentiated services Multi-protocol label switching (MPLS). The stream control transmission protocol (SCTP). The S1 application protocol This section gives a detailed account of the signalling procedures in the S1 application protocol, which the MME uses to control the operation of the eNB. The material looks at the procedures, messages and information elements, and relates them to the system-level procedures in which they are used. S1 setup procedure. UE context management procedures. Non access stratum information transport. Procedures for managing the evolved radio access bearer (E-RAB). Paging procedures. Mobility management procedures for S1-based handovers. Procedures in support of self-optimising networks. The X2 application protocol This section gives a detailed account of the signalling procedures in the X2 application protocol, which is used for peer-to-peer communication between eNBs. The material looks at the procedures, messages and information elements, and relates them to the system-level procedures in which they are used. X2 setup procedure. Mobility management procedures for X2-based handovers Procedures in support of self-optimising networks. High level system operation In the final section, we bring our discussions of the S1 and X2 application protocols together by reviewing the system-level operation of LTE. Attach procedure. Transitions between the states of RRC Idle and RRC Connected. Tracking area updates in RRC Idle. Handover procedures in RRC Connected.

SAFe® for Architects: In-House Training Enable continuous value flow by aligning technical strategy with business goals, communicating that strategy to development teams, and applying Agile architecture practices. Attendees can improve collaboration and alignment in a SAFe® Lean-Agile enterprise when they become a SAFe® 5 Architect. The SAFe® for Architects course prepares System, Solution, and Enterprise Architects to engage across the organization as effective leaders and change agents who collaboratively deliver architectural solutions. During this course, attendees will explore the roles, responsibilities, and mindset of Agile Architects, and appreciate how to align architecture with business value and drive continuous flow to large systems of systems while supporting SAFe® program execution. What you will Learn To perform the role of a SAFe® Architect, you should be able to: Architect using SAFe® principles Align architecture with business value Develop and communicate architecture vision and intent Plan architectural runway to enable delivery success Architect for continuous delivery and Release on Demand Lead and coach architects and team members during Program Increment (PI) Planning and execution Provide leadership during a Lean-Agile transformation Exemplifying Lean-Agile architecture Architecting for DevOps and Release on Demand Aligning architecture with business value Developing Solution Vision, Solution Intent, and Roadmaps Preparing architecture for Program Increment (PI) Planning Coordinating architecture throughout PI Planning Supporting Continuous Delivery during PI execution Supporting new Strategic Themes and Value Streams Leading as an architect during a Lean-Agile transformation

Software comes in a variety of guises - application software, firmware, middleware, system software. Increasingly, however, it doesn't necessarily present that way, especially as the boundaries between software, data and source code are becoming more and more blurred. And as software becomes more complex and more difficult to disentangle, so it becomes harder to manage and to value. But as it becomes more integral to every aspect of a business, so it is ever more important to keep on top of the technical, legal and commercial issues that arise, issues such as: To address these issues, organisations need a process for evaluating their current situation from all perspectives and for identifying the key actions they need to take to ensure holistic management of their software. This very practical programme will help set your organisation on the right path. Note: this is an indicative agenda, to be used as a starting point for a conversation between client and consultant, depending on the organisation's specific situation and requirements. This programme is designed to give you a deeper understanding of: The technical, legal and commercial risks associated with software development, procurement, use and commercial exploitation The most appropriate processes and responsibilities for managing those risks Note: this is an indicative agenda, to be used as a starting point for a conversation between client and consultant, depending on the organisation's specific situation and requirements. 1 Software business model What is the software business model? What options exist? Has the software business model been thoroughly reviewed to ensure its viability? This means fully understanding the market opportunity, the business environment and customer and end-user expectations. 2 Technology What are the technologies? How has the technology selection been validated considering the competitiveness, structure, and potential for future innovation? 3 UI and UX What is the UI and UX? How to best articulate this? Has the user interface and user experience been studied from both a subjective and objective view to give insight into customer behaviour? 4 Legal framework / commercial aspects Has the necessary legal framework or commercial aspects that may impact upon use or operation of the software been understood and risks identified and mitigated? 5 Software development What is the software development process? Are both the business management and development team's processes resilient in order to improve the company's capability and the maturity of the software? 6 Software quality What is quality? What are the metrics around software quality? What is the maturity level, based around a qualitative and quantitative assessment? 7 Intellectual property associated What IP should be considered when it comes to software? Does the company understand both the intellectual property risks and potential opportunities associated with this software? 8 Security What does software security mean in this context? How is it being addressed? 9 An holistic approach Review of roles and responsibilities to ensure appropriate management and protection