Software Development Process Assignment

DIT545 H14 – Software Processes Examination
Alexander Andreasson
Software Engineering and Management, Bachelor’s Programme
University of Gothenburg
Gothenburg, Sweden [e-mail] Abstract— As a process engineer for software development projects of the fictitious company OutOfTheBox Ltd. that has recently gained a new client, Superbanken AB, we are required to, with the help of a development team in which I will furthermore be aiding in the process of development efforts, monitoring progress and suggesting improvement before and after software product execution, create a new software to interface with the existing infrastructure of the client’s parent company, BigOldBank AB, and implement a system that conducts customer transactions

I will use the Incremental lifecycle model because it allows for an agile development approach which therefore permits changes and modifications to occur throughout the development process.
(1.2)A couple of advantages of this lifecycle are, compared to my second choice – the itera1tive lifecycle, first, it builds an initial feature (feature 1) completely and repeats this process for the next set of features. Thus, it allows for concentrated focus and effort from team, resulting in fast and early delivery of working software during early stages of development [1].
This advantage relates to the software development scenario (SDS) because the main goals for the project requires transactions through two critical features and rapid delivery of features.
It is favorable over the iterative approach because major features and requirements are identified and the software must be pushed out quickly, thus a low fidelity build of the whole system is unnecessary which would take more time to complete, and more if changes and software related problems

The second (i2), will allow results changes to be made after system release. The change requests will be handled using: Surveys created by developers for customers for both instances, Q & A sessions by developers for both instanced, think aloud sessions for i2, request changes will furthermore, be handled down into two sections: customer and developer support. Figure 1.0 depicts that a customer is able to request a change into a batch of other stored requests. Customer support checks if the CR (customer request) can be solved by them otherwise it is registered into developer support. Here, the request is analyzed, an estimation of the advantages and disadvantages of trying to solve the problem is created, the software is then changed according to request, and finally, the software is tested. If the process fails, it repeats the “modification” phase, else (the test passes) the CR is