Authors:
Yael Dubinsky
1
;
Orit Hazzan
1
;
David Talby
2
and
Arie Keren
2
Affiliations:
1
Technion – Israel Institute of Technology, Israel
;
2
MAMDAS – Software Development Unit, Israel
Keyword(s):
System analysis and design, Agile development, Project specifications, The system analyst role.
Related
Ontology
Subjects/Areas/Topics:
Enterprise Information Systems
;
Information Engineering Methodologies
;
Information Systems Analysis and Specification
;
Methodologies, Processes and Platforms
;
Model-Driven Software Development
;
Software Engineering
;
Systems Engineering
Abstract:
Agile software development methods mainly aim at increasing software quality by fostering customer collaboration and performing exhaustive testing. The introduction of Extreme Programming (XP) – the most common agile software development method – into an organization is accompanied with conceptual an organizational changes. These changes range from daily-life changes (e.g., sitting together and maintaining an informative project environment) and continue with changes on the management level (e.g., meeting and listening to the customer during the whole process and the concept of the whole team which means that all role holders are part of the team). This paper examines the process of transition to an agile development process in a large-scale software project in the Israeli Air Force as it is perceived from the system analysis and design perspective. Specifically, the project specifications of the agile team are compared with those of a team who continues working according to the prev
ious heavyweight method during the first half year of transition. Size and complexity measures are used as the basis of the comparison. In addition to the inspection of the specifications, the change in the role of the system analysts, as the system analysts conceive of it, is examined.
(More)