Nt1310 Chapter 4

2079 Words5 Pages

Chapter 4
Previously we have discussed the detail study of the system that analysis the requirements . While the requirements specification activity is entirely in the problem domain, design is the first step in moving from the problem domain toward the solution domain. Design is essentially the bridge between requirements specification and the final solution for satisfying the requirements[]. In this chapter we will produce a model that represent the system which can be used later to build the system. In the next sections we are going to discuss the architectural design of Smart Course. The architecting process can be thought as a decision making process in which the appropriate decisions must be made. Upon to that we will answer and clarify …show more content…

Smart Course is a distributed architecture that organized as a set of services and associated server and clients access these services. According to that, client/server is suitable for representing this computing. Client/server is a distributed software architecture in which systems are divided into autonomous processes, where a client sends requests to a server and that server sends responses as an answer to the request to that client[1]. When creating a distributed client/server system there are several strategies on can use to divide the logical layers over processes. A logical layer will be discussed later in the next section 4.4 while in this subsection we describe a physical layer. A physical layer is called a tier. Tiers describe the physical distribution of the functionality and components on separate servers, computers, networks, or remote locations. In the past, several strategies were implemented with different degrees of success. In the next paragraphs several tier-models are introduced.
1-tier : all the logical layers are putted into one physical layer. It is not a distributed model but mentioned here for completeness. Applications that presented to end user are used a 1-tier model like Microsoft …show more content…

There are three main styles which are mostly used:
1- The repository model: Sub-systems making up the system should exchange information so that they can work together effectively.
2- The client-server model: is a system where the system is organized as a set of services and associated servers and clients that access and use the services.
3- The layered model: organize the system into layers, each of which provide a set of services.

Our choice to organize the system is the layered model. Smart Course is suggested to be developed. The layering will make developing easy as it is support the incremental development of the system. Smart Course can be used as a template by other university because the layered organization is changeable more easily.

All logical layers together form the application. Each layer is responsible for a specific task. This logical layers does not need to be the same as physical layers. We mention a 5 different layers in the software (see figure 4.). The layering shown here is a reference model. In actually, when implementing the system the layers will not be clear as what mention here.

Figure 4. System

Open Document