Soft eng 1

Executable code
Program
Software
Software product
Software engineer
Collection of program
Program
Software
Software product
Software engineer
Software made with specific requirement
Program
Software
Software product
Software engineer
Developing products using well defined structure
Software
Engineering
Programming
Studying
Development of software product with well defined principles
Software engineering
Software development
Software
Programming
Who said software engineering is the establishment and use of sound engineering principles in order to obtain a software product
Albert einstein
Fritz baeur
Tim berners lee
Donald knuth
The process of developing a software product using a well defined principle
Software engineering
Software product
Software evolution
Engineer
Pick the right software evolution process
Request change -> impact analysis ->system update -> release planning -> system release -> go back to 1
Request change -> impact analysis -> system release ->system update -> release planning -> go back to 1
impact analysis ->request change ->->system update -> release planning -> system release -> go back to 1
Request change -> impact analysis -> release planning->system update -> system release -> go back to 1
Works strictly according to defined specifications and solutions. Solution and methods are understood before coding. Least subjected to change.
Static-type (S-type)
Practical-type (P-type)
Embedded-type (E-type)
Works closely as the requirement of real-world environment.
Static-type (S-type)
Practical-type (P-type)
Embedded-type (E-type)
Specifications can be described but the solution is not obviously instant. Software with a collection of procedures.
Static-type (S-type)
Practical-type (P-type)
Embedded-type (E-type)
E-type software system evolves, its complexity tends to increase
Continuing change
Increasing complexity
Conservation of familiarity
Continuing growth
Reducing quality
Feedback systems
Self-reggulation
Organization stability
E-type software system must continue to adapt
Continuing change
Increasing complexity
Conservation of familiarity
Continuing growth
Reducing quality
Feedback systems
Self-reggulation
Organization stability
Familiarity with the software or the knowledge about how it was developed, why was it developed in that particular manner etc., must be retained at any cost,
Continuing change
Increasing complexity
Conservation of familiarity
Continuing growth
Reducing quality
Feedback systems
Self-reggulation
Organization stability
In order for an E-type system intended to resolve some business problem, its size of implementing the changes grows according to the lifestyle changes of the business.
Continuing change
Increasing complexity
Conservation of familiarity
Continuing growth
Reducing quality
Feedback systems
Self-reggulation
Organization stability
- An E-type software system declines in quality unless rigorously maintained and adapted to a changing operational environment.
Continuing change
Increasing complexity
Conservation of familiarity
Continuing growth
Reducing quality
Feedback systems
Self-reggulation
Organization stability
The E-type software systems constitute multi-loop, multi-level feedback systems and must be treated as such to be successfully modified or improved.
Continuing change
Increasing complexity
Conservation of familiarity
Continuing growth
Reducing quality
Feedback systems
Self-reggulation
Organization stability
E-type system evolution processes are self-regulating
Continuing change
Increasing complexity
Conservation of familiarity
Continuing growth
Reducing quality
Feedback systems
Self-reggulation
Organization stability
The average effective global activity rate in an evolving E-type system is invariant over the lifetime of the product.
Continuing change
Increasing complexity
Conservation of familiarity
Continuing growth
Reducing quality
Feedback systems
Self-reggulation
Organization stability
Software Development Paradigm consist of(3)
Requirement gathering
Maintenance
Software design
Programming
Testing
Integration
Why is se needed? Select all the applies
Large software
Scalability
Cost
Dynamic nature
Quality management
Transitional
Flexibility
Portability
Main characteristics of a good software
Operational
Transitional
Maintanence
Correctness
Portability
Flexibility
{"name":"Soft eng 1", "url":"https://www.quiz-maker.com/QPREVIEW","txt":"Executable code, Collection of program, software made with specific requirement","img":"https://www.quiz-maker.com/3012/images/ogquiz.png"}
Powered by: Quiz Maker