superlinguini / cs2340 Goto Github PK

1. Create your team's Android Project and Import into Git
2. Create an opening or welcome screen which has options for Login and Registration. You may have some other method of differentiating login and registration, if you do not want an opening screen.
3. If someone selects Login, then you should display a way to enter the user name and password.
4. If someone requests login, you should check for the correct user name and password. For this first milestone, you may have a hard coded user with name "user" and password "pass" to check against.
5. If the login matches user name / password then go to your application. Otherwise, notify of the bad login attempt.
6. Canceling the login (press Cancel or going back a screen for example) will close out the login attempt , but no information is recorded and the application does not start up. Note here you are not explicitly required to have a cancel button, just a way to back out of the login.
7. Once in the application, there should be a way to logout. After logging out, the application should return to the welcome / opening page.

• Android project is created and launches .... (5)
• Welcome screen displays (or alternative).... (5)
• Welcome screen (or alternative) has controls for login or registration .... (5)
• Selecting login brings up screen to enter information .... (5)
• Screen displays fields for inputting user name and password .... (5)
• Login/Cancel(abort login) has appropriate action (10)
• Logout functions correctly (5)

Understand MVC and have a running app

Story/Task Details

• Edit and commit files as specified
• Test out adding and removing files
• View Git logs

Part 1 - Individual Who's Who

Part 2 - Team Page

Part 3 - Team Contract

Part 4 - Project Planning

• Create ClassStanding Enum with getters and setters.

• Add tostring Method to ClassStanding

• Add ClassStanding attribute to Students Class

Story/Task Details

• Download and unzip resource file
• Set up and upload zip to M2 repository
• Create branch called original

Hola! @SuperLinguini has created a ZenHub account for the SuperLinguini organization. ZenHub is the only project management tool integrated natively in GitHub – created specifically for fast-moving, software-driven teams.

How do I use ZenHub?

To get set up with ZenHub, all you have to do is download the browser extension and log in with your GitHub account. Once you do, you’ll get access to ZenHub’s complete feature-set immediately.

What can ZenHub do?

ZenHub adds a series of enhancements directly inside the GitHub UI:

• Real-time, customizable task boards for GitHub issues;
• Multi-Repository burndown charts, estimates, and velocity tracking based on GitHub Milestones;
• Personal to-do lists and task prioritization;
• Time-saving shortcuts – like a quick repo switcher, a “Move issue” button, and much more.

Add ZenHub to GitHub

Still curious? See more ZenHub features or read user reviews. This issue was written by your friendly ZenHub bot, posted by request from @SuperLinguini.

Story/Task Details

• Each member should install Gradle
• Each member will create a build file using gradle to build the application
• The build file should support - compileJava, compileTest, javadoc, clean, jar

The Following Changes should be done in the StudentEditController class

• Add an @FXML reference to the widgets you added for class standing
• Edit the initialize method to handle any start up code you need.
• Edit the setStudent method to set your widget to a default value
• Edit the OK button press to pull the information out of your new widget and put into the student instance.

1. Create a Context Diagram for the system
2. Brainstorm and list 10 user stories (title only) You may have fewer than 10 user stories if you can cover the entire system in fewer.
3. Each person on the team pick 1 user story and fully elaborate it (this is an individual grade, so you do not have to cover for a team mate). This includes the acceptance scenarios.

• Context diagram covers all actors ..... (5)
• 10 use cases (or fewer, see above) are listed. They are appropriate and phrased as verb-direct object ..... (10)

• Create widgets to allow input for ClassStanding in the StudentEditDialog.xml file.

Purpose
This exercise will ensure you can build and execute an Android application on your computer. You will also add functionality across the application stack to solidify your understanding of Model-View-Controller.

Recall from class the following guidelines:

Model - the classes that hold data for the application, and the business rules. These are normally POJO (plain old java objects) and are independent of any development frameworks you are using.

View - the screens that display and get information from the user. (in android, these are the .xml layout files)

Controller - a class associated with the view that has all the event handling code and code that interacts with the model to update information obtained from the model. In Android, these are called Activities.