goodBye

We are in the last week of the international project, I feel very sad because I have made some friends of other countries. It was a very exciting experience been working, sharing ideas and develop projects that give us professional experience. I feel that the final exam, was very so long and we have very little time for answer the questions , I think that there is no sense in the exams, because all the final project we have'd working on there was a retroalimentation.

It was a pleasure forming part of this project and with this last publication, I say good bye for this project

Final Exam

Finally we are in the final exam of the project and we will need to write like a report with some questions like Why is global software development difficult to execute in practice?. I feel happy because the team work of the tetris project ended successfully all of the requirements even though we had some setback as the use Visual Studio at the end everything went to perfection. As a team we are very pleased with the work until now.

Q&AProject3

In the last weekend I had some setbacks and I send questions later of the week 3 :( but when I could connect I send in the P4.

Software Crisis

In start to read about the software crisis and I found this article quite interesting. The problems of the software development planet are responsible for most of the project failures that force managements worldwide to put more rigid processes in place to ensure compliance. Is there a crisis at all? As you stroll through the aisles of neatly packaged software in your favorite computer discount store, it wouldn’t occur to you that there’s a problem. You may be surprised to learn that those familiar aisles of software represent only a small share of the software market--of the $90 Billion software market, a mere 10% of software products are "shrink wrapped" packages for personal computers. The remaining 90% of the market is comprised of large software products developed to specific customer specifications.
By today’s definition, a "large" software system is a system that contains more than 50,000 lines of high-level language code. It’s those large systems that bring the software crisis to light. If you’re familiar with large software development projects, you know that the work is done in teams consisting of project managers, requirements analysts, software engineers, documentation experts, and programmers.

http://www.unt.edu/benchmarks/archives/1999/july99/crisis.htm

Communication skills

Having effective team communication skills is a crucial requirement for both leaders and team members alike. It allows you to establish harmonious relationships, fully understand the team's intention, share your ideas easily, and even impress other team members.

The next articul talk about the communication skills.
http://ezinearticles.com/?Effective-Team-Communication-Skills-For-Maximum-Team-Performance&id=1091938

Integration

In the last week we had problems with the integration of the keyboard but Sergio Collazon and Cecilia worked in the problem and finished. Without controlling integration developers test their code and integrate believing all is well. But because of parallel integration there is a combination of source code which has not been tested together before. Integration problems happen without detection.
Further problems happen when there is no clear cut latest version. This applies not only to the source code but the unit test suite which must verify the source code correctness. If you can not lay your hands on a complete, correct, and consistent test suite you will be chasing bugs that do not exist and passing up bugs that do.
You can have developers own specific classes. Class owners integrate and commit to the repository properly. Interclass dependencies can still be wrong. Class owners can become bottle necks if one class requires many changes and it doesn't solve the whole problem.
Yet another way is to appoint an integrator or integration team. Integrating code from multiple developers is more than a single person can handle.

Some tecnics

Following development, the project is staged for deployment and user acceptance testing is performed to identify any technical modifications that may be necessary to stabilize the site. The final code is baselined and archived prior to launching the application.

A checklist that gives the project manager or software integration team leader a way to analyze, plan, communicate and execute the Integration Phase of a large or complex software project. The checklist gives reminders of needed activities and suggested behaviors that are not necessarily documented in the project life cycle, and highlights considerations that the project manager or integration team leader can use to minimize risks and delays inherent to the Integration Phase. This checklist highlights considerations that the project manager or integration team leader can use to minimize risks and delays inherent to the Integration Phase. The person responsible for planning and leading the Software Integration Phase of a project reviews the list of suggested activities and behaviors. Select the items that reflect obvious past problems or possible current problems.