Hi there. 2
This is day two. 3
And welcome back. 4
It's not time to implement our project and have some fun. 5
We've been promoting our Casterley that will implement a basic version of the. 6
The project will evolve as a course progresses but the framework and all the core features will be implemented 7
in this version. 8
So we would have been promoting a major part of the project and this version specifically here is what 9
we will do. 10
Vivek implement most of the features we have learned so far. 11
We will use proper object oriented design and coding conventions will implement the project using Eclipse 12
and will make use of all the commonly used features including the old ones like automatic source code 13
generation automatic refactoring and so on. 14
We will also use a popular and B.C.E. design pattern which we will discuss next and we will also use 15
another design pattern called Single and pattern. 16
Finally for some parts of the implementation we will use a popular software development process. 17
It and double up ment which is referred to as BTD in shock. 18
DDT is very widely used Technik desk is written before we start writing that legal logic. 19
So that would be interesting and we will discuss it and its benefits. 20
When we are implementing it so its going to be some real good stuff that we are going to implement. 21
And here is a project specification. 22
The system will involve five users and 15 bookmarks the 15 bookmarks would include five doublings five 23
books and five movies. 24
We would just build the necessary framework to load this data. 25
Next we will implement the real features. 26
I'm already familiar with all of them. 27
The first one would be the bookmarking process itself. 28
Each user can bookmark at most five items which can be any of the bookmark types. 29
So 5 is a max limit. 30
The marking decision itself will be done randomly. 31
So we'll be using randomisation function from the math class and for this version duplicate book Mazzariello 32
we will have to duplicate later. 33
Next week it is marking bookmarks as kid friendly with this feature an editor or chief editor can approve 34
or reject a bookmark as kid friendly or they may not even take any action to. 35
There is a bookmark will be left in an unknown state so only an editor or chief editor is authorized 36
to make approval or rejection decisions on it cannot be done by regular users. 37
We already know that. 38
Again for this first version this is done by a randomisation. 39
Later we can prompt the user to give his or her decision. 40
The final feature is sharing of good friendly bookmarks with partner websites. 41
So it's going to be only kid friendly bookmarks that you can share other regular bookmarks with partnership's 42
sites. 43
Again this can be done only by staff members such as editors and chief editors. 44
Moreover the constraint is that only books and ramblings can be shared so movies cannot be shared. 45
Also like other features for another shared decision is done by randomisation. 46
So basically for all three features that are shown here in green boxes a user decision is based on randomization 47
. 48
So that's the specification in the next lesson. 49
Let's look at the architecture that we are going to follow. 50
They'll be using the popular and Visio design pattern and so we will briefly discuss it and after that 51
we'll start our implementation