Identify e-commerce components and global considerations for developing a web presence.
Discuss obstacles to using global information systems.
Apply tasks involved in the requirements gathering phase of the systems development life-cycle.
Apply practices of the Agile methodology through the perspective of the requirements gathering phase.
Step 1: Think about your fictional business. Read https://www.webdesignerdepot.com/2018/10/7-ways-to-design-for-a-global-audience/ on how to design a website for a global website. Find a website of an organization like the one that youve proposed (or similar if your organization type is one of a kind), and identify features of their website that make them global. Include screenshots and a URL of the website that contains the global features.
Step 2: Answer the following questions
What are some challenges that you foresee your organization facing in a global environment as it relates to information systems? (200-400 words)
How do you plan to overcome one of the challenges that you have identified? (200-400 words)
Step 3: Think about your fictional business. Think of a hypothetical situation for which there is a need for an information system for your organization (payroll, human resources, sales, etc.). Briefly describe in 200-400 words this hypothetical situation and then describe the needs of the information system using the four Ws-why, who, when, and what (why do I need this, who needs this, when is this needed, and what is it needed for).
Step 4: Create 2 user stories for a fictional business need.
Read the item below on “User Stories” to familiarize yourself with this concept:
User Stories Explained (Visual Paradigm, 2020)
“In software development and product management, a user story is an informal, natural language description of one or more features of a software system. A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective. A user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement.
User stories are written in everyday language and describe a specific goal (what) from the perspective of an individual (who) along with the reason (why) he/she wants it.
In software development, the goal is often a new product feature, the individual is some type of end-user and the reason is the benefit that the user sees in the targeted product feature.
User Story Examples:
As a [customer], I want [shopping cart feature] so that [I can easily purchase items online].
As an [manager], I want to [generate a report] so that [I can understand which departments need more resources].
As a [customer], I want to [receive an SMS when the item is arrived] so that [I can go pick it up right away]
In the examples above:
Role represents the person, system, subsystem or any entity else who will interact with the system to be implemented to achieve a goal. He or she will gain values by interacting with the system.
Action represents a user’s expectation that can be accomplished through interacting with the system.
Benefits represents the value behind the interaction with the system.”
What your submission should include:
1) Responses to Steps 1-4.
2) The name of who contributed at the top of your submission.
3) Completion of the Activity 5 – Reflection Survey.