CS360 - archive

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

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.

Objectives

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.

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:

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. 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

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.

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.

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

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:

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();
}
}

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 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.

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:

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

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

Description:

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

Assignment 1

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

Learning Objectives
Problem Description
Deliverables
Demonstration Actions
Hints
Losing Marks
Submission Procedure

Due date: Check the schedule.

Learning Objectives

Solve a problem by constructing a simple, interactive application using Android and Java.

Document an object-oriented design in Unified Modeling Language.

Problem Description

Consider the situation of someone who wants to create and manage a wishlist of books they want to read. Develop a simple, attractive, and intuitive Android mobile app to assist users in organizing their reading preferences. Let's name this app: YOURCCID-MyBookWishlist (e.g., kennyw-MyBookWishlist).

Using this app, users can maintain a list of books they wish to read. Each book entry in the wishlist has the following editable fields:

Book title (textual, up to 50 characters)
Author name (textual, up to 30 characters)
Genre (e.g., Fiction, Non-Fiction, Mystery)
Publication year (four-digit integer)
Status (Read/Unread)

The app must allow the user to:

Show a list of books in their wishlist, displaying the title, author, genre, and read status.
Add a new book to the wishlist (appends to the bottom of the list).
View and edit the details of an existing book entry, including title, author, genre, and read status.
Delete a book from the wishlist.
See the total number of books in the wishlist and the count of books marked as read.

The list need not display all the information for an item if screen space is limited. Minimally, each item in the list should show its title, author, genre, and read status.

The app must assist the user in proper data entry. For example, use appropriate user interface controls to enforce particular data types and avoid illegal values.

For this assignment, the data need not be persistent across runs of the app.

The app must assist the user in proper data entry. For example, use appropriate user interface controls to enforce particular data types and avoid illegal values.

For this assignment, the data need not be persistent across runs of the app.

Encode your campus computing ID in the app name. Specifically, the app name must show up as YOURCCID-MyBookWishlist (e.g., kennyw-MyBookWishlist).

Deliverables

Code Base: Your complete source code and compiled binary, implementing the working app and its user interface, will be inspected and run by the TA. The Android Studio project and APK (Android Package Kit) binary must be included in the submission. Each class must contain comments describing its purpose, design rationale, and any outstanding issues.
Video: The video is a demonstration of the app. The video file must be included in the submission. The video is meant to show that the demonstration actions below actually work. No audio is needed. Maximum duration is 3 minutes. Focus on just the screen of the app, not the whole desktop. For visual clarity, do not use a handheld camera.
System Documentation:

Describe the structure of your app's object-oriented design using UML class diagram(s), saved as non-lossy image file(s).` Focus on the most important classes that you designed and implemented. Add notes to describe the main responsibilities of these classes.

You do not need to include classes from android or java standard library in your UML.

Demonstration Actions

Open the app from the launcher.
Show the list of books in the wishlist, with none so far. (This could be the initial screen.)
Add a book to the wishlist with the title "The Great Gatsby," author "F. Scott Fitzgerald," genre "Fiction," publication year 1925, and status "Unread."
Show the list and the total count, with this item.
View/edit this item to update the title to "The Great Gatsby: Updated Edition" and mark it as "Read."
Show the list and the updated counts, with this modified item.
Add another book to the wishlist with the title "To Kill a Mockingbird," author "Harper Lee," genre "Fiction," publication year 1960, and status "Unread."
Show the list and the updated counts, with the two books.
Add one more book to the wishlist with your CCID as the author and your student number as the title of the book, status "Read", year 2024.
Show the list and the updated counts, with the three books.
View/edit the details of one book in the wishlist.
Delete one book from the wishlist.
Show the list, with the remaining books.
View the details of one book in the wishlist.
Delete the remaining books from the wishlist.

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 These are brown M&M rules.

Submission Procedure

Create an assignment directory called ROLLNUM-MyBookWishlist (e.g., 25100052-MyBookWishlist), and within it have three subdirectories: code, video, doc.

Your Android Studio project directory goes within code. The compiled binary APK file(s) should be found within an /app/build/intermediates/apk/debug/app-debug.apk subdirectory or /app/build/outputs/apk/debug/app-debug.apk within the project directory. The video file goes in the video subdirectory. The UML documentation goes in the doc subdirectory.

Zip the assignment directory and upload to eClass.

e: It must be a zip file with the .zip file extension.

Please make sure all the required files are included to build the app. The TA will test your app from the submitted code and APK file.

The app name must show up as ROLLNUM-MyBookWishlist (e.g., 25100052-MyBookWishlist), so that it can be easily distinguished from other submissions.

This is how the assignment will be marked:

There are no inbetween marks, no part marks.

Rubric for Android App Assignment - MyBookWishlist

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

Class Participation Exercise Simple Factory

2020-03-27T00:00:00+05:00

Class Participation Exercise

Write a Simple Factory that opens a String URI that can either be to:

a file (starts with file:///),
a webpage (starts with http://),
or a TLS/SSL encrypted webpage (starts with https://).

You have the File class, the HTTPFile class and the HTTPSFile class that all accept a string in their constructor giving the URI (Uniform Resource Identifier). HTTPFile and HTTPSFile are subclasses of File. Please provide the code for the Simple Factory called FileFactory that has 1 method: public File getFile(String str).

BTW Java Strings have a method: public boolean startsWith(String prefix)

Class Participation Exercise Mock Objects

2020-03-23T00:00:00+05:00

Submit the java code as online text.

// CS360 Mock Object Quiz!
//
// You probably have to use the back of the page for this quiz.
//
//  WeatherService is a class that gets the weather report from a weather webservice.
//  It parses the webpage and produces a weather report. But sometimes you don't have
//  network conenctivity and sometimes the webservice goes down. Sometimes some
//  locations are not supported by the weather service.
//  Your boss wants you to test against some of these issues.
//
// 1. Write a mock object to enable testing of retrieveWeather.
// 2. Write a testCase using a mock object to ensures that if the weather service page 
//      returns a 404 code error that the LocationException is thrown
// 3. Write a testCase using a mock object to ensures that if the weather service page 
//      returns a 500 server side error code that the NoServiceException is thrown
//
//     Do not modify any of existing code. You may only write NEW code.
class WebserviceException extends Exception { ... }
class LocationException extends WebserviceException { }
class NoServiceException extends WebserviceException { }
class Page { int code; String contents; }
class Weather { ... }
class HTTPGetter {
    Page get(String url) {
        ...
    }
}
class WeatherService {
    HTTPGetter httpGet;
    WeatherService(HTTPGetter getter) { httpGet = getter; }
    protected parseWeather( Page page ) { ... }
    ...
    public Weather retrieveWeather() throws WebserviceException {
         Page page = httpGet.get( this.baseURL + "/” + Location.getCurrentLocation().toString());
         if (page.code == 404) {
             ...
             throw new LocationException("Location not supported!”); // TEST ME!
         } else if (page.code >= 500) {
             ...
             throw new NoServiceException("Service not reachable!”); // TEST ME!
         }
         Weather weather = parseWeather( page );
         return weather;
    }
}

Class Participation Exercise Command Pattern

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

Draw the UML Class diagram for commands that you expect would exist inside of a text editor.
Give example code of how you would fill in the CutMenuListener's void menuAction() Method of the Edit Menu's "Cut MenuItem"

class CutMenuListener {
// this is called when the Cut menu item in the Edit Menu
// is clicked or the key combo ctrl-X is pressed.
    public void menuAction() {

    }
}

Submit your drawing as a PNG file.