Case study: You are required to develop an application to keep track of meeting minutes. Every time a formal meeting takes place, corresponding meeting minutes should be generated. Each meeting has a list of participants, which the system receives from the caller of the meeting. The caller also assigns the role of meeting secretary to one of the participants. The contents of the minutes are usually text, however, images and audio clips can also be attached to the minutes. The number of attachments is not limited. For each meeting, minutes can only be created by the assigned meeting secretary (for that meeting), who is also responsible for uploading the attachments. Minutes can be created incrementally. Once the secretary is satisfied with his/her draft, the minutes can be broadcast to the participants, who can then make comments on the minutes. Participants can make comments on the minutes as a whole. These are global comments. They can also select particular sections of the minutes and make comments on particular sections. The secretary can make changes to the minutes based on the comments. The secretary can also reply to each comment. Once the secretary decides that minutes are finalized, with all comments addressed, he/she can ask the system to start the approval process. The approval process requires at least three participants or 50% of the meeting participants, whichever is less, to approve the minutes. Once that is done, the minutes are considered to be finally approved and archived in that state. The system is going to be web-based. Whenever a user logs in, he/she should see a list of upcoming meetings, completed meetings,. The user should also see different lists for meetings he/she has called, and meetings for which he/she is the secretary. All user options should be accessible via menus. Participants can make comments on meeting minutes by clicking on the link of a completed meeting (if the minutes have been posted.) Secretaries can broadcast minutes by completing the minutes for a completed meeting and by choosing the broadcast option. Asking for approval is also a similar option. If the approval process is initialized, all participants should receive a notification asking them to review and approve. From Wikipedia: Minutes, also known as protocols or, informally, notes, are the instant written record of a meeting or hearing. They typically describe the events of the meeting and may include a list of attendees, a statement of the issues considered by the participants, and related responses or decisions for the issues. Q1. Draw the use case diagram for the system. Q2. Write an expanded use case for the following: Use case name: Broadcasting meeting minutes.

Case study: You are required to develop an application to keep track of meeting minutes. Every time a formal meeting takes place, corresponding meeting minutes should be generated. Each meeting has a list of participants, which the system receives from the caller of the meeting. The caller also assigns the role of meeting secretary to one of the participants. The contents of the minutes are usually text, however, images and audio clips can also be attached to the minutes. The number of attachments is not limited. For each meeting, minutes can only be created by the assigned meeting secretary (for that meeting), who is also responsible for uploading the attachments. Minutes can be created incrementally. Once the secretary is satisfied with his/her draft, the minutes can be broadcast to the participants, who can then make comments on the minutes. Participants can make comments on the minutes as a whole. These are global comments. They can also select particular sections of the minutes and make comments on particular sections. The secretary can make changes to the minutes based on the comments. The secretary can also reply to each comment. Once the secretary decides that minutes are finalized, with all comments addressed, he/she can ask the system to start the approval process. The approval process requires at least three participants or 50% of the meeting participants, whichever is less, to approve the minutes. Once that is done, the minutes are considered to be finally approved and archived in that state. The system is going to be web-based. Whenever a user logs in, he/she should see a list of upcoming meetings, completed meetings,. The user should also see different lists for meetings he/she has called, and meetings for which he/she is the secretary. All user options should be accessible via menus. Participants can make comments on meeting minutes by clicking on the link of a completed meeting (if the minutes have been posted.) Secretaries can broadcast minutes by completing the minutes for a completed meeting and by choosing the broadcast option. Asking for approval is also a similar option. If the approval process is initialized, all participants should receive a notification asking them to review and approve. From Wikipedia: Minutes, also known as protocols or, informally, notes, are the instant written record of a meeting or hearing. They typically describe the events of the meeting and may include a list of attendees, a statement of the issues considered by the participants, and related responses or decisions for the issues. Q1. Draw the use case diagram for the system. Q2. Write an expanded use case for the following: Use case name: Broadcasting meeting minutes.

Programming with Microsoft Visual Basic 2017

8th Edition

ISBN:9781337102124

Author:Diane Zak

Publisher:Diane Zak

Chapter8: Arrays

Section: Chapter Questions

Problem 3E

See similar textbooks