Wednesday, 13 October 2010
Introduction to Visual Studio 2010
Tuesday, 3 August 2010
Tuesday, 2 February 2010
Tuesday, 19 January 2010
Rapid Development Tools On The Move
Which web-based databases have native client support for the iPhone by Jane Mccarty
This could really extend the range, functionality and remit of your Application. For instance it would allow users' to input data in the field allowing real-time update of your data. It could also be used to display information for the customer such as real-time quotes or data presentation.
The benefit of having these on small mobile platform would include lower hardware costs and quick deployment, especially over a bespoke hardware/software solution such as traditional data collection PDA's.
Wednesday, 13 January 2010
Another Article Evaluating More Generally MS Office v's Opensource and Cloud Options...
Kiss Microsoft Office Goodbye: Three Alternatives to Office 2010 by Bill Snyder
Tool Evaluation
- Data model implementation
- Code generation
- Interface development
- Deployment
Zoho Creator | DB Dabble | MS Access | |
Data Model | Strong Entity Relationship Management features | ||
Code Generation | Deluge Scripting ‘WYSIWYG’ | Very limited scripting available | Not available |
Interface Development | Easy to create web based entry forms | Excellent graphical outputs for Data Easy to create web based entry forms | Easy to create forms and tables. |
Deployment *based on 50 Users’ | Based online. Anyone with an internet connection can access the application. Data stored online. Client may have privacy/security concerns. Low cost additional licenses’ - around £2 per User* Inability to share administration for a database without giving access to entire Zoho account | Based online. Anyone with an internet connection can access the application. Low cost additional licenses’ - around £6 per User* Data stored online. Client may have privacy/security concerns. | Can be used on any machine with MS Access on it. No Internet connection required. Large support network for both end user and developers. Data is stored securely or locally within a company or clients’ network. |
Tuesday, 12 January 2010
Thursday, 10 December 2009
MS Access
Below is a screen-grab of what I've been doing. Again I've customised the colours and inserted the logo from my blog to show how you could use it for corporate or small business purposes.
Tuesday, 8 December 2009
Access Introduction...
Initialy this tutorial helps me to create the data tables.
More to come...
Tuesday, 1 December 2009
Link with Branding.
I've used the same branding as my RDT blog, this would be really useful if you were presenting data to a client, you could include your company branding to give a really professional impression.
Initial thoughts on Dabble DB
Intial thoughts are that I would look to use ZOHO to collect Data via forms and then export it to Dabble to use the data to discover trends, opportunities and present the data to various audiences...
...more too follow...
Wednesday, 25 November 2009
Tuesday, 24 November 2009
Zoho Creator - Rapid Development Tool..
Here's the Link...
The Idea is that I'll be able to ensure that I'm not neglecting any subjects, aswell as giving me a better understanding of Zoho
It's pretty intuitive with plenty of drag and drop options. I'd like to embed it into a website and create a database from the results eventually.
Friday, 20 November 2009
Tuesday, 17 November 2009
Monday, 16 November 2009
Tuesday, 10 November 2009
Rapid Application Development
RAD was a reaction to the 1980's Structured Design approach. Structured Design was very rigid in its approach, required much documentation and instilled that the whole system design be planned and designed at the beginning of the project. This made it difficult to re-evaluate previous decisions.
RAD was designed to respond to these challenges and deliver a quicker, more flexible solution to client demands.
There are three main types of RAD:
- Phased Development
- Prototyping
- Throw-away Prototyping.
More on these to follow...
Tuesday, 27 October 2009
The 5 Steps of Normalisation
The 5 Steps of Normalisation
- List the 'unnormalised' data and identify repeating groups by placing them in ()
- Choose a key for the main group. This is the Unique Identifier.
- Extract the repeating group and give that a key.
- Identify and extract Partial Key Dependencies
Identify and Extract Non-Key Dependencies.
Data Modelling
Data-Modelling
– A data model is concerned with the question 'What data does the system need to store and what is the best way to store it?'
Data modelling uses two techniques to achieve this:
- Entity- Relationship Modelling (ERM)
- Normalisation
ERM Modelling is a top- down approach:
Normalisation is a bottom-up approach:
An Entity is any data object. This can be an object or a person. An Entity is any object that a system needs to store data about. Eg. Customer, Product
An Attribute is the data item or elements that make up the Entity.
The Occurrence of any Entity describes the Entity eg. Customer Name. The Entity can represent a number of Occurrences.
Primary Keys are unique identifiers. If a system is to work than we must be able to uniquely identify every Occurrence of an Entity.
Enterprise Rule is a rule the business imposes onto the system.
Relationships link the above.
4 Principles of Database Developing:
- Identification of Entities
- Construction of a process independent model of the stored data requirements
- Construction of a robust data model
- Construction of a logical model of the data
- Identification of Entities
- Identify
- List Attributes
- Put Data in Logical Order
- Eliminate Redundancies
- Investigate and Record Relationships
Exercise:
The Library System: Worked Example
A library keeps records of loans, books and members. It stores member's names, addresses, status (junior or senior), loan limit (number of books a member may borrow) and date of birth; members are given individual member numbers when they join the library. The library also stores information about its books: title, authors, publisher, publication date, ISBN and purchase price. As some books are very popular, the library often buys several copies of the same book. All loans are for three weeks. The library needs to be able to record, edit and delete member details; record, edit and delete book details; record loans and returns; and reserve books. Overdue notices are to be sent when books are overdue. It also wants its library system to automatically update member status. The system must also record the current price of a book.
The following enterprise rules can be applied to the library data.
- Individual copies of books are identified by library ID number; when recording loans, the library needs to be able to identify which copy of the book has been borrowed. The book itself, i.e. a specific title/author combination, is identified by its ISBN.
- Members are identified by member number
- Member status determines how many books a member may borrow – the 'loan limit'. To keep the example simple, we are ignoring issues relating to fines for overdue books.
Entities
- Book
- Member
- Loan
- Reservation
- Copy
- Author
Member Name
Address
ID Number
Date of Birth
Loan Limit
Book ISBN
Price – Purchase
Price – Current
Publication Date
Reservation
Monday, 12 October 2009
Tuesday, 6 October 2009
Rapid Development Tools
I've just started on the Business Systems Design course at Teesside University.