Search (2 results, page 1 of 1)

0.0018318077 = product of:
  0.0036636153 = sum of:
    0.0036636153 = product of:
      0.0073272306 = sum of:
        0.0073272306 = weight(_text_:a in 2712) [ClassicSimilarity], result of:
          0.0073272306 = score(doc=2712,freq=14.0), product of:
            0.043477926 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.037706986 = queryNorm
            0.1685276 = fieldWeight in 2712, product of:
              3.7416575 = tf(freq=14.0), with freq of:
                14.0 = termFreq=14.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2712)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Software development is usually referred to as a knowledge intensive practice. In fact, companies involved in software development are Said to be the most clear example of the companies whose revenue and value is based in the creation, representation and modeling of knowledge. The software development process starts with the capture of some requirements provided by the final users or by the project stakeholders. Taking these requirements as a basis, the development teams must cross the chasm from the text-based requirements to their representation in a specific programming language. To move from the textual representation of the software requirements to the final code, different steps and artifacts must be created. These artifacts also represent the knowledge embeded in the functional specifications, and are an intermediate step to reach the final representation: the programming code. The author analyses the impact of knowledge management in software development processes, and describes the possibility of using a shared pool of code to make possible the sharing of the knowledge gained. A prototype tool to create and maintain the repository of code and link this code to functional specifications and any other artifacts (documents, models, reports, etc.) is described. This tool will link together the knowledge created at the different levels (business analysis, analysis, design, coding, etc.) in the development process to make the reuse of code easier.

Type

a

0.0013847164 = product of:
  0.0027694327 = sum of:
    0.0027694327 = product of:
      0.0055388655 = sum of:
        0.0055388655 = weight(_text_:a in 2515) [ClassicSimilarity], result of:
          0.0055388655 = score(doc=2515,freq=8.0), product of:
            0.043477926 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.037706986 = queryNorm
            0.12739488 = fieldWeight in 2515, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2515)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The internal organization of large software projects requires an extraordinary effort in the development and maintenance of repositories made up of software artifacts (business components, data models, functional and technical documentation, etc.). During the software development process, different artifacts are created to help users in the transfer of knowledge and enable communication between workers and teams. The storage, maintenance and publication of these artifacts in knowledge bases - usually referred to as "software repositories" are a useful tool for future software development projects, as they contain the collective, learned experience of the teams and provide the basis to estimate and reuse the work completed in the past. Different techniques similar to those used by the library community have been used in the past to organize these software repositories and help users in the difficult task or identifying and retrieving artifacts (software and documentation). These techniques include software classification - with a special emphasis on faceted classifications, keyword-based retrieval and formal method techniques. The paper discusses the different knowledge organization techniques applied in these repositories to identify and retrieve software artifacts and ensure the reusability of software components and documentation at the different phases of the development process across different projects. An enumeration of the main approaches documented in specialized bibliography is provided.

Source

Knowledge organization for a global learning society: Proceedings of the 9th International ISKO Conference, 4-7 July 2006, Vienna, Austria. Hrsg.: G. Budin, C. Swertz u. K. Mitgutsch

Type

a