2010 23 Aug
iPhone 4 Propaganda Strategy… Revealed!!
In the past year, HALF of the planet had one topic in common: iPhone! it doesn’t matter if they were saying “I want one”, “I love iPhone”, “I Hate iPhone”, “iPhone Rocks”, “iPhone Sucks”…. They were talking about it… so the Top Secret Attraction Strategy of iPhone WORKED!
Apple Inc. is by far a “Different” Company especially in how they treat their customers; They “Think Different” and they do things differently!
2010 13 Aug
Software development process should take into account many considerations. In general, we can divide them into two categories: functional which correspond to the main functionality of the software, and non-functional as security, persistence, maintenance, etc. This paradigm of separation leads to improve the modularity of software.
Aspect Oriented Programming (AOP) is a new programming paradigm dealing with this concept. An aspect is a software entity implementing a specific non-functional part of the application.
It brings together joinpoints, pointcuts and code advice. A joinpoint is a point in the program where aspects can act, e.g., methods, constructors, and classes, etc. pointcut is an element linked to the program execution flow where it is possible to graft an aspect around. From an abstract point of view, a pointcut defines a set of joinpoints, a "cut". The code advice defin
2010 13 Aug
With the evolution of technologies and software systems, applications and their interfaces had become more interactive leading to make the concerns of solution architects more critical.
Performance is one of these concerns, responding in real time to the users requests became critical especially in web and network based applications.
Service Oriented Architecture is widely spread now because it maintains an acceptable level of interactivity in the presentation layer of rich internet applications, and assures an acceptable level of distribution in the data layers.
In this kind of applications and in order to respond to a user request you may need to do multiple calls to a remote service that will clearly affect the performance and which depends on obvious factors: latency and Throughput.
2010 08 Jul
PERT introduces risk onto the project schedule via 3-point estimates of activity duration when deterministic time is unaffordable. This practice propagates the notion of risk over the scope of the project and allows for a feedback into the financial decisions pertaining. We shall start by introducing the risk profile of the activity and its rationale then proceed to its effect on the whole schedule and deadline. After that, we'll discuss various risk models implementation (analytical, simulation, ...) and the available commercial software. Finally, stochastic cost analysis impacted by risk is reviewed in light of project decision making.
Location: Holiday Inn – Dunes, Verdun Street
Time: 7:00 – 8:15
PDU: 1 Unit per lecture
Date: Thursday, 22 July 2010
PDU:
2010 08 Jul
I searched the internet about the best ways to represent the use cases and the user stories in agile project, I faced many points of views that fit all in the same basic standard format:
|
As an <actor> I want to <action> so that <achievement> |
This way of representing a user story is indicative and helps explaining the needed requirements to team members, but in big systems where the number of user stories is huge I see that the above representation becomes complex and less indexable and hard to manage, so I did more researches and consultancy work what lead me to refine the representation to a more indexable way to create the
2010 28 Jun
Currently, I am initiating a new project and building its team and giving the responsibilities and missions for the people working with me.
Without any researches or waste of time, and as always in such situations I came back to the God of leadership John Maxwell, who says “to build a successful team, you have to add people who make things happen, you need a catalyst in your team”.
If you ask a football player who is the best player in the game, 90% of them say do you want us to exclude Maradona?
If you are the coach of the world's greatest football team and you have a free kick in the last 5 seconds of the match, for which player do you give the
2010 09 Jun
What?
Software application architecture is the process of defining a structured solution that meets all of the technical and operational requirements, while optimizing common quality attributes such as performance, security, and manageability. It involves a series of decisions based on a wide range of factors, and each of these decisions can have considerable impact on the quality, performance, maintainability, and overall success of the application.
Why?
Like any other complex structure, software must be built on a solid foundation. Failing to consider key scenarios, failing to design for common problems, or failing to appreciate the long term consequences of key decisions can put your application at risk. Modern tools and platforms help to simplify the task of building applications, but they do not replace the need to design your application carefully, based on your specific scenarios and requirements. The risks exposed by
2010 08 Jun
Leaders are the influencers of people around them; they are the people who lead to accomplish great targets and goals. A team leader should have a dream, and as much as the dream is SMART the leader will be successful and close to make this dream real.
No one can accomplish big things alone, even God has a team of angels around him, so to do great things you need great people that help you do it.
Normal people are easy to find, but not everyone deserves being in your team. If you are building a dream team to accomplish something big, you have to gather special people around you.
So if you want to go and do some researches at Mars planet for example, you can’t having a team member who hate flying, it’s critical while building your team to gather people who have the ability and creativity to help accomplishing dream goals and targets.
It’s clear that having a dream is not enough to accomplish great things, it’s important to ask t
2010 07 Jun
In traditional projects, and the old life cycle management methodologies, the requirements changes were so hard, and the teams try to resist it as possible. So the detailed requirement catching was the first goals of project. So to minimize the changes in the requirement team shall include whatever they can imagine in their analysis and have to see the and predict the coming path for the software in order to minimize the final cost.
In contrast agile methodologies easily respond to changes, they are built on the base that requirements evolve, and it’s impossible to catch all the requirements even if you analyze and design a project for a long time.
In agile projects the requirements evolve but he timescale is fixed, so if an amount of work will be added
2010 04 Jun
OBJECTIVES
Highly motivated with extensive experience in solution development. Flexible as regards moving from project to project and in assimilating new technologies and integrating them with the existing solutions. Proven team leadership skills, now looking to continue making a significant contribution within the software development field.
EMLOYMENT
Jan 2010 – Present
ArabiaGIS - Solution Architect
In Addition to my software development responsibilities I am playing the solution architect role since January 2010.
May 2008 – Dec 2009
ArabiaGIS - Senior Software Developer
Software developer using the latest .Net frameworks and ESRI GIS technologies. I’m responsible of writing technical requirements, technical design, and codes.
Read more >>