Weekly progress

Week 1

In this first week, I developed my individual webpage and then decided on a meeting time with my subgroup by combining our schedules. Finally, we discussed various ideas for the project which we voted on in class Monday Sept. 8th.

• Our selection was Dr. Java, a text editor.
• Our meeting time will be Wednesdays at 7pm.

Week 2

In this week we establish what our project would be. We also chose subgroup leaders to meet once a week. Additionally we assigned activities for everyone in the group to achieve this week's goals.

• Our subgroup leader is Alex Christou
• Our project is the JPilotExam Simulator
• My role this week will be to prepare and guide us through the meeting, take notes and display the results of the meeting on the forum as well as organize the tasks for the week and make sure that they get done. I will also get familiar with the the software and sign up for the repository system.
• A few things I've gathered about the Exam Builder can be found here.

Week 3

This week my subgroup met on Wednesday as scheduled. We completed the assignment given to us in class to be turned in on Friday. We established what our role would be within the bigger group for the week as decided by the subgroup leaders in their meeting. Our concrete decisions were:

• Every person must come up with at least 3 requirements by the end of the weekend.
• We split that work into 5 parts so that each one of us in group 3 would have something concrete to do for the week.
• Alex will continue to receive requirements from the rest of the group and post them on our wiki.
• Here's a flowchart I created for OpenExam.java and MainPanel.java
• Here are the comments for OpenExam.java and MainPanel.java which can also be found within the code in the repository system.

This is the subgroup leaders' decision:

Get really familiar with Version 1 of simulator code (google site: trunk --> scr --> org --> jpilotexam -->jps), which is the version in the repository. Type up a document describing everything found while doing this and explaining the code. Comment the code and update in repository.

This is how we are accomplishing it:

Review and Document this code and make a document of with each class name, input/outputs, what it does, and any other relevant information.

• David
  ExamController.java
  
• Sid
  ReviewPanel.java
  JPESimulator.java
  
• Nury
  OpenExam.java
  MainPanel.java
  
• Alex
  Result Panel.java
  Report Table.java
  JPSFlashScreen.javav
• Josh
  ExamPanel.java
  QEditorPane.java
  JPSExam.java
  

Week 4

This week my subgroup is helping with creating the power point presentation. Additionally, we are in chare of compiling all of the documentation created after the entire group researched the code. Because the documentation is not complete, and the formats every person used are very different, we decided to come up with a format so that we could split up the work and do it independently this week. Our individual work is as follows:

• Alex will work on one third of the power point presentation like every other group leader.
• Sid will compile the documentation for the files in the root folder and inside of util.
• David will compile the documentation for the files in the jps and swing folders.
• Josh will compile the documentation for the files in the ui folder
• I will compile the documentation for the files in the jpb folder which is all of the source for the Exam Builder

Once all the work is done, they will email it to me and I will put it in one file and upload it to the group's docuemnt page. This should be done by Sunday night. I will also work on my 1st Progress Report and have it done by Tuesday the 30th.

Week 5 (Sep 30 to Oct 7)

This week, we had our meeting as usual. In this meeting, we split up the work for the week. That work consists of making the Ignored, Marked, Correct and Wrong buttons work. We will also add an All button and give it functionality. Additionally we will place all th buttons that are on the Review Panel on the Exam Panel to give the user more flexibility. We will add a label to both panels explaining what the navigation buttons are for since it's not very clear. Our main priority was to have a Submit button on the Exam Panel so that the user does not need to press Review first and then Submit. Also the submit button is now called Finish which is kind of confusing since the user might think it means to close the review screen and not to end the exam itself. All these things will make navigating the software easier and more self-explanatory(less confusing).

• Alex and Nury will work on Correct and Wrong buttons and will fix the messages displayed when an end is reached.
• David and Sid will work on Ignored and Marked buttons.
• David will also add an ALL button to the Review Panel.
• Sid will add a label on top or below the buttons that says "Choose how to navigate the questions". He will add that to both the ReviewPanel and the ExamPanel.
• Josh will add the navigation buttons that are on the Review Panel to the actual Exam Panel without taking them off of the Review Panel and using the same functionality and test them extensively.

Week 6(Oct 7 to Oct 14)

• Fixed the "select all 2choices" bug
• Fixed the "Question1of3" bug
• Fixed all navigation messages to have spaces in between the words
• Hid Finish button in Exam panel after exam is finished

• Enter user name and password
• Then click on either sign-in or create user account
• The create option will create a user account with the username and password entered
• One last button Guest will allow user to go into the software as a guest without entering a user name or password.

Week 7(Oct 14 to Oct 21)

This week I met with my subgroup on a different day and at a different time. We met before discussion at 12:50pm to complete the peer evaluation. We also split up the work that needed to be done for the Simulator this week. So far we're on schedule and everything seems to be going well. Here's the breakdown of work:

• Alex will be fixing a few bugs in the LoginPanel which was created last week. He will also change the name of the XMLLoader to ExamLoader and find all the classes in which that class is called to change it there too.
• Josh will finish the Student class which he started last week. He will also merge the code from the Builder team and our team.
• Sid will be creating a Welcome screen with buttons to go to the Builder, Take and Exam, Log Out, View Grades, Edit Personal Info
• David will be creating a screen to Edit the personal information of the student such as name, email, password, etc. It will also have a button to go back to the welcome screen.
• I will be creating a screen to view the students progress, grades for each exam taken and overall grade. This will contain labels to display the student's personal information and overall grade and a textbox with the list of exams taken and their grades. It will also have a button to go back to the welcome screen.

Since Josh will be finishing the Student class this week, we will not be able to give these screens full functionality. So I anticipated that next week we will all be working on making the account system work properly and lnking all of our work together.

Week 8(Oct 21 to Oct 28)

This week my subgroup will be creating the test case template and the test result template. We will also be designing the teacher account and the teacher class as well as working on the assignment given to us in class by Mr. Dobbins.

• Alex is going to be working on the presentation with the other group leaders and preparing himself to present, updating the group website with our weekly work schedule, and receiving the test case and test result templates from us and putting them into the same format and in a public place in our website.
• I will be designing the teacher account class and emailing the results to osh so he can start writing the code. I will be printing out the assignment to bring to class. I will also make small modifications to the GUIs once I have a design for the teacher accounts to move towards that.
• Sid will be designing the test case Template which he will email to Alex soon.
• David will be designing the Test Result Template which he will email to Alex soon.
• Josh will start to write code for the Teacher Class as soon as I email the design I came up with to him.

After giving it some thought and consulting with my groupmates, I came up with this design for the teacher account class solution. We're now going to have just a User Class for both teachers and students which will have a:

• First Name
• Last Name
• Login
• Password
• boolean IsTeacher
• JPExam array
• JPResult array
• studentsArray which will be used for teachers only.
• TeacherUserName which will be null for a teacher and only used to identify which teacher is the student associated with.

We need a new method for when a teacher logs in, to get an array of their current students:

Something like getStudents(TeacherUserName) which would return all the student for which TeacherUserName equals the parameter passed in which is the UserName of the teacher that just logged in.

The login method in the LoginPanel class, which calls a compareTo method in the User class will now have to check to see if the user is a teacher and call the getStudents method in the User class.

• Login, Guest, New Account and Exit in the Login Screen
• Edit and Back in Student Grades Screen
• Update Revert and Back in Edit Account Screen
• And also to the 5 buttons in the Welcome screen.
• I will give all 4 of these screens the right Icon for our program.
• In the Review Panel, gave mnemonics to the Wrong, Correct and Finish buttons.

Week 9 (Oct 28 to Nov 4)

This week I will be creating a test plan with my subgroup's members. We will also be evaluating our peer's test plan for the MS Paint application. I will individually be printing out and bringing that to class. This week I will also write my 2nd progress report.

Week 10 (Nov 4 to Nov 11)

This week we plan to write all the code necessary to link all of the registration and login screens to the welcome screen according to the design in my diagram.

• If Obj file is null, make createAdmin show up --David
• remove CreateUser button in login screen-- Sid
• When you click Login button-> check who is logging in, then make sure it saves correctly to disk --Josh
• Check instanceOf and initialize the right user in the JPESimulator class-- Josh
• change WelcomePanel to WelcomeStudent --Sid
• Add parameter to createUser (int type)-- Nury
• CreateUser returns to appropriate welcome screen/Exits on Create/Cancel--Nury
• Remove Build Exam button from student -- Nury
• Test Plan Revamp --Alex
• Make Welcoem Screens fully functional--Sid
• Add parameter to StudentsGrade which is the students username --David

This is what I've done so far this week

• Gave icons to all the windows I found without it.
• Logout buttons for Admins and teachers work.
• The create User in Loginpanel creates a Teacher for now.
• That then takes you back to the Admin Login Panel .
• From there you can log out and login as the teacher and then create students and log in as students.
• The admin login functionality is not implemented, only when you create a teacher it takes you to the admin welcome screen so you can see it that way.
• Build exam buttons also work now.
• For some reason the change password button in WelcomePanel for students does not work. Look into it
• For studentGrades and EditAccountInfo, I added a parameter that takes in a User tempUser
• My idea is to add a User tempUser to the JPESimulator so that we can use that to acces the grades and change the account info.

Week 11 (Nov 11 to Nov 18)

This week I had a meeting with my subgroup to discuss this week's work. Josh proposed adding a picture of the user so that teachers can identify their students. David discussed a bug that was not allowing the Admin to login correctly sometimes. We will both be working on that to find and fix the problem.

I found the bug that was not letting the Admin log in correclty. When you logged in once and logged out, the JPESimulator.admin was being set to null. The fix was easy but finding the problem took a little bit of time. Apparantly David and I worked on it separately and we both committed our solutions, but the sbug is fixed so it probably accepted the last one.

I played with the existing system to identify current bugs. Found the following:

• Delete Teacher functionality needs to be implemented
• Admin is not being created anymore
• Edit Admin needs to be implemented.
• Edit Teacher should use the EditPanel and not the CreateUser panel.
• CreateUser should create on Enter and also needs to check for missing info.
• New Account button in the Login screen no longer needed after bugs are fixed.
• The Change Password button in Student Welcome Panel is not working.

David, Josh and I have been working on fixing these bugs, Sid has been adding missing functionality to all the screens and Alex has been fixing out test cases and he was also really sick for the majority of the week. :(

Week 12 (Nov 18 to Nov 25)

This week we had a meeting to discuss the implementation of the following:

• Req 8: Exam information Screen's Time field should be labeled time limit and have the unit(seconds)(Sid)
• Req 17 (print), Nury
• Req 18 (save), Nury
• Revise Admin welcome screen to act/look like teacher (David)
• Make create user text fields have action listener(Sid)
• Fix create user screen that nury messed up (Nury)
• Checks that nothing is empty and passwords match in CreateUser(Alex)
• Fix Change Password button on student welcome(Sid)
• Fix edit admin button(David)
• Improve picture stuff (JOsh)

• Up to 3.04 Sid
• 3.05 to 3.09.1 Josh
• 4.01 to 9.01 Alex
• 10.01 to 16.01 David
• 17.01 to 24.01 Nury

I have spent a couple of hours working on saving the results to the disk after a student takes a test. I had some trouble getting the right format and now I have some trouble using dynamic naming for the file. I will continue to work on it, right now it saves the file with a static name so each time it will get replaced. I added, the title, the score and some instructions to the file on top of the questions and their answers. I still need to add a Pop up message saying that the file has been saved and specifying the name of it. And also I'd like to use a Save dialog box to allow the user to pick location and name on their own, but I've never done that so I have to keep looking into it.

Week 13 (Nov 25 to Dec 2)

Save functionality is fully implemented now, except the user has to make sure they enter an extension. I would like to make it so that it defaults to html since it's an HTML file that is getting saved.

Our weekly meeting will most likely be today(Tuesday) since we're all getting out of town tomorrow. We just need to go over testing and the progress we have made so far. We need to discuss any requirements that still need to be implemented.

After the meeting we have decided to go ahead and start testing already, and skip those test cases involving requirements that are yet to be implemented for now. We realize most likely we're not going to be doing this over Thanksgiving so testing will be completed by Friday Dec 5th.

I will be working on the Printing functionality for the rest of the week. The user should be able to print an exam's results when he/she's done. I will try to work on both that and the testing simultanously.

This is what was decided for this week: