Search

Computer aided assembly planning plays an important role in optimization of the assembly procedure. For this reason, a lot of research works have been done in the field of assembly planning and various assembly planning approaches have been improved. The assembly time is minimized by obtaining both all feasible assembly sequences and optimum assembly sequences through these computer aided assembly planning approaches. In this paper, the assembly planning approaches were discussed and classified according to methods utilized. [ABSTRACT FROM AUTHOR]

The article presents information on the role of Version Control (VC) systems in developing computer softwares. One of the oldest, most vulnerable VC systems is Concurrent Versions System (CVS). CVS is a open source tool. As software is developed in small steps or versions. These versions are results of collaborations among different persons. At times one want to refer to a previous version or compare various variants. Sometimes, one need to trace changes to change requests. All these tasks are concerned with version control. VC systems only stores the differences between successive versions. The basic VC idea is to separate the files that programmers work on, called working copies, from the master copies of the same files, which are stored in a repository. The programmers never work on the repository. They check out their working copies from the repository, make changes, and then check in their changes. Every time a programmer commits a file, the VC system creates a new version in the repository. In this way, the repository contains all versions of a file. In addition, it also highlights the comparison between various version control systems. INSET: Version Control System Resources..

The article discusses ways to identify and capture early aspects in requirements and architecture activities related to computer softwares. Early aspects are concerns that crosscut an artifact's dominant decomposition or base modules derived from the dominant separation-of-concerns criterion, in the early stages of the software life cycle. Identifying and managing early aspects helps in improving modularity in the requirements and architecture design and to detect conflicting concerns early, thus resolving trade-offs. Besides, identifying aspects at one stage provides benefits downstream. Knowledge of requirements-level aspects helps architects in designing a better systems. Similarly, knowing architecture-level aspects helps produce a better implementation. Early aspects can measure development activities and many find their way into the code as traditional implementation aspects. Identifying early aspects across phases can increase the consistency of requirements and architecture designs with each other and provides a rationale and traceability for aspects across life-cycle activities. INSET: Dominant Decomposition in Early Software Development..