QA (Quality Assurance)
  • Configuration Management
  • SILKROAD possesses its own process engine(Figure1) which means that users can modify workflow of a project according to their organization’s project policy. Users can create baseline and include change items and change request on it. Change request, Change control board and change order processes are preceded following the workflow that users have customized. Complicated workflow can be created by connecting simple processes.
  • Limitations of Traditional CM
  • File Deltas
    • Storing the entire file contents for every revision would be very wasteful because many lines would be similar or identical. This led to the development of file deltas – a technique allowing the storage of the difference between incremental revisions of a single file:
  • Manages File revisions NOT Software versions
    • File deltas is dependent upon the exact revision of a file to which it applies; trying to apply a file delta to a different revision of the same file is not always possible. As a result of this, it is natural to visually represent file deltas as jigsaw pieces that fit one on the other as follows:
    • If a file delta (excluding the final one) needed to be removed, perhaps because the associated software enhancement or fix had to be undone, the diagram indicates that the file deltas before and after the removed file delta would not fit together:
  • Importance & Benefits of CM
  • Provides a snapshot of dynamically changing software to help:
    • - Make decisions based on an instantaneous view
      - Determine status at module and system levels
      - Make better decisions about the future of a software project.
  • Tracks concurrent development of modules or components of the overall system to:
    • - Prevent different developers from making changes to the same module at the same time
      - Allow for the overall system progress to be faster.
      - Provide visibility of the entire software project to all developers.
  • Organizes all concurrently developing code and associated documentation to:
    • - Save overall project time.
      - Focus each phase of the software product development to be organized and executed in a documented, prescribed manner.
Main features & Functions
Workflow Integration
Data Integration between Requirement Documents, Baseline, CR & CCB
Baseline Management
CR Management
CCB Management
Baseline Management
It creates Baseline links related CR and request approval using the workflow. It marks any changes made in CI to an icon for Baseline approval.
CCB Management
It manages main CR and members who will join CCB. Users can register whether approval for CR is guaranteed based on meeting results of CCB.
CR management
It registers change request about Baseline in special form and decides whether it should be approved or rejected.
CO Progress Management
CO generated by approval for CR is managed as a task and users can check progress rate of the task.
Source code automatic tagging
It registers source code saved in Source Code Repository to baseline. When the source code is registered, it automatically uses the tag from Source Repository or converts revision into tag and then register it.
  • SILKROAD manages and traces requirements and configuration efficiently by data integration between 3rd party’s developing tools and self-developed tools.
  • btn_gs
  • btn_tuv