Architecture Design Document
Overview and Stakeholder Identification: Week 1
|
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 |