Business Analysis Project: Analyzing Business Requirements and Scope

Verified

Added on  2022/11/14

|4
|599
|198
Report
AI Summary
This report provides a comprehensive analysis of business requirements and project scope. It examines various aspects, including functional, non-functional, and stakeholder requirements. The report explores the use of different techniques such as document analysis, scope models, context diagrams, and process flows to define and manage the project scope effectively. It also discusses the application of use case diagrams, ecosystem maps, and feature trees for refining the solution scope. The report includes examples of business, stakeholder, functional, non-functional, and transition requirements. It also provides relevant references for further reading. This report aims to provide valuable insights into the techniques used in the business analysis and project management to ensure the effective delivery of the project.
Document Page
Running head: BUSINESS ANALYSIS PROJECT
Business Analysis project
Name of the student
Name of the university
Author note
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
1BUSINESS ANALYSIS PROJECT
Scoping techniques for improving solution scope
The bowling effect has become quite common in research where often the
solution scope is vague and not properly defined. Vague requirement specification
results in inappropriate representation of the consumer needs (Carstens, Richardson
and Smith, 2016). Therefore, it is essential to develop a scope statement that is clear
and concise. It should be able to explain the purpose of the business and the
priorities of the product. It should also support the objective of the business and
focused on the solution to the developed.
Document analysis is the first technique to identify the solution scope in a
research as it is essential to analyse all the available information to gather key
requirement. Scope model consist of the different factors which is necessary
successful definition of scope. Context diagram or level 0 data flow diagram can be
expanded into multiple data flow diagrams (Hazır, 2015). A functional decomposition
can also be used to breakdown the topic into smaller buckets. A process flow is
used to develop a swim lane diagram which depicts the processes in rows along with
resource allocation of each process (Ganushchak-Yefimenko, Shcherbak & Nifatova,
2017). A use case diagram is another method for improving the solution scope by
highlighting the relationship between the different functions and the involvement of
the users in it. An ecosystem map is used to map all the functions both in upstream
and downstream to determine the different functions to addressed while developing
the solution. The feature tree or the fishbone diagram is used for developing the
different factors for achieving the final output. It consists of the high level features
and the low level features in each of the high level features.
Example
Business Requirement
An example of business requirement are as follows:
“Productivity of the business needs to grow by 10% within the next 3 years”
Stakeholder requirement
An example of stakeholder requirement are as follows:
“Development of new online ordering and sales management software”
Functional requirement
Examples of functional requirement are as follows:
“The software will provide daily sales report”
“The software will also provide monthly forecast”
“The software will take orders from the consumers”
“The software will provide detailed data on the most popular products”
Non-functional requirement
Examples of non-functional requirement are as follows:
“Ingredients will be sourced based on the procurement standards”
“The data privacy will be managed based on the data protection act”
Document Page
2BUSINESS ANALYSIS PROJECT
Transition requirement
Example of transition requirement are as follows:
“The responsibilities of the project group members will be realigned”
Document Page
3BUSINESS ANALYSIS PROJECT
References
Carstens, D.S., Richardson, G. & Smith, R.B. (2016). Project management tools and
techniques: A practical guide. CRC Press.
Hazır, Ö. (2015). A review of analytical models, approaches and decision support
tools in project monitoring and control. International Journal of Project
Management, 33(4), 808-815.
Ganushchak-Yefimenko, L., Shcherbak, V., & Nifatova, O. (2017). Managing a
project of competitive-integrative benchmarking of higher educational
institutions. Eastern-European journal of enterprise technologies.
chevron_up_icon
1 out of 4
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]