Year 2 Addendum

I was to roleplay as a private company business analyst engaged to prepare a business case in response to the request for proposal (RFP) to key stakeholders of my case. A business case template provided contains the following sections for creating a professional business case submission:

1. Background, a quick description of the project's context hinting its origins and purposes.

2. Assumptions and constraints, researched criteria for maximizing the project's value.

3. Executive summary, a formal proposal summarizing the contents of the business case.

4. Project stakeholder, names of individuals who are either the case's project Sponsor, Champion, or none of the former.

   1. Project Sponsors are the owners of the project, providing and managing resources, and guiding the project group.

   2. Project Champions are initiators of the project, allocating time to them and providing resources.

5. Business needs, goals the project needs to satisfy after completion.

6. Business requirements, tasks that need to be done for completing the project.

7. Business values, tangible and intangible results stakeholders would earn after project initiation.

8. Appendices, diagrams or charts referenced by business case texts which further elaborate on given statements.

9. References, a mandatory section for all formal research papers containing sources to research materials. Even sources owned by the author need to be stated here in the latest APA format.

Following the hypothetical acceptance of my business case, preliminary investigation with intensive fact finding has begun, with the aim of better understanding business case requirements through separative categorization and narrative building.

Not to bloat this paragraph with text, here is a very brief description of each use case section:

1. Functional and non-functional requirements, which can be translated to important and not-so-important requirements respectively. Contains tasks and deeds the context-specific business case need done successfully to meet requirements.

2. User stories, imaginary dialogues from stakeholders that illustrate the business case's functions and individual values.

3. Use case model, a simple diagram illustrating stakeholders' actions they can perform with the business case.

4. Use case documentation, use case success-failure conditions and process normal, alternate, and exception flows.

5. Activity diagram, a logic blueprint documenting all stakeholders' actions with the use case.