ADD: Use Case, User Stories, and Development Methodology

 

As you continue to develop your ADD in your role as a software architect, use the CRM system described in the 

Assignment Background

 document to create the following additional sections in a 3- to 4-page Microsoft® Word document:

• Use Case section:
• Create a Use Case Diagram in Microsoft® Visio® for the “to-be” system. The use case diagram must show the major uses of the new system. 
• Include at least 7 use cases and at least 3 actors in your diagram.
• User Stories section:
• Create user stories for the use cases you identified above.
• Development Methodology section:
• Indicate how this system will be implemented through a methodology (Agile, Lean, Waterfall, etc.). 
• Explain how the development methodology impacts your architectural decisions.

Incorporate the three sections into a single Microsoft® Word document separate from the document created in Week 1. As this document is intended for a technical team, APA formatting is not required.

Title ABC/ 1 23 Version X

1

Assignment Background

CSS/422 Version 11

1

Assignment Background

Throughout this course, you will leverage concepts learned in class along with previous program material to create architectural artifacts for a Customer Relationship Management (CRM) system. The background for this assignment is as follows:

Resources: Materials presented throughout the course, course text, Microsoft® Visio®.

You, as a software architect, are assigned to modernize a CRM (Customer Relationship Management) system for your employer. The key driver behind this system is to attain and retain customers through its relationship with them.

The problems your company face are as follows:

· Your company produces products, but it is having trouble finding the target market for these products.

· Your company also has no way to market products to prospective customers.

· The customers your company has attracted are often unsatisfied and do not issue repeat business to the company.

On a positive note, your company has workable systems in existence:

· Sales – Order system is fine, but lead generation and marketing is non-existent

· Accounting

· Inventory

· Customer service call tracking

Unfortunately, none of these systems talk to each other. There is no synergy within the organization integrating the systems with one another.

In addition to solving these internal problems, the company wishes to address the following requirements:

· Simplify and ease integration with existing systems

· Expand the system into other areas

· Provide mobile access for customers and potential customers. The company will interact with customers in this way, and, more importantly, customers can interact with the company

· Mine its massive databases for analytical purposes

· Secure the system since the last data breach at the company tarnished its image and resulted in hundreds of thousands of stolen credit card numbers

By the end of the course, you will produce an architectural design document for this development project. The Architectural Design Document (ADD) includes the following sections:

· Overview (Week 1)

· Stakeholder Identification (Week 1)

· Use Cases (Week 2)

· User Stories (Week 2)

· Development Methodology (Week 2)

· Architectural Design Decisions (Week 3)

· Architectural Patterns ( Week 3)

· Control Flow Diagram (Week 3)

· Quality Attributes (Week 4)

· Views (Week 4)

· Technology (Week 5)

· Cloud Migration (Week 5)

Begin thinking about the situation and the end product. In-depth knowledge of a CRM is not required for this assignment. You may wish to preview the deliverables for the upcoming weeks to ensure you understand the artifacts your team will produce.

Copyright © XXXX by University of Phoenix. All rights reserved.

Copyright © 2018 by University of Phoenix. All rights reserved.

Overview and Stakeholder Identification: Week 1

Thomas F. Griffin

CSS/422

May 4, 2020

Annie O’Rourke

Running head: OVERVIEW AND STAKEHOLDER IDENTIFICATION: WEEK 1

2

OVERVIEW AND STAKEHOLDER IDENTIFICATION: WEEK 1

2

Overview and Stakeholder Identification: Week 1

After reading the user case information provided, I have come up with the plan to save the company and make it profitable again. After reviewing the data, we have several problems that we will need to address within the company for our products and who to sell to. Our whole system needs an overhaul to have new software interface with our current software. We need to have some marketing done so we can advertise our products and we need to figure out who we want to target for selling our product too. The other part we need to focus on is that retention of customers for return business and quality assurance.

After reviewing the data, I have found that there several issues in the current system that need to be addressed and fixed. All our systems need to interface with each other since this business needs to run and create revenue. We will need to have all the Sales, accounting, inventory and customer service center all working on the same system for functional needs. They will all need to talk in order to for the business to run more efficient and produce the numbers we need. We will interface all our current systems into a new CRM, and we will be able to do more any location at any time. The new CRM will also allow us to expand our business for even more things down the road. Since technology has gone from the traditional form of shopping, to the new form of online shopping, we are going to have to add a more versatile system for online shoppers and mobile app users. This is how we will target our customers, by using technology to gain their interest and buy our products.

Having the ability to run the system on a mobile platform will also require a lot more backbone and require more hardware for us to run it. All our systems will need to be upgraded and using the most up to date security features we can afford. Our data will include credit cards of customers, personal info and records, there cannot be another breach in the system and we loss our data again and spend millions on lawsuits and settlements. Our company got an unbelievably bad mark left from that breach, so we need to turn that around and make it right.

We will need to offer service, sales, costumer service, and support for all our products, and all these systems will be integrated to work together. All the server data will then be accessible from accounting and the warehouse where inventory will be kept. All these systems will need to be accessed by executives to maintain the numbers and show our stakeholders the gains. Our systems will need to be reliable and fast so there will be a need for cloud storage to make all this happen.

Stakeholder

Summary

Functional Use

Customer

The customer is the main stakeholder in this. They are the driving force behind the requirements of the software

Provides business and information system strategies, customer knowledge, Industry needs

User

The user is a stakeholder because they will be using the software the most and will have the most input for the build

Uses the software for business, operation of procedures

Project Manager

The project manager is a stakeholder because he/she is the main person over the project and has the most control over the success of the project

Main interface for the whole project, lead on all forms of the project

Analyst

The analyst is a stakeholder because they find the problems and fix them to stay within the budget

Tools, software writing methods

Developers

Technically without developers there is no software being made so they are a huge stakeholder

Languages used for programming, programming environments, design methods

Quality Assurance

Quality assurance is required to make sure that the software is working properly, so without them the software could fail

Software process, company standards, and methods