Going on-line on a shoestring: An experiment in concurrent development of requirements and architecture

A number of on-line applications were built for a small university using a micro-sized development team. Four ideas were tested during the project: the Twin Peaks development model, using fully functional prototypes in the requirements elicitation process, some core practices of Extreme Programming, and the use of open-source software in a production environment. Certain project management techniques and their application to a micro-sized development effort were also explored. These ideas and techniques proved effective in developing many significant Internet and networked applications in a short time and at very low cost

Using problem frames with distributed architectures: a case for cardinality on interfaces

Certain classes of problems amenable to description using Problem Frames, in particular ones intended to be implemented using a distributed architecture, can benefit by the addition of a cardinality specification on the domain interfaces. This paper presents an example of such a problem, demonstrates the need for relationship cardinality, and proposes a notation to represent cardinality on domain interfaces

Identifying Suitable Projects For Rapid Development: Some Proposed Selection Criteria

The use of rapid development techniques allows building high quality systems in short timeframes while reducing project costs and adding flexibility to the development process so it can be easily adapted to meet customer needs in a volatile market. In order to obtain the benefits of implementing rapid development methods, the development organization and the processes utilized need to be congruent with rapid development methodologies and techniques. A problem encountered by product development organizations is how to identify which projects are suitable for the rapid development approach. An extensive academic research about the implementation of rapid development techniques in Systems Development Life Cycle (SDLC) processes resulted in the identification of selection criteria for the determination of project suitability for rapid development methods. The selection criteria identified by this research are essential elements that must be present in every rapid development environment in order to obtain the benefits of implementing rapid development techniques

Exploring the requirements process for a complex, adaptive system in a high risk software development environment

This work ties together research from a number of different areas to show how the develop-ment of a complex adaptive system for an industrial company has a number of difficulties given the current state of the art. The INFER system which is a Complex Adaptive System (CAS) has a number of attributes which mean that current requirements and indeed develop-ment processes are not able to cope with them adequately. A CAS can be recognised by the fact that it consists of a number of agents acting together dynamically resulting in emergent behaviour. This emergent behaviour cannot be predicted and thus, along with other phenom-ena such as reaction to and with the environment and deciding the different responsibilities of the components means that the requirements process for such a system is a current research area. A retrospective case study is underway to capture the rich data available from the ex-periences of building such a syste

Requirements engineering practices: an empirical study

focus 2 I E E E S o f t w a r E P u b l i s h e d b y t h e I E E E C o m p u t e r S o c i e t y 0 7 4 0 -7 4 5 9 / 0 8 / $ 2 5 . 0 0 © 2 0 0 8 I E E E requirements and agility Agile Requirement

Multi-Agent Spiral Software Engineering: A Lakatosian Approach

This paper presents an epistemological approach for the development and validation of an original agent oriented software development methodology (see [Wautelet05a, Wautelet05b]). Agent orientation has been widely presented as a new modeling, design and programming paradigm that could be adopted to build systems mark to the determinant advantages it offers. This will be exposed and put into perspective in the paper through the Lakatosian approach. Spiral development (see [Boehm00a]) has become popular, especially through object-oriented software project development since it allows efficient software project management, continuous organizational modeling and requirements acquisition, early implementation, continuous testing and modularity, etc. The iterative nature of this requirements engineering process will be studied here through Herbert Simon's bounded rationality principle and Popper's knowledge growth principle but nuanced by Lakatos falsification principle criticism

Model and Technique over Software Requirement Prioritization

Requirement prioritization play a significant part in overcoming problems related to requirements and it use to increase customer satisfaction. Requirement prioritization is use to verify the correct functionality of product and guarantee that the software is built within the given constrains, like budget, cost, value, time and etc. Requirements prioritization reliant on the specific requirements of customer along with prediction of importance and cost of each requirements. The approaches proposed in modern days to prioritize requirements have not been widely used because of its complexity, its inconsistency and its time-consuming factor. This paper represents an analysis on obtainable prioritization techniques based on cost and benefit and drawbacks evaluation of requirements. This paper represents a new approach of requirement prioritization, which can be easily managed, implemented and used as decision-making device by decision maker for requirement prioritization. It also overcomes the drawback of existing requirement approaches. The results of newly proposed approach shows thatproposed model for requirement prioritization is simple and is useful for more refined critical decisions of prioritization, keeping in view the cost and benefit