oose-group5's website

Summary for iteration 3

Implemented basic functionalities of front and back ends and successfully built a demo. In the back end, we built the whole MySQL relationship database including user table, movie table and several other tables to satisfy the system needs. In addition, the whole system environment has been set up successfully, our system now works well under J2EE environment, JBOSS server and Sping framework.  In the front end, our GUI is based on AJAX technology and we implemented a simple Sign in/Sign out GUI and User virtual desktop GUI by using Ext-JS (a Javascript framework).  Also, we use JSON for interaction between front and back ends and the performance is great. In the end, two use cases: Sign in, Sign out have been fully implemented and a simple demo has been built to show our work.

What’s done in Iteration 3 (List Form):

What’s new ?

• Refined the system structure, including modified the model package and added exceptions class and corresponding classes
• Updated annotations in model package and successfully interacts with MySQL database, which means our model directly modify and retrieve data from database.

Fully implemented use-cases:

Back-end:

User related use-cases:

• Sign In: Registered user can sign in successfully and when user input wrong username and password combination, the system will refuse the sign in and show the error message.
• Sign Out: Registered user sign out successfully.

 

Administrator related use-cases:

• Sign In: Same as user’s sign in.
• Sign Out: Same as user’s sign out.

 

Front-end:

• Sign In UI: consists of two text fields and one button named “signin”. Administrator/user types his/her username and password in the corresponding text field and then clicks the button. These two actors use the same GUI when attempt to sign in.
• User Desktop UI: When signing in,  a windows like desktop which contains several icon buttons will be presented to the user; furthermore, user can click these buttons to access the movie resources.

 

Partially implemented features:

• Sign Up: New user need to be signed up for enjoying full functionalities of the Movie Maniac System and the implemented sign up function achieves this goal.
• Wrote some Junit tests for the classes but needed to be refined in next iterations.

Feature Plan:

Expectations for Iteration 4

For iteration 4, we expected to implement following user cases

 

Administrator/User

• Check Administrator Information(Administrator)
• Search for user(Administrator)
• Check user Information (Deactivate/Activate User) (Administrator)
• User Profile(User)

 

Movie:

• Create new Movie(Administrator)
• Search for movie(Administrator)
• Check Movie Information(Administrator)
• Modify movie information(Administrator)
• View movie information(User)
• Maintain Movie Following List(User)
• Score and Comment the Review(User)
• Search for movie(User)

 

Expectation for Iteration 5

For iteration 5, we expected to implement following user cases

Message System:

• Compose Mail(User)
• Inbox(User)
• Sent(User)

Friend List:

• View Other User’s Information(User)
• Friend List(User)
• Add Friends(User)

• Search User(User)

Recommendation System:

• Movie Recommendation(User)
• System Recommend Friend (Similar User’s Recommendation) (User)

 

Expectation for Iteration 6

For iteration 6, we expected to complete the whole system

• Fully JUnit test
• GUI
• Recommandation
• Code refactoring
• Regression testing
• Writing documents