COMP 1930
Projects 1
School | School of Computing and Academic Studies |
---|---|
Program | Computer Systems Technology (CST) Diploma |
Course Credits | 4 |
Minimum Passing Grade | 50% |
Start Date | September 03, 2019 |
End Date | December 13, 2019 |
Total Hours* | 60 |
Total Weeks | 15 |
Hours/Weeks | 4 |
Delivery Type | Lecture |
CRN | 45320 |
Acknowledgement of Territories
The British Columbia Institute of Technology acknowledges that our campuses are located on the unceded traditional territories of the Coast Salish Nations of Sḵwx̱wú7mesh (Squamish), səl̓ilwətaɁɬ (Tsleil-Waututh), and xwməθkwəy̓əm (Musqueam).
Instructor Details
Name | Carly Orr |
---|---|
Carly_Wong_Orr@bcit.ca | |
Location | SW2-319 |
Office Hours | Will be posted on the door; SW2-319; 604-432-8866 |
Course Description
Students learn to work in a collaborative environment and complete a small-scale software project: a web app. Design and managing of implementation concepts will be introduced: User Experience Design (XSD) and Agile methodology. The course takes students through the UX design process which includes creating and administering surveys & interviews, creating personas and user stories, designing wireframes, and performing user tests with a developed implementation that is based on the UX design process. Students will use the Agile methodology to manage the software process. Software management workflow also includes using version control, version control basics, utilizing web technologies (JavaScript, CSS, HTML, data persistence via NoSQL data technologies). Some of the JavaScript topics include DOM manipulation, event handling, web storage, AJAX calls and using JQuery in order to create a rich web app.
Course Learning Outcomes/Competencies
Upon successful completion of this course, the student will be able to:
- Describe how to work effectively within a collaborative environment.
- Demonstrate usage of a version control system (such as Git) at the terminal/console level to manage versions and components of an application.
- Explain the relationship between User Experience (UX) and the Agile Software Methodology and how they complement each other
- Demonstrate Agile methodology process such as project task breakdown, prioritization, progress tracking, and calculating velocity — within each iteration
- Demonstrate User Centred Design (UCD), utilizing personas, conducting surveys and interviews, creating user stories, performing user testing all within the context of UX Design.
- Design for a "mobile first" UI and utilize current UI mobile design patterns
- Design front-end logic utilizing JavaScript and JQuery, HTML5, and CSS
- Create our own JavaScript objects with their own properties and methods.
- Write DOM scripting using W3C standard methods and objects such as "createElement".
- Use the Constructor and the Prototype patterns to create objects.
- Utilize a NoSQL data technology for data persistence (such as MongoDB).
Learning Resources
https://developer.mozilla.org/en-US/docs/Learn/JavaScript
https://firebase.google.com/docs/
https://git-scm.com/book/en/v2
https://guides.github.com
https://www.figma.com/resources
https://support.proto.io/hc/en-us/articles/221499147-Step-by-step-Tutorial-Getting-Started
Evaluation Criteria
Criteria | % | Comments |
Quizzes (Individual) | 20 | |
Individual Assignments (Individual) | 25 | |
Team Assignments (Team) | 25 | |
Presentations (Team) | 10 | |
Final Project (Team) | 20 |
Note: Students must pass the individual components added together, in order to pass the entire course.
Attendance Requirements
Regular attendance in lectures, seminars, and labs is seen as critical to student success, and may be monitored by faculty.
Unapproved absence of 2 or more classes may result in failure or forced withdrawal from the course or program.
Please see Policy 5101 - Student Regulations: https://www.bcit.ca/files/pdf/policies/5101.pdf
Course topics
Week |
Week of ... |
Topics Covered (in conjunction with project development) |
Project Development Phase |
||
1 |
Sept 02 |
Intro to the course, technical setup at BCIT, Design fundamentals |
UI/UX design |
||
2 |
Sept 09 |
Good design vs bad design, heuristics |
UI/UX design |
||
3 |
Sept 16 |
Persona, Day in the Life, Empathy Maps |
Design Prototype |
||
4 |
Sept 23 |
Mobile-first design |
Project pitch |
||
5 |
Sept 30 |
Command-line |
Early Digital Prototype and Project Planning |
||
6 |
Oct 07 |
Version control, Git |
Early Digital Prototype |
||
7 |
Oct 14 |
Agile task management |
Early Digital Prototype |
||
8 |
Oct 21 |
Midterm – No class |
|||
9 |
Oct 28 |
Responsive design |
Continue digital prototype |
||
10 |
Nov 04 |
|
Continue digital prototype |
||
11 |
Nov 11 |
JSON structure, Javascript tips |
Sprint1 |
||
12 |
Nov 18 |
Testing; Authentication |
Sprint2 |
||
13 |
Nov 25 |
Hosting |
Sprint3 |
||
14 |
Dec 02 |
Presentation; Peer feedback |
Final Delivery / Handover |
||
15 |
Dec 09 |
Final exam week – No class |
BCIT Policy
The following statements are in accordance with the BCIT Policies 5101, 5102, 5104, and 7507, and their accompanying procedures. To review these policies and procedures please click on the links below.
Attendance/Illness:
In case of illness or other unavoidable cause of absence, the student must communicate as soon as possible with his/her instructor or Program Head or Chief Instructor, indicating the reason for the absence. Students who are seeking accommodation for a medical absence must have a BCIT approved medical certificate submitted to the department, substantiating the reason for absence. For other absences, the student should be prepared to provide appropriate supporting documentation. Unapproved absence in excess of the prescribed regulations within this outline may result in failure or forced withdrawal from the course or program. Please see Policy 5101 - Student Regulations, and accompanying procedures.
Academic Integrity:
Violation of academic integrity, including plagiarism, dishonesty in assignments, examinations, or other academic performances are prohibited and will be handled in accordance with Policy 5104 - Academic Integrity and Appeals, and accompanying procedures.
Accommodation:
Any student who may require accommodation from BCIT because of a physical or mental disability should refer to BCIT's Policy on Accommodation for Students with Disabilities (Policy #4501), and contact BCIT's Accessibility Services (SW1 2360, 604-451-6963) at the earliest possible time. Requests for accommodation must be made to Accessibility Services, and should not be made to a course instructor or Program area.
Any student who needs special assistance in the event of a medical emergency or building evacuation (either because of a disability or for any other reason) should promptly inform their course instructor(s) and Accessibility Services of their personal circumstances.
Human Rights, Harassment and Discrimination:
The BCIT community is made up of individuals from every ability, background, experience and identity, each contributing uniquely to the richness and diversity of the BCIT community as a whole. In recognition of this, and the intrinsic value of our diversity, BCIT seeks to foster a climate of collaboration, understanding and mutual respect between all members of the community and ensure an inclusive accessible working and learning environment where everyone can succeed.
Campus Mediation Services is a supportive resource for both students and employees of BCIT, to foster a respectful learning and working environment. Any student who feels that they are experiencing discrimination or harassment (personal or human rights-related) can confidentially access this resource for advice and support. Please see Policy 7507 – Harassment and Discrimination and accompanying procedure.
Students should make themselves aware of additional Education, Administration, Safety and other BCIT policies listed at https://www.bcit.ca/about/administration/policies.shtml
Guidelines for School of Computing and Academic Studies
Attempts:
Students must successfully complete a course within a maximum of three (3) attempts at the course. Students with two attempts in a single course will be allowed to repeat the course only upon special written permission from the Associate Dean. Students who have not successfully completed a course within three attempts will not be eligible to graduate from their respective program.
Approved
I verify that the content of this course outline is current.
Carly Orr, Instructor
September 02, 2019
I verify that this course outline has been reviewed.
D'Arcy Smith, Program Head
September 03, 2019
I verify that this course outline has been reviewed and complies with BCIT policy.
Aaron Hunter, Acting Associate Dean
September 03, 2019
Note: Students will be given reasonable notice if changes are required to the content of this course outline.
*Course hours and credits are calculated per Policy 5012 and the associated procedure.
Total hours – Example of 3 credit lecture/lab course:
- Full-time course: 45 hours of scheduled learning
- Flexible Learning course: 36 hours of scheduled learning plus 9 hours of independent (non-scheduled, non-instructional) learning