You Tube Channel: www.youtube.com/@bramanareddy0482

 Microsoft Cognitive Services is a set of APIs, SDKs, and services available to developers to make their applications more intelligent, engaging, and discoverable. Microsoft Cognitive Services expands on Microsoft’s evolving portfolio of Machine Learning APIs and enables the developers to easily add intelligent features – such as emotion and video detection, facial, speech, and vision recognition, speech and language understanding into our applications. We will be using Cognitive Service API to develop our Artificial Intelligent applications and to make easier. Cognitive Service API has 5 main categories and they are Vision Speech Language Knowledge Search Vision API: In Vision API, we have computer vision API for extracting actionable information from images, Face API to detect, identify, analyze, organize, and tag faces in photos, Content Moderator to Automate image, text, and video moderation, Emotion API Preview to personalize user experiences with emotion recognition and Custom

 This Method is used to evaluate the quality attributes(such as performance, availability, and security) of software architectures.  ATAM is used to mitigate risks in software architectures in the early stages of the software development life cycle (SDLC). Participants in ATAM  The ATAM requires the participation of three groups as follows. The evaluation team  The evaluation team consists of the members who are external to the project. This team consists of 3-5 members who play their specific roles in the team. Project decision-makers   Project decision-makers have the power to speak for the development of the project and have the authority to mandate changes. Architecture stakeholders   Any individual, team, or organization who has an interest in the realization of the architecture and is somehow related to the architecture is a stakeholder of that architecture. Stakeholders include users, maintainers, performance engineers, testers, integrators, developers. Process of Architecture T

 Scenario Based Architecture Analysis Method(SAAM), Scenario-based architecture evaluation is a specific kind of architecture review, which is based on the notion of a scenario. A scenario is a “short statement describing an interaction of one of the stakeholders with the system”. Each identified scenario is then checked to determine whether it is supported by a system’s architecture or not.  Well-known examples of scenario-based evaluation methods are ATAM and SAAM .  Scenario-based architecture analysis is typically performed as a one- or two-day workshop, where ideally all system stakeholders participate in the review. The workshop includes the explanation of the architecture, the identification of the most important scenarios, the analysis of the identified scenarios, and the presentation of the results. Like other review-based methods, scenario-based evaluation methods are a static and manual analysis approach

  Software architecture evaluation is an important activity in the software architecting process. The fundamental goal of architecture evaluation is to assess the potential of a proposed/chosen architecture to deliver a system capable of fulfilling required quality requirements and to identify any potential risks.  Researchers and practitioners have proposed a large number of architecture evaluation methods for which a classification and comparison framework has also been proposed. Most widely used architecture evaluation methods are scenario-based .  These methods are called scenario-based because scenarios are used to characterize the quality attributes required of a system. It is believed that scenario-based analysis is suitable for development-time quality attributes (such as maintainability and usability) rather than for run-time quality attributes (such as performance and scalability), which can be assessed using quantitative techniques such as simulation or mathematical models