Computer Sciences and Information Technology

Computer Sciences and Information Technology

Challenging issues in identifying and documenting IT acquisition requirements

According to Chatterjee, Sardar, Biondi-Zoccai & Kumbhani (2014), the process of identifying and documenting IT acquisition requirements requires significant work before establishing the contract. One of the most challenges issues in documenting and identifying IT acquisition requirements is acquisition planning. The events, such as setting the right structures and estimating essential effort for the acquisition project, need different methods. Pre-development stages comprise activities such as cost estimation and elicitation of requirements for software systems. These activities are vital for the attainment of the project and need extensive expertise in software engineering. Besides, these activities need exceptional organizational frameworks and significant effort. Nonetheless, neither techniques and generic tools nor the techniques and tools designed for software project management may be employed for multiple activities of pre-development stages. For instance, the size estimation case.

Experts are required to conduct the size estimation process to design the pre-development stages. But, the metrics used in initial life-cycle like function points may not be used since the requirements are not yet determined. According to Surbakti & Situmorang (2017), Software Engineering Institute practices and models states what acquisition process characteristics should have, but does not define how the process of acquisition should be executed or who to perform the activities. Thus, none of them gives the acquisition life cycle guide. Therefore, there is a need to create agency needs, including the description of requirements to fulfill the needs, select sources, solicitation, award of contracts, contract performance, formal agreement, and contract financing. These practices determine the acquisition type to be utilized for the products to be acquired and the transition of products acquired to the project.

If it should be permitted to add, delete, and change requirements after approval

The only inevitable thing in life is change, and contracts are not an exception of change as well. Maskoni & Poor (2017), define a deal as a legally binding document that brings two or more parties under a collective agreement. In the contract life-cycle, one or both parties can need to edit one or more things in the document, which means there can be changes to the primary obligations and entitlements of the contract. As the project progresses, the team can update the requirements after approval basing on the outcomes of the tracking processes. These changes may include adding, deleting, and changing conditions in the entry component to the time the service provider has signed it. Parties regularly adjust the contract if a need arises. Moreover, they can change a contract before signing process.

Experience in developing a work breakdown structure for individual project

To adequately develop a WBS, there is a need to implement strategies to interpret the project scope statement, conduct relevant research, and finally develop the WBS. According to Susiawan, Latief & Riantini (2019), a study on the development of WBS, the first step is to interpret project scope statements. Without doing so, a project will not be able to indeed start. There is a need to determine what the project scope statement says the project will deliver to the customer; in other words, what the result needs to be. Also, in the process of developing WBS, identify the criteria to use in determining if the project outcomes will meet the objectives. The most challenging step in the development of WBS is the evaluation of the project objectives (Susiawan, Latief & Riantini, 2019). Finally, the WBS should incorporate the project scope statement and what is involved in managing the expectations of stakeholders and the constraints in the project.

References

Chatterjee, S., Sardar, P., Biondi-Zoccai, G., & Kumbhani, D. (2014). Establishing Comparable Requirements and Treatment Groups Before Applying Statistical Comparison—Reply. JAMA Neurology, 71(3), 371. doi: 10.1001/jamaneurol.2013.6003

Maskoni, A., & Poor, C. (2017). An examination of agreement between the parties preceding the time of transferring the ownership from the moment of signing the contract. International Review, (3-4), 147-153. doi: 10.5937/intrev1704147m

Surbakti, I., & Situmorang, K. (2017). Acquisition Planning and Language Acquisition by Indonesian Four-year Old Children. International Journal Of Linguistics, 9(3), 152. doi: 10.5296/ijl.v9i3.11176

Susiawan, T., Latief, Y., & Riantini, L. (2019). Development of WBS (Work Breakdown Structure) risk-based standard for safety planning at seaport project. Journal Of Physics: Conference Series, 1360, 012007. doi: 10.1088/1742-6596/1360/1/012007