M&IB Devx - Requirements

An Incident Report is raised using GEL. GEL stands for Generic Execution Language, which is a programming language used in the CA Service Desk Manager software. GEL allows users to create and customize workflows, including the creation of Incident Reports. By using GEL, users can input the necessary information and details about the incident, ensuring that all relevant information is included in the report.

Geneos is a system monitoring tool. It is used to monitor and manage the performance of various systems and applications in real-time. It provides real-time alerts, dashboards, and reports to help administrators and operators track and analyze system performance, identify issues, and take proactive measures to ensure system stability and availability. Geneos is commonly used in financial institutions and other industries where real-time monitoring and performance management are critical.

In an interview closure, it is important to summarize the meeting to ensure that both parties are on the same page regarding the discussed topics and any conclusions reached. This allows for a clear understanding of the interview's outcomes. Additionally, thanking the individual shows appreciation for their time and consideration throughout the interview process. By summarizing and expressing gratitude, it helps create a positive impression and leaves a lasting impact on the interviewer.

Traceability refers to the ability to track and document the relationships between different components of a system or project. It helps in understanding the impact of changes made to one component on other components. By having traceability, it becomes easier to analyze and assess the potential impact of any change or modification. Therefore, it can be concluded that traceability indeed facilitates impact analysis.

User acceptance tests are derived from functional requirements because user acceptance testing is performed to determine whether a system meets the specified functional requirements and is acceptable to the end users. These tests are designed to validate the system's functionality, usability, and performance from the user's perspective. By conducting user acceptance tests, organizations can ensure that the system meets the needs and expectations of the users and that it functions correctly according to the defined functional requirements. Therefore, the statement "User acceptance tests are derived from functional requirements" is true.

GEL, which stands for Global Event Log, is used in M&IB for reporting incidents, tracking problems, and managing change requests. The Global Event Log is a centralized system that records and tracks all events and activities related to incidents, problems, and change requests. It allows for efficient reporting, tracking, and management of these issues, ensuring that they are properly addressed and resolved. Therefore, the correct answer is "All of the above."

The purpose of a team retrospective in Agile development is to identify areas in which the team can improve. This is done by reflecting on the previous sprint and analyzing what went well and what could have been done better. The retrospective allows team members to openly discuss their experiences, share feedback, and suggest improvements for future sprints. By identifying areas of improvement, the team can continuously enhance their processes, communication, and collaboration, ultimately leading to better results and increased efficiency in their Agile development practices.

A Use Case is defined as a sequence of steps that specifies the interaction between one or more interfacing elements and the system. It outlines the actions and events that occur when a user interacts with a system to achieve a specific goal. Use Cases are commonly used in software development to capture and document the functional requirements of a system and serve as a basis for testing and validation. They provide a clear understanding of how the system should behave and help in identifying potential issues or improvements.

The development team should contact production about making a new service go live as early as possible. This allows for ample time to address any potential issues or challenges that may arise during the process. By contacting production early, the team can ensure that all necessary preparations and coordination are in place to successfully launch the new service. It also allows for proper testing and validation to be conducted, minimizing the risk of any unexpected problems during the go live phase.

Anyone can raise an Incident Report. This means that anyone who witnesses or experiences an incident can report it, regardless of their role or position within the organization. This inclusive approach allows for a wide range of individuals to contribute to incident reporting, ensuring that all incidents are properly documented and addressed. It also encourages a culture of transparency and accountability, as it empowers everyone to take responsibility for reporting incidents and promoting a safe and secure working environment.

To minimize attack surfaces, it is important to expose as few points of entry into the system as possible and then defend them rigorously. By limiting the number of entry points, there are fewer opportunities for attackers to exploit vulnerabilities. Additionally, by implementing strong security measures and continuously monitoring and updating the defenses, the system is better protected against potential attacks. This approach helps to reduce the overall attack surface and enhances the security posture of the system.

A problem can be defined as the cause of one or more incidents. When an incident occurs, it is usually a result of an underlying problem. Identifying and addressing the problem is essential to prevent further incidents from happening. Therefore, this definition accurately captures the essence of what a problem represents in a given context.

A user story acts as a requirement in the context of software development. It is a short, simple, and concise description of a feature or functionality from the perspective of an end user. User stories help to capture the needs and expectations of the users and provide a clear understanding of what needs to be developed. They serve as a communication tool between the development team and stakeholders, guiding the development process and ensuring that the final product meets the user's requirements.

Authorization refers to the process of determining whether a user has the necessary privileges or permissions to perform a specific action or access certain resources within a system. It involves verifying the user's identity and then evaluating their permissions or roles to determine if they are allowed to perform the requested action. This helps to ensure that only authorized users can perform certain actions or access sensitive information, thereby maintaining security and preventing unauthorized access or misuse of resources.

A Customer Support Request can be for various purposes such as seeking information or advice, requesting a standard change, or gaining access to an IT service. Therefore, the correct answer is "All of the above" as it encompasses all the mentioned options.

The 'Warranty Period' for developers refers to the time in which they are available to provide support during and after the software's launch. This means that developers will assist with any issues or problems that may arise during this period, ensuring that the software is functioning correctly and meeting the requirements of the users.

The correct answer is Confidentiality, Integrity, Availability. These three concepts, commonly known as the CIA triad, are fundamental principles in information security. Confidentiality ensures that information is accessible only to authorized individuals or entities. Integrity ensures that information is accurate, complete, and unaltered. Availability ensures that information is accessible and usable when needed. By considering these three aspects, organizations can protect their data from unauthorized access, maintain its accuracy and reliability, and ensure its availability to authorized users.

PMX is not a step by step guide to software development within M&IB. Therefore, the correct answer is False.

A data element dictionary contains all of the above items for each entry. It includes the name and type of the data element, the default value or a reference to a use case where it is used, and the valid domain of the data element along with its default value.

"In Progress" is not an Incident Report Status because it is listed as one of the options in the question. The other options, "Open," "Resolved," and "Closed," are all commonly used incident report statuses in various industries.

A closed question is used to extract specific information from the interviewee. It typically requires a short and concise answer, often a "yes" or "no" response. These types of questions are useful when the interviewer wants to gather specific details or facts and does not require a lengthy explanation. By asking closed questions, the interviewer can narrow down the information and focus on specific aspects of the topic being discussed.

The Integration Manager is not an incident management role because their primary responsibility is not related to managing and resolving incidents. The role of an Integration Manager typically involves coordinating and overseeing the integration of different systems or components within an organization. They focus on ensuring smooth integration and functionality of various systems, rather than directly handling and resolving incidents that occur within those systems.

Once a use case starts, it continues until a successful or adverse result is achieved. This means that the use case will keep running until it reaches a desired outcome or an undesired outcome. It does not necessarily depend on whether all requirements are met, all inputs have been processed, or all outputs have been identified. The focus is on achieving a specific result, regardless of the other factors mentioned.

Planning Poker is a collaborative estimation technique used in Agile project management to identify and address potential issues related to development time. It involves team members assigning a numerical value to each task or user story based on its complexity and effort required. By discussing and comparing these estimates, the team can identify any discrepancies or concerns regarding the development time for specific tasks. This allows for a more accurate and realistic planning process, enabling the team to allocate resources effectively and meet project deadlines.

Agile development does not consider process to be the most important part of developing software. Instead, it emphasizes the importance of individuals and interactions, working software, customer collaboration, and responding to change. While process is still important in agile development, it is not considered the most important aspect.

The main advantage of using a fishbone diagram rather than the "Five Whys" for root cause analysis is that it generates multiple root causes. While the "Five Whys" method focuses on asking five consecutive questions to identify the root cause, the fishbone diagram allows for a more comprehensive analysis by identifying multiple potential causes that can contribute to the problem. This helps in gaining a deeper understanding of the issue and considering various factors that may be influencing it.

A SEV2 Incident Report should be updated at least every hour to ensure that all relevant information is captured and communicated in a timely manner. This allows stakeholders to stay informed about the incident's progress and any changes that may impact resolution efforts. Updating the report more frequently than every hour may be excessive and could hinder the incident response process, while updating it less frequently could lead to delays in providing necessary updates to stakeholders. Therefore, updating the report at least every hour strikes a balance between keeping stakeholders informed and allowing the incident response team to focus on resolving the issue.

The correct answer is "inputs, outputs, initial conditions, final conditions." Functional requirements describe the behavior of a system or its components. Inputs refer to the data or information that is provided to the system, while outputs are the results or outcomes produced by the system. Initial conditions represent the starting state or prerequisites required for the system to function properly, and final conditions specify the expected end state or outcome of the system. These four parts collectively define the functional requirements of a system.

Root causes are the underlying reasons or factors that contribute to a problem. While it is ideal to implement solutions that completely eliminate root causes, it is not always possible or practical. In some cases, a workaround can be used as a temporary solution until a permanent fix can be implemented. Therefore, it is not always true that all root causes must have solutions that completely eliminate them.

The quality of a requirement is not determined by its prioritization. Prioritization is a process of ranking requirements based on their importance or urgency, but it does not directly assess the quality of the requirement itself. Quality measures for requirements typically include factors such as clarity, consistency, and being separate from design.

A system designed with complete mediation includes checks when accessing any objects. This means that before any object is accessed, the system verifies and validates the request to ensure that it is authorized and appropriate. This helps to prevent unauthorized or malicious access to objects within the system. By implementing checks when accessing any objects, the system can enforce security measures and protect the integrity of the system and its data.

Functional and non-functional requirements must be met concurrently means that availability is not only concerned with the system being operational but also with meeting the necessary functionality and performance requirements. It implies that the system should not only be accessible but also able to perform its intended functions and meet the performance criteria at the same time. This ensures that the system is available and usable for the users when they need it, without any compromise on its functionality or performance.

Transactional Performance Testing involves testing the performance of a system during normal operations, as well as its ability to handle backup and restore processes and disaster recovery scenarios. Normal operations refer to the regular functioning of the system under typical conditions. Backup and restore testing ensures that the system can effectively backup and restore data without impacting its performance. Disaster recovery testing evaluates the system's ability to recover and resume operations after a catastrophic event. Integration, on the other hand, involves testing the interaction between different components or systems and is not specifically related to transactional performance testing.