A Web Based Meeting Scheduler Information Technology Essay

A Web Based Meeting Scheduler Information Technology EssayThe web based merging inscriptionr (WMS) is a substance abuser friendly tool developed to assists humans in office environments to muniment meets efficiently. The algorithmic rule used in the distributed clashing registerr paves behavior for negotiation of various processes on behalf of their users and comes up with an agreement on a reciprocal meeting time that is acceptable to all the users and abides by all theconstraints set by the hosts and attendees. The motive of the algorithm is to obtain a solution based on the noesis it acquires during the process. In summary the Web-based Meeting Scheduler follows a decision oriented methodology that depends on knowledge based approach. The purposeof WMS is to support the organization of meetings and to determine for each meeting request, a meeting while and location so that most of the intended recessicipants shall effectively participate.The principal users of this sy stem argon the Meeting Initiator and Meeting Attendees/Participants. Each user is going to save their own login IDs and passwords. It is the responsibility of the meeting initiator to schedule the meeting based on the availability of the attendees along with the constraints expressed by the attendees/participants. The meeting scheduler system shall pack the ability to handler several meeting requests in parallel and resolveconflicts. The key functionalities of this system atomic number 18 Schedule or scheme meetings, re-planning of meetings to support changing user constraints, support conflict resolution, keep participants intercommunicate of the meeting schedules and any changes, and to jackpotcel meetings.Problem ContextDespite the advances in technology, scheduling a meeting is not as simple as it looks. thither is a lot of judgment involved. Anytime you bring together a group of people, there are many factors to consider. You have to consider pecking order. Some members of the group are more important, so others must change their schedules to accommodate. But with the right system, meeting scheduling can be quick, easy and super efficient. Therefore, a web-based system meeting scheduler system leave behind be developed to allow individuals or organizations to easily, efficiently, and precisely schedule meetings in accordance with practical limitations of virtual and real-world meetings. This bemuse does on how the software system leave alone try to achieve what it is intended to do, by describing requirements such as security, reliability, maintainability, usability and performance.RationaleNow that the problem has been identified, once implemented, the system could bring some significant tangible and intangible benefits. It is anticipated that the system could be the best solution to the existing problems that meeting planners or organizers encounter when running meetings. The following are the tangible and intangible benefits of the systemMe etings are vital for communication and pull offment. Properly run meetings save time, increase motivation, productivity, and solve problems. Plan, run and follow up meetings properly, and they will repay the cost many times over because there is still no substitute for physical face-to-face meetingsDescription of Problem Area belongings meetings is an increasingly expensive activity, hence the need to run meetings well. Badly run meetings waste time, money, resources and are worse than having no meetings at all.The following are common problems that occur when scheduling a meetingThe meeting is scheduled and after everyone had been invited you discover that some important participants cant attend.Another date has to be found. This can lead to a cycle of invitations and revisions.A meeting is confirmed but whence needs to be changed.A meeting location is specified and then later changed in a subsequent meeting notice. Some of the attendees follow the original meeting notice and end up in a tweet room.Repeated meeting notices and revisions are sent out, so everyone is confused about the meeting.You use an internet based meeting scheduling system, but outside participants dont have the same software.A meeting is scheduled and confirmed, but the location is already booked.No one sends a meeting reminder, and several attendees forget about the meeting. race are invited to a meeting but the meeting organizer did not say what it is about, so they show up unpreparedNature of ChallengeThe hardest sensation part of building a software system is deciding precisely what to build. No other part of the inventionual execute is as difficult as establishing the detail technical requirements, including the entire interface to people, to machines, and to other software systems. No part of the work so cripples the resulting system if done wrong. No other part is more difficult to rectify later.Brooks, 1987We consider the problem of determining suitable meeting times and loc ations for a group of participants wishing to schedule a meeting subject to already scheduled meetings possibly held at a number of different locations. Each participant must be able to reach the upstart meeting location, attend for the entire duration, and reach the next meeting on time. Major problem will be in deriving efficient algorithms for solution general meeting scheduling problems, to find approximate solutions, where appropriate implement the solutions and to integrate them into applications that allow users who are connected over a network to schedule meetings. Currently meeting scheduling systems take into consideration only time and not location or geometry.C.Brief description of project objectives.(i.e. scope of proposal and deliverables)ScopeThe scope of the project shall include scheduling meetings in an efficient way, gathering the feedback from attendees, cancelling the meeting, changing the schedule and/or location, scheduling concurrent meetings in by the by e manner, conducting virtual meeting, confirming the location and time of the meeting and last but not the least minimize users effort in coordinating and scheduling meetings. lens nucleus ModulesThis is the main functionality of my project. It has to do the followingAutomate the meeting schedule process to enable efficient use of the time and efforts of meeting organizer.Select a date and time according to the availability of the participants.Allocate the location that is convenient to all the participants.Send reminders to the participants about the meeting and any schedule changes.Re-organize and modify the meeting schedule if required.Enhanced FeaturesThis are the additional features I plan to include in my projectAdding members of the meetingAdministrator has privilege to edit users pro single file.Search for members of the meeting and understand who is free and who is not, and who is coming for the meetingGeneration of appropriate reports to show meeting attendees and the mee ting agendasAttendees photos for verification incase of same breeding.Participants option for denying the invitation.User need to register. extra FeaturesBased on my explore and if I have the time and ability, these are the features I am going to attempt to implementMake the system work on diverse platforms (Windows, Blackberry, iPhone and other Smartphone compatibility).Participants choice of getting reminder in pop-up window or mail.Facility to book conference bridge (conference bridge is a phone) and editing reserved bridge.Assumptions and DependenciesThe following will be major assumptions of this projectWill ensure that I am available as needed to make out project tasks and objectives.Will abide by the guidelines identified within this plan.Project plan might change on new entropy revealed or issues encountered. approachability of participants for meetings and training.ConstraintsThe project has the below three constraintsTime time frame within which the project should be c ompleted.Cost cost of developing the system within the estimated budget. note level of quality to be met as per the requirements of the users.D.Brief description of the resources needed by the proposal.(i.e. hardware, software, access to information / expertise, user involvement etc.)Hardware requirementsA bar PC with minimum 40gig hard disk and 256MB RAM. A Smartphone. package requirementsThe system shall be developed utilise n-tier architecture consisting of the presentation (web layer), business layer and data Access layer.Integrated Development Environment Netbeans IDEDevelopment using Java 1.6, J2ee, Ajax, JavaScriptDatabase Management SQL server 2005The web-based interface for the WMS shall run in the below internet browsersprofit Explorer 64.x and aboveFirefoxAccess to information or ExpertiseMostly books are used as a source of information for this project. However websites and research paper also play a major role as a source of equalence.User InvolvementKnowledge and experience of people who have used the existing Web-based Meeting Schedulers is respected, valued and drawn upon to influence and shape the work of the proposed system. They would help to understand the requirements hence building a better system. These information can be gathered by using some research methods such as interviews, questionnaires or even case studies.E.Academic research macrocosm carried out and other information, techniques being learnt.(i.e. what are the names of books you are going to read / data sets you are going to use)The following are some of the books I am going to read in conjuction with the information gathered online as I will be doing this projectDawson, C.W. (2009) Projects in Computing and Information Systems A Student GuideTudor, D.J. and Tudor I.J. (1999)System Analysis and Design A Comparison of Structured Methods, New Edition. Palgrave Macmillan SoftwareHughes, B. Cotterell, M. (3rd Ed)(2009) Software Project ManagementSommerville, I. (6th Ed) (2000) Software Engineering by Ian SommervillePhilips, J. Project (3rd Ed) Management Professional Study GuideHall, E. Johnson, J. (2002)Integrated Project Management Prentice HallF.Brief description of the development plan for the proposed project.(i.e. which software methodology and why, the major areas of functions to be developed and the order in which developed)After reading and making researches, I strong-willed to do this project using Systems Development Life Cycle (SDLC). It is a conceptual model used in project management that unlike other methodologies describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application. Although SDLC has different forms and models, it follows authentic steps. These steps could have the same meaning in one methodology but they are treated in a different manner or could lead to something different. It is chosen because of its ability to cater for th e project as a whole and part of it that involves an application that is going to be developed on the web. These following steps are for the projectPlanning- Everything starts with a concept or with a question such as what do you want? being asked to certain people so as to know what they want and finalize to create an answer.Design- Once planning is done one can now design or create a rough plan regarding the software. Will square off on the initial specifics of the software to be created, decide what platform or programming language to use.Implementation- When the design and all the things that I need have been position out, it is time to work on the plan and present it for approval.Testing- Two types of test are going to be performed, one which will be the actual exam by users. Once the stage is completed the WMS will be tested by professionals in the field.Acceptance- When the software is released to be used by a certain company, acceptance means the software is implemented .Maintenance- When the software is implemented, it does not mean that the software is good as it is. Maintenance is included since there is absolutely no way that the software will be working perfectly.Disposal- When a software is outmoded, it is not just all deletion of files, affected files should be looked at and determine which file to protect and dispose.And the following are web development stages Analysis, Initial design, Design approval, Web development, Prototype, Launching, and Maintenance.G.Brief description of the evaluation and test plan for the proposed project.(i.e. what is the success criteria and how will be evaluated implementation will be tested, indicate the estimated size of the demonstration/test database)TestingTesting refers to the process of exercising a product to rank differences between expected and actual behavior. It is the means by which the presence, quality or genuineness of anything is determined a means of trial.The project will be lucky it if m anages to perform all the key functionalities. It will be tested by me and as I will be developing the system with both black-box and white-box testing methodologies while my supervisor will use White-box testing which provides a degree of sophistication that is not available with black-box testing as the tester is able to refer to and interact with the objects that comprise an application rather than only having access to the user interface to check if all the functionalities, deliverables and objectives are met.EvaluationEvaluation is a taxonomical determination of merit, worth and significance of something or someone using criteria against a set of standards. Without an evaluation process a product reaching consumers would be untried. It would meditate the intentions of its designer but there would be no study of the relationship between design and use. The two main types of evaluation, Formative and Summative evaluation are going to be used to evaluate Web based meeting schedu ler that is going to be developed in this project.The Web-based Meeting Scheduler will have rough 20 people in its database. They will be used for testing some of the functionalities of the system. For example if one person is invited to a meeting that clashes with another meeting that he or she has already been invited to, and the person showed that they will be attending it, an error message should be displayed to show that the person will not manage to attend that one. Or if meetings that should have the same attendees clash, an error message should be displayed also.