Question:

Now that you have created use-case models for your system, you will continue your system design by completing your class diagram and applying behavioral diagrams.

1. Extend your class diagram by including associations, indicating the object role and multiplicity on each end of your associations. Add any new classes, attributes, or operations that you may not have considered in your Week 3 project. Specify the data type and visibility of each attribute.

For your reference please have my following week 3 project

Task 1:

Use-Case Model Diagrams

1. The sales process management module activity diagram:

The sales process management module activity diagram shows the activities that need to be performed in order to streamline the sales process and to track and manage customer data more effectively.

2. The data management module activity diagram:

The data management module activity diagram shows the activities that need to be performed in order to track and manage customer data more effectively.

3. The user interface activity diagram:

The user interface activity diagram shows the activities that need to be performed in order to allow users to interact with the system and to access the features that they need (Enyinda, Opute, Fadahunsi & Mbah, 2020).

As depicted in last week project, the nonfunctional requirements categories that were identified for the project were as follows:

• Functionality
• Usability
• Reliability
• Performance
• Security
• Supportability
• Deplorability

The declarative requirements that were identified for each of these categories were as follows:

• Functionality: The system shall be able to streamline the sales process for the sales department. The system shall be able to streamline the sales process for the sales department.
• Usability: The system shall be easy to use for the sales department and the project manager. Project managers may keep all the project information on a single platform, make it easily available to any team member, and even carry out their job directly from the program (Oliveira & Rabechini Jr, 2019).
• Reliability: The system shall be reliable and provide accurate information to the users. The likelihood and proportion of the program working flawlessly for a predetermined number of uses or period of time is known as reliability.
• Performance: The system shall be able to perform all the tasks that are required of it in a timely manner. All Work shall be finished on schedule and in compliance with the project's needs and specifications.
• Security: The system shall be secure and protect the data that is entered into it. Security safeguards protect your program from sabotage and espionage. Even standalone systems need these characteristics since you don't want anyone to have access to your private information (Holder & Wang, 2021)
• Supportability: The system shall be supportable and have documentation that is up to date. The new system will give sales representatives more thorough, correct, and current product information. They will have quicker access to the product owner and quicker access to information about potential users.
• Deplorability: The system shall be deployable on the company's existing systems.

Subjects Of Use-Case Models

The subjects of the use-case models that will be specified in Week 3 are as follows:

• The sales process management module
• The data management module
• The user interface
• These subjects were chosen because they are the key components of the system that will help the company to manage its sales process and data more effectively.
• Sales Process Management Module: The sales process management module will help the company to streamline its sales process and to track and manage customer data more effectively.
• Data Management Module: The data management module will help the company to track and manage customer data more effectively.
• User Interface: The user interface will help the users to interact with the system and to access the features that they need (Ding, 2016).

Task 2:

Use-Case Descriptions

1. Use case title: Manage Customer Data
2. Brief description:

The Manage Customer Data use case allows the sales department to track and manage customer data more effectively.

1. The flow of events for use case is as follows:

The sales department will input customer data into the system.

The system will then track and manage the customer data.

The sales department will then be able to access the customer data when needed.

1. Special requirements:

The system will need to be able to interface with the company's existing sales and customer management systems.

1. Precondition:

The sales department will input customer data into the system.

1. Postconditions:

The system will track and manage the customer data.

1. Extensions:

The system will allow the sales department to access the customer data when needed.

1. Relationships:

The Manage Customer Data use case is related to the sales process management module.

Task 3:

An Object-Oriented (OO) Class Diagram

According to Enyinda, Opute, Fadahunsi & Mbah, (2020), the OO class diagram will include the following:

-The sales process management module class

-The data management module class

-The user interface class

The sales process management module class will include the following attributes:

-The ability to streamline the sales process

-The ability to track and manage customer data

The data management module class will include the following attributes:

-The ability to track and manage customer data

The user interface class will include the following attributes:

-The ability to interact with the system

-The ability to access the features that they need

The following elements will be included in the OO class diagram:

-The sales process management module class

- The class for the data management module

-The class for the user interface

The following characteristics are going to be included in the class of the sales process management module:

-The capacity to simplify and standardize the sales procedure

-The capacity to monitor and administer information pertaining to customers

The following characteristics are going to be included in the data management module class

-The capacity to monitor and administer information pertaining to customers

The following characteristics are going to be included in the user interface class:

-The capacity for participation in and interaction with the system

-The capacity to get access to the capabilities that they need.

Reference:

Ding, R. (2016). Control the Project Scope. In Key Project Management Based on Effective Project Thinking (pp. 167-187). Springer, Berlin, Heidelberg.

Enyinda, C. I., Opute, A. P., Fadahunsi, A., & Mbah, C. H. (2020). Marketing-sales-service interface and social media marketing influence on B2B sales process. Journal of Business & Industrial Marketing.

Holder, E., & Wang, N. (2021). Explainable artificial intelligence (XAI) interactively working with humans as a junior cyber analyst. Human-Intelligent Systems Integration, 3(2), 139-153.

Oliveira, G. F., & Rabechini Jr, R. (2019). Stakeholder management influence on trust in a project: A quantitative study. International journal of project management, 37(1), 131-144.