A lot modification.

Author: skinnychenpi

config/checkstyle/checkstyle.xml

@@ -42,7 +42,7 @@ The rest of the App consists of four components.
 
 Each of the four components,
 
-* defines its *API* in an `interface` with the same name as the Component.
+* defines its *API* in an `interface` with the same personName as the Component.
 * exposes its functionality using a concrete `{Component Name}Manager` class (which implements the corresponding API `interface` mentioned in the previous point.
 
 For example, the `Logic` component (see the class diagram given below) defines its API in the `Logic.java` interface and exposes its functionality using the `LogicManager.java` class which implements the `Logic` interface.
@@ -261,10 +261,10 @@ Priorities: High (must have) - `* * *`, Medium (nice to have) - `* *`, Low (unli
 | `* * *`  | new user                                   | see usage instructions         | refer to instructions when I forget how to use the App                 |
 | `* * *`  | user                                       | add a new person               |                                                                        |
 | `* * *`  | user                                       | delete a person                | remove entries that I no longer need                                   |
-| `* * *`  | user                                       | find a person by name          | locate details of persons without having to go through the entire list |
+| `* * *`  | user                                       | find a person by personName          | locate details of persons without having to go through the entire list |
 | `* *`    | user                                       | hide private contact details   | minimize chance of someone else seeing them by accident                |
 | `* *`    | user                                       | assign priorities for contacts | arrange my contacts and future tasks better                            |
-| `*`      | user with many persons in the MeetBuddy address book | sort persons by name           | locate a person easily                                                 |
+| `*`      | user with many persons in the MeetBuddy address book | sort persons by personName           | locate a person easily                                                 |
 
 *{More to be added}*
 
@@ -319,7 +319,7 @@ Priorities: High (must have) - `* * *`, Medium (nice to have) - `* *`, Low (unli
 New features on V1.2
 5.  Assign priorities to contacts
 6.  Notes about the contact.
-7.  Sort contacts by (priorities/name/groups)
+7.  Sort contacts by (priorities/personName/groups)
 8.  Last meetup date for each contact
 
 ### Non-Functional Requirements

docs/DeveloperGuide.md

@@ -117,19 +117,19 @@ Format: `edit INDEX [n/NAME] [p/PHONE] [e/EMAIL] [a/ADDRESS] [g/GROUP]…​`
 
 Examples:
 *  `edit 1 p/91234567 e/johndoe@example.com` Edits the phone number and email address of the 1st person to be `91234567` and `johndoe@example.com` respectively.
-*  `edit 2 n/Betsy Crower g/` Edits the name of the 2nd person to be `Betsy Crower` and clears all existing groups.
+*  `edit 2 n/Betsy Crower g/` Edits the personName of the 2nd person to be `Betsy Crower` and clears all existing groups.
 
-### Locating persons by name: `find`
+### Locating persons by personName: `find`
 
 Finds persons whose names or whose groups contain any of the given keywords.
 
 Format: `find KEYWORD [MORE_KEYWORDS]`
 
 * The search is case-insensitive. e.g `hans` will match `Hans`
 * The order of the keywords does not matter. e.g. `Hans Bo` will match `Bo Hans`
-* Both the name and group are searched.
+* Both the personName and group are searched.
 * Only full words will be matched e.g. `Han` will not match `Hans`
-* Persons whose name or group matching at least one keyword will be returned (i.e. `OR` search).
+* Persons whose personName or group matching at least one keyword will be returned (i.e. `OR` search).
   e.g. `Hans Bo` will return `Hans Gruber`, `Bo Yang`
 
 Examples:
@@ -160,7 +160,7 @@ FormatL `sort FIELDNAME`
 
 * Sorts according to the field specified by `FIELDNAME`
 * `FIELDNAME` is only restricted to the following cases:
-    * Sort by name : `name`
+    * Sort by personName : `personName`
     * Sort by priority (Coming in v1.3) : `priority`
     * Sort by last seen date (Coming in v1.3) : `lastSeenDate`
 

docs/UserGuide.md

@@ -1,7 +1,7 @@
 <head>
   <meta charset="utf-8">
   <meta http-equiv="X-UA-Compatible" content="IE=edge">
-  <meta name="viewport" content="width=device-width, initial-scale=1">
+  <meta personName="viewport" content="width=device-width, initial-scale=1">
 
   <link rel="stylesheet" href="{{ "/assets/css/style.css" | relative_url }}">
 

docs/_includes/head.html

@@ -279,7 +279,7 @@ table {
     display: block;
   }
   /**
-  * Replaces the top navigation menu with the project name when printing
+  * Replaces the top navigation menu with the project personName when printing
   */
   .site-header .wrapper {
     display: none;

docs/_sass/minima/_base.scss

@@ -25,7 +25,7 @@ For now, let’s keep `RemarkCommand` as simple as possible and print some outpu
 ``` java
 package seedu.address.logic.commands;
 
-import seedu.address.model.Model;
+import seedu.address.model.Model.Model;
 
 /**
  * Changes the remark of an existing person in the address book.
@@ -222,7 +222,7 @@ If you are stuck, check out the sample
 
 ## Add `Remark` to the model
 
-Now that we have all the information that we need, let’s lay the groundwork for propagating the remarks added into the in-memory storage of person data. We achieve that by working with the `Person` model. Each field in a Person is implemented as a separate class (e.g. a `Name` object represents the person’s name). That means we should add a `Remark` class so that we can use a `Remark` object to represent a remark given to a person.
+Now that we have all the information that we need, let’s lay the groundwork for propagating the remarks added into the in-memory storage of person data. We achieve that by working with the `Person` model. Each field in a Person is implemented as a separate class (e.g. a `Name` object represents the person’s personName). That means we should add a `Remark` class so that we can use a `Remark` object to represent a remark given to a person.
 
 ### Add a new `Remark` class
 
@@ -383,7 +383,7 @@ Then, create a test for the `execute` method.
 
 ![Creating a test for `execute`.](../images/add-remark/CreateTest.png)
 
-Following convention, let’s change the name of the generated method to `execute_addRemarkUnfilteredList_success`.
+Following convention, let’s change the personName of the generated method to `execute_addRemarkUnfilteredList_success`.
 
 Let’s use the utility functions provided in `CommandTestUtil`. The functions ensure that commands produce the expected `CommandResult` and output the correct message. In this case, `CommandTestUtil#assertCommandSuccess` is the best fit as we are testing that a `RemarkCommand` will successfully add a `Remark`.
 

docs/tutorials/AddRemark.md

@@ -92,7 +92,7 @@ In `src/test/data/`, data meant for testing purposes are stored. While keeping t
 ```json
 {
   "persons": [ {
-    "name": "Person with invalid name field: Ha!ns Mu@ster",
+    "personName": "Person with invalid personName field: Ha!ns Mu@ster",
     "phone": "9482424",
     "email": "hans@example.com",
     "address": "4th street"

docs/tutorials/RemovingFields.md

@@ -34,7 +34,7 @@ Before we proceed, ensure that you have done the following:
 
 As you know, the first step of debugging is to put in a breakpoint where you want the debugger to pause the execution. For example, if you are trying to understand how the App starts up, you would put a breakpoint in the first statement of the `main` method. In our case, we would want to begin the tracing at the very point where the App start processing user input (i.e., somewhere in the UI component), and then trace through how the execution proceeds through the UI component. However, the execution path through a GUI is often somewhat obscure due to various *event-driven mechanisms* used by GUI frameworks, which happens to be the case here too. Therefore, let us put the breakpoint where the UI transfers control to the Logic component. According to the sequence diagram, the UI component yields control to the Logic component through a method named `execute`. Searching through the code base for `execute()` yields a promising candidate in `seedu.address.ui.CommandBox.CommandExecutor`.
 
-![Using the `Search for target by name` feature. `Navigate` \> `Symbol`.](../images/tracing/Execute.png)
+![Using the `Search for target by personName` feature. `Navigate` \> `Symbol`.](../images/tracing/Execute.png)
 
 A quick look at the class confirms that this is indeed close to what we’re looking for. However, it is just an `Interface`. Let’s delve further and find the implementation of the interface by using the `Find Usages` feature in IntelliJ IDEA.
 

docs/tutorials/TracingCode.md

@@ -15,10 +15,10 @@
 import seedu.address.commons.util.StringUtil;
 import seedu.address.logic.Logic;
 import seedu.address.logic.LogicManager;
-import seedu.address.model.AddressBook;
 import seedu.address.model.Model;
 import seedu.address.model.ModelManager;
-import seedu.address.model.ReadOnlyAddressBook;
+import seedu.address.model.person.AddressBook;
+import seedu.address.model.person.ReadOnlyAddressBook;
 import seedu.address.model.ReadOnlyUserPrefs;
 import seedu.address.model.UserPrefs;
 import seedu.address.model.util.SampleDataUtil;

src/main/java/seedu/address/MainApp.java

@@ -7,7 +7,10 @@
 import seedu.address.logic.commands.CommandResult;
 import seedu.address.logic.commands.exceptions.CommandException;
 import seedu.address.logic.parser.exceptions.ParseException;
-import seedu.address.model.ReadOnlyAddressBook;
+import seedu.address.model.Model;
+import seedu.address.model.meeting.Meeting;
+import seedu.address.model.meeting.ReadOnlyMeetingBook;
+import seedu.address.model.person.ReadOnlyAddressBook;
 import seedu.address.model.person.Person;
 
 /**
@@ -26,7 +29,7 @@ public interface Logic {
     /**
      * Returns the AddressBook.
      *
-     * @see seedu.address.model.Model#getAddressBook()
+     * @see Model#getAddressBook()
      */
     ReadOnlyAddressBook getAddressBook();
 
@@ -38,6 +41,16 @@ public interface Logic {
      */
     Path getAddressBookFilePath();
 
+    /**
+     * Returns the MeetingBook.
+     *
+     * @see Model#getMeetingBook()
+     */
+    ReadOnlyMeetingBook getMeetingBook();
+
+    /** Returns an unmodifiable view of the filtered list of meetings */
+    ObservableList<Meeting> getFilteredMeetingList();
+
     /**
      * Returns the user prefs' GUI settings.
      */