Consider the following scenario: you have a team of seven to nine people working on a huge project with a solid architecture, partly stated requirements, and all team members onsite, indicating that there are no remote teams. Which incremental software development process paradigm would you recommend? Justify your stance

Consider the following scenario: you have a team of seven to nine people working on a huge project with a solid architecture, partly stated requirements, and all team members onsite, indicating that there are no remote teams. Which incremental software development process paradigm would you recommend? Justify your stance

Principles of Information Systems (MindTap Course List)

12th Edition

ISBN:9781285867168

Author:Ralph Stair, George Reynolds

Publisher:Ralph Stair, George Reynolds

Chapter13: Systems Development: Construction, Integration And Testing, Implementation, Operation And Maintenance, And Disposal

Section: Chapter Questions

Problem 11RQ

See similar textbooks

Similar questions

Consider the following scenario: you have a team of seven to nine people working on a huge project with a solid architecture, with needs that are only partly specified, and with all team members present on site, indicating that there are no remote teams. Please advise on the most effective incremental software development process paradigm to use. Justify your point of view.
Consider the following scenario: you have a team of seven to nine employees working on a large project with a strong architecture, with partially defined requirements and all team members onsite, meaning that no remote teams exist. Which process paradigm for incremental software development would you recommend? Justify your position.
Consider the following scenario: you have a team of seven to nine people working on a large project with a strong architecture where requirements are partially stable and all team members are onsite, which means there are no distributed teams. Which process model would you recommend for incremental development of a software product? Give a good rationale.
Consider the following scenario: a large project with a strong architecture, partially specified needs, and all team members onsite, suggesting no remote teams. Which iterative software development model would you suggest? Defend your viewpoint.
Consider the following scenario: you have a team of seven to nine individuals working on a big project with a strong architecture where the needs are partly solid and all team members are onsite, implying that no remote teams exist. Which process model would you suggest for incremental software development? Give a solid reason.
Assume a huge project with a well-defined design and fairly predictable needs is being worked on by a team of seven to nine people. No need for distributed teams when everyone is in the same room at the same time. How would you propose doing software development in small, incremental steps? Do you have any opinions on this?
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.
Take into consideration the following scenario: a huge project with a solid architecture, partly stated requirements, and all team members working onsite, implying that there are no remote teams. Which iterative approach of software development would you recommend, and why? Defend your opinion.
There are cases where an explicit implementation modeling activity, performed by trained OO analyst/designers, might be very important. Which is correct? A. If you intend to generate code directly from the model and if you are doing component based development (CBD) to reuse components. B. If you are considered a packaged solution from a software vendor. C. If you are re-developing an existing application for security reasons. D. If the project is not based on OO principles
Let's say you have a major project with a well-defined architecture and somewhat predictable requirements, and your team consists of seven to nine people. There are no remote teams since everyone is there at the same time. What approach do you suggest for incremental software development? Think things through?
A new project has an average novelty for the software supplier that is going to execute it. Development flexibility is high, and requirements may change radically. The development team is all located at the same office and the software house as a whole tends to be formal in its standards and procedures. The product should be very reliable, and the algorithms are complex. The supplier would like to reuse the project with suitable modifications on further contracts. Developers are familiar with the platform and they are capable of conducting this specific type of project. The toolsets available to the development team are judged to be typical for this size of company, but schedule pressure is tight to meet a deadline.
Imagine a team of seven to nine persons working on a huge project with a robust architecture, mostly predictable needs, and no scattered teams. What process paradigm is best for incremental software development? Explain.