Dear Omeco Solution

We would like to express our admiration for the professioncy in

which you prepared the analysis of the databases of the Sudanese
Agricultural Council. We would like to make some remarks on the analysis.
We will also show what we expect to be included in the analysis report.
Remark on Analysis
Non-functional requirements: it’s not clear and not complete
Mechanism of operation of the system
Section I: Registration of individuals: you don’t mention that system
import Certificates information from the minister of higher education and
scientific research - general administration of admission. To retrieve
academic qualification
And we think it should appear in the diagram in page 7 (sequence of the
classification process) instead of entering academic qualification he/she
should enter Certificate number then send number to Minister of Higher
Education to return with Certificate information
 You don’t mention the operation of pay through the application. You
mention only the operation of check for recipe number issued by third
party
Section II - Registration of institutions
 Before attaching the signed contract he/she should enter the Engineer
number and system will bring the engineer information from database.
To insure that the engineer is registered in the SAC. Otherwise he cant
complete the registration
 The operation of bay through system and third party.

Other DATABASE (Except Registration)

 No Normalization even 1NF
 No Class Diagram
 Flat Design for Database table (One table per Entity)
 Expected to involving in analysis beside above mention
Assumptions and dependencies associated with database design that may
relate to topics such as software, hardware, operating systems or user
attributes
Constrains description of Constrains or limitations that have a significant
impact on the design of the database system).
Risks (description of risks associated with database design and proposed
migration strategy).
here is also no justification for the choice of design that affects the purpose
of the database, include the operating system (platform) and database
management system and any information related to database design
decisions (such as data transfer plan and SLAs), Include:-
 The basic elements that affect the design and describe the main
functions or non-functional requirements affecting the design.
Indicating design decisions that meet the requirements outlined in the
tender (eg performance, availability, security and privacy)
 Functional Design Decision
Demonstrates how the database responds to the requirements that the user
has requested. Including the inputs to be received by the database and
outputs (such as reports, messages, response methods, etc.) and description
of general types of operations (sequential or random processes, whether
introduced, updated or deleted):-
 Database management system choices: Including the selected
database management system specifications and the justification for
this choice.
 Options to secure and ensure the privacy of the database: Includes a
general classification of users and their powers to access and options
to secure the database and ensure its privacy
 Design options for performance and maintenance: Describe how the
performance and availability requirements have been met under the
server / client architecture, updates and maintenance of the main
 database file and how they will meet the concurrency conflict
requirements (eg how to divide data to support more than one
application or to update). In addition to the supporting the service
level agreements, describing the strategy of buffer storage and
recovery, including the data and distribution strategies of operations
during storage and recovery.
Detailed aspect of the design
A description of the design of all system-related DBMS files and any non
RDBMS files but they are closely related to the database design. And that
include:
 Logical data model (LDM) with ERD this model
 The physical data model (PDM) and the ERD
 Data dictionary which describe data types, sizes, sources, constrains,
verification rules, maintenance possibilities (for CRUD operations),
control requirements, data masking, expected data size, data life
expectancy, data lifecycle management strategy, archiving strategy,
output and aliases. In addition to indexes required for data objects.
Planned implementation factors (such as distribution,
synchronization, etc.)
 Description of the data structures used to store and process data along
with the description of the data structures of the main parts of the
database including data structures passed between components. Lists
all database objects including stored procedures, functions, and
function parameters. For functions explain the function inputs and
outputs.
Managing and Monitoring the database
 roles and responsibilities
 Configure database management system
 Database support software
 Security and privacy
 Performance monitoring and database efficiency (such as data
transfer needs, data formats and functional outputs)
 Backup and restore