So we look at the demand through your system not let's get started with the work history. 2
Let's begin by looking at the different types of users that the system supports along with what those 3
users can do. 4
There are groups of users. 5
One is the regular user and the other is a staff member a regular user is the one who simply uses a 6
system for bookmarking like the one we have seen in our Demel. 7
Staff members are part of our company and they have all the privileges of a regular user but they can 8
also have some additional capabilities. 9
So let's review the capabilities of both these types of users Just type of user is the regular user 10
. 11
And let's look at the capabilities to this class diagram. 12
So you are using the methods in the class diagram to describe the user's capabilities not that class 13
diagrams. 14
Simply describe the classes that make up a software on a class diagram is a human concept and gives 15
you don't know what you are Melas it stands for unified modeling language and it is used to visualize 16
the design office system. 17
So he you to have a regular user who can bookmark an item since trillionaire lost three types of items 18
to be a mugger. 19
We have a separate method for bookmarking each one of those items. 20
That is same web link same more we unsavable. 21
Additionally a user can also rate bookmark a user can also review a particular bookmark. 22
However the review will not be published on the Web site until it is approved by one of the editorial 23
staff members. 24
Next type of user is an email administrator who is a staff member email admin can do everything a regular 25
user does. 26
Hence you can see that email admin has all the methods that a user has. 27
Methods that are unique to email admin are emphasized in green. 28
You can see the most posted a view is also shown in green. 29
All the user class has that. 30
And that's because email admins posted a few works slightly differently. 31
Unlike user email admin does not need any approval for posting a review email admin also has a new method 32
called handle mail campaign to periodically rants email campaigns with large numbers of emails are sent 33
out to its users. 34
And sometimes these email campaigns might get stuck and it would be the responsibility of image admin 35
to fix the issue. 36
So this new method is related to handling of such problematic email campaigns. 37
Next type of user is a continuity teacher who is also the staff member unlet email admin a continuity 38
there can also do everything a regular user does and does not need any approval for posting a review 39
. 40
Additionally Khond continued results are responsible for approving and rejecting reviews posted by regular 41
users so use the separate methods for both these activities. 42
If a review is rejected then it will not show up on the website. 43
Continuity itor is not responsible for handling problematic email campaigns and hence you don't see 44
a method for that. 45
Undefined final type of user is a chief content editor who is also a staff member. 46
It Chief Content Editor can do everything a content editor does and in addition is also responsible 47
for managing the homepage content that is he or she decides what goes on the homepage. 48
Most recently book martyrdoms are the ones that go on the homepage hollower some of the book martyrdoms 49
may not be appropriate to be shown on the homepage unswitched Chief Content Editor acts as a moderator 50
and makes the final judgment on what can be pushed on to the homepage. 51
So basically a chief editor can do everything as a regular user does and also everything a content or 52
network can do. 53
And that's about it for now. 54
And it would help us to get started the next chapter. 55
New features will be introduced later as we learn some more topics. 56
Thank you.