Reference no: EM133210323
Assignment - Big Data Management Challenge Case Study on Target Corporation PPT
The final project has both a theoretical and a practical component. Students will learn theoretical process models such as Unified Modeling Language (UML) and use them to design process innovations where you work to achieve efficiency, effectiveness and compliance objectives.
Objective - To demonstrate the ability to analyze work process challenges, propose a business process improvement initiative and make a business case for such an initiative.
Summary - The final project involves selecting a business process problem, describing the future "To-be" and current "As-is" process and presenting the business case for such to management. The project will be presented in MS PowerPoint; not an MS Word document. No MS Word document needs to be submitted.
Requirements gathering and analysis in support of business goals are skills and abilities basic to the core knowledge that systems analysts are expected to possess. Even if you never become a systems analyst, you may be involved in a project that demands process rework. Process modelling provides a way to graphically describe and analyze the business processes in an organization and to provide input driving the need for process improvement, process automation or software development. Having efficient and effective processes in place is a significant priority for any organization. It can determine the success or failure of the business. Without such focus, information technology ends up automating business inefficiencies and applications cannot interoperate with other processes and systems. Effective IT and business professionals are expected to be knowledgeable about business processes of an enterprise and process mapping tools.
"Architecting," however, only one part of the job. IT and business professionals also must be able to communicate effectively to senior-level management. This involves avoiding jargon, and conducting oneself in an executive-level manner that convincingly justifies the need for business, organizational and technology improvements.
Steps: Your work will follow six steps:
Step 1 - Identify the challenge you would like to address.
Describe your employer in terms of its history, core business and number of employees. Summarize financials if possible.
Describe a process challenge. What are the overall goals of the challenged process that you selected? What is the context and importance of the business process and system to the organization?
Note: If using your place of business is not possible, you may identify another organization of which you are familiar, or an organization you would like to have more familiarity with.
Step 2 - Describe the future, "To-be" process
Based on interviews and other requirement gathering techniques, create a high-level requirements document which captures the major functions of the "new and improved" process. The future "To-be" process should be driven by business requirements, strategic goals and IT objectives. Do not use an activity such as upgrading a server or application.
List functional and non-functional requirements.
Create a high-level UML-specific Activity Diagram with Swimlanes to visualize the new business process. You can use MS Word, PowerPoint, Visio or an open-source tool called Creately.
Describe the goal and expected benefits of the new process. See if you can quantify the business benefits (e.g., manhours saved, time saved).
Step 3 - Describe the current "As-is" process
Based on interviews and other requirements gathering techniques, create a high-level document which captures the major problems/issues/opportunities of the current process.
Describe the "business pain." See if you can quantify the pain (e.g., days required to complete a process, required staff).
Note: No UML Activity Diagram with Swimlanes needed for describing the "As-is."
Step 4 - Perform a gap analysis of the future and current states
Compare the differences between the two states. A template will be provided.
Step 5 - Recommend an action plan
List actions needed to move to the ideal "To-be" state. These actions range from introducing a new information system, to adding or reducing functionality of an existing information system, from changing or adding interfaces to shutting down the system. You will assign accountabilities and a timeline. A template of the gap analysis and the action plan will be provided.
Step 6 - Document your findings and recommendations into a final Microsoft PowerPoint presentation.
You are free to make assumptions, but be sure to state them.
Financials desirable, but not required.
Conclusion and lessons learned
References required.