Upload
others
View
1
Download
0
Embed Size (px)
Citation preview
2010
BUS 338 & CMPT 275
Understanding
Technological Innovation
& Software Innovation
Software Engineering I
Group: 8
ASSIGNMENT 1: PROJECT PLAN
GROUP #8 GRACE KAI, JULIAN DESCHUTTER, KATELYN WEATHERALL, ALFRED DE VERA, JORDON KIPNES
GARY HUI, ANGUS MACDONALD, JOOYONG JEONG, ELVIS ISIC
1
Table of Contents
Project Plan .......................................................................................................................................
1.0 Revision History .................................................................................................................... 2
2.0 Project Summary ................................................................................................................... 2
3.0 Project Overview ................................................................................................................... 3
3.1 The Problems .................................................................................................................... 3
3.2 The Solutions ..................................................................................................................... 3
3.3 The Stakeholders ............................................................................................................... 3
3.4 Features of the Aps ............................................................................................................ 3
3.5 Features that the Application will not have ....................................................................... 3
4.0 Project Planning .................................................................................................................... 4
4.1 Progress ............................................................................................................................. 5
4.2 The Website ....................................................................................................................... 5
4.3 Internal Communication Structure .................................................................................... 5
4.4 External Communication Structure ................................................................................... 5
5.0 Project Schedule .................................................................................................................... 6
6.0 Risk Management .................................................................................................................. 7
7.0 Project Organization and Staffing Plan ................................................................................. 8
7.1 Angus MacDonald ............................................................................................................. 8
7.2 Elvis Isic ............................................................................................................................ 8
7.3 Gary Hui ............................................................................................................................ 8
7.4 Jooyong Jeong ................................................................................................................... 8
7.5 Julian DeSchutter ............................................................................................................... 9
7.6 Katelyn Weatherall ............................................................................................................ 9
7.7 Alfred De Vera ................................................................................................................. 9
7.8 Grace Kai ........................................................................................................................... 9
7.9 Jordan Kipnes ................................................................................................................... 9
8.0 Team Meeting Minutes ....................................................................................................... 10
2
1.0 Revision History
Table 1.1 – Revision History
Revision Status Revision Date Revised By:
1.0 Created September 23rd, 2010 Angus MacDonald, Gary Hui,
Jooyong Jeong, Elvis Isic
1.1 Content input and
edit
September 26th, 2010 Grace Kai, Alfred De Vera,
Katelyn Weatherall, Jordan Kipnes,
Julian Deschutter,
1.2 Final revision
with both groups
September 28th, 2010 Everyone
2.0 Project Summary
The SFU BizAPP is designed to not only help SFU students Think of the World, but more
importantly Move up in the World. It is intended to provide clarification for prospective and
transfer students interested in applying to the SFU faculty of business, as well as service the
students who are already accepted. Its functions include a business course rating system, a GPA
transfer calculator, SFU business news and events RSS feeds, campus maps, and a variety of
essential tips and tricks for business students such as business faculty contacts and common lingo
used throughout the campuses. This application will be available for download for the iPhone,
the iPad, and the iPod touch.
3
3.0 Project Overview
3.1 The Problems:
� Students need to understand what is required to get into and succeed in SFU business, but
do not always have a chance to meet with faculty advisors.
� Students need to understand what a course actually entails when designing their next
semester and planning their degree.
� Students need a one-stop shop for all relevant SFU Business information.
3.2 The Solutions:
� To efficiently self-map business faculty requirements via a GPA calculator and course
outline depending on a student’s concentration.
� To provide course reviews from previous students who have taken the course, which will
give insight into the various aspects of each course. This will allow students to plan their
course schedules and degrees more effectively.
� To create a connection for interested SFU business students, the faculty of business, and
its associations.
3.3 The Stakeholders:
� Students who:
o Want to be more aware of SFU Business events & news.
o Are looking to enter the faculty of business.
o Are planning on enrolling in a business course.
� The SFU Faculty of Business – This application will affect the faculty of business as it
will be an extension of their department. Although it is student content driven, it still
needs to reflect the values and vision of SFU Business. Understanding what these are will
be a key component to the creation of the application.
� Academic Advisors – This application will affect academic advisors as it will be
designed to help students create a pathway in SFU Business. The content that will be in
the application will need to be verified and accepted by academic advisors.
� The Class Professors – Dr. Herbert Tsang & Dr. Jan Kietzmann will be the primary
facilitators for production of this application.
4
3.4 Features of the Application:
Essential
� The ability to view and provide feedback on SFU Business courses
o Each course will be ranked on the following criteria:
� Overall difficulty
� Amount of group work
� Writing Intensive
� Relevance to real world
o The following user generated content will be tied to each course:
� Which classes students should and should not take together
� Which campus students should take the class at
� A map of the campuses, highlighting dining areas, study areas, important Business
locations (advising centers, faculty office areas), and parking areas.
� Business GPA Calculator that will let prospective students know how close they are to
entering the program:
o This will tell them what grades they need to get in their remaining courses in
order to reach the required GPA for admission
� A news aggregator that pulls from relevant news feeds
� A list of ongoing and future events:
o Editing access will be provided to student groups (i.e. SIFE)
� A list of important contacts
� A glossary of relevant faculty jargon
� A list of suggested tips and tricks to improve class performance
Conditional
� A course scheduler/planner tied in with the course feedback system
� Social network integration
� Addition of extra dining information to the map, such as menus and hours of operation
� Addition of extra parking information to the map, such as rates and rate comparison
� Grouping option in contacts to help keep class groups organized
� Notifications for classes tied into course scheduler
� Homework planner that notifies students when homework is nearing its due date
Optional
� iClicker emulation
� GPS integration with the map
� GPS-based path finding on maps feature
� Event locations on map
3.5 Features the Application will not include:
� Faculty representation from other SFU faculty and student populations.
� A professor rating system.
5
4.0 Project Planning
4.1 Progress:
� Ideas were bounced back and forth about potential features of the application.
� Content for the application has since been decided on and research pertaining to each
feature is under way.
4.2 Website:
Our project website will be hosted by Google Code and regularly maintained. It can be found at
http://code.google.com/p/sfubusinessessentials/. Here project issues will be tracked, backups
maintained and code shared, in addition to hosting copies of all class assignments and other
relevant files.
4.3 Internal Communication Structure:
Communication between group members will be maintained through regular in person meetings,
e-mails and phone calls. Important project documents will be attached in e-mails and hosted on
the Google Code website.
4.4 External Communication Structure:
Frequent meetings will be held and both groups will collaborate whenever necessary. At least
one in person meeting will be held per week. Time for this meeting will be put aside each week.
Table 4.1 – Communication Structure
Type Objective Frequency Audience
Kickoff Meeting Decide on project to execute.
Define objectives and team
goals.
Once • Project team
• All potential
stakeholders
Project Team
Meetings
Review status and progress of
the project and its
deliverables.
Weekly • Project team
Business Faculty
Meeting
Obtain and secure business
faculty support for our
application.
As Needed • Business sponsors
• Project team
7
6.0 Risk Management
Table 6.1 – Risks
Risk Severity Management Strategy Similar user function to
current applications
including RateMyProfessor
and other university
applications
Could prevent students with
similar applications to download
another.
Clearly differentiate offering
through variety of options
for students.
CMPT science team unable
to develop specific business
functions identified
Lack of useable functions could
prevent others from
downloading this application.
Develop contingency plan
for alternate application
functions that could be
generated.
Lack of team experience
developing for the
application’s platform
Learning to develop for the new
platform will use up time that
could be spent creating and
improving features.
An early start in addition to
strong communication and
time management skills will
help limit the amount of
time required to learn to
develop for the new
platform.
Lack of access to the
platform and the hardware
necessary to develop for the
platform.
Limits the amount of time team
members can spend developing
the software.
Make hardware available to
those with time to make use
of it. Research into
development methods that
can make use of alternate
hardware.
Hardware Failure Will prevent development and
testing on the failed machine in
addition to data corruption and
loss on the machine. Machine
will then have to be replaced or
repaired before development can
resume.
Create many backups in
varied locations to prevent
data loss. Hardware should
be regularly and properly
maintained to prevent
failure.
Disinterest and lack of
commitment from business
faculty members
Application may lack sufficient
support needed to legitimize its
functional use for prospective
and current students
Approach SFU Business
faculty with messages that
appeal to their business
objectives
8
7.0 Project Organization and Staffing Plan
ANGUS MACDONALD
Email: [email protected]
Role(s):QA, Documentation, Development
ELVIS ISIC
Email: [email protected]
Role(s): QA, Project Manager, Documentation,
Development
GARY HUI
Email: [email protected]
Role(s): QA, Documentation, Development
JOOYONG JEONG
Email: [email protected]
Role(s): QA, Documentation, Development
9
JULIAN DESCHUTTER
Email: [email protected]
Roles: Concept Generator
KATELYN WEATHERALL
Email: [email protected]
Roles: Organizer, Point Contact
ALFRED DE VERA
Email: [email protected]
Roles: Writer
GRACE KAI
Email: [email protected]
Roles: Formatter, Partial organizer
JORDAN KIPNES
Email: [email protected]
Roles: Editor
10
9.0 Team Meeting Minutes
Team 8 Meeting #1 September 19th
2010
1:35
Burnaby CSIL Lab
Meeting called by: Gary Hui Type of meeting: Discussion of Assignment #1
Facilitator: Gary Hui Note taker: Angus MacDonald
Timekeeper: Elvis Isic
Attendees: Elvis Isic, Gary Hui, Angus MacDonald
Absent: Jooyong Jeong
Please read: N/A
Please bring: N/A
Minutes
Agenda item: Introductions/General Discussion Presenter: All Attendees
Discussion:
Semester load and time availability were discussed.
Group decided we were determined to try and win.
Available resources were discussed.
Angus and Elvis are able to provide MACs, iPhone and iPod touch.
Google Docs was decided as the main method of keeping track of work division and to do lists.
Discussed setup for meeting with BUS students in Surrey and arrangement of next meeting.
Decided Jooyong should read meeting minutes, preferably before next class.
Conclusions: We should be able to do some awesome stuff.
Action items Person responsible Deadline
� Get iPod Touch Angus Sep 20th
� Attend meeting with BUS students Angus and Gary Sep 21st
� Download XCode Angus Sep 20th
� Setup group Google Docs
Dropped in favour of github Angus Sep 21
st
� Read meeting minutes Jooyong Sep 20th
� Arranging next meeting Gary DONE
11
Agenda item: Communication Structure Discussion Presenter: All Attendees
Discussion: Began setting up a Google Doc spreadsheet for a to do list.
Elvis brought up the possibility of using Google Code.
Spent some time working through the features of Google Code.
Elvis brought up the possibility of github, spent time working through its features.
Elvis contacted a friend who has experience with the various tools, his friend recommended SourceForge.
Spent some time looking through the features of SourceForge.
Decided against SourceForge since it forces us to go Open Source.
Decided we’d go with github.
Found out github isn’t as free as we thought. Decided to go with Google Code.
Discovered that Google Code is open as well.
Switched back to github.
Decided we’d keep everything in passworded .rar files.
Password was decided to be: Sherlock
If this proves to be a problem we decided we would purchase a temporary github subscription for the
duration of the course.
Conclusions: We’re going to use github.
Action items Person responsible Deadline
� Create github account and project. Elvis DONE
� Create github account, send Elvis your info. Everyone but Elvis ASAP
Agenda item: Website Creation Discussion Presenter: Angus
Discussion: Angus asked if he could create the website.
Group consented.
Conclusions: Angus will create the website.
Action items Person responsible Deadline
� Create website Angus Sep 28th
Agenda item: Assign Group Roles Presenter: Elvis
Discussion: Decided everyone should be involved in QA.
Elvis nominated and voted project manager.
Note taker to be decided on a per meeting basis.
Documentation and Development assigned to everyone.
Documentation and Development will be subdivided as requirements are discovered.
12
Conclusions: As above.
Action items Person responsible Deadline
� N/A
Agenda item: Discussion of next meeting time Presenter: Gary
Discussion: Gary questioned attendees about availability after Wednesday.
In light of availability 11:30AM was decided to be the best time for our next meeting.
Conclusions: As above.
Action items Person responsible Deadline
� Consult Jooyong Gary DONE
Agenda item: Discussion of next meeting content Presenter: Angus
Discussion: Discuss any new developments
Define requirements for the app
Review project website
Complete Assignment 1
Time permitting:
- Affinity Mapping
- Paper Prototyping
Conclusions: As above.
Action items Person responsible Deadline
� N/A
�
Other Information
Observers: N/A
Resources: N/A
Special notes: N/A
Team 8 Meeting w/ BUS #1 September 21st 2010
~1:00
13
SFU Surrey Library
Meeting called by: Gary Hui Type of meeting: Discussion of App Features
Facilitator: Gary Hui Note taker: Angus MacDonald
Timekeeper: Jooyong Jeong
Attendees: Jooyong Jeong, Gary Hui, Angus MacDonald, Julian DeSchutter, Grace Kai, Katelyn Weatherall
Absent: Elvis Isic, Alfred De Vera, Jordan Kipnes
Please read: N/A
Please bring: N/A
Minutes
Agenda item: Application goals Presenter: All Attendees
Discussion:
Make it easy for non BUS students to find out what they need to do to become BUS students and track their
progress towards that goal.
Develop a course rating feature for BUS courses. Staying away from commentary on professors.
Inclusion of course transfer information from other universities.
Inclusion of features suggested in CMPT 275, such as map, events and news.
Inclusion of a contacts feature.
Conclusions: These are our goals.
Action items Person responsible Deadline
� Deliver a prioritized list of contact information BUS Students Soon
Agenda item: BUS GPA Tracker Presenter: All Attendees
Discussion:
User should be able to calculate their CGPA for the nine business courses required to gain entry to the
program.
Should display the CGPA for these courses that are required for successful admittance.
Conclusions: These are our goals.
Action items Person responsible Deadline
�
14
Agenda item: Contact list Presenter: All Attendees
Discussion: List of important contacts for BUS departments.
Prioritized.
Conclusions: These are our goals.
Action items Person responsible Deadline
�
Agenda item: Maps Presenter: All Attendees
Discussion: Highlight important BUS rooms. Such as advisors/offices.
Conclusions: These are our goals.
Action items Person responsible Deadline
� Deliver list of important rooms and their locations BUS Students Soon
Agenda item: News/Events Presenter: All Attendees
Discussion: Should be in there, heavy focus on BUS related news only. Possibly the option for general news.
Conclusions: These are our goals.
15
Action items Person responsible Deadline
�
Agenda item: Course transfer information Presenter: All Attendees
Discussion:
BUS courses only.
Students should be able to find out what courses from other Universities and Colleges are equivalent to SFU
BUS courses.
Conclusions: These are our goals.
Action items Person responsible Deadline
�
Agenda item: Events Presenter: All Attendees
Discussion: Information on what, where and when should be displayed.
Locations should be tied into the Maps feature.
Conclusions: These are our goals.
Action items Person responsible Deadline
�
Agenda item: Course ratings Presenter: All Attendees
Discussion:
Users should be able to rate without registering any account information
Should be able to choose the course no, have the name displayed.
User should then be able to rate overall, difficulty, homework load and relevance.
Users should also be able to leave comments.
Possibly include option to recommend other courses that should be taken concurrently.
16
Conclusions: These are our goals.
Action items Person responsible Deadline
�
Agenda item: Next meeting and communication scheme Presenter: All Attendees
Discussion:
Send e-mails to everyone, always use Reply All.
A Google Doc for inter-team communication/brainstorming should be setup.
Agreed to arrange our next meeting at Columbia Skytrain station Tuesday the 28th at 1PM.
E-Mail with contact information sent to everyone.
Conclusions: These are our goals.
Action items Person responsible Deadline
� Setup a Google Doc Katelyn Soon
Team 8 Meeting #2
Sept 23,10
10:30 am
Burnaby Campus CSIL
Meeting called by: Gary Hui Type of meeting: Discussion/Brainstorm/Assignment 1
Facilitator: Elvis Isic Note taker: Gary Hui
Timekeeper: Gary Hui
Attendees: Gary Hui, Angus Macdonald, Elvis Isic, Jooyong
Absent:
Please read:
Please bring:
Minutes
Agenda item: Google Code Presenter: Elvis Isic
Discussion: To use Google Code as our base for the website portion of Assignment 1.
17
Conclusions: Calling the project “sfubusinessentials” due to the lowercase and no space requirement for Google Code.
Almost done, just require team member bios.
Action items Person responsible Deadline
� Make a Google code website Elvis Isic Sept 28,10
Agenda item: Assignment 1 Presenter: Angus Macdonald
Discussion: To attempt to complete Assignment 1.
Conclusions: Finished most of the Assignment, just need to put together the Gantt Chart into the Project Plan.
Action items Person responsible Deadline
� Make the Google Code website. Elvis Isic Sept 28,10
� Make the Project Plan. Everyone Sept 28,10
Agenda item: Gantt Chart Presenter: Gary Hui
Discussion: To create the Gantt Chart requested in Assignment 1.
Conclusions: Finished
Action items Person responsible Deadline
� Create Gantt Chart in MS Project 2003 Gary Hui Sept 28,10
Team 8 Meeting with BUS #2 September 28th
2010
12:30
Starbucks Columbia Station
Meeting called by: Gary Hui Type of meeting: Finalize Details of Assignment #1
Facilitator: Alfred De Vera Note taker: Angus MacDonald
Timekeeper: Elvis Isic
Attendees: Elvis Isic, Gary Hui, Angus MacDonald, Jooyong Jeong, Alfred De Vera, Katelyn Weatherall, Grace Kai,
Jordan Kipnes, Julian DeSchutter
Absent: None
Please read: N/A
Please bring: N/A
Minutes
Agenda item: Merge Existing Project Plans Presenter: All Attendees
18
Discussion: Make sure each item in the project plans aligns with the team’s overall goals and objectives
Edit merged document for consistency and redundancies
Conclusions: Project Plan unified into one document
Action items Person responsible Deadline
� Finish Rough Edit Alfred Sep 28th
� Format paper Grace Sep 28th
� Final edits Katelyn and Alfred Sep 28th
Agenda item: Finish Gantt Chart Presenter: Gary Hui
Discussion: Find scheduled start and end dates for each deliverable for both BUS and CMPT classes
Enter dates into Microsoft Project to create Gantt chart