Requirements Engineering For Software And Systems 3rd Edition Phillip A Laplante - Solutions

Discover comprehensive solutions for "Requirements Engineering For Software And Systems 3rd Edition" by Phillip A. Laplante. Access the answers key and solutions manual with ease, providing step-by-step answers to solved problems. Explore a vast range of questions and answers, including chapter solutions and a detailed test bank. Whether you're an instructor seeking a manual or a student in search of a textbook guide, our platform offers free downloads of solutions in PDF format. Enhance your understanding and improve your skills with our online resources tailored to meet your educational needs.

What are some of the major objections and deterrents to proper requirements engineering activities?
How is requirements engineering different for “small” systems?
What are some factors that may cause customers to alter requirements?
What issues might arise when a requirements engineer, who is not a subject matter expert, enlists a subject matter expert to assist in defining requirements?
List some representative user requirements, system requirements, and software specifications for 1.5.1 The pet store POS system 1.5.2 The baggage handling system
List five typical functional requirements for 1.6.1 The pet store POS system 1.6.2 The baggage handling system
List five forbidden functional requirements for 1.7.1 The pet store POS system 1.7.2 The baggage handling system
Identify the nonfunctional requirements in 1.8.1 The specification for the smart home system in Appendix A 1.8.2 The specification for the wet well pumping system in Appendix B
List five possible nonfunctional requirements for 1.9.1 The pet store POS system 1.9.2 The baggage handling system
Conduct some Web research to discover prevailing regulations or standards(NFR) for smart home systems.
For the smart home system make a list of some of the hazards (what this system shall not do) based on the regulations you discovered in Exercise 1.9 and any other information you might have.
A product line is a set of related products that share certain features. Product lines may be planned or they may emerge. What are some of the requirements engineering challenges for product lines? How does the “one-shot solution” aspect of Ritter and Webber’s wicked problem apply? You may
Who is paying for the system?
Who is going to use the system?
Who is going to judge the fitness of the system for use?
What agencies (government) and entities (nongovernment) regulate any aspect of the system?
What laws govern the construction, deployment, and operation of the system?
Who is involved in any aspect of the specification, design, construction, testing, maintenance, and retirement of the system?
Who will be negatively affected if the system is built?
Who else cares if this system exists or doesn’t exist?
Who have we left out?
Who is paying for the system?—airline, grants, passengers, your tax dollars.
Who is going to use the system?—airline personnel, maintenance personnel, travelers (at the end).
Who is going to judge the fitness of the system for use?—airline, customers, unions, FAA, OSHA, the press, independent rating agencies.
What agencies (government) and entities (nongovernment) regulate any aspect of the system?—FAA, OSHA, union contracts, state and local codes.
What laws govern the construction, deployment, and operation of the system?—various state and local building codes, federal regulations for baggage handling systems, OSHA laws.
Who is involved in any aspect of the specification, design, construction, testing, maintenance, and retirement of the system?—various engineers, technicians, baggage handlers union, etc.
Who will be negatively affected if the system is built?—passengers, union personnel.
Who else cares if this system exists or doesn’t exist?—limousine drivers.
Who have we left out?
Who is paying for the system?—pet store, consumers.
Who is going to use the system?—cashiers, managers, customers (maybe if self-service is provided). Who else?
Who is going to judge the fitness of the system for use?—company execs,managers, cashiers, customers. Who else?
What agencies (government) and entities (nongovernment) regulate any aspect of the system?—tax authorities, governing business entities, pet store organizations, better business bureau. What else?
What laws govern the construction, deployment, and operation of the system?—tax laws, business, and trade laws. What else?
Who is involved in any aspect of the specification, design, construction, testing, maintenance, and retirement of the system?—various engineers, CFO,managers, cashiers. We need to know them all.
Who will be negatively affected if the system is built?—manual cash register makers, inventory clerks. Who else?
Who else cares if this system exists or doesn’t exist?—competitors, vendors of pet products. Who else?
Why is it important to have a concept of operation or mission statement at the start of requirements engineering?
What is the relationship of a system or product mission statement to a company’s mission statement?
When should a domain vocabulary be established?
At what stage of the requirements development are additions to the requirements considered scope creep?
Create a rich picture for the 2.5.1 Baggage handling system 2.5.2 Smart home system (Appendix A)2.5.3 Wet well pumping control system (Appendix B)
Using a block diagram or rich picture show the context for 2.6.1 The pet store POS system 2.6.2 The baggage handling system 2.6.3 The smart home system
Under what circumstances might the customer’s needs and desires be considered secondary?
Think of an everyday product that you use.2.8.1 Try to guess what the mission statement is for the company that manufactures the product.2.8.2 Search the Internet for the actual mission statement and compare it to your guess. If it exists, how does the actual mission statement compare to your guess?
List five goals for the airline baggage handling system.
List three more stakeholders (other than those already given) and their primary concern for 2.10.1 The baggage handling system 2.10.2 The pet store POS system
Create a comprehensive list of user subclasses for the smart home system described in Appendix A if it were to be built for an arbitrary set of residents and visitors (not just the current user set of two older adults).
Create a list of subclasses for the following stakeholders:2.12.1 Customers for the pet store POS system 2.12.2 Travelers for the baggage handling system 2.12.3 Patients in an IoT healthcare system
For the following, describe whether stakeholder elicitation should use a representative, sample, or exhaustive approach:2.13.1 Systems administrators for the pet store POS system 2.13.2 Maintenance technicians for the baggage handling system 2.13.3 Homeowners for the smart home system 2.13.4 Nurses
Investigate the KAOS requirements modeling methodology and discuss how goals are modeled in this approach.
On a scale of one to five, five being most important, how would you rate this feature?
How important is this feature with respect to other features?
What other features are dependent on this feature?
What other features must be independent of this feature?
What other observations can you make about this feature?
Identify stakeholder’s attributes or requirements.
Identify technical features of the requirements.
Relate the requirements to the technical features.
Conduct an evaluation of competing products.
Evaluate technical features and specify a target value, for each feature.
Prioritize technical features for development effort.
How many unique products (SKUs) do you carry in your inventory?(a) 0–1000; (b) 1001–10,000; (c) 10,001–100,000; (d) >100,000
How many different warehouse sites do you have? ____
How many different store locations do you have? ____
How many unique customers do you currently have? ___
What are some different user classes for the smart home system described in Appendix A?
What are some difficulties that may be encountered in attempting to elicit requirements without face-to-face interaction?
Does the Heisenberg uncertainty principle apply to techniques other than ethnographic observation? What are some of the ways to alleviate the Heisenberg uncertainty principle?
During ethnographic observation, what is the purpose of recording the time and day of the observation made?
Should requirements account for future scalability and enhancements?
Which subset of the techniques described in this chapter would be appropriate for a setting where the customers are geographically distributed?
Investigate the concept of “active listening.” How would this technique assist in requirements elicitation?
Which elicitation techniques would you use to elicit system requirements from the following stakeholder groups?3.8.1 Passengers in the baggage handling system 3.8.2 Cashiers in the pet store POS system 3.8.3 Doctors in the IoT healthcare system described at the end of Chapter 2
If you are working on a course project, list the elicitation techniques that you would you use to elicit system requirements from each of the stakeholder groups.
There are several “shall not” requirements in the SRS of Appendix A. Which, if any, of these would you consider to be hazards?
Speculate as to why there are no “shall not” requirements in the SRS in Appendix B.
For the pet store point of sale system, develop an antimodel pertaining to inventory control. For example, the system should not record negative inventory.Write the corresponding “shall not” requirements for this antimodel.
Under what circumstances is it appropriate to represent an SRS using informal techniques only?
What can the behavioral specification provide that a requirements document cannot?
If the customer requests that future growth and enhancement ideas be kept, where can these ideas be placed?
What are some items to be included under “data retention” in the SRS?
Here are some more examples of vague and ambiguous requirements that have actually appeared in real requirements specifications. Discuss why they are vague, incomplete, or ambiguous. Provide improved versions of these requirements (make necessary assumptions).4.5.1 The tool will allow for expedited
In Section 9.4 of the SRS in the appendix, which requirements are suitable for representing using the “measurable targets” in the format shown in Figure 4.4?
Many of the requirements in the appendix can be improved in various ways. Select ten requirements listed and rewrite them in an improved form.Discuss why your rewritten requirements are superior using the vocabulary of IEEE 29148.
Convert the following “shall not” requirements in Appendix A to “shall”format: 4.1.1, 5.2.2, 6.1.8, 8.1.17.
Convert the following “shall not” requirements in Appendix A to “shall”format: 9.1.2.6, 9.3.3, 9.3.5, 9.3.13, 9.5.10.
Research different techniques for creating context diagrams and prepare a report highlighting the strengths and weaknesses of each.
The requirements specifications in Appendices A and B use imperatives inconsistently. Using a textual analysis tool such as ARM or via manual analysis, assess the use of imperatives in these documents and suggest improvements.
What can be some pitfalls to consider when ranking requirements?
Describe two different ways to identify ambiguity in an SRS.
Which of the IEEE Standard qualities for individual requirements seem most important? Can you rank these?
Conduct an informal assessment of the IEEE 29148 qualities for the SRS given in Appendix B.
For an available SRS document, conduct an informal assessment of its IEEE 29148 qualities.
Should implementation risk be discussed with customers?
What are the advantages and risks of having requirements engineering conducted (or assisted) by an outside firm or consultants?
Create a traceability matrix for the SRS in 5.8.1 Appendix A 5.8.2 Appendix B
Calculate the requirements per test and tests per requirements metrics for the data shown in Table 5.2. Do you see any inconsistencies?
Consider the requirements in the SRS of Appendix A.5.10.1 Which of these could be improved through the use of visual formalisms such as various UML diagrams?5.10.2 Select three of these and create the visual formalism.

Showing 1 - 100 of 329

Requirements Engineering For Software And Systems 3rd Edition Phillip A Laplante - Solutions

Step by Step Answers