spss developer centrel

Developer Central has been around for almost five years, but Developer Central have never had the flexibility and tools to organize and deliver all the content in the way that would best serve the community of developers and users of SPSS Statistics and other SPSS products. With the new site (The SPSS Community if you are not already there) we have better tools and more control over the site organization. So Developer Central hope that users will find it more useful and easier to use. It has many downloads, forums, links to other resources, and this blog. It's also more of a two-way street, since anyone (who joins the community) can post comments about items and add their own content. (You need to send me an email with a link to the content in order to get it connected.)
Aim to broaden the content to include material for products other than SPSS Statistics, too. Right now, most of the content is for Statistics with some items for Data Collection, but we want that to grow. There is a new forum specifically for suggestions about this community. You can find the forums from the link in the community overview. Besides the SPSS Community, DeveloperWorks hosts gazillions of items for other IBM technologies, so explore those, too. Well, maybe not all the gazillions, but bound to find interesting things as you wander around the site.

AMD developer central latest news

What’s New in ATI Stream SDK v2.3
AMD recently released version 2.3 of the ATI Stream SDK with the following new features:Improved OpenCL™ runtime performance,Improved kernel launch times, Improved PCIe transfer times,Enabled DRMDMA for the ATI Radeon 5000 Series and AMD Radeon 6800 GPUs that are specified in the Supported Devices,Increased size of staging buffers,Enhanced Binary Image Format (BIF),Support for UVD video hardware component through OpenCL (Windows® 7),Support for AMD Radeon™ HD 6900 and HD 6800 Series graphics,Support for AMD E-Series and C-Series platforms,Support for OpenCL math libraries: FFT and BLAS-3.
In conjunction, the ATI Stream Profiler v2.1 and Stream KernelAnalyzer (SKA) v1.7 were released with a number of enhancements to help make programming with the SDK even easier.
Calling all software development innovators in general purpose GPU (GPGPU), data parallel and heterogeneous computing. On June 13-16, 2011 AMD will host the AMD Fusion Developer Summit (AFDS) in Bellevue, Washington. The AFDS conference board has issued a call for presentation proposals, inviting creators of next-generation software to share research and development work through presentations based on the latest technical papers or reports.

AFDS will be a great venue for developers, academics and innovative entrepreneurs to network with others engaged in related work, collectively defining the future course of heterogeneous computing. And delivering a presentation offers you the perfect opportunity to advocate programming paradigms or gain support for industry standards.

Attendees will be invited to participate in interactive sessions and hands-on labs to learn more about award-winning AMD Fusion APUs, GPUs, and advanced parallel processing programmability, as well as programming methodologies using industry standards such as OpenCL™, OpenGL™ and Microsoft DirectCompute.

The AMD Fusion APU is a unique and ideal development platform based on industry-standard APIs and programming languages, combining sequential style programming on the most widely used processor technology, the x86 architecture, with parallel programming on the GPU architecture. APUs are expected to enable users to experience things that were not possible previously, including advancements in user interfaces, video and image processing, Internet applications, and gaming – ushering in an era of intensely visual and more humanistic computing.

mozzila for developers to fix bugs

Software Developers can help Mozilla by fixing bugs, adding new features, writing tests, updating documentation, making Mozilla technology smaller and faster, and making Mozilla development easier for others.
* How to write code for Mozilla
* Other ways to get involved
* Documentation for developers

For Testers

Mozilla's products are what they are because of the help of people just like you who use them day to day, reporting bugs and helping us improve quality. To get involved, read about how you can help to test Mozilla.
Nightly Builds: The Bleeding Edge Created most weekdays from the previous day's work, these builds may or may not work. Use them to verify that a bug you're tracking has been fixed.
Mozilla developers make nightly builds for testing only. Mozilla developers writes code and post the results right away so people can join Mozilla's testing process and report bugs. You will find bugs, and lots of them. Mozilla might crash on startup. It might delete all your files and cause your computer to burst into flames. Don't bother downloading nightly builds if you're unwilling to put up with problems.

How To Get In Touch With Mozilla Developers:
You can find many Mozilla (and Firefox, Thunderbird, Camino, SeaMonkey, etc.) developers on IRC. You can talk with them in real time by logging on mozilla.org's chat server, irc.mozilla.org with an IRC client. Mozilla suite and SeaMonkey come bundled with a chat client, ChatZilla, which is available for Firefox as an extension.

Mozilla also host developer forums, which are available through both mailing list and newsgroup interfaces.

ios developer program

See how your development application will perform in a
real-world environment by installing and testing it directly on iPad, iPhone, and iPod touch.

Test in Real-Time

Plug in your iPad, iPhone, and iPod touch to use Xcode’s graphical debugger, or collect real-time performance data in Instruments’ timeline view. These powerful optimization tools allow you to quickly identify and address any performance issues.

Test Over the Air

With your app running on your iPad, iPhone, and iPod touch, you can test the performance of your application connected to a Wi-Fi or carrier’s network for a real world user experience.

Technical Support

The iOS Developer Program includes two Technical Support Incidents where Apple engineers will provide you with code-level assistance, helpful guidance, or point you towards the appropriate technical documentation to fastrack your development process.

House Passes Bills to Spur New Technology for Drilling, Cleaning Up Spills

The U.S. House of Representatives passed measures to develop new technologies for deep water drilling and cleaning up oil spills, the first legislation inspired by the BP Plc disaster to reach a floor vote.

One bill, passed on a voice vote today, aims to speed up the use of new technologies to limit the damage from oil spills and aid the cleanup. Lawmakers said the booms and skiffs BP is using after the Deepwater Horizon accident in the Gulf of Mexico are the same as units employed in 1989 after the Exxon Valdez tanker crashed off the coast of Alaska.

“We heard time and again the technology they were using was inadequate,” Representative Lynn Woolsey, a California Democrat, said in floor debate, commenting on hearings the House Science & Technology Committee held in response to the Gulf spill.

BP is struggling to contain its damaged well after the Deepwater Horizon rig blew out April 20, killing 11 workers. The oil flow has been temporarily stopped by a cap, after spewing as many as 60,000 barrels a day, according to government estimates.

The House also passed on a voice vote a second BP-related bill, to fund research and development for safer oil and gas drilling at the Department of Energy.

Qantas trials new check-in technology

QANTAS has signalled it will tighten its excess baggage policy as it introduces futuristic new domestic check-in facilities.

The new facilities are designed to slash the time spent in airport queues.

The airline is also preparing to offer upper-tier frequent flyers a unique personal electronic bag tag that can automatically store details of up to four flights and will replace the traditional paper bar code.

A trial of some of the new technologies begins in Perth next week when the flying kangaroo issues new frequent flyer smart cards to a select group of its premium flyers.

The new technologies includes electronic baggage scales and automated excess baggage payment. Its introduction comes as airlines worldwide are discovering baggage charges as a revenue stream.

Qantas officials say the airline will remain flexible on excess baggage during trials but revealed yesterday a new baggage policy was due out towards the end of the year.

Asked whether this meant a crackdown on excess baggage, Qantas customer experience executive manager Alison Webster said: "We'll be making sure we're offering a fair system and our customers are clear on what that system of charges is."

Ms Webster said Qantas had an online capability that allowed people to pre-purchase excess baggage at a significant discount to airport charges and would be publicising this with the baggage policy changes.

Officials said duty managers would also retain the discretion to waive excess baggage charges.

The new smart cards contain chip technology that will allow flyers who have not already checked in online or by mobile phone to tap an airport card reader and complete the process within five seconds.

A 2D barcode would be sent to passengers' handsets to confirm their mobile check-in.

Passengers will eventually be able to combine the smart card, which can also be used as a boarding pass, with RFID bag tags to check their bags at an automated bag drop in seconds.

The tag will be distributed free to chairman's lounge members, platinum, gold and silver level frequent flyers and is expected to be launched when the new system is unveiled in Sydney at the end of November. The airline hopes that about 600,000 upper-tier frequent flyers will no longer need a paper bag tag on the Qantas network by the end of 2011.

The multi-million dollar project took two years to develop in conjunction with 15-odd partners including IBM, Fujitsu, Telstra, Optus and Amadeus, said David Hall, Qantas group executive, corporate services and technology.

IBM spearheaded program management and produced new check-in kiosks and card readers.

Fujitsu provided handheld scanners and other peripherals while Telstra and Unisys worked on the baggage reconciliation system.

For the mobile check-in service, Optus built the SMS gateway, New Media Innovation was responsible for the application and SecureDoc built the 2D barcode system.

Indian companies Tata Consultancy Services and Mahindra Satyam were also involved in the project. TCS worked on enterprise integration and aspects of mobile check-in while Satyam covered off reporting and data warehouse integration.

Sky Assist will help Qantas staff quickly identify misallocated baggage and Amadeus continues to provide departure control smarts.

Tagsys and STMicroelectronics worked on the RFID tags, while the automatic bag drop offering was made possible by hardware provider ICM and software vendor SCL.

Comparison of Various Software Development Life Cycle

The Software Development Life Cycle (SDLC) in software engineering is a methodology that defines the logical steps for developing a custom software product.

This methodology is used to structure, plan and control the software development process. In simple terms, we can define SDLC as a methodology that a developer can use to standardise the process of software development.

A number of SDLC models are available, choosing the right one is no easy task. In this article we'll try to highlight the main advantages and disadvantages of some commonly used SDLCs.

Waterfall Model

This is one of the simplest, classic life-cycle models, also known as the 'linear-sequential' life cycle model. In a waterfall model, each phase must be completed before moving onto the next. A review process is scheduled at the end of each phase to check that the project is on the right track. The steps are as follows:

Advantages of the waterfall model

1. Simple to understand and use.
2. Each phase is independent of other phases and is processed and completed separately.
3. Suitable for smaller projects, and for projects where the requirements are clearly outlined.

Disadvantages of the waterfall model

1. No output or working software is produced until late in the life cycle.
2. High degree of uncertainty and risks.
3. Not a good choice for big or ongoing projects.


Iterative Model

The Iterative model can be thought of as a “multi-waterfall” cycle. Cycles are divided into smaller and easily managed iterations. Each iteration passes through a series of phases, so after each cycle you will get working software.

Advantages of the iterative model

1. Produces working software early during the lifecycle.
2. More flexible as scope and requirement changes can be implemented at low cost.
3. Testing and debugging is easier, as the iterations are small.
4. Low risks factors as the risks can be identified and resolved during each iteration.

Disadvantages of the iterative model

1. This model has phases that are very rigid and do not overlap.
2. Not all the requirements are gathered before starting the development; this could lead to problems related to system architecture at later iterations.

Spiral Model

The spiral model is similar to the iterative model, but places more emphasis on risk analysis. The steps involved in this model can be generalised as follows:

System requirements are defined in as much detail as possible by involving various users, so as identify the various aspects of the system.

A preliminary design of the system is created. This is the most crucial step in the spiral model, as it helps in developing cost-effective strategies for working on a project.

Using the preliminary design, a prototype for the new system is developed. This is generally a scaled down system, which represents an approximate characteristics of the final output.

Consecutive prototypes are then evolved through a fourfold procedure
o Strengths, weaknesses and risks of the previous prototype are evaluated
o Requirements for the new prototype are defined
o Planning and design of the new prototype begins
o Developing and testing the new prototype are carried out

Advantages of the spiral model

1. Good for large and critical projects
2. Working software is produced early during the lifecycle.
3. Large amount of risk analysis.

Disadvantages of the spiral model

1. Involves higher cost.
2. Not suitable for smaller projects.
3. Project success depends on the risk analysis phase - hence, it requires highly specific expertise in risk analysis.

Prototype Model

The prototype model is used to overcome the limitations of waterfall model. In this model, instead of freezing the requirements before coding or design, a prototype is built to clearly understand the requirements. This prototype is built based on the current requirements. Through examining this prototype, the client gets a better understanding of the features of the final product. The processes involved in the prototyping approach are shown in the figure below.

Advantages of the prototype model

1. Benefits from user input.
2. As a working model of the system is provided, users get a better understanding of the system that is being developed.
3. Errors and risks can be detected at a much earlier stage, as the system is developed using prototypes.

Disadvantages of the prototype

1. Increases complexity of the overall system.
2. Involves exploratory methodology and therefore involves higher risk.
3. Involves implementing and then repairing the way a system is built, so errors are an inherent part of the development process.