Software Development Methodology Case Study

1105 Words 5 Pages

3.0 Introduction
Sanders et al. (2003) delineates that a methodology is the theory of how a research should be undertaken encompassing the theoretical and philosophical assumptions upon which research is based and the implications of the method(s) adopted.

This chapter gives a detailed summary of basis for data collection and the software development methodology adopted with prescribed steps for the research in the achieving of the project aim and objectives.

3.1 Software Development Methodology
To avoid software crisis, selecting the right software development methodology for the planning, analysing of the requirements, design, evaluation, implementation, testing and maintenance is crucial and critical
…show more content…
(Beaudoin-Lafon and Mackay, 2007)
Software prototyping in software development process involves the creation of working design model in order to understand, examine, review and test the viability and performance of the system in detail for future stages of the design that satisfies the needs of the users before the final design. At an early stage in the development process of the system, through prototypes the functionality of the system is better understood.
The purpose of the prototype is for better decisions for the success of the final design and implementation of the system in the examining of the design problems and evaluation of the best solutions through the identification of the most important open design questions. (Houde and Hill, 1997)
Prototyping which encompasses a set of stages allows for continuous removal of unwanted features and improving on the system by making necessary changes towards eventually achieving its goal.
As an approach to software development for the assessment of ideas and decisions, prototyping involves the preparation of immature versions in terms of functionality and quality. (Riddle,
…show more content…
In this phase, the available literatures and information about the existing system is to be analysed to ascertain the issues and the achievability of the project aims and objectives.

• Requirement Definition: The non-functional and functional requirements of the software system of the user in detail needs are to be defined through a thorough observation along analytically reviewing available literature materials for the collection of data.

• Specification (User Interface) Prototyping: The first prototype of the system is fabricated with the fundamental functions to assess whether it meets the requirement specification of the intended users. If the prototype does not meet the requirement specifications, the process goes through the requirement analysis and definition until all the needed conditions are met.

• Architecture and Component Design: The modelled prototype with the assessed feedback and updated resultant requirements specification is developed into a potential architectural interface design with its basic

Related Documents