St Pauls University

DBT 1303: Software Development

Question 1
a. System software computer program designed to run a computers hardware
and application programs
Application software program designed for end users to perform specific
functions
b. Software development methodology also known as development
methodology is splitting of software development process into distinct phases
containing activities
c. Challenges developing software
d. Variable - A piece of memory that contain a data value used to store
information
Infinite loop - A sequence of instructions in a computer which loops endlessly
due to no terminating condition or no condition that cant be meet
Assignment statement sets or resets the value stored in the storage
location denoted by a variable name it copies a value into the variable
Assignment operator store a value in the object designated by the left
operand

e. Software quality assurance - Consists of a means of monitoring the software

engineering processes and methods used to ensure quality
Programming paradigm - A programming paradigm is a fundamental style of
computer programming. Paradigms differ in the concepts and abstractions
used to represent the elements of a program (such as objects, functions,
variables, constraints, etc.) and the steps that compose a computation
(assignation, evaluation, continuations, data flows, etc.).
User interface the interface features through which users interact with the
computer
f.

Algorithm procedural or formula for solving a problem. Set of rules for

solving a problem
Pseudo code - informal high Level description of the principle of a computer
program or algorithm

Question 2
a. Software testing Test techniques include the process of executing a program or application
with the intent of finding software bugs (errors or other defects). Software
testing involves the execution of a software component or system component
to evaluate one or more properties of interest.
Alpha Testing:
Alpha Testing is like performing usability testing, which is normally done by
the in-house developers. On rare occasions Alpha Testing is done by the client
or an outsider. Once the alpha testing version is released, its then called the
Alpha Release.
Generally we perform all testing types in alpha testing phase. Alpha testing
phase ends with a feature freeze, indicating that no more features will be
added to the software. Types of testing done by tester in Alpha phase
includes Smoke testing, Integration Testing, System testing, UI and Usability
testing, Functional Testing, Security Testing, Performance Testing, Regression
testing, Sanity Testing and Acceptance Testing.
Beta Testing:
Beta Testing is done by the number of the end users before delivery, the
change request would be fixed if user gives the feedback or report defects.
The Version Release after beta testing is called beta Release.
Beta testing can be considered pre-release testing. Beta test versions of
software are now distributed to a wide audience on the Web partly to give the
program a real-world test and partly to provide a preview of the next
release.
The main objective behind the Beta testing is to get the feedback from the
different groups of customers and check the compatibility of the product in
different kind of networks and hardware.
b. Manual testing
Manual testing is the process of manually testing software for defects. It
requires a tester to play the role of an end user and use most of all features
of the application to ensure correct behavior.
Automation testing

In software testing, test automation is the use of special software (separate

from the software being tested) to control the execution of tests and the
comparison of actual outcomes with predicted outcomes.
c. Black box and white box

Criteria

Black Box Testing

White Box Testing

Black Box Testing is a software

White Box Testing is a software

testing method in which the internal testing method in which the

Definition

structure/ design/ implementation of internal structure/ design/

the item being tested is NOT known implementation of the item being
to the tester

tested is known to the tester.

Mainly applicable to higher levels of Mainly applicable to lower levels

Levels Applicable testing:Acceptance Testing

To
System Testing
Responsibility
Programming
Knowledge
Implementation
Knowledge
Basis for Test
Cases

Generally, independent Software

Testers

of testing:Unit Testing
Integration Testing
Generally, Software Developers

Not Required

Required

Not Required

Required

Requirement Specifications

Detail Design

Question 5
a. Algorithm

b. Categories of software maintenance

1. Adaptive maintenance implementation of changes in part of the

system which has been affected by a change that occurred in some
other part of the system
2. Perfective maintenance deals with implementing new or changed user
requirements
3. Preventive maintenance involves activities to prevent the occurrence
of errors
4. Corrective maintenance deals with the repair of faults and errors

c. Explain the functional design process

d.