Software Process
Software Requirements
Software Design
Software Testing
Project Management
100

What is the Waterfall Model?

The waterfall model is a sequential, plan driven-process where you must plan and schedule all your activities before starting the project.

Any phase in the development process begins only if the previous phase is complete

100

What is a Requirement?

A requirement describes the desired behavior of a system, focusing on objects, their states, and the functions that change them. It defines what the customer wants without specifying how it will be implemented.

100

The design phase is accomplished by creating the detailed “micro” view, then determining the architectural “macro” view for the software project

False.


In software development, the macro (architectural) view is typically created first to define the overall structure and high-level components of the system. After that, the micro (detailed) view is developed to specify the design of individual components.

So the correct order is: macro first, then micro not the other way around.

100

What is a bug?

Bugs can be referred to by many terms, including defect, fault, problem, error, incident, anomaly, variance, failure, inconsistency, product anomaly, product incidence, and even feature (sometimes humorously).

100

What is a project?

A PROJECT IS A TEMPORARY ENDEAVOR UNDERTAKEN TO CREATE A UNIQUE PRODUCT, SERVICE, OR RESULT.




200

What model Tests the device is planned in parallel with a corresponding stage of development.

V-Model

200

What is a Functional Requirements?

Functional requirements specify the features or behaviors a system must have to support user tasks. They describe how the system should behave under certain conditions, and failing to meet them results in system failure.

200

Software engineering teams will usually create a design module for each requirement

False.


Software engineering teams typically do not create a separate design module for each individual requirement.

Instead, multiple requirements are often grouped together and addressed within a single design module. Modules are usually organized based on logical functionality, architectural layers, or system components not one module per requirement.

200

Project Mercury’s FORTRAN code has what fault?
 

DO I=1.10 instead of ... DO I=1,10

200

What is OPERATIONS MANAGEMENT?

OPERATIONS ARE ONGOING AND CONTINUOUS. THEY INVOLVE THE ROUTINE, DAY-TO-DAY ACTIVITIES NECESSARY TO SUSTAIN AN ORGANIZATION'S
CORE FUNCTIONS.

300

When should Incremental Model be used? 

The system’s major requirements must be clearly defined and understood, though some details can evolve over time. Quick market delivery is important, and the project involves new technology. There is a shortage of skilled resources, and the project domain is unfamiliar to the team.

300

What is non-functional requirements?

Non-functional requirements define the quality attributes and constraints that affect how a system operates, rather than what it does.

300

What does 4+1 view?

- Logical (OO decomposition – key abstractions)
- Process (run-time, concurrency/distribution of functions)
- Subsystem decomposition
- Physical architecture

+1: use cases

300

What is a testing plan?

A Test Plan is a detailed document that describes the test strategy, objectives, schedule, estimation, deliverables, and resources required to perform testing for a software product. 

300

True or False: Death is never a factor when it comes to faulty software.

False

400

What model is the one that is most important in Software Development Life Cycle?

Spiral model

400

What is "Itys" ?

Security requirements address the protection of sensitive information and adherence to industry standards. Compatibility requirements define the supported hardware and operating systems. Reliability and availability requirements specify acceptable failure rates and system uptime expectations.

400

The high-level design solution is based on what?

The high-level design solution is based on an event dispatcher, which manages events and the functionalities which depends on those events. These have the following characteristics:
 Events may be a simple notification or may include associated data
 Events may be prioritized or be based on constraints such as time
 Events may require synchronous or asynchronous processing
 Events may be “registered” or “unregistered” by components

400

What is Unit Testing?

Unit Testing: A unit test is a way of testing a unit - the smallest piece of code that can be logically isolated in a system. In most programming languages, that is a function, a subroutine, a method or property.

400

True or False: Loss or corruption of communication media, non delivery of data can be the results of faulty software.

True

500

What is a scrum?

Scrum is an agile method that focuses on managing iterative development rather than specific agile practices.




500

What is SRS?

The Software Requirements Specifications (SRS) document formalizes both functional and nonfunctional requirements by detailing the functions and capabilities the product must offer, as well as outlining its constraints and assumptions.

500

What is class design?

 Classes represent real-world entities or system concepts

 Organized into classes: objects in a class have similar characteristics

 Classes have properties (attributes or data)

 Classes also have methods (performs functions)




500

The erroneous 1.10 would cause what?




The erroneous 1.10 would cause the loop to be executed exactly once!




500

True or False: Sloppy redevelopment or maintenance, introduction of new flaws in attempts to fix old flaws, incremental escalation to inordinate complexity.

True

M
e
n
u