Problem Group 1 (30 points) - Project Definition and Management

A large consulting outfit, which offers consulting, integration, and software development services for the retail market, has won a contract with a premier national omnichannel retailer (the Client) to develop an innovative, e-comers system that will support partners, suppliers, and customers. The effort takes into account the rapid progress of digital transformation across the industry and is driven by the popularity of online shopping, which has grown rapidly during the COVID-19 pandemic with the trend projected to continue. The initialMinimal Valuable Products (MVPs)and the first full releases of the new system will be focused on (end)customers and will deliver aGuidedOrder and Delivery Managementsystem(GODM).The systemwill providerich functionality and an AI/ML enabled intuitive Ux. The system will learn, build its knowledge of individual registered customers' styles and shopping patterns, predict their needs, provide 3D experiences, and maintain customer loyalty index. The accumulated information, insights and knowledge about customer shopping patterns, market demands and supply fluctuations, will be used in later releases to enhance the supply chain management and the cooperation with partners and suppliers. (The supplier and partner support parts of the system are out of scope for the current project.)

The newGODMsystem will present a dynamic, configurable, customizable, and self-learning user interface. It will allow users to search for specific items, look for or be offered comparable option, review the details of available items, try them online, and place orders. Customers will also be able to update or delete orders. All payments will be done with a credit card. Customers will be able to schedule deliveries and provide delivery instructions, schedule pickups or request shipment, rate the experience, leave comments, and set tips. They will be offered a shopping assistant - a bot or a live person - to assist them with their choices.

Users will be required to create accounts the first time they visit the system. They can set extended profiles, including size, style and designer preferences. The system will track the purchases of individual customers, derive shopping patterns and make recommendations after some initial data is collected and using the preferences set in the user profiles.

The Client employees responsible for online sales shall have a quick and easy access to the latest information about customer orders and deliveries. They will be able to filter, analyze and print orders, schedule deliveries, pickups, or shipments, and track and update the status of any order if manual intervention is needed. The system will also allow them to send notifications to customers about missing items, offer replacements, and to inform them of unexpected changes or delays.

The shopping assistants will be able to interact with the shoppers with text and video chat. They will also be able to create, check and delete orders on customer behalf.

The store managers will use the system to monitor the volume of purchases, salles margins, monthly trends and other configurable KPIs (all generated on a customizable dashboard). They will also be able to review and approve special online sales, seasonal promotions, and set award policies for loyal customers.

The new system shall be integrated into the overall IMS of the retailer, obtaining information on available merchandize, including detailed descriptions, geographic distribution, promotions, discounts, policies, as well as information about new arrivals and special events.

Developers should pay a focused attention to customer experience with the system. Usability, security, response time, availability, and reliability are key requirements as they are of utmost importance for achieving customer loyalty and meeting the Client's objectives.

The Client's IT experts require that they be involved throughout the development of the system and reserve their rights to provide new requirements or change some of them as the development progresses. The GODM functionality will be delivered continuously using an established CICD pipeline with continuous testing, staging and deployment in production. The system will be a cloud-native application and will be deployed on Amazon public could (AWS). The Client has announced a long term partnership with AWS, which will develop and deliver the initial versions of CICD pipelines, offer trading for Client employees and on request to the Consulting company delivering the CODM software. The first MVP should be delivered in 3 months and the first release should be in production and operational in 6 months. After that the system will be transitioned to the Client's IT organization for any future development and upgrades.

The development team working on this project has 9 experienced members/ developers, who have worked together on several projects. Many of them, however, haven't deployed products onAWS.

Based on the above information answer the following questions:

1. What software developmentprocess modelwould you select for the project? Briefly explain why the selected models is a good fit.

1. Create asummary-level use case diagramfor theGODM system. Include key primary and secondary/supporting actors and the essential use cases of the future GODM system.

1. WriteoneUse Case specification using Alister Cockburn's use case template used in the class project and available on Canvas.

1. Create a PBL (product Backlog) for the development of the future system: write at least5User Stories. Use the following User Story format:"As a , I want so that ."

1. Identify 2 risks that may impact the project. Evaluate the probability, and potential impact/effect of the identified risks. Propose risk management strategies.

Extra Credit Question 1:In their paper "Lean Software Development: A Tutorial," Mary Poppendieck and Michael A. Cusumano briefly describe the Kanban system (method/model). Would the Kanban model be suitable for delivering the GODM system? Provide a brief explanation.

Extra Credit Question 2:To reduce the risk of customers not liking their experience with the new system and to enhance the UI design, what type of measures and activates the development company may use?

Problem Group 2 (20 Points) - Modeling (OOAD)

Community Food Donation System (CFDS)

The CFDS system is designed to support grassroot public volunteer efforts aimed at addressing hunger in their communities. The system is available free of charge.

Create aStatic OOA Model (a Class Diagram)reflecting the CFDSrequirements specified below.

Note 1: Represent all information that is documented in the requirements below.

Note 2: If some information is not provided explicitly, make your own assumptions and note them down. Note 3: There may be information that cannot be explicitly captured in the static model you are creating.

TheCFDSshall maintain up to date information about food Recipients, Donors, Moderators, Volunteers, Donated Food Items, Food Orders, Food Item Orders and will support the publishing of a Daily Food Listing to announce the available food items.

The specific requirements for the above entities are as follow:

1. Recipient [R]

Recipientsshall be characterized by a Recipient ID (also used as login id), name, telephone number, street address, and an optional email address.

All Recipients must be pre-registered with the system to be able order food.

Recipients can place Food Orders. Any Recipient may place up to 3 Food Orders daily.

1. Donor [D]

Donors shall be identified by a Donor ID (also used as login id), name, address, email address, and a contact phone number.

There are two, and only two, types of Donors - Enterprise Donors and Private Donors. No other Donor types shall be supported by the system.

Enterprise donors shall have an ERN (Enterprise Registration Number) attribute and a License number (for preparation and distribution of perishable food items) in addition to the common Donor attributes.

Private Donors have no additional attributes.

1. Food Order [FO]

A Food Order shall be characterized by a unique identifier, date, and a state (outstanding or delivered).

Each Food Order is a composition of one and possibly many Donated Item Order objects aggregated in it.

Each Food Order shall be placed by (associated with) a unique Recipient.

4) Donated Food Item [DFI]

Donated Food Items shall be characterized by DFI-ID (Donated Food Item Identifier), name, description, category, amount, number of portions and expiration date.

Any Food Donated Item is offered by one and only one Donor.

5) Donated Item Order [DIO]

Each Donated Item Order shall be characterized by an order id and quantity.

Each Donated Item Order is associated with one Donated Item.

The Donated Item Order objects provide a specialized Create operation, which in addition to the standard Create (constructor) functionality also sends a message to the corresponding Donated Item object to reduce the number of available copies.

The Donated Item Order objects also has a Notify service, responsible for notifying the corresponding Donor about the order.

6) Moderators [M]

Moderators must pre-register with the system before they can perform any actions, including the generation of Daily Food Listings.

Moderators are identified by a Moderator ID (also used as login id), name, address, email address, and a contact telephone number.

7) Volunteer [V]

Volunteers are cleared and registered with the system by the Moderators. They have a name, address, email, home actress, and an estimated availability time.

8) Daily Food Listing [DFL]

The Daily Food Listing is characterized by an ID (DFL_ID) and a date. It is verified and published by the Moderators. The Daily Food Listings are stored for audit purposes.