Assignment 4 Case Study: String Lights Coffeehouse

Background

Stevies String Lights Coffeehouse, popularly nicknamed The Strings, was opened 5 years ago by Stevie Ray Taylor. Mr. Taylor converted a former lighting factory in the downtown area of his town into a cozy 1400-square-foot restaurant serving various drinks and light food items. The restaurant has several cozy sitting areas with sofas, armchairs, bistro tables, and coffee tables. In addition, a small stage was built two years ago to accommodate musical performances by local artists. During the first year, The Strings hosted musical acts on Wednesday, Friday, and Saturday evenings. Now, however, the coffeehouse hosts musical acts every evening of the week with additional afternoon matinees on Saturdays and Sundays. Mr. Taylors assistant manager, Adele, updates their Facebook site with information on upcoming performances.

Musical genres range from the old 60s and 70s singer-songwriters to modern indie music, with bits of country and light jazz from time to time. Afternoon gigs are limited to 45 minutes, but evening gigs range between 60 and 120 minutes. Some weekends, The Strings will have several groups booked. Matinees are at 3:00pm and 4:30pm. The earliest evening performance time is 7:00pm. Performances end no later than 11:30pm; the coffeehouse closes at midnight.

Business has steadily grown and The Strings is a hot spot for customers of all ages. After 8:00pm, all customers must be over the age of 21.

Mr. Taylor implemented packaged software years ago to run the restaurant portion of his business but his assistant manager has been recording his music act bookings manually in a hardcopy calendar. He now wants to automate this process.

Your firm has been hired to analyze this system proposal. You have held numerous requirements gathering meetings with Mr. Taylor and Adele.

Your next step is to provide Mr. Taylor with UML diagrams depicting the system requirements he has requested. Here is the first draft of the Event Table your team has put together:

Event	Type of event	Use Case	Actor	Description
New musician expresses interest in booking a performance	external	Add new musician	Assistant manager (Adele)	A new musician or group contacts the coffeehouse Add info to Musician table
Musician calls with new contact info or changes to playlist/genre	external	Update musician info	Assistant manager	Musicians phone, address, etc. information has changed
Musicians agree to booking day and time	external	Add new booking	Assistant manager	The booking calendar is updated with a tentative gig. Status set as awaiting contract signature
Signed contract received	external	Confirm booking	Assistant manager	Booking now marked as confirmed
Day/date, time, or playlist info needs to change	external	Update existing booking	Assistant manager	Booking details are updated
Performance occurred and musicians receive payment as per contract	external	Pay upon completion of performance	Owner (Mr. Taylor)	Check is issued to performers. Record of payment sent to accounting system

Assignment 5

Here is the event table produced.

Event	Type of event	Use Case	Actor	Description
New musician expresses interest in booking a performance	external	Add new musician	Assistant manager (Adele)	A new musician or group contacts the coffeehouse Add info to Musician table
Musician calls with new contact info or changes to playlist/genre	external	Update musician info	Assistant manager	Musicians phone, address, etc. information has changed
Musicians agree to booking day and time	external	Add new booking	Assistant manager	The booking calendar is updated with a tentative gig. Status set as awaiting contract signature
Signed contract received	external	Confirm booking	Assistant manager	Booking now marked as confirmed
Day/date, time, or playlist info needs to change	external	Update existing booking	Assistant manager	Booking details are updated
Performance occurred and musicians receive payment as per contract	external	Pay upon completion of performance	Owner (Mr. Taylor)	Check is issued to performers. Record of payment sent to accounting system

Assignment 6 Case Study: String Lights Coffeehouse

Design-level System Sequence Diagrams

Assignment details

Refer back to assignments 4 and 5 which deal with the String Lights Coffeehouse system project.

Expand the analysis-level SSD from assignment 5 for the Add new musician use case to a three-layer design-level SSD. In other words, you will be breaking down the general System lifeline, which during analysis is rather a black box processing into its components user interface (view layer), internal logic (Controller), and data storage/retrieval functions (model). The purpose of this SSD is to clearly show ALL messages between system components.

Compare the diagrams on page 145 Figure 5-10 (analysis-level SSD) to page 421 figure 13-20 for an example of how to expand the SSD. Your completed diagram will have the same level of complexity as Figure 13-20.

Your data classes from assignment 4 will help you determine how many model lifelines you will need one for each data class.

Create customer account use case with view layer and data layer JRI view CustWindow controller CustomerHandlor Clerk aC:Customer ustomer homePh, email)creteNewCustomer name dataAccess CustomerDA (name, mobilePh, homoPh, omail)1 aC: create NewCustomer (name, mobilePh, homePh,email) showAddrWindow () t ] dataAccess AddressDA (name, mobilePh, homePh, email) writeDB (ac), AddressDA Viow AddrWindow Address enterAddressdd (type.no,atreet,city,statezip) enter Address aAddcreateAddress 1 (accNo.type.no.street,city.state. zip) (type,no,street.city.state.zip) enterAddress (type.no,street.city.state,zip) I