Create a State machine diagram, class diagram and a sequence diagram
A description of the System
Hjolaleidir.is - Better Biking routes
The group “Better biking routes” has got the idea of making the website: hjolaleidir.is for cyclists in the greater Reykjavik area. The group “Better biking routes” want to make the website accessible for a broad spectrum of users. They are catering to users who want information about good routes from a place to a destination and users who wish to more technical information, e.g., about road conditions, suitable trails for a family biking trip, trails for biking fast, etc. Additionally, cyclists can rate the biking routes and add comments for other cyclists about how the course was. The group is responsible for keeping the information updated daily. The users can register and pay a monthly fee and thereby sponsor the website. In return, they get a discount on outdoor activity stores and access to personal services through a “chat” on the website.
The group “Better biking routes” want to make the web hjolaleidir.is where at least this functionality will be possible:
Rules:
State machine diagrams
User state machine diagram
The system should be partly usable by non-logged-in users, and the system should provide additional functionality to signed-in users even without a paying subscription. But all of the functionality is provided to paying members.
Create a state machine diagram that shows the lifecycle of a user in the system. What are the possible states, and how does the user transition between them? Note that we are not asking to see all operations the user can perform; only the states that are applicable for the customers.
Comment state machine diagram
Signed-in users can comment on a biking trail (see requirement 6). Hjolaleidir.is wants to keep close moderation on these comments, to maintain a level of decency and excellence. New comments need to be accepted so that they are shown to users viewing the biking trail. The way the acceptance happens is as follows; paying members' comments are accepted right away and made available to other guests for viewing, while non-paying members' comments need to be reviewed by a moderator before being published (remain hidden to guests). The moderator reviews comments and either rejects or accepts them. Rejected comments get deleted from the system and accepted comments will be shown on the biking trail page.
Signed in users can also report comments, and thus flagging them to be moderated again. Until they get moderated, they remain hidden to guests on the biking trail page.
Create a state machine diagram that shows the lifecycle of comments in the system. What are the possible states, and how does it transition between them?
Class diagram
Create a class diagram for the system based on the information written in the list of requirements. You don't need to look at the extra material on the company or system from previous assignment descriptions, the information provided here should suffice. It's essential to show the correct usage of inheritance relationships (if applicable in your class diagram). Also, the proper usage of the multipliers, and finally, we want to see attributes and methods that you can read from the list of requirements.
Give a short description of what method you used to identify the classes that ended up in the class diagram, and how you used it.
Finally, list what classes these are, and what their purpose is, for example:
Sequence diagram
Create a sequence diagram detailing how the commenting mechanism described above (under the Comment state machine diagram part) should work. Consider the actors participating and the sequence of operations.
(1)
State Machine Diagram for users.
There are three states in which a user can be Not-logged-in, logged-in, and paid user.
Non-login user tries to login into the website, if successful then logs in.
Logged in user want to subscribe if successfully subscribed then the user becomes paid user.
(2) State machine diagram for comments:
There are three comments states: Non- reviewed,Reviewed and deleted comments.
There is an entity moderator that reviews and comment and flags its acceptable and unacceptable.
If unacceptable then the comment is deleted.
(3) The UML class diagram has 7 classes, each being unique and having the basic CRUD methods and attributes with proper primary and foreign keys set.
The cardinalities between each class is depicted in the image.
(4) Sequence diagram for comment section.
Threre are 4 lifeline objects Subscripted and LoggedIn user, moderator and database.
Subscripted user can directly save to the database.
LoggedIn user can send the comment to the moderator where he/she executes the check frame, if successful saves to database and if not then destroys the comment.
Loggedin user can flag a comment to be reviewed by the moderator.
Get Answers For Free
Most questions answered within 1 hours.