Unified Process vs. Agile Methodologies Use this Discussion to investigate the U

Question

Unified Process vs. Agile Methodologies Use this Discussion to investigate the UP and Agile modelling methodologies. To prepare for this Discussion, read the following: Chapter 14, "Current Trends in System Development" Then, answer the following questions: When would it be unwise to use either of these methodologies? Would you consider using an Agile methodology such as Scrum or XP in one of your projects? Justify your response Would you choose UP over the Agile methodology for some projects? Justify your response.

Explanation / Answer

. Agile Requirements Modeling in a Nutshell Figure 1 depicts the Agile Model Driven Development (AMDD) lifecycle, which depicts how Agile Modeling (AM) is applied by agile software development teams. The critical aspects which we're concerned about right now are initial requirements modeling, iteration modeling, model storming, and acceptance test-driven development (ATDD). The fundamental idea is that you do just barely enough modeling at the beginning of the project to understand the requirements for your system at a high level, then you gather the details as you need to on a just-in-time (JIT) basis. Figure 1. The AMDD lifecycle. 1.1 Initial Requirements Modeling At the beginning of a project you need to take several days to envision the high-level requirements and to understand the scope of the release (what you think the system should do). Your goal is to get a gut feel for what the project is all about, not to document in detail what you think the system should do: the documentation can come later, if you actually need it. For your initial requirements model my experience is that you need some form of: Usage model. As the name implies usage models enable you to explore how users will work with your system. This may be a collection of essential use cases on a Rational Unified Process (RUP) project, a collection of features for a Feature Driven Development (FDD) project, or a collection of user stories for an Extreme Programming (XP) project. Initial domain model. A domain model identifies fundamental business entity types and the relationships between then. Domain models may be depicted as a collection of Class Responsibility Collaborator (CRC) cards, a slim UML class diagram, or even a slim data model. This domain model will contain just enough information: the main domain entities, their major attributes, and the relationships between these entities. Your model doesn

Related Questions

Navigate

• Browse (All)
• Browse U
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.