Computer Science and Information Technology
Computer science and information technology play an integral part worldwide. It is also a business idea, and many tend to win contracts in supplying these computer requirements and running projects. However, it comes with numerous challenges that need to be resolved. This essay will discuss contract winning and the requirements for acquiring and documenting them.
Identifying and documenting IT acquisition requirements requires a lot of keenness during the planning stage. This is to avoid any unseen problems and chaos that may arise later. The issues in identifying and documenting IT acquisition requirements that somebody can ascertain to be challenging are understanding the business needs and developing an effective requirement document, as per Bjarnason et al. (2014). The business needs and how they will be addressed if the IT requirements are acquired should have been understood well. The cost-effectiveness and the security of these needs must be considered when undertaking the business needs and requirements.
Developing a practical requirements document has also proven challenging when identifying IT requirements. The document should entail all the details of the project. It should be clear and have all the project requirements captured as small as possible to avoid missing them during the project implementation, as per Robertson, S., & Robertson, J. (2012). Developing a practical requirements document requires engaging all the stakeholders and clients proactively to come up with an exclusive requirements document that includes all things, including the cost and timeline of the completion of the project.
The permission to add, delete, and change requirements after they have been approved up to the time a contract has been signed is legally granted. Contract alterations may occur after it has been signed and both parties have agreed on the modification of the contract to meet some needs, as per Macaulay, S. (2018). This modification can only be effective if both parties are involved in the alterations; otherwise, it will not work if one party modifies it, as it will be a breach of contract, which is legally binding. However, alterations of a contract come with some significant issues. The contract implementation time will be delayed, which may cause some loss of funds that generally affect the running of a project and increase the overhead cost.
A work breakdown structure is a hectic process that challenges almost everyone who wants to undertake a project. One needs to consciously understand the subject of the project very well to capture all the relevant details when breaking down a project. A project is carried out in steps, so the project needs to be broken down. Developing and breaking a project requires a lot of keenness and concentration. It also requires ample time to avoid rushing and missing some project parts. One can work with some group members to brainstorm ideas relevant to the subject of the project.
In conclusion, concentration and keenness are paramount when carrying out any project and during contract documentation and winning.
References
Bjarnason, E., Runeson, P., Borg, M., Unterkalmsteiner, M., Engström, E., Regnell, B., … & Feldt, R. (2014). Challenges and practices in aligning requirements with verification and validation: a case study of six companies. Empirical software engineering, 19, 1809-1855.
Robertson, S., & Robertson, J. (2012). Mastering the requirements process: Getting requirements right. Addison-Wesley.
Macaulay, S. (2018). Non-contractual relations in business: A preliminary study. In The Sociology of Economic Life (pp. 198-212). Routledge.