Assignment 4: Term Paper
Due Week 10 and worth 200 points
You were talking to members of your favorite local band after a recent show. The topic of software came up, and the leader said she has a love-hate relationship with it. She loves the recording software theyuse, andis okay with QuickBooks for the band’s financial records. But, she does not like the available options to track bookings and create set lists that draw from their entire repertoire.
In addition to their regular weekly gigs, the band performs for many school assemblies and community events. They have to pick music that’s appropriate for the audience and the theme without being repetitive. They are constantly adding new songs to theircatalog, andputting others on hiatus. The band likes to take requests, so they frequently update the set list after a gig. The band does not want to bother entering chords or lyrics because they don’t use computers or phones on stage.
You offer to put together a system design to address the band’s needs. It’s okay to collect ideas by looking at off-the-shelf solutions, but the design must be your own for this assignment. Include the following in your design:

A list and short explanation of each function to manage:
the band’s song catalog,
bookings,
set lists, and
any other category you believe is important for this application.
A logical data design that supports all of these functions. Use either an entity-relationship or a UML class diagram, which should be in third normal form. Indicate all primary keys, relationships, and cardinalities.
Recommend a system architecture that identifies the hardware and software components and how they interact. Include a short (not more than 500 words) description and rationale. Illustrate using your choice of a static functional decomposition or object-oriented diagram.
Identify security concerns and other nonfunctional requirements for this system.
Propose at least three distinct and measurable criteria to evaluate the quality of the finished software.

Your document must follow these formatting requirements:

Follow the Strayer Writing Standards (SWS). The format is different than other Strayer University courses. Please take a moment to review the SWS documentation for details.
Properly cite all sources.
Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date.
All charts and diagrams must be the student’s original work. They must be pasted into the document as neat, legible images.
The cover page and the reference page do not count towards the assignment’s length.

The specific Course Learning Outcomes associated with this assignment are:

Determine high-level logical system characteristics for an information technology-based solution.

Grading for this assignment will be based on answer quality, logic / organization of the paper, and language and writing skills, using the following rubric.

Please use the following headings in the following order in your paper for Assignment 4.You MUST use the headings below. Failure to use the headings below is not an option. Know that this assignment will take ample time to complete successfully. I therefore encourage you to begin your work on Assignment 4 immediately. Do not delay. Also recall the this assignment is worth 200 Points. Items in parentheses can be deleted from your headings in some cases, or simply select the appropriate item and include as part of your heading when given a list of options.
Good luck! You can do this — now make it happen!
Also: See the other Assignment 4 emails/announcements to help you complete this 200-point assignment to earn the maximum number of pointspossible. : )
Best,Professor Snyder.
Assignment 4Headings:
Explanation of How to Manage the Song Catalog Function
Explanation of How to Manage the Bookings Function
Explanation of How to Manage the Set Lists Function
Explanation of How to Manage at least one other Function
Logical Data Design Diagram Supporting all Functions (ERD or UML Diagram [select one]. Must indicate Keys, Relationships, Cardinalities)
Discussion of Diagram:

Diagram Type Selected and Justification
Third Normal Form
Keys
Relationships
Cardinalities

Recommended System Architecture: Hardware and Software and How They Interact
Justification of Recommended System Architecture
System Architecture Diagram (Static Functional Decomposition or Object-Oriented [select one])
Security Concerns and Non-Functional Requirements
Distinct and Measurable Criteria for Quality of Finished Software (at least 3)