No, I do not mean there is run-time display sensitivity for input time. I am asking about any known features which used to describe the alleged difficulty in developing and maintaining a given program. So far, I've only heard people in terms of lines of code. I have been asked about the count of my projects during the interview also. But I think this feature alone is very confusing. For example, there are projects for which you can add codes / features and it is not necessary that functionality is largely free due to complexity. There are also projects with very long data transport pipelines, where small changes in one stage of the pipeline can make huge changes in every second phase of that pipeline. Other examples of complexity: When the program contains predictive algorithms of NP-hard problems, mathematical accuracy, critical performance, complete stability, etc. are required. Basically I need to give people the idea of the complexity of the same project, as is the "mainstream contrary" desktop software projects are a standard term for this respect?
I am told that the work point is "second best" to use for complexity on LOC (Mainly because it is one of the most used under the LoC and is easy to understand and understand, but then it is for estimation and may not apply to you) You can also try to look at the feature points Or Object Point
Comments
Post a Comment