$($Database Design$)$ Design logical relational schema: Assume your company is developing a generic digital camera online purchasing system that can be sold to different camera stores. An initial analysis phase of the project has resulted in the following informal description of relevant data for the system. A store will be selling a variety of digital cameras and lenses. The digital cameras can have a combination of the following features: $1.$ An ability to replace lenses. $2.$ Cameras with an electronic viewfinder. $3.$ Cameras with an optical viewfinder. $4.$ Cameras with an optical rangefinder. Note that any subset of the feature set $\{1,2,3,4\}$ is a possible combination $($including the empty set$)$ except the combination will not have more than one of the features $3$ or $4.$ For example, feature sets $\{1,4\},\{2,3\}$ or $\{1,2,3\}$ are possible while feature set $\{1,3,4\}$ is not possible. Relevant properties of all cameras are: the manufacturer, model number, date of product release, sensor size, pixel number, retail price and the number currently in stock. Properties of cameras without an ability to replace lenses that are relevant include a focal length range and an aperture range. Cameras with an ability to replace lenses are related to at least two or more lenses. Properties of a lens that are relevant include the manufacturer, model number, focal length range, aperture range, retail price and the number currently in stock. A prime lens is any lens with only one possible value for a focal length range, i$.$e$.,$ will have the low end of the range equal to the high end of the range. Online customers are either domestic customers or foreign customers. Properties of customers that are relevant include a unique customer number, a customer name, an email address and a shipping address. Each customer may have any number of purchase orders. Each purchase order is for only one unit of any product at a time, either a camera or a lens, and will also have a selling price. Design logical relational schema