give me an example of a system that the software process models(waterfall model,V-model)can't be applied to it
828995
How about the universe? It is a system but you can't define the user requirements, thoroughly test it, build it, or even maintain it. However it is a system. A chaotic one, but still a system.\n\nIf you are talking software systems, then there are none. The models serve as a methodology for building systems so hence they apply to all systems. Anything built not using a methodology doesn't work and is not a system.\n\nLets say for instance that you sat at your computer and with no requirements from anyone, started tinkering on a project. Lets say you build a button, then jump over to write a line of code, to then jump over to its documentation... all being unrelated.\n\nNow this project is finished and doesn't work of course because it doesn't meet any requirements or even compile. Lets keep going like this and assume that eventually it starts working for some unknown reason. Now that it works it is a system because its parts work together to achieve a goal.\n\nYou could then apply a model to it, you had some requirements (because it has a purpose it is now achieving by working), it has a design (because it has parts working together and not randomly), you constructed it (because it is now come into being), you tested it (because now you know it works) and can be maintained (since it is now working and could continue working if you put more work into it).\n\nThe methodologies you mention outline a process of making a system so theoretically all systems conform to this process. Now if you didn't do them in order, so what? At the end you still went through the phases because you have a working product.\n\nAt least that is my take on it. If you are talking about any system though, I will stick to the universe.\n\nSee you later, testing Saturn.
1046915
The waterfall model is one in which each activity (analysis, design, implementation etc) is done once only in the development lifecycle.  Analysis spills into design, design into implementation and so on.  The problem with this style of development is that it doesn't cater very well to requirements change and the customer isn't provided with many opportunities for feedback before the deployment of the software near the end of development.\n\nThese days many software development teams prefer an approach that is both iterative and incremental - the system is built in stages over a series of smaller development cycles with all development activities occurring in each cycle and each cycle culminating in a release of the software to the customer.\n\nOften the riskier elements of a project are tackled in the earlier iterations, this is a risk mitigation strategy that works by exposing problems early while there's still time and resources to do something about them.\n\nCheers\nAdam
874242
will \nin the design approach you develope two main type of models \n\nthe static one that cant be changed such as water fall one \n\ndynamic that can be changed in the development time such as the errative one
66937
Perhaps decentralised software (e.g. programs that you use through your browser and therefore don't install locally). A good example of this is at [1].
312722
In my eyes nothing (it's by Microsoft) try out Java and JSP http://www.sun.com
106599
i. JDK - you can download this from java.sun.com \nii. Java IDE - examples are JDeveloper by oracle, JBuilder by borland, and Netbeans.
794890
language should have never been used for specifying JS vs VB or setting versions.\n\ntype is correct... language worked, but does not validate and is just OLD!
810080
something is wrong with your software
633705
Here is a complete definition with details...Too much info to type it all in here...\nhttp://en.wikipedia.org/wiki/Software_development
1152865
This is a very difficult question to really answer correctly. According to Godel's incompleteness theorem, a system is either complete or inconsistent. Although Godel proved it for the natural numbers, i have taken the liberty of using it as an analogy for software systems.\n\nA practical way to proceed is to test throughout the life cycle and to correct errors. As the software gets used and errors get fixed, (without introducing new errors), it becomes more reliable. The existence of various software environments (different operating systems, transaction monitors, database systems, interfaces to other applications and services, etc.) complicates matters. Particlarly when you have little knowledge and/or control over the environmental systems and software.\n\nSo what to do about the initial and subsequent releases. One way is to classify errors into severe, medium and minor. The classification depends on the application and impact of the application. Then have a release policy depending on the number and type of errors detected in testing.\n\nTo illustrate, consider the following applications:\n\nreal time flight control software for a passenger aircraft, passenger reservation software for airlines or trains, on-line stock trading software, word processing software, chat and email software.\n\nClearly the societal impact of errors in the above applications differs considerably.\n\nSome organizations also use quantitative models to predict residual-error distributions based on on-going test results.\n\nTesting, maintenance and support are part of the software life cycle and i think its very difficult to say "i've tested enough", simply because it's difficult to define "enough".\n\nTo build and maintain good software you need good requirements and analysis, good design which is maintainable and testable, good practices, good tools, good environments, good infrastructure, good communication and most of all good people.
265421
Here is a url to a very large site with more then you'll\never need. All free. Check it out.\nhttp://www.freeprogrammingresources.com/vbtutor.html
1150721
you can develope software in many ways.\nhttp://en.wikipedia.org/wiki/Software_development_model
1057610
Great little PDF here for you..\n\nhttp://www.oracle.com/technology/sample_code/tutorials/jsp20/files/jsp2.pdf
1182636
go to a template web site - dont steal other people's work. Thats not cool. Visual Studio? You need an upgrade!
450430
no microsoft doesn't allow you to take crap you make for other OS's and try to put it for windows you have to take the time and rewrite every bit of your code.
1052280
Try here: http://fvs.sourceforge.net/
659157
Its mainly for Webapplications,\n\nSo COBRA, DCOM, and RPC are component based models that are very important for software engineers... \n\nLook them up in the Java sun website..\nhttp://java.sun.com