Software Engineering 1

Question 1

Software engineering

Answer 1

an engineering branch associated with development of software product using well-defined scientific principles, methods and procedures.

Question 2

Software

Answer 2

considered to be collection of executable programming code, associated libraries and documentations. Software, when made for a specific requirement is called software product

Question 3

program

Answer 3

is an executable code, which serves some computational purpose.

Question 4

Engineering

Answer 4

on the other hand, is all about developing products, using well-defined, scientific principles and methods.

Question 5

Software Evolution

Answer 5

The process of developing a software product using software engineering principles and methods

Question 6

Software Evolution Cycle

Answer 6

1. change request
2. impact analysis
3. release planning
4. system update
5. system release

Question 7

Evolution Cycle

Answer 7

1. gathering process
2. create prototype
3. show to users
4. get feedback
5. update and maintenance

Question 8

Software Evolution Laws Lehman

Answer 8

1. Static-type (S-type)
2. Practical-type (P-type)
3. Embedded-type (E-type)

Question 9

Static-type (S-type)

Answer 9

• which works strictly according to defined specifications and solutions. The solution and the method to achieve it, both are immediately understood before coding. The s-type software is least subjected to changes hence this is the simplest of all.
• For example, calculator program for mathematical computation

Question 10

Practical-type (P-type)

Answer 10

• This is a software with a collection of procedures. This is defined by exactly what procedures can do. In this software, the specifications can be described but the solution is not obviously instant.
• For example, gaming software.

Question 11

Embedded-type (E-type)

Answer 11

• This software works closely as there quirement of real-world environment.
• This software has a high degree of evolution as there are various changes in laws, taxes etc. in the real world situations.
• For example, Online trading software.

Question 12

E-Type software evolution

Answer 12

1. Continuing change
2. Increasing complexity
3. Conservation of familiarity
4. Continuing growth
5. Reducing quality
6. feedback system
7. Self-regulation
8. Organizational stability

Question 13

Continuing change

Answer 13

An E-type software system must continue to adapt to the real world changes, else it becomes progressively less useful.

Question 14

Increasing complexity

Answer 14

As an E-type software system evolves, its complexity tends to increase unless work is done to maintain or reduce it.

Question 15

Conservation of familiarity

Answer 15

The 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, to implement the changes in the system.

Question 16

Continuing growth

Answer 16

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.

Question 17

Reducing quality

Answer 17

An E-type software system declines in quality unless rigorously maintained and adapted to a changing operational environment.

Question 18

Feedback systems

Answer 18

The E-type software systems constitute multi-loop, multi-level feedback systems and must be treated as such to be successfully modified or improved.

Question 19

Self-regulation

Answer 19

E-type system evolution processes are self-regulating with the distribution of product and process measures close to normal

Question 20

Organizational stability

Answer 20

The average effective global activity rate in an evolving E-type system is invariant over the lifetime of the product.

Question 21

Software paradigms

Answer 21

refer to the methods and steps, which are taken while designing the software. There are many methods proposed and are implemented. But, we need to see where in the software engineering concept, these paradigms stand.

Question 22

Software Development Paradigm

Answer 22

• This paradigm is known as software engineering paradigms
• where all the engineering concepts pertaining to the development of software are applied. It includes various researches and requirement gathering which helps the software product to build

Question 23

Software Development Paradigm consists of

Answer 23

1. requirement gathering
2. software design
3. programming

Question 24

This paradigm is a part of Software Development and includes

Answer 24

1. Design
2. Maintenance
3. Programming

Question 25

This paradigm is related closely to programming aspect of software development. This includes –

Answer 25

1. Coding 2. Testing 3. Integration

Question 26

Need of Software Engineering

Answer 26

1. Large software 2. Scalability 3. Cost 4. Dynamic Nature 5. Quality Management

Question 27

Large software

Answer 27

- It is easier to build a wall than a house or building, likewise, as the size of the software becomes large, engineering has to step to give it a scientific process.

Question 28

Scalability

Answer 28

If the software process were not based on scientific and engineering concepts, it would be easier to re-create new software than to scale an existing one.

Question 29

Cost

Answer 29

As hardware industry has shown its skills and huge manufacturing has lower down the price of computer and electronic hardware. But, cost of the software remains high if proper process is not adapted.

Question 30

Dynamic Nature

Answer 30

Always growing and adapting nature of the software hugely depends upon the environment in which the user works. If the nature of software is always changing, new enhancements need to be done in the existing one. This is where the software engineering plays a good role.

Question 31

Quality Management

Answer 31

Better process of software development provides better and quality software product.

Question 32

Characteristics of good software

Answer 32

1. Operational 2. Transitional 3. Maintenance

Question 33

Operational

Answer 33

This tells us how well the software works in operations

Question 34

Operational, It can be measured on:

Answer 34

1.  Budget 2. Usability 3. Efficiency 4. Correctness 5. Functionality 6. Dependability 7. Security 8. Safety

Question 35

Transitional platform to another:

Answer 35

1. Portability 2. Interoperability 3. Reusability 4. Adaptability

Question 36

Maintenance

Answer 36

This aspect briefs about how well the software has the capabilities to maintain it self in the ever-changing environment:

Question 37

Maintenance has the capabilities to maintain it self in the ever-changing environment:

Answer 37

1. Modularity 2. Maintainability 3. Flexibility 4. Scalability

Question 38

is a branch of computer science, which uses well-defined engineering concepts required to produce efficient, durable, scalable, in-budget, and on-time software products.

Answer 38

Software engineering