40 – 20 – 40 rule in software engineering
There exists the Computer Aided Software Engineering (CASE) tools that are majorly important for implementing applications and maintaining them in relation to their functionality. Britannica defines CASE as the “use of computers in designing sophisticated tools to aid the software engineer and to automate the software development process as much as possible. CASE tools can be used for simple operations, such as routine coding from an appropriately detailed design in a specific programming language, or for more complex tasks, such as incorporating an expert system to enforce design rules and eliminate software defects and redundancies before the coding phase.” For software engineering application development, there is a rule as: 40-20-40. It can be explained as follows:
- 40% of the development task work project is applied for the Software Requirements Specifications (SRS), the business analysis and the design phase.
- 20% for the coding part, and
- 40% for the quality control engineering testing phase.
Learn Saylor website link CASE with Change Management in organizations. Working now with intelligent assistive tools in the software field, CASE tools will be related to the ability of the tool to recognize reusable analysis and design fragments, rather than humans to recognize reusable code fragments. Intelligent options will be included to detect feature and function similarities across applications. “Very intelligent CASE will be able to recognize a design fragment, logically link to the base definition of the reused item, and use already operational code modules. This level of intelligent CASE that could manage the use of reusable code may surface in our lifetimes, but not soon.”
Know more and image courtesy of https://clutch.co/developers/resources/how-to-hire-successful-software-development-team
