For each method, if name exists ask if they want to edit.
Each method will return an integer indicating how many were added.
Each method will ask the user to confirm if data is what they want,
otherwise, go back to top of the prompt
Each method will not accept arguments
Add Researcher Method
Add Organization Method
Add Collaboration Method
Reimplement Parser and overhaul argument checking (checkArguments())
Modularize the program as much as possible
XML semantic checks not actually implemented in last milestone
-Year values and urls
Other details on John's notes
One more question. When the user adds a researcher and has to enter
an organization, do we automatically have to add that organization
into the organization list?
And thanks for the diagram... I'm thinking we should also add commands
in the menu for the print stuff rather than make the user manually
enter them from the command line. What do you guys think?
Added the day that we can try and aim to finish following tasks. That
way, we're done on Sunday and can work on bugs, testing, and making
software more robust.
Things Still Need to Be Done:
- Add Edit method for an existing researcher - Saturday
- Add Edit method for an existing organization - Saturday
- Add Edit method for an existing collaboration -Saturday
- Redo checkArgument Method -Saturday
- Modularize program (maybe add a print class, parser class and
userInteraction class) - Saturday
- MyIsernXmlSaver class for converting List of Researchers,
Organizations, and Collaborations to XML file - Saturday
- Powerpoint presentation -Saturday
- Use cases --- Need at least 6 to fulfill assignment criteria -
Saturday
- Test Cases --- Make sure coverage with Emma is 100% - Sunday
Hopefully I did not miss anything
-Sonny
What Marcius and I talked about for output format to xml is that the
top of the class, we will create lists for researcher, org, and
collab. When we load the existing xml files,we add the information
into their respective lists.
Then during the add process, if the user confirms that the information
he entered for either r, o, or c is correct, then its added to the
lists already containing the existing xml r, o, or c. Only when the
person chooses to save do we convert the lists into xml files. I
think this is the easiest way, unless you can find a more effective
way of doing it.
Also, when the user confirms, the unique ID for that r, o or c is also
added to the uniqueIdList. Hope this helps.
-Sonny
I've added a name for each task and that person is in charge of making
sure it gets done. Doesn't mean we have to do it all on our own, just
means we need to make sure that task gets done.
+ + + + TO DO + + + +
Edit Existing Files --- I can't seem to get this to work, my brain is
dead. (Sonny)
Modularize Program --- I think we have enough time to modularize our
program (yay!) Separate user Input, printer, and parser. ( Any
volunteers? )
Powerpoint Presentation --- Still need you guys input for the slides.
(Sonny)
Use Cases --- We need at least 6. (Marcius)
Test Cases --- Make sure Emma is 100% or at least near there. (John)
We're almost there guys!