HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2010T1 eNable"

From IS480
Jump to navigation Jump to search
 
(19 intermediate revisions by 2 users not shown)
Line 2: Line 2:
  
 
== Project Overview ==
 
== Project Overview ==
==== Whom are we working for? ====
+
=== Whom are we working for? ===
Our team is working for a non-profit organization, named Friends of The Disabled Society (FDS).  FDS establishes programs that brings a bridge between the able bodies and disabled friends together with the help from members and well-wishers.  Among those programs, the Skills Enrichment Program, which our project's focus is on, currently conducts training to advance the skills and creativity of the disabled friends in handicraft and jewelry making.
+
Our team is working for a non-profit organization, named '''Friends of The Disabled Society (FDS)'''.  FDS establishes programs that brings a bridge between the able bodies and disabled friends together with the help from members and well-wishers.  Among those programs, the Skills Enrichment Program, which our project's focus is on, currently conducts training to advance the skills and creativity of the disabled friends in handicraft and jewelry making.
  
==== Problem ====
+
=== Problem ===
 
Regarding the Skills Enrichment Program, FDS currently has a shopping website hosted on a blog only.  The problem comes in as this blog is not designed for disabled friends; so, they have to go through multiple steps just to upload one product.  Moreover, the current website cannot assist FDS in processing orders, managing products and generating reports. With all these limitations and more, the potential collaboration between the customers and disabled people is hindered.
 
Regarding the Skills Enrichment Program, FDS currently has a shopping website hosted on a blog only.  The problem comes in as this blog is not designed for disabled friends; so, they have to go through multiple steps just to upload one product.  Moreover, the current website cannot assist FDS in processing orders, managing products and generating reports. With all these limitations and more, the potential collaboration between the customers and disabled people is hindered.
  
the organization is currently facing a problem of not having an e-commerce system where the disabled friends can sell their products conveniently with minimum supervision.
+
=== Solution ===
 +
Our team believes that applications that involve interactions with disabled friends should be more effective than this while being kept simple.  Thus, we are determined to come up with a proper and professional e-commerce system that comes together with a simple, tidy and easy-to-manage back-end interface especially designed for the disabled friends.  This system will also be well equipped with all the functions that are necessary and useful for the users.  The detailed functions each user can do with the application can be seen in Use Cases section below.  
  
==== Solution ====
+
=== Use Cases ===
Our team believes that applications that involve interactions with disabled friends should be more effective than this while being kept simpleThus, we are determined to come up with a proper and professional e-commerce system that comes together with a simple, tidy and easy-to-manage back-end interface especially designed for the disabled friends.  This system will also be well equipped with all the functions that are necessary and useful for the users. The detailed functions each user can do with the application can be seen in Use Cases section below.  
+
Here, you can see what each user can do with our systemIn the use cases, you will see circles of different colors.
 +
* White Circles: As-is functions from OpenCart with very minor modifications made
 +
* Green Circles: Functions with major modifications made
 +
* Yellow Circles: Brand new functions
 +
==== Customer ====
 +
[[Image:CustomerUseCase.jpg]] <br><br>
 +
 
 +
==== Admin Assistant ====
 +
[[Image:AAUseCase.jpg]] <br><br>
  
==== Use Cases ====
+
==== Top Admin ====
[[Image:BuyerUseCase.jpg]] <br>
+
The Top Admin can do everything the Admin Assistant does.  On top of that, the Top Admin can do some additional tasks which are represented by red arrows.<br>
[[Image:SellerUseCase.jpg]] <br>
+
[[Image:TopAdminUseCase.jpg]] <br>
[[Image:AdminUseCase.jpg]]
 
  
 
== Stakeholders ==
 
== Stakeholders ==
==== Supervisor ====
+
=== Supervisor ===
 
'''''[http://www.sis.smu.edu.sg/faculty/infosys/kevinsteppe.asp Kevin Steppe]'''''
 
'''''[http://www.sis.smu.edu.sg/faculty/infosys/kevinsteppe.asp Kevin Steppe]'''''
  
==== Sponsor/Client ====
+
=== Sponsor/Client ===
 
* Ms. S Roogmanny (Executive Director, Friends of Disabled Society)
 
* Ms. S Roogmanny (Executive Director, Friends of Disabled Society)
 
* Mr. Joel Chiang (IT Manager, Jweeb Solutions Group)
 
* Mr. Joel Chiang (IT Manager, Jweeb Solutions Group)
  
==== Team eNable ====
+
=== Team eNable ===
 
# '''''[mailto:erene.ong.2008@sis.smu.edu.sg Erene ONG Yiling]'''''
 
# '''''[mailto:erene.ong.2008@sis.smu.edu.sg Erene ONG Yiling]'''''
 
# '''''[mailto:tdkhine.2007@sis.smu.edu.sg KHINE Tharaphe Din]'''''
 
# '''''[mailto:tdkhine.2007@sis.smu.edu.sg KHINE Tharaphe Din]'''''
Line 32: Line 40:
 
# '''''[mailto:lumon.kyaw.2008@sis.smu.edu.sg Lu Mon KYAW]'''''
 
# '''''[mailto:lumon.kyaw.2008@sis.smu.edu.sg Lu Mon KYAW]'''''
 
# '''''[mailto:soethetaung.2008@sis.smu.edu.sg Soe Thet AUNG]'''''
 
# '''''[mailto:soethetaung.2008@sis.smu.edu.sg Soe Thet AUNG]'''''
 +
<br>
  
 
== Project Management ==
 
== Project Management ==
 
Our team will use SCRUM project management framework.   
 
Our team will use SCRUM project management framework.   
  
==== SCRUM Documents ====
+
=== SCRUM Documents ===
[[Media:Enable_productback.docx|Product Backlog]] serves as a primary document for the client and the team to look into the list of all the functionalities that are to be implemented.  The functionalities are listed in order of their priority. <br>
+
'''''[[Media:Enable_productback.docx|Product Backlog]]''''' serves as a primary document for the client and the team to look into the list of all the functionalities that are to be implemented.  The functionalities are listed in order of their priority. <br>
[[Media:Enable_sprintback.docx|Sprint Backlogs]] is a subset of Product Backlog containing a detailed breakdown of functionalities into tasks for each of the sprints.
+
'''''[[Media:Enable_sprintback.docx|Sprint Backlog]]''''' is a subset of Product Backlog containing a detailed breakdown of functionalities into tasks for each of the sprints.
  
==== Project Schedule ====
+
=== Project Schedule ===
You can see the Planned Schedule of the whole project [[Media:Enable_planneds.docx|here]].  The comparison of this Planned Schedule and the Actual Schedule over time can be seen on our Midterm Wiki and Final Wiki pages.
+
Here, you can see our '''''[[Media:Enable_PlannedSchedule.docx|Planned Schedule]]''''' and '''''[[Media:Enable_ActualSchedule.docx|Actual Schedule]]''''' of the whole project.  As all the sprints have a fixed length of 15 days, any scope or requirement change throughout the project did not have an impact on the start date or end date of the sprints.  It only affected the iterations.  The changes in dates and additional tasks added are highlighted in red in the Actual Schedule.  The comparison of the two schedules over time can also be seen on our '''''[[Team eNable - Midterm Wiki|Midterm Wiki]]''''' and '''''[[Team eNable - Final Wiki|Final Wiki]]''''' pages.
  
==== Roles & Responsibilities ====
+
=== Roles & Responsibilities ===
 
{| border="3"
 
{| border="3"
 
|- style="background: silver; color: black"
 
|- style="background: silver; color: black"
Line 51: Line 60:
 
|-  
 
|-  
 
! scope=row | Din
 
! scope=row | Din
| Project Manager
+
| <div style="text-align:center;">Project Manager</div>
 
| - Plan meeting agenda and milestones<br>
 
| - Plan meeting agenda and milestones<br>
 
- Make sure the team is on the right track and in progress<br>
 
- Make sure the team is on the right track and in progress<br>
Line 57: Line 66:
 
|-
 
|-
 
! scope=row | Erene
 
! scope=row | Erene
| Chief Programmer || - Translate clients' requirements into functionalities<br>
+
| <div style="text-align:center;">Chief Programmer</div>
 +
| - Translate clients' requirements into functionalities<br>
 
- Integrate frontend design and backend logic
 
- Integrate frontend design and backend logic
 
|-
 
|-
 
! scope=row | Kyaw
 
! scope=row | Kyaw
| Chief Tester || - Track and prioritize bugs<br>
+
| <div style="text-align:center;">Chief Tester</div>
 +
| - Track and prioritize bugs<br>
 
- Develop test plans to ensure a smooth application
 
- Develop test plans to ensure a smooth application
 
|-
 
|-
 
! scope=row | Lu Mon
 
! scope=row | Lu Mon
| Chief Designer || - Create designs for user interface
+
| <div style="text-align:center;">Chief Designer</div>
 +
| - Create designs for user interface
 
|-
 
|-
 
! scope=row | Soe Thet
 
! scope=row | Soe Thet
| System Admin || - Create and maintain the server and system database   
+
| <div style="text-align:center;">System Admin</div>
 +
| - Create and maintain the server and system database   
 
|}
 
|}
  
==== Project Risks ====
+
=== Project Risks ===
 +
The risks specific to our project at the initial state are as follows: <br>
 +
{| border="3"
 +
|- style="background: silver; color: black"
 +
! scope=col width="200" | Risks
 +
! scope=col width="100" | Likelihood
 +
! scope=col width="100" | Impact
 +
! scope=col width="100" | Risk Level
 +
! scope=col width="400" | Mitigation Plans
 +
|-
 +
| Lack of experiences in php resulting a delay during application development
 +
| Moderate
 +
| High
 +
| High
 +
| Do research on php and help each other to be more familiar with it in a shorter period of time
 +
|-
 +
| No prior knowledge of OpenCart
 +
| High
 +
| High
 +
| High
 +
| Allocate  some time to familiarize with the new system
 +
|-
 +
| Look and feel of the application does not meet the end users’ needs
 +
| Moderate
 +
| Moderate
 +
| Moderate
 +
| Perform UAT with the real end users and gather feedback to ensure a design that appeals to them
 +
|-
 +
| Maintenance of the system by the client
 +
| High
 +
| Low
 +
| Moderate
 +
| Schedule some trainings for the client/admin of the system at the end of the project
 +
|}
  
 +
=== Quality Assurance ===
 +
To make sure that our project quality is kept at its best and that the application built meets the client's expectations, we will perform a number of User Acceptance Tests with the client and real end users throughout the project.  Moreover, we will also use Schedule Metric and Bug Metric to track the team's productivity and quality of work done.
  
==== Quality Assurance ====
+
== Go To ==
 +
'''''[[Team eNable - Midterm Wiki|Midterm Wiki]]'''''<br>
 +
'''''[[Team eNable - Final Wiki|Final Wiki]]'''''

Latest revision as of 23:57, 28 November 2010

eNable

Project Overview

Whom are we working for?

Our team is working for a non-profit organization, named Friends of The Disabled Society (FDS). FDS establishes programs that brings a bridge between the able bodies and disabled friends together with the help from members and well-wishers. Among those programs, the Skills Enrichment Program, which our project's focus is on, currently conducts training to advance the skills and creativity of the disabled friends in handicraft and jewelry making.

Problem

Regarding the Skills Enrichment Program, FDS currently has a shopping website hosted on a blog only. The problem comes in as this blog is not designed for disabled friends; so, they have to go through multiple steps just to upload one product. Moreover, the current website cannot assist FDS in processing orders, managing products and generating reports. With all these limitations and more, the potential collaboration between the customers and disabled people is hindered.

Solution

Our team believes that applications that involve interactions with disabled friends should be more effective than this while being kept simple. Thus, we are determined to come up with a proper and professional e-commerce system that comes together with a simple, tidy and easy-to-manage back-end interface especially designed for the disabled friends. This system will also be well equipped with all the functions that are necessary and useful for the users. The detailed functions each user can do with the application can be seen in Use Cases section below.

Use Cases

Here, you can see what each user can do with our system. In the use cases, you will see circles of different colors.

  • White Circles: As-is functions from OpenCart with very minor modifications made
  • Green Circles: Functions with major modifications made
  • Yellow Circles: Brand new functions

Customer

CustomerUseCase.jpg

Admin Assistant

AAUseCase.jpg

Top Admin

The Top Admin can do everything the Admin Assistant does. On top of that, the Top Admin can do some additional tasks which are represented by red arrows.
TopAdminUseCase.jpg

Stakeholders

Supervisor

Kevin Steppe

Sponsor/Client

  • Ms. S Roogmanny (Executive Director, Friends of Disabled Society)
  • Mr. Joel Chiang (IT Manager, Jweeb Solutions Group)

Team eNable

  1. Erene ONG Yiling
  2. KHINE Tharaphe Din
  3. KYAW Zin Hein
  4. Lu Mon KYAW
  5. Soe Thet AUNG


Project Management

Our team will use SCRUM project management framework.

SCRUM Documents

Product Backlog serves as a primary document for the client and the team to look into the list of all the functionalities that are to be implemented. The functionalities are listed in order of their priority.
Sprint Backlog is a subset of Product Backlog containing a detailed breakdown of functionalities into tasks for each of the sprints.

Project Schedule

Here, you can see our Planned Schedule and Actual Schedule of the whole project. As all the sprints have a fixed length of 15 days, any scope or requirement change throughout the project did not have an impact on the start date or end date of the sprints. It only affected the iterations. The changes in dates and additional tasks added are highlighted in red in the Actual Schedule. The comparison of the two schedules over time can also be seen on our Midterm Wiki and Final Wiki pages.

Roles & Responsibilities

Member Primary Role Responsibilities
Din
Project Manager
- Plan meeting agenda and milestones

- Make sure the team is on the right track and in progress
- Resolve internal conflicts, if any

Erene
Chief Programmer
- Translate clients' requirements into functionalities

- Integrate frontend design and backend logic

Kyaw
Chief Tester
- Track and prioritize bugs

- Develop test plans to ensure a smooth application

Lu Mon
Chief Designer
- Create designs for user interface
Soe Thet
System Admin
- Create and maintain the server and system database

Project Risks

The risks specific to our project at the initial state are as follows:

Risks Likelihood Impact Risk Level Mitigation Plans
Lack of experiences in php resulting a delay during application development Moderate High High Do research on php and help each other to be more familiar with it in a shorter period of time
No prior knowledge of OpenCart High High High Allocate some time to familiarize with the new system
Look and feel of the application does not meet the end users’ needs Moderate Moderate Moderate Perform UAT with the real end users and gather feedback to ensure a design that appeals to them
Maintenance of the system by the client High Low Moderate Schedule some trainings for the client/admin of the system at the end of the project

Quality Assurance

To make sure that our project quality is kept at its best and that the application built meets the client's expectations, we will perform a number of User Acceptance Tests with the client and real end users throughout the project. Moreover, we will also use Schedule Metric and Bug Metric to track the team's productivity and quality of work done.

Go To

Midterm Wiki
Final Wiki