Free SME Mobile B2B Application Dissertation Example

0 / 5. 0

SME Mobile B2B Application

Category: Architecture

Subcategory: Business

Level: Masters

Pages: 3

Words: 825

SME Mobile B2B Application
Functional Requirements
Functional requirements are a critical component for company X’s desire to introduce a mobile app that would enable it to connect with its customers. The discussion below illustrates the functional requirements that would make the project successful.
Architecture alignment. This involves examining the architectural and program needs for the new app. Zhao and Luo, (2014) highlight that an architectural alignment incorporates system features, and design patterns that create user-friendly interfaces.
Personalization options. These are the features that should be incorporated into the app to make it look exciting and elicit positive emotions among the users. These include flexible settings, attractive colors, and fonts.
Integration features. This includes how the application connects the customer to the company. The incorporation of features for the call, messaging, and tracking user’s interaction with the system can help to improve their connection with the firm.
Cost-benefit analysis. One of the functional requirements of this project is performing a cost-benefit analysis of the development of the app. This is an activity that involves examining the cost of the project versus the likely benefit that is to be gained from its use. In this regard, the cost includes the project development billings, related training expenses, software purchases, and other support activities. The benefits of the project should outweigh the costs to be deemed feasible.
Stakeholder analysis. This involves determining how the new app affects the individuals who are affected by it (Edkins et al., 2013). The employees of company X are a critical stakeholder since the app will determine how they relate with the customer. An analysis of how the app improves or hinders their activities will be essential in addressing any problems that may occur. The company’s shareholders will also be a critical stakeholder since they provide the resources required in the project. Finally, there is a need for determining how the mobile app will affect the consumers who will use it. Thus, it should fulfill the needs of the customers.
Structural Requirements
The structural requirements outline the support needs the client provides in the project implementation. The structural requirements include:
Staffing needs. In this case, the client provides the capabilities of skills, experience, and knowledge of personnel that understands app development and incorporation of the system features (Edkins et al., 2013).
Front-end management. This is where the client codes and offers the visual elements of the app while maintaining constant communication to clarify issues on an ongoing basis. According to Edkins et al. (2013), through front-end management, the client provides other critical project features such as content and security of the application.
Documentation. Documenting the whole process of using the app answers the question of efficiency to the end user, their security, and reliability (Reddy and Priyadarshini, 2016). Documenting the new application by the client helps the firm managers and staff to understand how to use the system.
Training. In this case, the client provides training to the firm staff to help them understand how the application system works. The client in collaboration with the firm may also conduct training of the customers in the usage of the app during the rollover stage.
Support and maintenance. During the first few years of the project delivery to the firm, the client takes the initiative to help the staffs become accustomed to the new application. Similarly, the client maintains contact with the firm to provide maintenance services on an ongoing basis to ensure that the system remains relevant and continues to address user objectives.
Resource Requirements
The client will have to provide the following resources to enhance the successful completion of the project:
Hardware. The client will provide the related hardware which refers to the physical components of the project. These include electronic apparatus to support the new app at the organization
Software. These consist of the program features with complete security features and user-interfaces for the project. Since the application runs on the user side, the software resources to be delivered by the client include control programs that will be used at the organization level.
User manual. This will be a critical resource to be provided by the client. It details how the users, both at the organizational and customer level should use the new app (Reddy and Priyadarshini, 2016). The user manual should be provided in both print and electronic format and provided the users with guidance on how to use the system.
Allocation memory. This is where the client will specify the memory requirements for the users of the new app. This relates to the storage space for the new app on mobile devices. The client has to document the allocation memory and minimize it as much as they can to allow the users user them in their mobile devices with ease.
Project time plans. This is where the client has to raise a detailed plan showing the critical project activities and time schedules for the achievement of each task. The plan is delivered to the firm to create awareness of critical project implementation milestones.
Database engine. This is where the client will provide a software tool to enables the firm to create, update, read, and delete data from the database that supports the mobile app. It is a critical resource that will enable the firm to take control of the operations of the new application.
References
Edkins, A., Geraldi, J., Morris, P. and Smith, A., 2013. Exploring the front-end of project management. Engineering Project Organization Journal, 3(2), pp.71-85.
Reddy, K.R., and Priyadarshini, C. 2016. 5 key functions to maintain a successful project management office in organization. International Journal of Pharmaceutical Sciences and Business Management, 8 (4), pp. 19-36.
Zhao, Y. and Luo, X., 2014. The Multiple Attribute Group Decision Making model for Web Software Trustworthiness. JSW, 9(3), pp.763-776.

All Examples

Do you need an original paper?

Approach our writing company and get top-quality work written from scratch strictly on time!

Get an original paper