Develop the following systems using the deployment pattern:
1. Software deployment is all of the activities that make a software system available for use. The general deployment process consists of several interrelated activities with possible transitions between them. These activities can occur at the producer side or at the consumer side or both. Because every software system is unique, the precise processes or procedures within each activity can hardly be defined. Therefore, “deployment” should be interpreted as a general process that has to be customized according to specific requirements or characteristics. A brief description of each activity will be presented later [6].
2. The military of the United States is deployed in more than 150 countries around the world, with over 150,000 of its active-duty personnel serving outside the United States and its territories and an additional 71,000 deployed in various contingency operations as well as through military attache offices and temporary training assignments in foreign countries [7].
3. A Rapid deployment force is a military formation capable of quick deployment of its forces. Such forces typically consist of elite military units (special ops, paratroopers, marines, etc.) and are usually trained at a higher intensity than the rest of their country’s military. They usually receive priority in equipment and training to prepare them for their mission. Quick response force (QRF) should not be confused with rapid deployment forces (US) or rapid response (NATO). QRF units are most often units that react to local or regional issues within their area of jurisdiction, that is, National Guard, militias, Forward Deployed, para-military forces, etc.

a. List all the functional requirements and nonfunctional requirements for each area.

b. List two challenges for each area.

c. Name five contexts for each area.

d. Draw the application of the pattern for each context in c.

e. Select a significant use case per application and describe each one of them with test cases.

f. Map each use case in e into a sequence diagram.