Software Engineering (10th Edition)
10th Edition
ISBN: 9780133943030
Author: Ian Sommerville
Publisher: PEARSON
expand_more
expand_more
format_list_bulleted
Expert Solution & Answer
Chapter 3, Problem 3.10E
Explanation of Solution
Alternatives for the problems faced due to the involvement of the user with development team:
- Changing the user who is involved with the team
- If any user creates problem in the team then, the user must be changed or removed from the team.
- Advantage
- Different perspectives can be obtained from different users by multiple suggestions.
- The suggestions provided by users can be checked separately by discussing about the suggestions among them.
- Disadvantage
- If the project is delayed then extra cost is charged.
- Verifying the user suggestions separately takes lot of time.
- The new users require lot of time to understand the project.
- Involving multiple users in the development team
- Different uses are involved in the team to get different suggestions...
Expert Solution & Answer
Want to see the full answer?
Check out a sample textbook solution
Students have asked these similar questions
When a user is actively involved in the creation of software, there is a risk that the user would "go native." This is one of the potential downsides of this approach. In other words, they adopt the viewpoint of the development team and become blind to the requirements posed by their user colleagues. Give this problem three different viable approaches, and discuss the benefits and drawbacks associated with each one.
One of the potential consequences of actively incorporating a user in the process of developing software is that the user may "go native." That is, they adopt the viewpoint of the development team and lose track of the needs of their user colleagues in the process. Give this problem three different potential solutions, and analyse both the positive and negative aspects of each one.
When a user is intimately connected with a software development team, one of the issues is that they "go native." That is, they adopt the development team's mindset and lose track of their user colleagues' needs. Consider three approaches to avoiding this problem and evaluate the benefits and drawbacks of each.
Chapter 3 Solutions
Software Engineering (10th Edition)
Ch. 3 - Explain why the rapid delivery and deployment of...Ch. 3 - Explain how the principles underlying agile...Ch. 3 - Extreme programming expresses user requirements as...Ch. 3 - Prob. 3.4ECh. 3 - Suggest four reasons why the productivity rate of...Ch. 3 - Compare and contrast the Scrum approach to project...Ch. 3 - Prob. 3.7ECh. 3 - Why is it necessary to introduce some methods and...Ch. 3 - Prob. 3.9ECh. 3 - Prob. 3.10E
Knowledge Booster
Similar questions
- One disadvantage of actively incorporating a user in the software development process is that the user may "go native." That is, they adopt the development team's viewpoint and lose sight of the requirements of their user colleagues. Provide three viable solutions to this problem and weigh the advantages and disadvantages of each.arrow_forwardOne of the downsides of associating a user directly with a software development team is that the user may become "native." Instead of considering the needs of their users, they focus on what the development team has to say. Identify and compare the advantages and disadvantages of three different approaches to this problem.arrow_forwardThe traditional Software Development Life Cycle has been used in a number of successful system development projects (SDLC). What is meant when anything is referred to be "traditional" is this. There are a few disadvantages to this decision, however. Is it beneficial or detrimental to use the SDLC method?arrow_forward
- One disadvantage of actively integrating a user with a software development team is that the user can "go native." That is, they adopt the viewpoint of the development team while ignoring the needs of their user colleagues. Provide three possible solutions to this problem and assess their benefits and drawbacks??arrow_forwardIt's feasible that the software development process's metric use may be elucidated. Everything has to be handled with extreme care.arrow_forwardOne of the problems of having a user closely involved with a software development team is that they may forget the requirements of the organization they represent. That is, they adopt the outlook of the development team and lose sight of the needs of their user colleagues. Suggest one way how you might avoid this problem and discuss at least one advantage and one disadvantage of your approach to solving this problem.arrow_forward
- Take this scenario: a team of seven to nine individuals working on a huge project with a solid architecture and largely predictable needs. All team members are onsite, therefore there are no dispersed teams. Which incremental software development method do you recommend? Reason well.arrow_forwardThe user may "go native" if they are involved too much in the software development process. In other words, they stop thinking like their user colleagues and start thinking like the development team. Give three workable answers to this challenge and discuss their benefits and drawbacks.arrow_forwardIn what way does the software development lifecycle and a focus on the end-users interconnect?arrow_forward
- Could you please explain the various metrics used in the software development lifecycle? Should we really be getting down to the nitty-gritty of this problem?arrow_forwardIf at all possible, could you elaborate on the metrics that go into the software development process?All aspects of the situation must be properly examined.arrow_forwardHow about a rundown of the software development process's metrics if you have the time? Each and every facet of the issue has to be considered.arrow_forward
arrow_back_ios
SEE MORE QUESTIONS
arrow_forward_ios
Recommended textbooks for you
Database System ConceptsComputer ScienceISBN:9780078022159Author:Abraham Silberschatz Professor, Henry F. Korth, S. SudarshanPublisher:McGraw-Hill Education
Starting Out with Python (4th Edition)Computer ScienceISBN:9780134444321Author:Tony GaddisPublisher:PEARSON
Digital Fundamentals (11th Edition)Computer ScienceISBN:9780132737968Author:Thomas L. FloydPublisher:PEARSON
C How to Program (8th Edition)Computer ScienceISBN:9780133976892Author:Paul J. Deitel, Harvey DeitelPublisher:PEARSON
Database Systems: Design, Implementation, & Manag...Computer ScienceISBN:9781337627900Author:Carlos Coronel, Steven MorrisPublisher:Cengage Learning
Programmable Logic ControllersComputer ScienceISBN:9780073373843Author:Frank D. PetruzellaPublisher:McGraw-Hill Education
Database System Concepts
Computer Science
ISBN:9780078022159
Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:McGraw-Hill Education
Starting Out with Python (4th Edition)
Computer Science
ISBN:9780134444321
Author:Tony Gaddis
Publisher:PEARSON
Digital Fundamentals (11th Edition)
Computer Science
ISBN:9780132737968
Author:Thomas L. Floyd
Publisher:PEARSON
C How to Program (8th Edition)
Computer Science
ISBN:9780133976892
Author:Paul J. Deitel, Harvey Deitel
Publisher:PEARSON
Database Systems: Design, Implementation, & Manag...
Computer Science
ISBN:9781337627900
Author:Carlos Coronel, Steven Morris
Publisher:Cengage Learning
Programmable Logic Controllers
Computer Science
ISBN:9780073373843
Author:Frank D. Petruzella
Publisher:McGraw-Hill Education