Recommendations for the interfaces:-

hi friends ,
I have some recommemdations for the interface designing.
1. The all designing activities of the RMO system should be User-Centred. And while designing the system the user evolvement should be more so that the all end user will be familiar with using system efficiently even before it is launched.2. RMO design team should strictly follow the eight golden rules of designing user interfaces. 3. RMO’s Customer Support System Interface should concentrate on the visibility and affordance of the system.4. While designing the data entry and data keying interfaces forms those layouts should be simple and appropriate. And there should be appropriate use of text box, combo box, radio buttons, check boxes etc whenever required while designing the forms

Designing the interfaces For system

hi friends,
Now we are in final part of our project that is User Interface Design
Following are the some rules we have follow during the design activities.
Design activity includes the designing of the System Interfaces and User Interfaces. System interfaces handle inputs and outputs that require minimal human intervention. Whereas the User interfaces handles inputs that involve a system user directly. And User interfaces require the user interaction to create inputs and outputs. The user interfaces is everything the end user comes in contact with while using the system. To the end user of a system, the user interface is the system itself. It is fact that designing the user interface is to design the system. Therefore the user interface should be given more priority in early development of the system. The term human computer interaction (HCI) is generally used to refer the study of end users and interactions with computer. Visibility and AffordanceVisibility means that control should be visible so users know it is available. Andaffordance means that the appearance of that control should suggest its functionality.

Recommedations for the application architecture :-

Hi friends,
Recommendations for Application Architecture:-

1. Single-Computer architecture is not useful for the RMO’s new Information System even though it can perform work at highest speed.
This is because when we look at the future of the RMO. We can surely say that within next 5 years RMO database will increase rapidly so that even largest mainframe cannot perform all required processing, data storage and data retrieval tasks in network environment.

2. On other hand, today as most of operating system and communication software became more sophisticated. So therefore now it is possible to connect several servers into cluster of servers can handle even greater workloads than single main frame computer.

3. For RMO we recommend that multicomputer architecture will be very useful and efficient.

4. Multicomputer architecture should be preferred because we can share the processing load through specialization of function to specific type of server.

5. We recommend that each computer system should be optimized to role that it will play in combined system.

6. We strongly recommend that RMO should adapt to distributed architecture rather than centralized architecture.
This is because sometimes storing whole data at one location is not safe.

7. The main advantage of distributed architecture is that we can create the backup of database to any other location in case of emergency.
And this will save us from disaster of loosing database completely.

Application architecture

Application architecture :-It is a description of the integrated information system that the organization need to carry out its business functions.
It involve the two types such as Single tier and Multi tier computer.Multi tier computer architecture subdivided into clustered and multi computer architecture.
In clustered architecture all servers are of same type or of same company. but in multi computer the all servers are of different types and configured according to their functions.

Recommendations For the RMO database architecture :-

1. According to us, the single server database is not useful for the RMO because of its widespread offices over different geographic locations.

2. The Replicated Database Servers system will be very useful and convenient for RMO. As this system makes information system more fault tolerant.-During peak hours when one server is unavailable, client can redirect their request to another server.
- Load balancing can be achieved by interposing transaction server between client and replicated database servers.

3. But partitioned Database server system also has some advantages over replicated database server i.e. this system doesn’t need of periodical Database Synchronisation.

4. We will recommend adapting both Replicated Database Server and Partitioned Database Server.

5. Combined use of the two systems will make RMO system more efficient and reliable.

Recommeded types for the RMO database

hi friend ,
I have done some research on the database architecture. and I found that the combination of replicate and partitioned server database.
Replicated Database Server: This can eliminate delay in accessing distance servers by a replicated database server. Each LAN has its own database server, so each stores a separate copy of the needed data
Partitioned database server: This server can minimize the need for database synchronization among the multiple database servers. In this different group of clients can assess each partition.

Database for RMO

hi friends, i found following very appropriate database type
Federated database server:
Some information system are best served by a federated database server which is mainly used to access data stored in database with incompatible storage models or DBMSs. A single unifies database schema is created on a combined database server. That server acts as an intermediary between application programmes and the database residing on other server. Database request are first sent to the combined database server, which in turns makes appropriate request of the underlying database server. Results from multiple servers are combined and reformatted to fit the unified schema before the system returns a response to the client.
This can be extremely complex. This also tends to demand considerable computer hardware and network capacity, but there expense and management complexity are generally less than would be required to implement and maintain application programme that interact directly with all of the underlying databases. This is used to implement a data warehouse. The fig 5 is the federated database server architecture.

Meeting On Project Progress.,.

hi friends,
Today we had a meeting about Project Progress. And so far everybody have done most of the art of their assigned work. Today I received the Major System Component requirement from Mr.Alam and application Architecture from Mr.Chirag. and we decided that for every ones work i will write the all recommendations for the report. and will also design key interfaces for the system.

Databse Tables..ERD

Hi ,
In constructing the relational database we need to understand the concept Entity Relationship Diagram(ERD).
The main concepts about ERD are as follows:-
There are three basic elements in ER models:
-Entities are the "things" about which we seek information.
-Attributes are the data we collect about the entities.
-Relationships provide the structure needed to draw information from multiple entities.