Certified Solutions Architect MOOC Training Course Guide. A Certified Solutions Architect certification MOOC (Massive Open Online Course) helps to grow your career. Click the following button to find out how to get your Solutions Architect Certification:
If you want to learn more about Digital Transformation take our FREE Online Course to become a Digital Transformation Manager in 10 Days!:
Solutions Architect Certification MOOC: FREE Online Courses & Training
- 1 Solutions Architect Certification MOOC: FREE Online Courses & Training
- 2 Certified Solutions Architect Q&A
- 3 Portfolio of Digital Transformation Certifications™
- 4 What is a Solutions Architect and Why You Should Become a Certified Solutions Architect?
- 5 Business Architecture
- 6 Information Architecture
- 6.1 Information Architecture Introduction
- 6.2 Information Architecture and Data
- 6.3 Information Architecture Tool: Card Sorting
- 7 Application Architecture
- 7.1 Application Architecture definition
- 7.2 Application Architecture specific scenarios and needs
- 7.3 Set the Goals for the Architecture
- 7.4 Understand the Architectural Landscape
- 7.5 Establish the Concepts of Architecture Design
- 7.6 Concentrate on the Key Architecture Concepts
- 8 Infrastructure Architecture
Certified Solutions Architect Q&A
Portfolio of Digital Transformation Certifications™
Welcome to the Portfolio of Digital Transformation Certifications™.
This Robotics certification training course guide is part of the Portfolio of Digital Transformation Certifications™ coached by Angel Berniz.
Following you can find all the Digital Transformation Certifications available:
- Digital Transformation Certification Training Course
- Big Data Certification Training Course
- Internet of Things Certification Training Course
- Industry 4.0 Certification Training Course
- Agile Coach Certification Certification Training Course
- Artificial Intelligence & Machine Learning Certification Training Course
- Robotics Certification Training Course
- Blockchain Certification Training Course
- Lean Startup Certification Training Course
- Design Thinking Certification Training Course
- Solutions Architect Certification Training Course
- Microservices Certification Training Course
- Management 4.0 Certification Training Course
CALL FOR LESSONS LEARNED TIPS by Pros, for writing 10 new books. The challenge is the following:
- If you are a Pro in one of these 10 areas, please contribute with one Lesson Learned tip that you would love someone else had taught you when you started. I mean a 1-page project management tip on Robotics, Big Data, Blockchain, etc.
- You can also help us with this challenge by sharing to your friends, colleagues, Twitter followers, Facebook friends, and LinkedIn connections, asking them for Pros to contribute one tip to be included in these books.
All contributors will be will be mentioned in the book and gain career exposure!
Send your contributions to [email protected]
Please, share this guide in your Social Media so that others can also benefit from it. Share you comments!
What is a Solutions Architect and Why You Should Become a Certified Solutions Architect?
Solutions Architect definition
A solutions architect is an essential part of projects, which may be of numerous natures and sizes across clients. This role may be the one, who understands the overall techno-functional problems and also the people problems. His understanding of the issues is needed another consultants to feel safer and assured and concurrently the customer would also be available to solution’s abilities and would share their business mind-space. This could assistance to bridge the gaps to understand between your customers and consultants, and motivate these to implement the very best solution.
Solutions Architect’s understanding
The solutions architect’s bent of mind for the overall completeness from the solution, which may be coupled with his understanding and prowess within the project implementation. Also his natural interest for the substantial achievement of satisfying the client needs will make him to aspire to achieve the complete look at the work and perhaps lead for the finalization and closure from the complete solution.
The solutions architect’s understanding about various solution modules is needed him to attain his objective. His ability to discover is needed stabilizing the project progress and balancing load inside the project.
Solutions Architect’s objectives
The fundamental objectives of the solutions architect may be as follows:
- Be conscious from the scope from the project
- Over the solution modules, this role would perform the followings:
– Understand client’s needs and it is business viabilities
– Determine the gaps between needs and solution functionalities and define workable methods to bridge the gaps
– Design the solutions at length house in the consultants and business
– Plan the closure from the solutions and find out with the implementation from the solutions
Solutions Architect and Project Management
A company executes projects across various industries and lots of these projects can be quite large in dimensions. A solutions architect could be very helpful in these types of projects to guarantee the smooth project execution along with a effective implementation to have high-business user satisfaction.
Business Architecture Introduction
Business architecture is understood to be “a blueprint from the enterprise that gives a typical knowledge of the business and it is accustomed to align proper objectives and tactical demands.” Individuals who develop and keep business architecture are classified as business architects.
Business architecture may be the bridge between your enterprise business design and enterprise strategy somewhere, and also the business functionality from the enterprise on the other hand.
Business Architecture documents and models an organization’s policies, processes, work activities, artifacts, and assets. Particularly, Business Architecture solutions the next questions in regards to the organizations and procedures:
- Exactly what are they doing?
- Who does implement it?
- So why do they are doing it?
- How can they are doing it?
- When will they get it done?
- Where will they get it done?
Business Architecture Modelling
The Company Layer is how elements associated with people, processes and places are managed. This lesson introduces the company Layer and provides an introduction to the primary constructs readily available for modelling Business Architecture.
The Company Layer is split up into the next views:
The conceptual layer is how we define the ‘what’. Running a business terms what this means is ‘what’ may be the business, and can comprise things in the higher level operating model, with the business domains and abilities to the kind of roles that’ll be needed to operate the company. Observe that this doesn’t discuss how anything is performed, purely what must be done. The ‘what’ is essential to understand is essential for your business and it is outside of how it’s done.
For instance, you can utilize telephone sales, however, you separate the ‘what’ – sales in the ‘how’ – telephone, to let you easily observe that there might be more ‘how’s’ for this one capacity, i.e. internet sales, in person sales etc. All of these are processes supporting one conceptual capacity.
- Business Objective – A proper business goal to have an enterprise. Example – We’ll supply the best customer support within our field.
- Business Principle – Higher level rules that govern the way business abilities are delivered through the enterprise and supply the context for designing and defining how these abilities is going to be recognized. Example – Quality won’t be sacrificed by cost efficiency.
- Business Domain – This is actually the top level construct in the industry Architecture. It possesses a way of categorising the company related elements in addition to the context that is used. Quite simply the primary groupings from the business, not always the organisational functions. e.g., Invoicing is one of the Finance domain but might come in the Sales Order process. Example – Marketing and advertising, Operations, Customer Services, Finance, Fulfilment, HR, IT, Business Control, Buying and selling and Order Management.
- Business Capability – Business Abilities are utilized to model the abilities of the business or enterprise. Abilities represent exactly what the business does (or must do) to be able to fulfil its objectives and responsibilities. Examples – Order Approval, Picking, Packing, Delivery, Client Management, Client Invoicing, Trades Matching and Confirmation, Perform Industry Research.
The logical layer is how we define the ‘how’. Running a business terms this is actually the lower level abstraction of ‘how’ the ‘what’ is going to be achieved and can contain items like the processes which will carry out the abilities defined within the conceptual level, along with the roles that carry out the process.
- Business Role – Business Role consists of Individual and Group Business Roles. They are utilised to represent the style of the organisation with regards to the roles which are needed and just how they’re related. Business Roles are groups, departments, teams or job roles inside the enterprise representing many amounts of granularity regarding the way the processes are carried out. Individual Role Example – Depot Manager, Packer, Picker, Sorter, Returns Manager, Broker Group Role Example – Courier, Depot Team, Postal Service, Front Office Team, Global HR Team, Local Office
- Business Process – The Company Process represents a specs or style of the way a process ought to be performed. Example – Approve Orders, Pick by Item, Pick by Order, Pack Orders, Dispatch by Courier, Dispatch by Postal Service, Create Allocate Executions and Switch Asset.
- Site Category – a kind of location where business processes are carried out that gives a means of classifying appropriate places where processes will occur (during process design). Examples – Factory, Office, Data Center.
The physical layer may be the actual implementation or deployment. Running a business terms this gives additional detail for example in which the logical processes occur and who – individuals or teams – will work them.
- Actor – Actor might be either a person Actor or perhaps a Group Actor. It might be a particular, named group, team or person that performs a job to carry out a physical process. An actress are capable of doing several business role. Observe that within the situation of the Individual Actor, in which the actual name of the baby isn’t known, a far more abstract name could be given (e.g. HQ Office Manager). Individual Actor Examples – London Depot Manager, Newcastle Depot Manager, John Cruz. Group Actor Examples – London Picking Team, Newcastle Picking Team, London Portfolio Services Team.
- Site – a particular, named location where processes or activities occur. A Website could be mapped to a number of Site Groups, i.e. it might be a warehouse as well as an office, or simply a warehouse. Sites may also contain other [sub]sites, enabling to capture of specific locations inside a particular site. Example – London Warehouse, Newcastle Warehouse, Warrington Warehouse, City Headquarters, Room 300 working in london Mind Office.
- Physical Process – The Physical process is a clear case of a procedure (defined within the Logical view) done by an organization or individual, playing a specific Role. Two Physical Processes only implement exactly the same Business Process when the steps they perform are identical. When the steps performed in 2 Physical Processes will vary, they are mapped to 2 different Business Processes, because both versions defines the steps performed. Example – ‘London Depot Team’ as Depot Team, Pick by ‘Order Deliver’ by Courier ‘Newcastle Depot Team’ as Depot Team, Pick by ‘Item Deliver’ by Postal Service.
How to begin using Business Architecture
Information Architecture Introduction
Information architecture is the concept of deciding how you can arrange the various components of something to become understandable.
Information architecture (IA) concentrates on organizing, structuring, and labeling content within an effective and sustainable way. Thefocus is to help users to get the information they need more quickly and finish tasks. To get this done, you must know the way the pieces fit together to produce the bigger picture, how products connect with one another inside the system.
If you’ve ever attempted to make use of something and thought, “where shall we be held designed to go next?” or “this makes no sense,” you’re encountering a problem by having an information architecture.
Information Architectures are around every corner us
Information architectures (IAs) have been in those sites we use, the apps and software we download, the printed material we come across, as well as the physical places we spend some time in.
A great Information Architecture helps individuals to understand their needs and discover what they’re searching for – within the real life in addition to online. Practicing information architecture involves facilitating the folks and organizations make certain with to think about their structures and language attentively.
We love to to state when you’re making things for other people, you’re practicing information architecture.
Information Architecture forms a basis for UX design
So many people are curious how IA relates to consumer experience (UX) design. UX designers practice IA everyday the 2 are carefully connected. Quite simply, Information Architecture is a vital skill within UX along with other disciplines, for example content strategy, technical writing, library science and interaction design.
Information Architecture and Data
Information Architecture documents and models key information assets, the applications which use these to enable business processes, and defines how applications and knowledge together offer the enterprises functions. The data architecture also specifies which areas of the company process are based on each application where each kind of information is stored and managed.
Information Architecture is comprised with information and data architecture – Using data models, the Information and Data Architecture identifies the data and knowledge needed to perform its mission. For instance, access and distribution models identify enterprise data stores and knowledge flows.
Information Architecture Tool: Card Sorting
Companies are complex, even when they possess zero large amount of staff, they’ve enough detailed information online, different processes and terminology. A huge part of designing a highly effective intranet is ensuring we define the best information architecture.
The information architecture is essentially the structuring of knowledge, how can we organize things. The issue with this particular is the fact that everybody appears to determine this in different ways, everybody includes a different mental model. What exactly we have to do is locate the consensus to ensure that we create an info architecture making sense towards the many people possible.
To be able to know how different users begin to see the business and just how we ought to organize the data, we run a number of card sorting sessions.
Card sorting is really a design technique which involves users. We write different topics of knowledge on individual cards therefore we ask customers or ends users to group cards into logical groups.
Open versus Closed Card Sorting
There’s two kinds of card sorting:
A open sort is were the participants can invent their very own groups, which is helpful when you are developing a new site and you have to define a totally new information architecture.
A closed sort differs, within this situation the participants need to classify the data into pre-existing groups. Which is helpful if you have a current information architecture and you have to bring in many new information directly into it.
Physical versus Online Card Sorting
That old fashioned method of doing card sorting is in person with users by using physical cards. It’s additional time consuming but you will have more qualitative insight because you’re able to ask users what they are thinking because they carry out the task.
Alternatively you should use online software to operate your card sorting exercise. This really is good because it offers a superior a bigger sample size and you may have more quantitative insight. Such software frequently includes built-in analysis tools where you can be preferable from the data.
Ultimately whichever way you take your card sorting you need to discover that you come with an improved feeling of the Information Architecture which will resonate most with nearly all users.
Application Architecture definition
Application Architecture is the procedure of defining the framework of the organization’s application solutions against business needs. It calls for the phrase the applying landscape, planning to optimize this landscape from the ideal blueprint. Outdoors Group’s architectural framework, TOGAF, defines the goal of application architecture as “defining the main types of application systems essential to process the information and offer the business”.
When confronted with today’s unparalleled pace of technological change, the analysts at Gartner predict which more than 75% of multi-enterprise processes is going to be implemented as composite applications by 2018.
Like a discipline, application architecture lays the building blocks for agility, scalability and reliability inside your application landscape. The keyword here’s agility. Traditional companies are now being reinvented overnight. With effective application architecture, your business can respond rapidly and effectively to sudden alterations in the landscape.
With regards to just one application, Application Architecture is the procedure of defining an organized solution that fits all the technical and operational needs, while optimizing common quality attributes for example performance, security, and manageability. It calls for a number of decisions according to an array of factors, and all these decisions might have considerable effect on the standard, performance, maintainability, and overall success from the application.
Application Architecture specific scenarios and needs
Like every other complex structure, software should be built on the firm foundation. Neglecting to consider key scenarios, neglecting to the perception of common problems, or neglecting to understand the lengthy term effects of key decisions can place your application in danger. Technology advances and platforms assistance to simplify the job of creating applications, but they don’t replace the necessity to create your application carefully, according to your particular scenarios and needs. The potential risks uncovered by poor architecture include software that’s unstable, is not able to aid existing or future business needs, or perhaps is hard to deploy or manage inside a production atmosphere.
Systems ought to be made with consideration for that user, the machine (the IT infrastructure), and also the business goals. For all these areas, you need to outline key scenarios and identify important quality attributes (for instance, reliability or scalability) and key regions of satisfaction and dissatisfaction. Where possible, develop and think about metrics that measure success in all these areas.
User, business, and system goals
Tradeoffs are most likely, along with a balance must frequently be located between competing needs across these 3 areas. For instance, the general consumer experience from the option would be very frequently the purpose from the business and also the IT infrastructure, and alterations in either can considerably modify the resulting consumer experience. Similarly, alterations in the consumer experience needs might have significant effect on the company also it infrastructure needs. Performance may well be a major user and business goal, however the system administrator may be unable to purchase the hardware needed to satisfy that goal 100 % of times. An account balance point may be to satisfy the aim only 80 % of times.
Architecture concentrates on the way the major elements and components inside an application are utilized by, or communicate with, other major elements and components inside the application. Selecting data structures and algorithms or even the implementation information on individual components are design concerns. Architecture and design concerns very frequently overlap. Instead of use solid rules to differentiate between architecture and style, it seems sensible to mix both of these areas. In some instances, decisions are clearly more architectural anyway. In some cases, the choices tend to be more about design, and just how they enable you to understand that architecture.
By using the processes described within this lesson, and taking advantage of the data it has, you’ll be able to create architectural solutions that address all the relevant concerns, could be deployed in your selected infrastructure, and deliver results that satisfy the original aims and objectives.
Think about the following higher level concerns when considering software architecture:
- How can you be utilising the applying?
- How can the applying be deployed into production and managed?
- Do you know the quality attribute needs for that application, for example security, performance, concurrency, internationalization, and configuration?
- Just how can the applying be made to be flexible and maintainable with time?
- Do you know the architectural trends that may impact the application now or once it has been deployed?
Set the Goals for the Architecture
Application architecture seeks to construct a bridge between business needs and technical needs by understanding use cases, after which finding methods to implement individuals use cases within the software. The focus of architecture would be to find out the needs affecting the dwelling from the application. Good architecture cuts down on the business risks connected with creating a technical solution. A great design is sufficiently flexible so that you can handle natural drift which will occur with time in software and hardware technology, plus user scenarios and needs. An architect architect must think about the overall aftereffect of design decisions, the natural tradeoffs between quality attributes (for example performance and security), and also the tradeoffs needed to deal with user, system, and business needs.
Bear in mind the architecture should:
- Expose the dwelling from the system but hide the implementation details.
- Realize all the use cases and types of conditions.
- Attempt to address the needs of numerous stakeholders.
- Handle both functional and quality needs.
Understand the Architectural Landscape
You should comprehend the key forces which are shaping architectural decisions today, and that will change how architectural decisions come in the long run. These key forces are impelled by user demand, in addition to by business interest in faster results, better support for different work styles and workflows, and improved adaptability of software design.
Think about the following key trends:
- User empowerment. A design that supports user empowerment is flexible, configurable, and centered on the consumer experience. Create your application with appropriate amounts of user personalization and options in your mind. Permit the user to define the way they communicate with the application rather of dictating for them, but don’t overload all of them with unnecessary options and settings that can result in confusion. Comprehend the key scenarios making them as easy as possible allow it to be simple to find information and employ the applying.
- Market maturity. Make the most of market maturity by benefiting from existing platform and technology options. Develop greater level application frameworks where it seems sensible, to be able to concentrate on what’s distinctively useful for the application instead of recreating something which already exists and could be reused. Use patterns that offer wealthy causes of proven solutions for common problems.
- Flexible design. More and more, flexible designs make the most of loose coupling to permit reuse and also to improve maintainability. Pluggable designs permit you to provide publish-deployment extensibility. You may also make the most of service orientation techniques for example SOA to supply interoperability along with other systems.
- Future trends. When building your architecture, comprehend the future trends that may affect your design after deployment. For instance, consider trends in wealthy UI and media, composition models for example mashups, growing network bandwidth and availability, growing utilization of cellular devices, ongoing improvement in hardware performance, curiosity about community and private publishing models, an upswing of cloud-based computing, and remote operation.
Establish the Concepts of Architecture Design
Current thinking on architecture assumes that the design will evolve with time and you cannot know all you need to know in advance to be able to fully architect the body. Your design will normally have to evolve throughout the implementation stages from the application while you find out more, so that as you test the look against real life needs. Make your architecture with this particular evolution in your mind in order that it can adjust to needs that aren’t fully known at the beginning of the look process.
Think about the following questions while you create an architectural design:
- Do you know the foundational areas of the architecture that represent the finest risk when you get them wrong?
- Do you know the areas of the architecture that are likely to alter, or whose design you are able to hold back until later with little impact?
- What exactly are your key assumptions, and how would you test them out?
- What conditions may need you to refactor the look?
Don’t attempt to in excess of engineer the architecture, and don’t assume things that you can’t verify. Rather, keep the options open for future change. You will see facets of your design that you need to fix early along the way, which might represent significant cost if redesign is needed. Identify these areas rapidly and with time essential to have them right.
Concentrate on the Key Architecture Concepts
Think about the following key concepts when making your architecture:
- Build to alter rather of creating to last. Consider the way the application might need to change with time to deal with new needs and challenges, and make within the versatility to aid this.
- Model to evaluate and lower risk. Use design tools, modeling systems for example Unified Modeling Language (UML), and visualizations where appropriate that will help you capture needs and architectural and style decisions, and also to evaluate their impact. However, don’t formalize the model towards the extent it suppresses the capacity to iterate and adapt the look easily.
- Use models and visualizations like a communication and collaboration tool. Efficient communication from the design, the choices you are making, and continuing changes towards the design, is crucial to get affordable architecture. Use models, views, along with other visualizations from the architecture to speak and share your design efficiently with the stakeholders, and also to enable rapid communication of changes towards the design.
- Identify key engineering decisions. Make use of the information within this lesson to know the important thing engineering decisions and also the places that mistakes are most frequently made. Purchase getting these key decisions right the very first time so the design is much more flexible and less inclined to be damaged by changes.
Think about using an incremental and iterative method of refining your architecture. Begin with set up a baseline architecture to obtain the main issue right, after which evolve candidate architectures while you iteratively make sure enhance your architecture. Don’t try to have it okay the very first time-design nearly as much as you are able to to be able to start testing the look against needs and assumptions. Iteratively add details towards the design over multiple passes to make certain that you will get the large decisions right first, after which concentrate on the details. A typical pitfall would be to dive in to the details too rapidly and obtain the large decisions wrong by looking into making incorrect assumptions, or by neglecting to evaluate your architecture effectively. When testing your architecture, think about the following questions:
- What assumptions have I produced in this architecture?
- What explicit or implied needs is that this architecture meeting?
- Do you know the key risks with this particular architectural approach?
- What countermeasures have established yourself to mitigate key risks?
- How is that this architecture a noticable difference within the baseline or even the last candidate architecture?
Infrastructure Architecture definition
Infrastructure Architecture (also referred to as Technology Architecture) represents the technical infrastructure and also the specific software and hardware technologies that offer the business applications. The infrastructure architecture includes the next domains:
- Platform – includes the mixture of software, middleware, hardware infrastructure and development frameworks which allow the event, deployment, operation, integration and control over applications.
- Systems Management – includes the technical tools accustomed to collect and evaluate data that appraise the systems performance to enhance system availability, performance, and reliability.
- Networks – contain the technical elements needed to supply data and Internet connectivity and communication internal and exterior towards the enterprise.
Infrastructure Architecture landscape
Infrastructure Architecture has become a little more interesting recently as we view it expand into two distinct overarching groups: Physical Infrastructure and Virtual Infrastructure. Ultimately, all Infrastructure defaults with a hardware foundation, the revolution referred to as Cloud-computing illustrates how complex seo of architecture is becoming. Infrastructure Architecture is also called sometimes as Technical Architecture (in TOGAF for instance).
Infrastructure Architecture today typically includes the next sub-groups:
- Data Center Architecture – This can be a comprehensive look at infrastructure poor specific data center installations / implementations. Data Center Consolidations typically involve standardizing architectures across heterogeneous data centers because they are reduced in number to streamline operations (this really is frequently done along with ITIL process standardization).
- Network Architecture – This kind of architecture could be internet focused (IPv4, IPv6), or include internet and telecommunications (ATM, SS7 etc.) or both. It may have a public use or private (backbones or customer-facing systems) focus.
- Cloud Architecture – Including the next core patterns: IaaS (Infrastructure like a Service), PAaaS (Platform like a Service), SaaS (Software like a Service). These may be configured as Private or public Clouds. And there’s now a ubiquitous category referred to as Hybrid Clouds which combine facets of the prior patterns listed. This third category was created being an method for optimizing the sources from the previous two groups through Virtualization technology (the concept because oftentimes hardware had been under-utilized when focused on merely a single system or purpose).
Infrastructure Architecture represents the sum of the hardware and telecommunications related IT capacity connected having a particular enterprise too it is the connected keeper. The interior architecture of person hardware devices represents another design field (embedded hardware). Infrastructure Architecture is worried using the synergistic operation and control over multiple devices that when taken together offer a number of enterprise services which all of those other Architecture stack can exploit. Infrastructure had formerly been considered a “back-finish” technology capacity until lately when the likes of Google, Dropbox and a large number of others could create public facing “Cloud” choices which effectively exploited infrastructure services direct to consumers.
Infrastructure Architecture has additionally been considered (previously) because the key focus for this security mainly in line with the perception of perimeter to safeguard data centers. However Security Architecture is a lot more expansive than Infrastructure.