College of Business Administration
University of Sharjah Business Forum,
2011
Title
International School
Students
Sendos Nezar: U00011650
HAlA Albenni: U00014095
Supervisor
Dr. Mohamed Nour
ABSTRACT
Royalty car insurance company is dealing with easy tips sales agent in almost all of it is daily operations. The customer deals directly
with the agent when he/she needs any insurance service, like: buying a policy, renewing a policy, terminating a policy or requesting
payments for accidents (claims), so the interacting between the customer and the insurance company is very limited in this case.
In our project we have applied three of the mentioned insurance services: buying new policy, renewing policy and requesting payments
for accidents (claims) which we call them use cases. This project consists of three parts each part depends on the previous one.
In the first part we had implemented the following:
• A set of First-Cut Interaction Diagrams that reflect an initial implementation (realization) of your chosen use cases (SSDs).
• A First-Cut Design Class Diagram (DCD) that appropriately extends the Domain Model Class Diagram (DMCD).
In the second part:
To extend the project Part One by creating the following:
• A set of interaction diagrams that reflect the three-layered design by extending the first cut interaction diagrams you created in Part
One (add view & data access layers to the 1st cut sequence diagrams).
• A complete and fully updated and refined design class diagram that includes the three main types of classes from the three-layered
SDs: problem domain classes, user-interface classes, and data access classes. You must include use case controllers also.
• Code snippets that provide a first-cut implementation of ALL the classes in the design class diagram—the code should be in objectoriented programming pseudo code (or Javasyntax). Only the declarations are needed, no actual processing statements or method bodies
needed.
In part three (under process):
Providing a prototype implementation for only one use case (one interaction diagram). The prototype will be three-layered, with the
following components:
• A GUI (view) layer, providing a form-like interface for dialog with the user.
• A business logic layer that implements the required use case processing.
• A data access layer, with classes for interfacing with the database server.
• A database on oracle that includes a table for each domain (business logic) entity used
Title
Students
Supervisor
International School
Hamad Saaed 20710738
Abdulsalam Alwani 20710201
Nawaf Alawadi 20710197
Dr. Mohamed Nour
ABSTRACT
The aim of this project is to enhance the university registration system
.We discussed how the student add or drop a course and what procedure he/she should follow. First we explain the modified payment
procedure. Second how to add courses in a simple and friendly way. Third how to drop a course in the system without going through the
complicated procedures.
Title
Internet Security
Students
Sulafa Aqel 20720219
Sundos Kayali U00011776
Supervisor
Dr. Mohamed Nour
ABSTRACT
Introduction: Uos nursery is located on campus at the UOS. It has services offered to children of all University City staff and others from
outside the University ( seats are limited)
Problem : The registration system in the centre is so old(manual) and behind in all means which causes lots of trouble.They have two
choices :remain current manual system or new computerized system
Methods: proposed DSS System using MS access to store and retrieve data gradually by a small prototype(Ms access) ,define main
users,training sessions,and implementation
Results: using the new computerized system will solve many problem and provide security and advantages to nursery staff ,managers,
families,and the stored data files
Conclusion: manual system is good for people who don’t care about technology, however,we need to keep pace with the times and use the
latest technology in order to save time, effort ,make our lives more easier and gain profit quickly