2 1 2 1 User Requirements User requirements typically describe the needs goals and tasks of the user Maiden 2008 ascertained that stakeholders analysts and designers often fail to differentiate the roles of user and system requirements but unfortunately treating them as the same thing can create problems for the projects as in the mobile B2B application It is encouraged that any user requirements document define and describe the end user and that any measurements of quality or success be taken with respect to the end user of the mobile B2B application User requirements specify the acceptable level of user performance and satisfaction with the system and hence are usually defined after the completion of the task analysis the examination of the tasks and goals of the end user 2 1 2 2 System Requirements System requirements can be defined in two ways First it can refer to the software requirements that describe the capabilities of the mobile B2B application system with which the product will function For example the web site may need to run on an application server and be clustered Second it can refer to the requirements that describe the mobile B2B product itself with the meaning that the product is a system 2 1 2 3
Software Requirements Specifications Software requirement specifications describe what the software or web site should do by defining functions and high-level logic It should also provide a realistic basis for estimating product costs risk and schedules Bourque and Fairley 2014 Roger 2010 suggested that the software requirements specification document should enlist enough and necessary requirements that are required for the project development as in the case of the mobile B2B application If the user requirements are written for the requestor and not the end user the user requirements are combined with the mobile B2B software requirements specifications Software requirements specifications specify what the system must do 2 1 2 4 Design Specifications A design specification is a detailed document providing information about a designed product or process Mohan 2015 This deals with diagraming the organization of the information i e data flow diagrams Designing flowcharts can be very handy when trying to work through a lot of information Anything you develop now will change over time but you will want a thorough flowchart for the mobile B2B application included with the software requirement specification Also the design specifications should include navigational path through the information on this diagram Visio is an awesome tool for developing technical diagrams and flowcharts such as these 2 2 Objective 2 Structural Requirements
After revealing the physical requirements above the structural requirements for the implementation of the mobile B2B application seeks to focus more on the current company structure and capabilities in implementing and sustaining the mobile application 2 2 1 Human Resource Planning Bulla and Scott 1994 defined human resource planning as the process for ensuring that the human resource requirements of an organization are identified and plans are made for satisfying those requirements Human resource planning includes creating an employer brand retention strategy absence management strategy flexibility strategy talent management strategy recruitment and selection strategy Reilly 2003 also defined workforce planning as a process in which an organization attempts to estimate the demand for labour and evaluate the size nature and sources of supply which will be required to meet the demand Human resource planning should serve as a link between human resource management and the overall strategic plan of an organization The planning processes of best practice organizations not only define what will be accomplished within a given time frame but also the numbers and types of human resources that will be needed to achieve the defined business goals such as successfully implementing and sustaining the mobile B2B application by the client 2 2 1 1 Assessing the Current Human Resource Capacity This stage develops a skills catalog for your employees so that you have a clear understanding of what your staff currently holds This employee catalog should including everything from volunteer activities to certifications of all degrees These catalogs can be assessed to deem whether or not an employee is ready to add more responsibility or to forecast the employee's future development plans for the mobile B2B application 2 2 1 2 Forecasting Human Resource Requirements This stage includes projecting what the HR needs for the future will be based on the strategic goals of the organization in order to effectively sustain the mobile B2B application
Keep in mind you will need to also accommodate for external challenges that can affect your organization Some questions to ask during this stage include which jobs will need to be filled in the upcoming period What skill sets will people need How many staff will be required to meet the strategic goals of our organization Is the economy affecting our work and ability to appeal to new employees How is our community evolving or expected to change in the upcoming period 2 2 1 3 Gap Analysis Gap analysis is the comparison of actual performance with potential or desired performance Kalpana 2013 During this stage you will observe where your organization is currently and where you want to be in the future You will identify things such as the employee count and skills evaluation and compare it to what will be needed to achieve your future goal implementing the mobile B2B app During this phase you should also review your current HR practices and identify what you are doing that is useful and what you can add that will help you achieve your goal These questions are to be answered during this stage what new jobs will we need What new skills will we need Do our present employees have the necessary skills Are employees currently aligned to their strengths Are current HR practices adequate to meet our future goal
Write and Proofread Your Essay
With Noplag Writing Assistance App
Noplag.com. User Requirements Document Define and Describe the End User (2020, January 30) Retrieved from https://noplag.com/free-essays/user-requirements-document-define-and-describe-the-end-user
Noplag.com.(2024.) User Requirements Document Define and Describe the End User [Online]. Availible at: https://noplag.com/free-essays/user-requirements-document-define-and-describe-the-end-user [Accessed: 22 Dec. 2024]
"User Requirements Document Define and Describe the End User" Noplag, 22 Dec 2024, https://noplag.com/free-essays/user-requirements-document-define-and-describe-the-end-user
"User Requirements Document Define and Describe the End User". Noplag, Jan 30, 2020. Accessed: December 22, 2024. https://noplag.com/free-essays/user-requirements-document-define-and-describe-the-end-user
"User Requirements Document Define and Describe the End User" Noplag, 22 Dec 2024, https://noplag.com/free-essays/user-requirements-document-define-and-describe-the-end-user
"User Requirements Document Define and Describe the End User" Noplag, 30-Jan-2020. [Online]. Availible: https://noplag.com/free-essays/user-requirements-document-define-and-describe-the-end-user . [Accessed: 22-Dec-2024]
Noplag. (2020). User Requirements Document Define and Describe the End User30-Jan-2020. . [Online]. Availible at: https://noplag.com/free-essays/user-requirements-document-define-and-describe-the-end-user [Accessed: 22-Dec-2024]
{{cite web|url=https://noplag.com/free-essays/user-requirements-document-define-and-describe-the-end-user |title=User Requirements Document Define and Describe the End User|publisher=Noplag.com |date=January 2020 |accessdate= 22 December 2024 }}
Noplag. User Requirements Document Define and Describe the End User [Internet]. January 2020. [Accessed December 22, 2024.]; Availible from: https://noplag.com/free-essays/user-requirements-document-define-and-describe-the-end-user