All activities exist concurrently but reside in different states. Similarly, other activities (e.g., design or customer communication) can be represented in an analogous manner. The activity-analysis-may be in any one of the states noted at any given time. For example, the engineering activity defined for the spiral model is accomplished by invoking the following tasks: prototyping and/or analysis modeling, requirements specification, and design. The concurrent process model can be represented schematically as a series of major technical activities, tasks, and their associated states. is driven by user needs, management decisions, and review results. Most software development process models are driven by time the later it is, the later in the development process you are. Kellner's more recent work uses statecharts to represent the concurrent relationship existent among activities associated with a specific event (e.g., a requirements change during late development), but fails to capture the richness of concurrency that exists across all software development and management activities in the project. Software engineering process models by Humphrey and Kellner have shown the concurrency that exists for activities occurring during any one phase.
personnel are writing requirements, designing, coding, testing, and integration testing.
project is in the coding phase, there are personnel on the project involved in activities typically associated with many phases of development simultaneously. These are examples of trying to track extremely complex sets of activities using overly simple models. The concurrent development model, sometimes called concurrent engineering, has been described in the following manner by Davis and Sitaram : Project managers who track project status in terms of the major phases have no idea of the status of their projects. It requires to remember the status of the different activities. It needs better communication between the team members. It provides an accurate picture of the current state of a project.ĭisadvantages of the concurrent development model
It gives immediate feedback from testing. This model is applicable to all types of software development processes. Advantages of the concurrent development model The concurrent process model activities moving from one state to another state If the customer specifies the change in the requirement, then the modeling activity moves from the under development state into the awaiting change state. The modeling activity completed its initial communication and then go to the underdevelopment state. The communication activity has completed in the first iteration and exits in the awaiting changes state. The concurrent development model is called as concurrent model. Concurrent Process Models The concurrent development model
0 kommentar(er)
