KEMBAR78
CAP805 Addendum | PDF | Databases | World Wide Web
0% found this document useful (0 votes)
29 views5 pages

CAP805 Addendum

Uploaded by

Angela Guo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
29 views5 pages

CAP805 Addendum

Uploaded by

Angela Guo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Course Addendum

Semester: Summer 2023 Subject Code: CAP805 Section: NAA


Subject Title: Capstone Project
Professor: Clint MacDonald Office:
E-mail: clint.macdonald@senecacollege.ca
Office Hours: By Appointment ONLINE

Approved by:
Kathy Dumanski, Chair, School of Software Design and Data Science

Please read this addendum to the general course outline carefully. It is your guide to the course
requirements and activities. Please refer to the course outline for learning outcomes, course
description and text and materials. Please also visit sdds.senecacollege.ca for key information on
courses, graduation requirements, transfer credit, and more from the School of Software Design and
Data Science.

Assessment Summary

Labs (5 individual labs) – 25%


Group Project (min 4 milestones) – 65%
In-Progress Work (4 IP @ 2.5% each) – 10%

Recommended Books
 Systems analysis and design, an object-oriented approach with UML, 5th Edition,
By: Dennis, Wixom, and Tegarden, Wiley, 978-1-118-80467-4
 24 deadly sins of software security, Programming Flaws and How To Fix Them,
By: Howard, LeBlanc, and Viega, 978-0-07-162676-7
 Testing Computer Software, by Cem Kaner, Jack Falk, Hung Quoc, Nguyen. ISBN: 0-471-
35846-0

Promotion Policy
 Have a grade of 50% or better on Group Project,
 Have an average of 50% or better on individual assignments,
 Have a grade of 50% or better on the overall course,
 Successfully completed the final presentation as part of a group

Academic Policies:
http://www.senecacollege.ca/about/policies/academics-and-student-services.html
Most of the materials posted in this course are protected by copyright. It is a violation of Canada's Copyright
Act and Seneca's Copyright Policy to share, post, and/or upload course material in part or in whole without
the permission of the copyright owner. This includes posting materials to third-party file-sharing sites such as
assignment-sharing or homework help sites. Course material includes teaching material, assignment
questions, tests, and presentations created by faculty, other members of the Seneca community, or other
copyright owners.

It is also prohibited to reproduce or post to a third-party commercial website work that is either your own work
or the work of someone else, including (but not limited to) assignments, tests, exams, group work projects, etc.
This explicit or implied intent to help others may constitute a violation of Seneca’s Academic Integrity
Policy and potentially involve such violations as cheating, plagiarism, contract cheating, etc.

These prohibitions remain in effect both during a student’s enrollment at the college as well as withdrawal or
graduation from Seneca.

PLEASE RETAIN THIS DOCUMENT FOR FUTURE EDUCATIONAL AND/OR EMPLOYMENT


USE.
TENTATIVE WEEKLY SCHEDULE
Semester Year

Week Topics Reading Assessments Weight


Provided PPTs
Introduction to the Course and a
Roadmap to successful completion Provided Handouts – project
ideas
Review of: the SDLC, UML and
IP 1: Team Formation,
Week UML diagrams, Roles in Software
Group Work Contract Team Contract, Project 2.5%
1 Teams, Collaboration Tools (MS
Selection
Teams / Task Management /
Various provided Web Links
BugTrackers), Terms and
(TBD)
Definitions
Dennis Chapter 1
Provided PPTs
Planning and Analysis stage of the Handout – Function vs. Non-
SDLC Functional Requirements
 System Request, Scope Provided URL: Scope Lab 1 - Functional / Non-
Week  Function/Non-Function Creep(TBD) Functional Requirements 5%
2 Requirements, Survey Questions
 Scope Determination and Provided Web Resource Links –
Statement Mockups and WireFrames
 GUI Wireframe Mockups http://Draw.io
(Software Usage)
Dennis Chapter 3

Analysis Continued Provided PPTs


Project Phase I - System
 Feasibility (Technical, Financial, Dennis Chapter 2, 4 Request, Requirements
Week etc) Definition/Scope – with
15%
3  Modelling Use Case Use Case Scenarios,
Scenarios/Diagrams Activity Diagrams, and
 Use Case Documentation Screen Mockups
 Activity Diagrams (UML)
System Architecture (Servers, MVC, Provided PPTs
Cloud Computing)
Dennis Chapter 5, 6 Lab 2 – Project
 The role of the database in the Management Software
Week architecture 5%
4 JIRA Implementation for
 Software Development Your Group
Methodologies
 Team Development Tools
 The development Environment
Provided PPTs

Provided Web Resources


Task, Issue and Bug Tracking
Software
How to Use Jira | Official Buyer &
Week  JIRA User Guide (atlassian.com) IP 2 – Testing Cases and
2.5%
5  Integrated Development Use Case Scenarios
Environments (IDE) https://www.guru99.com/jira-
 Source Control (Git/GitHub) tutorial-a-complete-guide-for-
beginners.html
Database Integration Provided PPTs
 Role of the database https://www.guru99.com/jenkin-
 System Architecture Involving a Lab 3 - Install and setup
database continuous-integration.html
Week the database, connections
 Relational and Non-Relational from software, and display
6 databases 5%
data on website
 Cloud (Azure) vs Server based
database
 Scaffolding and Code
Generation
Provided PPTs Project Phase II –
Website Screens Created
Provided Links to Web with Navigation and
Resources from various providers Launched live to web
Week Coding with Database (TBD) 15%
7 Connections server (Heroku) through
source control (GitHub),
and the database setup
with test data inserted

READING WEEK

Provided PPTs
Coding with Database Connections
Continued Static Code Analysis Control |
Week OWASP Foundation 10%
8 Continuous Integration
 Jenkins Source Code Analysis Tools |
 GitLab OWASP

Automated Building Provided PPTs


 Automated Scripted (ANT / Provided Online Resources Lab 4 – Continuous
Week NANT) (TBD) 5%
9 Integration
 Build Server
 Simulated Production
Environment
Testing Provided PPTs
IP 3 - Test Cases 2.5%
Week  testing plan Kaner, Chapters 1-3
10 Derivation and Coding 5%
 test cases
Dennis, Chapter 12
 testing tools overview
Provided PPTs Project Phase III -
Week Automated Test and Build 15%
Test Automation Provided Online Resources
11 setup
(TBD)

Software Security and Provided PPTs


Vulnerabilities
Week https://owasp.org/www-project- Lab 5 - Software
5%
12  Top vulnerabilities top-ten/ Vulnerability Research
 How to code them and code
Howard, Chapters 1-2
against them
Week Testing for Vulnerabilities Provided PPTs IP 4 – Individual 2.5%
13 Review/Reflection of the
https://owasp.org/www-project- software development
top-ten/ process and how we have
Howard, Chapters 1-2 implemented it and other
technologies that we have
not covered.
Project Phase V - Final
15%
Week Submission
Project Presentation and Wrap-up
14 5%
Project Presentation

Summary:
Labs (5 labs) – 25% (5% each)
Project Phase 1 – 15%
Project Phase 2 – 15%
Project Phase 3 – 15%
Project Phase 4 – 15%
Project Presentation – 5%
In-Progress (4) – 10% (2.5% each)

PLEASE RETAIN THIS DOCUMENT FOR FUTURE EDUCATIONAL AND/OR EMPLOYMENT USE.

You might also like