What is the difference between Execution environment and Operation Environment in Technical Architecture Dsign
602776
From what I remember ...\n\nThe execution environment refers to the environment, memory, disk space etc as well as environment variables, path= etc, a running (executing) program finds itself in.\n\nOperating Environment refers to bigger issues like how to talk to other processes, what protocols to follow etc.\n\nBut it's been a while ...
248799
Access is a file based database and Microsoft SQL Server a client server database.\nAccess utilises a File Server design while SQL Server employs a Client/Server approach. This is a fundamentally different architecture which has many, many implications.
254248
For what you are doing, there is no practical difference.\n\nThere are differences in terms of complex database activities, such as using triggers; changing server variables on the database server; error handling; the nature of the way data is returned, and other very complex, vary narrow semantics.
621788
different states have laws about each job,  if a person meets both qualifications they can do both.\n\nMany private dect firms do work as process servers
146982
Back in the eighties when network equipment vendors first started to hawk their wares, the term client/server was used to conjure up a host of fancy capabilities offered by the new hardware. Today, client/server has a very specific meaning that has nothing to do with hardware at all. Even so, most folks still associate the term client with the physical computers they are using and the term server with some other physical computer to which they are connected. There's a glimmer of truth there, to be sure, but today client/server means much more.\n\nWe're going to cover the essentials of client/server computing. We'll define one-tier, two-tier, three-tier, and n-tier client/server program architectures; we'll explain the difference between a thin client and a fat client; and we'll discuss the middleware concept. But first, you need to understand a few things about general software architecture.\n\nMost application programs have three major layers. On top is the presentation layer, which provides the human/machine interaction (the user interface). The presentation layer handles input from the keyboard, mouse, or other device and output in the form of screen displays. In the middle is the application or business logic, the functionality that gives the application program its character. Application logic makes the difference between an order entry system and an inventory control system, for example; it is often called business logic because it contains the business rules that drive a given enterprise. The bottom layer provides the generalized services needed by the other layers, including such things as file services, print services, communications services, and, perhaps most important, database services.\n\nFor simplicity, we will confine this discussion just to those programs needing database services. That's what most architects first think of when they hear the term client/server, but the general rules apply to any kind of service.\n\nThe number of tiers in a client/server application is determined by how tightly or loosely the three program layers are integrated. A one-tier application is one in which the three program layers are tightly connected. In particular, the presentation layer has intimate and detailed knowledge of the database structure. The application layer is often interwoven with both the presentation layer and the services layer. All three layers, including the database engine, almost always run on the same computer.\n\nOne-tier applications are easy to design and write, especially with today's modern software tools. It's also possible to create a multiuser one-tier application by running the application on several PCs and having them share the database. The database can be stored either on one of the PCs (a peer solution) or on a file server. Note that each PC running the application has its own copy of the database engine; only the data is shared, not the database logic itself.\n\nMultiuser one-tier applications are okay until the number of users gets large. The problem is that all the database work is performed in each client. For example, if the program needs to list all clients with the last name of Smith, all the information (indexes and data records) needed to resolve that query to the database must be transferred over the network. For some complex queries, a significant amount of data must be examined, perhaps even the entire database. At a more technical level, it is difficult to manage independent database engines to be sure that no conflict arises when two clients attempt to access or update the same record. This is called the record-locking problem.\n\nThe solution for the performance and technical problems associated with multiuser one-tier programs is two-tier client/server architecture. This type of application is written in mostly the same way as a one-tier application, with the exception that the database service (engine) no longer runs with the client. Instead, it
319401
An application is based on a code (C,C++,Java,Perl,C#...). After the code is written it's compiled for a specific operating system. The role of the compiler is to translate the cod instructions into sequences that the CPU will understand. It's called assembling the application.\nA driver doesn't have direct acces to the CPU. It's like a library that contains definition, methods so that if you would like to create an application that will make use of them or for another application (like the OS) to communicate with devices.
1008551
Not sure the question but it is set up (generally) as a program that has includes (one for data declarations, one for the main program, one to hold the subroutines). The main can then reference the includes decreasing impact issues when changes are required.
1059804
yeah, the only difference between the default and public specifier is that default can only be accessed in the same package whereas public can be accessed in other packages too.
428865
order of operation - parenthesis, power, multi/divide, and add/subtract
433146
The difference between "programming" and "scripting" is better defined by usage, or application, as well as scope and purpose. A programming language is used for building standalone projects, or "applications"; a scripting language is used to write "scripts" that interact with other data or systems to perform parts of a task rather than an entire workflow.\n\nAn example might make this clearer. Imagine an accounting application program used in a large corporation. The program would be written in a programming language by a team of developers, probably at some other company, a software house. It would have a long lifecycle, and have many features. One of them might be to generate a series of invoices. This would be one of many tasks done with the program, which runs for extended periods of time. But it might be necessary to separate the invoices, sending some to a printer in the mail room, others to a fax machine, and still others to be sent via email. This task might be accomplished by a local programmer, who writes a simple "script" that sorts through the accounting program's output files and dispatches them appropriately. That little snippet of local, customized programming would be a script, written in a scripting language. The script would be started, perform its one task, and stop.\n\nProgramming languages are used to write programs, which can run for a while and do multiple things.\nScripting languages are used to write scripts, which run for a short duration to perform a single, simple task.\n\nOf course, there are applications programs that have been cobbled together out of collections of scripts, and there are programmers who use a traditional programming language to write a full-blown program to erase a file, but the general sense of the range of usages should now be clear.\n\nSome languagees such as Perl or Visual Basic can be used for both kinds of task, and therefor can be characterized as one or the other.
853061
In a computernetwork all the systems may be physically avaialble in an area which covers it. In a distributed system environment physical presence pays less importance.
923821
If you compare the jobs with actual construction jobs:\n\nCIO - Customer; defines what he wants\nSystems Analyst - Architect\nProgrammer - Builds the house; frames, electrical, plumbing\nDBA - Painter, landscape, appliances.\n\nAlthough the Programmer and DBA really have very similar jobs and have to work together. The DBA builds the database to be efficient; tables, relationships, etc. The Programmer writes the code that reads the data, presents it to the customer, writes it back to the database.\n\nSo of the two, probably the Programmer leads by a little with the DBA just behind.
48945
both of the databases have the ability to return consistent (correct) \nresults.  Only oracle can do so in a mixed workload environment (mixed \nupdates and reads) in a highly concurrent fashion.  In Oracle we employ \nmulti-versioning and read consistency.  The others use shared read locks (which \nwill lead to deadlocks and blocking).  We never block on a read -- they \nfrequently block on a read.  So, another feature with a check mark that is \nvirtually meaningless
1088147
Analysis is understanding the problem you're trying to solve. What environment is it in. Who are your customers going be. What behaviors should your solution exhibit. etc.\n\nDesign is figuring out how to organize the solution once you've done the analysis and you understand the problem.\n\nUsing resouces like UML, analysis would be in the requirements, use case, activity diagram arena.\n\nDesign would be in the class diagram, sequence diagram, state diagram section.\n\nArchitecture kind of has a foot in each camp.\n\nGenerally you want to do a fair amount of analysis before design, otherwise you'll start building a solution for a problem you don't truly understand. These solutions usually aren't a good match. They are difficult to fit the problem once you eventually understand it, and they generally aren't as flexible.\n\nHowever, this doesn't mean that analysis has to be 100% complete before design begins. It's just wise to have done a fair amount of analysis first.
748203
The code varies by game. It really depends on the Engine that it is run on. In effect games are just a bunch of linked files. each one has to be coded, but the coding varies, because there are tons of scripting languages.
657835
when an organisation is in business it must decide what it is going to do how, and why? This is the planning stage, a study of the external and internal environments (environmental scanning) will show what the core competances of the compnay are and they can set about establishing goals, the goal must be inline with what these are and how they are going to achieve it and must permeate through the whole oganisation so they are aware of what they want.\n\ngoogle search click on advanced and then search in domains ac.uk, should give you some good answers, or try bized.co.uk?\n\nhope it helps
418748
reaction and operation time of a task < allowed delay\n\nnot only how fast can it be done, but can it be done as specific times and can these time be accurately reported.\n\n\nis buffering or queuing of data possible.\nmulti-tasking/priority (can not do everything at same time)