HeaderSIS.jpg

IS480 Team wiki: 2009T2

From IS480
Revision as of 02:36, 18 January 2010 by Deeptarka.h.2007 (talk | contribs)
Jump to navigation Jump to search

Team #

Sharp.jpg

About Us

Team Members:

  • Abhishek "earlobe" Kumar (abhishek.k.2007@smu.edu.sg) – Lead Programmer
  • Deeptarka "sizzle" Hazra (deeptarka.h.2007@smu.edu.sg) – Interface Designer
  • Namrata "momo" Sen (sen.namrata.2007@smu.edu.sg) – Chief Tester
  • Priya "nonickname" Raghavan (priya.2007.2007@smu.edu.sg) – Chief Liaison Officer
  • Shiv "chiu" Whorra (shiv.whorra.2007@smu.edu.sg) – Project Manager

The Project

The primary aim of the project is the design and development of a comprehensive e-commerce site for a travel agency dealing with national and international travel coupled with related services. The site seeks to provide an end-to-end facilitation platform for online transactions supporting the agencies’ core business process as well as for auxiliary services (such as insurance packages) provided by the agency.

The scope of the project encompasses studying the business needs of the travel agency and translating them into a site design incorporating all of the business logic captured as well as the development, testing and deployment of the e-commerce solution.

We will be working in tandem with Team Autobots to come up with our database structure. Due to constraints we will only be able to meet and discuss with them issues such as dependencies and the API in the first week of January. Our scope of the WebXTravel solution is limited to developing the user-facing front-end solution. Team Autobots will provide the back end (database) support for our project.

The Motivation

The motivation behind the project is the facilitation of a foray of the travel agency into the online realm serving the purpose of allowing for the conduct of transactions related to the agency’s core competency – selling travel packages - on an exclusively online platform. The agency seeks to capture new and wider markets through its e-commerce initiative. The website allows for this in a streamlines, low cost and effective manner.


StakeHolders

The project sponsored is designing the user-interface (front-end system) of the eCommerce travel agency website - WebXTravel, the project was introduced to us by Metor LLP, a company of a faculty member at SMU’s School of Information Systems. Prof. Ilse will be the facilitator between the company and our team – communicating to us requirements and the scope of the project as well as supervising the progress we make on the same.

Client: The client in our scenario is a travel agency, WebXTravel, for whom we are developing the e-commerce site. It is the agency who will employ what we develop and use the same in their organization. The client will host the website and allow for their end users i.e. potential travelers to use the web-site to make bookings or carry out other transactions with our client (the travel agency) via the platform provided by the e-commerce site.

End User: While our client is the travel agency, an important stakeholder we will consider during the design and development of our solution will be the end user of our website - the aforementioned customers of the travel agency as they will, in fact, be the ones interacting with and using out system most often.

Supervisor: Professor Ilse Baumgartner.

Course Coordinator: Professor Benjamin Gan


Project Management

Gantt Chart

Example.jpg

Risk Mitigation

Risk.jpg

Meeting Minutes

Minutes - Meeting 1 (Group Meeting)

Meeting 1

DateNovember 20, 2009
VenueSIS Level 2 Benches
Duration 3 hr
Meeting AttendeesTeam #
Abhishek
Deep
Namrata
Priya
Shiv

Agenda: Gathering requirements based on first meeting with the client. Creating Use Cases to further simplify the requirements Work Break Down Structure

Completed: Requirement Gathering was the only aspect completed during this meeting as it took us longer than anticipated. The meeting was ended early after the requirement gatherings had been set due to up coming examinations. It was decided in this meeting that the meetings till the examinations end will be shorter ones and we will try to finish as much as possible in these.

To be completed: Creating Use Cases WBS Structure Start off with Gantt chart

Minutes - Meeting 2 (Group Meeting)

Meeting 2

DateNovember 23, 2009
VenueSubway Benches
Duration 3 hr
Meeting AttendeesTeam #
Abhishek
Deep
Namrata
Priya
Shiv

Agenda: Creating the Use cases Work breakdown Structure Start off with the Gantt Chart

Completed: All use cases were made and completed during this meeting. The work break down structure was created too. However, as per this Work Break Down structure, we were following a waterfall process when ideally we would like to follow an iterative process. This would be changed later on after the meeting with the client to clear out the requirements for Phase I. The Gantt chart shaped in this meeting was a general one without much detailing. The detailing would also be added in once we were clear on the requirements.

To Be Completed: Role Allocation Risk Identification and Mitigation Start on the Project Proposal

Minutes - Meeting 3 (Group Meeting)

Meeting 3

DateNovember 29, 2009
VenueSIS Level 3 Benches
Duration 2.5 hr
Meeting AttendeesTeam #
Abhishek
Deep
Namrata
Priya
Shiv

This is the last meeting before December, as our team members would be occupied over December in various competitions and community service projects. More than anything else, we set out with the agenda of starting the draft project proposal and finishing as much of it as possible. Role allocation has been completed and the following permanent roles have been assigned to each member – 1. Abhishek: Lead Programmer 2. Deep: Lead Interface Designer 3. Namrata: Chief Tester & Database Manager 4. Priya: Liaison Officer & Database Manager 5. Shiv: Project Manager Everyone in the team will take up all of the roles at some point of time during the project. However, for most of the project, the above-mentioned people will be the heads in the respective departments to overlook when the others take over. Risk Identification has been completed in this meeting too and added to the draft proposal report. The standard matrix taught to us in Software Engineering has been followed here. The Draft report has been completed and is ready for submission and feedback.

To Be Completed: Currently on time and waiting for supervisor feedback.

Minutes - Meeting 4 (Group Meeting)

Meeting 4

DateDecember 18, 2009
VenueOnline
Duration 2 hr
Meeting AttendeesTeam #
Abhishek
Deep
Namrata
Priya
Shiv

Agenda: An online meeting to finalise the proposal draft, before submission on 4th January 2010.

Completed: The meeting lasted roughly 2 hours and was the only meeting we were able to coordinate over the December break since the team members were all over the globe attending different events. Supervisor feedback was incorporated. Resources and references were improved upon and everything else was left untouched as we were told that our report was fine and could be submitted.

To Be Completed: Get feedback from Ben and submit final report before 4th Jan.

Minutes - Meeting 5 (Group Meeting)

Meeting 5

DateDecember 30, 2009
VenueOnline
Duration 5.5 hr
Meeting AttendeesTeam #
Abhishek
Deep

Agenda: Change report based on feedback from Ben (Online Meeting) The feedback was as follows:

  1. Not clear what is in front end and back end (no database on your system? What API? What dependencies?)
  2. Such as insurance packages is not clear
  3. The supervisor is playing both roles as supervisor and client (can there be other client rep? Testers for the client side, domain users, travel agency, etc?) Stakeholders should be clearly identified.
  4. The scope is only at level 1. Needs 2 more level down. What fields? You need to have an agreed database schema quickly or the dependencies will delay one or both teams. Details on main page (screen shots? Prototype?), criteria for search should be clearly described (keywords? What search engine? Multi keywords? Etc), workflow on the shopping cart, what payment methods (research/reference on how to do this) I don’t understand what is 7. Be specific on 8. Limit the scope with the sponsor. If insurance package, say insurance package only. This is usually where the sponsor and the developer differ in what it means.
  5. The WBS looks like waterfall. Deliverables need dates! Rough dates are OK 2 week iterations? With user testing on each iteration?
  6. Lack of familiarity is top risk exposure but team have 2-4 VS. Mitigation over dec but what does it mean? Is there assigned work in dec? What prototypes have you developed? Anyone done google analytics/map? Crystal reports? There are good tutorials. These needs to be in the resource and references section. Links to your training. (more than the 3 footnotes).
  7. The learning objectives are included in all IS480 projects. I suggest you concentrate on 1 or 2 and define it as an X factor in your project. As you are doing the front end, maybe learning about Usability and research on HCI, usability testing, etc might be good.

The agenda of this meeting was to try and incorporate as much of Ben’s feedback as possible into our proposal with the short time we had.

Completed: The meeting lasted almost 5-6 hours so that we could incorporate as much of the feedback as possible. The changes have been documented in the versioning history of the proposal report. However, not all changes could be made since we were still unclear on various aspects of the project, as we had not had our first client-team meeting yet. The Proposal was submitted for grading

To Be Completed: Get started on Elaboration phase I after 1st meeting with client.

Minutes - Meeting 6 (Group Meeting)

Meeting 6

DateJanuary 5, 2010
VenueSophia Food Mall Study Area
Duration 4 hr
Meeting AttendeesTeam #
Abhishek
Deep
Namrata
Priya

Agenda: UI Conceptualization Gantt chart updating Class Diagrams

Completed: The UI Prototype had already been made over the December break and we roughly had an idea of what was required in the application. It was further discussed and a UI template was finalized for us to start work on. After the meeting with the client and all members being back, we updated the gantt chart with details of the project timeline. Class Diagrams were created during the meeting and previous class diagrams were updated. Updated in documents

To Be Completed: Sequence Diagrams System Sequence Diagrams Use Case with descriptions

Minutes - Meeting 7 (Group Meeting)

Meeting 7

DateJanuary 11, 2010
VenueSophia Food Mall Study Area
Duration 4 hr
Meeting AttendeesTeam #
Abhishek
Namrata
Priya

Agenda: The agenda of this meeting was to complete the following: Sequence Diagrams System Sequence Diagrams Use case with descriptions

Completed: All the system diagrams and system sequence diagrams were completed so we could get started on the coding aspect of the application. Previous use cases were updated and new ones created. Use case descriptions were added to each use case.

To Be Completed: Start coding on the user interface Start creating the design website layout

Prototype

Proto1.jpg Proto2.jpg Proto3.jpg