There is many software development methodologies exist that is used to control the process of developing a software system. No exact system was found which could help the software engineers for selection of best software development methodology. This paper present the framework of expert system combined with Likert scale. With the help of Likert scale we create a rule based model and assign some weighted score to each methodology and develop a tool named as ModSet which will help the software engineers to select an appropriate development methodology that may increase the probability of system success.
Keywords: Software Development Methodology, Expert System, Likert Scale
1. Introduction
The problem of selecting a suitable software development methodology has been addressed in different way by many researchers but there is no proper framework has developed. This paper extends prior work by considering the expert system with the likert scale to selecting best software development methodology.
The goal of developing a rule based expert system is to come up with result that would help to establish which software development methodology is particularly suitable for a particular project. In other words obtaining one clear answer was not the aim, but rather obtaining guidance in choosing from a known set of methodologies. The model selected should suit the characteristics of a given project should correspond to the criteria set out in the selection of methodology, the criteria should be stored in knowledge base of the system. Then to obtain information about a suitable model, the user of such a program would have to determine the characteristics of their project by answering a set of questions asked by the system.
1.1 Software Develo...
... middle of paper ...
...ologies. The next block represents selection criteria, final score, dynamic priority allocation and results. Expect the result block all the blocks have check boxes and the priorities can be assigned between 0 and 10. After making the entire selections “Decide” button is pressed and the result is displayed in the result text box giving the model selected. “View Heuristic Report” button gives the entire report with situational analysis.
6. Conclusion and Future Work
This study proposed a rule base expert system combined with Likert scale measurement that will become a base for the software engineers in the selection of appropriate software development methodology for the project. In this paper we provide a tool that will help in the selection process of development methodology. The future work will include more development methodologies and more selection parameters.
The project is going I am working is almost in the finish stage it is going into the production phase means getting to the live so that the users can able to use the application. After the developing the total code it will go to the testing phase where the testers will check the code is working properly without any errors actually the testers task is to check the code and submit to the developers if they found any errors or mistakes or else they will send the code to the production phase to deploy in the server to check the application.
The Software Development Life Cycle is seldom used at my place of work. Unfortunately, recent developments in its use are deemed confidential. Due to this fact, this paper will examine in general terms one of the projects we are undertaking right now while at the same time attempting to maintain our confidentiality.
SDLC( Software Development Life Cycle) , is a process used by the software industry to design, develop and test high quality software .The SDLC aim to produce good quality software that meets or exceeds the user’s expectation and reaches completion within time and cost estimates.
1. FRAMEWORK. I planned the framework and design, with the final version ending up more than 5,000 lines. I then designed layers to be placed on the framework as sample implementations. Finally, I tested the system for efficiency by asking all my friends to visit the application and by stress testing it. I tried CLIPS, a LISP-like rule-based expert system by NASA. I realized that it was too cumbersome to program rule structures in it. I also realized it was slow; query executions averaged around three secon...
While developing a software many complex activities are required which in turn have dependencies along them. Large software projects require the involvement of programmers, documentation specialists, program managers, architects, database analysts, system analysts, , and trainers and last but not the least testers. Along with their independent responsibilities these persons are also responsible to maintain and keep a check on the software system quality as well.
The authors of this article begin by listing the main problems that are associated with large software requirement processes and then summarize how StakeRare will alleviate these through social networks and collaborative filtering in the elicitation process. This is a significant idea in utilizing technology in the software engineering process that have become more widely used since the creation of the more dated requirements elicitation methods. Large scale software projects are more likely to have stakeholders that are more spread out geographically and organizationally. This is due to organizations
What technique or strategy would you apply to evaluate the effectiveness of your development processes?
This article discuss about a requirement elicitation process in the context of why, what, who, when and how. First, elaborating why should be there a requirement elicitation process, secondly what sort of requirements and types need to be defined at various levels, who are the stakeholders and how to get them involved in this process, When the requirement elicitation process should happen during the Software development life cycle and Finally how to analysis, specifying , validate requirements during requirement validation process by using various techniques .
This paper has the intention to explain what Rational Unified Process (RUP) is like an IBM product and a CASE tool. After is explained what phases it has, what are the most common extensions thus what are its workflows more used. The Rational Unified Process (RUP) is a software design method created by the Rational Software Corporation and now is part of IBM developer software. This paper describes how to deploy software effectively. The Rational Unified Process (RUP) use commercially proven techniques, and is a heavy weight process, and hence particularly applicable to larger software development teams working on large projects.
The purpose of the new system that I will develop is to improve on the
This Chapter presented a description of Knowledge Acquisition and Knowledge Representation in Expert Systems. This chapter will explain the knowledge Acquisition and Representation methods, production rules and frames. The section below explains the concept of Production rule, their training and learning. Also this chapter discusses methods of Knowledge Acquisition and Knowledge Representation.
Every methodology has pros and cons, wherefore we have to compare various of methodologies and select one of the best and suitable for the particular project. According to the information that we have gathered from the Lotuskrish and come out with a methodology to be used in the project.
e defined as the ability of a computer to reason, to learn, to strive for self-improvement, and to simulate human sensory capabilities. The knowledge base they rely on is the accumulation of knowledge of a number of experts (the domain expert) on the particular subject. Coupled with an expert system shell, which is the software used to interrogate the knowledge base, the knowledge base can be put to work logically recommending alternatives to current problems. Expert systems have been developed for subjects such as medical diagnosis, oil exploration, financial planning, taxation return preparation, chemical analysis, surgery, weather prediction, computer repair, nuclear power plant operation, newspaper layout, interpreting government regulation, and troubleshooting computer systems configurations (eg.
Most of the software development projects change just during the development is in process. This is the reason that agile methodology is best for these projects. There is a room for change in them. Software developers follow these methods and this is the reason that they have further modified these methods according to the different types of projects they confront in their development time.
behind in these field compared to resourceful languages in implementation of these techniques. Rulebased methods are