Software Engineering (Pnq)

Project management involves balancing all the options, which include quality, scope, resources, and time. This means that project managers need to ensure that these factors are properly managed and coordinated to achieve successful project outcomes. By balancing these factors, project managers can ensure that the project is delivered within the specified scope, with the required quality standards, utilizing the available resources efficiently, and meeting the designated timeline.

The correct answer is "high" because the banking industry deals with sensitive financial information and transactions. Security is of utmost importance to protect the client's assets, personal information, and prevent fraud or unauthorized access. Therefore, a high level of security is necessary to ensure the safety and confidentiality of the client's data and transactions.

The project manager is responsible for overseeing all aspects of a project, including profitability, business development, utilization, and scheduling. They are concerned with ensuring that the project is profitable, contributes to the overall business development goals, maximizes resource utilization, and adheres to the project schedule. Therefore, all the options mentioned are valid concerns for the project manager.

The given statement is false. Software development involves more than just coding. It includes various activities such as requirements gathering, analysis, design, testing, and maintenance. Coding is an important part of the software development process, but it is not the only aspect. The development process involves a series of steps that are followed to create a software product that meets the desired requirements and quality standards.

Software metrics are used to measure various aspects of software development. This includes both the process and the product. By measuring the process, we can assess the efficiency and effectiveness of the software development process, identify areas for improvement, and track progress over time. On the other hand, measuring the product allows us to evaluate its quality, reliability, performance, and other attributes. Therefore, software metrics are used to measure both the process and the product in order to ensure the successful development and delivery of high-quality software.

The stages that SDLC covers in software development are requirements, design, testing, coding, and maintenance. These stages represent the sequential steps involved in the development process. The requirements stage involves gathering and analyzing the needs and expectations of the stakeholders. The design stage involves creating a blueprint or plan for the software solution. The testing stage involves verifying and validating the software against the specified requirements. The coding stage involves writing the actual code for the software. Finally, the maintenance stage involves making updates, enhancements, and bug fixes to the software throughout its lifecycle.

Delivery management runs in parallel to the software development life cycle (SDLC). This means that the activities and processes involved in delivering the software product, such as planning, testing, and deployment, occur simultaneously and independently alongside the phases of the SDLC. This parallel approach allows for efficient and timely delivery of the software, ensuring that it aligns with the development process and meets the project's objectives.

Good coding improves the readability and maintainability of the code. Readability refers to how easily the code can be understood by other developers, making it easier to collaborate and maintain the code in the long run. Maintainability refers to how easily the code can be modified or updated without introducing errors or breaking functionality. By focusing on these aspects, good coding practices ensure that the code is clear, organized, and easy to work with, leading to more efficient development and less time spent on debugging and fixing issues.

Testing is the activity associated with quality control. Quality control involves ensuring that a product or service meets the desired quality standards. Testing is a crucial part of quality control as it involves checking the product or service for any defects, errors, or deviations from the expected quality. Through testing, any issues or problems can be identified and addressed, ensuring that the final product or service meets the required quality criteria.

The correct answer is waterfall. The question is asking about the model that is used for ordering a plate at a restaurant. The waterfall model is a sequential design process in which progress flows steadily downwards through the phases of requirements analysis, design, implementation, testing, and maintenance. This model suggests that each phase must be completed before the next one can begin, making it suitable for a process like ordering a plate at a restaurant, where each step needs to be followed in a specific order.

Application installation is indeed a part of installation testing. During installation testing, the focus is on ensuring that the application is installed correctly and functions properly on the target system. This includes verifying that all necessary files are installed, dependencies are met, and the application can be launched without any errors or issues. Therefore, the statement "Application Installation is a part of installation testing" is true.

A bug that has been fixed can be reopened if the issue reoccurs or if there are new problems related to the original bug. The fixing of a bug does not guarantee that it will never resurface, as software systems are complex and interconnected. Therefore, it is possible for a previously fixed bug to be reopened for further investigation and resolution.

A process audit is a quality assurance activity that involves examining and evaluating the processes and procedures used in an organization to ensure they are being followed correctly and efficiently. It helps to identify any deviations or inefficiencies in the processes and provides recommendations for improvement. This activity focuses on ensuring that the established processes are being adhered to and that they are effective in achieving the desired outcomes. Code review, coding, and testing are also important activities in software development but they are not specifically focused on evaluating and improving processes, unlike a process audit.

The objectives of testing include checking the presence of errors in the code. This means that during the testing process, the main focus is on identifying any mistakes or bugs in the code. The presence of errors indicates that there are flaws in the code that need to be addressed and fixed. Testing helps to ensure that the code is free from errors and functions correctly, which ultimately leads to a more reliable and efficient software system.

Maintenance is the correct answer because production support involves activities related to maintaining and enhancing the existing software system. It includes tasks such as bug fixing, troubleshooting, and making necessary updates to ensure the system's smooth operation. While waterfall, incremental, and iterative are software development methodologies, maintenance is specifically focused on the ongoing support and maintenance of the software after its initial development and deployment.

A metric is a quality measure that is used to evaluate a specific desirable attribute of software. It provides a quantitative value or measurement to assess the performance or effectiveness of the software. Unlike a defect, which refers to a flaw or malfunction in the software, or a plan, which is a strategy or course of action, a metric focuses on measuring and analyzing the software's attributes. A baseline, on the other hand, is a reference point or starting point for comparison. Therefore, the most appropriate term for a quality measure of a specific desirable attribute of software is a metric.

The given answer "goal" is the correct answer because the question is asking about what needs to be set based on the date from a project of similar nature executed previously from OLBM. In this context, setting a goal for the project is essential as it provides a clear direction and purpose for the project. By referring to the data from previous projects, the goal can be defined and aligned with the objectives and expectations of OLBM.

Defect density refers to the number of defects found in a product or system per unit of measurement, such as lines of code or functionality. It directly affects the quality of the product, as a higher defect density indicates a higher likelihood of errors or flaws in the product. Therefore, defect density has a significant impact on product quality.

OLBM stands for Organizational Level Business Model. Project quality goals are typically found in the OLBM, which outlines the overall business objectives and strategies of the organization. This document provides a high-level view of the organization's goals, including quality goals, which can then be translated into specific project objectives and requirements. The other options, such as proj estimates, work mgmt plan, and metric plan, may contain information related to project quality, but the OLBM is the most comprehensive and strategic document where project quality goals are typically defined.

The answer suggests that the baseline, which is the original plan or target, needs to be reviewed because the capability of the project has improved. This means that the project is performing better than expected, as it is delivering at a schedule variance of 2%-1% instead of the goal of h%. Therefore, it is necessary to reassess the baseline to reflect the improved capability and make necessary adjustments to the project plan.

This project can be classified as medium because the duration of 4 months and effort of 45 person months falls within the range typically associated with medium-sized projects. Large projects usually have longer durations and require more effort, while small and very small projects have shorter durations and require less effort. Therefore, based on the given information, medium is the most appropriate classification for this project.

A process audit is a quality assurance activity that involves examining and evaluating the processes and procedures used in a project or organization to ensure they are being followed correctly and efficiently. This activity helps identify any deviations or non-compliance with established standards, allowing for corrective actions to be taken to improve the overall quality of the project or organization. Testing, code review, and coding are also important activities in software development but are not specifically focused on evaluating and improving processes like a process audit.

Iterative software development is the appropriate approach for a client with rapidly changing requirements. This approach involves breaking down the development process into smaller iterations or cycles, where each iteration focuses on a specific set of requirements. After each iteration, feedback is obtained from the client and adjustments are made accordingly. This iterative process allows for flexibility and adaptability to changing requirements, ensuring that the final system meets the client's evolving needs.

Quality management refers to the overall process of planning, controlling, and improving the quality of products or services within an organization. It involves various activities such as setting quality standards, implementing quality control measures, conducting quality audits, and continuously monitoring and improving quality. Quality management ensures that all aspects of the organization's operations are focused on delivering high-quality products or services that meet customer expectations and comply with relevant quality standards.

A project with 8 members and a duration of 12 months is considered large because it involves a significant number of team members and a substantial amount of time. Large projects typically require extensive planning, coordination, and resources to successfully complete. The size of the project team and the duration suggest that it is a complex and significant undertaking.

The answer "s/w dev method" is the correct choice because a high-quality program requires a well-defined and structured software development methodology. This methodology ensures that the software is developed in a systematic and organized manner, following best practices and industry standards. It includes processes such as requirement analysis, design, coding, testing, and maintenance. By following a software development method, developers can ensure that the program is reliable, maintainable, and meets the desired quality standards.

The correct answer is 3 because having too many if..then..else statements in a program can make it complex and difficult to understand. It is generally recommended to keep the number of conditional statements to a minimum to improve code readability and maintainability. Having more than 3 if..then..else statements in a program may indicate a need for refactoring or redesigning the code to make it more efficient and organized.

Delivery Quality is a metric goal that maps to the overall quality of the product or service being delivered to the customers. It focuses on meeting customer expectations, ensuring that the deliverables are of high quality, and minimizing defects or errors. By prioritizing Delivery Quality as a metric goal, the organization aims to improve customer satisfaction, maintain a good reputation, and achieve long-term success in the market.

The tester closes the defect because it is their responsibility to identify and report any defects or issues found during the testing process. They are responsible for verifying that the defect has been fixed and retesting the system to ensure it is working correctly. The reviewer and developer may also be involved in the defect resolution process, but ultimately it is the tester who determines when the defect can be closed.

Analysis is not a part of delivery management because it is typically conducted before the delivery phase. Analysis involves gathering and interpreting data, evaluating options, and making informed decisions. Delivery management, on the other hand, focuses on the actual implementation and coordination of the project or service. It includes activities such as planning, organizing, and controlling the delivery process to ensure successful outcomes. Therefore, analysis is not directly related to the execution and control of delivery, making it the correct answer.

After the design stage, when a change of request occurs, it is important to perform an impact analysis. This involves evaluating the potential effects and consequences of implementing the change. In this case, since the coding has not started yet, the impact is likely to be less significant. However, it is still necessary to assess the potential implications of the change on the design and overall project. Rejecting the change and proceeding with the coding may not be the best approach, as it is important to consider the potential impacts before making a decision. Therefore, the correct answer is to conduct an impact analysis.

6 sigma is a methodology used to improve business processes by reducing defects and errors. It focuses on achieving a high level of quality and consistency in products or services. By implementing 6 sigma, organizations can identify and eliminate variations in their processes, leading to increased efficiency and customer satisfaction. This methodology is widely used in industries such as manufacturing, healthcare, and finance to drive continuous improvement and achieve operational excellence.

A code review is a process where one or more developers review the code written by another developer to identify any errors, bugs, or potential improvements. This is done to ensure the code meets the required standards and is of high quality. It involves analyzing the code for readability, efficiency, and adherence to coding conventions. The purpose of a code review is to catch mistakes early, improve the overall codebase, and promote collaboration and knowledge sharing among team members. Therefore, a code review is an example of peer review.

The given statement is true because unit test cases are designed to test individual components or units of a system, while integration test cases are designed to test the interaction between these components. If the unit test cases pass successfully, it indicates that the individual components are functioning correctly. Therefore, when these components are integrated, they should ideally work together without any issues, leading to the integration test cases also passing.

Comments do not improve the readability of poorly written code. In fact, if the code is poorly written, comments can sometimes add confusion or be misleading. It is better to focus on writing clean and understandable code rather than relying on comments to explain it.

Elicitation is the stage in which business needs, concerns, and high-level requirements are identified in the mind of customers. This involves gathering information from stakeholders through various techniques such as interviews, surveys, and workshops. It is an important step in the requirements gathering process as it helps in understanding the customers' expectations and goals, which then serves as a basis for further analysis and documentation.

The team structure is mentioned in the SPP document.

BS 7799 is the correct answer because it is a British standard for information security management systems. It provides a framework for organizations to establish, implement, operate, monitor, review, maintain, and improve their information security management system. Cognizant, being a multinational technology company, would prioritize information security and may adopt this standard to ensure the confidentiality, integrity, and availability of their information assets. BS 7788 and BS 7779 are not relevant standards in this context and may not be applicable to Cognizant's security practices.

A contract is the output of formalization, which refers to the process of making something formal or official. In the context of a contract, formalization involves documenting and finalizing the terms and conditions agreed upon by the parties involved. It ensures that the agreement is legally binding and provides clarity and protection for all parties. The other options, closure, startup, and proposal, do not directly relate to the creation of a contract.

Business understanding is part of the proposal phase. During this phase, the business requirements and objectives are analyzed and understood in order to develop a comprehensive proposal. This involves gathering information about the business, its industry, target market, competitors, and other relevant factors. By understanding the business, its needs, and its goals, a well-informed and tailored proposal can be created to address these specific requirements and provide solutions.

During the design phase of a project, test cases are indeed written. This is because test cases help in defining the expected behavior of the system or software being developed. By writing test cases during the design phase, the development team can ensure that the requirements and specifications are being met. It also helps in identifying any potential issues or bugs early on, allowing for necessary adjustments to be made before the development phase begins. Therefore, it is important to write test cases in the design phase to ensure the quality and functionality of the final product.

Unit test cases are not insensitive to the number of iterations of the code. The number of iterations can affect the behavior and outcome of the code, which in turn can impact the test results. Test cases should be designed to cover different scenarios and iterations of the code to ensure comprehensive testing and accurate results. Therefore, the statement "Unit Test cases are insensitive to the number of iterations of the code" is false.

Rational Robot is a test automation tool developed by IBM. It is primarily used for functional and regression testing of software applications. While Rational Robot does have the capability to record and playback test scripts, it does not specifically focus on developing VB Script. Instead, Rational Robot uses its own scripting language called "Rational TestScript Language" (RTL) for test automation. Therefore, the statement that Rational Robot is used to develop VB Script for recording is false.

The term "iteration" refers to the process of repeating a set of instructions or steps multiple times in order to achieve a desired outcome. In the context of buying a branded computer, iteration could mean that the buyer goes through multiple rounds of analysis and comparison before making a decision. This could involve evaluating different brands, models, and features, and iterating the process until the buyer finds the best fit for their needs.

The word "maintenance" is the most suitable answer because it is often associated with the ongoing process of keeping something in good condition or functioning properly. In the context of knowledge, maintenance refers to the continuous effort of updating and preserving knowledge to ensure its accuracy and relevance over time. This aligns with the idea that knowledge requires regular attention and care to stay current and reliable.

In unit testing, test cases should be independent of each other to ensure accurate and reliable results. However, if unit test cases are dependent on each other, it means that the outcome of one test case affects the outcome of another. This can lead to false positives or false negatives in the test results, making it difficult to identify the actual issues in the code. Therefore, it is important to ensure that unit test cases are designed to be independent of each other.

The given equation calculates the review efficiency, which is the ratio of the total number of defects found during the review process to the total number of defects found during both the review and testing phases. This metric helps measure the effectiveness of the review process in identifying and addressing defects before the software goes into testing. A higher review efficiency indicates a more thorough and effective review process, leading to a higher quality product.

The correct answer is False. Unit testcases are not written just after coding the unit. Unit testing is a software testing method where individual units or components of a software are tested. Unit testcases are usually written before or during the coding process to ensure that each unit of code is functioning correctly. Writing testcases after coding the unit may lead to overlooking certain aspects of the code and can result in incomplete or ineffective testing.

The tear down in JUnit refers to the process of executing certain code or actions after the execution of a test case. It is used to clean up any resources or variables that were created during the test case, ensuring that the environment is left in a consistent state. This is typically done to avoid any interference between different test cases and to prepare for the next test case execution.

Peer review ensures that defects in the code are identified and documented. It involves a group of peers reviewing the code to identify any potential defects or issues. By logging these defects, the development team can prioritize and address them early in the development process, ensuring that they are rectified before the code is delivered. This helps in improving the overall quality of the code and reducing the chances of defects going unnoticed or causing issues later on.