Difference between revisions of "IS480 Team wiki: 2011T2 IMATEAM2"
Kikoh.2009 (talk | contribs) |
Kikoh.2009 (talk | contribs) |
||
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | [[Image: | + | [[Image:ImateamLogo.jpg|400px|right]] |
− | + | <font face="century gothic" size="2"> | |
− | <div style="text-align: | + | |
− | < | + | |
+ | =<div class="NavHead" style="{{Round corners}}; background: #000000; text-align: left; padding: 2px; font-size: 160%; border:solid 4px black;"><font color="#f4ede3" size="+1"><b>The Team</b></font></div>= | ||
+ | |||
+ | [[Image:imateamRoles.jpg|1000px|center]] | ||
+ | |||
+ | =<div class="NavHead" style="{{Round corners}}; background: #000000; text-align: left; padding: 2px; font-size: 160%; border:solid 4px black;"><font color="#f4ede3" size="+1"><b>Stakeholders</b></font></div>= | ||
+ | |||
+ | |||
+ | |||
+ | [[Image:imateamStakeholders.jpg|center]] | ||
+ | |||
+ | =<div class="NavHead" style="{{Round corners}}; background: #000000; text-align: left; padding: 2px; font-size: 160%; border:solid 4px black;"><font color="#f4ede3" size="+1"><b>Project Overview</b></font></div>= | ||
+ | |||
+ | ===<div style="color: #ffffff; font-size:0%">Project Description</div>=== | ||
+ | |||
+ | |||
+ | |||
+ | {| border="0" cellspacing="0" cellpadding="0" width="100%" | ||
+ | | style="background-color:#000000;" width="0" | | ||
+ | {| style="width="30%"; font-size:95%; text-align: justify;" padding:-2px; background:ffffff" cellpadding="0" cellspacing="0" | ||
+ | | rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" | <div style="margin-top: -20px; padding-left:3px"></div><div style="padding-left:10px; margin-top:20px; font-size:130%"><font color="#000000">Project Description</font></div> | ||
+ | |} | ||
+ | | style="border-bottom:2px solid #7e786f; background:#ffffff;" width="8" | | ||
+ | | style="border-bottom:2px solid #7e786f; background:#ffffff;" width="100%"| | ||
+ | |} | ||
+ | {| style="width:100%; margin-bottom:.5em; font-size:95%; text-align: justify;" padding:-2px; background:FFFFFF" cellpadding="0" cellspacing="0" | ||
+ | | rowspan="1" width="100%" colspan="2" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; border-top:0; padding:0; margin:0" | | ||
+ | <div style="padding:10px; text-align: justify;"> | ||
+ | <font color="#000000"> | ||
+ | Our [[IS480_Team_wiki:_2011T2 IMATEAM_Wiki_Copy | team]] will be building a web and mobile social platform that enables attendees of conferences organized by IMAPAC to interact with each other before, during and after the conference. This social platform will allow them to post and receive conference updates, engage in discussions, network with industry partners and arrange meetings. The platform will be built using a content management system written in PHP such as Drupal. Data analysis will be applied to the information provided by the sponsor to build a user-centered system that provides recommendations to the conference attendees based on their individual profiles, such as suggestions of industry partners they might want to work with. | ||
+ | </font> | ||
+ | |- | ||
+ | | colspan="2" class="radius_bottom" style="background:#7e786f; border:2px solid #7e786f" |<div style="font-size:0">[[image:pix.gif|15px]]</div> | ||
+ | |||
+ | |} | ||
+ | |||
+ | ===<div style="color: #ffffff; font-size:0%">Motivation</div>=== | ||
+ | |||
+ | {| border="0" cellspacing="0" cellpadding="0" width="100%" | ||
+ | | style="background-color:#000000;" width="0" | | ||
+ | {| style="width="30%"; font-size:95%; text-align: justify;" padding:-2px; background:ffffff" cellpadding="0" cellspacing="0" | ||
+ | | rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" | <div style="margin-top: -20px; padding-left:3px"></div><div style="padding-left:10px; margin-top:20px; font-size:130%"><font color="#000000">Motivation</font></div> | ||
+ | |} | ||
+ | | style="border-bottom:2px solid #7e786f; background:#ffffff;" width="8" | | ||
+ | | style="border-bottom:2px solid #7e786f; background:#ffffff;" width="100%"| | ||
+ | |} | ||
+ | {| style="width:100%; margin-bottom:.5em; font-size:95%; text-align: justify;" padding:-2px; background:FFFFFF" cellpadding="0" cellspacing="0" | ||
+ | | rowspan="1" width="100%" colspan="2" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; border-top:0; padding:0; margin:0" | | ||
+ | <div style="padding:10px; text-align: justify;"> | ||
+ | <font color="#000000"> | ||
+ | Attendees of IMAPAC business conferences vary widely, from governments to NGOs, businesses and academics. They currently do not have a platform that allows their attendees to communicate efficiently with each other. Extra time spent on handling logistics issues such as scheduling of meetings, searching for contact information, arranging meeting locations etc. could be better spent on trying to create an even bigger impact for the social causes they are advocating. We also believe that if organizations have an improved communication channel, especially after a conference, they will be able to build a closer link to one another that further nurtures the social enterprise spirit within. | ||
+ | |||
+ | Hence, our proposed web and mobile platform can potentially eradicate the above problems by being user friendly and interactive. We will achieve this by applying heuristics used in usability studies to the user interface design. The platform will be interactive because we will consider all aspects of each group of users’ needs and enable them to engage one another according to their business relationship. | ||
+ | |||
+ | </font> | ||
+ | |- | ||
+ | | colspan="2" class="radius_bottom" style="background:#7e786f; border:2px solid #7e786f" |<div style="font-size:0">[[image:pix.gif|15px]]</div> | ||
+ | |||
+ | |} | ||
+ | |||
+ | ===<div style="color: #ffffff; font-size:0%">Project Deliverables</div>=== | ||
+ | |||
+ | {| border="0" cellspacing="0" cellpadding="0" width="100%" | ||
+ | | style="background-color:#000000;" width="0" | | ||
+ | {| style="width="30%"; font-size:95%; text-align: justify;" padding:-2px; background:ffffff" cellpadding="0" cellspacing="0" | ||
+ | | rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" | <div style="margin-top: -20px; padding-left:3px"></div><div style="padding-left:10px; margin-top:20px; font-size:130%"><font color="#000000">Project Deliverables</font></div> | ||
+ | |} | ||
+ | | style="border-bottom:2px solid #7e786f; background:#ffffff;" width="8" | | ||
+ | | style="border-bottom:2px solid #7e786f; background:#ffffff;" width="100%"| | ||
+ | |} | ||
+ | {| style="width:100%; margin-bottom:.5em; font-size:95%; text-align: justify;" padding:-2px; background:FFFFFF" cellpadding="0" cellspacing="0" | ||
+ | | rowspan="1" width="100%" colspan="2" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; border-top:0; padding:0; margin:0" | | ||
+ | <div style="padding:10px; text-align: justify;"> | ||
+ | <font color="#000000"> | ||
+ | <b>Overview:</b><br/> | ||
+ | At the end of the project, our team aims to deliver a robust and dynamic integrated social platform that will improve the overall experience of conference attendees. The platform’s focus will be centered on IMAPAC’s aim to promote good social causes and help businesses do good. Our project will achieve this by meeting the user needs that arise from attending a conference and all the relevant interlinked events such as discussions and meetings. The platform will be deployed on a virtual dedicated server. | ||
+ | <br/> | ||
+ | <h3>User Oriented</h3> | ||
+ | <b>Web platform:</b><br/> | ||
+ | *User profile module - Profile, information, interests, conference history of users. Allows adding of 'friends' | ||
+ | *Recommendations module - Recommends fellow attendees and conferences to users based on interest keywords | ||
+ | *Conference/event module - Information about the conferences: Introduction, time, date, venue, list of speakers, list of attendees | ||
+ | *Real time module - Voting, post/respond to questions and notes taking | ||
+ | *Discussion forums module - A forum for users to discuss issues and interact both pre and post conference | ||
+ | *Sponsored children module - Includes information of the children to be sponsored; allows users to be updated of their progress | ||
+ | *Private messaging module - Allows users to send private messages to each other | ||
+ | *Evaluation module - Allows users to rate and evaluate conferences and speakers | ||
+ | *News and announcements module - Allows users to read the latest news and updates about conferences, social causes and IMAPAC | ||
+ | <b>Mobile platform:</b> | ||
+ | *User profile module - Profile, information, interests of users | ||
+ | *Conference/event module - Information about the conferences: Introduction, time, date, venue, list of speakers | ||
+ | *Private messaging module - Allows users to send private messages to each other | ||
+ | *News and announcements module - Allows users to read the latest news and updates about conferences, social causes and IMAPAC | ||
+ | <h3>Admin Oriented</h3> | ||
+ | <b>Web platform:</b><br/> | ||
+ | *User registration | ||
+ | *User profile management | ||
+ | *Event creation/management | ||
+ | *Notes creation/management | ||
+ | *Polls creation/management | ||
+ | *Evaluation forms creation/management | ||
+ | </font> | ||
+ | |- | ||
+ | | colspan="2" class="radius_bottom" style="background:#7e786f; border:2px solid #7e786f" |<div style="font-size:0">[[image:pix.gif|15px]]</div> | ||
+ | |||
+ | |} | ||
+ | |||
+ | ===<div style="color: #ffffff; font-size:0%">Project Usability</div>=== | ||
+ | |||
+ | {| border="0" cellspacing="0" cellpadding="0" width="100%" | ||
+ | | style="background-color:#000000;" width="0" | | ||
+ | {| style="width="30%"; font-size:95%; text-align: justify;" padding:-2px; background:ffffff" cellpadding="0" cellspacing="0" | ||
+ | | rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" | <div style="margin-top: -20px; padding-left:3px"></div><div style="padding-left:10px; margin-top:20px; font-size:130%"><font color="#000000">Usability Studies</font></div> | ||
+ | |} | ||
+ | | style="border-bottom:2px solid #7e786f; background:#ffffff;" width="8" | | ||
+ | | style="border-bottom:2px solid #7e786f; background:#ffffff;" width="100%"| | ||
+ | |} | ||
+ | {| style="width:100%; margin-bottom:.5em; font-size:95%; text-align: justify;" padding:-2px; background:FFFFFF" cellpadding="0" cellspacing="0" | ||
+ | | rowspan="1" width="100%" colspan="2" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; border-top:0; padding:0; margin:0" | | ||
+ | <div style="padding:10px; text-align: justify;"> | ||
+ | <font color="#000000"> | ||
+ | Our team aims to develop a user friendly and intuitive platform for our users. Hence, usability studies play a big part of our development process as they allow us to assess user requirements and find out what works best for them. Usability studies will be conducted in two forms: heuristic evaluations and UAT. | ||
+ | |||
+ | Heuristic evaluations will be based on Nielsen's ten usability heuristics, which are ten general principles for user interface design.<br>Violations of these heuristics will be assessed on a severity scale of 1 to 4 according to these factors: | ||
+ | *Frequency | ||
+ | *Impact | ||
+ | *Persistence | ||
+ | |||
+ | 1 = Cosmetic problem only: need not be fixed unless extra time is available on project<br> | ||
+ | 2 = Minor usability problem: fixing this should be given low priority<br> | ||
+ | 3 = Major usability problem: important to fix, so should be given high priority<br> | ||
+ | 4 = Usability catastrophe: imperative to fix this before product can be released | ||
+ | </font> | ||
+ | |- | ||
+ | | colspan="2" class="radius_bottom" style="background:#7e786f; border:2px solid #7e786f" |<div style="font-size:0">[[image:pix.gif|15px]]</div> | ||
+ | |||
+ | |} | ||
+ | |||
+ | ===Project Scope=== | ||
− | + | We will utilize an open-source content management system written in PHP, Drupal, to develop our web application on. We chose Drupal because it is highly customizable, scalable and flexible in terms of UI design, functionalities and access control. Our project can be divided into 2 core components: the web platform and the mobile application. | |
+ | {| class="wikitable" cellpadding="15" | ||
+ | |- | ||
+ | | style="background: #000000; color: #FFFFFF; padding: 10px 0 10px 30px; font-weight: bold; font-size: 14px; text-indent: 8px; width: 950px;" colspan="5" valign="top" |Project Functionalities - User (Attendee, Speaker, Sponsor, Organizer) | ||
+ | |- | ||
+ | | style="background: #8f8c87; color: #000000; font-weight: bold; text-indent: 2px; width: 15%;" valign="top" | | ||
+ | | style="background: #8f8c87; text-align: Left; padding-left: 20px; width: 25%;" | <b>Functionality</b> | ||
+ | | style="background: #8f8c87; text-align: Left; padding-left: 20px; width: 60%;" | <b>Description</b> | ||
+ | |- | ||
+ | | style="background: #585550; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top" rowspan="12" | Web Platform | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Profile of attendees</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Users can sign up for their accounts and set up information such as bio, interests and conference-related history details. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Real time feedback</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Allow attendees to provide real time feedback to speakers and fellow attendees during conferences in the form of live polls and comments. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Friend system</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Anyone with an account on the social platform can add another to his network via the Friend system. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Conference/event details</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Provide attendees and speakers with conference information such as detailed location, time, date, attending list, topics covered etc. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Networking opportunities</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Enable users to connect with potential business partners by matching them to other users with similar interest and keywords. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Make a Child smile</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Allow conference attendees to read some stories about the sponsored children helped by the efforts of IMAPAC and B1G1 thus far. This page will also have a link so that site members can choose to make a donation if they wish to. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Private messaging system</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Enable users to send private messages to each other. There will be a setting to make it public or friends-only. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Post-conference rating and evaluation</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Enable conference attendees to complete their post-conference evaluation for the conference and its speakers. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Personalized recommendation system</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Users will be recommended similar conferences based on past history. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Live note-taking function</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Allow attendees to take notes live during a conference which they can choose to save, send to email or share (public/friends only). | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Search</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Search for other users according to name, interests and keywords. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Discussion Forum</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Forums for pre and post conference discussion. | ||
+ | |- | ||
+ | |||
+ | | style="background: #585550; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top" rowspan="5" | Mobile Platform | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Profile of attendees</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Simplified (only View) profiles of attendees. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Conference/event details</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | View conference details such as those detailed above. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Geo-location services</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Locate conference location on smartphone maps using GPS. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Announcement and news</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | View and read announcements and news to be kept updated of event happenings. | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Private messaging system</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Send messages on-the-go in case they need to contact a fellow attendee. | ||
+ | |- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
+ | {| class="wikitable" cellpadding="15" | ||
+ | |- | ||
+ | | style="background: #000000; color: #FFFFFF; padding: 10px 0 10px 30px; font-weight: bold; font-size: 14px; text-indent: 8px; width: 950px;" colspan="5" valign="top" |Project Functionalities - Administrator | ||
+ | |- | ||
+ | | style="background: #8f8c87; color: #000000; font-weight: bold; text-indent: 2px; width: 15%;" valign="top" | | ||
+ | | style="background: #8f8c87; text-align: Left; padding-left: 20px; width: 25%;" | <b>Functionality</b> | ||
+ | | style="background: #8f8c87; text-align: Left; padding-left: 20px; width: 60%;" | <b>Description</b> | ||
+ | |- | ||
+ | | style="background: #585550; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top" rowspan="13" | Web Platform | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>User registration</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Import .CSV files of all newly registered users into Drupal by Admin to create the accounts | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Profile of attendees</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Admin can create, edit and delete profile information of all users (attendees, speaker, sponsors) | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Conference/event details</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Create, edit and delete conference data with uploading of files as conference resources | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Live note-taking function</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Manage notes taken by users at conferences | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Real time feedback</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Able to create polls and vote on polls during conferences | ||
+ | |- | ||
+ | | style="background: #b8b6b2; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | <b>Post-conference rating and evaluation</b> | ||
+ | | style="background: #e4e1de; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Create rating/evaluation forms for attendees, view and collate responses | ||
+ | |- | ||
+ | |||
+ | |} | ||
+ | |||
+ | ===<div style="color: #ffffff; font-size:0%">Project X Factor</div>=== | ||
+ | |||
+ | {| border="0" cellspacing="0" cellpadding="0" width="100%" | ||
+ | | style="background-color:#000000;" width="0" | | ||
+ | {| style="width="30%"; font-size:95%; text-align: justify;" padding:-2px; background:ffffff" cellpadding="0" cellspacing="0" | ||
+ | | rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" | <div style="margin-top: -20px; padding-left:3px"></div><div style="padding-left:10px; margin-top:20px; font-size:130%"><font color="#000000">The X Factor</font></div> | ||
+ | |} | ||
+ | | style="border-bottom:2px solid #7e786f; background:#ffffff;" width="8" | | ||
+ | | style="border-bottom:2px solid #7e786f; background:#ffffff;" width="100%"| | ||
+ | |} | ||
+ | {| style="width:100%; margin-bottom:.5em; font-size:95%; text-align: justify;" padding:-2px; background:FFFFFF" cellpadding="0" cellspacing="0" | ||
+ | | rowspan="1" width="100%" colspan="2" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; border-top:0; padding:0; margin:0" | | ||
+ | <div style="padding:10px; text-align: justify;"> | ||
+ | <font color="#000000"> | ||
+ | The selling points of our project are features that are different or not readily available in other similar social platforms out on the market such as LinkedIn and Facebook. In addition, our social platform is specially customized to meet the needs of conference attendees by catering to every aspect of their interactions. | ||
+ | |||
+ | Unique features of IMAPAC Connect include: | ||
+ | *Real Time Feedback - Allows attendees to vote in polls or raise questions during the conference. This improves the audience interaction aspect of the conference and makes it easier for speakers to receive feedback. | ||
+ | *Real Time Note Taking - Allows conference attendees to take notes on the web using their laptops. Handwritten notes can be slow, untidy and easy to misplace. Typed notes on the web can be saved can shared with users who are in their social circle. | ||
+ | *Business Card Exchange - Allows conference attendees and speakers to exchange virtual 'business cards' over the platform in order to build a wider network and keep in touch with contacts met at a past conference. | ||
+ | *Provides both conference attendees and speakers the ability to interact and keep in contact beyond the actual conference itself, which might have been harder before as the conferences are international and attempting to exchange email addresses can be a hassle. | ||
+ | *Our web platform will be developed using Drupal to create a interactive social experience for users with customized functions for the target audience. All features will be closely integrated to provide the most user-friendly and convenient experience for the user as possible. | ||
+ | </font> | ||
+ | [[Image:Clickdl-brown.png]] [[Media:socialcomparison.docx|<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">Click to see how Connet is different from other social platforms</span>]] | ||
+ | |- | ||
+ | | colspan="2" class="radius_bottom" style="background:#7e786f; border:2px solid #7e786f" |<div style="font-size:0">[[image:pix.gif|15px]]</div> | ||
+ | |||
+ | |} | ||
+ | |||
+ | ===<div style="color: #ffffff; font-size:0%">Development Environment</div>=== | ||
+ | |||
+ | {| border="0" cellspacing="0" cellpadding="0" width="100%" | ||
+ | | style="background-color:#000000;" width="0" | | ||
+ | {| style="width="30%"; font-size:95%; text-align: justify;" padding:-2px; background:ffffff" cellpadding="0" cellspacing="0" | ||
+ | | rowspan="1" width="30%" colspan="2" height="37px" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; padding:0; padding-right:1em; margin:0; -moz-border-radius-topright:1em" | <div style="margin-top: -20px; padding-left:3px"></div><div style="padding-left:10px; margin-top:20px; font-size:130%"><font color="#000000">Development Environment</font></div> | ||
+ | |} | ||
+ | | style="border-bottom:2px solid #7e786f; background:#ffffff;" width="8" | | ||
+ | | style="border-bottom:2px solid #7e786f; background:#ffffff;" width="100%"| | ||
+ | |} | ||
+ | {| style="width:100%; margin-bottom:.5em; font-size:95%; text-align: justify;" padding:-2px; background:FFFFFF" cellpadding="0" cellspacing="0" | ||
+ | | rowspan="1" width="100%" colspan="2" valign="top" style="background:#dfd8ce; border:2px solid #7e786f; border-bottom:0; border-top:0; padding:0; margin:0" | | ||
+ | <div style="padding:10px; text-align: justify;"> | ||
+ | <font color="#000000"> | ||
+ | <b>Server</b><br> | ||
+ | Our web platform will be developed in Drupal and deployed on a virtual dedicated server for our development phase. | ||
+ | |||
+ | The specification of our production server is: | ||
+ | *Operating System: Windows Server 2008 r2 | ||
+ | *RAM: 1 GB | ||
+ | *Total Disk Space: 20 GB | ||
+ | *Bandwidth Quota: 500 GB | ||
+ | |||
+ | Our sponsors have been informed of possible changes in capacity requirements and the server can be upgraded accordingly as we are on a monthly subscription. | ||
+ | |||
+ | Server status:<br> | ||
+ | Active, FTP site configured. | ||
<br> | <br> | ||
+ | <br> | ||
+ | <b>Targeted Platforms</b><br> | ||
+ | Web portal: | ||
+ | *Browser: Firefox 8, Chrome | ||
+ | *OS: Windows Vista, Windows 7, Mac OS X 10.7 | ||
+ | |||
+ | Mobile application: | ||
+ | *Web-based application | ||
+ | *Browser: Mobile Safari, Android browser | ||
+ | *OS: iOS, Android | ||
+ | </font> | ||
+ | [[Image:Clickdl-brown.png]] [[Media:cmscomparison.docx|<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">Click to see why Drupal was chosen over other CMS</span>]] | ||
+ | |- | ||
+ | | colspan="2" class="radius_bottom" style="background:#7e786f; border:2px solid #7e786f" |<div style="font-size:0">[[image:pix.gif|15px]]</div> | ||
+ | |||
+ | |} | ||
+ | |||
+ | ===Learning Outcomes=== | ||
+ | |||
+ | [[Image:Clickorange.png]] [https://wiki.smu.edu.sg/is480/Team_IMATEAM_LOMS<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">View Learning Outcomes</span>] | ||
+ | |||
+ | =<div class="NavHead" style="{{Round corners}}; background: #000000; text-align: left; padding: 2px; font-size: 160%; border:solid 4px black;"><font color="#f4ede3" size="+1"><b>Project Documentation</b></font></div>= | ||
− | <font | + | ==Diagrams== |
+ | |||
+ | ===Use Case Diagrams=== | ||
+ | |||
+ | [[Image:Clickyellow.png]] [https://wiki.smu.edu.sg/is480/Team_IMATEAM_Use_Cases<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">View Use Cases (Web & Mobile)</span>] | ||
+ | |||
+ | ===Architecture Diagram=== | ||
+ | |||
+ | [[Image:Clickgreen.png]] [https://wiki.smu.edu.sg/is480/Team_IMATEAM_Architecture_Diagram<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">View our Architecture Diagram</span>] | ||
+ | |||
+ | ===Deployment Diagram=== | ||
+ | |||
+ | [[Image:Clickblue.png]] [https://wiki.smu.edu.sg/is480/Team_IMATEAM_Deployment_Diagram<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">View our Deployment Diagram</span>] | ||
+ | |||
+ | ==Prototypes== | ||
+ | |||
+ | ===User Interface=== | ||
+ | |||
+ | ====Web Platform==== | ||
+ | |||
+ | [[Image:Clickmocl.png]] [https://wiki.smu.edu.sg/is480/Team_IMATEAM_Web_Mockup_Placeholders<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">View Mockup Placeholders</span>] | ||
+ | |||
+ | |||
+ | [[Image:Clickmocly.png]] [https://wiki.smu.edu.sg/is480/Team_IMATEAM_Web_Platform_Design<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">View Web Platform Designs</span>] | ||
+ | |||
+ | ====Mobile Platform==== | ||
+ | |||
+ | [[Image:Clickmoclg.png]] [https://wiki.smu.edu.sg/is480/Team_IMATEAM_Mobile_Platform_Design<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">View our Mobile Platform Designs</span>] | ||
+ | |||
+ | ===Logo=== | ||
+ | |||
+ | [[Image:Clickmoclb.png]] [https://wiki.smu.edu.sg/is480/Team_IMATEAM_Logo_Design<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">View our Logo Designs</span>] | ||
+ | |||
+ | ==Meeting Minutes== | ||
+ | |||
+ | [[Image:Clickmin.png]] [https://wiki.smu.edu.sg/is480/Team_IMATEAM_Meeting_Minutes<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">View our Minutes of Meetings</span>] | ||
+ | |||
+ | ==Acceptance Presentation== | ||
+ | |||
+ | [[Image:Clickdl.png]] [[Media:AcceptanceSlides.pdf|<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">Download our acceptance presentation</span>]] | ||
+ | |||
+ | =<div class="NavHead" style="{{Round corners}}; background: #000000; text-align: left; padding: 2px; font-size: 160%; border:solid 4px black;"><font color="#f4ede3" size="+1"><b>Project Management</b></font></div>= | ||
+ | |||
+ | ==Time Management== | ||
+ | |||
+ | ===Project Plan=== | ||
+ | |||
+ | [[Image:imateamProjectPlanning.jpg]] | ||
+ | |||
+ | ===Project Iterations=== | ||
+ | |||
+ | [[Image:imateamIteration.jpg]] | ||
+ | |||
+ | ===Project Tasks=== | ||
+ | |||
+ | [[Image:Clickdl.png]] [[Media:fyptasks(planned).docx|<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">Click to download our Project Tasks</span>]] | ||
+ | |||
+ | ===Schedule Metric=== | ||
+ | |||
+ | [[Image:Clicksch.png]] [https://wiki.smu.edu.sg/is480/Team_IMATEAM_Schedule_Metric#Project_Iterations<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">Click to view our Schedule Metric</span>] | ||
+ | |||
+ | ==Quality Management== | ||
+ | |||
+ | ===Bug Metric=== | ||
+ | |||
+ | [[Image:Clickbug.png]] [https://wiki.smu.edu.sg/is480/Team_IMATEAM_Bug_Metric<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">Click to view our Bug Metric</span>] | ||
+ | |||
+ | ==Risk Management== | ||
+ | |||
+ | ===Risk Metric=== | ||
+ | |||
+ | [[Image:Clickrisk.png]] [https://wiki.smu.edu.sg/is480/Team_IMATEAM_Risk_Metric<span style="color: #000000; padding: 10px 15px 0 15px; font-size: 14px;">Click to view our Risk Metric</span>] | ||
+ | |||
+ | ===Risk Analysis=== | ||
+ | |||
+ | The risks listed on this table will be specific to our group and do not include generic risks. | ||
{| class="wikitable" cellpadding="15" | {| class="wikitable" cellpadding="15" | ||
+ | |- | ||
+ | | style="background: #000000; color: #FFFFFF; padding: 10px 0 10px 30px; font-weight: bold; font-size: 14px; text-indent: 8px; width: 950px;" colspan="5" valign="top" |Project Risks | ||
+ | |- | ||
+ | | style="background: #8f8c87; color: #000000; font-weight: bold; text-indent: 2px; width: 15%;" valign="top" | <b>Risk Rating</b> | ||
+ | | style="background: #8f8c87; text-align: Left; padding-left: 20px; width: 10%;" | <b>Likelihood of Occurrence</b> | ||
+ | | style="background: #8f8c87; text-align: Left; padding-left: 20px; width: 10%;" | <b>Impact on Project</b> | ||
+ | | style="background: #8f8c87; text-align: Left; padding-left: 20px; width: 35%;" | <b>Risk</b> | ||
+ | | style="background: #8f8c87; text-align: Left; padding-left: 20px; width: 30%;" | <b>Mitigation Plan</b> | ||
+ | |||
+ | |- | ||
+ | | style="background: #921f1f; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top" rowspan="3" | A | ||
+ | | style="background: #cf5c5c; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | Medium | ||
+ | | style="background: #cf5c5c; padding-left: 20px; color: #ffffff;" valign="top" | | ||
+ | High | ||
+ | | style="background: #e38e8e; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | <b>Working with new technology and tools</b> | ||
+ | <br/> | ||
+ | Team has lack of experience in working with Drupal and jQuery Mobile (for mobile app development) which have a steep learning curve and requires time to familiarize with the technology | ||
+ | | style="background: #e38e8e; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Plan the project to allow sufficient time for the team to familiarize themselves with new technology and tools. Pair programming to share knowledge | ||
+ | |- | ||
+ | |||
+ | | style="background: #cf5c5c; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | Medium | ||
+ | | style="background: #cf5c5c; padding-left: 20px; color: #ffffff;" valign="top" | | ||
+ | High | ||
+ | | style="background: #e38e8e; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | <b>Deployment</b> | ||
+ | <br/> | ||
+ | |||
+ | Team might have deployment failures which will require some time to resolve as our virtual dedicated server is located in the United States. Hence, any request for assistance will have to depend on timezone differences. Server uptime is also dependent on the host's reliability and availability. | ||
+ | | style="background: #e38e8e; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Deploy and test the applications after every iterations, giving ourselves some buffer time in case of server downtime or assistance needed. | ||
+ | |- | ||
+ | |||
+ | | style="background: #cf5c5c; padding-left: 20px; color: #FFFFFF;" valign="top" | | ||
+ | High | ||
+ | | style="background: #cf5c5c; padding-left: 20px; color: #ffffff;" valign="top" | | ||
+ | Medium | ||
+ | | style="background: #e38e8e; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | <b>Extending Drupal Module</b> | ||
+ | <br/> | ||
+ | Required 3rd party modules do not provide full functionalities for the project. The modules need to be tested and custom-coded to cater to the project functionalities. | ||
+ | | style="background: #e38e8e; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Prioritize usage of modules which have stable releases for Drupal 7. | ||
+ | Allocate time to fix bugs and add custom features in 3rd party modules | ||
+ | |||
+ | |- | ||
|- | |- | ||
− | | style="background: # | + | | style="background: #b95a20; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top" rowspan="2" | B |
− | | style=" | + | | style="background: #d28353; padding-left: 20px; color: #FFFFFF;" valign="top" | |
− | | style="background: # | + | Medium |
− | | style=" | + | | style="background: #d28353; padding-left: 20px; color: #ffffff;" valign="top" | |
− | | style="background: # | + | Medium |
+ | | style="background: #e7bda3; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | <b>Underestimation</b> | ||
+ | <br/> | ||
+ | Underestimation of the actual duration of a task during the planning stage due to team's lack of experience and knowledge of Drupal development. This may cause us to fail to deliver intended deliverables for a milestone according to the schedule in the project plan. | ||
+ | |||
+ | | style="background: #e7bda3; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Buffer time in the schedule for unexpected lag in schedule. | ||
+ | PM to track constantly on progress of the project. | ||
+ | |||
|- | |- | ||
− | | style="background: # | + | | style="background: #d28353; padding-left: 20px; color: #FFFFFF;" valign="top" | |
− | + | Medium | |
− | | style= "background: # | + | | style="background: #d28353; padding-left: 20px; color: #ffffff;" valign="top" | |
− | | style=" | + | Medium |
− | | style="background: # | + | | style="background: #e7bda3; padding-left: 20px; color: #000000;" valign="top" | |
+ | <b>Managing Expectations</b> | ||
+ | <br/> | ||
+ | Managing sponsor’s expectations since sponsors are not technological persons who are IT-inclined. | ||
+ | | style="background: #e7bda3; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | The team is to update and discuss with sponsor which features we will be able to implement within our project's timeline. | ||
|- | |- | ||
− | | style= "background: # | + | |
− | | style=" | + | |- |
− | | style="background: # | + | | style="background: #a77814; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top" rowspan="3" | C |
− | < | + | | style="background: #b39149; padding-left: 20px; color: #FFFFFF;" valign="top" | |
− | + | Small | |
− | + | | style="background: #b39149; padding-left: 20px; color: #ffffff;" valign="top" | | |
− | + | Medium | |
− | + | | style="background: #ebd5aa; padding-left: 20px; color: #000000;" valign="top" | | |
− | + | <b>Overpromising on new features</b> | |
− | + | <br/> | |
− | | style=" | + | |
− | | style="background: # | + | Team may be too ambitious. We may promise more features due to our project being developed in Drupal and underestimate integration or debugging time, possibly resulting in us not being sticking to the schedule. |
− | + | ||
− | + | ||
− | + | | style="background: #ebd5aa; padding-left: 20px; color: #000000;" valign="top" | | |
− | + | Prioritizes the core functions in the requirement list. | |
− | + | Communicate among team members to check whether it is feasible to implement the feature promptly and take into account all the other tasks that have to be done besides the actual module development. | |
− | + | ||
− | + | |- | |
− | + | ||
− | + | | style="background: #b39149; padding-left: 20px; color: #FFFFFF;" valign="top" | | |
+ | Medium | ||
+ | | style="background: #b39149; padding-left: 20px; color: #ffffff;" valign="top" | | ||
+ | Small | ||
+ | | style="background: #ebd5aa; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | <b>Resource limitations</b> | ||
+ | <br/> | ||
+ | |||
+ | Our team only consists of 4 members and we may have insufficient resources to deliver as promised or may be overworked. | ||
+ | |||
+ | | style="background: #ebd5aa; padding-left: 20px; color: #000000;" valign="top" | | ||
+ | Efficient allocation of manpower for each task. | ||
+ | Inclusion of buffer time period for each deliverable. | ||
|- | |- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
+ | |||
+ | ==<div class="NavHead" style="{{Round corners}}; background: #000000; text-align: left; padding: 2px; font-size: 160%; border:solid 4px black;"><font color="#f4ede3" size="+1"><b>Resource & Reference</b></font></div>== | ||
+ | |||
+ | |||
+ | [[Image:imateamTools.jpg|700]] | ||
+ | |||
+ | [[Image:imateamMobile.jpg|700]]<br> | ||
+ | Our mobile web application will be developed using jQuery Mobile, a mobile web framework for smartphones. jQuery Mobile works seamlessly with PHP and mySQL, which are the technologies we are using for the web platform. It also meets our clients' needs because it is cross-platform and can be used for development on many platforms such as Apple iOS, Android, Windows Phone 7, Blackberry etc. Thus, we will not have to do different sets of codes for each separate platform. jQuery Mobile also integrates with Drupal. We chose jQuery Mobile over Sencha Touch because Sencha Touch does not support Windows Phone 7. | ||
+ | |||
+ | [[Image:imateamProgramming.jpg|700]] | ||
+ | |||
+ | [[Image:imateamCollaboration.jpg|700]] | ||
+ | |||
+ | Besides those mentioned above, we will be using the following: | ||
+ | |||
+ | *Project Management: Microsoft Office, iWork and Microsoft Visio | ||
+ | *Additional Gadgets: Mobile Smartphones for testing (Mainly iPhone and Android Phones) | ||
+ | *Training & Research: http://drupal.org/forum, http://forum.jquery.com/jquery-mobile, Google and Online tutorials |
Latest revision as of 16:09, 21 February 2012
The Team
Stakeholders
Project Overview
Project Description
|
Our team will be building a web and mobile social platform that enables attendees of conferences organized by IMAPAC to interact with each other before, during and after the conference. This social platform will allow them to post and receive conference updates, engage in discussions, network with industry partners and arrange meetings. The platform will be built using a content management system written in PHP such as Drupal. Data analysis will be applied to the information provided by the sponsor to build a user-centered system that provides recommendations to the conference attendees based on their individual profiles, such as suggestions of industry partners they might want to work with. | |
Motivation
|
Attendees of IMAPAC business conferences vary widely, from governments to NGOs, businesses and academics. They currently do not have a platform that allows their attendees to communicate efficiently with each other. Extra time spent on handling logistics issues such as scheduling of meetings, searching for contact information, arranging meeting locations etc. could be better spent on trying to create an even bigger impact for the social causes they are advocating. We also believe that if organizations have an improved communication channel, especially after a conference, they will be able to build a closer link to one another that further nurtures the social enterprise spirit within. Hence, our proposed web and mobile platform can potentially eradicate the above problems by being user friendly and interactive. We will achieve this by applying heuristics used in usability studies to the user interface design. The platform will be interactive because we will consider all aspects of each group of users’ needs and enable them to engage one another according to their business relationship.
| |
Project Deliverables
|
Overview: User OrientedWeb platform:
Mobile platform:
Admin OrientedWeb platform:
| |
Project Usability
|
Our team aims to develop a user friendly and intuitive platform for our users. Hence, usability studies play a big part of our development process as they allow us to assess user requirements and find out what works best for them. Usability studies will be conducted in two forms: heuristic evaluations and UAT. Heuristic evaluations will be based on Nielsen's ten usability heuristics, which are ten general principles for user interface design.
1 = Cosmetic problem only: need not be fixed unless extra time is available on project | |
Project Scope
We will utilize an open-source content management system written in PHP, Drupal, to develop our web application on. We chose Drupal because it is highly customizable, scalable and flexible in terms of UI design, functionalities and access control. Our project can be divided into 2 core components: the web platform and the mobile application.
Project Functionalities - User (Attendee, Speaker, Sponsor, Organizer) | ||||
Functionality | Description | |||
Web Platform |
Profile of attendees |
Users can sign up for their accounts and set up information such as bio, interests and conference-related history details. | ||
Real time feedback |
Allow attendees to provide real time feedback to speakers and fellow attendees during conferences in the form of live polls and comments. | |||
Friend system |
Anyone with an account on the social platform can add another to his network via the Friend system. | |||
Conference/event details |
Provide attendees and speakers with conference information such as detailed location, time, date, attending list, topics covered etc. | |||
Networking opportunities |
Enable users to connect with potential business partners by matching them to other users with similar interest and keywords. | |||
Make a Child smile |
Allow conference attendees to read some stories about the sponsored children helped by the efforts of IMAPAC and B1G1 thus far. This page will also have a link so that site members can choose to make a donation if they wish to. | |||
Private messaging system |
Enable users to send private messages to each other. There will be a setting to make it public or friends-only. | |||
Post-conference rating and evaluation |
Enable conference attendees to complete their post-conference evaluation for the conference and its speakers. | |||
Personalized recommendation system |
Users will be recommended similar conferences based on past history. | |||
Live note-taking function |
Allow attendees to take notes live during a conference which they can choose to save, send to email or share (public/friends only). | |||
Search |
Search for other users according to name, interests and keywords. | |||
Discussion Forum |
Forums for pre and post conference discussion. | |||
Mobile Platform |
Profile of attendees |
Simplified (only View) profiles of attendees. | ||
Conference/event details |
View conference details such as those detailed above. | |||
Geo-location services |
Locate conference location on smartphone maps using GPS. | |||
Announcement and news |
View and read announcements and news to be kept updated of event happenings. | |||
Private messaging system |
Send messages on-the-go in case they need to contact a fellow attendee. |
Project Functionalities - Administrator | ||||
Functionality | Description | |||
Web Platform |
User registration |
Import .CSV files of all newly registered users into Drupal by Admin to create the accounts | ||
Profile of attendees |
Admin can create, edit and delete profile information of all users (attendees, speaker, sponsors) | |||
Conference/event details |
Create, edit and delete conference data with uploading of files as conference resources | |||
Live note-taking function |
Manage notes taken by users at conferences | |||
Real time feedback |
Able to create polls and vote on polls during conferences | |||
Post-conference rating and evaluation |
Create rating/evaluation forms for attendees, view and collate responses |
Project X Factor
|
The selling points of our project are features that are different or not readily available in other similar social platforms out on the market such as LinkedIn and Facebook. In addition, our social platform is specially customized to meet the needs of conference attendees by catering to every aspect of their interactions. Unique features of IMAPAC Connect include:
Click to see how Connet is different from other social platforms | |
Development Environment
|
Server The specification of our production server is:
Our sponsors have been informed of possible changes in capacity requirements and the server can be upgraded accordingly as we are on a monthly subscription. Server status:
Mobile application:
| |
Learning Outcomes
Project Documentation
Diagrams
Use Case Diagrams
Architecture Diagram
Deployment Diagram
Prototypes
User Interface
Web Platform
Mobile Platform
View our Mobile Platform Designs
Logo
Meeting Minutes
Acceptance Presentation
Download our acceptance presentation
Project Management
Time Management
Project Plan
Project Iterations
Project Tasks
Click to download our Project Tasks
Schedule Metric
Click to view our Schedule Metric
Quality Management
Bug Metric
Risk Management
Risk Metric
Risk Analysis
The risks listed on this table will be specific to our group and do not include generic risks.
Project Risks | ||||
Risk Rating | Likelihood of Occurrence | Impact on Project | Risk | Mitigation Plan |
A |
Medium |
High |
Working with new technology and tools
|
Plan the project to allow sufficient time for the team to familiarize themselves with new technology and tools. Pair programming to share knowledge |
Medium |
High |
Deployment
Team might have deployment failures which will require some time to resolve as our virtual dedicated server is located in the United States. Hence, any request for assistance will have to depend on timezone differences. Server uptime is also dependent on the host's reliability and availability. |
Deploy and test the applications after every iterations, giving ourselves some buffer time in case of server downtime or assistance needed. | |
High |
Medium |
Extending Drupal Module
|
Prioritize usage of modules which have stable releases for Drupal 7. Allocate time to fix bugs and add custom features in 3rd party modules | |
B |
Medium |
Medium |
Underestimation
|
Buffer time in the schedule for unexpected lag in schedule. PM to track constantly on progress of the project. |
Medium |
Medium |
Managing Expectations
|
The team is to update and discuss with sponsor which features we will be able to implement within our project's timeline. | |
C |
Small |
Medium |
Overpromising on new features
Team may be too ambitious. We may promise more features due to our project being developed in Drupal and underestimate integration or debugging time, possibly resulting in us not being sticking to the schedule.
|
Prioritizes the core functions in the requirement list. Communicate among team members to check whether it is feasible to implement the feature promptly and take into account all the other tasks that have to be done besides the actual module development. |
Medium |
Small |
Resource limitations
Our team only consists of 4 members and we may have insufficient resources to deliver as promised or may be overworked. |
Efficient allocation of manpower for each task. Inclusion of buffer time period for each deliverable. |
Resource & Reference
Our mobile web application will be developed using jQuery Mobile, a mobile web framework for smartphones. jQuery Mobile works seamlessly with PHP and mySQL, which are the technologies we are using for the web platform. It also meets our clients' needs because it is cross-platform and can be used for development on many platforms such as Apple iOS, Android, Windows Phone 7, Blackberry etc. Thus, we will not have to do different sets of codes for each separate platform. jQuery Mobile also integrates with Drupal. We chose jQuery Mobile over Sencha Touch because Sencha Touch does not support Windows Phone 7.
Besides those mentioned above, we will be using the following:
- Project Management: Microsoft Office, iWork and Microsoft Visio
- Additional Gadgets: Mobile Smartphones for testing (Mainly iPhone and Android Phones)
- Training & Research: http://drupal.org/forum, http://forum.jquery.com/jquery-mobile, Google and Online tutorials