CmpE 232 – Component-Based andPart 1: Component-Based Software DevelopmentPart 2: Stable Pattern-Based Software DevelopmentSINGLE VIEW OF CUSTOMERDomain: Customer Relationship ManagementDESCRIPTION OF A DOMAINDESIRED SYSTEMUSE CASESCmpE 232 – Component-Based and Reuse-Oriented SW EngineeringPractice Problem (7)___________________________________________________________This problem statement was developed byAnita Ranganath, Jayashree Rajagopalan, Pratibha Harkuni, Uma M Vishnubhatla, and Mohamed Fayad___________________________________________________________Part 1: Component-Based Software DevelopmentAnswer the following questions:(1) Document all of the Use Cases in Your Problem:(a) Identify two of the use cases(b) Identify Actors and their roles(c) Identify corresponding classes(d) Describe the Use Case Repeat the process for at least two of the use cases. Use the following Use Case Template to document your Use CasesAll the fields must be filled for each use case.1. Use Case Id.2. Use Case Title1. Actors & Corresponding Roles2. Classes5. Corresponding Attributes6. Corresponding Interfaces (services or operations)7. Use Case Description – Feel free to use pre- and post-conditions where appropriate.8. Alternatives(2) Create CRC cards for the existing classes.(CRC stands for Class Responsibility and Collaborations)(3) Prepare traditional models for this problem showing at least 10 relationships among the object classes in this problem, including associations, aggregations, and generalizations. Show multiplicities in your diagrams. You must name attributes and operations for each class. Use association and role names when needed. (4) Create Sequence diagrams. Sequence diagrams will be used to "realize" Use Cases. All Use cases should be described through sequence diagrams. The sequence diagramscan describe the same Use Cases that a flow of events was created for in the Use Case portion of the assignment.(5) Create Components diagrams for as many components in your project as you wish, and show all the interfaces, usage dependencies, ports, and connectors. Document the component diagrams. Address implementation issues that are related to these component diagrams if any.Please submit your answer electronically as MS word documents before the next lecture. – Feel free to submit all diagrams in Rational Rose or Visio formats Part 2: Stable Pattern-Based Software Development(1) Use Cases. Update #1. Document all use case templates with software stability in mind. Use the following template to document your use cases. 1. Use Case Id.2. Use Case Title3. Actors & Corresponding Roles4. Classes1. Corresponding Attributes2. Corresponding Interfaces3. Class Classification: EBTs, BOs, IOs 4. Use Case Description1. Alternatives(2) Create or/and update all the CRC cards for all the (EBTs, BOs, Roles) in your stability model of your team project (CRC stands for Class Responsibility and Collaborations). (3) Class diagram (Stability Model). Create a new Class diagram of your team problem based on the EBTs, BOs, and IOs – Describe your stability model. Class descriptions should include all attributes and methods for the class. All class relationships (associations, aggregations, dependencies, and specializations) should be included in the class diagram. association classes, interface classes, constraints, interfaces, tagged values and/or stereotypes, and notes must be included in the class diagram. (4) Sequence diagrams. Create Sequence diagrams with stability in mind that will be used to "realize" Use Cases. All Use cases should be described through sequence diagrams. The sequence diagrams can describe the same Use Cases that a flow of events was created for in the Use Case portion of the assignment. (5) Create Components (or Stable Patterns) diagrams based on Software Stability for as many components (Patterns) in your project as you wish, and show all the interfaces, usage dependencies, ports, and connectors. Document the component (stable pattern) diagrams. Address implementation issues that are related to these component diagrams if any. Please submit your answer electronically as MS word documents before the next lecture. – Feel free to submit all diagrams in Rational Rose or Visio formats ___________________________________________________________SINGLE VIEW OF CUSTOMERDomain: Customer Relationship ManagementAbstract: Customers are a company’s greatest single asset and having consistent, reliable information aboutthese customers is essential for business success. This problem statement explores ACME, a DSL Internet Service Company which is improving by building a comprehensive view of the customers and prospects so that the company can cross-reference and analyze them quickly and simply. The goal is to access all the customer data for a customer by using a unique ID. The ID is a single index key that retrieves all information about the customer, i.e. account summary, servicedetails, contracts, interactions with any departments, etc. Due to the highly competitive market, ACME has to provide the best customer service in order to increase its revenue, profit, market share, and market capitalization.Keywords: Customer Relationship Management and Customer ServicesDESCRIPTION OF A DOMAINACME, a DSL Internet Service Provider serves customers such as small business firms, companies, and individual household customers with their fast and reliable Internet Service. The company presently tracks all its inventory, sales, billing, customer service, and marketing information of their customers into separate databases. The customer data is scattered around and locked away in different departmental silos and hence results in having a partial view of customers in every department. If this data is linked together customer service can be more effective.A customer speaks with the pre-sales department that provides information on the services offered. If the customer decides to choose the service, he/she places an order with the sales department. The sales department records the customer’s information which includes the plan he/she wants to purchase, etc. The sales department notifies the inventory, billing, and customer service departments only with the required information that the respective departments require. The inventory back-office sends a DSL kit which includes manuals. Initial installation is provided. The billing department sends the customer the initial