All Matches
Solution Library
Expert Answer
Textbooks
Search Textbook questions, tutors and Books
Oops, something went wrong!
Change your search query and then try again
Toggle navigation
FREE Trial
S
Books
FREE
Tutors
Study Help
Expert Questions
Accounting
General Management
Mathematics
Finance
Organizational Behaviour
Law
Physics
Operating System
Management Leadership
Sociology
Programming
Marketing
Database
Computer Network
Economics
Textbooks Solutions
Accounting
Managerial Accounting
Management Leadership
Cost Accounting
Statistics
Business Law
Corporate Finance
Finance
Economics
Auditing
Ask a Question
AI Study Help
New
Search
Search
Sign In
Register
study help
business
software testing and quality assurance
Questions and Answers of
Software Testing And Quality Assurance
24.1. Explain why a high-quality software process should lead to high-quality software products.Discuss possible problems with this system of quality management.
understand how measurement may be helpful in assessing some software quality attributes and the current limitations of software measurement.
understand how reviews and inspections are used as a mechanism for software quality assurance;
be aware of the importance of standards in the quality management process and know how standards are used in quality assurance;
understand that software quality is affected by the software development process used;
have been introduced to the quality management process and know why quality planning is important;
23.10. Is it ethical for a company to quote a low price for a software contract knowing that the requirements are ambiguous and that they can charge a high price for subsequent changes requested by
23.9. Some very large software projects involve writing millions of lines of code. Explain why the effort estimation models, such as COCOMO, might not work well when applied to very large systems.
23.8. A software manager is in charge of the development of a safety-critical software system, which is designed to control a radiotherapy machine to treat patients suffering from cancer. This system
23.7. The XP planning game is based around the notion of planning to implement the stories that represent the system requirements. Explain the potential problems with this approach when software has
23.6. Figure 23.14 shows the task durations for software project activities. Assume that a serious, unanticipated setback occurs and instead of taking 10 days, task T5 takes 40 days. Draw up new bar
23.5. Figure 23.14 sets out a number of tasks, their durations, and their dependencies. Draw a bar chart showing the project schedule.
23.4. Cost estimates are inherently risky, irrespective of the estimation technique used. Suggest four ways in which the risk in a cost estimate can be reduced.
23.3. Briefly explain the purpose of each of the sections in a software project plan.
23.2. Explain why the process of project planning is iterative and why a plan must be continually reviewed during a software project.
23.1. Under what circumstances might a company justifiably charge a much higher price for a software system than the software cost estimate plus a reasonable profit margin?
understand how the COCOMO II model can be used for algorithmic cost estimation.
have been introduced to the ‘planning game’, which is used to support project planning in extreme programming;
understand what is involved in project scheduling and the use of bar charts to present a project schedule;
know what sections should be included in a project plan that is created within a plan-driven development process;
understand the fundamentals of software costing and reasons why the price of the software may not be directly related to its development cost;
22.10. As a programmer, you are offered promotion to a project management position but you feel that you can make a more effective contribution in a technical rather than a managerial role.Discuss
22.9. You are asked by your manager to deliver software to a schedule that you know can only be met by asking your project team to work unpaid overtime. All team members have young children. Discuss
22.8. Write a case study in the style used here to illustrate the importance of communications in a project team. Assume that some team members work remotely and it is not possible to get the whole
22.7. What problems do you think might arise in extreme programming teams where many management decisions are devolved to the team members?
22.6. Explain why keeping all members of a group informed about progress and technical decisions in a project can improve group cohesiveness.
22.5. Fixed-price contracts, where the contractor bids a fixed price to complete a system development, may be used to move project risk from client to contractor. If anything goes wrong, the
22.4. In addition to the risks shown in Figure 22.1, identify at least six other possible risks that could arise in software projects.
22.3. Using reported instances of project problems in the literature, list management difficulties and errors that occurred in these failed programming projects. (I suggest that you start with The
22.2. Explain why the best programmers do not always make the best software managers. You may find it helpful to base your answer on the list of management activities in Section 22.1.
22.1. Explain why the intangibility of software systems poses special problems for software project management.
understand key issues that influence team working, such as team composition, organization, and communication.
understand factors that influence personal motivation and what these might mean for software project managers;
have been introduced to the notion of risk management and some of the risks that can arise in software projects;
know the principal tasks of software project managers;
21.10. Suggest how you could use aspects to simplify the debugging of programs.
21.9. Explain why expressing pointcut specifications as patterns increases the problems of testing aspect-oriented programs. To answer this, think about how program testing normally involves
21.8. Explain how aspect interference can arise and suggest what should be done during the system design process to reduce the problems of aspect interference.
21.7. Using the aspect stereotype notation illustrated in Figure 21.15, develop in more detail the Ordering and Monitor aspects, shown in Figure 21.14.
21.6. Using the outline functionality for each viewpoint shown in Figure 21.9, identify six further use cases for the equipment inventory system, in addition to those shown in Figure 21.11.Where
21.5. What viewpoints should be considered when developing a requirements specification for the MHC-PMS? What are likely to be the most important cross-cutting concerns?
21.4. What assumptions underlie the idea that a system should be organized as a core system that implements the essential requirements, plus extensions that implement additional functionality? Can
21.3. What is the difference between a join point and a pointcut? Explain how these facilitate the weaving of code into a program to handle cross-cutting concerns.
21.2. Summarize what is meant by tangling and scattering. Using examples, explain why tangling and scattering can cause problems when system requirements change.
21.1. What are the different types of stakeholder concern that may arise in a large system? How can aspects support the implementation of each of these types of concern?
be aware of the difficulties of testing aspect-oriented systems.
understand how an aspect-oriented approach may be used for requirements engineering, software design, and programming;
have been introduced to the fundamental ideas underlying aspects and aspect-oriented software development;
understand why the separation of concerns is a good guiding principle for software development;
20.10. Why are general-purpose operating systems, such as Linux or Windows, not suitable as real-time system platforms? Use your experience of using a general-purpose system to help answer this
20.9. If a periodic process in the onboard train protection system is used to collect data from the trackside transmitter, how often must it be scheduled to ensure that the system is guaranteed to
20.8. Suggest a possible process architecture for this system.
20.7. A train protection system automatically applies the brakes of a train if the speed limit for a segment of track is exceeded or if the train enters a track segment that is currently signaled
20.6. Design a process architecture for an environmental monitoring system that collects data from a set of air quality sensors situated around a city. There are 5,000 sensors organized into 100
20.5. Show how the Environmental Control pattern could be used as the basis of the design of a system to control the temperature in a greenhouse. The temperature should be between 10 and 30 degrees
20.4. Explain why an object-oriented approach to software development may not be suitable for real-time systems.
20.3. Using the state-based approach to modeling, as discussed in Section 20.1.1, model the operation of an embedded software system for a voice mail system included in a landline phone. This should
20.2. Identify possible stimuli and the expected responses for an embedded system that controls a home refrigerator or a domestic washing machine.
20.1. Using examples, explain why real-time systems usually have to be implemented using concurrent processes.
understand the organization of real-time operating systems and the role that they play in an embedded, real-time system.
understand three architectural patterns that are commonly used in embedded real-time systems design;
have been introduced to a design process for real-time systems, where the software systems are organized as a set of cooperating processes;
understand the concept of embedded software, which is used to control systems that must react to external events in their environment;
19.10. Using an example, explain in detail why the thorough testing of services that include compensation actions is difficult.
19.9. For the example of the vacation package reservation service, design a workflow that will book ground transportation for a group of passengers arriving at an airport. They should be given the
19.8. Explain what is meant by a ‘compensation action’ and, using an example, show why these actions may have to be included in workflows.
19.7. In Section 19.2.1, I introduced an example of a company that has developed a catalog service that is used by customers’ web-based procurement systems. Using BPMN, design a workflow that uses
19.6. Giving reasons for your answer, suggest two important types of applications where you would not recommend the use of service-oriented architecture.
19.5. Design possible input and output messages for the services shown in Figure 19.11. You may specify these in the UML or in XML.
19.4. Define an interface specification for the Currency Converter and Check credit rating services shown in Figure 19.7.
19.3. Using the same notation, extend Figure 19.5 to include definitions for MaxMinType and InDataFault. The temperatures should be represented as integers with an additional field indicating whether
19.2. Explain why SOAs should be based on standards.
19.1. What are the most important distinctions between services and software components?
understand how business process models may be used as a basis for the design of service-oriented systems.
have been introduced to the notion of service composition as a means of service-oriented application development;
understand the service engineering process that is intended to produce reusable web services;
understand the basic notions of a web service, web service standards, and service-oriented architecture;
18.10. Your company wishes to move from using desktop applications to accessing the same functionality remotely as services. Identify three risks that might arise and suggest how these risks may be
18.9. Explain why deploying software as a service can reduce the IT support costs for a company.What additional costs might arise if this deployment model is used?
18.8. Give two advantages and two disadvantages of decentralized and semicentralized peer-to-peer architectures.
18.7. Using a distributed component approach, propose an architecture for a national theater booking system. Users can check seat availability and book seats at a group of theaters. The system should
18.6. Your customer wants to develop a system for stock information where dealers can access information about companies and evaluate various investment scenarios using a simulation system. Each
18.5. You have been asked to design a secure system that requires strong authentication and authorization. The system must be designed so that communications between parts of the system cannot be
18.4. What is the fundamental difference between a fat-client and a thin-client approach to client–server systems architectures?
18.3. Using an example of a remote procedure call, explain how middleware coordinates the interaction of computers in a distributed system.
18.2. Explain why distributed software systems are more complex than centralized software systems, where all of the system functionality is implemented on a single computer.
18.1. What do you understand by ‘scalability ’? Discuss the differences between ‘scaling up’ and‘scaling out’ and explain when these different approaches to scalability may be used.
understand the notion of software as a service, providing web-based access to remotely deployed application systems.
have been introduced to commonly used patterns for distributed systems architectures and know the types of system for which each architecture is most applicable;
understand the client–server computing model and the layered architecture of client–server systems;
know the key issues that have to be considered when designing and implementing distributed software systems;
17.10. It has been suggested that an independent certification authority should be established.Vendors would submit their components to this authority, which would validate that the component was
17.9. Design the interfaces of components that might be used in a system for an emergency control room. You should design interfaces for a call-logging component that records calls made, and a
17.8. Using examples, illustrate the different types of adaptor needed to support sequential composition, hierarchical composition, and additive composition.
17.7. Design the ‘provides’ interface and the ‘requires’ interface of a reusable component that may be used to represent a patient in the MHC-PMS.
17.6. Explain why it is difficult to validate a reusable component without the component source code. In what ways would a formal component specification simplify the problems of validation?
17.5. Using an example of a component that implements an abstract data type such as a stack or a list, show why it is usually necessary to extend and adapt components for reuse.
17.4. Why is it important that components should be based on a standard component model?
17.3. What are the fundamental differences between components as program elements and components as services?
17.2. The principle of component independence means that it ought to be possible to replace one component with another that is implemented in a completely different way. Using an example, explain how
Showing 800 - 900
of 3313
First
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Last