CS360

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.

Assignment 1

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

Assignment: EmotiLog - A Quick Emotion Logging App
Learning Objectives:
Problem Description:

Due date: Check the schedule.

Assignment: EmotiLog - A Quick Emotion Logging App

Learning Objectives:

Create a simple, interactive mobile application using Android and Java.
Document an object-oriented design using Unified Modeling Language (UML).

Problem Description:

Develop an Android app called ROLLNUM-EmotiLog (e.g., 25100052-EmotiLog) that allows users to quickly log their feelings or significant events by pressing emoticon buttons. The app should enable users to easily record each selected emoticon along with the corresponding timestamp, and then provide a summary of logs by frequency over a specified period.

Features:
- Preset Emoticon Buttons: 6 to 9 customizable emoticon buttons representing different feelings or events (e.g., Happy, Sad, Grateful, Angry, Excited, etc.).
- Logging Functionality: Each button press records the selected emoticon and the current timestamp.
- Daily Summary: Users can view a summary of logged emoticons for each day, including total counts and frequencies.
- User-Friendly Interface: The app must provide a simple and attractive user interface to enhance ease of use.
Deliverables:
1. Code Base:
  - Complete Android Studio project and compiled APK.
  - Each class must be properly commented to describe its purpose, design rationale, and any outstanding issues.
2. Video:
  - A demonstration video (max 3 minutes) showing the app\'s core functionalities without audio. It should illustrate how to log emoticons and view summaries.
3. System Documentation:
  - UML class diagram(s) detailing the app\'s object-oriented design. Include notes on each class\'s main responsibilities.
Demonstration Actions:
1. Open the app from the launcher.
2. Show the main screen with emoticon buttons.
3. Press an emoticon button (e.g., Happy)
4. Navigate to the list of emoticon events and confirm that it logs the selected emoticons with the timestamp.
5. Return to main screen with emoticon buttons.
6. Press 1 emotion 10 times in rapid succession.
7. Navigate to the list of emoticon events and confirm that it logs the selected emoticons with the timestamp.
8. Return to the main screen.
9. Press 1 emotion 5 times in rapid succession.
10. Go to the summary screen and show the emoticon counts.
Hints

This is a description of the core functionality. Often, problem statements from users lack details. As you are prototyping a design, you may uncover other behaviors that have not been specified, but make sense in the context and intent of the application. For example, think about how someone might effectively use your application. It is up to you to decide what functions your design will need, based on the given problem description and valid assumptions, in discussion with your users (the TAs and instructor). You should consider asking the customer (the instructor) what they want to see. While you may discuss your design with other students, the code and documentation must be your own work.

Code from publicly available sources may be used within reason and only if their licenses permit so. Always fully cite to give proper credit to the original developers in the source code and in the system documentation. For example, in citing a work, at least state: from whom, the date of publication, license, and URL. Do what is required by its license.

The TAs will be inspecting your code, so \"major\" commented-out experiments should be cleaned up so that the code is readable.

Do not skimp on the UML class diagrams in the system documentation. For neatness and readability, diagrams should be created or drawn using a vector graphics editing tool and exported in a common, non-lossy graphics format.

Besides addressing the problem correctly, your software design will be evaluated on its proper use of object-oriented design concepts, such as separation of concerns and information hiding.
Losing Marks

You may lose marks for any of the following:
- files not in properly named subdirectories
- missing compiled binary APK file for the app
- cannot run the app after install
- cannot distinguish CCID from the app name
- cannot view files without specialized tools
- lossy compression used in image file(s) for UML (e.g., JPEG)
- inadequate or improper citations
- using RAR archive format
These are brown M&M rules.
Submission Procedure:
- Create a directory named ROLLNUM-EmotiLog (e.g., kennyw-EmotiLog) and include the following subdirectories: code, video, doc.
- Place the Android Studio project in the code directory.
- Include the APK file under code/app/build/outputs/apk/debug/app-debug.apk.
- Store the demonstration video in the video directory.
- Keep UML documentation in the doc directory.
- Zip the ROLLNUM-EmotiLog directory and upload.
Evaluation Criteria:

The submission will be assessed according to the following categories:
- Excellent (8): Functionality meets all requirements, intuitive UI, comprehensive UML, and a clear video demonstration.
- Good (7): Minor issues but overall functional and follows submission rules.
- Satisfactory (5): Runs, but noticeable issues; some requirements may be missing; UML is present but may be incomplete.
- Unsatisfactory (4): Significant issues affecting functionality or missing requirements.
- Failure (0): Incomplete submissions or missing vital components such as Videos, UML, or code.
Excellent (8):
- The app is fully functional, meeting all the specified requirements.
- The user interface is intuitive, attractive, and responsive.
- The app follows the brown M&M rules.
- The UML documentation is comprehensive and accurately represents the object-oriented design.
- The video demonstration clearly showcases all required actions, and the app performs flawlessly in the demo.
- Must have a Video
- Must have UML
- Must Have Codebase
Good (7):
- The app runs and performs the expected functionalities.
- Minor issues may be present, such as a small bug or a slight deviation from the requirements.
- The user interface is satisfactory but may have some room for improvement.
- The app follows the brown M&M rules.
- The UML documentation is mostly complete but may have minor omissions.
- Must have a Video
- Must have UML
- Must Have Codebase
Satisfactory (5):
- The app runs, but there are noticeable issues affecting its stability or functionality.
- Some requirements may be missing or not fully implemented.
- The user interface is functional but may lack polish or suffer from usability issues.
- The app may not fully adhere to the brown M&M rules.
- The UML documentation is present but may be incomplete or inaccurate.
- Must have a Video
- Must have UML
- Must Have Codebase
Unsatisfactory (4):
- Effort has been put into the assignment, but the app may not run well or may have significant functionality issues.
- Several requirements are missing or not implemented.
- The user interface may be confusing or challenging to use.
- The app may not follow the brown M&M rules.
- The UML documentation lacks essential components, incomplete, inaccuate.
- Must have a Video
- Must have UML
- Must Have Codebase
Failure (0):
- The assignment is incomplete, lacking essential components such as UML documentation, video demonstration, or code.
- No submission is provided.
- Could be missing any one of these: Video, UML, Codebase

Assignment 1

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

Assignment: EmotiLog - A Quick Emotion Logging App
Learning Objectives:
Problem Description:

Due date: Check the schedule.

Assignment: EmotiLog - A Quick Emotion Logging App

Learning Objectives:

Create a simple, interactive mobile application using Android and Java.
Document an object-oriented design using Unified Modeling Language (UML).

Problem Description:

Features:
- Preset Emoticon Buttons: 6 to 9 customizable emoticon buttons representing different feelings or events (e.g., Happy, Sad, Grateful, Angry, Excited, etc.).
- Logging Functionality: Each button press records the selected emoticon and the current timestamp.
- Daily Summary: Users can view a summary of logged emoticons for each day, including total counts and frequencies.
- User-Friendly Interface: The app must provide a simple and attractive user interface to enhance ease of use.
Deliverables:
1. Code Base:
  - Complete Android Studio project and compiled APK.
  - Each class must be properly commented to describe its purpose, design rationale, and any outstanding issues.
2. Video:
  - A demonstration video (max 3 minutes) showing the app\'s core functionalities without audio. It should illustrate how to log emoticons and view summaries.
3. System Documentation:
  - UML class diagram(s) detailing the app\'s object-oriented design. Include notes on each class\'s main responsibilities.
Demonstration Actions:
1. Open the app from the launcher.
2. Show the main screen with emoticon buttons.
3. Press an emoticon button (e.g., Happy)
4. Navigate to the list of emoticon events and confirm that it logs the selected emoticons with the timestamp.
5. Return to main screen with emoticon buttons.
6. Press 1 emotion 10 times in rapid succession.
7. Navigate to the list of emoticon events and confirm that it logs the selected emoticons with the timestamp.
8. Return to the main screen.
9. Press 1 emotion 5 times in rapid succession.
10. Go to the summary screen and show the emoticon counts.
Hints

This is a description of the core functionality. Often, problem statements from users lack details. As you are prototyping a design, you may uncover other behaviors that have not been specified, but make sense in the context and intent of the application. For example, think about how someone might effectively use your application. It is up to you to decide what functions your design will need, based on the given problem description and valid assumptions, in discussion with your users (the TAs and instructor). You should consider asking the customer (the instructor) what they want to see. While you may discuss your design with other students, the code and documentation must be your own work.

Code from publicly available sources may be used within reason and only if their licenses permit so. Always fully cite to give proper credit to the original developers in the source code and in the system documentation. For example, in citing a work, at least state: from whom, the date of publication, license, and URL. Do what is required by its license.

The TAs will be inspecting your code, so \"major\" commented-out experiments should be cleaned up so that the code is readable.

Do not skimp on the UML class diagrams in the system documentation. For neatness and readability, diagrams should be created or drawn using a vector graphics editing tool and exported in a common, non-lossy graphics format.

Besides addressing the problem correctly, your software design will be evaluated on its proper use of object-oriented design concepts, such as separation of concerns and information hiding.
Losing Marks

You may lose marks for any of the following:
- files not in properly named subdirectories
- missing compiled binary APK file for the app
- cannot run the app after install
- cannot distinguish CCID from the app name
- cannot view files without specialized tools
- lossy compression used in image file(s) for UML (e.g., JPEG)
- inadequate or improper citations
- using RAR archive format
These are brown M&M rules.
Submission Procedure:
- Create a directory named ROLLNUM-EmotiLog (e.g., kennyw-EmotiLog) and include the following subdirectories: code, video, doc.
- Place the Android Studio project in the code directory.
- Include the APK file under code/app/build/outputs/apk/debug/app-debug.apk.
- Store the demonstration video in the video directory.
- Keep UML documentation in the doc directory.
- Zip the ROLLNUM-EmotiLog directory and upload.
Evaluation Criteria:

The submission will be assessed according to the following categories:
- Excellent (8): Functionality meets all requirements, intuitive UI, comprehensive UML, and a clear video demonstration.
- Good (7): Minor issues but overall functional and follows submission rules.
- Satisfactory (5): Runs, but noticeable issues; some requirements may be missing; UML is present but may be incomplete.
- Unsatisfactory (4): Significant issues affecting functionality or missing requirements.
- Failure (0): Incomplete submissions or missing vital components such as Videos, UML, or code.
Excellent (8):
- The app is fully functional, meeting all the specified requirements.
- The user interface is intuitive, attractive, and responsive.
- The app follows the brown M&M rules.
- The UML documentation is comprehensive and accurately represents the object-oriented design.
- The video demonstration clearly showcases all required actions, and the app performs flawlessly in the demo.
- Must have a Video
- Must have UML
- Must Have Codebase
Good (7):
- The app runs and performs the expected functionalities.
- Minor issues may be present, such as a small bug or a slight deviation from the requirements.
- The user interface is satisfactory but may have some room for improvement.
- The app follows the brown M&M rules.
- The UML documentation is mostly complete but may have minor omissions.
- Must have a Video
- Must have UML
- Must Have Codebase
Satisfactory (5):
- The app runs, but there are noticeable issues affecting its stability or functionality.
- Some requirements may be missing or not fully implemented.
- The user interface is functional but may lack polish or suffer from usability issues.
- The app may not fully adhere to the brown M&M rules.
- The UML documentation is present but may be incomplete or inaccurate.
- Must have a Video
- Must have UML
- Must Have Codebase
Unsatisfactory (4):
- Effort has been put into the assignment, but the app may not run well or may have significant functionality issues.
- Several requirements are missing or not implemented.
- The user interface may be confusing or challenging to use.
- The app may not follow the brown M&M rules.
- The UML documentation lacks essential components, incomplete, inaccuate.
- Must have a Video
- Must have UML
- Must Have Codebase
Failure (0):
- The assignment is incomplete, lacking essential components such as UML documentation, video demonstration, or code.
- No submission is provided.
- Could be missing any one of these: Video, UML, Codebase

Project Part 1

2025-08-28T00:00:00+05:00

Learning Objectives
Exercise
Submission Procedure
Hints

Due date: Check the schedule.

Learning Objectives

Set up and use collaborative tools for team-based project development.
Collaborate in a team.

Exercise

Your team is expected to use GitHub for a git repository and wiki to share, manage, and store your project artifacts.

See the Project Teams sheet for your assigned team name, Example: indigo.
Add CS360S26 to it. Example CS360S26indigo
Create a new GitHub Organization using the following naming format: CS360S26teamname e.g.CS360S26indigo
This must be the exact name of your team’s GitHub organization. Use the free GitHub plan.
Inside your newly created organization, create one public repository. The repository name must be a professional, respectful project name related to your team name. Example: indigo-events
Make sure your repository is accessible at all times to team members, the TAs, and the instructor via GitHub. Record the repo URL.
Create a doc/ directory in your repository, create a team.txt file within doc/, and have each of your team members make a distinct, versioned edit to that file. For each member, that edit must be a line with their GitHub username.

(Later in the course, project documentation will be done using the GitHub wiki.)

Submission Procedure

One team member uses the Google form to submit project part 1.

Hints

This exercise can be completed with your team in the labs that cover git and GitHub.

Project Problem Description

2025-08-26T00:00:00+05:00

Dr Abdul Ali Bangash
Dr Suleman Shahid status: published summary: Project Problem Description

Project Problem Description

Select any one topic out of the following:

Project 1: Campus Event Discovery and Management Platform

A centralized platform where students can discover, browse, and RSVP to campus events while event organizers can create and manage their events efficiently.

Core Features

Event browsing and discovery (talks, sports, clubs, performances)
RSVP and attendance tracking
Calendar integration for personal scheduling
Event creation and management dashboard for organizers
Ticket management or capacity tracking
Real-time event updates and notifications
Event categorization and search filters

Primary Users

Students
Student club leaders
LUMS Staff

Key Challenges

Calendar API integration
Real-time notifications
Capacity management
Event discovery algorithms

Project 2: Peer Tutoring Marketplace

A platform that connects students seeking academic help with peer tutors, enabling scheduling, session management, and quality feedback.

Core Features

Tutor and student profile creation with subjects/courses
Tutoring session request and offer system
Session scheduling and booking
Rating and review system for tutors
Session history and progress tracking
Subject-based tutor matching
Simple payment integration or credit system (extra)

Primary Users

Students seeking help
Peer tutors
Academic advisors

Key Challenges

User matching algorithms
Scheduling optimization
Review system integrity
Payment handling (if applicable)

Project 3: Campus Sustainability Tracker

A gamified platform that encourages sustainable behavior by allowing students to log daily activities, track environmental impact, and participate in green challenges.

Core Features

Daily activity logging (transport mode, energy use, waste)
Personal impact dashboards with visualizations
Collective campus-wide impact tracking
Green challenges and competitions
Leaderboards and achievement badges
Sustainability tips and educational content
Team-based challenges for clubs or departments

Primary Users

Students
Campus sustainability office
Environmental clubs

Key Challenges

Data visualization
Gamification mechanics
User engagement strategies
Impact calculation accuracy

Project 4: Campus Gate Access System

A security management system that streamlines visitor entry, credential verification, and entry/exit logging for campus gates.

Core Features

Guard dashboard for visitor credential checking
Visitor request submission portal for faculty and staff
Approved entry time verification
Entry and exit logging system
Ad-hoc visitor approval workflow
Guest pass system for students
Security audit logs and reporting
Visitor lookup and search functionality

Primary Users

Security guards
Faculty
Staff
Students
Security administrators

Key Challenges

Real-time credential verification
Approval workflows
Audit trail integrity
Mobile accessibility for guards

Scope Note:
Focus on core functionality—guard dashboard, visitor lookup, and entry logging. Advanced features like SMS notifications or facial recognition can be considered for future iterations.

Project 5: Counseling Appointment System

An appointment management platform that connects students with counseling services, enabling easy booking, scheduling, and session management.

Core Features

Counselor discovery and availability viewing
Time slot booking system
Appointment reminders and notifications
Rescheduling and cancellation functionality
Counselor availability management dashboard
No-show tracking and analytics
Pre-session intake forms
Post-session feedback mechanism
Appointment history for students and counselors

Primary Users

Students
Counselors
Counseling office administrators

Key Challenges

Privacy and confidentiality
Scheduling conflict management
Reliable notification system
No-show prevention

Scope Note:
Focus on appointment booking flow, availability management, and basic notifications. Intake forms and feedback can be added progressively.

Project Problem Description

2025-08-26T00:00:00+05:00

Dr Abdul Ali Bangash
Dr Suleman Shahid status: published summary: Project Problem Description

Project Problem Description

Select any one topic out of the following:

Project 1: Campus Event Discovery and Management Platform

A centralized platform where students can discover, browse, and RSVP to campus events while event organizers can create and manage their events efficiently.

Core Features

Event browsing and discovery (talks, sports, clubs, performances)
RSVP and attendance tracking
Calendar integration for personal scheduling
Event creation and management dashboard for organizers
Ticket management or capacity tracking
Real-time event updates and notifications
Event categorization and search filters

Primary Users

Students
Student club leaders
LUMS Staff

Key Challenges

Calendar API integration
Real-time notifications
Capacity management
Event discovery algorithms

Project 2: Peer Tutoring Marketplace

A platform that connects students seeking academic help with peer tutors, enabling scheduling, session management, and quality feedback.

Core Features

Tutor and student profile creation with subjects/courses
Tutoring session request and offer system
Session scheduling and booking
Rating and review system for tutors
Session history and progress tracking
Subject-based tutor matching
Simple payment integration or credit system (extra)

Primary Users

Students seeking help
Peer tutors
Academic advisors

Key Challenges

User matching algorithms
Scheduling optimization
Review system integrity
Payment handling (if applicable)

Project 3: Campus Sustainability Tracker

A gamified platform that encourages sustainable behavior by allowing students to log daily activities, track environmental impact, and participate in green challenges.

Core Features

Daily activity logging (transport mode, energy use, waste)
Personal impact dashboards with visualizations
Collective campus-wide impact tracking
Green challenges and competitions
Leaderboards and achievement badges
Sustainability tips and educational content
Team-based challenges for clubs or departments

Primary Users

Students
Campus sustainability office
Environmental clubs

Key Challenges

Data visualization
Gamification mechanics
User engagement strategies
Impact calculation accuracy

Project 4: Campus Gate Access System

A security management system that streamlines visitor entry, credential verification, and entry/exit logging for campus gates.

Core Features

Guard dashboard for visitor credential checking
Visitor request submission portal for faculty and staff
Approved entry time verification
Entry and exit logging system
Ad-hoc visitor approval workflow
Guest pass system for students
Security audit logs and reporting
Visitor lookup and search functionality

Primary Users

Security guards
Faculty
Staff
Students
Security administrators

Key Challenges

Real-time credential verification
Approval workflows
Audit trail integrity
Mobile accessibility for guards

Project 5: Counseling Appointment System

An appointment management platform that connects students with counseling services, enabling easy booking, scheduling, and session management.

Core Features

Counselor discovery and availability viewing
Time slot booking system
Appointment reminders and notifications
Rescheduling and cancellation functionality
Counselor availability management dashboard
No-show tracking and analytics
Pre-session intake forms
Post-session feedback mechanism
Appointment history for students and counselors

Primary Users

Students
Counselors
Counseling office administrators

Key Challenges

Privacy and confidentiality
Scheduling conflict management
Reliable notification system
No-show prevention

Scope Note:
Focus on appointment booking flow, availability management, and basic notifications. Intake forms and feedback can be added progressively.

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

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]

Old Lecture Recordings Fall 2020

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

Old Lecture Recordings 2020 Fall

Old Lecture Recordings Fall 2021

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

Old Lecture Recordings 2021 Fall

Course Outline Winter 2024

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

General Information

Term: Winter 2024
Number of credits: 3 credits

Lecture (E)B1
Date and Time: Monday-Wednesday-Friday, 10:00-10:50 MT
Location: C E1-60
Instructor: Dr. Abram Hindle

Lecture (E)B2
Date and Time: Monday-Wednesday-Friday, 11:00-11:50 MT
Location: ETLC E1-017
Instructor: Dr. Hazel Campbell

Labs start in the FIRST week of classes.

Lab (E)H01

Date and Time: Tuesday, 17:00-19:50
Location: ETLC E1-013

Lab (E)H02

Date and Time: Wednesday, 17:00-19:50
Location: ETLC E1-0003

Lab (E)H03

Date and Time: Thursday, 17:00-19:50
Location: CCIS 1-140

See Contact Information for details about your instructor and teaching assistants.

Policy about course outlines can be found in Course Requirements, Evaluation Procedures and Grading of the University Calendar.

This statement is required verbatim, as per Calendar regulations.

Disclaimer: Any errors in this Course Outline and Course Policy are subject to change and will be announced in class. The date of the final examination is set by the Registrar and takes precedence over the final examination date reported in this syllabus.

Overview

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.

Pre-requisites

CMPUT 201 or 275

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 in-person. Exercises are in person. Midterms are in person.

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

Note the rightmost column below, which shows collaboration models for each unit of course work. These models are described on the CS course policy page:

https://www.ualberta.ca/computing-science/resources/policy-information/department-course-policies.html

Individual Work	Assignment 0	required	January 22	Consultation
	Assignment 1	8%	February 5	Consultation
	Participation	7%	throughout	Consultation
	Midterm Exam 1	15%	January 31	Solo Effort
	Midterm Exam 2	15%	March 4	Solo Effort
	Midterm Exam 3	15%	April 3	Solo Effort
Team Work	Project Part 0	required	January 22	Teamwork
	Project Part 1	required	February 5	Teamwork
	Project Part 2	8%	February 16	Teamwork
	Project Part 3	12%	March 8	Teamwork
	Project Part 4	20%	April 8	Teamwork
		100%

Reading break: Feb 19-23

Exams:

* There is no possibility of a reexamination in this course for midterms 1 and 2.

* Midterm 3 has a deferred oral exam. If you miss Midterm 3, you will have to do an oral exam.

There is NO Final exam.

In the midterm exams, you will be asked to code, diagram, write, describe and draw solutions to software engineering problems.

Grade Evaluation:

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. Obtaining 50 course marks or more guarantees a passing grade of at least D. Obtaining 90 course marks or more guarantees a grade of at least A-.

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

Course Materials

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.

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 exam pages when posted for representative example questions.

Academic Integrity

The University of Alberta is committed to the highest standards of academic integrity and honesty. Students are expected to be familiar with these standards regarding academic honesty and to uphold the policies of the University in this respect. Students are particularly urged to familiarize themselves with the provisions of the Code of Student Behaviour (online at www.governance.ualberta.ca) and avoid any behaviour which could potentially result in suspicions of cheating, plagiarism, misrepresentation of facts and/or participation in an offence. Academic dishonesty is a serious offence and can result in suspension or expulsion from the University. (GFC 29 SEP 2003)

Course Policies

Please see the Course Policies specific to CMPUT 301.

Most course policies are determined by the Department of Computing Science. See the following page for general information on CS course policies.

https://www.ualberta.ca/computing-science/resources/policy-information/department-course-policies.html

2011 W Project Problem Description

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

Project Problem Description

You are to design and implement an attractive, usable, interactive Java application to help satisfy the following user's goals. Your design should be flexible enough to allow future developers to add new types of entries (see below).

Needs In (Partial) User Story Form

These needs are expressed in the form of partial user stories: as a , I want as a , I want so that

These description may change in minor ways to correct omissions and clarify noticed issues.

As a user, I want to keep a record of my daily fitness-related activities in a journal so that I can monitor my progress. Types of entries include cardio workouts (i.e., outdoor cycling), strength workouts (i.e., free weights), and comment. There may be multiple, reorderable entries per day.
As a user, I want to see the entries for a single day, and move backwards and forwards one day at a time.
As a user, I want to see the entries for the days of four weeks at a time, and move backwards and forwards one week at a time. A week begins on Monday and ends on Sunday.
As a user, I want to be able to add, edit, and delete entries, including instant, multiple undo and redo of these changes (at the level of entries), so that I can freely make changes at any time.
As a user, I want data entry to be quick and structured, yet not unduly fussy. This is especially important if I happen to be using the application during a strength workout to keep track of exercises.
As a user, I want to obtain help, so that I can learn what tasks I can do and what a data field is intended for.
As a user, I want a comment entry to record a non-workout activity or general observation. Typical uses would be, for example, to note a meal, a weight measure, a waist measure, a resting heart rate measure, a soreness, a sickness, fatigue, mood, etc.
As a user, I want each outdoor cycling workout to include the following information: trip distance (in km, to 2 decimal places), trip time (in hh:mm:ss format), average speed (in km/h, to 2 decimal places), average cadence (in whole revolutions/min), and maximum speed (in km/h, to 2 decimal places). This data will be entered manually, in that order.
As a user, I want each outdoor cycling workout to include the following optional weather-related information: temperature (in whole degrees Celsius), wind speed (in whole km/h), and direction (one of 16 compass points). This data will be entered manually, in that order.
As a user, I want each cardio workout to include the following information: time in zone (in hh:mm:ss format), zone start (in whole beats/min), zone end (in whole beats/min), average heart rate (in whole beats/min), peak heart rate (in whole beats/min), and calories expended (in whole kcal). This data will be entered manually, in that order.
As a user, I want to name and specify preset heart rate values of up to 5 heart rate zones, so that I can choose a named zone to quickly fill in the values for the zone start and end in a cardio workout.
As a user, I want each free-weight workout to include for each exercise, the exercise name (required), number of sets (optional), number of reps (optional), and amount of weight (optional).
As a user, I want each strength workout to include the time duration in hh:mm.
As a user, I want to specify a workout in advance to remind me what activity to do on a particular day. I can delete the workout should it not occur.
As a user, I want to have a plan for a workout, detailing a particular goal or set of exercises. After the workout, I can rate the workout (0 to 5) on how well I achieved that goal or completed the exercises.
As a user, I want to avoid reentering plan details if different workouts will have the same plan. Also plans for different workout types should not be mixed.
As a user, I want to add a free-form note to a workout, containing anything else that doesn't belong to one of the existing data fields.
As a user, I want to have a brief free-form note for a week, so that I can specify the cardio and/or strength goal or phase for that week.
As a user, I want to see (as needed) a chart of outdoor cycling total trip distances covered in each month for a given year and previous year compared. It should be possible to have this chart visible as workouts are edited. If there is no data for a particular year, omit that year.
As a user, I want to see (as needed) a chart of outdoor cycling total trip times done in each month for a given year and previous year compared. It should be possible to have this chart visible as workouts are edited. If there is no data for a particular year, omit that year.
As a user, I want to see the outdoor cycling total trip distance covered and total trip time done so far in the current year compared to that of the previous year.

2012 W Project Problem Description

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

You are to design and implement an attractive, usable, interactive Android application to help satisfy the following user's goals. Your design should be flexible enough to allow future developers to extend it to, for example, add new types of entries (see below).

User's Problem Description

I went to my doctor and had a physical. It was embarassing. The doctor pointed out some spots and asked if I had seen them before. I wasn't sure, so neither put pushed the issue any further. We didn't know, so we weren't going to do anything. Another time I went to the doctor and had the doctor investigate a spot on my hand. The doctor asked me if it had changed, I wasn't sure. The doctor asked me if it had grown, I said I assume so because why am I noticing it now. The doctor shrugged, said it looked alright and told me to keep track of it. Come back if it changed.

I can't remember if it changes, to prove something changed I need evidence. I could take photos of my whole body and keep them in a safe place, but would I remember to take the photos again and consistently?

Thus I want software that will run on my phone and allow me to take photos of skin issues I might have. These photos will be for my own sanity as well I can provide them to physicians when they are needed.

I the user want to be able to track and document changes that occur on my skin. I want to use my cellphone to help me document all the blemishes and marks on my skin such that I can keep track of them.

Needs in (Partial) User Story Form

User needs are expressed in the form of partial user stories: as a , I want as a , I want so that

These descriptions may change to correct omissions and clarify noticed issues.

As a user, I want to keep a visual log of any skin conditions I might . The purpose could be to gather a personal history of a medical condition as to provide evidence to a physician.

As a user, I want pictures I take to be stored so that I may recall them and view them later.

As a user, I want all pictures I take to be timestamped so that I can measure the time between photos and know when an event occurred.

As a user, I want a method to organize these pictures so that I can view pictures of the same bit of skin over time and see if there is any progression or growth. For instance I might want to organize some photos that are related to my "gross mole that occurs on my right hand".

As a user if I have an organizational tag or group, I want to be able to add photos to that group so that I can further track the progression of something relevant to that group.

As a user, I want to be able to review any photos I have taken and view them so that I can see any changes.

As a user, I want some method of helping me take consistent photos, so that when I show the doctor any progression such as the growth of a mole is evident.

As a user, I should be able to retake photos I am taking, if I fail to take the photo I want to correct, so that I don't have erroneous photos.

As a user, I should be able to compare pictures in some manner, so that I can personally inspect them for differences.

New Needs for Project Part 4 in (Partial) User Story Form

As a user, I am worried that if my phone gets stolen people will see my photos. I want my photos secured via a password.

As a user, I am worried that if my phone gets stolen people will extract my photos and view them. I want my photos encrypted on the phone so if someone accesses the file system the image data should be encrypted so they can't extract the jpegs.

As a user, I want notifications about when I should take photos again. I'm forgetful and being told every so often to take new photos would be helpful. Certain photos I don't have to retake again.

As a user, I would like to control the rate, per blemish/set of photos that the notifications occur.

As a user, I want to email a set of photos to my physician.

As a user, I want to extract a set of the photos into an archive on my SDCard so I can share them.

As a user I would like to annotate images with annotations to describe the scenario that I made this photo

As a user I would like to tag the images so I can query the image by tag.

As a user I would like to browse the photos in different ways, by time, by tag, etc.

As a Doctor, I want to use this application to record information about my own patients. Thus I need to organize blemishes and photo collection per patient.

As a Doctor, I want to browse my patient photos in different ways, by time, by tag, etc.

Note A class advances and questions are asked new story cards will be created.

2013 W Project Problem Description

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

User's Problem Description

I want to keep recipes, but I also want to find recipes, eventually I found similar people had similar goals. Some people wanted recipes they could execute immediately given what they had in their fridge or pantry.

I want a system where I can record, post, search and download recipes. I want such a system to be able to address the food I have in my pantry and refridgerator.

It would be nice to include photos of said recipes.

I want the system to query the recipes system with ingredients I already have and have it suggest appropriate recipes.

Furthermore it should be easy to share these recipes over email.

Needs in (Partial) User Story Form

User needs are expressed in the form of partial user stories: as a , I want as a , I want so that

These descriptions may change to correct omissions and clarify noticed issues.

As a user, I want to record recipes.

As a user, I want to share recipes over email.

As a user, I want to publish recipes.

As a user, I want to search for recipes.

As a user, I want to have some recipes cached so that I don't need the internet to work for me to use this program.

As a user, I want to post and publish photos associated with the recipe.

As a user, executing a recipe I want to take photos and attach the photos to the recipe.

As a user, I want the recipes to be stored so I can view them offline.

As a user, recipes I make can have multiple photos.

As a user, I can upload photos for other recipes I did not make, but were downloaded.

As a user, I should be able to retake photos I am taking, if I fail to take the photo I want to correct, so that I don't have erroneous photos.

As a user I should be able to get recipes from other users somehow.

As a user I want to be able to record/edit/view/modify the ingredients I already have.

As a user I want to be able to query for recipes that have the ingredients I already have.

New requirements

- As a user, I want to email other users recipes that they can
  immediately import into their recipe program.  [s]


- As a user, I want to limit modifications of a recipe to myself
  only. -- Note: this doesn't have to be done server side, your
  app could enforce this.  [l]


- As a user, I want to globally tag recipes. Recipes can have
  multiple tags and other users can see these tags. [l]


- As a user, I want to browse recipes by tags. [s]


- As a user, I want to query recipes based on a subset of my
  ingredients. [s]


- As a user, I want to organize ingredients into folders (like
  fridge, or cabin fridge) and be able to query recipes based on
  these folders. [l]


- As a user, I want to optionally browse recipes with only photos
  [s]


- As a user, I want to search recipes I downloaded already. [s]


- As a user, I want to read/write comments on a recipe. [l]

- As a user, I want to delete cached recipes (downloaded). [s]


- As a user, I want to export my recipes to some kind of file so I
  can export them to other programs. [l]

- As a user, I want to browse the most popular recipes based on their downloaded counts.[l]

- As a user, I want to STAR good recipes and I want to browse recipes that everyone has given to the most stars. [l]

Notes

As class advances and questions are asked new story cards will be created.

Webservice Notes

Please see the URL: http://www.elasticsearch.org/ and http://www.elasticsearch.org/guide/reference/query-dsl/query-string-query.html

Each group now has its own personal prefix on the elastisearch. Your Android application can communicate to your group's webservice.

Binaries should be small, and you can post them, but be sure you read up on how to send binaries to elastisearch http://www.elasticsearch.org/guide/reference/mapping/core-types.html http://www.elasticsearch.org/guide/reference/api/admin-indices-put-mapping.html

This webservice is meant to allow posting, listing, deleting and searching recipes. It has a JSON format that can be defined by your group in order to encode more difficult tasks.

http://cmput301.softwareprocess.es:8080/CMPUT301W13T01/

http://cmput301.softwareprocess.es:8080/CMPUT301W13T02/

http://cmput301.softwareprocess.es:8080/CMPUT301W13T03/

http://cmput301.softwareprocess.es:8080/CMPUT301W13T04/

http://cmput301.softwareprocess.es:8080/CMPUT301W13T05/

http://cmput301.softwareprocess.es:8080/CMPUT301W13T07/

http://cmput301.softwareprocess.es:8080/CMPUT301W13T08/

http://cmput301.softwareprocess.es:8080/CMPUT301W13T09/

http://cmput301.softwareprocess.es:8080/CMPUT301W13T10/

http://cmput301.softwareprocess.es:8080/CMPUT301W13T11/

http://cmput301.softwareprocess.es:8080/CMPUT301W13T12/

http://cmput301.softwareprocess.es:8080/CMPUT301W13T13/

http://cmput301.softwareprocess.es:8080/CMPUT301W13T14/

These are not protected in anyway and they should stick to their own repos.

http://cmput301.softwareprocess.es:8080/testing/ is for testing.

2014 F Project Problem Description

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

User's Problem Description

We want a mobile question and answer site. A user can browse questions and post answers. A user can pose questions and see answers. Both question and answers can have a small discussion accompanied with them.

Imagine http://stackoverflow.com/ but geo-location aware.

Needs in (Partial) User Story Form [do all of these]

User needs are expressed in the form of partial user stories: as a , I want as a , I want so that

These descriptions may change to correct omissions and clarify noticed issues.

As a user, I want browse questions.

As a user, I want to view a question and its answers.

As a user, I want to view the replies to a question or answer.

As an author, I want to make questions.

As an author, I want to answer questions by making an answer.

As an author, I want to reply to questions and answers to clarify things.

As an author, I want to attach a picture to my questions or my answers.

As a sysadmin, I do not want the pictures to be large (> 64kb).

As a user, I want to sort questions by if they have pictures.

As a user, I want to sort questions by date or some scoring system.

As a user, I want to upvote the questions of other users.

As a user, I want to upvote the answers of other users

As a user, I want to see the most upvoted questions and most upvoted answers.

As a user, I want to see how many answers a question has received.

As a user, I want to search for questions or answers.

As an author, I want my device to remember which questions I asked.

As a user, I want questions and answers that I read or questions and answers that I've indicated I want to read, to be locally cached so I can read them when I am not on the internet.

As a user, I want to explicitly save some questions as favorites.

As a user, My favorites and their replies should always be available to me regardless of network connectivity.

As an author, I want to author replies, questions and answers offline.

As an author, I want to push my replies, questions and answers online once I get connectivity.

As a user, by default, I should see the most fresh comments.

As an author, I set my username.

New requirements [Choose 1 of these]

Requirements Cluster: Geolocation
As an author, I want to be asked if my location should be attached to my post
As a user I want to be able to query for posts (questions/answers/replies) that are near to me
As an author, I want my geolocation to come from my GPS, or allow me to set to it
As a user, I want to know if the location of post is near city or town or country.
Requirements Cluster: Social Analytics
As a user, I want to see the trending posts that have recent popularity and activity
As a user, I want to see who the top contributors are
As a user, I want to see a summary of what topics are trending, that is a textual analysis or summary of what is happening lately
As a user, I want to see controversial questions: questions with few upvotes but many replies
As a user, I want a word cloud of all the posts cached on my phone.
Requirements Cluster: Recommendations
As a user I want to browse other questions asked by an author
As a user I want to browse answers written by an author
As an author I want to see related questions when I ask a question
As an author I want to see other question I may be able to answer when I write an answer
As a user I want to see related questions when I browse questions
More to come!

Notes

As class advances and questions are asked new story cards will be created.

Webservice Notes

Please see the URL: http://www.elasticsearch.org/ and Query String DSL

Each group now has its own personal prefix on the elastisearch. Your Android application can communicate to your group's webservice.

Binaries should be small, and you can post them, but be sure you read up on how to send binaries to elastisearch Core-types , Put Mappings

This webservice is meant to allow posting, listing, deleting and searching recipes. It has a JSON format that can be defined by your group in order to encode more difficult tasks.

http://cmput301.softwareprocess.es:8080/cmput301f14t01/

http://cmput301.softwareprocess.es:8080/cmput301f14t02/

http://cmput301.softwareprocess.es:8080/cmput301f14t03/

http://cmput301.softwareprocess.es:8080/cmput301f14t04/

http://cmput301.softwareprocess.es:8080/cmput301f14t05/

http://cmput301.softwareprocess.es:8080/cmput301f14t06/

http://cmput301.softwareprocess.es:8080/cmput301f14t07/

http://cmput301.softwareprocess.es:8080/cmput301f14t08/

http://cmput301.softwareprocess.es:8080/cmput301f14t09/

http://cmput301.softwareprocess.es:8080/cmput301f14t10/

http://cmput301.softwareprocess.es:8080/cmput301f14t11/

http://cmput301.softwareprocess.es:8080/cmput301f14t12/

http://cmput301.softwareprocess.es:8080/cmput301f14t13/

http://cmput301.softwareprocess.es:8080/cmput301f14t14/

http://cmput301.softwareprocess.es:8080/cmput301f14t15/

http://cmput301.softwareprocess.es:8080/cmput301f14t16/

These are not protected in anyway and they should stick to their own repos.

http://cmput301.softwareprocess.es:8080/testing/ is for testing.

Requirements Cluster: Recommendations - As a user I want to browse other questions asked by an author - As a user I want to browse answers written by an author - As an author I want to see related questions when I ask a question

As an author I want to see other question I may be able to answer when I write an answer
As a user I want to see related questions when I browse questions

2015 F Project Problem Description

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

Project Problem Description

will mean the theme of your group project: condiments, sewing tools, tools, craft supplies, baking supplies, kitchen tools, books, DVDs, games, audio equipment, photography equipment, etc. Each team will choose a theme for their app distinct from other teams. TA will approve the theme.

User's Problem Description

We want to create a distributed library where by we can trade with other people.

We want a mobile application that allows users to record the they have and share them with others! Users can share with each other. This means that you get to see your neighbor's and they can browse your collection of . Then when you want a from your neighbor you send them a request to see if they want one of your as collateral for their .

Needs in (Partial) User Story Form

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

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

Inventory

US01.01.01

As an owner, I want to remove, edit, or add an item to my inventory that I want to share. It will have a name, quantity, quality, category, if I want to share it with others, and comments.

US01.02.01

As an owner, I want to view my inventory and its details.

US01.03.01

As an owner, I want to view each of my inventory items.

US01.03.01

As an owner, not every item in my inventory will be shared or listed. Items that are not to publicly shared will not be. As an owner, I might use them for trades.

US01.04.01 As an owner, I want to edit and modify inventory items.

US01.05.01 As an owner, I want to delete inventory items.

US01.06.01 As an owner, I want the category for an item to be one of 10 relevant categories for .

US01.07.01 As an owner, I want the entry of an item to have minimal required navigation in the user interface. It must be easy to describe an item.

Friends

US02.01.01

As an owner, I want to track people I know. Adding a textual username should be enough.

US02.02.01

As an owner, I want to add friends

US02.03.01

As an owner, I want to remove friends

US02.04.01

As an owner or borrower, I will have a profile where by my contact information and city are recorded.

US02.05.01

As an owner or borrower, I will be able to view the profile of anyone I know of including friends.

Browse Search Inventories of Friends

US03.01.01

As an borrower, I want to search the inventories of my friends.

US03.01.02

As an borrower, I want to search/browse the inventories of my friends by category.

US03.01.03

As an borrower, I want to search/browse the inventories of my friends by textual query..

US03.02.01

As an owner, any of my publicly shared items will be browseable / searchable by my friends.

Trade with Friends

US04.01.01

As an borrower, I want to offer a trade with a friend. A trade will consist of an item from the owner's inventory and 0 or more items from the borrower's inventory.

US04.02.01

As an owner, when a borrower offers a trade I will be notified of the trade.

US04.03.01

As an owner, I can accept or decline a trade.

US04.04.01

As an owner, upon declining a trade I can offer a counter trade initialized with the items of the declined trade.

US04.05.01

As a borrower or owner, when composing a trade or counter-trade I can edit the trade.

US04.06.01

As a borrower, when composing a trade or counter-trade I can delete the trade

US04.07.01

As an owner, if I accept a trade both parties will be emailed all trade and item information relevant to the trade, as well owner comments for how to continue on with the trade.

US04.08.01

As an owner or borrower, I can browse all past and current trades involving me.

US04.09.01

As an owner or borrower, I can browse all past and current trades involving me as either borrower or owner. I should look at my trades and trades offered to me.

US04.10.01 [must]

As an owner, I can set a trade to complete when the borrower returns the item and the item is now available again.

US04.11.01 [must]

As an owner or borrower, a trade is considered current and in-progress when the item is borrowed.

US04.12.01 [must]

As an owner or borrower, I should be able to browse in-progress trades, and complete trades.

Photographs of Items

US06.01.01 As an owner, I want to optionally attach photographs of items to the item. Photos are optional for items.

US06.02.01 As an owner, I want to view any attached photograph for an item.

US06.03.01 As an owner, I want to delete any attached photograph receipt on an item, so that unclear images can be re-taken.

US06.04.01 As a sysadmin, I want each receipt image file to be under 65536 bytes in size.

US06.05.01 As a borrower, if photo downloads are disabled, I want the option of manually choosing inventory photos to download.

Offline Behaviour

US09.01.01 As an owner, I want to make inventory items while offline, and push changes once I get connectivity.

US09.02.01 As a borrower, I want to make trades while offline, and push changes online once I get connectivity.

US09.03.01 As a borrower, I should be able to browse the inventories of friends that I previously looked at. Cache the inventories of the friends.

Configuration

US10.01.01 As a user, I should be able to specify if I download images or not.

US10.02.01 As a user, I should be to edit my profile.

Your team must choose Option 1 features or Option 2 features and implement them.

Item Geolocation (Option 1)

US11.01.01

As an owner, I want to have a default geolocation (Lat/Long) that will be assigned to my items.

US11.02.01

As a user, I should be able to search for items near my current location (GPS or Lat/long). E.g. hammers within 2 km.

US11.03.01

As an owner, I should be able use the GPS to determine my geolocation.

US11.04.01

As an owner, I should be able to specifically edit the geolocation of each individual item -- items could be located in different locations.

Top Traders (Option 2)

US12.01.01

As a user, I should be able to see friends and users who are top-traders. Top traders are users with successful (current, in-progress, and complete) trades. The more successful traders, the more top the trader.

Item Cloning (Option 2)

US13.01.01

As an owner, I should be able to clone another user's item, if I own it or a copy. E.g. I have the same XBOX game as my friend and I don't want to type it in again.

Revisions:

2015-11-12 - US10 to US13 added, US04.10 to US04.14 added.

2015-10-08 - US09.01.01 and US09.02.01 clarified and editted

2015-10-07 - US06.05.01 changed to manual photo download

2015-10-07 - the trade with friends section had stories renumbered as US.04. (previously US.03.)

2015-10-06 - the last US.06.04.01 becomes US.06.05.01

2015-10-06 - claimant becomes owner in US.06.01.01

2015 W Project Problem Description

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

Project Problem Description

User's Problem Description

We want a mobile application for travel expense tracking and approval.

Needs in (Partial) User Story Form

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

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

Expense Claims / Overall

US01.01.01 As a claimant, I want make an expense claim that records my name, a starting date of travel, and an ending date of travel.

US01.02.01 As a claimant, I want an expense claim to record one or more destinations of travel and an associated reason for travel to each destination.

US01.03.01 As a claimant, I want to view an expense claim and its details.

US01.04.01 As a claimant, I want to edit an expense claim while changes are allowed.

US01.05.01 As a claimant, I want to delete an expense claim while changes are allowed.

US01.06.01 As a claimant, I want entered information to be remembered, so that I do not lose data.

Expense Claims / Listing

US02.01.01 As a claimant, I want to list all my expense claims, showing for each claim: the starting date of travel, the destination(s) of travel, the claim status, tags, and total currency amounts.

US02.02.01 As a claimant, I want the list of expense claims to be sorted by starting date of travel, in order from most recent to oldest, so that ongoing or recent travel expenses are quickly accessible.

Expense Claims / Tags

US03.01.01 As a claimant, I want to give an expense claim one or more alphanumeric tags, so that claims can be organized by me into groups.

US03.02.01 As a claimant, I want to manage my personal use of tags by listing the available tags, adding a tag, renaming a tag, and deleting a tag.

US03.03.01 As a claimant, I want to filter the list of expense claims by tags, to show only those claims that have at least one tag matching any of a given set of one or more filter tags.

Expense Items / Overall

US04.01.01 As a claimant, I want to make one or more expense items for an expense claim, each of which has a date the expense was incurred, a category, a textual description, amount spent, and unit of currency.

US04.02.01 As a claimant, I want the category for an expense item to be one of air fare, ground transport, vehicle rental, private automobile, fuel, parking, registration, accommodation, meal, or supplies.

US04.03.01 As a claimant, I want the currency for an expense amount to be one of CAD, USD, EUR, GBP, CHF, JPY, or CNY.

US04.04.01 As a claimant, I want to manually flag an expense item with an incompleteness indicator, even if all item fields have values, so that I am reminded that the item needs further editing.

US04.05.01 As a claimant, I want to view an expense item and its details.

US04.06.01 As a claimant, I want to edit an expense item while changes are allowed.

US04.07.01 As a claimant, I want to delete an expense item while changes are allowed.

US04.08.01 As a claimant, I want the entry of an expense item to have minimal required navigation in the user interface.

Expense Items / Listing

US05.01.01 As a claimant, I want to list all the expense items for a claim, in order of entry, showing for each expense item: the date the expense was incurred, the category, the textual description, amount spent, unit of currency, whether there is a photographic receipt, and incompleteness indicator.

Expense Items / Receipts

US06.01.01 As a claimant, I want to optionally take a single photograph of a receipt and attach the photograph to an editable expense item, so that there is supporting documentation for the expense item in case the physical receipt is lost.

US06.02.01 As a claimant, I want to view any attached photographic receipt for an expense item.

US06.03.01 As a claimant, I want to delete any attached photographic receipt on an editable expense item, so that unclear images can be re-taken.

US06.04.01 As a sysadmin, I want each receipt image file to be under 65536 bytes in size.

Expense Claims / Statuses

US07.01.01 As a claimant, I want to submit an expense claim for approval, denoting the claim status as submitted, with no further changes allowed by me to the claim information (except the tags).

US07.02.01 As a claimant, I want a visual warning when trying to submit an expense claim when there are fields with missing values or there are any incompleteness indicators on the expense items.

US07.03.01 As a claimant, I want a submitted expense claim that was not approved to be denoted by a claim status of returned, with further changes allowed by me to the claim information.

US07.04.01 As a claimant, I want a submitted expense claim that was approved to be denoted by a claim status of approved, with no further changes allowed by me to the claim information (except the tags).

US07.05.01 As a claimant, I want to see the name of the approver and any comment(s) from the approver on a returned or approved claim.

Expense Claims / Approval

US08.01.01 As an approver, I want to view a list of all the expense claims that were submitted for approval, which have their claim status as submitted, showing for each claim: the claimant name, the starting date of travel, the destination(s) of travel, the claim status, total currency amounts, and any approver name.

US08.02.01 As an approver, I want the list of submitted expense claims to be sorted by starting date of travel, in order from oldest to most recent, so that older claims are considered first.

US08.03.01 As an approver, I want to view all the details of a submitted expense claim.

US08.04.01 As an approver, I want to list all the expense items for a submitted claim, in order of entry, showing for each expense item: the date the expense was incurred, the category, the textual description, amount spent, unit of currency, and whether there is a photographic receipt.

US08.05.01 As an approver, I want to view any attached photographic receipt for an expense item.

US08.06.01 As an approver, I want to add a comment to a submitted expense claim, so that I can explain why the claim was returned or provide accounting details for a payment.

US08.07.01 As an approver, I want to return a submitted expense claim that was not approved, denoting the claim status as returned and setting my name as the approver for the expense claim.

US08.08.01 As an approver, I want to approve a submitted expense claim that was approved, denoting the claim status as approved and setting my name as the approver for the expense claim.

Expense Claims / Offline

US09.01.01 As a claimant, I want to make and work on expense claims and items while offline, and push application and expense information online once I get connectivity.

2015 W Project Problem Description Surprise

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

Project Problem Description Surprise

Expense Items / Driving

As a claimant, I want to record the starting location, ending location, and distance for a drive and attach this information to an editable expense item with the private automobile category.

As a claimant, I want the driving locations to come from GPS or allow me to set the locations.

As a claimant, I want the driving distance to be estimated from the starting and ending locations or allow me to set the distance in kilometres.

As a claimant, I want to take a photograph of an odometer and attach the photograph to the starting location or the ending location of a drive.

Expense Claims / Communication

As a claimant, I want to email all the details of an expense claim, organizing the expense items by the categories, in the order of air fare, ground transport, vehicle rental, private automobile, fuel, parking, registration, accommodation, meal, then supplies.

As a claimant, I want a notification when an expense claim is returned or approved, and there is connectivity.

Expense Claims / Native Currency

As a claimant, I want to note my native currency in which payments are made.

As a claimant, I want each expense item for which a foreign currency value was entered and later replaced by the equivalent native currency value to keep a record of the foreign currency value.

As a claimant, I want to compute the expense amount of a private automobile expense item by entering a rate in the native currency per kilometer and multiplying that rate by the distance traveled.

Expense Items / Receipt Reading

As a claimant, I want to request that a photograph attached to an editable expense item be read, so that the date, category, textual description, amount spent, and unit of currency is entered for me when there is connectivity.

As a claimant, I want an indicator to show whether a receipt read request succeeded or failed.

As a receipt reader, I want to view receipt reading requests, and for each one, update the associated expense item with the date, category, textual description, amount spent, and unit of currency, and indicate success or failure.

2016 F Project Problem Description

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

Project Problem Description

Warning: This is subject to change! 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. We want a mobile application that allows drivers to search for recent ride requests, and for riders to post requests for rides. Riders will describe the start and end of their ride and their suggested payment. Drivers will browse for nearby requests and accept ride requests that they are willing to fulfil.

In general, a user can be both a driver and a rider.

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. New requirements will be introduced for the final project part.

Requests

US 01.01.01 As a rider, I want to request rides between two locations. US 01.02.01 As a rider, I want to see current requests I have open. US 01.03.01 As a rider, I want to be notified if my request is accepted. US 01.04.01 As a rider, I want to cancel requests. US 01.05.01 As a rider, I want to be able to phone or email the driver who accepted a request. US 01.06.01 As a rider, I want an estimate of a fair fare to offer to drivers. US 01.07.01 As a rider, I want to confirm the completion of a request and enable payment. US 01.08.01 As a rider, I want to confirm a driver's acceptance. This allows us to choose from a list of acceptances if more than 1 driver accepts simultaneously.

US 1.09.01 (added 2016-11-14) As a rider, I should see a description of the driver's vehicle.

US 1.10.01 (added 2016-11-14) As a rider, I want to see some summary rating of the drivers who accepted my offers.

US 1.11.01 (added 2016-11-14) As a rider, I want to rate a driver for his/her service (1-5).

Status

US 02.01.01 As a rider or driver, I want to see the status of a request that I am involved in User profile US 03.01.01 As a user, I want a profile with a unique username and my contact information. US 03.02.01 As a user, I want to edit the contact information in my profile. US 03.03.01 As a user, I want to, when a username is presented for a thing, retrieve and show its contact information.

US 03.04.01 (added 2016-11-14) As a driver, in my profile I can provide details about the vehicle I drive.

Searching

US 04.01.01 As a driver, I want to browse and search for open requests by geo-location. US 04.02.01 As a driver, I want to browse and search for open requests by keyword.

US 04.03.01 (added 2016-11-14) As a driver, I should be able filter request searches by price per KM and price.

US 04.04.01 (added 2016-11-14) As a driver, I should be able to see the addresses of the requests.

US 04.05.01 (added 2016-11-14) As a driver, I should be able to search by address or nearby an address.

Accepting

US 05.01.01 As a driver, I want to accept a request I agree with and accept that offered payment upon completion. US 05.02.01 As a driver, I want to view a list of things I have accepted that are pending, each request with its description, and locations. US 05.03.01 As a driver, I want to see if my acceptance was accepted. US 05.04.01 As a driver, I want to be notified if my ride offer was accepted.

Offline behavior

US 08.01.01 As an driver, I want to see requests that I already accepted while offline. US 08.02.01 As a rider, I want to see requests that I have made while offline. US 08.03.01 As a rider, I want to make requests that will be sent once I get connectivity again. US 08.04.01 As a driver, I want to accept requests that will be sent once I get connectivity again.

Location

US 10.01.01 As a rider, I want to specify a start and end geo locations on a map for a request. US 10.02.01 As a driver, I want to view start and end geo locations on a map for a request.

Requirements cluster 1: US 1.09.01 (car details) US 03.04.01 (car details) US 04.03.01 (price search) US 1.10.01 (ratings) US 1.11.01 (ratings)

Requirements cluster 2: US 1.09.01 (car details) US 03.04.01 (car details) US 04.03.01 (price search) US 04.04.01 (addresses) US 04.05.01 (addresses)

2016 W Project Problem Description

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

Project Problem Description

Warning: This is subject to change!

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. We want a mobile application that allows owners to record the things they have and share them with borrowers. For example, a thing could be a good (like a piece of camera equipment), a service (like giving a ride in a car), or a resource (like a parking spot). Generally, a thing should be something reusable and typical underused. It is up to each team to choose some specific thing of focus, with approval from the TA.

In general, a user can be both an owner of their own things and a borrower of someone else's things. A borrower can borrow a thing by making a monetary bid for it. The owner can accept a bid, so the thing becomes borrowed. The owner can denote when a borrowed thing is returned and available again.

Needs in (Partial) User Story Form

Things

US 01.01.01 As an owner, I want to add a thing in my things, each denoted with a clear, suitable description. US 01.02.01 As an owner, I want to view a list of all my things, and their descriptions and statuses. US 01.03.01 As an owner, I want to view one of my things, its description and status. US 01.04.01 As an owner, I want to edit a thing in my things. US 01.05.01 As an owner, I want to delete a thing in my things.

Status

US 02.01.01 As an owner or borrower, I want a thing to have a status of one of: available, bidded, or borrowed. User profile US 03.01.01 As a user, I want a profile with a unique username and my contact information. US 03.02.01 As a user, I want to edit the contact information in my profile. US 03.03.01 As a user, I want to, when a username is presented for a thing, retrieve and show its contact information.

Searching

US 04.01.01 As a borrower, I want to specify a set of keywords, and search for all things not currently borrowed whose description contains all the keywords. US 04.02.01 As a borrower, I want search results to show each thing not currently borrowed with its description, owner username, and status.

Bidding

US 05.01.01 As a borrower, I want to bid for an available thing, with a monetary rate (in dollars per hour). US 05.02.01 As a borrower, I want to view a list of things I have bidded on that are pending, each thing with its description, owner username, and my bid. US 05.03.01 As an owner, I want to be notified of a bid. US 05.04.01 As an owner, I want to view a list of my things with bids. US 05.05.01 As an owner, I want to view the bids on one of my things. US 05.06.01 As an owner, I want to accept a bid on one of my things, setting its status to borrowed. (Any other bids are declined.) US 05.07.01 As an owner, I want to decline a bid on one of my things.

Borrowing

US 06.01.01 As a borrower, I want to view a list of things I am borrowing, each thing with its description and owner username. US 06.02.01 As an owner, I want to view a list of my things being borrowed, each thing with its description and borrower username.

Returning

US 07.01.01 As an owner, I want to set a borrowed thing to be available when it is returned.

Offline behavior

US 08.01.01 As an owner, I want to define new things while offline, and push the additions once I get connectivity.

Photographs

US 09.01.01 (added 2016-02-29) As an owner, I want to optionally attach a photograph to a thing of mine.

US 09.02.01 (added 2016-02-29) As an owner, I want to delete any attached photograph for a thing of mine.

US 09.03.01 (added 2016-02-29) As an owner or borrower, I want to view any attached photograph for a thing.

US 09.04.01 (added 2016-02-29) As a sys admin, I want each photograph to be under 65536 bytes in size.

Location

US 10.01.01 (added 2016-02-29) As an owner, I want to specify a geo location on a map of where to receive a thing when I accept a bid on the thing.

US 10.02.01 (added 2016-02-29) As a borrower, I want to view the geo location of where to receive a thing I will be borrowing.

"Wow"

Non-trivial requirement(s) on approval from your TA (added 2016-03-11)

2017 F Project Problem Description

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

Project Problem Description

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 developers to extend or migrate it. To assist in forming good habits, we want a mobile application that allows one to track, encourage, and share their habits. Recurring habits could be, for example, "write a joke", "eat breakfast", "exercise dog", "call family", and "no car accident". The intent is to make such habits: regular (e.g., daily), unbroken (so missed habit events are noted), and shared (so there's public pressure not to miss).

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.

Habits

US 01.01.01 As a participant, I want to add a new type of habit, giving it a brief title, reason, and date to start. US 01.02.01 As a participant, I want a habit to have a plan for what days of the week it should regularly occur. US 01.03.01 As a participant, I want to view a given habit and its details. US 01.04.01 As a participant, I want to edit the details of a habit of mine. US 01.05.01 As a participant, I want to delete a habit of mine. US 01.06.01 As a participant, I want a habit title to be no more than 20 characters and habit reason to be no more than 30 characters. US 01.07.01 As a participant, I want to see what habits I need to do today. US 01.08.01 As a participant, I want for each habit type, a visual and statistical habit status indicator to show how closely I am following its plan.

Habit Events

US 02.01.01 As a participant, I want to add a habit event to my habit history when I have done a habit as planned. US 02.02.01 As a participant, I want a habit event to have an optional comment of no more than 20 characters. US 02.03.01 As a participant, I want a habit event to have an optional photograph to record what happened. US 02.04.01 As a participant, I want to view a given habit event and all its available details. US 02.05.01 As a participant, I want to edit the details of a habit event of mine. US 02.06.01 As a participant, I want to delete a habit event of mine. US 02.07.01 As a system administrator, I want the storage for each photographic image to be under 65536 bytes.

Profile

US 03.01.01 As a participant, I want to be uniquely identifiable. Habit History US 04.01.01 As a participant, I want to view as a list my habit history, sorted in reverse chronological order (most recent coming first). US 04.02.01 As a participant, I want to filter my habit history list to show only a particular type of habit. US 04.03.01 As a participant, I want to filter my habit history list to show only habit events whose comment text contains a given word.

US 05.01.01 As a participant, I want to ask another participant to follow the statuses of all their habits, and follow for each of their habits, its most recent event. US 05.02.01 As a participant, I want to grant another participant permission to follow the statuses of all my habits, and follow for each of my habits, its most recent event. US 05.03.01 As a participant, I want to view as a list the habit statuses of the participants I am granted to follow, ordered by participant identifier then habit title. Geolocation and Maps US 06.01.01 As a participant, I want to optionally attach my current location to a habit event. US 06.02.01 As a participant, I want to see a map of the habit events (that have locations) from my filtered habit history list. US 06.03.01 As a participant, I want to see a map of the recent habit events (that have locations) from participants I am following. US 06.04.01 As a participant, I want to highlight habit events of mine or by participants I am following that are within 5 km of my current location.

Offline Behavior

US 07.01.01 As a participant, I want to add, edit, or delete a habit event while offline, and have any of these changes synchronized once I get connectivity.

"Wow" Factor

Non-trivial requirement(s) of your choice that fit with the app, on approval from your TA An example could be collecting kudos or badges from other participants. Another example could be partnering for certain habits, like "play tennis".

2017 W Project Problem Description

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

Project Problem Description

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 developers to extend or migrate it. To assist in understanding the emotional states and triggers of individuals and groups, we want a mobile application that allows one to post, track, and share their moods. For university students or staff, this could allow a clearer picture of their experiences, perceptions, and mental well-being in the face of challenges in academic life.

Needs in (Partial) User Story Form

Moods

US 01.01.01 As a participant, I want to add a mood event to my mood history, each event with the current date and time, a required emotional state, optional trigger, and optional social situation. US 01.02.01 As a participant, I want the emotional states to include at least: anger, confusion, disgust, fear, happiness, sadness, shame, and surprise. US 01.03.01 As a participant, I want consistent emoticons and colors to depict and distinguish the emotional states in any view. US 01.04.01 As a participant, I want to view a given mood event and all its available details. US 01.05.01 As a participant, I want to edit the details of a given mood event of mine. US 01.06.01 As a participant, I want to delete a given mood event of mine.

Other Details

US 02.01.01 As a participant, I want to express the reason why for a mood event using a brief textual explanation (no more than 20 characters or 3 words). US 02.02.01 As a participant, I want to express the reason why for a mood event using a photograph. US 02.03.01 As a system administrator, I want the storage for each photographic image to be under 65536 bytes. US 02.04.01 As a participant, I want to specify the social situation for a mood event to be one of: alone, with one other person, with two to several people, or with a crowd.

Profile

US 03.01.01 As a user, I want a profile with a unique username.

Mood History

US 04.01.01 As a participant, I want to view as a list my mood history, sorted by date and time, in reverse chronological order (most recent coming first). US 04.02.01 As a participant, I want to filter my mood history list to show only mood events that occurred in the most recent week. US 04.03.01 As a participant, I want to filter my mood history list to show only mood events with a particular emotional state. US 04.04.01 As a participant, I want to filter my mood history list to show only mood events whose reason why text contains a given word.

US 05.01.01 As a participant, I want to ask another participant to follow their most recent mood event. US 05.02.01 As a participant, I want to grant another participant permission to follow my most recent mood event. US 05.03.01 As a participant, I want to view as a list the most recent mood events of the participants I am granted to follow, sorted by date and time, in reverse chronological order (most recent coming first). US 05.04.01 As a participant, I want to filter my mood following list to show only mood events that occurred in the most recent week. US 05.05.01 As a participant, I want to filter my mood following list to show only mood events with a particular emotional state. US 05.06.01 As a participant, I want to filter my mood following list to show only mood events whose reason why text contains a given word.

Geolocation and Maps

US 06.01.01 As a participant, I want to optionally attach my current location to a mood event. US 06.02.01 As a participant, I want to see a map of the mood events (showing their emotional states) from my filtered mood history list (that have locations). US 06.03.01 As a participant, I want to see a map of the mood events (showing their emotional states and the username) from my filtered mood following list (that have locations). US 06.04.01 As a participant, I want to see a map of the most recent mood event of every participant (showing their emotional states) if the event has a location and is within 5 km of my current location.

Offline Behavior

US 07.01.01 As a participant, I want to add, edit, or delete a mood event while offline, and have any of these changes synchronized once I get connectivity.

"Wow" Factor

Non-trivial requirement(s) that fit with the app on approval from your TA

2018 F Project Problem Description

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

Project Problem Description

Warning: This is subject to change!

User's Problem Description

Thus I want software that will run on my phone and allow me to take photos of skin issues and notes about medical issues I might have. These photos and notes will be for my own sanity as well I can provide them to physicians when they are needed.

Each photo or note should be timestamped and associated with a problem. Each photo or note should optionally be mapped to a location. Each photo or note should be associated with a location on my body which I can indicate by clicking on paper-doll-cut-out-like image of myself. So if my left arm was affected, I'd click on my left arm on a picture of myself--that body location would recorded. If I suffer headaches near smokestacks I probably want to record the GPS location as well.

Thus as a user I want to be able to track and document medical issues. I want to use my cellphone to help me document all the blemishes and marks, and other stuff on my body such that I can keep track of them.

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.

Task Basics

US 01.01.01

As a patient I want to record my problems, each denoted with a title, date started, and a brief description.

US 01.01.02 (added 2018-02-14) As a patient, I want the maximum length of the task title to be at least 30 characters.

US 01.01.03 (added 2018-02-14) As a patient, I want the maximum length of the task description to be at least 300 characters.

US 01.02.01 As a patient, I want to view a list of my problems, with their titles, dates, and number of records.

US 01.03.01 (revised 2018-02-16) As a patient, I want to edit the details for any one of my problems.

US 01.04.01 As a patient, I want to delete a problem of mine.

US 01.05.01

As a patient I want to add records (photos, locations, comments) to problems.

Record Details

US 02.01.01 As a patient or care provider, I want to view all the records for a given problem, including its title, description, photo, etc.

US 02.02.01 As a patient, I want to add records to problems.

US 02.03.01 As a patient, records can have a geo-location.

US 02.04.01 As a patient, records can have a body location.

US 02.05.01 As a patient, records can have a title and comment.

US 02.06.01 As a patient, records can have a photo.

US 02.07.01 As care provider, I want to add new comment records to a problem for my patients.

US 02.08.01 As a patient, records have a timestamp.

US 02.09.01

As a patient, I want some method of helping me take consistent photos, so that when I show the doctor any progression such as the growth of a mole is evident.

US 02.10.01

As a patient, I need to have a slideshow mode whereby photo records of a problem can be browsed by clicking. So I could "animate” changes to a doctor.

User Profile

US 03.01.01 As a patient, I want a profile with a unique userid and my contact information.

US 03.01.02 As a patient, I want the minimum userid to be at least 8 characters.

US 03.01.03 As a patient, I want the contact information to include an email address and a phone number.

US 03.02.01 As a patient, I want to edit the contact information in my profile.

US 03.03.01 As a patient or care provider, I want to, whenever a username is shown, be able to retrieve and see its corresponding contact information.

US 03.04.01 new

As a patient or care provider, I do not want to have to ever use a password, remember a password, or have to care about a password. If I need security tokens or anything like that it must be hidden from me.

US 03.05.01 *new

As a patient or care provider, when I use a new device I want to be able to use the same profile.

US 03.06.01 new

As a patient, I want to be able to share a very short code, or something visually scannable by a photo camera, with a care provider so they can add my profile.

US 03.07.01 new

As a patient, I want to be able to share a very short code, or something visually scannable by a photo camera, with myself so I can enable a new device to browse as me.

Searching

US 04.01.01 As a patient or care provider, I want to specify a set of keywords, and search for all problems or records that contains all the keywords.

US 04.02.01 As a patient or care provider, I want to specify a set of keywords, and search for all problems or records that are near a particular Geo-location.

US 04.03.01 As a patient or care provider, I want to specify a set of keywords, and search for all problems or records that are near a particular body-location.

Patient Assigned

US 06.01.01 As a care provider, I want to view a list of patients I am assigned to.

Care Provider

US 07.01.01

As a care provider, I want to add patients that I am assigned to.

US 07.01.02

As a care provider, I want to want to browse my patients problems.

US 07.01.03

As a care provider, I want to add comment records to my patients' problems

Offline behavior

US 08.01.01 As a patient, I want to add or edit problems and records while off the network, and have these changes synchronized once I regain connectivity.

Photographs

US 09.01.01 As a patient, I want to optionally attach one or more photographs as further viewable details to a record of mine.

US 09.01.02 (added 2018-04-06) As a patient, I want the maximum number of photographs that can be attached to a record to be at least 10.

US 09.02.01 As a patient or care provider, I want to view any attached photograph for a record.

US 09.03.01 As a sys admin, I want each photograph to be under 65536 bytes in size.

Geolocation and Maps

US 10.01.01 As a patient, I want to specify a geo location on a map of a record.

US 10.02.01 As a patient or provider, I want to view any geo location for a record, on a map.

US 10.03.01 As a patient or care provider, I want to see a map of all records for a patient (that have locations).

Body-locations

US 11.01.01

As a patient, I want to upload at least front and back body-location photos so I may indicate where photo records were taken on my body.

US 11.02.01

As a patient, body locations are effectively a reference to a body-location photo and a point location on the photo.

US 11.03.01

As a patient, I should be able to have at least 2 body location pictures.

US 11.04.01

As a patient, when I view a body location it should be a clear indicator of a point on a body-location picture.

US 11.05.01 new

As a patient, when making a record I want to choose from available body locations to associate with a photo or a record.

US 11.06.01 new

As a patient, I should be able to add body location photos.

US 11.07.01 new

As a patient, I should be able to remove body location photos.

US 11.08.01 new

As a patient, I should be able to label body location photos.

US 11.09.01 new

As a patient, I want body-location photos stored locally on my device (and remotely) so that access to them is fast.

Sys-admin

US 12.01.01 new

As a sysadmin, I want to use a Free/Libre Open Source Software service-side tool such as Elasticsearch to host this application. No proprietary software for data-hosting.

"Wow" Factor

Non-trivial, visible requirement(s) of your choice that fit with the app, on approval from your TA. This should be decided for the initial use cases.

An example could be a nice UI for the paper-cut-out-doll view. Another could be dealing with records (that have locations) from a map view.

Another wow factor could be encryption---if you can encrypt photos that are uploaded.

2018 W Project Problem Description

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

Project Problem Description

Warning: This is subject to change!

We want a mobile application that allows task requesters to post the tasks they would like done by task providers. For example, a task could be giving a ride in a car or delivering a package, within the city.

In general, a user of the app could be both a task requester and a task provider. A task provider can offer their service by making a monetary bid on a task. The task requester can accept a bid, so the task is assigned to the winning task provider. The task requester can denote when the task is done.

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.

Task Basics

US 01.01.01 As a task requester, I want to add a task to my tasks, each denoted with a title, brief description, and initial status: requested.

US 01.01.02 (added 2018-02-14) As a task requester, I want the maximum length of the task title to be at least 30 characters.

US 01.01.03 (added 2018-02-14) As a task requester, I want the maximum length of the task description to be at least 300 characters.

US 01.02.01 As a task requester, I want to view a list of my tasks, with their titles and statuses.

US 01.03.01 (revised 2018-02-16) As a task requester, I want to edit the details for any one of my tasks with status: requested.

US 01.04.01 As a task requester, I want to delete a task of mine.

Task Details

US 02.01.01 As a task requester or provider, I want to view all the details for a given task, including its title, description, status, and lowest bid so far (if any).

US 02.02.01 As a task requester or provider, I want a task to have a status to be one of: requested, bidded, assigned, or done.

Bidded means at least one provider bidded on the task.

User Profile

US 03.01.01 As a user, I want a profile with a unique username and my contact information.

US 03.01.02 (added 2018-02-16) As a user, I want the maximum length of a username to be at least 8 characters.

US 03.01.03 (added 2018-02-16) As a user, I want the contact information to include an email address and a phone number.

US 03.02.01 As a user, I want to edit the contact information in my profile.

US 03.03.01 As a user, I want to, whenever a username is shown, be able to retrieve and see its corresponding contact information.

Searching

US 04.01.01 As a task provider, I want to specify a set of keywords, and search for all tasks, with status: requested or bidded, whose description contains all the keywords.

US 04.02.01 As a task provider, I want search results to show each task with its task requester username, title, status, lowest bid so far (if any).

Task Bidding

US 05.01.01 As a task provider, I want to make a bid on a given task with status: requested or bidded, using a monetary amount.

US 05.02.01 (revised 2018-02-14) As a task provider, I want to view a list of tasks that I have bidded on, each with its task requester username, title, status, lowest bid so far, and my bid.

US 05.03.01 As a task requester, I want to be notified of a bid on my tasks.

US 05.04.01 As a task requester, I want to view a list of my tasks with status bidded, each having one or more bids.

US 05.05.01 As a task requester, I want to view the bids on one of my tasks.

US 05.06.01 (revised 2018-03-28) As a task requester, I want to accept a bid on one of my tasks, setting its status to assigned, and declining any other bids on that task.

US 05.07.01 (revised 2018-03-28) As a task requester, I want to decline a bid on one of my tasks.

Declining may be done by marking the bid as such or hiding it.

Task Assigned

US 06.01.01 As a task provider, I want to view a list of tasks I am assigned, each task with its task requester username, title, status, and my accepted bid.

US 06.02.01 As a task requester, I want to view a list of my tasks with status: assigned, each task with its task provider username, title, status, and accepted bid.

Task Done

US 07.01.01 As a task requester, I want to set a task with status: assigned to have status: done, when it is completed.

US 07.02.01 (revised 2018-03-28) As a task requester, I want to set a task with status: assigned to have status: requested, when it is not completed and there are no other bids on it.

US 07.03.01 (added 2018-03-28) As a task requester, I want to set a task with status: assigned to have status: bidded, when it is not completed and there are other bids on it.

Offline behavior

US 08.01.01 As a task requester, I want to add or edit tasks while off the network, and have these changes synchronized once I regain connectivity.

Photographs

US 09.01.01 As a task requester, I want to optionally attach one or more photographs as further viewable details to a task of mine.

US 09.01.02 (added 2018-04-06) As a task requester, I want the maximum number of photographs that can be attached to a task to be at least 10.

US 09.02.01 As a task requester or provider, I want to view any attached photograph for a task.

US 09.03.01 As a sys admin, I want each photograph to be under 65536 bytes in size.

Geolocation and Maps

US 10.01.01 As a task requester, I want to specify a geo location on a map as further viewable details to a task of mine.

US 10.02.01 As a task requester or provider, I want to view any geo location for a task, on a map.

US 10.03.01 As a task provider, I want to see a map of all tasks (that have locations), with status: requested or bidded, that are within 5 km of my current location.

"Wow" Factor

Non-trivial, visible requirement(s) of your choice that fit with the app, on approval from your TA. This should be decided for the initial use cases.

An example could be a way to rate task providers and see their ratings. Another could be dealing with tasks (that have locations) from a map view.

2019 F Project Problem Description

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

Warning: this is subject to change!

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 developers to extend or migrate it.

To assist in understanding the emotional states and triggers of individuals and groups, we want a mobile application that allows one to post, track, and share their moods.

For university students or staff that participate in using the app, this could allow a clearer picture of their experiences, perceptions, and mental well-being in the face of challenges in academic life.

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, clarify noticed issues, and add new needs. Talk to the customer and propose options, rather than making what might be an unwarranted assumption or interpretation.

Moods

US 01.01.01 As a participant, I want to add a mood event to my mood history, each event with the current date and time, a required emotional state, optional reason, and optional social situation.

US 01.02.01 As a participant, I want consistent emoticons and colors to depict and distinguish the emotional states in any view.

US 01.03.01 As a participant, I want to view a given mood event and all its available details.

US 01.04.01 As a participant, I want to edit the details of a given mood event of mine.

US 01.05.01 As a participant, I want to delete a given mood event of mine.

Other Mood Details

US 02.01.01 As a participant, I want to express the reason why for a mood event using a brief textual explanation (no more than 20 characters or 3 words).

US 02.02.01 As a participant, I want to express the reason why for a mood event using a photograph.

US 02.03.01 As a participant, I want to specify the social situation for a mood event to be one of: alone, with one other person, with two to several people, or with a crowd.

Profile

US 03.01.01 As a user, I want a profile with a unique username.

Mood History

US 04.01.01 As a participant, I want to view as a list my mood history, sorted by date and time, in reverse chronological order (most recent coming first).

US 04.02.01 As a participant, I want to filter my mood history list to show only mood events with a particular emotional state.

US 05.01.01 As a participant, I want to ask another participant to follow their most recent mood event.

US 05.02.01 As a participant, I want to grant another participant permission to follow my most recent mood event.

US 05.03.01 As a participant, I want to view as a list the most recent mood events of the other participants I am granted to follow, sorted by date and time, in reverse chronological order (most recent coming first).

Geolocation and Maps

US 06.01.01 As a participant, I want to optionally attach my current location to a mood event.

US 06.02.01 As a participant, I want to see a map of the mood events (showing their emotional states) from my mood history list (that have locations).

US 06.03.01 As a participant, I want to see a map of the mood events (showing their emotional states and the username) from my mood following list (that have locations).

2019 W Project Problem Description

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

Project Problem Description

Warning: This is subject to change!

We want a mobile application that allows owners to record the books they have and loan them to borrowers.

In general, a user can be both an owner of their own books and a borrower of someone else's books. A borrower can borrow an available book by making a request for it. The owner can accept such a request. When the book is handed over, the book becomes borrowed. The owner can denote when a borrowed book is returned and available again.

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. New requirements will be introduced for the final project part.

Books

US 01.01.01 As an owner, I want to add a book in my books, each denoted with a clear, suitable description (at least title, author, and ISBN).

US 01.02.01 As an owner, I want the book description by scanning it off the book (at least the ISBN).

US 01.03.01 As an owner or borrower, I want a book to have a status of one of: available, requested, accepted, or borrowed.

US 01.04.01 As an owner, I want to view a list of all my books, and their descriptions, statuses, and current borrowers.

US 01.05.01 As an owner, I want to view a list of all my books, filtered by status.

US 01.06.01 As an owner, I want to view and edit a book description in my books.

US 01.07.01 As an owner, I want to delete a book in my books.

User profile

US 02.01.01 As an owner or borrower, I want a profile with a unique username and my contact information.

US 02.02.01 As an owner or borrower, I want to edit the contact information in my profile.

US 02.03.01 As an owner or borrower, I want to retrieve and show the profile of a presented username.

Searching

US 03.01.01 As a borrower, I want to specify a set of keywords, and search for all books that are not currently accepted or borrowed whose description contains all the keywords.

US 03.02.01 As a borrower, I want search results to show each book not currently accepted or borrowed with its description, owner username, and status.

Requesting

US 04.01.01 As a borrower, I want to request a book that is not currently accepted or borrowed.

US 04.02.01 As a borrower, I want to view a list of books I have requested, each book with its description, and owner username.

US 04.03.01 As an owner, I want to be notified of a request.

US 04.04.01 As an owner, I want to view all the requests on one of my books.

Accepting

US 05.01.01 As an owner, I want to accept a request on one of my books. (Any other requests are declined.)

US 05.02.01 As an owner, I want to decline a request on one of my books.

US 05.03.01 As a borrower, I want to be notified of an accepted request.

US 05.04.01 As a borrower, I want to view a list of books I have requested that are accepted, each book with its description, and owner username.

Borrowing

US 06.01.01 As an owner, I want to hand over a book by scanning the book ISBN code and denoting the book as borrowed.

US 06.02.01 As a borrower, I want to receive an accepted book by scanning the book ISBN code to confirm I have borrowed it.

US 06.03.01 As a borrower, I want to view a list of books I am borrowing, each book with its description and owner username.

Returning

US 07.01.01 As a borrower, I want to hand over a book I borrowed by scanning the book ISBN code to denote the book as available.

US 07.02.01 As an owner, I want to receive a returned book by scanning the book ISBN code to confirm I have it available.

Photographs

US 08.01.01 As an owner, I want to optionally attach a photograph to a book of mine.

US 08.02.01 As an owner, I want to delete any attached photograph for a book of mine.

US 08.03.01 As an owner or borrower, I want to view any attached photograph for a book.

Location

US 09.01.01 As an owner, I want to specify a geo location on a map of where to receive a book when I accept a request on the book.

US 09.02.01 As a borrower, I want to view the geo location of where to receive a book I will be borrowing.

"Wow"

Non-trivial requirement(s) on approval from your TA.

2020 F Project Problem Description

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

Warning: This is subject to change!

We want a mobile application that allows owners to record the books they have and loan them to borrowers.

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. New requirements will be introduced for the final project part.

Books

US 01.01.01 As an owner, I want to add a book in my books, each denoted with a clear, suitable description (at least title, author, and ISBN).

US 01.02.01 As an owner, I want the book description by scanning it off the book (at least the ISBN).

US 01.03.01 As an owner or borrower, I want a book to have a status to be one of: available, requested, accepted, or borrowed.

US 01.04.01 As an owner, I want to view a list of all my books, and their descriptions, statuses, and current borrowers.

US 01.05.01 As an owner, I want to view a list of all my books, filtered by status.

US 01.06.01 As an owner, I want to view and edit a book description in my books.

US 01.07.01 As an owner, I want to delete a book in my books.

User profile

US 02.01.01 As an owner or borrower, I want a profile with a unique username and my contact information.

US 02.02.01 As an owner or borrower, I want to edit the contact information in my profile.

US 02.03.01 As an owner or borrower, I want to retrieve and show the profile of a presented username.

Searching

US 03.01.01 As a borrower, I want to specify a keyword, and search for all books that are not currently accepted or borrowed whose description contains the keyword.

US 03.02.01 As a borrower, I want search results to show each book with its description, owner username, and status.

Requesting

US 04.01.01 As a borrower, I want to request a book that is not currently accepted or borrowed.

US 04.02.01 As a borrower, I want to view a list of books I have requested, each book with its description, owner username, and status.

US 04.03.01 As an owner, I want to be notified of a request.

US 04.04.01 As an owner, I want to view all the requests on one of my books.

Accepting

US 05.01.01 As an owner, I want to accept a request on one of my books. (Any other requests on the book are declined.)

US 05.02.01 As an owner, I want to decline a request on one of my books.

US 05.03.01 As a borrower, I want to be notified of an accepted request.

US 05.04.01 As a borrower, I want to view a list of books I have requested that are accepted, each book with its description, and owner username.

Borrowing

US 06.01.01 As an owner, I want to hand over a book by scanning the book ISBN code and denoting the book as borrowed.

US 06.02.01 As a borrower, I want to receive an accepted book by scanning the book ISBN code to confirm I have borrowed it.

US 06.03.01 As a borrower, I want to view a list of books I am borrowing, each book with its description and owner username.

Returning

US 07.01.01 As a borrower, I want to hand over a book I borrowed by scanning the book ISBN code to denote the book as available.

US 07.02.01 As an owner, I want to receive a returned book by scanning the book ISBN code to confirm I have it available.

Photographs

US 08.01.01 As an owner, I want to optionally attach a photograph to a book of mine.

US 08.02.01 As an owner, I want to delete any attached photograph for a book of mine.

US 08.03.01 As an owner or borrower, I want to view any attached photograph for a book.

Location

US 09.01.01 As an owner, I want to specify a geo location on a map of where to receive a book when I accept a request on the book.

US 09.02.01 As a borrower, I want to view the geo location of where to receive a book I will be borrowing.

2020 W Project Problem Description

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

Warning: This is subject to change!

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.

We want a mobile application that allows drivers to search for open and recent ride requests, and for riders to post requests for rides. Riders will describe the start and end of their ride and their suggested payment. Drivers will browse for nearby requests and accept ride requests that they are willing to fulfil. We're going to use the new baloney currency QR-Bucks! It's like an IOU but in QR code form!

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. New requirements will be introduced for the final project part.

Requests

US 01.01.01 As a rider, I want to request rides between two locations. US 01.02.01 As a rider, I want to see current request I have open. US 01.03.01 As a rider, I want to be notified if my request is accepted. US 01.04.01 As a rider, I want to cancel requests. US 01.05.01 As a rider, I want to be able to phone or email the driver who accepted a request. US 01.06.01 As a rider, I want an estimate of a fair fare to offer to drivers and I should be able to offer more. US 01.07.01 As a rider, I want to confirm the completion of a request and enable payment.

US 01.08.01 As a rider, I want to cancel a ride before the rider picks me up. US 1.10.01 As a rider, I want to see the driver's profile and ratings.

US 1.11.01 As a rider, I want to rate a driver for his/her service thumbs up or thumbs down.

Status

Searching

US 04.01.01 As a driver, I want to browse and search for open requests by geo-location.

Accepting

US 05.01.01 As a driver, I want to accept a request I agree with and accept that offered payment upon completion. US 05.02.01 As a driver, I want to view the current active request. US 05.03.01 As a driver, I want to be notified if my ride offer was accepted.

Offline behavior

US 06.01.01 As an driver, I want to see requests that I already accepted while offline. US 06.02.01 As a rider, I want to see the current request, even if I am offline.

Location

US 07.01.01 As a rider, I want to specify a start and end geo locations on a map for a request. US 07.02.01 As a driver, I want to view start and end geo locations on a map for a request.

Payment

US 08.01.01 As a rider I wish to generate a QR-Bucks QR Code for my driver to scan to pay them. US 08.02.01 As a driver I want to scan my rider's QR-Bucks to get paid!

Note: QR-Bucks do not exist yet, please enable the generation and scanning of QR-Bucks for payment. It can be dummy values like "Abram owes me $10.00"

2021 F Project Problem Description

2024-11-04T00: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 developers to extend or migrate it.

To assist in forming good habits, we want a mobile application that allows one to track, encourage, and share their habits. Recurring habits could be, for example, "write a joke", "eat breakfast", "exercise dog", "call family", and "no car accident". The intent is to make such habits: regular (e.g., daily), unbroken (so missed habit events are noted), and shared (so there's public pressure not to miss).

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.

Habits

US 01.01.01 [updated] As a doer, I want to add a habit, giving it a brief title, reason, date to start, and whether it is public or private.

US 01.02.01 As a doer, I want a habit to have a plan for what days of the week it should regularly occur.

US 01.03.01 As a doer, I want to view a given habit and its details.

US 01.04.01 As a doer, I want to edit the details of a habit of mine.

US 01.05.01 [updated] As a doer, I want to delete a habit of mine, and any corresponding habit events.

US 01.06.01 As a doer, I want a habit title to be up to 20 characters and habit reason to be up to 30 characters.

US 01.07.01 As a doer, I want to see what habits I need to do today.

US 01.08.01 As a doer, I want to see a list of all my habits.

US 01.08.02 [new] As a doer, I want to manually reorder habits on my list of habits.

US 01.09.01 As a doer, I want for each habit on the list, a visual indicator to show how closely I am following its plan over time.

Habit Events

US 02.01.01 As a doer, I want to denote a habit event when I have done a habit as planned.

US 02.02.01 As a doer, I want a habit event to have an optional comment of up to 20 characters.

US 02.03.01 As a doer, I want a habit event to have an optional photograph to record what happened.

US 02.03.02 [new] As a doer, I want the photograph for a habit event to be taken with the camera within the app.

US 02.04.01 As a doer, I want to view a given habit event and all its available details.

US 02.05.01 As a doer, I want to edit the details of a habit event of mine.

US 02.06.01 As a doer, I want to delete a habit event of mine.

Profile

US 03.01.01 As a doer, I want to be uniquely identifiable in the system.

US 05.01.01 [updated] As a doer, I want to ask another doer to follow all their public habits.

US 05.02.01 [updated] As a doer, I want to grant or deny another doer permission to follow all my public habits.

US 05.03.01 [updated] As a doer, I want to view the public habits and visual indicators of the other doers I am granted to follow.

Geolocation and Maps

US 06.01.01 [updated] As a doer, I want a habit event to have an optional location to record where it happened.

US 06.01.02 [new] As a doer, I want the location for a habit event to be specified using a map within the app, with the current phone position as the default location.

2021 W Project Problem Description

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

Warning: This is subject to change!

We want a mobile application that allows crowd-sourced testing of phenomona. There are 4 kinds of crowd-sourced tests: counts (how many did you see), binomial trials (pass fail), non-negative integer counts (each trial has 0 or more), measurement trials (like the temperature).

Count-based tests are about how many of something a person observed, it could be blue cars. Everytime they see a blue car they add 1 to the count seen. For instance you want to crowdsource how many blue cars are seen in Edmonton.

Binomial trials are trials where there's a chance to pass or fail. Users will repeat these trials and indicate pass or success. It could be a series of trials where you try to flip a water bottle upside down.

Non-negative integer counts are trials where each trial results in a non-negative integer results (usually a count). Such as if I drop a carton of eggs, how many eggs survive.

Measurement trials are repeated measurements and you record a decimal value of whatever was measured.

A chief experimenter (owner) describes and proposes a trial, gives rules and constraints that crowd experimenters will follow when they execute the trials. The crowd experimenters will look for trials that interest them, subscribe to trials and help execute and record trials for these experiments.

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. New requirements will be introduced for the final project part.

Experiment

US 01.01.01 As an owner, I want to publish an experiment with a description, a region, and a minimum number of trials.

US 01.02.01 As an owner, I want to unpublish an experiment.

US 01.03.01 As an owner, I want to end an experiment. This leaves the results available and public but does not allow new results to be added.

US 01.04.01 As an owner or experimenter, I want to subscribe to an experiment to participate in it.

US 01.05.01 As an experimenter, I want to be able to execute trials for an experiment and upload them to the experiment.

US 01.08.01 As an owner, I want to ignore certain experimenters results.

US 01.09.01 As an owner or experimenter, I want to observe statistics (quartiles, median, mean, stdev) about a current trials.

US 01.06.01 As an owner or experimenter, I want to see histograms of the results of trials.

US 01.07.01 As an owner or experimenter, I want to see plots of the results of trials over time.

Questions

US 02.01.01 As an experimenter, I want to ask a question about an experiment.

US 02.02.01 As an experimenter or owner, I want to ask to reply to questions about an experiment.

US 02.03.01 As an experimenter or owner, I want to browse questions and replies about an experiment.

QR Codes

US 03.01.01 As an experimenter, I want to be able to generate QR codes that I can print for a specific experiment and trial result (for instance PASS for a binomial trial I subscribed to).

US 03.02.01 As an experimenter, I want to be able scan QR codes to indicate success or failure, or increment counts for trials I subscribed to.

US 03.03.01 As an experimenter, I want to be able to register an arbitrary bar code (such as one off of your favourite book) to act a specific experiment result for a trial.

User profile

US 04.01.01 As an owner or experimenter, I want a profile with a unique username and my contact information.

US 04.02.01 As an owner or experimenter, I want to edit the contact information in my profile.

US 04.03.01 As an owner or experimenter, I want to retrieve and show the profile of a presented username.

US 04.04.01 new for Part 4

As an owner or experimenter, I do not want to log into my application using a username and password.

Searching

US 05.01.01 As an experimenter, I want to specify a keyword, and search for all experiments that are available.

US 05.02.01 As an experimenter, I want search results to show each experiment with its description, owner username, and status.

Location

US 06.01.01 As an owner, I want to specify a Geo-location is required or not for trials.

US 06.02.01 As an experimenter, I want to add Geo-location to experimental trials that need it.

US 06.03.01 As an experimenter, I want to be warned about geo-location trials.

US 06.04.01 As an experimenter, I want to see a map of geo-locations of a geo-location enabled expirement.

2022 W Project Problem Description

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

Project Problem Description

Warning: This is subject to change!

We want a mobile application that allows us to hunt for the coolest QR codes that score the most points. Players will run around scanning QR codes, barcodes, etc. trying to find barcodes and QR codes that give them the most points.

QR codes and barcodes (scannable codes) will be hashed and the hashes they produce will be analyzed and scored. A QR code that has certain properties like repeated nibbles or bytes (hex digits) will have a higher score than a QR code that does not. We have a proposed scoring system, but the implementers are free to use a different scoring system.

We want users to compete with each other for the highest scoring QR codes, the most QR codes, the highest sum of QR codes, or highest scoring QR codes in a region.

When a player scans a QR code they will take a photo of what or where the QR code is and also record the geolocation of the QR code.

Players can see on a map local QR codes that other players have scanned.

Scenario:

I open my QRHunter app. I see a QR code in my wallet. I indicate I want to add a new QR code and I use the phone camera to add the QR code. The QR code is scored and I’m told that my QR score is 30. The system prompts me for a photo of the object I scanned. I decline since this was an ID card. I also decline geolocation because it is in my wallet. The system adds the 30 points to my total score and records a hash of the QR code. I then see some sticker on a pole. I scan it and am told it is worth 1000 points! I record the geolocation and take a photo of the pole and save it to my account. 1000 points wow. Then I see that other users have found this pole as well. So I open the map for nearby QR codes and I see something worth 10000 is 100 meters away so I’m going to head on over there!

Needs in (Partial) User Story Form

Actors:

Player: a person who plays the game

Owner: the entity that owns 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 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.

Player

US 01.01.01

As a player, I want to add new QR codes to my account.

US 01.02.01

As a player, I want to see what QR codes I have added to my account.

US 01.0X.01

As a player, I want to remove QR codes from my account.

US 01.0X.01

As a player, I want to see my highest and lowest scoring QR codes.

US 01.0X.01

As a player, I want to see the sum of scores of QR codes that I have scanned.

US 01.0X.01

As a player, I want to see the total number of QR codes that I have scanned.

US 01.0X.01

As a player, I want to see other player’s profiles

Game QR Codes

US 02.0X.01

As a player, I want to be able to scan QR codes and record a photo of the location or object, and the geolocation of the location or object.

US 02.0X.01

As a player, I want to be able to comment on QR codes.

US 02.0X.01

As a player, I want to be able to browse QR codes that I own. (2022-03-08: Deleted because identical to US 01.02.01)

US 02.0X.01

As a player, I want to be able to browse QR codes that other players have scanned.

US 02.0X.01

As a player, I want to see that other players have scanned the same QR code.

Player QR Codes

US 03.0X.01

As a player, I want to be able to generate QR codes so that other players can scan my QR code to see my game status.

US 03.0X.01

As a player, I want to be able to generate a QR code so that I can log in to another device with the same account.

Player profile

US 04.01.01

As a player, I want a profile with a unique username and my contact information.

US 04.0X.01

As a player, I do not want to log into my application using a username and password as my device can identify me.

Searching

US 05.01.01

As a player, I want to search for other players by username.

US 05.0X.01

As a player, I want to search for nearby QR codes by using geolocation.

Location

US 06.01.01

As a player, I want to see a map of geo-locations of nearby QR codes.

Scoring

US 07.0X.01

As a player, I want to see game-wide high scores of all players.

US 07.0X.01

As a player, I want an estimate of my ranking for the highest scoring unique QR code.

US 07.0X.01

As a player, I want an estimate of my ranking for the total number of QR codes scanned.

US 07.0X.01

As a player, I want an estimate of my ranking for a total sum of scores of QR codes scanned.

Privacy

US 08.0X.01

As a player, I don’t want the actual code recorded. E.g., so I can scan and score my vaccine passport.

US 08.0X.01

As a player, I want to be able to decline recording geolocation for privacy reasons.

Owner

US 09.0X.01

As an owner, I don’t want to store big images online.

US 09.0X.01

As an owner, I want to be able to delete QR codes that are bad or malicious.

US 09.0X.01

As an owner, I want to be able to delete players.

Proposed Scoring System:

First, we calculate a SHA-256 hash of the QR code contents.

Example:

QR code contents: BFG5DGW54

Calculating SHA-256 hash:

@slate:~$ echo BFG5DGW54 | sha256sum 696ce4dbd7bb57cbfe58b64f530f428b74999cb37e2ee60980490cd9552de3a6 -

Then, based on the hexadecimal representation of the sha256, the score is calculated in the following way:

a "0" is 1 point

Many 0 in a row are multiplied by 20^(n-1) whereby n is the number of repeats

00 - 20^1 - 20

000 - 20^2 - 400

0000 - 20^3 - 8000

Same for other numbers

11 - 1

111 - 1

1111 - 1

22 - 2

222 - 4

2222 - 8

99 - 9

999 - 81

aa - 10

aaa - 100

ff - 15

fff - 225

So the best QR code would be made of all 0s or higher digits

For the QR code above

696ce4dbd7bb57cbfe58b64f530f428b74999cb37e2ee60980490cd9552de3a6

Let’s find the repeated digits

echo BFG5DGW54 | sha256sum | perl -lpe 'print "$1$2" while /([0-9a-f])(\1+)/g'

bb 999 ee 55

And calculate the score

bb - 11

999 - 9^2 - 81

ee - 14

55 - 5

Score: 11 + 81 + 14 + 5 = 111

Changelog:

2022-03-08: Deleted US 02.0X.01 ("As a player, I want to be able to browse QR codes that I own"). Reason: identical to US 01.02.01.

Old Lab Notes

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

Old Lab Notes

Class Participation Exercise 18

2024-10-24T00:00:00+05:00

Class Participation Exercise 18

Proper completion of this exercise is considered as part of course participation.

Which of these code smells are signs of "bloat", i.e., code, methods, and classes that have increased to an extent that they become hard to work with. - [ ] comments - [ ] duplicated code - [ ] long method - [ ] large class - [ ] data classes - [ ] data clumps - [ ] large parameter list - [ ] divergent change - [ ] shotgun surgery - [ ] feature envy - [ ] inappropriate intimacy - [ ] message chains - [ ] primitive obsession - [ ] switch statements - [ ] speculative generality - [ ] refused bequest

Which of these code smells are signs of incomplete or incorrect use of object-oriented design principles? - [ ] comments - [ ] duplicated code - [ ] long method - [ ] large class - [ ] data classes - [ ] data clumps - [ ] large parameter list - [ ] divergent change - [ ] shotgun surgery - [ ] feature envy - [ ] inappropriate intimacy - [ ] message chains - [ ] primitive obsession - [ ] switch statements - [ ] speculative generality - [ ] refused bequest

Which of these code smells are signs that change is difficult and likely expensive? - [ ] comments - [ ] duplicated code - [ ] long method - [ ] large class - [ ] data classes - [ ] data clumps - [ ] large parameter list - [ ] divergent change - [ ] shotgun surgery - [ ] feature envy - [ ] inappropriate intimacy - [ ] message chains - [ ] primitive obsession - [ ] switch statements - [ ] speculative generality - [ ] refused bequest

Which of these code smells are signs of something unnecessary, which if avoided would lead to cleaner, more efficient, and easier to understand code? - [ ] comments - [ ] duplicated code - [ ] long method - [ ] large class - [ ] data classes - [ ] data clumps - [ ] large parameter list - [ ] divergent change - [ ] shotgun surgery - [ ] feature envy - [ ] inappropriate intimacy - [ ] message chains - [ ] primitive obsession - [ ] switch statements - [ ] speculative generality - [ ] refused bequest

Which of these code smells are signs of excessive coupling between classes? - [ ] comments - [ ] duplicated code - [ ] long method - [ ] large class - [ ] data classes - [ ] data clumps - [ ] large parameter list - [ ] divergent change - [ ] shotgun surgery - [ ] feature envy - [ ] inappropriate intimacy - [ ] message chains - [ ] primitive obsession - [ ] switch statements - [ ] speculative generality - [ ] refused bequest

Consider the following piece of code:

// Order.java

package com.nq.util;

import java.io.*;
import java.util.*;
import java.lang.*;

public class Order {

    private lineitemlist lineItemList;

    public Order(lineitemlist lis) {
        lineItemList = lis;
    }

    public boolean equals(Object aThat) {
            if ( this == aThat ) return true;
        if ( !(aThat instanceof Order) ) return false;
            Order that = (Order)aThat;
        return this.lineItemList.equals(that.lineItemList);
    }

    // writes this order object to the specified print writer
    public void writeOrder(Order order, PrintWriter pw) {
        // get a vector of line items
        Vector lineItems = order.getLineItemList().getLineItems();

        // ------------------------------------------------------
        // calculate total
        // ------------------------------------------------------
        // create an iterator for the vector
        Iterator iter = lineItems.iterator();
        lineItem item;
        // set total to zero
        int total = 0;
            while (iter.hasNext()) {
                item = (lineItem)iter.next();

                // calculate total for line item
                int unitPrice = item.getUnitPrice();
                int qty = item.getQuantity();
                int lineitemtotal = unitPrice * qty;

                total += lineitemtotal;
            }
        // ------------------------------------------------------
        // END calculate total
        // ------------------------------------------------------

        // ------------------------------------------------------
        // write order
        // ------------------------------------------------------
        // create an iterator for the vector
        iter = lineItems.iterator();
            while (iter.hasNext()) {
                item = (lineItem)iter.next();

                // calculate total for line item
                int unitPrice = item.getUnitPrice();
                int qty = item.getQuantity();
                int productID = item.getProductID();
                int imageID = item.getImageId();
                int lineitemtotal = unitPrice * qty;

                pw.println("Begin Line Item");
                pw.println("Product = " + productID);
                pw.println("Image = " + imageID);
                pw.println("Quantity = " + qty);
                pw.println("Total = " + lineitemtotal);
                pw.println("End Line Item");
            }
        pw.println("Order total = " + total);
    }

    public int getTotal() {
        // get a vector of line items
        Vector lineItems = lineItemList.getLineItems();
        // create an iterator for the vector
        Iterator iter = lineItems.iterator();
        lineItem item;
        // set total to zero
        int total = 0;
            while (iter.hasNext()) {
                item = (lineItem)iterator.next();

                // calculate total for line item
                int unitPrice = item.getUnitPrice();
                int qty = item.getQuantity();
                int lineitemtotal = unitPrice * qty;

                total += lineitemtotal;
            }
            return total;
    }
}

// lineitemlist.java

package com.nq.util;

import java.io.*;
import java.util.*;
import java.lang.*;

class lineitemlist {
    private Vector LIList;

    public void setLineItems(Vector lineItems) {
        LIList = lineItems;
    }

    Vector getLineItems() {
        return LIList;
    }
}

// lineItem.java

package com.nq.util;

import java.io.*;
import java.util.*;
import java.lang.*;

class lineItem {
    protected int productId;
    private int ImageID;
    private int qty;
    private int Unitprice;

    public lineItem(int prodID, int ImageID, int inQty) {
        productId = prodID;
        this.ImageID = ImageID;
        qty = inQty;
    }

    public void setLineItems(Vector lineItems) {
        LineItems = lineItems;
    }

    Vector getLineItems() {
        return LineItems;
    }

    int getProductID() {
        return productId;
    }

    int getImageID() {
        return imageID;
    }

    int getQuantity() {
        return qty;
    }

    int getUnitPrice() {
        return Unitprice;
    }

    public void setProductID(int id) {
        productId = id;
    }

    public void setImageID(int ID) {
        imageID = ID;
    }

    public void setQty(int qty) {
        this.qty = qty;
    }

    public void setUnitPrice(int i) {
        Unitprice = i;
    }
}

What code smells are evident? For each, briefly describe its occurrence(s) in the code.

Occurrence(s) of "comments" code smell:

Occurrence(s) of "duplicated code" code smell:

Occurrence(s) of "long method" code smell:

Occurrence(s) of "large class" code smell:

Occurrence(s) of "data classes" code smell:

Occurrence(s) of "data clumps" code smell:

Occurrence(s) of "large parameter list" code smell:

Occurrence(s) of "divergent change" code smell:

Occurrence(s) of "shotgun surgery" code smell:

Occurrence(s) of "feature envy" code smell:

Occurrence(s) of "inappropriate intimacy" code smell:

Occurrence(s) of "message chains" code smell:

Occurrence(s) of "primitive obsession" code smell:

Occurrence(s) of "switch statements" code smell:

Occurrence(s) of "speculative generality" code smell:

Occurrence(s) of "refused bequest" code smell:

Other occurrence(s) of inconsistent or nonstandard coding:

Practice w23hm2q1

2024-10-18T00:00:00+05:00

CRC Cards

Engage in Object-Oriented Analysis and read the following scenario paragraph and pull out potential nouns that may lead to classes and verbs may lead to methods or relationships.

Make CRC cards to model each meaningful class relevant to the problem and scenario. Collaborators and responsibilities must be described.

You may use plain text, and separate the cards by a blank line. The following format is recommended:

Class: X

Collaborator: Y

Collaborator: Z

Responsibility: K

Responsibility: L

Responsibility: M

I want to track my tea collection. I collect tea. I use TeaBox app to track my tea and to make trades of tea with other users: I propose a trade and if the other player accepts then we email each other. Some teas cannot be consumed if they are too old, so I need to be warned when tea in my collection needs to be consumed. Some teas are meant to age and I don’t need warnings but I need to know their age. When I completely consume a tea, it should be removed from the active collection into the archived collection, as I would like to keep a record of past teas.

Practice w23hm2q2

2024-10-18T00:00:00+05:00

Model-View (UML)

Interpret the Java code below. It represents a pressure cooker, like the instant-pot. It’s a device that heats up food while under pressure. It provides an API to monitor the pressure and temperature of the pressure cooker. Currently class PressureCooker monitors pressure and temperature, draws a pressure gauge, graphs pressure over time, and draws a thermometer of the temperature. We want to add a temperature graph. Unfortunately we seem to be making this class too big.

Refactor/restructure this code AS A UML CLASS DIAGRAM OF RESTRUCTURED CODE to implement the Model-View pattern (variation of the MVC pattern, but without a dedicated Controller). Separate out models and views, and add new views as necessary to address the new features that were asked for. Explicitly improve cohesion with your restructuring of the code. You can make new classes and interfaces, you can move methods, rename methods, and make new methods.

Add temperature graph
Restructure into MVC using just models and views
Improve Cohesion

On the diagram, CLEARLY LABEL which class(es) represents the Model and the View components. You do NOT need to have a Controller.

Draw a well-designed UML class diagram to represent this information. Provide the basic abstractions, attributes, methods, relationships, multiplicities, and navigabilities as appropriate. "..." means much code is omitted.

import java.util.*;
class PressureCooker {
    private double pressure;
    private double temperature;
    private LinkedList<Double> pastPressures;
    public double currentPressure() { return pressure; }
    /* called by the hardware driver */
    protected void setPressure(double p) {
        pastPressures.push(Double.valueOf(pressure));
        pressure = p;
                draw();
    }
    // drawPressureGauge draws a pressure gauge based on the
    // current value of pressure
    public void drawPressureGauge() {
        /* ... */
    }
    // drawPressureGraph draws a plot of pressure over time.
    public void drawPressureGraph() {
        /* ... */
    }
    // drawThermometer draws a thermometer representing the
    // temperature
    public void drawThermometer() {
        /* ... */
    }
    public void draw() {
        drawPressureGauge();
        drawPressureGraph();
        drawThermometer();
    }
}

A1/A2 20th September Class Exercise

2024-10-17T00:00:00+05:00

Class Participation Exercise Sept 20

Based on the UML, write some Java classes that implement the structure described by the UML. First, implement the class structure. Then add attributes/methods to each class for the relationships (association/aggregation/composition) that enforce the multiplicities. The fields and methods are missing from the UML, but you need to add code to each class for the methods and attributes shown in the relationships. If you have time, you can add other reasonable methods and attributes as well.

Add your name and your partner's name (if you have one) to the code. If you don't add your name, you will receive a zero.

Either upload your java code as a single file or take a picture or screenshot and upload it.
- car.pdf

A1/A2 2nd October Class Exercise

2024-10-17T00:00:00+05:00

Class Participation Exercise Oct 2

The Java code below is software for a tiny sound recorder used by spies. It has a physical hardware counter display to show how much recording time is left and a button that starts it recording and stops it.
Refactor/Restructure this single class into MVC classes as a UML diagram. You do not need to diagram the original code, you only need to make a UML class diagram for your new MVC version of the code. Only refactor the code shown. You do not need to include the TimeCounter or Microphone classes in your UML, because they are static hardware that you cannot change or reprogram.
On the diagram, clearly label which classes represent model, view, and controller. Your UML class diagram should have all the basic abstractions, attributes, methods, relationships, multiplicities, and navigabilities as appropriate. “...” means much code is omitted.
Use the “active model” type of MVC that we discussed in class: the one that uses the observer pattern.
Do not submit Java, submit UML.

public class SpyCorder {
    final int storage;
    private boolean enabled;
    private ArrayList<Sounds> recording;

    SpyCorder(int storage) {
        this.storage = storage;
        enabled = false;
        runLoop();
    }

    void runLoop() {
        while (true) {
            if (enabled) {
                recording.add(Microphone.listen());
            }
            showRemaining();
        }
    }

    void buttonPressed() {
        enabled = !enabled;
    }

    void showRemaining() {
        TimeCounter.show(storage - recording.size());
    }
}

Add your name and your partner's name (if you have one) to the diagram. If you don't, you won't get credit.

Upload a screenshot. If you worked in a pair, get the screenshot from your partner and upload the same screenshot.

You can screenshot a diagrammer of your choice, or draw it on paper and take a photo. Here's a handy diagrammer online: https://app.diagrams.net/ IF that one doesn't work for you, try a different one.

A1/A2 Sept 23rd Class Exercise

2024-10-17T00:00:00+05:00

Class Participation Exercise Sept 23

Based on the Java code, design a UML class diagram that represents the structure of this these classes. Pay special attention to the relationships and their multiplicities (the 1 or 0.. or 1.. etc.).

Add your name and your partner's name (if you have one) to the diagram.

Upload a screenshot. If you worked in a pair, get the screenshot from your partner and upload the same screenshot.

You can screenshot a diagrammer of your choice, or draw it on paper and take a photo.

Do not change file extension without converting in a conversion application, you will make the file unreadable by eclass and get a zero. For example, renaming a file from .heif or .heic to .png will make it unreadable and you will get a zero. Instead, open it in a conversion tool like preview and export it as a different file format.

Here's a handy diagrammer online: https://app.diagrams.net/ IF that one doesn't work for you, try a different one. I use umlet personally, which you have to download and install. https://www.umlet.com/

Here's the Java code: code

Class Participation Exercise 10

2024-10-15T00:00:00+05:00

Class Participation Exercise 10

Proper completion of this exercise is considered as part of course participation. An answer will be discussed in class.

You want a GPS device to disable itself temporarily if it detects it is going faster than 200 km/h. Write the code for a mock object (class MockLocation) that will allow running of bolded lines of class PersonTracker in method testTooFast of class TestPersonTracker.

class PersonTracker {
    ...
    Location lastLocation = null;

    // called every second
    void updateLocation( Location l ) throws GPSException {
        if (lastLocation != null) {
            if (lastLocation.distance( l ) > 200.0*1000/3600) {
                // 200 km/h in m/s
                GPS.getGPS().disable( 200 );
                throw new GPSException( "Too Fast!" );
            }
        }
        lastLocation = l;
    }
}

interface Location {
    // distance in metres
    public double distance( Location l );
}

class TestPersonTracker extends TestCase {
    void testTooFast() {
        PersonTracker p = new PersonTracker();
        Location l = new MockLocation( 0, 0 );
        try {
            p.updateLocation( l );
            p.updateLocation( l );
            fail( "This was supposed to throw exception." );
        } catch (GPSException e) {
            return; // exception was properly thrown
        }
    }
}

State any assumptions. You should try to avoid modifying the given code.

Submit your Java code in a zip file.

A1/A2 18th September Class Exercise

2024-10-08T00:00:00+05:00

Class Participation Exercise Sept 18

Imagine a mobile application designed for the world of Dungeons & Dragons (D&D). This application serves as a tool for managing and tracking character stats, and creating and customizing D&D characters. It keeps track of stats such as strength, dexterity, constitution, intelligence, wisdom, and charisma.

There is a spell management system. In the context of D&D, a spell is a magical effect conjured by a character. Each spell has specific effects, casting time, range, and duration. A spellbook is a collection of spells that a character knows and can use during gameplay. The application allows users to add or remove spells from their character’s spellbook, effectively managing their repertoire of spells.

The concept of spell slots represents the energy a character has to cast spells. Each spell requires a certain level of energy, represented by the level of the spell slot. The application tracks the usage of these spell slots, helping users manage their character’s magical energy efficiently.

The application also monitors the character’s health through hit points, tracks their progress through experience points.

A key feature of this application is its detailed inventory management system. In the context of D&D, a character’s inventory can include a wide range of items. These can be weapons like swords and bows, armor like shields and helmets, adventuring gear like ropes and torches, tools like thieves’ tools and musical instruments, and even magic items like potions and scrolls. The application allows users to add or remove items from their character’s inventory, effectively managing their collection of items.

The inventory management system also keeps track of the weight of the items, as carrying too many heavy items can slow a character down. It provides detailed information about each item, such as its properties, value, and description.

One special item that can be managed in the inventory is the “Bag of Holding”. In D&D, a Bag of Holding is a magical item that can hold more items than its size would suggest. It’s a small sack, but its inside is larger than its outside dimensions. Regardless of what is put into the bag, it weighs a fixed amount. This makes it highly valuable for characters carrying many items. The application should be able to handle such special items and their unique properties.

Based on this description, design a UML class diagram that represents the structure of this application. Consider the classes, their attributes, methods, and relationships.

Add your name and your partner's name (if you have one) to the diagram. If you do not put your name on the file you will get a zero.

Upload a screenshot. If you worked in a pair, get the screenshot from your partner and upload the same screenshot.

You can screenshot a diagrammer of your choice, or draw it on paper and take a photo, or you can draw it with a tablet.

Here are some free diagrammers:

Here's a handy diagrammer online: https://app.diagrams.net/
IF that one doesn't work for you, try a different one.
Here's a Java one: https://www.umlet.com/changes.htm (download the stand alone)

B2 27th March Class Exercise

2024-10-08T00:00:00+05:00

Class Participation Exercise

Design and create a sequence diagram for a system that allows users to customize a car using the decorator pattern. It might be helpful to sketch the class diagram, but it's not required, only the sequence diagram is required.

Use the decorator pattern to implement a simulator, a car and some upgrades that can be applied to the car. The car has some basic properties like model, color, speed, and price. A variety of upgrades are available such as a V8 engine, a turbocharger, a spoiler, and racing tires.

Make a sequence diagram that shows the interaction between the objects when it constructs a car with at least 2 upgrades and then computes its price.

Do not submit Java, submit UML Sequence Diagram.

Add your name and your partner's name (if you have one) to the diagram. If you don't, you won't get credit.

Upload a screenshot. If you worked in a pair, get the screenshot from your partner and upload the same screenshot.

Class Participation Exercise Sequence Diagram

2024-09-25T00:00:00+05:00

Class Participation Exercise March 24 - Sequence Diagram

Proper completion of this exercise is considered as part of course participation. An answer will be discussed in class.

Consider the basic command design pattern, with Invoker, ConcreteCommand, and Receiver classes. Assume also there is a Client class to create a ConcreteCommand object and bind it to an Invoker object via dependency injection.

Draw the UML sequence diagram that depicts:

the command creation and its binding to an invoker, and
the behavior of the command pattern to have the invoker execute the command, which runs an action on a receiver

Submit your sequence diagram as a PDF, PNG, or JPEG file.

Class Participation Exercise (Cohesion and Coupling)

2024-09-21T00:00:00+05:00

Class Participation Exercise: Cohesion and Coupling

For the first set of UML diagrams which one has more coupling CarA or CarB?
For the second set of UML diagrams (spaceship) which one has the most coupling?
Out of all these classes, which classes are the least Cohesive?
Out of all these classes, which classes are the most Cohesive?

Class Participation Exercise (CRC Cards)

2024-09-21T00:00:00+05:00

Class Participation Exercise: CRC Cards

Instructions: You are tasked with the Object Oriented Analysis (OOA) of the following problem. Please make CRC cards (Class Reponsibility Collaboration) for each meaningful class.

I want to see if a skin-blemish changes over time. To prove that a blemish changes I need evidence (photos). I would like to take photos of these blemishes over time and store them in a safe place. I want the photos to be taken consistently. These photos can be provided to physicians when needed.

Example format:

Class: UFO Collaborator: Alien, Earthling Responsibility: Provide an Earthling abduction platform Responsibility: Carry Aliens

Class: Earthling Collaborator: Alien, UFO Responsibility: Abductee Responsibility: To be mind probed

Class: Cow Collaborator: Alien, UFO Responsibility: Abductee Responsibility: To be mind probed Generalization: Earthling

Repeat this format for each class you think is relevant.

Class Participation Exercise (Git)

2024-09-21T00:00:00+05:00

CMPUT301 Exercise: GIT Stuff you should know!

Q1: I committed a big mistake, I want to restore my repository to the prior commit, what should I run?
Q2: I want to record a change locally, what do I run?
Q3: How do I share my changes?
Q4: How do I get my colleagues changes?
Q5: How do you checkout commit, 9a4c3ef1630e13ced5b5a34faaa70d82c3634138 as a new branch?

Class Participation Exercise: Factory Method Pattern (Mar 29)

2024-09-19T00:00:00+05:00

Class Participation Exercise: Factory Method Pattern

Design a framework using the Factory Method Pattern for:

Application and Document superclasses
And an actual application would make these:
- Add MyApplication and MyDocument subclasses
- Add YourApplication and YourDocument subclasses

Write a general newDocument method in Application that ultimately instantiates a MyDocument if your application is a MyApplication.

Draw the UML class diagram for the above problem using the Factory Method Pattern using concrete and abstract classes.
What is the code in MyApplication for the method newDocument?

Class Participation Exercise: Template Method Pattern (Mar 26)

2024-09-19T00:00:00+05:00

Class Participation Exercise: Template Method Pattern

Rewrite countWords() * Convert the countWords() method to a template method using the Template Method Pattern, removing the conditionals.

Write code for one of the following subclasses: * RawWordCounter * WordCounterNoStopWords * LowerCaseWordCounter

public class WordCounter {
...
void countWords() {
    loadData();
    if (lowerCaseWords) {
        lowerCaseData();
    }
    if (removeStopWords) {
        filterStopWords();
    }
    calculateTermFrequency();
    calculateTermDocumentFrequency();
    saveCountData();
}
}

Practice w23hm1 Answers

2024-09-19T00:00:00+05:00

Practice w23hm1 Answers Videos:

Practice W23HM1 Answers Videos

Class Participation Exercise 11

2024-09-18T00:00:00+05:00

Class Participation Exercise 11

Apply the composite design pattern to:

model the structural representation of binary logical expressions involving the binary operators and and or, and boolean literals true and false; and
support the uniform, recursive evaluation of such expressions

Draw the UML class diagram for the object-oriented design, applying the design pattern. Include suitable classes, relationships, attributes, and methods.

Class Participation Exercise 12

2024-09-18T00:00:00+05:00

Class Participation Exercise 12

Proper completion of this exercise is considered as part of course participation. An answer will be discussed in class.

You have a design where a two-dimensional rectangle drawing method takes a top left point and a bottom right point. Also, in your design, the points are specified by integer x and y coordinates.

public interface RectangleDrawer { public void draw( Point topLeft, Point bottomRight ); } Suppose, however, you want to reuse a rectangle drawing method that takes four integer parameters: top left x coordinate, top left y coordinate, width, and height.

public class RectangleRenderer { public void render( int x, int y, int width, int height ) { ... } ... } Write Java code for a rectangle drawing object adapter.

public class RectangleDrawerAdapter ... Submit your Java code as a zip archive.

Class Participation Exercise 13

2024-09-18T00:00:00+05:00

Class Participation Exercise 13

Proper completion of this exercise is considered as part of course participation. An answer will be discussed in class.

Apply the decorator design pattern to represent the structure of a pizza and for calculating its total cost.

Starting with a base (e.g., thick crust), you can decorate with successive toppings (e.g., rich sauce, then pepperoni, then cheese). Each base or topping has a specific incremental cost to add to the total cost.

Draw a UML class diagram that applies the decorator pattern for the structure of the above base and toppings.

Submit your diagram as a PNG file.

Class Participation Exercise 9

2024-09-18T00:00:00+05:00

Class Participation Exercise 9

Consider a Rect class to represent a rectangle in a two-dimensional integer plane.

public class Rect {
    ...
    // create rectangle with given corners
    public Rect( Point topLeft, Point botRight ) { ... }

    // return true iff point p is in or on this rectangle
    public boolean encloses( Point p ) { ... }
}

Depict a thorough set of test case equivalence classes for the encloses method, also indicating the expected results. Add explanatory text as needed for analogous or unusual cases. State any assumptions.

Do not implement the method. Do not write test code. Do not use JUnit.

Class Participation Exercise 9

2024-09-18T00:00:00+05:00

Class Participation Exercise: Code to UML (UFO)

// UFO.java
public class UFO {
    private Collection<Earthling> abductees;
    ...
}

// Earthling.java
public class Earthling {
    private int stomachs;
    public boolean mindProbeable() { ... }
    ...
}

What notation goes here for this relationship?

a) Not selected
b) ←
c) —
d) ◇
e) ◆
f) ◁

What notation goes here for the multiplicity

a) 0
b) 1
c) 0..1
d) 0.._
e) 1.._

What notation goes here for the instance variable?

a) private
b) public
c) -
d) +
e) attributes

What notation goes here for this method?

a) private
b) public
c) -
d) +
e) behaviors

Class Participation Exercise April 14

2024-09-18T00:00:00+05:00

Speaker is a class that utters words and uses the state pattern to change its behaviour.

class Speaker {

    Speak speak;

   // delegate behaviour

   public String speak() {

       return speak.speak();

    }

     ...

}

public interface Speak {

     public String speak();

}

class Squawk implements Speak { ... }

class Cluck implements Speak { ... }

class Tick implements Speak {

     public String speak() {

          return "Tick”;

     }

}

Speaker has behaviours such as Squawk which returns random Squawking strings, and Cluck which returns random clucking strings. Tick just returns "Tick”.

Finish this decorator for Speak states that lowercases the Speak states.

//"X”.toLowerCase().equals("x”)

class LowerCaseSpeakDecorator implements Speak {

     Speak speak;

     LowerCaseSpeakDecorator(Speak delegate) {

         speak = delegate;

     }

     public String speak() {







     }

}

Show how to make a lowercase tick behaviour.

Class Participation Exercise April 17

2024-09-18T00:00:00+05:00

View adapter-pattern-quiz

Class Participation Exercise (Code to UML)

2024-09-18T00:00:00+05:00

Class Participation Exercise

Consider a Rect class to represent a rectangle in a two-dimensional integer plane.

public class Shape {
    protected Location myLocation;
    public Shape() { ... }
    public void setLocation( Location p ) { ... }
    public Location getLocation() { ... }
}

public class Square extends Shape {
    private int side;

    public Square() { ... }
    public void setSide( int s ) { ... }
}

Document this Java code by expressing its design in a corresponding UML class diagram.

Submit the diagram as a PNG or JPG or PDF file.

(For this exercise, the diagram can be hand drawn on paper, with a picture of it submitted as the file.)

Class Participation Exercise Design Principles

2024-09-18T00:00:00+05:00

Proper completion of this exercise is considered as part of course participation.

Initial versions of early programming languages (e.g., Fortran) supported:
[ ] abstract data types
[ ] program and subroutines
[ ] local variables
[ ] classes and objects
Abstraction is the idea of simplifying a concept in the problem domain to its essentials within some ____.
Using encapsulation is sometimes called ____ thinking.
Decomposition of a whole thing into parts mainly involves thinking about:
[ ] fixed or dynamic number of parts
[ ] essential attributes and behaviors of parts
[ ] lifetimes of wholes and parts
[ ] commonalities among the parts

Class Participation Exercise Proxy Pattern

2024-09-18T00:00:00+05:00

Class Participation Exercise: Proxy Pattern

Use the Proxy pattern to improve performance by not reading files that aren't actually needed yet.

interface OurFile {
    byte[] fileContents(); // returns entire file
    String getName();
}
class ConcreteFile implements OurFile {
    String name;
    byte[] fileContents;
    ConcreteFile(String name) { ... }
    String getName() { return name; }
    byte[] fileContents() { return fileContents; }
    ...
}

assume ConcreteFile exists and implements OurFile. ConcreteFile reads the entire file when it is constructed.

Write java code for ProxyFile that proxies a ConcreteFile and doesn't have to read the entire file until the contents of the file are needed, using the proxy pattern.

Class Participation Exercise 9

2024-09-18T00:00:00+05:00

Class Participation Exercise: Code to UML (UFO)

// UFO.java
public class UFO {
    private Collection<Earthling> abductees;
    ...
}

// Earthling.java
public class Earthling {
    private int stomachs;
    public boolean mindProbeable() { ... }
    ...
}

What notation goes here for this relationship?

a) Not selected
b) ←
c) —
d) ◇
e) ◆
f) ◁

What notation goes here for the multiplicity

a) 0
b) 1
c) 0..1
d) 0.._
e) 1.._

What notation goes here for the instance variable?

a) private
b) public
c) -
d) +
e) attributes

What notation goes here for this method?

a) private
b) public
c) -
d) +
e) behaviors

Class Participation Exercise 9

2024-09-18T00:00:00+05:00

Class Participation Exercise 9

Consider a Rect class to represent a rectangle in a two-dimensional integer plane.

public class Rect {
    ...
    // create rectangle with given corners
    public Rect( Point topLeft, Point botRight ) { ... }

    // return true iff point p is in or on this rectangle
    public boolean encloses( Point p ) { ... }
}

Do not implement the method. Do not write test code. Do not use JUnit.

Class Participation Exercise 2020-04-06 Long Method Refactoring

2024-09-17T00:00:00+05:00

Class Participation Exercise: Long Method Refactoring

Extracts methods from this long method body by putting a box around code that will go into a new method. Then on the right hand side of that box write the method name.

At the bottom, rewrite insertRecipe using those new methods.

/**

* Inserts a Recipe into the Webservice

*/

public void insertRecipe(Recipe recipe){

     StringEntity stringentity = null;

     try {

         stringentity = new StringEntity(gson.toJson(recipe));

     } catch (UnsupportedEncodingException e) {

          handleError(e);

     }

     HttpPost httpPost = new HttpPost(recipeURI);

     httpPost.setHeader("Accept","application/json");

     httpPost.setEntity(stringentity);

     HttpResponse response = null;

     try {

          response = httpclient.execute(httpPost);

     } catch (ClientProtocolException e) {

          handleError(e);

     } catch (IOException e) {

          handleError(e);

     }

      HttpEntity entity = response.getEntity();

      try {

          EntityUtils.consume(entity);

     } catch (IOException e) {

         handleError(e);

     }

     httpPost.releaseConnection();

}

public void insertRecipe(Recipe recipe) { // your new refactored method

}

Class Participation Exercise 2020-04-08 Refactoring

2024-09-17T00:00:00+05:00

License

Copyright 2012 Neil Borle, Mitchell Home, Bronte Lee, Aaron Padlesky, Eddie Santos
Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License.
You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and limitations under the License.

Class Participation Exercise: Refactoring

public class ResponseObtainerObtainer {

    public static ResponseObtainer getResponseObtainer(
            MediaType media, LayoutInflater inflater,
            ViewGroup root) throws Exception {

        ResponseObtainer obtainer = null;
        int layout_id = -1;
        ViewGroup view = null;
        Class<? extends ResponseObtainer> obtainerClass = null;

        switch (media) {
            case TEXT:
                layout_id = R.layout.fragment_fulfill_text;
                obtainerClass = TextResponseObtainer.class;
                break;
            case AUDIO:
                layout_id = R.layout.fragment_fulfill_audio;
                obtainerClass = AudioResponseObtainer.class;
                break;
            case PHOTO:
                layout_id = R.layout.fragment_fulfill_photo;
                obtainerClass = PhotoResponseObtainer.class;
                break;
            default:
                // err....
                // TODO: Give an error response obtainer?
        }

        view = (ViewGroup) inflater.inflate(layout_id, root);
        obtainer = obtainerClass.getConstructor(ViewGroup.class)
                    .newInstance(view);
        return obtainer;
    }
}

List 1: Code Smell

Evident in this code:

Propose or draw a refactoring for this code.
Why would a MediaType (TEXT, AUDIO, PHOTO) still be necessary after a refactoring?

Class Participation Exercise 3

2024-09-17T00:00:00+05:00

Class Participation Exercise 3

Proper completion of this exercise is considered as part of course participation. An answer will be discussed in class.

Convert this UML class diagram to corresponding basic Java source code.

Submit your code as a zip archive of the Java files. Or hand write the code on paper, and submit a picture of it as a PNG or JPG or PDF file.

Class Participation Exercise 8

2024-09-17T00:00:00+05:00

Class Participation Exercise 8

Proper completion of this exercise is considered as part of course participation. An answer will be discussed in class.

Model the following behavior using a correct UML state diagram.

I want to keep my flamethrower in a vault that's hard to find.

So, to reveal the lock to the vault, I have to remove a helmet from a shelf. This will reveal the lock only while a door is closed.

Once I can see the lock, I can insert my key to open the vault.

For extra security, I make sure that I can open the vault only if I put the helmet back on the shelf.

If an intruder forgets this precaution, a facehugger will be unleashed to disable the intruder.

Submit the diagram as a PNG file.

Class Participation Exercise 15

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

Class Participation Exercise 15

Proper completion of this exercise is considered as part of course participation. An answer will be discussed in class.

Consider the following (partial) implementation of a Person class.

class Person {
    ...

    public String getName() {
        return name;
    }

    public String getTelephoneNumber() {
        return "(" + officeAreaCode + ") " + officeNumber;
    }

    String getOfficeAreaCode() {
        return officeAreaCode;
    }

    void setOfficeAreaCode( String areaCode ) {
        officeAreaCode = areaCode;
    }

    String getOfficeNumber() {
        return officeNumber;
    }

    void setOfficeNumber( String number ) {
        officeNumber = number;
    }

    private String name;
    private String officeAreaCode;
    private String officeNumber;
}

Draw the UML class diagram for the refactored design.

Submit your diagram as a PNG file.

Practice w23am1q1

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

Java to UML Class Diagram

Convert this Java code to a UML class diagram. This Java code is meant to represent passengers and buses in the fictional world of My Neighbour Totoro. A Catbus can take passengers to places like a regular bus, but it also behaves like a cat. There is one specific kind of passenger (Totoro) that can ask the Catbus to do things for him.

public abstract class Bus {
    private String sign; // destination sign (e.g. "Hospital")
    private ArrayList<Passenger> passengers;
    public Bus(String sign) {
        this.sign = sign;
        this.passengers = new ArrayList<Passenger>();
    }
    public abstract void load(Passenger p);
    public abstract boolean travel(Location from, Location to);
}

public interface CatLike {
    public void purr();
}

public class CatBus extends Bus implements CatLike {
    public CatBus(String sign) {
        super(sign);
    }
    public void load(Passenger p) {
        // ...
    }
    public boolean travel(Location from, Location to) {
        // ...
        return true;
    }
    public void purr() {
        // ...
    }
}

public interface Location {
    // ...
}


public interface Passenger {
    // ...
}

public class Totoro implements Passenger {
    // Totoro is the only King of the Forest
    // He doesn’t only ride Catbuses, but can control them
    public void controlCatBus(CatBus bus) {
        // ...
    }
}

Practice w23am1q2

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

UML Class Diagram to Java

Convert this UML class diagram about the Harry Potter universe to skeletal Java Code. Include all attributes and obviously public methods. Make sure all required methods are implemented. Include all generalizations and necessary associations. You may use ellipses (...) to indicate there is some code in the method but it's a midterm and who has time to write that code!

ACCOMMODATIONS: If you need a textual version of this UML Q2.pdf and Q2.svg are available for you

Practice w23am1q3

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

Liskov Substitution Principle

This Java code is poor! It violates the Liskov Substitution principle!

Restructure this code as UML and draw a UML Class Diagram of restructured code that doesn't violate the Liskov Substitution principle.

Draw a well-designed UML class diagram to represent this information. Provide the basic abstractions, attributes, methods, relationships, multiplicities, and navigabilities as appropriate.

"...” means much code is omitted.

This Java code is about quizzes (similar to eClass quizzes).

Be sure to leave a note on the diagram highlighting how you address the violation

class Quiz {
    protected Question[] questions;

    // ...

    public void printAnswerKey() {
        for (int i = 0; i < questions.length; i++) {
            System.out.println(questions[i].getCorrectAnswer());
        }
    }
}

class Exam extends Quiz {
    protected Room room; // unlike quizzes, exams are administered in a room

    // ...
}

class Question {
    protected String question;

    protected String[] answers; // choices
    protected int correctAnswer; // index of a correct answer

    // ...

    public int getCorrectAnswer() {
        return correctAnswer;
    }
}

class EssayQuestion extends Question {
    // ...

    public int getCorrectAnswer() {
        System.err.println("Essay questions do not have a correct answer.");
        return -1;
    }
}

Practice w23am2q1

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

CRC Cards

Engage in Object-Oriented Analysis and read the following scenario paragraph and pull out potential nouns that may lead to classes and verbs that may lead to methods or relationships.

Make CRC cards to model each meaningful class relevant to the problem and scenario. Collaborators and responsibilities must be described.

You may use plain text, and separate the cards by a blank line. The following format is recommended:

Class: X

Collaborator: Y

Collaborator: Z

Responsibility: K

Responsibility: L

Responsibility: M

I see that the class that I take is scheduled in TEL 150. I have never taken a class in this classroom before, so I open the RateMyUofAClassroom app. It shows a long list of rooms. I start typing “TEL 1”, and the app suggests “TEL 150”. I click it and see that this classroom has an average rating of 4.3, nice! I go to my class and actually like the room a lot. I open the app and give the room a 5. The average rating is updated, it's now 4.4! What if I try to rate it again? No, I get an error message saying "You have already rated this classroom.”

Practice w23am2q2

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

Model-View (UML)

Interpret the Java code below. It represents an automated parking lot system. It provides an API to monitor the status of a parking lot. Currently, the ParkingLot class can display available parking spots and draw the parking lot map. We want to add a pie chart showing the current ratio of available and occupied parking spots. Unfortunately, we seem to be making this class too big.

Refactor/restructure this code AS A UML CLASS DIAGRAM OF RESTRUCTURED CODE to implement the Model-View pattern (variation of the MVC pattern, but without a dedicated Controller). Separate out models and views, and add new views as necessary to address the new features that were asked for. Explicitly improve cohesion with your restructuring of the code. You can make new classes and interfaces, you can move methods, rename methods, and make new methods.

Add a pie chart
Restructure into MVC using just models and views.

On the diagram, CLEARLY LABEL which class(es) represents the Model and the View components. You do NOT need to have a Controller.

Do NOT submit Java, submit UML!

import java.util.*;


class ParkingLot {
    private int capacity;
    private int numCars;
    private HashMap<Integer, Boolean> spots;

    /* ... */

    /* called by the parking detection system */
    protected void carIn(int spot) {
        spots.put(spot, true);
        numCars++;
        render();
    }

    /* called by the parking detection system */
    protected void carOut(int spot) {
        spots.put(spot, false);
        numCars--;
        render();
    }

    // lists available parking spots
    public void listSpots() {
        /* ... */
    }

    // draws a map of the parking spots and their status
    public void drawMap() {
        /* ... */
    }

    public void render() {
        listSpots();
        drawMap();
    }
}

Practice w23am2q3

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

Use Case

Write a use case for the task of a young person applying for a job based on the following scenario.

I am 16 years old and looking for my first job, so I go to the MyFirstJob website. The website shows that the minimum age to work in Alberta is 15 and asks for my date of birth. I enter "2007-01-23". On the next page, there is a map showing all employers with current job openings. I use a filter to select the "Food" category. I see that a local coffee shop in my neighbourhood, "Café con Sabor," is looking for a part-time barista. I know a lot about coffee from my parents, so this sounds like a good fit! I click on "Café con Sabor" and see the application form. I go ahead and fill it out. Then I have to upload a resume. I try to upload my resume in DOCX format, but I get an error message: "Only PDF is supported". I upload the PDF, and the site displays the message "Application submitted!" and a happy face emoticon.

Include the following elements:

Use case name
Participating actors
Goal
Trigger
Preconditions
Postconditions
Basic flow
One exception

Practice w23hm1q1

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

Java to UML Class Diagram

Convert this Java code to a UML class diagram. This Java code is meant to represent a mouth tasting and consuming food. There are food, flavours, tongues, and taste buds.

import java.util.*;

class Mouth {
    Collection<Tooth> teeth;
    Tongue tongue;
    // ...
}
class Tooth {
    // ...
}
class Tongue {
    private TasteBud[] buds;
    Flavour taste(Food f) {
        Flavour[] flavours = new Flavour[buds.length];
        for (int i = 0; i < buds.length; i++) {
            flavours[i] = buds[i].taste(f);
        }
        return new AggregateFlavour(flavours);
    }
    // ...
}
interface TasteBud {
    public Flavour taste(Food f);
}
interface Flavour {
    public int sweet();
    public int salty();
}
class AggregateFlavour implements Flavour {
    Flavour[] flavours;
    AggregateFlavour(Flavour[] flav) {
        flavours = flav;
    }
    public int sweet() {
        // Sum of sweetness
        // ...
    }
    public int salty() {
        // Sum of salty
        // ...
    }
    // ...
}
interface Food {
    // ...
}

Practice w23hm1q2

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

UML Class Diagram to Java

Convert this UML class diagram about the parameciums (a fancy microbe) to skeletal Java Code. Include all attributes and obviously public methods. Make sure all required methods are implemented. Include all generalizations and necessary associations. You may use ellipses (...) to indicate there is some code in the method but it's a midterm and who has time to write that code!

ACCOMMODATIONS: If you need a textual version of this UML output.pdf is available for you.

Practice w23hm1q3

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

Liskov Substitution Principle

This Java code is poor! It violates the Liskov Substitution principle!

Restructure this code as UML and draw a UML Class Diagram of restructured code that doesn't violate the Liskov Substitution principle.

Draw a well-designed UML class diagram to represent this information. Provide the basic abstractions, attributes, methods, relationships, multiplicities, and navigabilities as appropriate.

"...” means much code is omitted.

This Java code is about Monsters in a video game.

Be sure to leave a note on the diagram highlighting how you address the violation

interface Monster {
    // move object to x, y
    public void translate(double x, double y);
    public void draw();
}
// Blob is an amphorous pile of goo
class Blob implements Monster {
    public void translate(double x, double y) { /* ... */ }
    public void draw() { /* ... */ }
    // ...
}
// ImmobileBlob is the blob that doesn't move!
class ImmobileBlob extends Blob {
    private int x;
    private int y;
    ImmobileBlob(int x, int y) { /* ... */ }
    public void translate(double x, double y) {
        // do nothing
    }
    // ...
}
class GameCanvas {
    // ...
    // translate the monsters into a 16 x 16 grid
    void gridify(Monster[] xs) {
        for (int i = 0; i < xs.length; i++) {
            xs[i].translate(i / 16, i % 16); // % is modulus
            xs[i].draw();
        }
    }
}

Practice w23hpmq1

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

Convert this Java code to a UML class diagram. This Java code is meant to represent a animals. Draw a well-designed UML class diagram to represent this information. Provide the basic abstractions, attributes, methods, relationships, multiplicities, and navigabilities as appropriate.

"..." means much code is omitted.

class Animal {
    protected String name;
    protected int age;
    public String getName() { return name; }
}

interface Predator {
    public boolean hunt(Animal a);
}

interface Herbivore {
    public void eat(Plant p);
}

class Lion extends Animal implements Predator {
    public boolean hunt(Animal a) {
        // ...
    }
    // ...
}

class Zebra extends Animal implements Herbivore {
    protected int stripes;
    public void eat(Plant p) {
        // ...
    }
}

class Savannah {
    private int area;
    private Lion alphaLion;
    protected ArrayList<Animal> inhabitants = new ArrayList<Animal>();
}

Class Participation Exercise 20

2024-09-10T00:00:00+05:00

Class Participation Exercise 20

Consider the following method to compute the base-two logarithm of a byte value (assumed positive here, maximum 127), truncated down to the nearest integer. For example, if the byte value is 17, the method returns 4.

public static int logb2( byte b ) {
    return (int)( Math.log( b ) / Math.log( 2 ) );
}

Assume this method is heavily used, and that operations like Math.log( double ) are relatively slow and should be avoided.

Optimize this method to reduce the computation time needed, while maintaining the same expected behavior and using comparable data space. Your method must be proper Java and be a self-contained implementation (not call other methods). Add comments as appropriate to explain how it is intended to work.

Class Participation Exercise 19

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

Opened: Monday, 5 August 2019, 10:29 AM

Closed: Tuesday, 6 August 2019, 4:59 PM

Edit

Proper completion of this exercise is considered as part of course participation.

Edit

Consider the following sloppily designed user interface (a form for a web browser). Identify at least 5 issues why this user interface design is poor or inconsistent.

Issue 1:

Issue 2:

Issue 3:

Issue 4:

Issue 5:

Issue 6:

Issue 7:

Issue 8:

Issue 9:

Issue 10:

Exam Practice Questions

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

Exam Practice

Old Lecture Recordings

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

Old Participation Exercise

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

Old Participation Exercises

Old Participation Exercises

Practice w23am3q1

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

Scenario to Sequence Diagram

Convert this scenario into a sequence diagram. Remember to include all the actors, components, lifelines, activation boxes and guards (conditions). Use good names for the methods.

My car needs gas, so I drive to the nearest gas station. I swipe my debit card at the pump. The pump connects to the processing center to authorize the card for the default amount of $100, and if there are sufficient funds in my account, the processing center confirms successful authorization. Next, I select Regular and the pump dispenses the selected grade of gasoline. It then asks the processing center to charge my card and receives a transaction ID in response. The pump asks if I want a receipt. The pump prints a receipt only if I tap Yes.**

Practice w23am3q2

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

Template Method Pattern Refactoring (Java Code to UML Class Diagram)

This code represents a training program that includes two different types of workouts (cardio and strength training).

Restructure this code with the template method pattern and provide a UML class diagram depicting the structure and operations one would expect after refactoring this code to use a template method pattern. Your solution must significantly reduce code duplication and enhance reuse.

You must provide the template method Java code in a UML comment (see example below).

Draw the resulting UML class diagram of the refactored code. Provide the basic abstractions, attributes, methods, relationships, multiplicities, and navigabilities as appropriate.

class CardioWorkout {
    public void doCardioWorkout() {
        warmUp();
        run();
        stretch();
    }

    private void warmUp() {
        System.out.println("Warming up.");
    }


    private void run() {
        System.out.println("Running.");
    }


    private void stretch() {
        System.out.println("Stretching.");
    }
}

class StrengthWorkout {  
        public void doStrengthWorkout() {
            warmUp();
            doPushUps();
            doSquats();
            stretch();
        }

        private void warmUp() {
            System.out.println("Warming up.");
        }


        private void doPushUps() {
            System.out.println("Doing push ups.");
        }


        private void doSquats() {
            System.out.println("Doing squats.");
        }


        private void stretch() {
            System.out.println("Stretching.");
        }
}

Practice w23am3q3

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

Adapter Design Pattern Refactoring (UML class diagram)

The code represents the university HR system. There are employees paid hourly (support staff, secretaries, assistants etc.) and students. Some students can be employed as teaching assistants. In this case, their hourly rate depends on their year. The Report class prepares reports on employees and teaching assistants.

There is a problem with the Report class as it knows too much about students!

Restructure this code with the Object Adapter design pattern and provide a UML class diagram depicting the structure and operations one would expect after refactoring this code to use an object adapter.

In your solution, the Report class must have one (and only one) method. Your solution must significantly reduce code duplication and enhance reuse.

Draw the resulting UML class diagram of the refactored code. Provide the basic abstractions, attributes, methods, relationships, multiplicities, and navigabilities as appropriate.**

class Employee {
    private String name;
    private String jobTitle;
    private double hourlyRate;
    public String getName() { return name; }
    public String getJobTitle() { return jobTitle; }
    public double getHourlyRate() { return hourlyRate; }
}

class Student {
    private String name;
    private String major;
    private int year;
    public String getName() { return name; }
    public String getMajor() { return major; }
    public int getYear() { return year; }
}

class Report {
    // Prints report for an employee (hourly staff)
    public void employeeReport(Employee e) {
        System.out.println("Name: " + e.getName());
        System.out.println("Job Title: " + e.getJobTitle());
        System.out.println("Hourly Rate: " + e.getHourlyRate());
    }

    // Prints report for a teaching assistant
    public void studentReport(Student s) {
        System.out.println("Name: " + s.getName());
        System.out.println("Job Title: Teaching Assistant");
        double hourlyRate = 0;
        if (s.getYear() == 1) {
            hourlyRate = 17;
        } else if (s.getYear() <= 3) {
            hourlyRate = 18;
        } else {
            hourlyRate = 19;
        }
        System.out.println("Hourly Rate: " + hourlyRate);
    }
}

Project Demo Schedule

2024-08-28T00:00:00+05:00

Project Demo Schedule

Lab 5 Instructions

2024-08-26T00:00:00+05:00

Lab 5 Instructions

Read Firestore 🔥.pdf for introduction of Firestore Follow instructions on Lab 5 Firestore Integration Instructions.pdf along with the TA. Complete Lab Exercise.

Download Starter Code here

Lab 5 Participation Exercise

Proper completion of this exercise is considered as part of course participation.

In this exercise it is your task to add the ability to delete Cities and integrate this functionality with the Firestore database, allowing for the persistence of deletions.

After applying the changes in the lab demo (LINK TO INSTRUCTIONS), add the ability to delete cities from the ListView and apply these same deletions to your instance of the Firestore database. If you have implemented this functionality correctly, restarting your app should not have an impact on what cities are displayed in your ListView after any addition or deletion actions.

Note: the design of the deletion functionality is up to you, however, we have uploaded a few mockups to give you some ideas.

Submission

LMS

Due Date

Tuesday 5PM

Lab 6 Instructions

2024-08-26T00:00:00+05:00

Lab 6 Instructions

Follow the slides on Javadoc and JUnit
Follow instructions on this link along with the TA.
Complete Lab Exercise.

Some known issues:

"test events were not received" --> Solution: link
"Error creating JavaDoc" --> Solution: link

Lab 6 Participation Exercise

Proper completion of this exercise is considered as part of course participation.

In this exercise your task is to implement and test the following methods in the CityList class AND create Javadocs for the main source files (not tests):

1) Implement and test these methods: - hasCity(City city) - When given a city, return whether or not it belongs in the list

    - Test to see whether your method is correct (Read https://www.infoworld.com/article/3305792/comparing-java-objects-with-equals-and-hashcode.html) delete(City city)

    - Check if a city is present in the list. If it does then remove it from the list, if not then **throw an exception**

    - Test to see if your method actually removes it from the list

    - Test to see if the exception is actually thrown (Read more here https://howtodoinjava.com/junit5/expected-exception-example/) countCities()

    - Return how many cities are in the list

    -  Test to see whether your method is correct

2) Add Javadocs to all methods in CityList class and City class AND generate the javadocs to /app/javadocs

Submission

LMS

Due Date

Tuesday 5PM

Lab 7 Instructions

2024-08-26T00:00:00+05:00

Lab 7 Instructions

Lab Topic/Demo

Lab 7 Participation Exercise

# Implement and test activity: ShowActivity (create by yourself to have the following property)

- By clicking on the city list, the UI should change to another activity which is "ShowActivity"

- The activity shows the city name you have clicked on

- Create a back button which goes back to MainActivity

# Test: (create 3 test cases/functions to test the 3 following functionalities)

- Check whether the activity correctly switched

- Test whether the city name is consistent

- Test the "back" button

Submission

LMS

Due Date

Tuesday 5PM

Lab 8 Participation Exercise

2024-08-26T00:00:00+05:00

Lab 8 Instructions
Lab 8 Slides
- Updated Slides
- Original Slides
Lab 8 Instructions
Lab 8 Participation Exercise
Submission

Lab 8 Instructions

In this lab, we will learn about test driven development (TDD) and continuous integration (CI). These are both solutions for solving some common software engineering problems using unit testing. We will go through the slides (updated version) posted below, and go through a live demo in class based on the instructions below to show you how to use TDD and CI.

Lab 8 Slides

Updated Slides

These slides are based on the original slides posted below, but have a couple more diagrams and a more concise format. If you want to read more about the topic, check out the original slides.
Lab 8 Updated Slides

Original Slides

Lab 8 Slides

Lab 8 Instructions

Lab 8 Instructions

Lab 8 Participation Exercise

Lab Exercise

• Implement has city, delete city, and count cities (same as lab 6), however, this time using TDD.

• Create each functionality one at a time, creating (and pushing) a test to create a failing build, before adding functionality to make it pass.

• e.g., create hasCity test, push for failing build, write functionality for hasCity to make passing build. Repeat for delete city and count cities.

Submission

LMS

Due Date

Tuesday 5PM

Project Part 0

2024-08-26T00:00:00+05:00

Team Members
What to submit
Submission Procedure
Marking

Due date: Check the schedule.

Team Members

Project teams consist of 5 members and each member must be registered in the same lab section.

The intent is that all members are available together for a good block of time during the week, to regularly meet their assigned TA, and to attend their project demos in their registered lab, without potentially overloading the lab section.

For an initial teamwork exercise you will be asked to pick a team name according to the exact specifications below.

If you have fewer than 5 members, you may be split up and assigned to other teams.

What to submit

Every team member will need to submit the following:

The lab section (Wednesday/Thursday)
Each team member's ROLLNUM
Each team member's name
Each team member's GitHub username
A proposed team name
- Good examples: kakuna, helium, orchid, magnet, indigo
- Exactly six (6) ASCII lowercase letters
- A single English word
- Must be professional
  - Sexism/Racism/etc. or any other harassment will be brought to the Dean of Students for sanctions
  - Must not contain any insults or negativity. Examples: suckers, copium, haters, betray, regret, losers...
- Must not contain anyone's name as a substring
- Should be unique
  - Words like heroes, awesome, are overused: they'll be accepted but might conflict with another team, if they conflict, the second team to submit will be assigned a different name.

Submission Procedure

All members of the team must submit the Google Form: Form

Marking

If you do not form a team before the due date, you will receive a mark of zero.
If you do not submit on time, you will receive a mark of zero. No late submissions are allowed. No extensions will be granted.
Every team member must submit. If you don't submit you will receive a mark of zero even if your other team members submitted.
You will be deducted one mark for each violation of the required submission format!
- This also includes violating the team name format

Project Part 2

2024-08-26T00:00:00+05:00

Project Part 2 -- Preparation

Due date: Check the schedule.

Learning Objectives

Refine requirements
Apply object-oriented analysis and design
Prototype a user interface.

Overview

The project description outlines the problem and a set of needs. The entire project has several deliverables. Subsequent deliverables may be further refinements of earlier ones, and should address any TA feedback or concerns. This project part focuses on some initial preparations.

Deliverables

The following components are required for this project part.

1. Product Backlog:

Form the initial partial user stories into a backlog of the product's requirements. For each user story, estimate its size in story points, and denote its risk level (i.e., low, medium, or high). These requirements will likely evolve and should be maintained up-to-date throughout the project. Make sure they are numbered for easy reference. Note which stories will be released for the half-way checkpoint.

2. User Interface Mockups and Storyboard Sequences:

Diagram the layout of your main user interface and major dialogs, with comments describing the important elements. Also, diagram storyboard sequences of using your application, with transitions between different states of the user interface, caused by the user manipulating the controls or providing input. Within the diagrams, reference the relevant requirements. Convincingly show all the requirements are covered.

3. Object-Oriented Analysis:

Document your initial object-oriented analysis using CRC cards, focusing on the most important anticipated classes, their responsibilities, and collaborators.

4. Tool use:

Regular and consistent use of GitHub by all team members to share files for the project deliverables, to effectively track issues, and to manage tasks.

Hints

Ask questions about the requirements. Your interpretation of a need or task may be more complex or sophisticated than what is actually desired. Involve the TA for your team to gain feedback on your deliverables.

For neatness and readability, diagrams must be drawn well using a computer tool at a suitably legible scale for insertion into your document(s). Submitted diagram(s) must be embedded as image(s) in your team wiki, not linked externally.

You should look ahead to the future project parts and their deliverables to know what is coming. Do not wait until this part's deliverables are due before working on the next part.

Very likely, the requirements and user interface design will need to evolve during the project. You should keep this information up-to-date so that your team members are properly coordinated.

Submission Procedure

Use GitHub. Your team repo must be self-contained, i.e., not link to external content that might change.

Individual Task and Peer Review Form

After the due date, each member must complete an assessment form to describe his or her individual contribution to the project for this stage, and to review the performance of the other members: https://forms.gle/oJj2AAmdiXL7tybu9 Deadline to complete the form and submit it is 11:59 PM Tuesday 10 March

Marking

Each component of your deliverable will be evaluated individually based on the following rubric:

No part marks, no extra marks. No half marks.

Failure (0) :
- Incomplete. Missing important components.
- Or no submission
Unsatisfactory (2)
- A project submission that is missing components. Inconsistency is key. Missing important test cases. Lack of planning or adherence. Lack of attendance etc. Must demonstrate clear understanding of purpose and rationale behind deliverables.
- Or A project that effort has been put into and doesn't meet the requirements described. Most deliverable points have been met.
Satisfactory (3)
- A project submission that is missing minor components and contains some rough elements, but is NOT missing anything major.
Good (4)
- A not-quite excellent submission that meets the majority of all the requirements without problem.
Excellent (5)
- A excellent submission that meets the all the requirements without problem.
- A flawless project that meets the requirements described.

Project Part 3

2024-08-26T00:00:00+05:00

Project Part 3 -- Half-Way Checkpoint

Due date: Check the schedule.

Learning Objectives

Develop a usable, interactive, mobile application.
Refine object-oriented design.
Produce tests.
Follow scrum practices.

Overview

This project part focuses on a working prototype with about half of the requirements. You must have some server connectivity working by this part.

Deliverables

1. Addressing Feedback: Address any TA feedback on the previous project part.

2. Code Base of Prototype: Your source code will be inspected. The code should conform to some consistent coding convention. Your prototype should provide something tangible to the user, supporting about half the requirements. Maintain the source code in your source repository.

3. Code Documentation: For each source code file, you should have a brief introductory comment describing its purpose or role within the application or a design pattern, as well as any currently outstanding issues. Provide Javadoc interface documentation for your model classes and their public methods (at least).

4. Test Cases: Write runnable tests for your model and control classes. Provide intent tests for the requirements you have done. Deliver the test code to your source repository. If you have test data files, also include those. Test data should be realistic.

5. Object-Oriented Design: Document your object-oriented design using a UML class diagram (or diagrams), including details on key attributes and methods. Add notes as appropriate to clarify. The diagram(s) will likely evolve.

6. Product Backlog: Update the requirements as appropriate. Note which user stories are done at this checkpoint.

7. User Interface Mockups and Storyboard Sequences: Update these diagrams as appropriate.

8. Sprint Planning and Reviews: Maintain a record of what user stories are planned for each weekly sprint at its start, including who is to work on them. For each intermediate week, in the lab, have a sprint review with your TA mentor and all team members present to review the completed user stories.

9. Demonstration: During your team's assigned lab section after the due date (or possibly at a mutually arranged time), you must demo your working prototype to your TA mentor. All team members have to attend the demo.

10. Tool use: Regular and consistent use of GitHub by all team members to share files for the project deliverables, to effectively track issues, and to manage tasks.

There must be consistency across the deliverables at this checkpoint.

The evaluation of this project part will also include a component called "relative quality". This is used to differentiate projects that meet the minimum from projects that go "the extra mile".

Restrictions

Use Java, with Android, and Firestore.

Hints

Integrate early and often, even if some parts may have to be stubbed out to return canned data. Think about issues like server connectivity early in the design, rather than trying to retrofit them later.

Submission Procedure

Use GitHub. Your team repo must be self-contained, i.e., not link to external content that might change.

Please make sure your repository has the right version of code by the deadline. The TA will try to build your program from the submitted code. The TA may contact you if there are build issues.

If you reuse software, give proper credit to the original developers. Obtain approval for the use of third-party libraries as appropriate.

Individual Task and Peer Review Form

After the due date, each member must complete an assessment form to describe his or her individual contribution to the project for this stage, and to review the performance of the other members.

Marking

No part marks, no extra marks. No half marks.

Failure (0) :
- Incomplete. Missing important components.
- Or no submission
Unsatisfactory (5)
- A project submission that is missing components. Inconsistency is key. Missing important test cases. Lack of planning or adherence. Lack of attendance etc. Must demonstrate clear understanding of purpose and rationale behind deliverables.
- Or A project that effort has been put into and doesn't meet the requirements described. Most deliverable points have been met.
Satisfactory (7)
- A project submission that is missing minor components and contains some rough elements, but is NOT missing anything major.
Good (8)
- A not-quite excellent submission that meets the majority of all the requirements without problem.
Excellent (10)
- A excellent submission that meets the all the requirements without problem.

Project Part 4

2024-08-26T00:00:00+05:00

Project Part 4 -- Final Checkpoint

Due date: Check the schedule.

Learning Objectives

Develop a usable, interactive, mobile application.
Produce a product demonstration.
Follow scrum practices.

Overview

Your product is ready to be released!

Most deliverables are final, consistent updates of what was initiated for the previous project part.

Deliverables

Addressing feedback: Address any TA feedback on the previous project part.
Code Base of Prototype: Your source code will be inspected. The code should conform to some consistent coding convention. Maintain the source code in your source repository.
Code Documentation: For each source file, you should have a brief introductory comment describing its purpose or role within the application or a design pattern, as well as any currently outstanding issues. Provide Javadoc interface documentation for your model classes and their public methods (at least).
Test Cases: Write runnable tests for your model and control classes. Provide intent tests for the requirements you have done. Deliver the test code to your source repository. If you have test data files, also include those. Test data should be realistic.
Object-Oriented Design: Update your object-oriented design using a UML class diagram (or diagrams), including details on key attributes and methods. Add notes as appropriate to clarify. Include notes on the use of design patterns among the classes.
Product Backlog: Update the requirements as appropriate. Note which user stories are done at this checkpoint.
User Interface Mockups and Storyboards: Update these diagrams as appropriate.
Sprint Planning and Reviews: Maintain a record of what user stories are planned for each weekly sprint at its start, including who is to work on them. For each intermediate week, in the lab, have a sprint review with your TA mentor and all team members present to review the completed user stories.
Demonstration: Present an engaging demo. The final demo of your final prototype should show the usability of its user interface and the degree to which its functionality fulfills the user's needs. All team members must contribute to the demo. During the last week of labs you and your team will present this demo in less than 3 minutes to the entire lab. It will be your app live, with your team members. No videos, audio, or powerpoint. Just your live app. Make backup videos of the functionality in case your demo fails. Practice your demo in the lab room ahead of time. Make sure you can present your app by testing the projector and your devices the week before. All teams should participate and be present. Aim for live presentation in 3 minutes. Do not leave early.
Tool Use: Regular and consistent use of GitHub by all team members to share files for the project deliverables, to effectively track issues, and to manage tasks. There must be consistency across the deliverables at this checkpoint.

The evaluation of this project part will also include a component called "relative quality". This is used to differentiate projects that meet the minimum from projects that go "the extra mile".

Restrictions

Use Java, with Android, and Firestore.

Submission Procedure

Use GitHub. Your team repo must be self-contained, i.e., not link to external content that might change.

Please make sure your repository has the right version of code by the deadline. The TA will try to build your program from the submitted code. The TA may contact you if there are build issues.

If you reuse software, give proper credit to the original developers. Obtain approval for the use of third-party libraries as appropriate.

This demo should have a logical flow in what is presented (following a story about what a user would naturally do, not just enumerating assorted features).

Individual Task and Peer Review Form

After the due date, each member must complete an assessment form to describe his or her individual contribution to the project for this stage, and to review the performance of the other members.

Marking

No part marks, no extra marks. No half marks.

Failure (0) :
- Incomplete. Missing important components.
- Or no submission
Unsatisfactory (8)
- A project submission that is missing components. Inconsistency is key. Missing important test cases. Lack of planning or adherence. Lack of attendance etc. Must demonstrate clear understanding of purpose and rationale behind deliverables.
- A project that effort has been put into and doesn't meet the requirements described. Most deliverable points have been met.
Satisfactory (11)
- A project submission that is missing minor components and contains some rough elements, but is NOT missing anything major.
Good (14)
- A not-quite excellent submission that meets the majority of all the requirements without problem.
Excellent (16)
- A excellent submission that meets the all the requirements without problem.
- A flawless project that meets the requirements described.

Project Problem Description

2024-08-26T00:00:00+05:00

Project Problem Description

Project Problem Description

Warning: This is subject to change!

Event Lottery System Application

Description:

We want a mobile application where people can sign up for events at community centres that are popular and fill up fast. We want to allow people with limitations such as work, disability, etc. to be able to sign up for these events fairly and not have to sit refreshing a webpage until they can get a chance at reserving a spot.

How? Lottery! If I am running swimming lessons for 20 kids, I will post my event or series of events and I will let everyone join the waiting list for a period of a week. After the week is up, I will ask the system to choose 20 kids to sign up. The system will then notify these kids (or their guardians), if they say no they don’t want swimming lessons, then the system will sample another child to sign up. I can monitor the progress and then get access to the final list of everyone who signs up. If perhaps someone cancels later I can cancel them in the app and a new applicant is drawn.

Lottery systems are great because you don’t have to first get a chance to go to an event, you just have to say you are interested and if you’re lucky you will be offered a chance. This gives people who need the time, the time to sign up properly without a time pressure. Accessibility!

Features:

Pooling System:
- Organizers can draw from a waiting list of interested event attendees as selected participants.
QR Code Scanning:
- entrants can scan QR promotional code to view details about the event and also join the waiting list
Firebase Integration:
- Utilize Firebase for storing event details, attendee lists, and real-time check-in status updates.
Multi-User Interaction:
- Distinguish between entrants, organizers, and admin with special roles and privileges granted to each actor.
Image Upload:
- Allow event organizers upload event poster image
Geolocation Verification (Optional)
- Optionally use geolocation to verify where users are joining the waiting list from. This is the location provided by the device.

Scenario:

I want to sign my partner up to swim lessons, they need to learn how to swim if they are going to go canoeing with me. I go to the local rec centre, I see they have listed swimming lessons for beginners, I scan the QR code. I see that it is open to register for 2 more days. I click register. 2 days later when it is closed the system samples people, but not me. It notifies me that I wasn’t sampled in the first draw, but there might be a chance if someone declines. Nobody declines. Boo.
I am running an interpretive dance class where I teach the safety basics of dance (no eye gouging, that kind of stuff). I tell the app that I have classes every monday From 2025-01-01 to 2025-03-01, and that you need to register by 2024-12-15 and registration opens on 2024-12-01. The price is $60 and I can accommodate 60 people. I click publish and now an event is made where people can join the waiting list and they get this basic information. Also a QR code is generated that will lead them to this page.
I want to sign my partner up to piano lessons, they need to learn how to play if they are going to play piano with me. I go to the app, I go to my local rec centre, I see they have listed piano lessons for beginners, I scan the QR code. I see that it is open to register for 2 more days. I click register. 2 days later when it is closed the system samples people, but not me. It notifies me that I was sample.

Actors:

Entrant: a person who signs up for an event
Organizer: the entity that runs the event
Administrator: The entity that administers and runs the infrastructure

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.
Entrant: someone who declares their interest in signing up for an event by joining the waiting list
Waiting List: a record of entrants that showed interest in a specific event
Sign Up : An action of registering/confirming for an event when successfully selected
- You can think of this like accepting an invitation.
Profile : A screen on the application that holds information about an entrant
Choosing: Randomly selecting a number of entrants in the waiting list to be invited to sign up

User Stories:

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

As a (role), I want (goal).

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

User:

US 01.01.01 As an entrant, I want to join the waiting list for a specific event

US 01.01.02 As an entrant, I want to leave the waiting list for a specific event

US 01.02.01 As an entrant, I want to provide my personal information such as name, email and optional phone number in the app

US 01.02.02 As an entrant I want to update information such as name, email and contact information on my profile

US 01.03.01 As an entrant I want to upload a profile picture for a more personalized experience

US 01.03.02 As an entrant I want remove profile picture if need be

US 01.03.03 As an entrant I want my profile picture to be deterministically generated from my profile name if I haven't uploaded a profile image yet.

US 01.04.01 As an entrant I want to receive notification when chosen from the waiting list (when I "win" the lottery)

US 01.04.02 As an entrant I want to receive notification of not chosen on the app (when I "lose" the lottery)

US 01.04.03 As an entrant I want to opt out of receiving notifications from organizers and admin

US 01.05.01 As an entrant I want another chance to be chosen from the waiting list if a selected user declines an invitation to sign up

US 01.05.02 As an entrant I want to be able to accept the invitation to register/sign up when chosen to participate in an event

US 01.05.03 As an entrant I want to be able to decline an invitation when chosen to participate in an event

US 01.06.01 As an entrant I want to view event details within the app by scanning the promotional QR code

US 01.06.02 As an entrant I want to be able to be sign up for an event by scanning the QR code

US 01.07.01 As an entrant, I want to be identified by my device, so that I don't have to use a username and password

US 01.08.01 As an entrant, I want to be warned before joining a waiting list that requires geolocation.

Organizer:

US 02.01.01 As an organizer I want to create a new event and generate a unique promotional QR code that links to the event description and event poster in the app

US 02.01.02 As an organizer I want to store the generated QR code in my database

US 02.01.03 As an organizer, I want to create and manage my facility profile.

US 02.02.01 As an organizer I want to view the list of entrants who joined my event waiting list

US 02.02.02 As an organizer I want to see on a map where entrants joined my event waiting list from.

US 02.02.03 As an organizer I want to enable or disable the geolocation requirement for my event.

US 02.03.01 As an organizer I want to OPTIONALLY limit the number of entrants who can join my waiting list

US 02.04.01 As an organizer I want to upload an event poster to provide visual information to entrants

US 02.04.02 As an organizer I want to update an event poster to provide visual information to entrants

US 02.05.01 As an organizer I want to send a notification to chosen entrants to sign up for events.

This is the notification that they "won" the lottery.

US 02.05.02 As an organizer I want to set the system to sample a specified number of attendees to register for the event

US 02.05.03 As an organizer I want to be able to draw a replacement applicant from the pooling system when a previously selected applicant cancels or rejects the invitation

US 02.06.01 As an organizer I want to view a list of all chosen entrants who are invited to apply

US 02.06.02 As an organizer I want to see a list of all the cancelled entrants

US 02.06.03 As an organizer I want to see a final list of entrants who enrolled for the event

US 02.06.04 As an organizer I want to cancel entrants that did not sign up for the event

US 02.07.01 As an organizer I want to send notifications to all entrants on the waiting list

US 02.07.02 As an organizer I want to send notifications to all selected entrants

US 02.07.03 As an organizer I want to send a notification to all cancelled entrants

Admin:

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

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

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

US 03.03.02 As an administrator, I want to be able to remove hashed QR code data

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

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

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

US 03.07.01 As an administrator I want to remove facilities that violate app policy

Project Teams

2024-08-26T00:00:00+05:00

Project Teams

Project Problem Description

2024-08-26T00:00:00+05:00

Project Problem Description

Project Problem Description

Warning: This is subject to change!

Event Lottery System Application

Description:

Features:

Pooling System:
- Organizers can draw from a waiting list of interested event attendees as selected participants.
QR Code Scanning:
- entrants can scan QR promotional code to view details about the event and also join the waiting list
Firebase Integration:
- Utilize Firebase for storing event details, attendee lists, and real-time check-in status updates.
Multi-User Interaction:
- Distinguish between entrants, organizers, and admin with special roles and privileges granted to each actor.
Image Upload:
- Allow event organizers upload event poster image
Geolocation Verification (Optional)
- Optionally use geolocation to verify where users are joining the waiting list from. This is the location provided by the device.

Scenario:

I want to sign my partner up to swim lessons, they need to learn how to swim if they are going to go canoeing with me. I go to the local rec centre, I see they have listed swimming lessons for beginners, I scan the QR code. I see that it is open to register for 2 more days. I click register. 2 days later when it is closed the system samples people, but not me. It notifies me that I wasn’t sampled in the first draw, but there might be a chance if someone declines. Nobody declines. Boo.
I am running an interpretive dance class where I teach the safety basics of dance (no eye gouging, that kind of stuff). I tell the app that I have classes every monday From 2025-01-01 to 2025-03-01, and that you need to register by 2024-12-15 and registration opens on 2024-12-01. The price is $60 and I can accommodate 60 people. I click publish and now an event is made where people can join the waiting list and they get this basic information. Also a QR code is generated that will lead them to this page.
I want to sign my partner up to piano lessons, they need to learn how to play if they are going to play piano with me. I go to the app, I go to my local rec centre, I see they have listed piano lessons for beginners, I scan the QR code. I see that it is open to register for 2 more days. I click register. 2 days later when it is closed the system samples people, but not me. It notifies me that I was sample.

Actors:

Entrant: a person who signs up for an event
Organizer: the entity that runs the event
Administrator: The entity that administers and runs the infrastructure

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.
Entrant: someone who declares their interest in signing up for an event by joining the waiting list
Waiting List: a record of entrants that showed interest in a specific event
Sign Up : An action of registering/confirming for an event when successfully selected
- You can think of this like accepting an invitation.
Profile : A screen on the application that holds information about an entrant
Choosing: Randomly selecting a number of entrants in the waiting list to be invited to sign up