This document is a report bid proposal for conducting a scoping study that determines the necessary requirements for development and implementation of a B2B mobile application for the client, company X. The report focuses on different things that the client should consider before investing resources into the project, helps the company to make the necessary preparations and serves as a strategic decision making tool.
The approach presented are techniques and methods approved by industry experts as well as case study-based experiences. The bid introduces the appropriate methods to investigate the suitable functionalities of the B2B application (Functional requirements), conditions necessary for the adequacy of the implementation of the application in the structural conditions of the company X (Structural requirements) and the resources requirements for the project.
While the study will be conducted within six (6) months, a Gantt chart is used to indicate which activities should be performed; as well as where and when, in order to complete the study efficiently and effectively. Lastly, the contribution section acknowledges the benefits of the methods/techniques chosen, their relevance to the project and the reasons why they were adopted in the study.
Table of Contents
1. INTRODUCTION
1.1. Study Objectives
1.2. Methodology
2. SUPPORTING EVIDENCES
2.1. Objective 1: Functional Requirements
2.1.1. Market and Stakeholder Analysis
2.1.2. Software evaluation
2.1.3. Security Requirements analysis
2.2. Objective 2: Structural Requirements
2.2.1. System Environmental Analysis
2.2.2. Personnel Analysis
2.2.3. Risk Identification and Analysis
2.3. Objective 3: Resource Requirements
2.3.1. Project Time Planning
2.3.2. Life Cycle Cost Analysis
3. STUDY GANTT CHART
4. CONTRIBUTIONS
4.1. Objective 1: Functional Requirements
4.1.1. Market and Stakeholder Analysis
4.1.2. Software Evaluation
4.1.3. Security Requirements analysis
4.2. Objective 2: Structural Requirements
4.2.1. System Environmental Analysis
4.2.2. Personnel Analysis
4.2.3. Risk Identification and Analysis
4.3. Objective 3: Resource Requirements
4.3.1. Project Time Planning
4.3.2. Life-Cycle Cost Analysis
5. CONCLUSION
6. REFERENCES
Project Objective and Scope
The primary objective of this project is to provide a strategic scoping study for Company X, an SME in the food industry, to determine the necessary requirements for the successful development and implementation of a B2B mobile application. The study aims to act as a decision-making tool, guiding the client through functional, structural, and resource-related considerations before they commit significant resources to the project.
- Identification of functional requirements through market analysis and software benchmarking.
- Assessment of structural requirements, including system environment, personnel skills, and risk factors.
- Determination of resource requirements through project time planning and life-cycle cost analysis.
- Creation of a detailed Gantt chart to manage project execution over a six-month timeline.
Excerpt from the Book
2.1. Objective 1: Functional Requirements
As early mentioned, mobile has become a new frontier in the current dynamic and complex business environment where technology continues to shrive. Because mobile devices are used on a move, all businesses, either big or small will eventually need to develop a mobile app to allow customers to reach them from wherever they are (Ali, 2013).
Oinas-Kukkonen et al (2013) distinguish two types of mobile applications: “highly goal-driven and entertainment-focused”. According to them, the difference lies in their features and functionalities, which vary depending on the app purposes. What’s more challenging on today’s marketplace is developing an application that adds value to your business.
Recognizing that mobile B2B applications face market acceptance problems due to lack of user-focus and relevance (Sadler, 2005), to succeed on marketplace, mobile B2B applications are best examined their functioning and the value they provide to their users.
Summary of Chapters
1. INTRODUCTION: This chapter introduces the growth of mobile technology in a business context and defines the specific objectives for scoping a B2B mobile application for Company X.
2. SUPPORTING EVIDENCES: This section reviews existing literature, techniques, and methodologies required to analyze functional, structural, and resource requirements.
3. STUDY GANTT CHART: This chapter presents the project timeline and illustrates how interdependent tasks are scheduled over the course of six months.
4. CONTRIBUTIONS: This section discusses the practical application of chosen methods, detailing how they contribute to achieving project objectives and client success.
5. CONCLUSION: The conclusion synthesizes the study findings and provides final guidance for the client's decision-making process regarding the mobile app project.
6. REFERENCES: This section lists all academic and industrial sources cited throughout the document.
Keywords
Requirements elicitation techniques, B2B application, software engineering, requirements engineering process, mobile app features, functionality, market analysis, stakeholder analysis, system environmental analysis, personnel analysis, risk identification, project time planning, life-cycle cost analysis, Gantt chart, SME
Frequently Asked Questions
What is the primary goal of this management project?
The primary goal is to provide a scoping study for Company X that identifies the functional, structural, and resource requirements necessary to successfully develop a B2B mobile application.
Which key areas does the report cover?
The report covers functional requirements (market and stakeholder needs), structural requirements (IT environment and personnel), and resource requirements (time planning and cost analysis).
What research methodology is employed in the study?
The project utilizes an industry-based and case-study approach, incorporating established techniques like requirements elicitation, software benchmarking, risk identification, and life-cycle cost analysis (LCCA).
How is the project schedule managed?
The project uses a Gantt chart to visualize the six-month (24-week) timeline, mapping out interdependent tasks to ensure efficient execution and timely delivery.
Who is the target audience for this document?
The target audience is the management team of Company X, as the report serves as a strategic decision-making tool for their upcoming investment in mobile technology.
What is the importance of software benchmarking in this context?
Benchmarking allows Company X to compare potential app functionalities with industry leaders, ensuring that the final product offers competitive advantages and effectively meets user needs.
How does the study address IT security for the B2B mobile app?
The study emphasizes the need to identify security requirements (such as authentication and authorization) and proposes using the Common Vulnerability Scoring System (CVSS) to mitigate project risks.
Why is personnel analysis critical for the success of this project?
Personnel analysis ensures that Company X has the right staff with appropriate skill sets to manage the development, implementation, and ongoing maintenance of the new application.
How does the LCCA contribute to the decision-making process?
Life-Cycle Cost Analysis helps the client understand the total financial commitment beyond initial development costs, covering maintenance and future operational expenses.
What happens if the client's requirements change during the study?
The consultant maintains constant communication with the client, ensuring that any identified changes or new project needs can be integrated into the study in a timely manner.
- Quote paper
- Sixbert SANGWA (Author), 2018, Requirements Elicitation for the Development and Implementation of a B2B Mobile App. Writing A Consultant Bid Report, Munich, GRIN Verlag, https://www.grin.com/document/1008017
