CUMULATIVE PROJECT

 

 

 

Part 1
Determine a business or organization in need of information systems. This can be a business startup or changes in an existing business. If an existing business belonging to you (now or in the future), treat it as if you will be upgrading technology beyond a single computer, software integration, or system..
In this lab:
Project Definition
1. Define your IS project and determine what information systems and personnel will be necessary to meet needs and requirements.
2. Is this a startup or a business converting to or making significant changes to its business model and systems?
Data
3. What types of data do you think you will be working with?

Organizational Changes

4. How big a staff do you think will be needed and in what capacity? Will new people need to be hired and trained? Will existing staff need training?
Initial Concerns
5. What initial security, ethical, or legal concerns might you have?

Part 2Project Plan: Moore’s Law and Software/Hardware

Hardware/Software Requirements
1. After this week’s readings on hardware and software, determine the kinds of hardware you think you’ll need to get meet project requirements.
2. Is this a single-user or multi-user system? Explain.
3. Research, if necessary, to help justify your choices and arrive at an estimate of what these items may cost. Again, you’ll get the chance to revise this information as you learn more and perhaps adjust your initial ideas but try to keep the totals realistic based on your current understanding.
Competition
4. Also, explore Moore’s law in the Week 3 videos. Moore’s Law essentially proposes that technological changes will occur on average every 2 years. These changes can create advantages for companies that have the means to implement them quickly, thus creating greater competition. Investigate the probability that your business will have significant competition in the next 18 months.
5. Does competition exist now and how will you make your product or service stand out?

Part 3 Project Plan: Data

Data Types
1. Create at least 3 tables to illustrate the kinds of data your company will deal with. They can be related or separate types, internal or external. Consider your headings and which might work as primary keys – remember primary keys must be unique. Highlight or bold the primary key for each table. See Chapter 5, Section 1b for examples.
Data Flow
2. Create a diagram illustrating data flow (see Chapter 5 figures for examples). It doesn’t need to be complex at this point, just a breakdown of the system or systems you’ll be using to handle data. Where does external data enter the system? Where does it go and who will have access? Is internal data like employee information directed to one department or person? Why? Where will data be stored – on a local server, the cloud, or something else?
PII
3. Lastly, address how you will handle PII (Personally Identifiable information). In what ways can you ensure only those who need access to such information can retrieve and view it?
Address each of these areas using the headings provided and submit as a Word document. with the required tables and diagrams embedded. Be sure to run spellcheck and keep quotes to a minimum with credit given to sources. Include any references used.
Include project summary each week at the top or add to the previous week as the project is cumulative and the entire document will be submitted in week 8.

Part 4 Project Plan: Cloud and Networking Needs

Infrastructure
1. What kind of infrastructure will be necessary to support your business? Consider the options discussed in Chapter 6 reading and videos and determine what kind of network and storage will be necessary to support the business.
Integration
2. Will you start small and expand or get everything in place from the beginning? What are the cost and other benefits of each?
Legal concerns or security risks
3. Are there any risks or legal issues that preclude a specific option?
Cloud integration
4. What about cloud services? Can SaaS, DaaS, or other cloud-based tools be more economical and convenient than traditional ones? Do you foresee a need for occasional upscaling of services in times of increased usage like sales, inventory cycles, or holidays? If you decide against cloud services or storage, discuss why you made that decision.
Revisit your data flow diagram from last week. Do your choices now affect your original design? If so revise to include the new decisions.

Part 5 Project Plan: eCommerce and/or mCommerce

eCommerce Model
1. What types of commerce will fit with your business (B2B, B2C, C2C or a blend)? How? Even if it isn’t an immediate concern, proceed as if it will be in the future. See sections 7-1 for details on each.
Feasibility Plan
2. Create a feasibility plan for eCommerce, mobile, and/or traditional commerce. How will they interact with one another and how will data be handled? Will everything go to a central location to help track availability and inventory? Sections 7-4 and 7-5 will be of help here.
Web or Mobile Presence
3. Discuss how you’ll go about creating a web and/or mobile presence.
4. Sketch out or using a photo editing program to envision what your website or app might look like.

Part 6 Project Plan: Using data mining, business intelligence, AI, Expert systems or knowledge management

Data Collection
1. Discuss preliminary ideas on how you can make use of the data you collect to continue to grow your business (chapter 9).
2. Will you use live data or datamining or some combination? Explain (chapter 9).
3. Are there any ethical or legal concerns with its use? Explain (chapter 9).
Knowledge Management
4. What about knowledge management (Ch. 10, section 1)? Expert systems or AI (Ch 10, section 2)? Do they fit in your business plan? Detail which and how. If you don’t think they will fit, discuss why not.

Part 7 Project Plan: Agile, Waterfall, DevOps, SWOT

SWOT Analysis
1. Perform a SWOT analysis on your business project. Define strengths, weaknesses, opportunities and threats. Use table 11-1 as a guide.

Strategic Plan

2. Expand on your analysis with a strategic plan to address each area. How do you protect or ensure strengths and opportunities while mitigating risks and threats? The strategic planning pyramid in figure 11-2 will be helpful. Each level is described below the pyramid.

DevOps

3. After reading more about DevOps, consider where it fits with your organization or department. What principles and practices would you consider useful to adopt? Why? (MindTap assignment as well as section 12-5).

Models and Frameworks

4. Also consider the Agile and Waterfall models as well as Scrum. Again, which would you adopt? Will more than one work for different aspects of the business? Refer to figures 12-1 and 12-17, tables 12-2 and 12-10.

5. Create a diagram or flowchart detailing how the model or framework you chose would work within your structure. Figures and tables mentioned above can provide example models.

Part 8 Project Plan: Risks and Threats

Risk Assessment
1. In the last portion of our project, perform a risk assessment based on learning and experience. What risks can you identify? What can be done to address them? Are any of them considered acceptable risks? Why and what will it cost if the risk becomes reality? (Chapter 13, section 2).
2. Discuss or expand on threats and plans to address them. Are your plans for security, both locally and online, sufficient? If not, what else can you do to protect your systems as well as your data? (Chapter 13)
Ethics
3. Will you require training in ethics for employees? How will you respond to or enforce breaches due to employee error or deliberate misbehavior? (Chapter 14).

This question has been answered.

Get Answer