Introduction
：
make clean
make
⾸readfile
.read –file Beattles_db.txt
⼊txt
⽤ajones cindy：
display playlist –from user ajones
display playlist –from user cindy
follow -u ajones -p help -f cindy
cindy help ⼊ ajones了。（ajoneshelp）
cindy⼀⾸
delete track 1041 –from playlist help –from user cindy
cindyajones
display playlist –from user cindy
display playlist –from user ajones
cindyhelp1041 Help！
ajones
follow -u ajones -p help -f stop
ajoneshelp⽌follow cindy。
cindy⼀⾸ 1043
delete track 1043 –from playlist help –from user cindy
cindy 1042了
ajones 1042
行follow cindyhelp
follow -u ajones -p help -f cindy
add track 1041 –to playlist help –from user cindy
cindy help 1041
ajoneshelp 1041
行 stop follow ajoneshelp
follow -u ajones -p help -f stop
add track 1042 –to playlist help –from user cindy
cindy help 1042
ajoneshelp 1042
⾥里，不 行了。
⼀
⾃⼰follow ⾃⼰
follow -u cindy -p help -f cindy
follow
follow -u ajones -p help -f cindy
follow -u cindy -p help -f ajones
follow⼀不
follow -u ajones -p none -f cindy
：
search user xxxx;
search playlist xxxx;
search album xxxx;
search song xxx;
search track xxx;
Requirement
Assignment #4 Patterns and Your Choice
This assignment has two parts. Part I is mandatory and if you complete it you get full
marks for the assignment. Part II is optional and the marks obtained from it will be
added to any lost marks on other assignments. That is, you only need to do Part I but
if you want some extra marks to add to your assignment term marks do Part II.
Refactoring, Design Patterns and Design Experience
Please be aware of the following relationship between Refactoring, Design Patterns
and Design Experience. The Gamma et al Design Patterns were presented as
Refactorings, that is, better ways to solve problems the were being solved in other
ways. (In assignment #3 you also refactored the containers by coming up with a
better way.) Once learned however, these refactorings become the way you might
solve the problem in the first place -it becomes part of your design experience. These
days the Gamma patterns, like the Observer Pattern, are used to solve the problem
in the first place. The refactorings have become part of the experience passed down
to others. So refactoring is how we discover better ways so solve problems and then
by documenting them as patterns they become part of our catalog of design
techniques much the way that algorithms and data structures passed on experience
to procedure-oriented designers.
Part I
Scope
For Part I we want you to add a new functional capability to the code developed so
far and base your solution on the Gamma Observer Pattern. You can base your
solution on any code base: your A2 or A3 solution or our solutions for A2 or A3. Your
solution for this assignment need NOT include the refactoring done in assignment #3
(That is, you can go back to your assignment A2 code if you want.)
Here is a the scenario:
A group of musicians have seen our playlist app and want to use it to manage their
setlists during rehearsals and performances. Setlists are lists of songs that are meant
to be performed together. They intend use our playlists as their setlists. (From here
on we will use the terms setlist and playlist interchangeably.)
The musicians often have a situation where one band member makes changes to a
setlist that must be reflected in the same setlist of other members. In this scenario
each musician (user) has their own copy of a setlist. So they want the application to
be modified so that band members can have their setlists following the changes
made to another member’s setlist. The new feature that they have requested is a
command and behaviour that lets band members have their setlists follow the
contents of another member’s setlist. They want you to implement the following new
command (or your version of the command based on your applications language).
follow -u userid -p playlist_name -f userid2
for example:
follow -u ajones -p brass_monkey_set1 -f cindy
In which case ajones’s brass_monkey_set1 setlist would be updated to reflect
the contents of a similiarly named setlist owned by cindy. Whenever
user cindy makes a change to her setlist ajones’s setlist will automagically update
to be the same. Changes would pertain to adding and removing tracks.
The command
follow -u ajones -p brass_monkey_set1 -f stop
Should cause ajones’s brass_monkey_set1 setlist to stop following that of
another user.
By the way there are several iPad apps (Forscore, Newzip for example) that lets
orchestras have lists of pdf scores and have the feature that a users can have their
score follow that of the orchestra conductor. These apps also seem to be using the
“follower” protocol for keeping scores in synch.
Functional and System Requirements for Part I
You must provide a testing script. that the TA’s can run that demostrates all of the
requirements. You will only get marks for those requirements tested in your script.
Your README.txt file must tell them how to run the script.
FR4.1.1) The application should support a command similar to:
follow -u userid -p playlist_name -f userid2
Which should cause userid’s playlist playlist_name to have exactly the same
contents as a similarly named playlist of userid2.
FR4.1.2) A command similar to
follow -u userid -playlist_name -f stop
Should cause userid’s playlist playl㱳⽡㹭ਠ㑴㈠㝴⥯⁰ⸯ㰾⽮㹯൴੨㑥㈠㡳⥥†‱㱥⽲㹥ഠ੭䡡⁴†⁹㩤㰠⽮㸠൴੨䑨†㱥⽦㹬䙴†⁴†⁴†‼
㱤⽴㹨൳ੴ⁴⁴⁹䄠‼⁹㱬⁴⽳㸮ഠ⁵‼ 㰮⽥㸠ൣ੯⁵†⁹†Ᵽ㰻⁰⽬㹡൹੬†‼ ‴⁔㱬⁷⽩㹴൨ੳ䍴⁵⁴††‼ⱡ㱳⽩㹴൨††⁰ ⭬†㱥⁵⽳㹥ഠ⭲⬠⹆⁒‱⁔㰠⁴⽨㹳൴⁴㱮⁰⽬㹡൹੬‾Ɱ†⸠㱭⁴⼠㹥൩ੴ䅨††⁰†⠠⸼⥳㱳⼠㹵൳⸠䥯⁷††⁰†⁴㱲‾⼍㸊െ
⁴⡩⸠⁔⥳⸬†㰼†⼯㸾ਊ†††㩯㱦⁴⽨㹥൲ਠ♵㬮‼ ‸㱢†⽴㹯ഠ੨♡㭯†‼⠹⸠†♱㭰䅬♡㬠†䅴㱨†⽬㹩൳ੴ⤠㱮†⽢㹥ഠ੬♥㭲†…♲㬮☠㭭⁵†べ†⁴⸠ ☾㬮䜱
䤠♦㭥㱲⽱㹵൯☠㭥䝥⁴䘠⁴䤠♥㭲㱥⽲㹯൭ਠ♡㭩♷㭔♥㬠⁷⡥♤㬠䥮䝴⁵䙯♮㭲††㱢 ⼾㸍ഊ੦ ††⥭㱥⽴㹩൯੮㱨⽤㸠ൢ⁴†⁴ ⸩†䥔㱤⽫㹥ഠੵ⁓⁏⡴⤯‾⁰††㰠⽥㹳ഠੴ⁴†‾†⁴㱲⽴㹴ੲ‾″†⁴††㰮⽡㹴഼‾†䥷⁰†㱩⽹㸼ൢੲ䴠⁰⁹㱪⁴⽳㸠൳੨‾†ⱰⱩ††㰠⽹㹬൩ੳ䍴‾††††⁴⸠㱯⼠㹡ഠ䍲‾ⴍ䈊⁴⁴䅨㱫‼⽢㹲ഠਯ ⁴⁏
⁉⁉⁵⁶㰠†⽡㹮ൡ੬㰠⁰⽲㹥൳ੳ㰠†⽩㹮ഠੴ♥㭯㱦⼼㹲 />
functional, system or domain requirements and then implement it. You are asked to
capture the scenario in eight requirements and then implement those requirements.
To get the marks you have to actually implement the requirements, just writing the
requirements will not count for any marks.
For any scenario below write 8 requirements in such a way that you think best
captures what is needed and then implement them. You will be judged on your
selection on requirements and how well they are chosen to reflect the scenario. You
should categorize your requirements as either Functional, System or Domain
requirements (use FR, SR, DR numbering scheme.)
You will get 2 marks for implementing those requirements but only for those
requirements that properly reflect what the scenario requires. So a possible 16 bonus
marks will be added to your assignment term total. You MUST provide a Part II
testing script. of commands that shows all of the features you have implemented are
working. You will only get marks for those requirements tested in the script.
4.2.1) Your scenario requirement.
4.2.2) Your scenario requirement.
4.2.3) Your scenario requirement.
4.2.4) Your scenario requirement.
4.2.5) Your scenario requirement.
4.2.6) Your scenario requirement