By using our site, you agree to our collection of information through the use of cookies. To learn more, view our Privacy Policy. To browse Academia. Log in with Facebook Log in with Google. Remember me on this computer. Enter the email address you signed up with and we'll email you a reset link. Need an account? Click here to sign up. Download Free PDF. Chapter 3 Research Methodology. Nomy Espino. A short summary of this paper.
Download Download PDF. Translate PDF. Chapter 3 Research Methodology 3. It is a systematic way of accomplishing certain tasks and is defined as a collection of procedures, techniques, tools and documentation aids that helps a software developer to speed up and simplify the software development process Pressman, In this research, a combination of methodologies was used.
This chapter describes the methodology for this dissertation and the methodology that is used for system development. In addition, it defines the system development life cycle SDLC for developing the system.
From the analysis study, understanding of the literature reviewed and analysis of questionnaires, will lead the initial requirements for the system. Evolutionary prototype is used as methodology for SDLC. Once the initial requirements are ready, the next step is to design the system, followed by coding and testing.
Can the system help management apply the concept of decentralization in decision making? Is the system flexible in managing a variable number of head offices and stores? Is the system able to manage product inventory for each store and define which product has reached to the reorder point?
Is the system able to find which supplier should supply a product for a store? Are the customers able to buy from the online shop in a convenient way? Therefore, this research covers to two types of e-commerce, B2C and B2B e- commerce. The features of the four systems have been summarized and can be seen in the table 2. The structures of the questionnaires are designed to capture data about companies that have online purchasing system, and customers who buy from an online shop.
The prototype is normally discarded though sometimes the code may be reused Davis et al. The software process begins with a concept document and progresses in cycles to coding of individual programs in the spiral model. Each cycle involves the same sequence of steps; of determining objectives, alternatives and constraints that resolve risks by the use of prototypes, simulations etc. The spiral model embeds prototypes for risk resolution in the process of software development.
As the organisation surrounding the system evolves, new requirements emerge. The implementation of a new system can also transform the usage context and therefore new requirements arise Floyd, The evolutionary prototyping approach results in the gradual development of systems and allows for, or adapts to, changes that take place within an organisation as a result of either the operationalisation of the system, or externally induced changes to the organisation Ince and Hekmatpour, In contexts of high uncertainty and unlike contexts with high certainty where waterfall models are employed , the evolutionary prototyping approach dynamically responds to changes in user needs and accommodates subsequent unpredictable changes in requirements, as the development process progresses Pape and Thoresen, Floyd identifies incremental development and evolutionary system development as two distinct approaches that employ prototypes.
During incremental development the system evolves gradually in partial increments against the backdrop of an overall long range development strategy. The fundamental difference between evolutionary development and incremental development is in system design; while software design evolves in evolutionary development, there are no changes to the design during incremental development Ince and Hekmatpour, Initial development, however, starts in an area where the requirements are known.
The iterative enhancement approach and the incremental development approach are closely related approaches to prototyping though here we clarify the differences. A practical approach to the problem is to start with a simple initial subset of the problem and iteratively enhance existing versions until a full system is implemented.
At each step of the process, not only extensions but also design modifications can be made. In fact, each step can make use of stepwise refinement in a more effective way as the system becomes better understood through the iterative process. Incremental development is a method in which a partial system is constructed from an overall system design.
Functionality and increased performance are slowly added to the partial system. Each version adds a part of the original design Ince and Hekmatpour, The system is deliberately built in a manner that facilitates the incorporation of additional requirements.
Evolutionary system development, is adopted in a context of a dynamic and changing environment. This type of development necessities a sequence of cycles of re- design, re- implementation and re- evaluation without any attempt to capture a complete set of requirements in advance Floyd, A prototype of partially known requirements is implemented first.
When users use the prototype a fuller understanding of the requirements is gained. New requirements are then implemented. The final system evolves in a continuous fashion Davis et al. Each successive prototype explores new user needs, and refines functionality that has already been implemented. While the sequence of prototypes are perhaps converging approximations towards a moving target they may never hit it, as the requirements are subject to continual change Tate, Therefore, the system is always in continuous evolution and there is no such distinct phase as maintenance.
Floyd, We have provided a framework within which the terms relating to prototyping can be properly located. The framework integrates prototypes, the prototyping process and approaches to software development that use prototyping. Software development approaches use prototyping and prototypes for a variety of different purposes.
Essentially prototypes are used for three main purposes in software development - exploration, experimentation and evolution. Exploratory approaches use prototypes for finding requirements early and to make complete users incomplete knowledge of their requirements. Experimental approaches use prototypes to investigate certain kinds of feasibilities or possibilities within the process of development. The feasibility investigated may be technical, increasing efficiency, etc.
The evolutionary approaches use the philosophy of the prototyping process itself and employ it as the methodology for the software development process as a whole.
Incremental development and evolutionary system development can both be viewed as types of evolutionary software development approaches. Whilst the distinctions made here are necessarily for classificatory purposes, in practice it has been found that one or more kinds of prototypes may be employed within a particular prototyping development approach as demonstrated by the case studies of Lichter et al. The evolutionary system development approach produces pilot prototypes and the experimental approach at times uses breadboard prototypes.
Finally, the boundaries between experimentation and exploration are blurred and evolution may initially include both experimentation and exploration Floyd, Royce, W. The prototype converts industrial ideas to concrete realities. A highly trained professional team will adopt your entrepreneur idea specifications and sketch your ideas using the latest CAD technology.
Next, with the help of computer simulation, these CAD drawings are transformed into a prototype which is an exact copy of the final product. Prototyping helps you get an accurate and complete working model of innovation, adjust the weight of several different options, adjust them, and ultimately create the perfect design. In evolutionary prototyping, the concept of the system will be developed as the project progresses. First of all, we will develop the most visual aspect of the system.
You present a portion of the system to the customer and continue to develop prototypes based on the feedback received. It is may be best suited for business systems where developers can interact frequently and informally with end users.
However, it is suitable for commercial, shrink wrap, and system projects as long as end-user involvement is obtained. Communication with users of these projects is generally more structured and formal.
If evolved prototyping does not provide more control than is necessary or if you already know what the system should do, you can use evolutionary delivery or gradual delivery instead. The throw-away prototype is cheap, fast ones, which is designed to model an idea or feature. They are commonly used in early phases of design when a large number of ideas are still being considered. The throw-away prototype sounds like what it is.
0コメント