Software Engineering Technology by Jacobs - Article Example

He concludes this article by arguing that new business proposal managers, IT instructors, project managers, system engineers, and software project managers tend to overlook the engineering requirements from different perspectives. He recommends that clients and engineers should begin working together in order to understand each other’s opinions to ensure effective requirements engineering. Development teams should also understand what they can or cannot build, and this is only attainable through client and developer teamwork.

Jacobs further asserts that seasoned IT professionals remember panicking moments when the requirements are overlooked, when customers despise their services, when customers staff frequently change requirements or fail to agree, when they fail to develop promised requirements when estimates skew due to lack of understanding, and when all “nice to have’s” drive schedule and cost (Jacobs 23). Jacobs’s article primarily describes strategies for managing and defining engineering requirements.

It provides the meaning of engineering requirements, and how to describe useable requirements. He presents that there are several tools such as databases, checklists, and requirements modeling for maintaining and defining requirements and that IT professionals should learn how to select the best tools that keep things simple so that things do not get ugly (Jacobs 23).