Java - blogging application
- or -
Post a project like this3573
€30(approx. $32)
- Posted:
- Proposals: 3
- Remote
- #517852
- Awarded
Description
Experience Level: Entry
Estimated project duration: 3 - 4 weeks
General information for the business: Blog application
Kind of development: New program from scratch
Description of every module: With the diagrams included In the attached documents , the simplified class diagram of a blogging application is shown. Below that, three use case diagrams showing proposed functionality are shown. For ideas on how something could look like, there are plenty of examples on the internet, such as www.nujij.nl .
Create this application using the technology. Components to be used are Servlets, Java Server Faces, Java Persistency API and either Hibernate or EclipseLink with MySQL. The application server to run it on is JBoss 7.1.
All use cases have a priority assigned. For this assignment, only the ones called Must have to be done. That makes for a functional application, and we will assume our users are very nice and do not misbehave.
Most use cases should be self-explaining. The functionality ‘remove post’ should take care to remove answers to the removed post as well. Also, when creating a new post, you refer to an already existing one by saying ‘ @34 Bla… ‘ , which should build a link to – in this case – post 34. When removing a post, renumber this as well.
Description of requirements/functionality: A few hints on implementation:
1. Use a MVC pattern.
2. When adding a topic, add a (first) post as well.
3. When removing a post, don’t forget to remove all reactions to that post as well.
4. If the user adds a post, he may answer to another post by typing ‘ @12 Bla bla‘ meaning anwering to post 12. Keep track of these references, because:
5. When removing a post, recalculate references and change them accordingly.
6. We didn’t really cover how to work with privileges (it’s done by EJB.) Ignore privileges for now; all that matters is whether a user is logged on or not.
7. When trying to do something the user needs to be logged on for, catch it with a logon page. Having him lose his text because of the logging on is not nice.
Specific technologies required: Servlets, Java Server Faces, Java Persistency API and either Hibernate or EclipseLink with MySQL. The application server to run it on is JBoss 7.1.
Extra notes:
1. A domain model shows the entity types relevant in the domain and how they relate to each other. Also, it shows the kind of responsibilities for those main classes. Do not try to implement it literally, the implementation has more classes and methods.
2. The priorities are shown above the name of the Use Case (see attachment).
Please note- I am not looking for a production ready blog site of any sort. This is just a coursework, so the implementation doesn't require to be entirely working.
Kind of development: New program from scratch
Description of every module: With the diagrams included In the attached documents , the simplified class diagram of a blogging application is shown. Below that, three use case diagrams showing proposed functionality are shown. For ideas on how something could look like, there are plenty of examples on the internet, such as www.nujij.nl .
Create this application using the technology. Components to be used are Servlets, Java Server Faces, Java Persistency API and either Hibernate or EclipseLink with MySQL. The application server to run it on is JBoss 7.1.
All use cases have a priority assigned. For this assignment, only the ones called Must have to be done. That makes for a functional application, and we will assume our users are very nice and do not misbehave.
Most use cases should be self-explaining. The functionality ‘remove post’ should take care to remove answers to the removed post as well. Also, when creating a new post, you refer to an already existing one by saying ‘ @34 Bla… ‘ , which should build a link to – in this case – post 34. When removing a post, renumber this as well.
Description of requirements/functionality: A few hints on implementation:
1. Use a MVC pattern.
2. When adding a topic, add a (first) post as well.
3. When removing a post, don’t forget to remove all reactions to that post as well.
4. If the user adds a post, he may answer to another post by typing ‘ @12 Bla bla‘ meaning anwering to post 12. Keep track of these references, because:
5. When removing a post, recalculate references and change them accordingly.
6. We didn’t really cover how to work with privileges (it’s done by EJB.) Ignore privileges for now; all that matters is whether a user is logged on or not.
7. When trying to do something the user needs to be logged on for, catch it with a logon page. Having him lose his text because of the logging on is not nice.
Specific technologies required: Servlets, Java Server Faces, Java Persistency API and either Hibernate or EclipseLink with MySQL. The application server to run it on is JBoss 7.1.
Extra notes:
1. A domain model shows the entity types relevant in the domain and how they relate to each other. Also, it shows the kind of responsibilities for those main classes. Do not try to implement it literally, the implementation has more classes and methods.
2. The priorities are shown above the name of the Use Case (see attachment).
Please note- I am not looking for a production ready blog site of any sort. This is just a coursework, so the implementation doesn't require to be entirely working.
Massalo V.
0% (0)Projects Completed
-
Freelancers worked with
-
Projects awarded
100%
Last project
12 May 2024
Netherlands
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies