Reference no: EM131136264

PROJECT DESCRIPTIONS

The final project has both a theoretical and a practical component. Students will learn theoretical process models such as Unified Modeling Language (UML) and Business Process Modeling (BPM) and use them to design process innovations where you work to achieve efficiency, effectiveness and compliance objectives.

Objective: To demonstrate the ability to analyze business and technology issues, 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 an MS PowerPoint presentation in a prescribed format. No MS Word document.

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 at work that demands a BPM. Process modelling provides a way to graphically describe and analyze the business processes in an organization and to provide input to process improvement, process automation or software development processes. Having a BPM policy and practice in place is (or should be) a significant priority for any organization. It can determine the success or failure of the business. Without a BPM, information technology ends up automating business inefficiencies and applications cannot interoperate with other processes, applications 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 change.

Steps: Your work will follow seven 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. Include financials if possible.

· What are the overall goals of the challenged process that you selected?

· What is the context and importance of the business process and system?

· What is the scope of the project?

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 "To-be" process should be driven by business requirements, strategic goals and IT objectives. Do not use an activity such as upgrading a server.

· List functional and non-functional requirements.

· Describe hardware and software to be used.

· Create a high-level UML-specific Activity Diagram with Swimlanes to visualize the new business process. You will be provided with drawning options.

· 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 requirements 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).

· Describe hardware and software used.

Note: No UML Activity Diagram with Swimlanes needed.

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 will be provided.

Step 6: Document your findings and recommendations into a final Microsoft PowerPoint management presentation.

· You are free to make assumptions, but be sure to state them.
· Financials desirable, but not required.
· Conclusion and lessons learned
· References required.
· No MS Word document needed. Expand your points in the Notes section of PowerPoint.

There are two deliverables for the final project:

Project Identification - due end of Week 3

Using Step 1 as a guide, describe your selection. No need for APA formatting or turning the work into Turnitin.com

Final Research Paper - due end of Week 12

The final business process model (BPM) will include:

· Executive Summary
· Overview of the organization (aka current state of the business, not the process)

· Problem statement (goals of the process, context and importance)

· Project scope

· Analysis of the desired future "To-be" process with Activity Diagram/Swimlanes (include process and product analysis. Copy and paste the diagram into PowerPoint. Do not submit drawings separately)

· Analysis of the current "As is" situation (include process and product analysis.)
· A gap analysis
· An action plan
· Conclusion and lessons learned
· References

Your PowerPoint presentation should mirror the structure described above. The presentation will include notes (aka speakers notes; taking notes) and references.