PROJECT TITLE :

Contextualizing agile systems engineering

ABSTRACT:

Discussion regarding agility at intervals Systems Engineering is ongoing [9,10,thirteen] however there had been little discussion about the correct context for it. This proposed a classification theme for the proper context of the Agile Development Cycle that was identified to be the most principle of agile development. Prior work about the context of agile software development [5,7, 8] was taken as the basis. Interviews in system developing companies were used to analyze the differences between context of agile software and systems development (hardware systems). It had been found that the character of the system isn't only the most difference between the 2 domains however also the most driver for the right context of the Agile Development Cycle. In contrast to software, hardware systems that must be produced physically often are difficult to be developed in little cyclic steps. Only if prototyping, testing, and implementing changes will be done quickly and cheaply, this principle is feasible. The system ought to not be safety-vital additionally. Another requirement for feasibility is the willingness of client to support this kind of development. On the other hand, some factors were identified to drive the demand for agility, like market dynamism, level of innovation, and rate of change. Thus the context of Agile Systems Engineering was classified into the 2 dimensions: feasibility and demand. Some company examples got to explain the different things in this classification theme. By using the factors one company can be classified at intervals the theme. Thus we find if the Agile Development Cycle will be place into the correct context. For a situation where the Cycle is not feasible however agility is required it we tend to conjointly show how it might be applied partially.