Assignment No. 1
Graded
Semester Fall 2019
Software Architecture and Design– CS603
Total Marks: 15
Due Date: 11th Nov. 2019
Objective:
The assignment has been designed to enhance your knowledge about discipline of design and design processes.
Instructions:
Please read the following instructions carefully before solving & submitting assignment:
- The assignment will not be accepted after due date.
- Zero marks will be awarded to the assignment that does not open or the file is corrupt.
- The assignment file must be an MS word (.doc or .docx) file format; Assignment will not be accepted in any other format.
- Zero marks will be awarded to the assignment if copied (from other student or copied from handouts or internet).
For any query about the assignment, contact only at [email protected]
Do not post queries related to assignment on MDB.
GOOD LUCK
Scenario
Customer wants to reserve room(s) in hotel online. S/he can check whether room(s) is/are available for reservation or not. The system will provide information about rooms. The customer will request for room(s). After getting customer feedback regarding rooms, the system will check whether it is new customer or existing customer. For new customer the system asks to enter his/her information. After registration the room(s) is/are assigned to customer and they will receive confirmation invoice.
Question No. 1 [Marks = 10]
Draw an ACTIVITY diagram for the above scenario.
Question No. 1 [Marks = 5]
The following UML activity diagram shows typical document routing system in offices, the clerk generates a draft document, after which it is forwarded to manager for review. The manager sends original document to “Accounts” section while the copy of the document with comments is moved towards “Records” section. Both (Accounts & Records) section forward the consolidated document to Head office for final approval, after which the document is approved and financial bill is generated.
The diagram shows execution of two activities i.e. “Accounts” and “Records” in parallel. Redraw the above diagram by showing this parallelism using Joins/forks notation.
