Question 2. (50 POINTS) : A simple calendar management system is described below

Question

Question 2. (50 POINTS): A simple calendar management system is described below. Limit the length of the SRS to no more than two pages. This calendar management software allows the user to schedule personal activities such as meetings and tasks to be performed. An activity can take place on a future date during a certain period of time. An activity can take place for several consecutive days. Each activity has a brief mnemonic description. An activity can be a recursive activity, which takes place repeatedly every hour, every day, every week, or every month. A user can schedule an activity using a month-by-month calendar to select the date or dates, and then zooms in to select the begin time and end time on a date. The calendar system shall notify the user by email, text message, or phone call the day before and on the activity day. The user can review past activities and modify the schedule including updating and deleting activities.

2.A.) (10 POINTS) List the functional requirements as a Software Requirements Specification (SRS) for the calendar management system.

2.B.) (10 POINTS) Identify the type of system and briefly justify your answer.

2.C.) (10 POINTS) Produce an architectural design for the system.

2.D.) (10 POINTS) Specify the functionality and interface for each of the subsystems and components in the architectural design.

2.E.) (10 POINTS) Discuss which software design principles are applied, how they are applied, and the benefits of each of the principles.

Explanation / Answer

2A)

Functional Requirements for Calendar Management System:

Scheduling a meeting/other personal activities following process needs to be followed:

Initiator can be the representative or any one of the participants. A request will be sent to all the required attendees with a subject line which will highlight the agenda of the activity to be held.

Initiator will fill basic details including convenient timings, type of activity, goal of activity and list out all of the possible participants before issuing the activity.

Initiator can ask for a confirmation from rest of the participants. There needs to be a 2 way communication between any other participant and initiator. If activity involves some other details from all/some of the participants then there needs to be system to raise the same along with the activity initiation.

After confirmation from all of the participants/or some specific participants, initiator can ask the system to schedule the activity with all of the inputs from the initiator as well as participants.

All the logistics asked by the initiator shall be available or the initiator/any other concerned team should be informed about the same.

If it is a not a virtual meeting then asked meeting room should be checked for availability in the required slot.

In case of any mismatch or lack of resources, Initiator should be asked for acceptance.

There should be separate handling of conflicts. One for lack of availability of room or logistics in the required slot and the other for overall unavailability of any required resource.

System should be able to ask initiator to cancel the meeting in case of any conflict with a proper description of the problem.

Initiator should be able to reschedule the activity and ask for re-acceptance from all/some of the participants.

2B)

It needs to be web based system compatible on both desktop as well as mobile browsers becuase based on the requirement or scale of activity anyone should be able to initiate/accept/reject the activity requests. The service which deals with database needs to be on an active server and a backup should be available in case of system crash or any other technical challenge. The system for initiation and conflict management should be as per client/s policies.

Related Questions

Navigate

• Browse (All)
• Browse Q
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.