New Semester
Started
Get
50% OFF
Study Help!
--h --m --s
Claim Now
Question Answers
Textbooks
Find textbooks, questions and answers
Oops, something went wrong!
Change your search query and then try again
S
Books
FREE
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
Tutors
Online Tutors
Find a Tutor
Hire a Tutor
Become a Tutor
AI Tutor
AI Study Planner
NEW
Sell Books
Search
Search
Sign In
Register
study help
computer science
introduction to software engineering
Software Engineering A Practitioner's Approach 7th Edition Roger Pressman - Solutions
4.11. What three “domains” are considered during requirements modeling?
4.12. Try to add one additional principle to those stated for coding in Section 4.3.4.
4.13. What is a successful test?
4.14. Do you agree or disagree with the following statement: “Since we deliver multiple increments to the customer, why should we be concerned about quality in the early increments—we can fix problems in later iterations.” Explain your answer.
4.15. Why is feedback important to the software team?
Are requirements stated clearly? Can they be misinterpreted?
Is the source (e.g., a person, a regulation, a document)of the requirement identified? Has the final statement of the requirement been examined by or against the original source?
Is the requirement bounded in quantitative terms?
What other requirements relate to this requirement? Are they clearly noted via a cross-reference matrix or other mechanism?
Does the requirement violate any system domain constraints?
Is the requirement testable? If so, can we specify tests(sometimes called validation criteria) to exercise the requirement?
Is the requirement traceable to any system model that has been created?
Is the requirement traceable to overall system/product objectives?
Is the specification structured in a way that leads to easy understanding, easy reference, and easy translation into more technical work products?
Has an index for the specification been created?
Have requirements associated with performance, behavior, and operational characteristics been clearly stated? What requirements appear to be implicit?
Who is behind the request for this work?
Who will use the solution?
What will be the economic benefit of a successful solution?
Is there another source for the solution that you need?
How would you characterize “good” output that would be generated by a successful solution?
What problem(s) will this solution address?
Can you show me (or describe) the business environment in which the solution will be used?
Will special performance issues or constraints affect the way the solution is approached?
Are you the right person to answer these questions? Are your answers“official”?
Are my questions relevant to the problem that you have?
Am I asking too many questions?
Can anyone else provide additional information?
Should I be asking you anything else?
Meetings are conducted and attended by both software engineers and other stakeholders.
Rules for preparation and participation are established.
An agenda is suggested that is formal enough to cover all important points but informal enough to encourage the free flow of ideas.
A “facilitator” (can be a customer, a developer, or an outsider) controls the meeting.
A “definition mechanism” (can be work sheets, flip charts, or wall stickers or an electronic bulletin board, chat room, or virtual forum) is used.
A statement of need and feasibility.
A bounded statement of scope for the system or product.
A list of customers, users, and other stakeholders who participated in requirements elicitation.
A description of the system’s technical environment.
A list of requirements (preferably organized by function) and the domain constraints that apply to each.
A set of usage scenarios that provide insight into the use of the system or product under different operating conditions.
Any prototypes developed to better define requirements.
Who is the primary actor, the secondary actor(s)?
What are the actor’s goals?
What preconditions should exist before the story begins?
What main tasks or functions are performed by the actor?
What exceptions might be considered as the story is described?
What variations in the actor’s interaction are possible?
What system information will the actor acquire, produce, or change?
Will the actor have to inform the system about changes in the external environment?
What information does the actor desire from the system?
Does the actor wish to be informed about unexpected changes?
Enters a password to allow all other interactions.
Inquires about the status of a security zone.
Inquires about the status of a sensor.
Presses the panic button in an emergency.
Activates/deactivates the security system.
1. Identification of the system or subsystem’s key stakeholders.
2. Determination of the stakeholders’ “win conditions.”
3. Negotiation of the stakeholders’ win conditions to reconcile them into a set of win-win conditions for all concerned (including the software team).
1. Recognize that it’s not a competition. To be successful, both parties have to feel they’ve won or achieved something. Both will have to compromise.
2. Map out a strategy. Decide what you’d like to achieve; what the other party wants to achieve, and how you’ll go about making both happen.
3. Listen actively. Don’t work on formulating your response while the other party is talking. Listen to her. It’s likely you’ll gain knowledge that will help you to better negotiate your position.
4. Focus on the other party’s interests. Don’t take hard positions if you want to avoid conflict.
5. Don’t let it get personal. Focus on the problem that needs to be solved.
6. Be creative. Don’t be afraid to think out of the box if you’re at an impasse.
7. Be ready to commit. Once an agreement has been reached, don’t waffle; commit to it and move on.
Is each requirement consistent with the overall objectives for the system/product?
Have all requirements been specified at the proper level of abstraction? That is, do some requirements provide a level of technical detail that is inappropriate at this stage?
Is the requirement really necessary or does it represent an add-on feature that may not be essential to the objective of the system?
Is each requirement bounded and unambiguous?
Does each requirement have attribution? That is, is a source (generally, a specific individual) noted for each requirement?
Do any requirements conflict with other requirements?
Is each requirement achievable in the technical environment that will house the system or product?
Is each requirement testable, once implemented?
Does the requirements model properly reflect the information, function, and behavior of the system to be built?
Has the requirements model been “partitioned” in a way that exposes progressively more detailed information about the system?
Have requirements patterns been used to simplify the requirements model?Have all patterns been properly validated? Are all patterns consistent with customer requirements?
5.1. Why is it that many software developers don’t pay enough attention to requirements engineering? Are there ever circumstances where you can skip it?
5.2. You have been given the responsibility to elicit requirements from a customer who tells you he is too busy to meet with you. What should you do?
5.3. Discuss some of the problems that occur when requirements must be elicited from three or four different customers.
5.4. Why do we say that the requirements model represents a snapshot of a system in time?
5.5. Let’s assume that you’ve convinced the customer (you’re a very good salesperson) to agree to every demand that you have as a developer. Does that make you a master negotiator? Why?
5.6. Develop at least three additional “context-free questions” that you might ask a stakeholder during inception.
5.7. Develop a requirements gathering “kit.” The kit should include a set of guidelines for conducting a requirements gathering meeting and materials that can be used to facilitate the creation of lists and any other items that might help in defining requirements.
5.8. Your instructor will divide the class into groups of four to six students. Half of the group will play the role of the marketing department and half will take on the role of software engineering. Your job is to define requirements for the SafeHome security function described in this chapter.
5.10. What do use case “exceptions” represent?
5.11. Describe what an analysis pattern is in your own words.
5.12. Using the template presented in Section 5.5.2, suggest one or more analysis pattern for the following application domains:a. Accounting softwareb. E-mail softwarec. Internet browsersd. Word-processing softwaree. Website creation softwaref. An application domain specified by your instructor
5.13. What does win-win mean in the context of negotiation during the requirements engineering activity?
5.14. What do you think happens when requirement validation uncovers an error? Who is involved in correcting the error?
Scenario-based models of requirements from the point of view of various system “actors”
Data models that depict the information domain for the problem
Class-oriented models that represent object-oriented classes (attributes and operations) and the manner in which classes collaborate to achieve system requirements
Flow-oriented models that represent the functional elements of the system and how they transform data as it moves through the system
Behavioral models that depict how the software behaves as a consequence of external “events”
1. What mechanisms protect unauthorized use of this capability by employees of SafeHome Products?
2. Is security sufficient? Hacking into this feature would represent a major invasion of privacy.
3. Will system response via the Internet be acceptable given the bandwidth required for camera views?
4. Will we develop a capability to provide video at a higher frames-per-second rate when highbandwidth connections are available?
6.2. An analysis rule of thumb is that the model “should focus on requirements that are visible within the problem or business domain.” What types of requirements are not visible in these domains? Provide a few examples.
Showing 1300 - 1400
of 1534
First
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Step by Step Answers
Get 50% OFF
Claim Now
