The Infona portal uses cookies, i.e. strings of text saved by a browser on the user's device. The portal can access those files and use them to remember the user's data, such as their chosen settings (screen view, interface language, etc.), or their login data. By using the Infona portal the user accepts automatic saving and using this information for portal operation purposes. More information on the subject can be found in the Privacy Policy and Terms of Service. By closing this window the user confirms that they have read the information on cookie usage, and they accept the privacy policy and the way cookies are used by the portal. You can change the cookie settings in your browser.
The visualization of system requirements in a domain-independent, transparent and flexible manner with respect to the progress of the project for all project stakeholders is an area that still needs attention. There are several means to visualize requirements stored in a database, but few ways in which the status of a requirement — such as at what stage of realization it is at a given point in time,...
Changing requirements are a characteristic of all projects today, and the subject of requirements volatility has received attention in both research and industry. The inherent inflexibility of traditional, plan-driven development methods, such as the V-model, in adapting to changes in requirements at various phases of the project has given rise to several agile approaches. In practice, however, globally...
Although current trends in software development methodologies allow for changes to requirements at various phases of development, modifying the existing system design to reflect these changes is often architecturally challenging. In many real world instances, seemingly simple updates to user or functional requirements often have a significant impact on several dimensions of the overall system architecture...
Distributing the various phases of system development across multiple locations has posed several requirements-related challenges. These challenges directly and indirectly arise from the lack of opportunities for face to face communication and collaboration between project team members, while trying to obtain clarity on requirements. These concerns are more pronounced when the constituent sub-systems...
High level requirements that describe the various objectives to be met by a system may not always be fully comprehensible, especially when expressed in textual form. The possibilities of misinterpreting requirements, and missing out on grasping the contextual information associated with requirements increase with several factors. Some of these causes include the volume of interaction between related...
The complexities associated with managing requirements for building systems within systems, interconnected and networked systems, and systems communicating with each other across many distributed types of environments has long since been recognized. However, dealing with the process of requirements engineering for these types of systems is still a serious concern for most complex projects, given the...
Set the date range to filter the displayed results. You can set a starting date, ending date or both. You can enter the dates manually or choose them from the calendar.