Meeting Scheduler Requirements Engineering

When arranging a meeting types of information may include the reason for the meeting, the time and length, the date and location, what resources are required and a list of required attendees and their contact details.

A meeting agenda ensures that the meeting will be a productive use of everyone's time. It can focus the attendee’s efforts and provide a structure to accomplish the meeting purpose. It defines outcomes, and important information, attendee roles and responsibilities and a meeting timeline. It allows attendee’s to prepare for the meeting as it is made available a week before. It also works as a checklist of those attending, goals and topics for discussion to make sure that all the necessary information is covered and keeps team members focused on the specific goals and stay on track with the subject matter.

Meetings management involves a variety of different activities. Before a meeting has begun the office administrator should make sure that he/she has booked a room for the meeting and that it is in accessible location so that it allows access for anyone who is disabled and it complies with all current government legislation. The secretary should make sure that all the equipment is already set up in the room and check it is in good working order. For example: a computer and a projector if there are going to be presentations of any kind. There should also be sufficient refreshment available. An agenda which contain: Apologies, minutes of the previous meeting, matters arising, any other business and the date of the next meeting. This is sent to all attendees of the meetings in advance so they know what is being discussed.*

Minutes of meeting: Title; date; place; attendees; apologies; matters arising from previous meetings; record of business; action points and details of next meeting.

Step-3: Assign the roles of facilitator, scribe, and timekeeper: A meeting is a time bound activity. The meeting

A set of preliminary usage scenarios that describe the use of the system under different operating conditions.

It should include the date, time, location and purpose. It should also contain any specific instructions or actions they need to bring or that need to be undertaken prior to meeting. It might also ask participants if they have agenda items they wish to raise.

Types of events and main features (formal meetings including board meetings and annual general meetings, semiinformal including team meetings or sales meetings, exhibitions and trade fairs, receptions, conferences); agreeing role and responsibilities to provide support activities required (clarifying purpose, type and size of event, identifying target audience and confirming numbers, planning tasks and resources); confirming venue with others

If there is a problem with meeting times or, if a member is going to be late, we expect to have notice, preferably well in advance, but if that is not possible, as soon as they are aware that they will not be there or will be late. Attendance is expected from all members to be present and prepared for all meetings and presentations.

Requirement Traceability: Provide inputs to User stories, proposing the enhancements, review user stories written by business analysts and discuss with Business users to ensure all requirements are captured and provide

The non-functional requirements are the attributes of the system; these include: reliability, performance, cost, system quality attributes, and the challenges encountered during installation.

This would list the venue, date and time, speaker, contact details. An agenda of the meeting would be the best way to send out these details as it lists all that information and lets attendees knows how the meeting will be run.

In your role organising schedules you will have to work according to the organisation’s policies and procedures.  If you look at the GSE Intranet, you will see the Administration policies and procedures for making appointments and processing schedules.    An organisation’s requirements will depend on the availability of

Each participant has an agenda, and the need to complete daily tasks ensures meetings are short.

Out of these factors, Supply Management, Project Tracking and Receiving are the core functionalities which are anyway required. Design and Foundation, Documentation and Request Definition are the supporting requirements which add value and enhance the quality of service or