Tag Archives: John Mylopoulos

Design Requirements Engineering: A Ten-Year Perspective: Design Requirements Workshop, Cleveland, OH, USA, June 3-6, 2007, Revised and Invited Papers (Lecture Notes in Business Information Processing) (by William N. Robinson, John Mylopoulos, Pericles Loucopoulos, Kalle Lyytinen)


Author(s): William N. Robinson, John Mylopoulos, Pericles Loucopoulos, Kalle Lyytinen

Publisher: Springer
Publish date: 2009-01-20
ISBN-10: 3540929657
ISBN-13: 9783540929659
Language: English
Description:
Since its inception in 1968, software engineering has undergone
numerous changes. In the early years, software development was
organized using the waterfall model, where the focus of
requirements engineering was on a frozen requirements document,
which formed the basis of the subsequent design and
implementation process. Since then, a lot has changed: software
has to be developed faster, in larger and distributed teams, for
pervasive as well as large-scale applications, with more
flexibility, and with ongoing maintenance and quick release
cycles.

What do these ongoing developments and changes imply for the
future of… more…

Read Source: Design Requirements Engineering: A Ten-Year Perspective: Design Requirements Workshop, Cleveland, OH, USA, June 3-6, 2007, Revised and Invited Papers (Lecture Notes in Business Information Processing) (by William N. Robinson, John Mylopoulos, Pericles Loucopoulos, Kalle Lyytinen)»

Design Requirements Engineering: A Ten-Year Perspective: Design Requirements Workshop, Cleveland, OH, USA, June 3-6, 2007, Revised and Invited Papers (Lecture Notes in Business Information Processing) (by William N. Robinson, John Mylopoulos, Pericles Loucopoulos, Kalle Lyytinen)


Author(s): William N. Robinson, John Mylopoulos, Pericles Loucopoulos, Kalle Lyytinen

Publisher: Springer
Publish date: 2009-01-20
ISBN-10: 3540929657
ISBN-13: 9783540929659
Language: English
Description:
Since its inception in 1968, software engineering has undergone
numerous changes. In the early years, software development was
organized using the waterfall model, where the focus of
requirements engineering was on a frozen requirements document,
which formed the basis of the subsequent design and
implementation process. Since then, a lot has changed: software
has to be developed faster, in larger and distributed teams, for
pervasive as well as large-scale applications, with more
flexibility, and with ongoing maintenance and quick release
cycles.

What do these ongoing developments and changes imply for the
future of… more…

Read Source: Design Requirements Engineering: A Ten-Year Perspective: Design Requirements Workshop, Cleveland, OH, USA, June 3-6, 2007, Revised and Invited Papers (Lecture Notes in Business Information Processing) (by William N. Robinson, John Mylopoulos, Pericles Loucopoulos, Kalle Lyytinen)»