features for their customers to browse and search products and to place orders for these products online.  Figures below are interaction diagrams for use case ‘search product’ (Figure 1) and use case ‘place an order’ (Figure 2).   b) Suggest an architecture for this system. Provide justification for your proposal. Include diagrams to support your answer.   c) Explain at least TWO (2) quality attributes that the proposed architecture will satisfy.

5, Analysis and Design (20 points) The WSP is a collection of overlapping applications for warehouse management, its Entity/Relationship diagram representing the entities involved in is shown in the figure 2. 1 CUSTOMER 1 stored at n n owns ITEM PLACE Figure 2 All the functions (element processes) of the WSP system are listed in figure 3. - Add customer Change customer data Delete customer - Delete place - Print customer item list - Print bill - Print stored items list - Query customers Query customer's items - Query places Query stored items Receive payment Deposit item Retrieve item Add place Change place data Figure 3 (1), please draw the domain class diagram and (2), please draw the use case diagram for the system. The domain class diagram and Use case diagrams can be drawn with modeling tools, or they can be drawn by hand, photographed, and inserted here. (for each diagram, 5 points for the correct format, 5 points for correct content) Answer question 5 here

Draw an entity diagram diagram for a car rental business  identifying primary and foreign keys with the below attributes and cardinality Customer - Customer_ID (pk), Cust_Title, FirstName, LastName, DoB,  Telephone, Address1, Address2, City, State, ZipCode Employee - Emp_ID (pk), Firstname, lastname, Telephone, Address, City, State, ZipCode, hiredate, SSN Car - Car_ID (pk), Model, Make, Year, Color, capacity, Customer_ID (fk), Payment_ID (fk) Payment - Payment_ID (pk), PaymentType, PaymentMethod, payment amount, Signature, PaymentDate, Receipt_ID (fk) Receipt - Receipt_ID (pk), Bill_To, Receipt_Total, Total_Amt_Due, Amt_Paid, CreateDate, Payment_ID (fk)     Relationship and Cardinality Description Customer/Car: 1:M - one customer can have multiple cars on file, a car must belong to a customer Employee/Customer:1:M - One employee can have many customers to attend to but just one customer can be attended to at a time. Car/Payment: 1:M - one car can have multiple payment options on file,…

4+1 view alignment with UML diagrams. How can the different views of the 4+1 view model, be represented or modeled in correspondence to different UML diagrams.