Abstract
Most published software development models present software engineering as a series of discrete phases. They often capture the "inevitable intertwining" of pairs of phases and they often capture the need to return to earlier phases when new information is ascertained. However, in actual software development projects, activities typically associated with multiple phases are performed concurrently. This paper presents a new model of the software development process that effectively captures the concurrency among activities that is in berent in all non-trivial software development. Statecharts are used to present the model.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
