Understanding what a software system has to do is a key part of building successful software and requirements are an important tool for making sure the right thing is built. However, maintaining formal requirements is very expensive and as Hartson and Pyla (2012) state: ■ Detailed formal requirements cannot ever be complete. ■ Detailed formal requirements cannot ever be 100% correct. ■ Detailed formal requirements cannot be prevented from changing throughout the life cycle (p164) This provides a problem for software developers, as expensive formal requirements may not adequately describe the project. Glinz and Fricker (2015) explore the idea of implicit 'shared understanding' as a way of decreasing a reliance on formal requirement specifications. For this task you will review Glinz and Fricker's paper and assess the use of implicit shared requirements as a way of dealing with the problem of managing requirements. Section 1: Introduction In this section you should consider: ■ Explain the purpose of the paper (e.g., report research results, raise awareness of an issue, propose a theory, review work practice, etc) ■ Define any key terms or concepts Section 2: Significance and Contribution In this section consider: ■ Does the paper have anything important to say, if so, what is it? Section 2: Evidence In this section consider: ■ What arguments are made to support the author's position? ■ What evidence is used to support their position? ■ How convincing are the arguments/evidence presented? ■ Can you find any counter evidence or have an opposing argument? Section 3: Implications for software development In this section consider: ■ What are the implications of the paper for the software development community? ■ Is the author's position consistent with UCD process and principles?