Evaluation 2

The reason I chose to use Microsoft Access 2007 is because I felt that the software was easier to use than the other recommened programmes. I have also worked with access on previous occassions so I know more about the software then on other applications. I also feel that Access has better features then the other two recommened programmes. I did not think my 2nd project worked as well as my first project because I did not have as much time as I did on the first project. I still feel that my data base works well and meets some of the assessment brief.

The reason I choose the method prototyping is because I think it is an easier method to do because you only have to create one version for the user, if i chose one of the other methods then I would have had to keep contacting the user. This would have wasted too much time, so I feel I have chose the right method. I followed all the stages correctly within the method by doing the planning first, then analysing, designing and implementing.

Exhibition Guest List Management System- ICA project 1

The reason I chose to use Microsoft Access 2007 is because I felt that the software was easier to use than the other recommened programmes. I have also worked with access on previous occassions so I know more about the software then on other applications. I also feel that Access has better features then the other two recommened programmes. I feel that my first project has worked well and my database works correctly and has met the criteria of the assessment brief. If I had longer than I may have added Macros in to the database and presented the reports better. The relationships link well within my database, also the tables work correctly and are all linked as they should be. I have shown the information I needed on the queries and that has worked well by bringing the correct information up. I also feel that the forms and reports have worked well. The reason I choose the method prototyping is because I think it is an easier method to do because you only have to create one version for the user, if i chose one of the other methods then I would have had to keep contacting the user. This would have wasted too much time, so I feel I have chose the right method. I followed all the stages correctly within the method by doing the planning first, then analysing, designing and implementing.

Zoho Creater Tool

It is easy to implement a data model by using Zoho Creater Tool because the user clicks on create new application and enters the application and form names. The user then selects the time zone that they are in, and then creates a new application. The user then drags and drops the fields that they are going to be using within the data model.

normalisation

5 steps for normalisation:

1) List the un-normalised data and identify repeating groups (in brackets).
2) Choose a key for the main group.
3) Extract the repeating group and give that a key.
4) Identify and extract partial key dependencies.
5) Identify and extract non key dependencies.

For the 0NF i am going to list the un-normalised data.

0NF:

Order

Customer No
Name
Address
Date
Salesman No
Salesman Name
(Item No)
(Description)
(Quantity)
(Price)

Order Value

1NF:

Order

Customer No
Date
Name
Address
Salesman No
Salesman Name
Order Value

Order Item

Customer No
Date
Item No
Description
Quality
Price


2NF:

Order

Customer No
Date
Salesman No
Salesman Name
Order Value

Customer

Customer No
Name
Address

Order item

Customer No
Date
Item No
Quantity

Item

Item No
Description
Price

3NF:

Order

Customer No
Date
Salesman No
Order Value

Salesman

Salesman No
Salesman name

Customer

Customer No
Name
Address



Item

Customer No
Date
Item No
Quantity
Item No
Description
Price

Examples of normalisation and entity relationships

Normalisation

http://www.sqa.org.uk/e-learning/MDBS01CD/page_26.htm

http://sandbox.mc.edu/~gwiggins/syllabi/csc415/normalization-examples.html

Entity Relationship Diagram

http://www.smartdraw.com/resources/tutorials/Entity-Relationship-Diagrams

http://www.umsl.edu/~sauterv/analysis/er/er_intro.html

http://www.cs.sfu.ca/CC/354/zaiane/material/notes/Chapter2/node8.html

Rapid Application Development

1) Less Documentation.
2) Faster Delivary Time.

Iterative Builds

1) Phased: Customers uses version 1,2 etc.
2)Prototyping: Customer views version 1.

Iterative Design:

3) Throwaway Prototyping: Design version only.

Prioritising Requirements:

Two Functions:

1) Version release to customer as early as possible.
2) If expectations are high but budgets are low-product must contain the essential elements.

Difficulties:

1) Customers want everything in version 1.
2) For customers to set priorities.
3) Functionality is interlinked and hard to be seperated.

Sample Requirments Scales:

High Priority: Product not acceptable without this function or feature.
mission critical.
required for next release.

Medium Priority: Supports necessary system operations. Required eventually but not immediately.
Would enhance the product.

Low Priority:Nice to have if budget allows.

Steps:

1) List all the features/functions contained in the requirements.
2) Assocaiate each one with a priority category and state a reason why.
3) Sort the list into a descending order of importance.
4) Agree final list with customers.
5)Group features/functions in to versions.

RAD

Planning/Analysis/Design/Implementation
Phases-Steps-Technique-Deliverable

Phased Development: Planning and Analysis. For system version 1 analysis, design and implement, then for version two analysis, design and implement, while the user is using version 2,version 3 will be created. system version 3 includes analysis, design and implementation.
Prototyping: This involves planning, then analysis, design and implementation are carried out at the same time in order to get system prototype. the system protype then needs implementating for the final system.
Throwaway Prototyping: This involves planning and analyis, then analyis, design and implementation is carried out at the same time. then design prototype. The final design is created and then implemented in to the system.