Computer Science

To get high quality software, various documents associated with software development like Requirement Specification must be verified and validated. People doing the verification or validation effectively must get an understanding of these documents.
Reading is the key technical activity to understand a document and one of the effective reading techniques is called Perspective-Based Reading (PBR). A PBR review ensures that requirements are sufficient to support all the necessary later stages of software development.
PBR helps reviewers answer two important questions about the requirements they inspect: What information in these requirements should they check? How do they identify defects in that information?

Software development involves teamwork and a lot of communication. It seems rational to put all your engineers in one place, encourage them to share objectives, and let the project (collocated project) run. In line with this, only a decade ago, the number of entities engaging in Global Software Development was small—but this has rapidly changed. Many Fortune 500 firms have already done with or are in the process of a radical push to send their key software processes to offshore centres.
This paper layout the challenges, the problems faced and the success factors of Global Software Development and addresses how to remain organized in distributed teams. There are basically two critical, strategic reasons for moving to offshore software development: cost advantage and a large labour pool. Furthermore, the radical rethinking in our collective concept of a firm enables software globalization. Another source for internationally dispersed software development is the growing number of acquisitions and mergers, which add new markets, products, engineers, and creativity to the existing team.

Technology Experience Repositories (TERs) as part of the learning software organization are considered to be one means for providing the decision makers in software development with the type of evidence about technologies that they need to support informed decision-making when introducing new technologies. A systematic literature review on TERs was conducted to characterize them with regard to the following research question: "What are the success factors for the implementation of Technology Experience Repositories and how TER differs for Agile Process settings"? The review includes publications on TER up to and including 2011. 6952 studies were identified, of which 33 were considered as relevant for answering the research question. The studies were characterized along three themes: Success Factors of TER, TER Implementation and TER for Agile Process. The review investigates what is currently known about the success factors for the implementation of TER and how it differs for agile process settings. For the industrial readership, the review provides a map of findings that can be compared for relevance to their own settings and situations.