Introduction The word system can be traced to a Greek word that suggests combination of various features or properties (Dixit & Kumar 2007). Based on this a system is thought of as a combination between related functioning components or units with the purpose of achieving a single goal (Shelly & Rosenblatt 2011). A component of a system is single irreducible part that allows for changes to be made in a modular fashion (Dixit & Kumar 2007). Due to this nature of systems changes can be made to the various components with little or no effect on the entire system. In this report, the discussion will involve the considerations that prevail in the design and development of a computerized ordering system. Agile Systems and Software Development Cycle As it has been mentioned in the previous section a system is composed of components. The main objective of systems analysis and design is to gain an understanding of how the system works and take steps to improve this system. The process of system analysis and design typically involves six distinct stages namely; preliminary investigation, requirements analysis, design, coding and development, implementation and maintenance (Dixit & Kumar 2007). For the production of a suitable system these steps can be followed to completion using a variety of methodologies. The traditional approaches to this have been noted to be cumbersome and often hamper the speedy completion of a software project (Dixit & Kumar 2007). For this and other similar reasons this project was undertaken using an alternative approach to software development. This approach which is categorized under Agile methodologies was chosen due to the ability to counter problems inherent in traditional approaches to software design and development (Caine 2011). The there are three key principles that are used in Agile methodologies that were found suitable for this project. First is the fact that Agile methodologies focus on adaptive rather than predictive procedures (Dixit and Kumar 2007). Traditional methods are especially poor at this due to their sequential nature thus making it difficult to adapt to changes in the requirements. In addition to that Agile methodologies also focus on people rather than roles. This allows for the creation of the most suitable solution for the users. Lastly Agile methodologies focus on self adaptive processes (Dixit & Kumar 2007). Based on these specific traits it was observed that Agile methods were more likely to be useful in achieving the desired objectives. Software Selection The decision to utilize an Agile approach to the development of this software was also based on several considerations that were made after the design stage. It should be noted that during the design stage the development team makes decisions on how the new system will operate (Denis, Wixom & Roth 2009). The design stage comes after analysis which involves identification of business needs the software to accomplish. Through the use of various tools during the design stage the development team will create a blue print of the desired system (Denis, Wixom & Roth 2009). Upon completion of the blue print the team then makes a decision on what software to use in the development of the software. (See Appendix A) One approach that can be adopted to acquiring the relevant software is the purchase of already completed products available in