Software myths

There are number of myths associated with the software developing processes. Some of them are really affect the way, in which the software development takes place. Following are some myths and their applicability to find out the standers of the software development process.

what is software myths, software myths
 Software are easy to change
- It is true that software source code file is easy to edit but it is much difficult to say that software are easy to change.
- It is easy to alter the source code file of any software but it is very difficult to change the software without introducing  the error.
- Every changes made in software may leads to compute system re-verified and  it is not possible to complete system re-verified after every changes, this causes lot of more errors in system.

Computer provide the greater reliability than the device changed
- It is true that software does not fail in traditional sense.
- There is no limit to how many times your piece of code is executed, it wears out.
- Back if we see, there are lots of manually working human errors, now its software errors or computerized errors.

Testing software can remove all the errors
- Testing shows the presence of errors only, not the absence of errors.
- Our aim is to be design effective testcases in order to find out the maximum possible errors.
- The more we test, the more we are confident about our software.

 Software can work right the first time
- It is fictitious that the software can work right at first time.

Software with more feature is the better software
- It is the opposite of truth that the software with more feature is better software
- In fact having  more features create the software more error handling.
- If the software may work at only one operation then there may be less chances of errors rather than having more features software.

Addition of more software process engineers will make up the delay
- This is almost opposite of the truth. In most of the cases, addition of more software engineers will further delay the process.

 


Comments

Post a Comment

Popular posts from this blog

Articulation point of graph / Biconnected components and DFS traversal

Image
In the connected graph G, a vertex V is said to be an articulation point if and only if the deletion of vertex V disconnects the graph into two or more non - empty components. For more precisely satisfy this concept, consider the following connected graph   In this graph, basically vertex 2 is an articulation point, as if we delete the vertex, it will disconnects the graph into two non - empty component.
Read more

Requirement Engineering

Image
- Requirement engineering produces one large document, written in natural language, contain a description of what the system will do without describing how will it do. - Requirement engineering is the discipline application of proven principles, methods, tools and notations to describe the proposed system’s intended behavior and its associated constraints. - This process contains the four steps as shown in fig i] Requirement Elicitation This is also known as gathering of requirements. Here the requirements are identified with the help of customer and existing system process are available. ii] Requirement Analysis Requirement analysis     are start with requirement elicitation. Here the requirements are analysis in order to identify inconsistencies, defects, omission etc. iii] Requirement Documentation This is the end product of requirement elicitation and analysis. The documentation is very important as it is the foundation of the software. ...
Read more

Brief shortnote on Requirement elicitation and requirement analysis

Image
- Requirement elicitation means gathering of requirements. - Perhaps it is most difficult, critical, most error prone and most communication intensive aspect of software development. - The most important goal of software requirement engineering is to find out what the customer really wants. - The users need can be identify only by understanding expectation of the user from the developers. - Requirements are gathered by asking the question to user and writing down their answers and their exceptions of the software that how he want to use software. - Gathering the requirements of users is the most difficult part of the software development, because both developer and user have different mindset regarding the software. - Here, communication of both the parties are the most essential for software product. - There are number of requirement elicitation method. https://en.wikipedia.org/wiki/Requirements_elicitation   - Some people think that one methodology is a...
Read more