Friday, 24 April 2009

Rehearsal of presentation

Hi friends,
Today we have done our rehearsal of group presentation.
and I pleased  that everybody did well. and most important that we manage to finish our presentation in given 10 minute time.
So far our group had done very good job and hope we will do well on 27 Apr .
I request everybody be prepared on Monday and don't late. please come 15 minute before decided time. And friend please follow the standard dress code for the presentation
ok bye see all of  you  on Monday 27Apr.

Tuesday, 21 April 2009

Presentation Planning

Hi friends,
today we received the presentation from Mr.Chirag.Today we have done the planning for the presentation. we have decided who will do what? who will give intro? who will finish the presentation?
So friends during these week prepare for your given task and we will have rehersal on  24th of Apr.
so be prepare for the rehersal.

Group meeting

hi Friends ,
Today we have finished our meeting to discuss about the presentation. we have decoded to prepare the presentation in miscrosoft powerpoint. 
In this meeting we all agreed that in order to prepare the presentation everybody have to prepare a 2 slides about what they did in the report on  system design.
and we decide that then Mr.Chirag will collect everyones work and he will design the final  presentation before21st of Apr.

Saturday, 11 April 2009

Presentation Prepration

Hi friends,
We just submitted our report on the system design for RMO.
Now in second part of the assignment we have to prepare the 10 minute presentation of solution for the RMO.
To discuss about the presentation we have arranged a formal meeting on coming Tuesday in the library.next meeting is on 14 Apr.

Thursday, 2 April 2009

Final submission

Ok my friend we have done the most of the work now and we will collect everybodies work and we will make the final report. and the Mr.Alam will do the executive summary for main report.
thank you my friend for your contribution to this project.

Tuesday, 31 March 2009

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

Sunday, 29 March 2009

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.

Wednesday, 25 March 2009

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.

Friday, 20 March 2009

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.

Monday, 16 March 2009

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.

Thursday, 12 March 2009

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.

Sunday, 8 March 2009

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.

Thursday, 5 March 2009

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.

Monday, 2 March 2009

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.

Friday, 27 February 2009

Work recieved

hi,
It is great pleasure that i received the some part of work that they are assigned to. I received the Major System Component requirement from Mr. Alam. And I received the Application Architecture from the Mr.Chirag. And I received the database table proposal from Mr.Laxchhuman yesterday.
And we will discuss about the all reports tomorrow

Wednesday, 25 February 2009

Sequence Diagram..

Hi friend,
I found particulary interesting that Sequence Diagram are very important in system development. Here is the some information about sequence diagram.
A lifeline in a sequence diagram represents an object and shows all its points of interaction with other objects in events that are important to it. Lifelines start at the top of a sequence diagram and descend vertically to indicate the passage of time. Interactions between objects – messages and replies – are drawn as horizontal direction arrows connecting lifelines. In addition, boxes known as combine fragments are drawn around sets of arrows to mark alternative actions, loops, and other control structures.

Saturday, 21 February 2009

Traditional versus OOA lecture Review-3 Use case Realization

hi ,
today I will discuss on the various attributes of OOA.
Use Case realization:-The process of elaborating the detailed design with interaction diagrams of particular Use Case.
Design patterns:- Standard design techniques and templates that are widely recognised as good practise.
Sepration Of responsbilities:- a design principle to segregate classes into separate components based on the primary focus of the classes
Dependancy Relationship :-a relationship between packages, classes, or use cases that indicates a change in independent item will require a corresponding change in dependant item.
Sequence diagram:- Sequence diagrams map the scenarios described by use cases in step by step detail to define how objects collaborate to achieve your application’s goals.

Wednesday, 18 February 2009

Traditional versus OOA lecture Review-2

hi friends,
I found some valuable information about OOA and I would like to share it with you.
OOA to system development views Information System as a set of interacting objects that work together to accomplish tasks.oblect can be described as the thing in the computer that respond to messages. The use of object oriented approach began with development of Simula programming language in Norway in 1960s.
And in 1970,the SmalTalk language was developed to solve problem by creating graphical user interfaces(GUI) that involved "Objects" such as pull down menus,buttons ,check boxes.
since then object oriented approach became popular and successful.

Monday, 16 February 2009

Traditional versus OOA lecture Review-1

Hellow my friend,
Today Hui gave lecture on the different approaches in system development i.e on traditional approach and Object Oriented Approach.
From this lecture I realised that traditional approach based on techniques to develop IS with structured and modular progamming. The key concept of structured program is that it has one beginnign and one ending.

Saturday, 14 February 2009

Network Integration Review ..2

hi friends,
Following major steps involved in network integration.
If existing network is not sufficient enough to support new system. Then executive planning required for the significant expansion, new communication protocols and modifying security protocols. Network Administrator have to play key role in acquiring of the new capacities and making any configuration changes to support the new system. As he or she is only one who understand the existing network and other network-dependent applications operate. The analyst’s role is to provide network administrator sufficient information and time to enable system development, testing and deployment.

Thursday, 12 February 2009

Network Integration Review ..1

Hi friends,
Yesterday I read new concept involved in network architecture plan and that is Network Integration.Many organizations such as RMO rely on networks to support many different applications
During the development and integration of new network existing systems are not disturbed as much of important data associated with older system. First of all we have to make sure that existing network capacity is sufficient and only minimal charges required such as adding creating connection for the new servers or modifying routing and firewall configuration to enable new application layers to communicate.

Monday, 9 February 2009

Netwok Architecture Discussion

hellow my friends,
As we ddecided i have done some researsch on network architecture.I realised that RMO can afford set up LAN over small distances. But in order to set up WAN there is lot of initial cost and maintaince cost as well. I recommed that its better to set up WAN on contract From companies such as AT&T and Sprint.
I will need some suggestions and improvement in Network Architecture Plan.

Sunday, 8 February 2009

Redistribution Of tasks

hi ,
Today we have done the general meeting about the project progress. And reslult is that one of my group mate found it difficult to do the Network Architecture. So there for as a group represntative i decided to do that task.An di shifted one of my task to him.

Friday, 6 February 2009

The meeting on Project Progress

hi friend ,
Today we had group meeting about progress of project. and so far everybody contributed for project. and everybody agreed that I will do the recommendations for the everybodies work. and Chirag will do the table of content. and Mr. Alam will present the meeting of all group meeting so far.

Wednesday, 4 February 2009

Initiatives for the design

hi,Today I had done some research on the access book for self training. I found the book Aceess For Dummies very useful. And I will spend my time reading this book in order to grasp the concept of the Designing Interfaces.

Monday, 2 February 2009

Database Tables Review

hi,In lst meeting we have created the work breakdown structure and distribited the different tasks to group members. Mine task is to construct the database tables and design the forms in access. I took this task because i thought that i am caable of designing the appropriate interfaces for the RMO system.

Thursday, 29 January 2009

Project plan and minutes of meeting recieved

hi today i received the minutes of the meeting from Mr. Alam by email attachment. and the project plan was done bye me yesterday and i also send that both to my all group members, so that they can go ahead to do their assigned tasks.

Tuesday, 27 January 2009

Group meeting

We start our course from January 26. Our first group meeting was at 11.00am in the library.The persons present for the meeting were as follows
1. Mr.Rohit Deshmukh
2. Mr. Mahbubul Alam
3. Mr.Chirag Limbachia
4. Ms. Azita Pourbakhtiar
In this meeting, we mainly focus on project plan and the distribution of work within the group members.
The another topic was about setting out the primary and foreign keys within the tables.Mr.Alam was taking minutes of the meeting. He is responcible to send minutes to all members.
and I will do the proect plan.
g will be on Feb 2 .

Monday, 26 January 2009

Introduction to Report 2

hi Dear friends,
In last Group Report we did our best. From today we have to work on the second group report. Today we have to group meeting at 11am at library. In this meeting we will decide what we going to do ? and how we going to? Please read the sceanario first before coming to meeting. So it will be easy to start our Project planning directly.