IRMA-International.org: Creator of Knowledge
Information Resources Management Association
Advancing the Concepts & Practices of Information Resources Management in Modern Organizations

Analyses of Evolving Legacy Software into Secure Service-Oriented Software using Scrum and a Visual Model

Analyses of Evolving Legacy Software into Secure Service-Oriented Software using Scrum and a Visual Model
View Sample PDF
Author(s): Sam Chung (Institute of Technology, University of Washington, USA), Conrado Crompton (Institute of Technology, University of Washington, USA), Yan Bai (Institute of Technology, University of Washington, USA), Barbara Endicott-Popovsky (University of Washington, USA), Seung-Ho Baeg (Korea Institute of Industrial Technology, Korea)and Sangdeok Park (Korea Institute of Industrial Technology, Korea)
Copyright: 2014
Pages: 23
Source title: Software Design and Development: Concepts, Methodologies, Tools, and Applications
Source Author(s)/Editor(s): Information Resources Management Association (USA)
DOI: 10.4018/978-1-4666-4301-7.ch084

Purchase

View Analyses of Evolving Legacy Software into Secure Service-Oriented Software using Scrum and a Visual Model on the publisher's website for pricing and purchasing information.

Abstract

This chapter explores using service-oriented computing to reengineer non-secure legacy software applications to create new secure target applications. Two objectives of this chapter are: (1) to analyze the architectural changes required in order to adopt new web technologies and cope with resultant vulnerabilities in source code; and (2) to measure the level of effort required to modernize software by adopting new web technologies and adding security countermeasures. To meet these objectives, a model-driven Scrum for Service-Oriented Software Reengineering (mScrum4SOSR) methodology was chosen and applied to a reengineering project. Scrum is employed to manage the reengineering project, as well as to measure implementation effort related to the modernization process. Further, a re-documentation technique called 5W1H Re-Doc is used to re-document the non-secure software application at a high level of abstraction in order to help project participants comprehend what is needed to identify candidate services for service-oriented reengineering. Case studies with and without security features are created for different types of applications - a desktop graphical user interface, a web application, a web services application, a restful web services application, and an enterprise service bus application.

Related Content

Babita Srivastava. © 2024. 21 pages.
Sakuntala Rao, Shalini Chandra, Dhrupad Mathur. © 2024. 27 pages.
Satya Sekhar Venkata Gudimetla, Naveen Tirumalaraju. © 2024. 24 pages.
Neeta Baporikar. © 2024. 23 pages.
Shankar Subramanian Subramanian, Amritha Subhayan Krishnan, Arumugam Seetharaman. © 2024. 35 pages.
Charu Banga, Farhan Ujager. © 2024. 24 pages.
Munir Ahmad. © 2024. 27 pages.
Body Bottom