Agile philosophy is to deliver working versions of the software in short iterations, then update the software according to customers' feedback. Applying this philosophy will help to overcome the problems faced in traditional development. By welcoming changes and involving the customer when planning for iteration helps to improve the quality of the product, enables faster development, and in the end, users will have just the system they need. This paper also discusses some of the potential risk and constraints in agile adoption.
General TermsAgile methodology.
Power consumption is the bottleneck of system performance. Power reduction has become an important issue in digital circuit design, especially for high performance portable devices (such as cell phones, PDAs, etc.). Many power reduction techniques have also been proposed from the system level down to the circuit level. High-speed computation has thus become the expected norm from the average user, instead of being the province of the few with access to a powerful mainframe. Power must be added to the portable unit, even when power is available in non-portable applications, the issue of low-power design is becoming critical. Thus, it is evident that methodologies for the design of high-throughput, low-power digital systems are needed. Techniques for low-power operation are shown in this paper, which use the lowest possible supply voltage coupled with architectural, logic style, circuit, and technology optimizations. The threshold voltages of the MTCMOS devices for both low and high Vth are constructed as the low threshold Vth is approximately 150 -200 mv whereas the high threshold Vth is managed by varying the thickness of the oxide Tox. Hence we are using different threshold voltages with minimum voltages and hence considered this project as ultra-low power designing.
Agile methodologies are at present widely used in industry. Many agile software development metrics are irrelevant to practitioners since they are dependent on the scope or content [Fenton and Neil, 2000]. Currently estimation is done by the team for each of the prioritized features [1] in order to commit to the number of features that can be implemented in each sprint. Each sprint is time-boxed; meaning the time to deliver is fixed. Risk in agile development is failing to deliver planned features in each sprint. There could be many reasons for not being able to deliver. Two of the reasons are discussed in this paper; one being incorrect time estimation and the other reason could be technical impediments. Actually the time taken to complete the task (feature implementation) depends on the proficiency of the development team and there has been no publication on estimation based on how and when to measure this. This is one of the gaps the research paper is trying to address. The scrum master assists the team in removing the impediments that obstructs the progress. In other words scrum master helps in facilitating productivity [2]. Hence, preparedness to resolve impediments as and when it arises is essential. This second risk is addressed by using semantic agents which is discussed in this paper.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.