Crud and jad

2. (C REATE , R ETRIEVE , U PDATE , D ESTROY )

3. INTRODUCTION (CRUD)
The acronym CRUD represents the most
common SQL operations performed on a
database.
C
Create
MySQL
Statement
INSERT
R
Retrieve
SELECT
U
Update
UPDATE
D
Destroy
DELETE
Letter
Operation
3

4. CRUD ANALYSIS
• A good way to validate an ERD is to do a
CRUD analysis on it.
– CRUD is an acronym for create, retrieve, update, delete.
• These are the four basic operations that a
database allows.
– Part of checking a data model for completeness and
accuracy is making sure that all the CRUD functions
specified by the business scenario and the business rules
are represented in the ERD.

5. Create Operation
• Keywords to look for in the client interviews,
business scenarios, and so on are INPUT,
ENTER, LOAD, IMPORT, RECORD, and
CREATE.
• These all indicate that a record is created in
the database at this time. Review the
requirements for these keywords.
• Does your data model account for all these
functions?

6. Retrieve Operation
• Keywords to look for are VIEW, REPORT,
BRING UP, PRINT, FIND, READ and
LOOK UP.
• These all point to retrieving information
from
the
database.
Review
the
requirements for these keywords.
• Does your data model account for all these
functions?

7. UPDATE OPERATION
• Keywords to look for are CHANGE,
MODIFY, ALTER and UPDATE.
• These all point to updating information that
is already in the database. Review the
requirements for these keywords.
• Does your data model account for all these
functions?

8. DELETE OPERATION
• Keywords to look for are DISCARD,
REMOVE, TRASH, PURGE, and DELETE.
• These all point to deleting information that
is already in the database. Review the
requirements for these keywords.
• Does your data model account for all these
functions?

9. (J OINT APPLICATION DEVELOPMENT )

10. INTRODUCTION
•
Joint Application Development, or JAD, is a process
originally developed for designing a computer-based
system.
•
JAD is a technique that allows the developers, managers, IT
Professionals and end users to work together to build a
product.
•
It is a series of highly structured interviewed sessions and is
aimed to achieve project’s goal.

11. JAD SCOPE
•
The JAD should cover the complete development
life cycle of a system.
•
The JAD is usually a 3 to 6 month well-defined
project.
•
For large-scale projects, it is recommended that the
project be approached incrementally, and that
separate JAD's be used for each increment.

12. WHY?
•
JAD reduces the amount of time required to develop
systems since it eliminates process delays and
misunderstandings and improves system quality.
•
It also improves the quality of the final product by focusing
on the up-front portion of the development lifecycle, thus
reducing the likelihood of errors.

13. HOW?
•
•
•
JAD centers around a structured workshop session.
Participants get together in a room to discuss the
problem/project.
Everyone hears what the rest of the group has to say.

14. JAD STRUCTURE
•
They are less frequent
•
More structured, and productive
•
An agenda provides the structure
•
The facilitator directs the process
•
Visual aids clarify concepts being discussed and the
group dynamics, with constant feedback, stimulates
creativity

15. JAD PARTICIPANTS
•
Project sponsor
• Project lead
• Facilitator
• Scribe
• End users
• Developers
• Observers
• Subject matter experts

16. BENEFITS OF JAD
•
Enhanced communication and relationship between
business end users and IT personnel
•
Build consensus and ownership
•
Reduced system cost and development time
•
Reduced function creep
•
Improved system quality and productivity
•
Design cross-functional solutions
•
Helps project teams get focused and stay focused
•
Helps you get the right job done at the right time!

17. 1:en.wikipedia.org/wiki/Create,_read,_update_and_delete
2:jsj.sict.edu.cn/.../S05L04_Understanding%20 CRUD%20Requ
irements
3:ssyu.im.ncnu.edu.tw/course/CSDB/Unit10.ppt
4:www.ksinc.com/itpmcptools/JADGuidelines.pdf
5:en.wikipedia.org/wiki/Joint_application_design

18. THANK YOU