Getting Development Software Done on Time

2184 Words5 Pages

1. Introduction
Getting software development done on time, within budget and that covers all functional and non-functional requirements specified have been difficult and challenge (Darville and Zhang, 2012). In addition, Development effort, cost for developing an application and delivery on time are substantially high in producing complex systems (Ionita and Hammer et al., 2002). In order to evaluate the quality of the system against the business requirement, methods and tools are playing important role to support architects and the developers in evaluation process (Ionita and Hammer et al., 2002). Developing and maintaining a complex and highly featured systems needs making a sequence of architecture design decisions (Kazman and Asundi et al., 2002).
Moreover, the issue occurs in the application development is that business requirement is not clear enough and poorly specified non-functional requirement. Hence software architecture designs fail to support the business needs efficiently (Darville and Zhang, 2012). Architecture has to be designed such that architecture should reflect all Quality Attributes (QAs) (such that usability, performance, modifiability, security etc.) and business objectives (Lee and Kang et al., 2009, pp. 453--475).

Ionita and Hammer et al.,(2002) stated the currently available software architecture methods for analysis the software architecture quality are SAAM - Software Architecture Analysis Method, ATAM - Architecture Trade-off Analysis Method, CBAM - Cost Benefit Analysis Method, ALMA - Architecture Level Modifiability Analysis, FAAM - Family–Architecture Analysis Method (Ionita and Hammer et al., 2002)
ATAM and CBAM are widely used architecture evolution method.[4] ATAM is for assessing Quality At...

... middle of paper ...

... calculated by current and desire responses with expected through interpolation.

In step 7 following formula used to calculate total benefit. Sum of the benefit that falls to each scenario, normalized by weight of the scenarios.
Each Architectural strategy (i), benefit which we calculated B and weight of Scenario j.
Bi = ∑( bi, j × Wj ) j This “delta utility” is computed as follows: bi,j = Uexpected - Ucurrent, minus the utility value of current with expected

In step 8 estimation of cost was done based on experience for each scenario. Then ROI has been calculated for each Architectural strategy with the result of estimation. Each Architectural strategy ranked using ROI.
The ROI value ratio calculates as follows,

Total benefit = Bi
Cost = Ci

ROI, Ri= Bi / Ci

Iteration went on the same CBAM process again . In that team were discussed various risks and

Open Document