Recommended
Recommended
More Related Content
Similar to Running Head E-GRANT REQUIREMENTS2E-GRANT REQUIREMENTS .docx
Similar to Running Head E-GRANT REQUIREMENTS2E-GRANT REQUIREMENTS .docx (20)
More from todd271
More from todd271 (20)
Recently uploaded
Recently uploaded (20)
Running Head E-GRANT REQUIREMENTS2E-GRANT REQUIREMENTS .docx
- 1. Running Head: E-GRANT REQUIREMENTS 2 E-GRANT REQUIREMENTS 2 E-grant Requirements Krishna Marepalli 170068 Harrisburg University E-grant requirements Business requirements User requirements System requirements Non-functional requirements Safe means of money transfer The applicant requires to enter their banking details into the system. The e-grant system should enable the user to enter their banking data. Conform with financing p & ps The state administrators require to send money to applicants (Little, 2016). The e-grant system should also enable the user to select the account type they wish their money to be deposited. Submission of applications The applicant requires to sign in to the system at any time. The system should allow the user to create an account and enter their data.
- 2. Conform with system processing p & ps User should be in a position to select the required application from a list of applications. The system should be user friendly and should allow them to navigate through the application process (Alla, Pazos & DelAguila, 2017). The user requires to submit their applications The system is required to send confirmatory messages to the applicants. Implementation of a standard accreditation scale. Administrators require to evaluate the applications. The system should permit the administrators to access the applications at all times. Conform with auditing p & ps The system is required to store the applications in a systematic manner for easier retrieval. Administrators require to turn down or approve applications. The system should allow the administrators to carry out these approvals and rejections (Chari & Agrawal, 2018). The system is required to allow for a comment section. Administrators require to enter applications scores manually The system should enable the administrators to enter the
- 3. applications scores. The system should enable the entered scores to be saved. The system is also required to update the scores regularly and automatically. References Alla, S., Pazos, P., & DelAguila, R. (2017). The Impact of Requirements Management Documentation on Software Project Outcomes in Health Care. In IIE Annual Conference. Proceedings (pp. 1419-1423). Institute of Industrial and Systems Engineers (IISE). Chari, K., & Agrawal, M. (2018). Impact of incorrect and new requirements on waterfall software project outcomes. Empirical Software Engineering, 23(1), 165-185. Little, T. A. (2016). A Foundational Perspective on Core Competency Requirements for Project Management Initiatives. Requirements Workshop Agenda eGrants Project Date, Time & Location Objective and Scope To …
- 5. Running Head: REPORT FOR THE EGRANTS PROJECT 1 REPORT FOR THE EGRANTS PROJECT 2 Report for the eGrants Project Krishna Marepalli ITPM 515 170068 Date: 30th September 2019 Total eGrants approved for the first quarter of the year Agency name: Finance Approvals: 1 Pending Applications: 1 Rejected applications: 1 Applicant’s name: John Stones Applicant’s no: 45672389 Status: Approved Amount: $23,000 Amount credited: Yes Applicant’s name: James Milner Applicant’s no: 34562387 Status: Pending Amount: $50,000 Amount credited: No
- 6. Applicant’s name: Mart Roberts Applicant’s no: 67856453 Status: Rejected Amount: $45,000 Amount credited: No Agency name: Information Technology Approvals: 2 Pending Applications: 1 Rejected applications: 1 Applicant’s name: Eden James Applicant’s no: 56473896 Status: Approved Amount: $35,000 Amount credited: Yes Applicant’s name: Kevin Andrew Applicant’s no: 87695463 Status: Approved Amount: $20,000 Amount credited: Yes Applicant’s name: Alex John Applicant’s no: 68965743 Status: Pending Amount: $14,000 Amount credited: No Applicant’s name: Jose Hazard Applicant’s no: 65435289 Status: Rejected Amount: $36,000 Amount credited: No Agency name: Operations Management
- 7. Approvals: 1 Pending Applications: 2 Rejected applications: 0 Applicant’s name: George Andrew Applicant’s no: 56473844 Status: Approved Amount: $14,000 Amount credited: Yes Applicant’s name: Alex John Applicant’s no: 78654368 Status: Pending Amount: $34,000 Amount credited: No Applicant’s name: Cynthia John Applicant’s no: 98965643 Status: Pending Amount: $6,500 Amount credited: No Report date 30th Sep 2019 Requirements Management Plan Krishna Marepalli
- 8. ITPM 515 Overview of the Requirements Management Plan The e-Grants app is a platform that is aimed at automating the process of application, allocation and disbursement of grants. Purpose of the Requirements Management Plan The e-Grants requirements management plan aims at bringing together all grant application systems to be collectively harmonized and hence through a coordinated system, they can be allocated easily. Scope of the Requirements Activity at this Time The scope includes the formulation and modification of an approach that can be utilized throughout the state hence bring about the provision of process that incorporates security, simplicity, automation as well as adequate communication of the grants process through the online platform (Nicholas et al, 2017). Process The process includes the identification of the areas that need optimization of the automation process so that the desired specifications can be achieved through the application of necessary processes and resource allocation (Stark, 2015). Roles and Responsibilities The developer of the system gets the specifications of the desired design from the client who in this case is the government after which they execute the plan as prescribed to them (Mesquida et al, 2016). The government has the responsibility of providing financial support and the requisite resources for the implementation of the project. Rules/Procedures
- 9. The team must adhere to the set requirements regarding the management plan which thus requires all stakeholders to strictly adhere to the procedures and guidelines regarding the implementation of government projects. International standards must be met regarding the equipment as well as procedures used. Prioritizing and Tracking Requirements (Attributes) The requirements of the project would be relative to the importance associated with the particular attribute requisite for the undertaking. Professional in various sections of the project will need to meet set guidelines and thus should be approved by the respectful institutions. Requirements Management Tools The appropriate tools will be used to conduct various activities as may be most appropriate. MS word will be utilized for the purposes of documentation besides the use of MS excel for documentation of calculations (Eskerod et al, 2016). The MS access interface of appropriated and modified for the process of data capture. Schedule The recruitment of personnel will come first for purposes of pooling the best human resource to conduct the exercise. The allocation of duties comes next for purposes of optimization of the process. The work schedule structure will thus follow and finally the coordination of the work while undertaking the actual execution of the project. Running Head: REQUIREMENTS MANAGEMENT PLAN 2 Requirements Management Plan [e-Grants] Last Update: [4th August 2019] 2
- 10. Approval and Authority to Proceed We approve the project component as described above, and authorize the team to proceed. Name [type or sign name] /Title Date Dennis Brown Project Manager/ 4/8/2019 James Saddle Supplies controller 4/8/2019 Timmy Tractor Finance manager 4/8/2019 Johannes Shimizu Chief Coordinator 4/8/2019 Katlyn Jones Overall manager 4/8/2019 Prepared By: Charles Gregor – Planning coordinator.
- 11. References Eskerod, P., & Jepsen, A. L. (2016). Project stakeholder management. Routledge. Mallari, N. A. D., Collar, N. J., McGowan, P. J., & Marsden, S. J. (2016). Philippine protected areas are not meeting the biodiversity coverage and management effectiveness requirements of Aichi Target 11. Ambio, 45(3), 313-322. Mesquida, A. L., & Mas, A. (2015). Integrating IT service management requirements into the organizational management system. Computer standards & interfaces, 37, 80-91. Nicholas, J. M., & Steyn, H. (2017). Project management for engineering, business and technology. Routledge. Stark, J. (2015). Product lifecycle management. In Product lifecycle management (Volume 1) (pp. 1-29). Springer, Cham. Change Request Organization: Date: Project Manager: Project Name: Project Sponsor: Change Request Prepared By: Version/Number: Revision Date: Change Request Description Business or Technical Justification
- 12. Priority and Impact if Change is Not Implemented |_| HIGH |_| MEDIUM |_| LOW Impact Assessment Project Area Yes or No Detail impact Cost Schedule Resources Requirements Goals/Objectives Deliverables
- 13. Risk Technical Architecture Other Projects Options for Resolution Recommendation in Bold 1. [insert text] Change Request Resolution Change Request Decision □ Approved □ On Hold □ Denied Decision Date Decision Made By □ Project Manager □ Project Sponsor □ Executive Sponsor □ Other Decision Maker Name 1