Lesson 1 – What is Software
1. is more than just a program code.
2. is an executable code, which serves some computational purpose.
3. Software, when made for a specific requirement is called_____.
4. Helps run the computer hardware and computer system itself. includes operating
systems, device drivers, diagnostic tools and more
5. Allows users to accomplish one or more tasks. It includes word processing, web
browsing and almost any other task for which you might install software.
6. is a set of tools to aid developers in writing programs. The various tools available are
compilers, linkers, debuggers, interpreters and text editors.
7. Classes of Software : (3)
8. Software, commonly known as________ or ________, consists of all the instructions
that tell the hardware how to perform a task.
9. The process of developing a software product using software engineering principles and
methods.
10. Evolution starts from the __________.
11. A software system must continue to adapt to the real world changes, else it becomes
progressively less useful.
12. A software system evolves, its complexity tends to increase unless work is done to
maintain or reduce it.
13. 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.
14. In order for a system intended to resolve some business problem, its size of
implementing the changes grows according to the lifestyle changes of the business.
15. A software system declines in quality unless rigorously maintained and adapted to a
changing operational environment.
16. The software systems constitute multi-loop, multi-level feedback systems and must be
treated as such to be successfully modified or improved.
17. a system evolution processes are self-regulating with the distribution of product and
process measures close to normal.
18. The average effective global activity rate in an evolving a system is invariant over the
lifetime of the product.
19. Laws in software Evolution (8).
Lesson 2 Software Paradigms
1. refer to the methods and steps, which are taken while designing the software.
2. is a subset of Software design paradigm which is further a subset of Software
development paradigm.
3. This Paradigm is known as ____________where all the engineering concepts pertaining
to the development of software are applied.
4. Software engineering paradigms (3)
5. Software design paradigms (3)
6. Programming paradigms (3)
7. Characteristics of a good software (3)
8. Cost.
9. the degree of ease with which products such as software and Web applications can be
used to achieve required goals effectively and efficiently.
10. is defined as a level of performance that uses the lowest amount of inputs to create the
greatest amount of outputs.
11. adherence to the specifications that determine how users can interact with the software
and how the software should behave when it is used correctly.
12. is the ability of the system to do the work for which it was intended.
13. is the ability to provide services that can defensibly be trusted within a time-period.
14. secured system.
15. Types of Operational (8)
16. This aspect is important when the software is moved from one platform to another.
17. the usability of the same software in different environments.
18. the ability of computer systems or software to exchange and make use of information.
19. the use of existing assets in some form within the software product development
process;
20. an open system that is able to fit its behavior according to changes in its environment or
in parts of the system itself.
21. This tells us how well software works in operations.
22. Types Of Transitional (4).
23. This aspect briefs about how well a software has the capabilities to maintain itself in the
ever-changing environment.
24. the extent to which a software/Web application may be divided into smaller modules.
25. is defined as the degree to which an application is understood, repaired, or enhanced.
26. it normally refers to the ability for the solution to adapt to possible or future changes in its
requirements.
27. is the ability of a program to scale.
28. Types of Maintenance (4).
Lesson 3 – SDLC
1. is a well-defined, structured sequence of stages in software engineering to
develop the intended software product.
2. initiate the request.
3. bringing out the information on what the project requirement is.
4. The team analyzes if a software can be made to fulfill all requirements of the
user and if there is any possibility of software being no more useful.
5. decide a roadmap of their plan and try to bring up the best software model
suitable for the project.
6. The inputs from users and information gathered in requirement gathering phase
are the inputs of this step. Output will be the logical design and the physical
design.
7. programming phase.
8. End user testing.
9. integration with other entity.
10. installing the software on user machines.
11. maintaining the code, the systems for patch updates.
12. retirement; legacy system.
13. Steps in SDLC (11):
14. is the simplest model of software development paradigm. It says the all the
phases of SDLC will function one after another in linear manner.
15. This model leads the software development process in iterations.It projects the
process of development in cyclic manner repeating every step after every cycle
of SDLC process.
16. is a combination of both, iterative model and one of the SDLC model. It can be
seen as if you choose one SDLC model and combine it with cyclic process
(iterative model).
17. refers to activities that occur before the system is turned over to its users.
18. implementation covers six major activities (6).
19. is the process where the physical design specifications developed by the
analysis team are converted into computer codes by the programming team.
20. is the process of examining a product to ascertain what defects it contains.
21. three testing types (3)
22. Combining modules and testing them is called_____. The use of this test is to
identify errors that were not or could not be detected by unit testing individual
modules.
23. An example is a caller module that passes a variable of the wrong data type
to a subordinate module.
24. A module is passed or returns a value that was unexpected (such as negative
number for a price).
25. A module generates an error such as “out of memory” or “file already in
use” due to conflicting resource needs.
26. The conditions of two or more modules interact to cause complex failures (such
as an order class method that operates correctly for all possible customer
object conditions except one).
27. is performed first by developers or test personnel to make sure that the system
does not fail and meets the developers’ understanding of user requirements.
28. user testing of a completed information system using simulated data.
29. user testing of a completed information system using real data in the real user
environment.
30. types of Acceptance testing (2).
