Overview

For this project you will implement the data manager of a simplified version of the popular social networking software Facebook (http://www.facebook.com). Facebook allows you to keep lists of friends, check their online status, e-mail them, and other tasks. In addition, you can add applications in order to customize your account. The first part of your project consists of submitting an UML class diagram representing the design of the data manager; the second part consists of implementing your design and providing a gui. Keep in mind that each part has a separate deadline.

We want to remind you that you don't need to have an account in Facebook or use Facebook in order to complete this project.

Objectives

• Practice the design and implementation of object-oriented software systems.
• Learn to use UML class diagrams to represent object-oriented designs.

Grading

• (35%) Design (UML Class Diagram)
• (20%) Implementation of provided design
• (25%) Tests
  • (15%) Public Tests
  • (10%) Release Tests
• (10%) GUI
• (10%) Style

Clarifications

Any clarifications or corrections associated with this project will be available at Clarifications

Code Distribution

The project's code distribution is available by checking out the project named FacebookJr. The code distribution provides you with the following:

• A package named model - Package where all the classes representing your design will be implemented.
• A package named gui - Package for gui classes.
• A package named tests - Includes the public tests (PublicTests.java) and a shell for a class (StudentTests.java) for student tests. Notice that you are not required to write student tests for this project; however, we recommend you do so.

Specifications

Data Manager

For this project you will implement the data manager (model component of the MVC paradigm) for a simplified version of Facebook (http://www.facebook.com). The data manager you will design will allow us to add friends, to post to a person's wall, and to complete other typical activities you can find in facebook. Keep in mind that for this project you will implement a subset of the facebook functionality. The first part of your project consists of submitting an UML class diagram representing the design of the data manager; the second part consists of implementing your design.

The functionality of the system you will implement is represented by the interface FacebookJrDBManager (FacebookJr Database Manager). The interface represents the methods available to anyone trying to make use of the system. The javadoc documentation for the project can be found at javadoc. Your task for the design part of the project is to come up with a set of classes and interfaces that together provide the functionality defined by the FacebookJrDBManager interface.

Access to the data manager functionality will be possible through a class named FacebookJrDB that you must define. This class implements the FacebookJrDBManager interface. Feel free to add any instance variables and private methods to this class. Public and release tests create an instance of the FacebookJrDB class in order to test your system.

Keep in mind that your implementation must match your design, otherwise you will lose significant points. We encourage you to start working on this project as soon as possible, as there are a lot of details that can not be completely specified in this description. The earlier you start, the sooner you will get the feedback you need to complete this assignment. The system you will design deals with following entities:

• Person → A person has a name, e-mail, gender(M/F), relationship status (Single/Married), photo, friends, status (e.g., "I am tired") and a wall application (area where people can leave messages). In addition, a person can be part of several networks.
• Networks → A network is defined as a group of people and it is identified by name. Three possible types of networks are available:
  • Regional Network → Group of people that belongs to certain geographical area (e.g., California, East Coast, etc.)
  • High School Network → Group of people that attended a particular high school. A high school network keeps track of the year students graduated, and which students attended college.
  • College Network → Group of people that attended a particular college. A college network keeps track of the year students graduated, and the major associated with each student.
• Application→ Applications are programs the user can add. Every person has a wall application by default. In this project, for simplicity, we will only have one application (Wall); however, your design should assume that future versions of the system will allow users to add different kinds of applications. An application will be identified by a name, author, and url. The Wall application allows one person to leave a message on another person's wall. The wall application will have "Wall", "FacebookJr", and "http://www.notreal.really" as name, author, and url, respectively.

Your design should make use of object-oriented design concepts (e.g., generalization, specification, etc.) discussed in class. Keep in mind that having a large number of classes does not guarantee a better design grade. Your UML class diagram does not need to include all the parameters to each method, though return types are interesting. You are encouraged to list all the class fields and their types. Your UML class diagram does not need to include the FacebookJrDBManager interface. In addition, the class diagram for the FacebookJrDB class does not need to include the FacebookJrDBManager methods. You should use some graphic tool (e.g., AmaterasUML) to generate the UML class diagram. You will not get any extra credit for using a particular tool; just make sure you provide the file representing your design.

For this project you may assume that all names (e.g., persons' name, networks' name, etc.) are unique (i.e., no duplicates will occur).

GUI

The GUI you will implement represents the gui a FacebookJr system administrator will use to interact with the system. You get to decide how your GUI looks like and how it interacts with the FacebookJrDB class. When it comes to the GUI keep the following in mind:

• Your UML class diagram does not include any GUI information (classes).
• You gui must use a JFrame, JButton(s), and JTextField(s). Feel free to add other Swing components.
• You do not need to implement a fancy/complex/beautiful GUI to get full credit.
• Your GUI must provide access to the functionality associated with the following FacebookJrDB methods: addPerson, getInfoPerson, removePerson, addRegionalNetwork, addHighSchoolNetwork, addCollegeNetwork, getAllPersons, getAllNetworks, and findMatches. You get to decide how to provide access to the functionality through the GUI (this is your opportunity to create and design!)
• You may not use System.out.println.
• Feel free to use JOptionPane class methods.

All your GUI code must be located in the gui package. Make sure you define a class named FacebookGUI that we can use to run the GUI application.

Requirements

• We expect to see at least four classes (FacebookJrDB and three additional classes) in your design.
• You should use maps/sets to keep track of your data. In particular, do not use arrays and then call Collection.sort to sort the data. Your implementation should be as efficient as possible.
• Verify that your project passes the submit server tests (https://submit.cs.umd.edu/)
• See StudentTests.html for information regarding the implementation of student tests.
• You must attempt to submit your project immediately after checking out the project (even if you have not implemented any methods). This will allow you to verify that the submission process is working as expected.
• You should submit your project often. This will keep versions of your project in the submit server that are easy to retrieve (you can also get previous versions from your CVS repository). If your computer crashes or you experience any other problem you will have a permanent backup in the submit server.
• Make sure you check your project results in the submit server. Those are the results we use to compute your grade.
• You have three tokens for this project in the submit server.
• Style
  • Good variable names.
  • You must avoid code duplication by calling appropriate methods (rather than cutting and pasting code). You may define your own private utility methods to perform often repeated tasks.
  • Style as defined by the Eclipse Format Element option (Source → Format → Format Element) or as specified in Code Conventions for the JavaTM Programming Language (focus on the following sections: Indentation, Declarations, Statements, White Space, and Naming Conventions).
  • Although you should avoid source lines exceeding 80 characters, you will not be penalize if they are present in your code.

Honor Section Requirements

Your data manager should be able to keep track of photos associated with a person. For each photo you should keep track of the photo url, the date the photo was taken, a description and the size. Your gui should provide access to the photos associated with a person.

Submission

Design Submission

Submit a UML class diagram with your design by creating a pdf document or image file named uml (e.g., uml.pdf or uml.jpg) and then uploading this file to the submit server (use the "submit" link for "FacebookJr UML Design"). Double-check your submission is correct by downloading it from the submit server after submitting.

In a Windows environment you can create pdf files by using CutePDF Writer, a free tool available at:

http://www.cutepdf.com/Products/CutePDF/writer.asp.

Implementation Submission

Submit your implementation using the Eclipse "Submit Project" option (available by right clicking on the project folder).

Academic Integrity

Please make sure you read the academic integrity section of the syllabus so you understand what is permissible in our programming assignments. We want to remind you that we check your work against other students' work and any case of academic dishonesty will be referred to the University's Office of Judicial Programs.