All categories

3 years ago

Rapid development programming languages eliminate the possibility of having bugs in code. True or False

Computers and Technology

1 answer:

Pachacha [2.7K]3 years ago

3 0

False,

" I am talking about 20-30+ millions lines of code, software at the scale and complexity of Autodesk Maya for example.

If you freeze the development as long as it needs to be, can you actually fix all the bugs until there is simply not a single bug, if such a thing could be verified by computers? What are the arguments for and against the existence of a bug-free system?

Because there is some notion that every fix you make creates more bugs, but I don't think that's true.

By bugs I meant from the simplest typos in the UI, to more serious preventative bugs that has no workaround. For example a particular scripting function calculates normal incorrectly. Also even when there are workarounds, the problem still has to be fixed. So you could say you can do this particular thing manually instead of using the provided function but that function still has to be fixed."

work cited:

https://softwareengineering.stackexchange.com/questions/195571/is-it-possible-to-reach-absolute-zero-bug-state-for-large-scale-software

You might be interested in

Play among us with me

omeli [17]

Answer:

cool

Explanation:oof

8 0

3 years ago

Read 2 more answers

13) What are the benefits and detriments of each of the following? Consider both the systems and the programmers’ levels. a. Sym

dsp73

Answer:

Automatic and Explicit Buffering.

In the case of explicit buffering, the length of the queue is provided while in automatic buffering the queue size needs to be indefinite. In automatic buffering there is no need to block the sender while coping the message. While in explicit buffering the sender is blocked for the space in queue.

No memory is being wasted in explicit buffering.

Send by Copy and Send by Reference.

By using the send by copy method, the receiver is not able to change the state of parameter while send by reference allow. The advantage of using the send by reference method is that it allows to change a centralized application to its distributed version.

Fixed-sized and Variable-sized Messages.

In fixed size messaging refers, the buffer size is fixed. This means only a particular number of messages can only be supported by the fixed size buffer. The drawback of the fixed size messages is that they must be a part of fixed size buffer. These are not a part of variable size buffer. The advantage of variable size message is that the length of the message is variable means not fixed. The buffer length is unknown. The shared memory is being used by the variable size messages.

Explanation:

5 0

3 years ago

A domain account is one that is created on a Windows server domain controller (network) using (Describe Microsoft accounts)

Korvikt [17]

Answer:

Explanation:

3 0

3 years ago

Design a generic post-implementation evaluation form. The form should consist of questions that you could use to evaluate any in

irina1246 [14]

Answer:

Project Identification

Provide the identifying information associated with the project, including the applicable project control code, system acronym, and system title.

System Proponent

Provide the name of the System Proponent.

History of the System

Briefly describe the system’s history and predecessor, if any. State the mission needs and information requirements, including how the system is expected to help users.

Functional System Description and Data Usage

Briefly describe what the system does functionally and how the data are used by the system.

Explanation:

Overview

The Post-Implementation Review is used to evaluate the effectiveness of the system development after the system has been in production for a period of time (normally 6 months). The objectives are to determine if the system does what it is designed to do: Does it support the user as required in an effective and efficient manner? The review should assess how successful the system is in terms of functionality, performance, and cost versus benefits, as well as assess the effectiveness of the life-cycle development activities that produced the system. The review results can be used to strengthen the system as well as system development procedures.

The review is scheduled to follow the release of a system or system revision by an appropriate amount of time to allow determination of the effectiveness of the system. A representative from the functional development group or other member of the major user organization participates in the review. The System Proponent ensures that all documentation and all personnel needed to participate in the review are accessible.

The reviewer and an assigned team collect the information needed for the Post-Implementation Review by interviewing end users and their managers, system administrators, and computer operations personnel. The report is then prepared and provided to the user organization that requested it and the information systems organization, which may jointly use the findings to initiate other actions.

The Post-Implementation Review is a free-form report, and not all sections are relevant or necessary to the final product. A description of the Post-Implementation Review Report is attached.

3 0

3 years ago

Dam naj za pierwszej osobie która odpowie dobrze!

Rama09 [41]

I don’t understand that language

8 0

3 years ago