Monday, 10 November 2008

OVP Gamma Group's take on Carlos Perez's 10 Fallacies

As a group excercise in class, we have been asked to review a list of 10 Fallies as discussed by Carlos Perez (as a follow-up to Peter Deutsch first who came up with his “Eight Fallacies of Distributed Computing” to debunk misconceptions about distributed computing).

My class group is GAMMA and we have chosen to post our analysis under the heading: "OVP Gamma Group" on the Wikipedia. The link is: http://dynamic/wiki/index.php

Below is the article in full:

OVP Gamma
From Wiki
Jump to: navigation, search
OLYMPIC VILLAGE – STRAIGHTFORD
NETWORK APPLICATION (GAMMA GROUP )
03 NOVEMBER 2008


Summary There are a lot of ideas in software engineering are considered as truth until someone pinpoints the fallacies. Peter Deutsch first came up with his “Eight Fallacies of Distributed Computing” to debunk misconceptions about distributed computing. I happen to have a list of my own. Here are 10 Fallacies of Software Analysis and Design. I happen to have a list of my own (Carlos Perez June 27, 2004):

These are the 10 Fallacies of Software Analysis and Design:

1. You can trust everyone Access ID badge :
Not a very good idea, because if everyone has unrestricted access, there would be no control or security. Cannot verify/authenticate in real-time the owner of the badge (staff, management, press, athletes and visitors) Information sent out/announced may not be correct/accurate, legal because it’s not edited and the announcer may not be authorised. Mobile communication – if everyone has security codes for communication, poses a security risk (Leakage in confidential information) Passwords must be protected in case the wrong people get online access and post harmful material on the web or steal confidential information from Olympic databases…. Handsets in hall-ways and public phone booths need to be configured to allow authorised access through a secure switchboard Satellite communication needs to be scrambled.

2. Universal agreement is possible:
It is not possible to agree universally; hence all policies need to be discussed, analysed and standardised. Every industry has its own software and network requirements…a universal agreement may limit these. Hence, will affect security and applications being developed/carried out. Limited by budget, conflict of ideas.


3. A perfect model of the real world can be created:
There is no ideal world – there will always be shortcomings in the systems in place. We need to plan for any failures in these systems (especially in relation to security, functionality, durability, efficiency, accessibility….. )

4. Change can be avoided:
We need to plan for change. Change will always occur – hence we need to have contingencies in place. Requirement, technology, hardware/software, expansion, unexpected risks

5. Time doesn't exist:
Time is always limited so this aspect needs to be addressed at every stage. Every project has a deadline, based on timescales. All applications have life-cycles that will determine their end-dates to the event(s)

6. Everyone can respond immediately :
Not everyone can respond immediately due to personal involvement in other activities. Time-difference will affect response to communication network.

7. Concurrency can be abstracted away:
Lots of events will be happening at the same time and they all need to be covered, updated and distributed/broadcasted.


8. Side effects and non-linearity should be removed:
People get tired of routine; hence there should be systems in place to initiate change. Interruptions (e.g. power failure) could happen at some stage during the event. Some form of entertainment should be in place to fill in for the lack of activity and provide an alternative.


9. Systems can be proven to be correct:
Systems have been known to be unreliable….weather forecasts, incorrect race results due to incorrect data input as well as inaccuracy in the systems that time races electronically.

10. Implementation details can be hidden:
We need to be transparent with codes and data to developers, and technicians, so that they can easily refer to records when they need to rectify problems and breakdowns in the system(s)


As reviewed by:
Lauretta Amata
Muhammad Fayyaz
Dhanvin Parekh
Jaydip Madani
Peter Omondi
(Gamma Group - Advanced Networking and Database Connectivity, LSBU)

Reference: Carlos Perez :”10 Fallacies of Software Analysis and Design”, June 27, 2004,[Online] available at: http://www.artima.com/weblogs/viewpost.jsp?thread=57224 (accessed Nov 2008-11-03)

Retrieved from "http://dynamic/wiki/index.php/OVP_Gamma"

No comments: