CS360 - general

Course Outline Spring 2026

2026-01-19T00:00:00+05:00

Dr. Suleman Shahid and Dr. Abdul Ali Bangash, Department of Computing Science, LUMS (2026). Dr. Hazel Campbell, Department of Computing Science, University of Alberta (2019, 2023, 2024). Dr. Abram Hindle, Department of Computing Science, University of Alberta (2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023). Alexander Wong, 2019. status: published summary: Lecture, Labs, Contact Information, Lecturer, Teaching Assistants, Course Content, Course Description, Prerequisites, Objectives and Learning Outcomes, Course Topics, Learning Resources, Course Schedule, Required Textbook and/or Other Major Course Materials, Recommended or Optional Learning Resources, Course Fees, On-Line Homework Disclaimer, Academic Success Centre, Faculty of Science Student Services, Grade Evaluation, Letter Grades, Statement of Expectations for AI Use, Re-Evaluation of Term Work, Re-examination, Past or Representative Evaluative Material, Labs, Participation, Policies for Late and Missed Work, Late Policy, Non-medical Protected Grounds, Missed Term Work: Assignments, Labs, Quizzes, Project Parts, Midterm Exams, Missed Term Work: Participation, Deferred Final Examination, Required Technology, Labs Assignments and Project, Lecture Participation, Remote Delivery Considerations, Technology Requirements, Recordings of Synchronous Activities, Home-Based Lab Activities, Student Resources for Remote Learning, Student Responsibilities, Academic Integrity and Student Conduct, Contract Cheating and Misuse of University Academic Materials or Other Assets, Contract Cheating: CS Courses, Academic Integrity Issues Related to Minor Formative Assessments, Appropriate Collaboration, Citation, Solo Effort: Participation Exercises, Quizzes, Exams, Confidential: Exams, Consultation: Assignments, Labs, Teamwork: Group Projects, Intellectual Violence, Exam Conduct, Lecture Conduct, Students Eligible for Accessibility-Related Accommodations, Recording and/or Distribution of Course Materials, On-Campus Computer Labs, Recording and/or Distribution of Course Materials, Learning and Working Environment, Feeling Stressed, Anxious, or Upset?, Student Self-Care Guide, Land Acknowledgement, Administrative, Policy about Course Outlines, Disclaimer, Update History, Copyright

Course Instructors
Lecture Information
Labs: Online 6:15pm to 8:30pm Wed/Thur

CS360: Software Engineering
Spring 2026

Course Instructors

Dr. Abdul Ali Bangash

Email: abdulali@lums.edu.pk
Office: 9-G20A
Office Hours: TBA

Dr. Suleman Shahid

Email: suleman.shahid@lums.edu.pk
Office: 9-G46A
Office Hours: TBA

Safa Salam

Email: safa.salam@lums.edu.pk
Office: 9-G48
Office Hours: Mon/Wed 10-12pm Fri 3-5PM

Lecture Information

Lecture Room: SDSB B3
Lecture Time: Tuesday & Thursday, 01:00 PM – 02:15 PM

Teaching Assistant(s): Available on LMS

Labs: Online 6:15pm to 8:30pm Wed/Thur

COURSE CONTENT

Calendar Description:
As an introduction to software engineering, this course is about building software effectively. You will apply good practices, effective design techniques, and development tools within a team project to create an application with a graphical user interface.

The focus is largely practical, with broad coverage in topics such as: object-oriented design, user interfaces, unit testing, design patterns, and refactoring.

Communication skills, team dynamics, working with a "customer", and creativity are also important factors in the course project. The knowledge, skills, and experience you gain will be invaluable in your future software development projects.

Course Objectives and Expected Learning Outcomes:
We will learn about applying software engineering concepts to design and implement interactive applications.

One effective way to build such applications is to apply object-oriented design and use software components. To be useful to end users, the design of these applications must also be guided by usability principles. The course involves a team project in building a well-designed Java/Android application with a sophisticated graphical user interface.

By the end of this course, you will have a strong background in basic software engineering concepts. Also, you will have the skills to implement interactive applications in Android. You will learn to propose and think critically about software and user interface designs.

Students are expected to participate in all classes and labs.

LEARNING RESOURCES

Required Course Materials:
This course does not have a required textbook. There are a number of excellent resources for this course, available as electronic books or through open access on the Web. See the course LMS for links.

Images reproduced in lecture slides have been included under section 29 of the Copyright Act, as fair dealing for research, private study, criticism, or review. Further distribution or uses may infringe copyright on these images.

In addition to fair dealing, the Copyright Act specifically exempts projected displays by educational institutions for the purposes of education or training on the premises of the education institution.

You may assume that any code examples we provide to you are public domain and free for you to take without attribution, unless they are licensed.

Recommended or Optional Learning Resources:
See the resources page on the course webpage.

Course Schedule & Assigned Readings:
See the online live schedule here: https://docs.google.com/spreadsheets/d/1WXOvrmoseOKpqhYd16F1AkesHH3Ew_GlPVFuwbTS_4Y/edit?usp=sharing

Other Course Fees:
Students will be required to use the online service Firebase in order to complete the coursework and course project. The expected fees are $0, however, Firebase may assess fees if storage, bandwidth, user, or operation limits are exceeded. One member of the group will be required to supply payment information. It is the responsibility of the student to pay for any Firebase charges. If you are unable to pay these fees, you must contact your TA and instructor immediately.

On-Line Homework Disclaimer:

Online homework is a component of this course and is provided by a third-party company. Please be aware that this company will be storing assessment information that may be associated with you. As a way to protect your personal information, you may be assigned a random ID to enter into the system. Only the random ID, performance on the online homework, and the affiliation to the LUMS for this random ID will be conveyed to the company. You are not required to provide any additional personal information to this company. If you have concerns about this, please contact the instructor of the course.
Firebase (Google) - See "Course Fees" above.
Registration in the system and any monetary transactions are of your own accord and not the responsibility of the University.
Students should be mindful of protecting their personal information and should be aware of how their personal information might be used and/or shared.
Students MUST NOT use their LUMS email to register into the system and instead should use a non-identifying email address or account.

REMOTE DELIVERY CONSIDERATIONS

Hybrid Synchronous Delivery:
There are no online lectures or recorded lectures. Lectures are in person.

GRADE EVALUATION

Assessment	Weight	Collaboration Policy	Date
Participation	8%	Solo Effort	Most Lectures
Labs	5%	Consultation	Tuesdays 5:00pm
Assignment 0	1%	Consultation	~ Week 3 - 2026-02-05 5pm
Project Part 0	1%	Teamwork	~ Week 3 - 2026-02-05 5pm
Assignment 1	8%	Consultation	~ Week 5 - 2026-02-17 5pm
Project Part 1	1%	Teamwork	~ Week 5 - 2026-02-16 5pm
Project Part 2	5%	Teamwork	~ Week 8 - 2026-03-10 5pm
Project Part 3	10%	Teamwork	~ Week 10 - 2026-03-26 5pm
Project Part 4	16%	Teamwork	~ Week 14 - 2026-04-19 5pm
Midterms	45%	Confidential	MT1 - 20% - 2026-03-12 MT2 - 25% - 2026-04-23

Grades are unofficial until approved by the Department and/or Faculty offering the course.

Midterm Dates

50 minute exams at:

Midterm 1
- March 12, 2026
Midterm 2
- April 23, 2026

Re-examination:
There is no possibility of a re-examination in this course.

Course Grades Obtained by Undergraduate Students:
This table reflects the GPA Point Value and Descriptor (e.g., Excellent, Good) for each Letter Grade.

Descriptor	Letter Grade	Grade Point Value
Excellent	A+	4.0
Excellent	A	4.0
Excellent	A-	3.7
Good	B+	3.3
Good	B	3.0
Good	B-	2.7
Satisfactory	C+	2.3
Satisfactory	C	2.0
Satisfactory	C-	1.7
Poor	D+	1.3
Minimal Pass	D	1.0
Failure	F or F4	0.0

Note: F4 denotes eligibility of a student to apply for a re-examination in a course.

Course Grades Obtained by Graduate Students:
This table reflects the GPA Point Value and Descriptor (e.g., Excellent, Good) for each Letter Grade.

Descriptor	Letter Grade	Grade Point Value
Excellent	A+	4.0
Excellent	A	4.0
Excellent	A-	3.7
Good	B+	3.3
Good	B	3.0
Satisfactory	B-	2.7
Satisfactory	C+	2.3
Failure	C	2.0
Failure	C-	1.7
Failure	D+	1.3
Failure	D	1.0
Failure	F	0.0

Statement of Expectations for AI Use:
You MUST not submit work by LLMs as your own, that is plagiarism. This also applies to other "AI" and Generative Models: ChatGPT, Lex, Page, DALL-E2, Google BARD/Gemini, Microsoft Bing/Copilot, and others. If you use LLMs you must cite it. This includes the corporation that made the AI, the AI, Subject, and Date. For example:

// The following function is from Microsoft, Copilot, "How do I write a merge sort in JavaScript?", 2023-08-31

function mergeSort(array) {

If you use LLMs you must cite it, but it's probably better to Google what it tells you and find a real citation because:

LLMs like ChatGPT are wrong a lot. It does not understand computer science. It understands how to form sentences and paragraphs well enough to be convincing, but it doesn't actually understand what anything it is saying means. When it has the choice between two answers, with opposite meanings, it will pick the answer that looks more like things it has seen before, not the answer that is more correct. This means you need to double-check that what it tells you is actually correct.

StackOverflow is always a better resource than Large Language Models such as ChatGPT, Copilot, Bard/Gemini, etc., but of course if you use code from StackOverflow or any other website, you must cite it. This is because other human programmers will usually check and downvote, remove, or fix bad information on StackOverflow. No one is checking the output of LLMs: if an LLM lies to you, no one will ever know.

ChatGPT and similar services are recording everything you tell it, and tracking you. Using ChatGPT/Bing/Bard etc. they are recording everything you say and how the LLM responds to you. There is no privacy.

ChatGPT example from another course:
Me: "What is the difference between the b and j pseudoinstruction in RISC-V?"
ChatGPT: "... The b instruction is actually a shorthand for the more general beq (branch if equal) instruction, which compares two registers and branches if they are equal. However, > > in the case of b, one of the registers is always x0 (the zero register), so the comparison > is always false, effectively causing an unconditional jump. ...the key difference between b > and j is that b is a relative branch instruction that jumps to a location within a limited range, while j is an absolute jump instruction that can jump to any address within the range of the program counter."
There are 3 problems with this answer:
b is not shorthand for beq: RARS replaces it with jal -- the actual replacement depends on the assembler used and the situation it is used in.
This also makes ChatGPT's conclusion about relative limited range jumps and absolute jumps wrong. All jumps and branches in RISC-V are relative, short range jumps except jalr. RARS also (at least in every case I've seen) translates j to jal, not jalr, and jal is also a short-range, relative jump.
If b gets translated to beq x0, Y, label then what guarantees that the other register isn't also zero? The comparison with beq x0, Y cannot always be false, despite what ChatGPT claimed. This really doesn't make any sense. It would make more sense for it to be translated to bne x0, x0, label ... but that's the opposite instruction of what ChatGPT claimed.

Re-evaluation of Term Work:
Any questions or concerns about marks on a particular assignment must be brought to the attention of the instructor (not a TA) within 7 calendar days of its return date. After that, we will not consider remarking or re-evaluating the work. So do not expect anyone to re-evaluate all the work you did all term long in the hopes of getting a higher final grade.

However, clerical errors such as incorrectly computing or recording a mark may be raised at any time prior to 2 business days following the final exam. It is the student's responsibility to confirm that their term work has been recorded properly.

POLICIES FOR LATE AND MISSED WORK

Late Policies:

Missed Term Work/Final Exam Due to Non-medical Protected Grounds (e.g., religious beliefs):
When a term assessment or final exam presents a conflict based on non-medical protected grounds, students must apply for a petition from OSA. Students can review their eligibility and choose the application process specific for Accommodations Based on Non-medical Protected Grounds.

It is imperative that students review the dates of all course assessments upon receipt of the course syllabus, and apply AS SOON AS POSSIBLE to ensure the timely application of the accommodation. Students who apply later in the term may experience unavoidable delays in the processing of the application, which can affect the accommodation.

Missed Labs:
Labs are due Friday at 5PM on the same week the lab was presented. Project meetings are due at the time of the meeting, and they are included in the lab mark. Failure to attend and actively participate in project meetings will result in a lab mark of zero.

The 2 lowest marks for Labs (including project meetings) will be dropped when calculating the course mark. No late labs will be accepted. Failure to complete a lab (or to attend a project meeting) on time for any reason will result in a mark of zero. Please note that you can miss 2 labs (or project meetings) without penalty.

Missed Lecture Participation:
Participation exercises will be available at most lectures.

The 6 lowest marks for lecture participation will be dropped when calculating the course mark. No late participation will be accepted. Failure to complete a participation exercise on time for any reason will result in a mark of zero. Please note that you can miss 6 lectures without penalty.

Missed Assignments, Project Parts, Quizzes, Midterm Exams:
A student who cannot complete an assignment, project part, quiz, or midterm exam, due to incapacitating illness, severe domestic affliction or other compelling reasons must contact the instructor within two business days of missing the assessment, or as soon as possible, to request an excused absence using the absence form. If an excused absence is granted, then the deliverable weight will be split and shared over other deliverables in the same category. If a Midterm exam is missed, then its weight will be split and shared over the other Midterm exams. An excused absence is a privilege and not a right. There is no guarantee that an absence will be excused. Misrepresentation of facts to gain an excused absence is a serious breach of the Student Academic Integrity Policy. In all cases, instructors may request adequate documentation to substantiate the reason for the absence at their discretion.

Failure to complete an assignment or contribute to a project part without an excused absence will result in a raw score of zero or a proportional score reduction.

Additional information regarding missed Midterm Exams: If Midterm 3 is missed, then it will be replaced by a deferred exam that will include an oral examination component. The time of this deferred + oral exam will be determined individually between student and instructor.

STUDENT RESPONSIBILITIES

Academic Integrity and Student Conduct:
LUMS is committed to the highest standards of academic integrity and honesty, as well as maintaining a learning environment that fosters the safety, security, and inherent dignity of each member of the community, ensuring students conduct themselves accordingly. Students are expected to be familiar with the standards of academic honesty and appropriate student conduct, and to uphold the policies of the University in this respect.

Students are particularly urged to familiarize themselves with the academic policy, and avoid any behaviour that could potentially result in suspicions of academic misconduct (e.g., cheating, plagiarism, misrepresentation of facts, participation in an offence) and non-academic misconduct (e.g., discrimination, harassment, physical assault). Academic and non-academic misconduct are taken very seriously and can result in suspension or expulsion from the University.

All forms of academic dishonesty are unacceptable at the University. Unfamiliarity of the rules, procrastination or personal pressures are not acceptable excuses for committing an offence. Listen to your instructor, be a good person, ask for help when you need it, and do your own work -- this will lead you toward a path to success. Any academic integrity concern in this course will be reported to the College of Natural and Applied Sciences.

"Integrity is doing the right thing, even when no one is watching" -- C.S. Lewis

Contract Cheating and Misuse of University Academic Materials or Other Assets:
Contract cheating describes the form of academic dishonesty where students get academic work completed on their behalf, which they submit for academic credit as if they had created it themselves. Contract cheating may or may not involve the payment of a fee to a third party, who then creates the work for the student.

Examples include:

Getting someone to write an essay or research paper for you.
Getting someone to complete your assignment or exam for you.
Posting an essay, assignment, or exam question to a tutorial or study website; the question is answered by a "content expert", then you copy it and submit it as your own answer.
Posting your solutions to a tutorial/study website, public server, or group chat and/or copying solutions that were posted to a tutorial/study website, public server, or group chat.
Sharing your login credentials to the course management system (e.g., Canvas) and allowing someone else to complete your assignment or exam remotely.
Using an artificial intelligence bot or text generator tool to complete your essay, research paper, assignment, or exam solutions for you (without the instructor's permission).
Using an online grammar checker to "fix" your essay, research paper, assignment, or exam solutions for you (without the instructor's permission).

Contract cheating companies thrive on making students believe that they cannot succeed without their help; they attempt to convince students that cheating is the only way to succeed.

Uploading the instructor's teaching materials (e.g., course outlines, lecture slides, assignment, or exam questions, etc.) to tutorial, study, or note-sharing websites or public servers is a copyright infringement and constitutes the misuse of University academic materials or other assets. Receiving assignment solutions or answers to exam questions from an unauthorized source puts you at risk of receiving inaccurate information.

Receiving assignment solutions or answers to exam questions from an unauthorized source puts you at risk of receiving inaccurate information.

Additional Examples of Contract Cheating:

Logging in as someone else Sharing your login credentials Sharing your anonymous ID Using someone else's anonymous ID Allowing someone else to log in as you Representing yourself as someone else Having someone else represent themselves as you	On other LUMS services and linked services: Zoom gmail Google Chat, Drive, ... Lab computers Wi-Fi ... On an external service, website, or app: repository hosting services: GitHub, GitHub Classroom, Bitbucket, GitLab, ... live quiz services: Mentimeter, ... Textbook websites/apps KnowledgeTree/MasteryGrids online tutorials online practice systems online homework systems

Misrepresenting authorship to a version control system such as git:
Forging git commit metadata (author, time, etc.)
Creating git commits where the author recorded did not create the changes being committed.
...
Submitting participation exercises for someone else.
Representing yourself as someone else, or having someone else represent themselves as you to an instructor, TA, or other LUMS employee.
Attending a lecture/lab/seminar for someone else.
Having someone else attend a lecture/lab/seminar for you.

Appropriate Collaboration:
Students need to be able to recognize when they have crossed the line between appropriate collaboration and inappropriate collaboration. If students are unsure, they need to ask instructors to clarify what is allowed and what is not allowed.

Here are some tips to avoid copying on assessments:

Do not write down something that you cannot explain to your instructor.
When you are helping other students, avoid showing them your work directly. Instead, explain your solution verbally. Allowing your work to be copied is also considered inappropriate collaboration.
It is also possible that verbally discussing the solution in too much detail may result in written responses that are too similar. Try to keep discussions at a general or higher level.
If you find yourself reading another student's solution, do not write anything down. Once you understand how to solve the problem, remove the other person's work from your sight and then write up the solution to the question yourself. Looking back and forth between someone else's paper and your own paper is almost certainly copying and considered inappropriate collaboration.
If the instructor or TA writes down part of a solution in order to help explain it to you or the class, you cannot copy it and hand it in for credit. Treat it the same way you would treat another student's work with respect to copying, that is, remove the explanation from your sight and then write up the solution yourself.
There is often more than one way to solve a problem. Choose the method that makes the most sense to you rather than the method that other students happen to use. If none of the ideas in your solution are your own, there is a good chance it will be flagged as copying.

For programming assignments, powerful software tools are used to detect plagiarism. When the software tools indicate that there is similarity between two submissions, the submissions are reviewed by the instructor or teaching assistant. If the possibility that the standards for academic honesty were violated is confirmed, an investigation is started. Eventually the submitted solutions may be forwarded to the Faculty of Science Associate Dean of Students for further investigation and eventual sanctions.

Each student must be able to verbally describe their exam answers and code, line by line, to a professor or TA, if asked to do so. Your mark may be reduced if you aren't able to explain your own work satisfactorily.
For some substantial programming assignments and homework questions, students may discuss the concepts covered by the assignment with other students registered in the course as long as they do not share actual solutions or programming code.
All suspected cases of plagiarism will be forwarded to the Dean's office and thoroughly investigated. Receiving a low mark for work not completed is a far superior alternative to this process and its possible long-term consequences for your career.

All suspected cases of plagiarism and other forms of cheating are immediately referred to the Disciplinary Committee. Please do not put yourself or us into such an unpleasant situation.

Citations:
If you include code or ideas from someone who isn't you (including from a Generative AI or LLM) you must cite it. Here are examples of an appropriate citation:

// The following function is from Microsoft, Copilot, "How do I write a merge sort in JavaScript?", 2023-08-31

function mergeSort(array) {

To cite something written by an entity such as a real person you must include the name of the author, the name of the resource, directions to the resource (like a URL).

/* This function was made by Gerald <gerald@example.com> in lib/X.c at https://example/libX/src/lib/X.c 2015 */

void scrambleEggs() {

Stackoverflow recommends you cite the author, the license, the title of the question, the url to the answer.

/* 
   Author: Felix Too https://stackoverflow.com/users/4083076/felix-too
   Title: "Failed to install the following Android SDK packages as some licences have not been accepted" error
   Answer: https://stackoverflow.com/a/55641042
   Date: 2019-04-11
   License: CC-BY-SA 4.0 (International)
*/

Collaboration policy definitions:
The following are definitions for the different collaboration policies used in this course

Solo Effort:
Participation exercises fall under the department's Solo Effort model unless announced by the instructor. Solo Effort must be completed by the student registered in the course without external assistance from any individual or organization.

Students may only submit work authored by themselves.
Students may not discuss or exchange solutions, steps, strategies, code, links, code, images, videos, output, comments, repositories, answers, etc.
Students may not consult with other students on how to solve the problem, unlike the consultation model described below.
Students may not submit a participation exercise, quiz, or exam without attending the relevant lecture, lab, seminar, or exam.
Students may not share a participation exercise, quiz, or exam link (URL).
Students may not represent themselves as someone else, (or have someone else represent themselves as the student) during lectures, labs, seminars, or exams.
Including in-person or over Zoom, or any other remote video, voice call, chat, or email service.
See Contract Cheating above.

Confidential:
Midterms and Final Exams are also Confidential in addition to Solo Effort as listed above.

Students may not discuss the contents of the exam, except with instructors.
Students are not always able to take the exam at the same time, so do not discuss the contents of the exam even if you have already taken it!
No human, computer, electronic assistance is allowed of any sort, including AI chatbots, calculators, tutors, etc.

Consultation:
Individual assignments and labs are under the department's Consultation model. That means you may discuss the labs with others, but you must create and submit a solution that is entirely your own work. If you consult with other students, you must list their names in a comment at the top of your submission or in your repository README, along with a brief description of the part(s) of the assignment you discussed.

How to consult with other students without plagiarizing:

Study the Course, Computing Science Department, CNAS, and University policies listed above regarding Academic Integrity.
All sources used must be cited.
If you use code snippets you must cite them, please see the examples above.
All sources of information used, e.g., books, websites, students you talked to etc., must be cited in your submitted file or repo README for each assignment.
If student A cites student B, then B should also cite A as consulted.
Individually develop your own solution for assignments and exercises. Submit only your own work for evaluation.
Each student is responsible for what is handed-in and must be able to explain it.
Students may only submit work authored by themselves. Work submitted by a student that is the work of someone else (e.g. another student or a tutor) either in part or in entirety is considered plagiarism.
You can freely discuss the steps and solutions with your classmates on a conceptual verbal level.
Limit discussion to be among students taking the current course, not students who took in earlier terms or other students. Consultation is a two-way process that benefits both sides.
Do not exchange any text, code, images, videos, output, comments, repositories, or detailed (low-level) step-by-step procedures.
Do not share solutions.
Do not give other students access to your solutions and do not seek access to other's solutions. This is considered plagiarism.
Do not show your code to classmates.
Do not look at a classmate's code.

Examples of consultation:

Acceptable consultation example:
Student A has a problem with the code
Student A asks Student B for help
Student B explains the steps, concepts, or techniques they used to get their code working
Student A understands the fix
Student A can reproduce and explain the fix.
Student A submits the code
Acceptable consultation example:
Student A needs to make a grid for a board game program.
Student A asks Student B for help.
Student B explains that they "used two nested for loops, one for the vertical and one for the horizontal."
Student A implements two nested for loops using their own unique code.
Student A can use the for loops to fix similar problems, and they can explain why each piece of code is needed, along with how it works to solve the problem.
Student A submits the code
Unacceptable consultation example:
Student A needs to make a grid for a board game program.
Student A asks Student B for help.
Student B sends the code they used to make the board game grid for their solution.
Student A copies Student B's code into their own solution, changing it a little.
Student A submits the code
Unacceptable plagiarism example:
Student A has a problem with the code
Student A asks Student B for help
Student B provides Student A with the code
Student A submits the code

Teamwork:

As long as you are a part of a group, you are responsible for everything in the group project, whether you participated in every component or not.
A group may only submit work authored by group members or appropriately cited and credited code that does not violate the author's license.

Intellectual Violence:
In this course, Intellectual Violence is considered bullying. Intellectual violence is when one teammate uses their skill, knowledge, or experience, to intimidate or control the other teammate(s) rather than sharing and helping them learn. Examples of Intellectual Violence

Using complex terminology or concepts to make others feel inferior.
Dismissing or ridiculing colleagues’ ideas or contributions.
Withholding information to maintain a power imbalance.
Creating an environment where only certain knowledge or skills are valued.
Rejecting contributions without constructive feedback.
Imposing overly strict code standards.
Ignoring or delaying code reviews, pull requests, or commits.
Favouring contributions from certain team members.
Using harsh or condescending language in comments, code reviews, pull requests, issues, commit messages, etc.
Making contributors feel unwelcome.

Exam Conduct:

Some key points to be aware of:

Your student photo ID is required at exams to verify your identity.
Students must arrive at the specified time to take the exam. Once the exam has started, students must remain in the physical in-person or remote environment for at least 30 minutes. Students who arrive more than 30 minutes late for an in-person exam will not be permitted to take the exam. Students who arrive more than 30 minutes late for an online exam may have their exam attempt removed or disqualified by the instructor. In both cases, students may apply for a deferred examination.
All cell phones must be turned off and stored in your bags.

Recording and/or Distribution of Course Materials:
Audio or video recording, digital or otherwise, of lectures, labs, seminars or any other teaching environment by students is allowed only with the prior written consent of the instructor or as a part of an approved accommodation plan. Student or instructor content, digital or otherwise, created and/or used within the context of the course is to be used solely for personal study, and is not to be used or distributed for any other purpose without prior written consent from the content authors.

Disclaimer:
Any typographical errors in this syllabus are subject to change and will be announced in class and/or posted on the course website. The date of final examinations is set by the Registrar and takes precedence over the final examination date reported in the syllabus.

Copyright:

Dr. Abdul Ali Bangash, Department of Computer Science, Lahore University of Management Sciences (LUMS)(2025).
Dr. Suleman Shahid, Department of Computer Science, Lahore University of Management Sciences (LUMS)(2025).

Midterms

2025-09-09T00:00:00+05:00

The Midterm Exams consist of two exams, each with multiple questions, taking about 10-20 minutes each.

The midterm exams are closed book/closed notes. No collaboration is allowed. Solo and Confidential.No cheat sheet is allowed.

2026 Times

1.5 hr exams:

Midterm 1
- March 12, 2026
Midterm 2
- April 23, 2026

Topics

The exam topics involve everything covered or presented in class up until the day of the midterm exam.

The exam questions are very similar to our in class exercises.

Exam Practice

Later exams are more directly relevant to your midterms. Answers will not be provided, but you can post your answers for correction in the discussion forum on slack.

CS360 Course Fall 2021

2024-11-12T00:00:00+05:00

CS360 Course Outline

General Information

Term: Fall 2021 Number of credits: 3 credits

Lecture (E)A1 Date and Time: Monday-Wednesday-Friday 11:00-11:50 MT Location: CCIS L2-190

Labs start in the second week of classes.

Lab (E)D01 Date and Time: Tuesday 17:00-19:50 Location: CSC B-10

Lab (E)D03

Date and Time: Wednesday 17:00-19:50 Location: CSC B-02

Lab (E)D04

Date and Time: Thursday 17:00-19:50 Location: NRE 2-003

Overview

As an introduction to software engineering, this course is about building software effectively. You will apply good practices, effective design techniques, and development tools within a team project to create an application with a graphical user interface.

The focus is largely practical, with broad coverage in topics such as: object-oriented design, user interfaces, unit testing, design patterns, and refactoring.

Objectives

We will learn about applying software engineering concepts to design and implement interactive applications.

Students are expected to participate in all classes and labs.

Course Topics

Software engineering:

object-oriented analysis and development
Unified Modeling Language
software processes
requirements
testing
design patterns
refactoring
tools
revision control

Course Work and Evaluation

All assignments and project parts are due at 16:00 MT on the due date.

Exams are synchronized.

In the labs, the TAs will explain the submission process for lab exercises (typically online). Late submissions will not be accepted.

|-------------------------------------------------------------------------|

|Total | |100% | | |

Exams:

There is no possibility of a reexamination in this course.

The final exam is tentatively scheduled for: Monday, December 13 starting at 14:00.

You must verify the date and time on BearTracks when the final exam schedule is posted.

Grade Evaluation:

The individualized project score depends on the following main factors: how well your team did, the peer review forms of your team members, your completion of peer review forms, and the instructor and TAs' assessment of your individual contribution.

The conversion of your total numeric coursework score to a final grade will be based on interpreting the guidelines of the descriptors, letter grading system, and four-point scale as defined in the University Calendar §23.4. That is, grades are assigned on what we judge to be "failure", "minimal pass", "poor", "satisfactory", "good", or "excellent" performance in the context of the class.

We do not use a particular distribution to do the conversion, but instead use our judgement of how your score reflects mastery of the course material. That said, you generally need to be above the median to earn at least a 3.0 or B.

Course Materials

This course does not have a required textbook. There are a number of excellent resources for this course, available as electronic books or through open access on the Web. See the course eClass site for links.

Copyright regulations, however, prohibit me from distributing complete copies of the lecture slides on the course eClass site.

You may assume that any code examples we provide to you are public domain and free for you to take without attribution, unless they are licensed.

Please see the Final Exam page when posted for representative example questions.

CS360 Course Fall 2021 Old Lab Recordings

2024-11-12T00:00:00+05:00

CS360 Course Old Project Problem Descriptions

2024-11-12T00:00:00+05:00

You are to design and implement a simple, attractive, and easy-to-use Android application to satisfy the follow goals. Your design must be flexible enough to allow future developers to extend or migrate it.

To assist in meal planning, we want a mobile application that allows one to track their food storage, record their recipes, plan their meals for several days, and prepare shopping lists.

Needs in (Partial) User Story Form

User needs are expressed in the form of partial user stories: As a , I want .

These descriptions may change to correct omissions and clarify noticed issues. Talk to the customer and propose options, rather than making what might be an unwarranted assumption or interpretation.

Ingredient Storage

US 01.01.01 As a meal planner, I want to add an ingredient, with a brief description, best before date, location, amount, unit, and ingredient category.

US 01.02.01 As a meal planner, I want to view an ingredient and its details.

US 01.03.01

As a meal planner, I want to edit the details of an ingredient.

US 01.04.01 As a meal planner, I want to delete an ingredient.

US 01.05.01 As a meal planner, I want to see a list of my ingredients.

US 01.06.01 As a meal planner, I want to sort the list of ingredients by description, best before date, location, and ingredient category.

Recipes

US 02.01.01 As a meal planner, I want to add a recipe, with title, preparation time, number of servings, recipe category, comments, photograph, and list of ingredients.

US 02.02.01 As a meal planner, I want to add an ingredient to a recipe, with a brief description, amount, unit, and ingredient category.

US 02.03.01 As a meal planner, I want to delete an ingredient from a recipe.

US 02.04.01 As a meal planner, I want to view a recipe and its details.

US 02.05.01 As a meal planner, I want to edit the details of a recipe, including the ingredients.

US 02.06.01 As a meal planner, I want to delete a recipe.

US 02.07.01 As a meal planner, I want to see a list of my recipes.

US 02.08.01 As a meal planner, I want to sort the list of recipes by title, preparation time, number of servings, or recipe category.

Meal Plan

US 03.01.01 As a meal planner, I want to make a meal plan, for several upcoming days of meals, based on choosing from my recipes or individually from my ingredient storage.

US 03.02.01 As a meal planner, I want to scale my recipes to adjust the number of servings for the meal plan.

Shopping List

US 04.01.01 As a meal planner, I want to view a shopping list of ingredients that I need to buy, based on my ingredient storage and meal plan.

US 04.02.01 As a meal planner, I want each ingredient on the shopping list to show its description, amount, unit, and ingredient category.

US 04.03.01 As a meal planner, I want to sort the shopping list of ingredients by description or category.

US 04.04.01 As a meal planner, I want to note that I have picked up an ingredient on the shopping list.

US 04.05.01 As a meal planner, I want to add ingredients I have picked up to my ingredient storage, reminding me to complete details like location, actual amount, and unit.

CS360 Course Old Project Problem Descriptions Fall 2024

2024-11-12T00:00:00+05:00

Warning: This is subject to change!

QR Code Event Check-In System

You are to design and implement a simple, attractive, and easy-to-use Android application to satisfy the following goals. Your design must be flexible enough to allow developers to extend or migrate it.

Description:

Create an event management system where attendees check in using QR codes on their mobile devices. Organizers can track attendance, manage event details, and send notifications.

Features:

QR Code Scanning:

Attendees can use the app to scan event-specific QR codes for quick and seamless check-ins.

Firebase Integration:

Utilize Firebase for storing event details, attendee lists, and real-time check-in status updates.

Multi-User Interaction:

Distinguish between organizers and attendees with different app roles and permissions.

Geolocation Verification (Optional):

Optionally use geolocation to verify that attendees are physically present at the event location during check-in.

Image Upload:

Allow organizers to upload event posters and attendees to upload profile pictures for a more personalized experience.

Scenario:

Update for Project 3:

John, an event organizer, opens the QRCheckIn app for an upcoming tech conference. He generates a unique QR code for the event. Potential attendees browse the events and notice John's event, they view the event poster, and then click sign up to indicate they will attend the event as an attendee. As attendees arrive, they use the app to scan the QR code, automatically checking them into the conference. The app updates John's dashboard in real-time, showing the current attendance. John can also send push notifications to all attendees through the app.

Scenario for Project 2: John, an event organizer, opens the QRCheckIn app for an upcoming tech conference. He generates a unique QR code for the event. As attendees arrive, they use the app to scan the QR code, automatically checking them into the conference. The app updates John's dashboard in real-time, showing the current attendance. John can also send push notifications to all attendees through the app.

# Actors:

Organizer: a person who organizes the event and is in control of an event

Attendee: a person who attends the event

Administrator: the entity that is responsible for the infrastructure that the game runs on.

Glossary:

QR Code: a scannable code, either a barcode, a QR code, or other code scannable by Zebra crossing libraries or google QR code scanning libraries.

User Stories:

User needs are expressed in the form of partial user stories:

As a , I want .

These descriptions may change to correct omissions and clarify noticed issues. New requirements will be introduced for the final project part.

Organizer:

US 01.01.01 As an organizer, I want to create a new event and generate a unique QR code for attendee check-ins.

US 01.01.02 As an organizer, I want the option to reuse an existing QR code for attendee check-ins.

US 01.02.01 As an organizer, I want to view the list of attendees who have checked in to my event.

US 01.03.01 As an organizer, I want to send notifications to all attendees through the app.

US 01.04.01 As an organizer, I want to upload an event poster to provide visual information to attendees.

US 01.05.01 As an organizer, I want to track real-time attendance and receive alerts for important milestones.

US 01.06.01 As an organizer, I want to share a generator QR code image to other apps so I can email or update other documents with the QR code.

US 01.07.01 As an organizer, I want to create a new event and generate a unique promotion QR code that links to the event description and event poster in the app.

US 01.08.01 As an organizer, I want to see on a map where users are checking in from.

US 01.09.01 As an organizer, I want to see how many times an attendee has checked into an event.

[New for Part 3] US 01.10.01 As an organizer, I want to see who is signed up to attend my event.

[New for Part 3] US 01.11.01 As an organizer, I want to OPTIONALLY limit the number of attendees that can sign up for an event.

Attendee:

US 02.01.01 As an attendee, I want to quickly check into an event by scanning the provided QR code.

US 02.02.01 As an attendee, I want to upload a profile picture for a more personalized experience.

US 02.02.02 As an attendee, I want to remove profile pictures if need be.

US 02.02.03 As an attendee, I want to update information such as name, homepage, and contact information on my profile.

US 02.03.01 As an attendee, I want to receive push notifications with important updates from the event organizers.

US 02.04.01 As an attendee, I want to view event details and announcements within the app.

US 02.05.01 As an attendee, I want my profile picture to be deterministically generated from my profile name if I haven't uploaded an profile image yet.

US 02.06.01 As an attendee, I do not want to login to the app. No username, no password.

[New for Part 3] US 02.07.01 As an attendee, I want to sign up to attend an event from the event details (as in I promise to go).

[New for Part 3] US 02.08.01 As an attendee, I want to browse event posters/event details of other events.

[New for Part 3] US 02.09.01 As an attendee, I want to know what events I signed up for currently and in and in the future.

Both:

US 03.02.01 As a user, I want the option to enable or disable geolocation tracking for event verification.

Administrator:

US 04.01.01 As an administrator, I want to be able to remove events.

US 04.02.01 As an administrator, I want to be able to remove profiles.

US 04.03.01 As an administrator, I want to be able to remove images.

US 04.04.01 As an administrator, I want to be able to browse events.

US 04.05.01 As an administrator, I want to be able to browse profiles.

US 04.06.01 As an administrator, I want to be able to browse images.

[New for Part 3 stories do not need to be addressed in Part 2]

Group Assignment 5: Presentation Marking Rubric

2024-04-05T00:00:00+05:00

This is currently a copy of the 402 presentation requirements and needs to be updated for 301
Overview
Requirements
Marking
Evaluating Deliverables Based on Presentation Content

This is currently a copy of the 402 presentation requirements and needs to be updated for 301

Overview

The purpose of the presentation marking rubric is to outline precise evaluation criteria for the assessment of the group assignment 5 presentation. Its aim is to provide clear guidance to presenters, ensuring they have a thorough understanding of what is expected of them.

Requirements

Slides
- Make sure to use readable fonts.
- Use short phrases instead of paragraphs of text. Avoid crowded text-only slides.
- Use pictures, diagrams etc., whenever possible.
- Add slide numbers so that it is easy to ask questions about specific slides.
Delivering the talk
- Be positive and (pretend to be?) interested and excited.
- Speak loudly and clearly & avoid being monotonous.
- Face the audience and look at them and try to engage the audience.
- Make your talk entertaining (without overdoing it).
- Rehearse your presentation well enough that you don’t need to keep reading off your slides. If you are always reading off the slides, then the audience could simply read your slides and not listen to you at all.
- Anticipate things you need to highlight and use boxes etc to highlight them on the slides.
Present the project to the class
- Your presentation must be targeted to the audience who are in the class.
- Presentations will be done by group.
- Presentation should be about 8 minutes, no more. Try NOT to wrap up the presentation really early. You MUST finish your presentation within the time constraints so please rehearse properly. You will lose 2 marks if you run over time.
- Presentation should cover all the aspects of group assignment 5 including the five points which should be in the report.
- You can use PowerPoint or Google Slides or whatever presentation software you like.
- You will need to present in lab in person during lab time.
- All group members will have to present.
You must be able to answer questions about the presentation and your work so far
- You are expected to attend each other's presentations and ask questions.

Marking

Presentation quality is marked by the below rubric (out of 20):

Component	Excellent (5)	Good (4)	Satisfactory (3)	Unsatisfactory (2)	Poor (1)
Slides	Slides are clear, readable, and well-designed. Text is large enough to be seen from the back of the room. Figures are appropriately sized and labeled. No more than five bullet points per slide.	Slides are mostly clear, readable, and well-designed. Text is large enough to be seen from most of the room. Figures are adequately sized and labeled. No more than seven bullet points per slide.	Slides are somewhat clear, readable, and well-designed. Text is large enough to be seen from the front of the room. Figures are somewhat sized and labeled. No more than nine bullet points per slide.	Slides are unclear, unreadable, or poorly designed. Text is too small to be seen from the back of the room. Figures are too large or too small and unlabeled. More than nine bullet points per slide.	Slides are missing, illegible, or incomprehensible. Text is too small to be seen from anywhere in the room. Figures are irrelevant or absent. Too many bullet points per slide or no bullet points at all.
Organization	Presentation has a clear introduction, body, and conclusion. Transitions between slides are smooth and logical. Main points are highlighted and supported by evidence.	Presentation has an introduction, body, and conclusion. Transitions between slides are mostly smooth and logical. Main points are stated and supported by some evidence.	Presentation has an introduction, body, and conclusion. Transitions between slides are somewhat smooth and logical. Main points are mentioned and supported by weak evidence.	Presentation lacks a clear introduction, body, or conclusion. Transitions between slides are abrupt or illogical. Main points are unclear or unsupported by evidence.	Presentation has no discernible structure or flow. Transitions between slides are nonexistent or confusing. Main points are missing or irrelevant.
Demonstration of quality evaluation	Presenters demonstrate a comprehensive understanding of quality evaluation principles using SonarQube. Presenters provide a comprehensive and detailed overview of the current CI pipeline. Presenters offer insightful and well-reasoned advice on addressing current technical debt, providing clear justification and actionable recommendations. Presenters engage in a thorough and insightful discussion of metrics and tool changes, offering clear rationale and considerations for potential modifications.	Presenters demonstrate a solid understanding of quality evaluation using SonarQube, with clear explanations and examples. Presenters provide a clear and informative discussion of the current CI pipeline, covering key aspects with sufficient detail. Presenters provide solid advice on addressing current debt, supported by logical reasoning and relevant examples. Presenters provide a coherent and informative discussion of metrics and tool changes, supported by logical reasoning and relevant examples.	Presenters demonstrate a basic understanding of quality evaluation using SonarQube, but with some gaps in clarity or depth. Presenters provide an adequate overview of the current CI pipeline, though some areas may lack depth or clarity. Presenters provide basic advice on addressing current debt, though some aspects may lack depth or specificity. Presenters provide a basic overview of metrics and potential tool changes, though depth and justification may vary.	Presenters demonstrate poor understanding of quality evaluation using SonarQube, with significant gaps or inaccuracies. Presenters provide a poor or incomplete description of the current CI pipeline, with significant gaps or omissions. Presenters provide limited or unclear advice on addressing current debt, with weak reasoning or insufficient detail. Presenters offer limited or unclear insights into metrics and tool changes, with weak justification or relevance.	Presenters demonstrate little to no understanding of quality evaluation using SonarQube, with major inaccuracies or misconceptions. Presenters fail to effectively discuss the current CI pipeline, lacking coherence or relevant details. Presenters fail to provide meaningful advice on addressing current debt, lacking coherence or relevance. Presenters fail to effectively discuss metrics and tool changes, lacking coherence or substantive content.
Ability to answer questions	Presenters answer all questions from the audience correctly and confidently. Presenters provide additional information or examples when appropriate. Presenters are respectful and courteous to the questioners.	Presenters answer most questions from the audience correctly and confidently. Presenters provide some additional information or examples when appropriate. Presenters are respectful and courteous to the questioners.	Presenters answer some questions from the audience correctly and confidently. Presenters provide little additional information or examples when appropriate. Presenters are respectful and courteous to the questioners.	Presenters answer few questions from the audience correctly and confidently. Presenters provide no additional information or examples when appropriate. Presenters are disrespectful or discourteous to the questioners.	Presenters answer no questions from the audience correctly and confidently. Presenters provide irrelevant or inaccurate information or examples when appropriate. Presenters are rude or hostile to the questioners.

Evaluating Deliverables Based on Presentation Content

We will use both the content of your report and presentation to grade the 5 points from the deliverables. The weight of the content of the presentation for the main grading is given below:

Quality evaluation using SonarQube (points 1 and 2): 7.5 out of 30
Discussing current CI pipeline (point 3): 2.5 out of 10
Advice on paying back current debt (point 4): 3.75 out of 15
Discussion of metrics & tool changes (point 5): 2.5 out of 10

Total presentation content grade: 16.25 out of 70

Please note that this section is separate from the presentation marks, which will be graded out of 20 according to the rubric in the table above.

Individual

2024-03-20T00:00:00+05:00

Assignments
Late Submission Policy
Participation
- Participation Exercises are marked as follows:

Assignments

Late Submission Policy

To ensure fairness and consistency for all participants, the following late submission policy applies for all assignments:

Up to 1 hour late: 5% penalty

More than 1 hour and up to 24 hours late: 10% penalty

More than 24 hours and up to 48 hours late: 50% penalty

More than 48 hours late: Submissions will not be accepted

Late penalties are applied to the final evaluated score. Submissions are considered late based on the timestamp recorded by the submission system.

Participation

You can earn lecture participation credit by attending lecture on time and doing a lecture participation exercise. Instructions will be given during lecture.

These will be done on paper and you need to bubble in your student number.

You must provide your student number to get credit. Failure to do so will not earn credit.

For lecture participation exercises, given N total exercises only N-6 will be counted. You can miss 6. No extensions, excused absences, or weight transfers are possible. See the outline for more information.

Entering answers for someone else will be considered a violation of the SAIP.
- See the outline section on contract cheating for more information.

Participation Exercises are marked as follows:

Given N total exercises, count the number of sufficiently complete exercises (M), calculate percent exercises as 100% * M / (N - 6).

Failure 0: Write less than 50% of exercises
Unsatisfactory 4: Write more than or equal to 50% of exercises
Satisfactory 6: Write more than 60% of exercises
Good 7: Write more than 70% of exercises
Excellent 8: Write more than 80% of exercises

If you participate enough in discussion you can get 1 bonus mark to your participation grade (not exceeding 7). You only get credit for participation in your own section.

Group Project

2024-01-06T00:00:00+05:00

Project

Project

IMPORTANT NOTICE
Project meetings are mandatory for all group members.
There will be 7 scheduled throughout the semester.
Attendance will be recorded by the TA.
5% of the total project marks are strictly allocated to meeting attendance.
Failure to attend meetings will result in a direct deduction from project marks.

Labs

2024-01-06T00:00:00+05:00

Lab Schedule
Lab 1
Lab 2
Lab 3
Lab 4
Lab 5
Lab 6
Lab 7
Lab 8
Late Submission Policy
Marking
- Labs are marked as follows:

Lab Schedule

Labs will be held online on Microsoft Teams.

Ramadan Timings:
- Friday: 2:30 PM – 4:30 PM

Regular Timings:
- Wednesday: 6:15 PM – 8:30 PM
- Thursday: 6:15 PM – 8:30 PM

Students will be assigned to a specific lab group and will attend one of the above sessions, depending on their assigned group.

Lab Groups

Late Submission Policy

To ensure fairness and consistency for all participants, the following late submission policy applies for all labs:

Up to 1 hour late: 5% penalty

More than 1 hour and up to 24 hours late: 10% penalty

More than 24 hours and up to 48 hours late: 50% penalty

More than 48 hours late: Submissions will not be accepted

Late penalties are applied to the final evaluated score. Submissions are considered late based on the timestamp recorded by the submission system.

Marking

From the syllabus

Missed Labs:

Labs are due Tuesday at 5PM in the week after the lab was presented. Project meetings are due at the time of the meeting, and they are included in the lab mark. Failure to attend and actively participate in project meetings will result in a lab mark of zero.

The 2 lowest marks for Labs (including project meetings) will be dropped when calculating the course mark. No late labs will be accepted. Failure to complete a lab (or to attend a project meeting) on time for any reason will result in a mark of zero. Please note that you can miss 2 labs (or project meetings) without penalty.

Labs are marked as follows:

Given N total labs, count the number of sufficiently complete labs (M), calculate percent labs as 100% * M / (N - 2).

Failure 0: Write less than 50% of labs
Unsatisfactory 2: Write more than or equal to 50% of labs
Satisfactory 3: Write more than 60% of labs
Good 4: Write more than 70% of labs
Excellent 5: Write more than 80% of labs

You only get credit for labs in your own section.

Learning Resources & Reference Materials

2024-01-06T00:00:00+05:00

If you find broken links, please file a GitHub issue.

Readings

Course Notes

General Resources

Assignment FAQ
Exam Practice Questions
Old Participation Exercise
SPM and SDA MOOC Resources
Old Lecture and Lab Recordings
Old Lab Notes
Safari O'Reilly Books
- You must log in with the University of Alberta Library to get free access to O'Reilly books
- Also try this link
Folder icon B2 Car Example
StackOverflow

Java + UML + OO Textbooks

You already paid for these full e-textbooks with your tuition!

Java

Android Studio

Android Studio Tips

UML

MVC

Git and GitHub Resoirces

Android Activity Resources

Android Debugging Resources

Android Studio: Debug Your App

Android Student Picker Example App

An example of developing an Android app that randomly picks students in a class.
Part 1: Storyboarding
Part 2: Laying Put the User Interface Screens
Part 3: Developing and Testing the Model
Part 4: Navigating between Activities
Part 5: Controllers and Adding Students

Code Conventions Resources

Code Conventions for the Java Programming Language

Software Process

Unit Testing in Android with JUnit

Requirements

Testing

Intent Testing in Android

Design Patterns

User Interface Design

Human Error

Book: GUI Bloopers

Mentis for Review

Fall 2024 1 2 3

Slides

2024-01-06T00:00:00+05:00

Welcome
Objects UML Java
Software Process Models
Requirement Engineering
User Interface Design
Object-oriented analysis and design

CS360 - general

Course Outline Spring 2026

Course Instructors

Dr. Abdul Ali Bangash

Dr. Suleman Shahid

Safa Salam

Lecture Information

Labs: Online 6:15pm to 8:30pm Wed/Thur

Midterms

2026 Times

Topics

Exam Practice

CS360 Course Fall 2021

CS360 Course Outline

General Information

Overview

Objectives

Course Topics

Course Work and Evaluation

Exams:

Grade Evaluation:

Course Materials

CS360 Course Fall 2021 Old Lab Recordings

CS360 Course Old Project Problem Descriptions

CS360 Course Old Project Problem Descriptions Fall 2024

QR Code Event Check-In System

Description:

Features:

Scenario:

Glossary:

User Stories:

Organizer:

Attendee:

Both:

Administrator:

Group Assignment 5: Presentation Marking Rubric

This is currently a copy of the 402 presentation requirements and needs to be updated for 301

Overview

Requirements

Marking

Evaluating Deliverables Based on Presentation Content

Individual

Assignments

Late Submission Policy

Participation

Participation Exercises are marked as follows:

Group Project

Project

Labs

Lab Schedule

Lab 1

Lab 2

Lab 3

Lab 4

Lab 5

Lab 6

Lab 7

Lab 8

Late Submission Policy

Marking

Labs are marked as follows:

Learning Resources & Reference Materials

Readings

Course Notes

General Resources

Java + UML + OO Textbooks

Java

Android Studio

UML

MVC

Git and GitHub Resoirces

Android Activity Resources

Android Debugging Resources

Android Student Picker Example App

Code Conventions Resources

Software Process

Unit Testing in Android with JUnit

Requirements

Testing

Intent Testing in Android