This week you must begin creating a Software Requirements Specification (SRS) for an application that will be assigned by your facilitator. Your SRS must include a use-case model with an appropriate use-case diagram and individual use-case specifications for each use case. Additionally, your SRS must contain two example user interface mock-up screens. Submit the SRS as a MS Word document to this course's drop box.
The use-case model in this assignment will be assessed using the following UseCaseModelRubrics.doc expectations rubric. An example SRS template can be found here: Example SRS Template.doc and an example use-case specification template found here UC_Details_Template.doc. 

For your Bridal Registry SRS/Use cases, the Rubrics found in the Weekly Activities
section of the Week by Week Notes for Week 1 provide an overview of all the 
requirements you will need to meet when developing your use-case model.
Don't go crazy with use cases. For example, 25 is way too many.

Introduction
The Bridal Registry (BR) case study examines the design and implementation of a small distributed enterprise application that provides a single in-store bridal registry to customers. Within an education setting, this case study provides a vehicle for introducing various model-based object-oriented software engineering concepts. The remainder of this document specifies a set of requirements as requested by the client stakeholder.

1 Client Request
Target which is a medium-scale department store requested to develop a single user in store bridal registry (BD) application for the convenience of their customers. The BD application will allow the bride and groom to be to create, update, and delete their bridal registry. Also the application will print a copy of their selected items for the convenience of their guests (customers). The key objective of the bridal registry application will be display a basic CRUD functionality within an object-oriented software application. 

Target is a medium-scale department store that would like to have you develop an in-store bridal registry application. 

The bridal registry application should allow a betrothed couple to create** a bridal registry and populate it with products that they'd like to receive as gifts.( Subsequently, wedding guests (i.e. Target customers), while in the store, can obtain a printed** copy of the registry to purchase products from Target. When guest customer checks out at the cash register, the corresponding bridal registry must be updated**. Consequently, the cashier must also be able to find** the appropriate bridal registry. As the guest may know either the bride or the groom, the system must be able to find the registry given either of these names, possibly in combination with other information about the betrothed couple (e.g. wedding date, address, etc.).

It's also possible that the betrothed couple may require multiple gifts of the same type (e.g. two doormats). Hence, the application must be able to handle multiple gift requests. Additionally, the betrothed couple may not know the exact name of UPC code of the products they desire as gifts. Thus, the application should also provide assistance in finding these products. The betrothed couple may update the gift list at any time after it is created, including removing gifts/delete** from the list. 

Address and telephone information must be kept for the betrothed couple in order to contact them as necessary.