Technology Related Questions

Technology Related Questions

1:

How much longer can Moore's Law continue to hold true?

A:

Moore's Law is based on the observation made in 1965 by Gordon Moore, co-founder of Intel. Moore observed that the number of transistors per square inch on an integrated circuit had doubled every year since the integrated circuit was invented. He also predicted that this trend would continue for the foreseeable future. Today, nearly 35 years after Moore's initial observation, CPU density, along with CPU speed and processing power, continue to double every twelve to eighteen months. Most experts, including Moore himself, expect Moore's Law to hold for at least another two decades.

2:

What is the best Interactive Development Environment (IDE) for developing software?

A:

We don't really have a single favorite IDE it really depends on what sort of code you are trying to write and in what environment. For general purpose IDEs, two favorite tools are Sun's Java Workshop for developing in a Solaris environment and Symantic's Visual Cafe for Java for developing in a Windows environment. For C or C++ environments, both companies have sister tools with similar names . Imprise's JBuilder would be our pick for Windows development where the application had a large amount of database connectivity. Finally, if there was a large amount of legacy Unix/X-Windows code, we would choose UIM/X because of its excellent X-Windows to Java conversion utility. Additional information on these and other development tools is provided in Chapter 15.

3:

How long does it take to learn Java?

A:

Java was designed from the ground up with simplicity in mind. A week of training is typically sufficient for a C or C++ developer to get started with Java programming. Programmers whose experience is limited to less-similar languages such as COBOL or FORTRAN will usually take longer to learn Java and several weeks training will probably be required. In either case, learning Java syntax is much simpler than learning object-oriented design, the subject of the next question.

4:

How long does it take to learn object-oriented design?

A:

You will gain only a small fraction of the benefits of an object-oriented language such as Java if your software architects and designers do not understand object-oriented design principals. It takes between six and eighteen months for a good procedural developer to become a good object-oriented software architect, and time alone is no guarantee.

5:

Shouldn't I wait for Java technology to mature before I start considering it for large software development projects?

A:

As with any new technology, Java is climbing the maturity curve and may not be suited today for every large software project you will undertake. However, the explosion of the Internet has caused Java to mature much faster than it would have otherwise done so. If you are not at least considering Java today for your enterprise-wide applications, you are probably hopelessly behind your competitors who are already figuring out how best to use and benefit from Java technology.

6:

How fast is a real-time operating system?

A:

While there is no precise definition, a typical real-time operating system is able to respond to interrupt signals with a worst case latency of fifty microseconds or less. General purpose operating systems, such as Windows NT or Unix may have an interrupt latency up to five hundred microseconds or more. For a typical computer operation, it may not matter if the computer responds within fifty or five hundred microseconds. However, many classes of control systems, ranging from telephone switches to modern anti-lock brake systems, require interrupt signals to be processed within precise deterministic time periods or an essential process i.e., stopping a car will not function properly.

7:

Can a RAID-5 disk configuration contain more than (fewer than) five disks?

A:

Yes. Most RAID-5 systems support as few as three disks (two data plus one parity) in a stripe and as many as several dozen or more. A five disk stripe is one of the more common configurations as it minimizes the data overhead while retaining plenty of space for parity information while not overtaxing log disks.

See Chapter 16 for a more complete description of RAID disk systems.

8:

Doesn't a RAID 0+1 (mirrored) system cost twice as much as a RAID-5 system?

A:

No. Assuming a five way stripe, a RAID-5 system already uses 20% more disk than a system of stand-alone disks. The additional cost overhead to move to a RAID 0+1 system is thus only 1.2 / 2 = 60%. These figures are for disk costs only, and do not include any additional controller costs.

9:

Which tools would you recommend for source/version control?

A:

A source/version control tool is a basic requirement of successful software development projects. Nevertheless, we continue to see many software development projects well underway without any such tool in use. So for starters, the first recommended tool is any tool that you have. Most Unix operating systems come with a bundled version of either SCCS (source code control system) or RCS (revision control system). Either provide all the functionality necessary to implement a basic source/version control system. The second recommended source/version control tool is the one, if any, that comes with your Integrated Development Environment (IDE). Many IDEs come bundled with some sort of source/version control tool. The only warning here is that you get what you pay for. Bundled source/version control tools may be stripped down versions of other products or may be simple afterthoughts to meet a check box on a marketing brochure. For instance, some IDEs have source/version control tools that, while integrated into the IDEs graphical user interface, do not have command line equivalents. Anyone who has ever handled configuration management for a large project knows that this is almost impossible with command line interaction that can be called from automated build (and other types of) scripts. One of the most innovative source/version control tools, and our favorite, is JavaSafe, from Sun's Java Products Division.

Despite its name , JavaSafe is not just for managing Java code. JavaSafe can be used for managing C, C++, Perl, HTML, or almost any other type of file. JavaSafe has two components: a server based on Sun's Java Webserver, and a client that can be run stand-alone or within a web browser. Both components can be used locally by a single developer on a single workstation. In contrast, the server and client components can be distributed across an Intranet or even the Internet providing unparalleled support for distributed developer teams . More information on JavaSafe can be found at http://java.sun.com/products/javasafe/.

10:

Which tools would you recommend for software stress testing?

A:

Stress testing is a critical component of the Web-Centric Production Acceptance (WCPA) process described in Chapter 13. One of my favorite quick and easy tricks for stress testing web servers is the Lynx text-only web browser. Lynx is commonly available at freeware sites over the Internet. One of the little known features of Lynx is that it has a command line interface. It is trivial to write a simple script to call Lynx in a loop. Once you download a copy of Lynx, just run "lynx -h" for help in determining the appropriate command line options. Be sure to set the lynx cache to 0 or you will be defeating the purpose of your web testing. If you want something a little fancier to stress test your web server, WebLoad, from Radview Corporation (http://www.radview.com) is my favorite commercial web server stress testing tool. It does cost more than Lynx, but it's worth the cost.

Most stress testing, however, requires more than the simple process defined above. One of my favorite application level stress testing tools is Jtest from Parasoft (http://www.parasoft.com). Parasoft also has a complete line of testing tools for C and C++ code.

At the enterprise level, stress testing really needs to go one step further than simple application or web server stress testing. Ganymede Software's Pegasus tool (http://www.ganymedesoftware.com) is one of the few stress testing tools available that performs complete end-to-end performance analysis and stress testing of web-centric and client-server applications.

11:

What is a JavaBean?

A:

JavaBeans are reusable software components written in Java. A more complete description of JavaBeans can be found in Chapter 17. Using an Integrated Development Environment such as Symantec Cafe, Imprise JBuilder, or Sun's Workshop for Java (see Chapter 15), you can customize JavaBeans parameters and visually manipulate them to create Java applets or stand-alone Java applications.

12:

What is the difference between a Java applet and a JavaBean?

A:

JavaBeans are designed to be easily reused and visually manipulated by JavaBean aware development tools. The JavaBeans API endows a JavaBean with specific component functionality, including:

  • introspection: allows a development tool to analyze a JavaBean and determine its properties

  • customization: allows a developer to customize a JavaBean by modifying the properties that have been discovered by introspection

  • events: allows a JavaBean to communicate with other JavaBeans and connect together to form a processing tree

  • persistence: enables developers to save customized JavaBeans for further reuse



Software Development. Building Reliable Systems
Software Development: Building Reliable Systems
ISBN: 0130812463
EAN: 2147483647
Year: 1998
Pages: 193
Authors: Marc Hamilton

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net