concurrent model in software engineering

These are summarized by Nogueira and his colleagues :ĭespite the unquestionable benefits of evolutionary software processes, we have some concerns. Evolutionary process models were conceived to address these issues, and yet, as a general class of process models, they too have weaknesses. If a market window is missed, the software project itself may be meaningless. In many cases, time-to-market is the most important management requirement. I have already noted that modern computer software is characterized by continual change, by very tight time lines, and by an emphatic need for customer user satisfaction. Events generated at one point in the process network trigger transitions among the states. Each activity, action, or task on the network exists simultaneously with other activities, actions, or tasks. Rather than confining software engineering activities, actions, and tasks to a sequence of events, it defines a process network. If, however, the customer indicates that changes in requirements must be made, the modeling activity moves from the under development state into the awaiting changes state.Ĭoncurrent modeling is applicable to all types of software development and provides an accurate picture of the current state of a project. The modeling activity (which existed in the inactive state while initial communication was completed, now makes a transition into the under development state. All software engineering activities exist concurrently but reside in different states.įor example, early in a project the communication activity (not shown in the figure) has completed its first iteration and exists in the awaiting changes state. Similarly, other activities, actions, or tasks (e.g., communication or construction) can be represented in an analogous manner. The activity modeling may be in any one of the states12 noted at any given time. For example, the modeling activity defined for the spiral model is accomplished by invoking one or more of the following software engineering actions: prototyping, analysis, and design.įigure 1 provides a schematic representation of one software engineering activity within the modeling activity using a concurrent modeling approach. The concurrent development model, sometimes called concurrent engineering, allows a software team to represent iterative and concurrent elements of any of the process models described in this chapter.

Concurrent model in software engineering