jump to navigation

Did Egypt Win…..!? February 8, 2008

Posted by essamabdelaziz in General.
add a comment

Dear all,

it was a long  time since i last wrote any thing here..it was a pretty busy on my side.

i  back again and i will  keep writing as soon as i get achance .

yestrday i was watching  the semi final egypt Vs Cote D’Ivoir in africian cup.

omani guy was sitting beside me and he was very ardent  as he is an  egyption

a fter the  game while  omani friend’s were   congarts me for the victory,

i was so happy with the spirit i felt regardless we won the game or not .

i felt how great the arabian People is   ….

Why Software Projects Fails ? December 12, 2007

Posted by essamabdelaziz in General.
add a comment

When I was reading a book about the Rational Unified Process, I found a useful nice piece of information that I would like to share with you. This piece of information states why the software projects fail.

The book says that the main reasons behind most of the software projects failures:

1. Incomplete Requirements:
The design and the implementation may start before even the requirements has been completed or signed by the customer.

2. Ambiguous Communication:
When the communication between the team members is ambiguous. The way the application which will be developed will be also ambiguous.

3. Architecture Problems:
It has 2 sub problems:
3.1. Complex Architecture:
Complex architecture may be hard to understand by the team designers. So wrong low level design and implementation may occur.
3.2. Inflexible Architecture:
When the architecture is not extensible. It will be very hard to accommodate with the new customer requirements.

4. Undetected Inconsistencies with External Systems:
Interfaces with external system should be well-defined before going into implementation to prevent “Developing the wrong system”.

5. Waterfall Model:
Waterfall model cannot succeed with customer software services. Customers always want to give their feedback periodically so Software models that are based on iterations and milestones are the most recommended with customer services. The (Rational Unified Process) is one of these software models.

This is all about.

 

http://jroller.com/HazemBlog/entry/why_software_projects_fails

 

Software Development Top 30 Mistakes August 30, 2007

Posted by essamabdelaziz in General.
add a comment

Welcome again

Today I found a very good article regarding software development

I passed the document to my mates and they like it so much

It affect them because every one saw him self  doing the same mistakes always

So read it carefully and don’t repeat the mistakes again

 

 

I have been developing software and web applications for nearly 11 years now.  Software development has come a long way since the days of Binary, Cobol, etc.  What still fascinates me about software development is the same mistakes made before, are still made today.  Below are the top 30 Mistakes that are made within the software development process.  It’s amazing to see that none of these have anything to do with the language itself.  

  1. Not understanding the user’s needs. Lack of user input, or not even asking.
  2. Underestimating the size of the project.
  3. Rushing through the planning stage, or avoiding the planning all together.  Code first, plan later! BAD!
  4. Not testing early enough, often, or at all!  Make it a habit!
  5. Choosing the “Cool” methodology at the time, vs. one that has worked in the past. Which leads into my next point…
  6. Not using a methodology.
  7. Letting a software developer run the software development project.
  8. Bored, unmotivated team!  You have to motivate your developers!  If you can’t motivate, don’t bother trying to lead.  Your team will fall asleep, literally.
  9. Planning on catching up later.  You won’t… don’t even think it!
  10. Non Source Control!  Ouch.. not good people… and no, just installing a software package is not it…
  11. Deciding to switch your development tools when you’re already into the project.
  12. Allowing feature creep.  Just say NO!  Everyone will be happier in the end.
  13. Omitting necessary tasks to shorten the project plan.  Really, what’s the point of doing this?
  14. Insufficient management controls in the development project.
  15. Lack of high level business sponsorship.
  16. Adding people at the end of the project to “speed things up”.  You will only slow things down…
  17. No unit testing.  Heck if you can do it, use Visual Studio Team Foundation Server and set up some automated testing nightly.
  18. Stressed out software developers.  If you have managed to perform even one or two of these software development mistakes, you will have a stressed out bunch of programmers to deal with!
  19. Lack of error handling.
  20. “Off by one” errors.  These happen a lot during the software development process.. *sigh*.
  21. Typos…  Just use option strict and explicit please..  during one software development project, which I was on as a consultant, they were getting ridiculous amounts of errors everywhere… turned out the developer couldn’t spell and would declare variables with incorrect spelling.. no big deal, until you use the correct spelling when you’re assigning a value to it…  and  you had option explicit off.  Ouch to them…
  22. No understand the deployment or hardware the software is to be installed on.  Ohhhh it’s for a Macintosh… lol.  Well hopefully not that bad, but you get the point.
  23. No naming style or code conventions.  Honestly it doesn’t matter what you use… as long as you are consistent with the rest of the team, and hopefully at least yourself.
  24. Using global variables everywhere.  These are NOT your friend and hog memory like nothing you have ever seen before!
  25. Not asking for help at all during the software development process.  If you’re stuck, don’t fight with it for hours on end!  Ask for help!
  26. Not commenting your code.
  27. Hogging all information to yourself.  You think you’re more valuable this way?  You’re actually not and there is a plan brewing to get you kicked off the development project, and possibly out of the company.  You might want to brush up your sign “Will code for pizza!”. 
  28. Performing database operations at the application layer instead of the database layer. Not only is this putting the processing juice on your application instead of your server, but you have put your database at risk of data integrity issues, and getting bad data!  Some of my hipster cool friends are always saying “It’s alllll good”, well, if your database can be caught saying this… and If everything looks good to your database, then you should be worried.  It is NOT all good!
  29. Not validating your data! Yikes…  Yes.. let’s just assume all the data is perfect! NOT!
  30. No load testing.  What.. This is supposed to run on 1,000 user’s machines through Citrix?  Interesting… Shouldn’t be an issue! lol… NOT.

Software development is tricky enough!  Make it easier on yourself by ensuring you do not make any of these mistakes.  Although it seems like a simple list of things not to do, it can make your life so much easier

http://www.realsoftwaredevelopment.com/2006/10/software_develo.html  

Following are my contact details. July 4, 2007

Posted by essamabdelaziz in General.
add a comment

 

Sorry guys  I will stop writing  for AwhileI will be on annual leave starting from 5th July, 2007 till 7th August, 2007.

 Following are my contact details.

Email – essam.abdelaziz9@gmail.com   during my leave starting from tomorrow till 7/8

What’s your project score? June 17, 2007

Posted by essamabdelaziz in General.
add a comment

The Standish group’s CHAOS report has a table of success factors:

Success Criteria Points
1. User Involvement 19
2. Executive Management Support 16
3. Clear Statement of Requirements 15
4. Proper Planning 11
5. Realistic Expectations 10
6. Smaller Project Milestones 9
7. Competent Staff 8
8. Ownership 6
9. Clear Vision & Objectives 3
10. Hard-Working, Focused Staff 3
TOTAL 100

The study is not new, but still is valid. This are the critical factors for a project success.
Mapping it to your current project, will let you focus on the areas that will improve your chances…
What is your current project score?

http://gabrielsw.blogspot.com/2007/05/whats-your-project-score.html

THE 13 CHARACTERISTICS OF SUCCESSFUL PEOPLE – June 7, 2007

Posted by essamabdelaziz in General.
1 comment so far

By Jeffrey J. Mayer - SucceedingInBusiness.com  

I’ve spent many years studying successful people and have identified the skills, talents, and characteristics that enable them to succeed. As you look at and study these skills, talents, and characteristics, you’ll realize that you possess many of them yourself.

Some of these skills and talents are more dominant than others and will play a greater part in your being, or becoming, a success in the business of life. These are the things you do well.

The things you do easily and effortlessly. These are your strengths. When you find you need a skill or talent you don’t have, just go out and look for a person or group of people with the skills, talents, and training you need.

Skills and talents that complement your own. These people will become your teammates, colleagues, co-workers, professional advisors, and friends. With these combined skills and talents organizations grow, prosper, and become successful.

These are the five things you’ll find every successful person has in common :-
They have a dream.
They have a plan.
They have specific knowledge or training.
They’re willing to work hard.
They don’t take no for an answer.

Remember: Success begins with a state of mind. You must believe you’ll be successful in order to become a success.

The following is a list of the skills, talents, and characteristics you’ll find in successful people: -

Successful People Have a Dream. 
They have a well-defined purpose. They have a definite goal. They know what they want.  They aren’t easily influenced by the thoughts and opinions of others.
They have willpower. They have ideas.  Their strong desire brings strong results. They go out and do things that others say can’t be done.
Remember: It only takes one sound idea to achieve success.
Remember: People who excel in life are those who produce results, not excuses. Anybody can come up with excuses and explanations for why he hasn’t made it. Those who want to succeed badly enough don’t make excuses.

Successful People Have Ambition. 
They want to accomplish something. They have enthusiasm, commitment, and pride. They have self-discipline. They’re willing to work hard and to go the extra mile. They have a burning desire to succeed. They’re willing to do whatever it takes to get the job done.
Remember: With hard work come results. The joy in life comes with working for and achieving something.

Successful People Are Strongly Motivated Toward Achievement. 
They take great satisfaction in accomplishing a task.

Successful People Are Focused. 
They concentrate on their main goals and objectives. They don’t get sidetracked. They don’t procrastinate. They work on the projects that are important, and don’t allow those projects to sit until the last minute. They’re productive, not just busy.

Successful People Learn How to Get Things Done. 
They use their skills, talents, energies, and knowledge to the fullest extent possible. They do the things that need to be done, not just the things they like to do.
They are willing to work hard and to commit themselves to getting the job done.
Remember: Happiness is found in doing and accomplishing, not in owning and possessing. Many years ago I was asked: “Jeff, do you like pleasing habits or pleasing results?” As I pondered that probing question, and squirmed in my chair like a worm at the end of a hook, I felt as if I had painted myself into a corner. A few moments later I answered: “I like pleasing results.” From that moment on my life changed. I began to do the things that were difficult, because they enabled me to achieve my goals.

Successful People Take Responsibility for Their Actions. 
They don’t make excuses. They don’t blame others. They don’t whine and complain.

Successful People Look for Solutions to Problems. 
They’re opportunity minded. When they see opportunities they take advantage of them.

Successful People Make Decisions. 
They think about the issues and relevant facts, give them adequate deliberation and consideration, and make a decision. Decisions aren’t put off or delayed, they’re made now!
Success Tip: Spend more time thinking and planning before you make your decision, and you’ll make better decisions.

Success Tip: When you don’t get the expected results from the decision you’ve made, change your course of action.  Decisions should never be carved in stone.

Successful People Have the Courage to Admit They’ve Made a Mistake. 
When you make a mistake, admit it, fix it, and move on. Don’t waste a lot of time, energy, money, and/or other resources trying to defend a mistake or a bad decision.
Remember: When people are wrong, they may admit it to themselves.  If they are handled gently and tactfully, they may admit it to others and even take pride in their frankness and broad-mindedness. But people become very defensive and angry when others try to cram their mistakes down their throats. If you want to learn how to overcome the fear of failure, overcome the procrastination habit, and become more successful by writing and reviewing your goals, you should 

Successful People Are Self-Reliant. 
They have the skills, talents, and training that are needed in order to be successful. Your thoughts, comments & opinions are appreciated. 

Successful People Have Specific Knowledge, Training, and/or Skills and Talents. 
They know the things they need to know to be successful. And when they need information, knowledge, or skills and talents that they don’t possess, they find someone who does possess them.

Successful People Work with and Cooperate with Other People. 
They have positive, outgoing personalities. They surround themselves with people who offer them help, support, and encouragement. They are leaders.

Successful People Are Enthusiastic. 
They’re excited by what they’re doing, and that excitement is contagious. They draw people to them because these people want to work with them, do business with them, and be with them.

create web applications that can run offline. June 4, 2007

Posted by essamabdelaziz in General.
add a comment

Google Gears consists of three modules that address the core challenges in making web applications work offline.

LocalServer LocalServer
Cache and serve application resources (HTML, JavaScript, images, etc.) locally
Database Database
Store data locally in a fully-searchable relational database
WorkerPool WorkerPool
Make your web applications more responsive by performing resource-intensive operations asynchronously

read more

comapre 2 date using javascript April 7, 2007

Posted by essamabdelaziz in General.
1 comment so far

function compareDates(Date1,Date2){

var now = new Date();var myDate1 = new Date(Date1);var myDate2 = new Date(Date2); // Get user date in mm/dd/yyyy format

 if(myDate1.getTime() >= myDate2.getTime())

   return false;

else

  return true; }

Extreme Programming April 6, 2007

Posted by essamabdelaziz in General.
1 comment so far

With Extreme Programming, developers working in pairs do software development. Two developers share the same workstation, taking turns using the keyboard. Does this mean half the output? No, development speed is not impacted by how fast you can type! The work of programming includes coding, thinking, designing, testing, listening, and talking. The following benefits are derived from pair programming:

All design decisions involve two minds 

At least two developers are familiar with that part of the system 

There is less chance that tests will be missed

Switching pairs enhances knowledge sharing even  

All code is reviewed all the time 

One developer is looking at detail while the other is looking at the conceptual

Switching pairs enhances knowledge sharing even further

All code is reviewed all the time

One developer is looking at detail while the other is looking at the conceptual

http://mooparmghor.com/blog/?p=160#respond 

stored procedeure? April 1, 2007

Posted by essamabdelaziz in General.
add a comment

 find under an example for stored procedeure

CREATE OR REPLACE
PROCEDURE PRO_ESSAMPROCEDURE

(InputParam1 IN VARCHAR2,InputParam2 IN VARCHAR2)
AS
begin
 update MY_Table_NAME
 set

Coulmn1=InputParam1,

Coulmn 2=InputParam2
 commit;
 end;