c= doc_zip7.jpg / gt;
Figure 2.2 ER diagram of the system (user entities)
Fig. 2.3 ER diagram of the system (address entities)
Fig. 2.4 ER diagram of the system (registration process entities)
the last diagram, figure 2.5, is shown entities related to entity medical card.
Fig. 2.5 ER diagram of the system (medical card entities)
2.2.2 The actors of the system. The behavior of the systemmodel a system the most important aspect is to capture the dynamic behavior. To clarify a bit in details, dynamic behavior means the behavior of the system when it is running and operating.only static behavior is not sufficient to model a system rather dynamic behavior is more important than static behavior. In UML there are five diagrams available to model dynamic nature and use case diagram is one of them. Now as we have to discuss that the use case diagram is dynamic in nature there should be some internal or external factors for making the interaction.internal and external agents are known as actors. So use case diagrams are consists of actors, use cases and their relationships. So to model the entire system numbers of use case diagrams are used.purpose of use case diagram is to capture the dynamic aspect of a system. But this definition is too generic to describe the purpose.in brief, the purposes of use case diagrams can be as follows:
- used to gather requirements of a system
- used to get an outside view of a system
- show the interacting among the requirements are actors
2.6 Use case diagram of the system
diagrams are the parts of the diagram above, and have more specific and detailed information.
2.7 Use case diagram of the system (Actors)
2.9 Use case diagram of the system (Patient)
2.10 Use case diagram of the system (Government)
. 2.3 Physical scheme of interaction of individual parts of information systemsection describes the physical schema interaction of individual components of the projected information systems. There are diagrams which demonstrate separate subsystems with their brief description. In the project are used the following methodologies: Repository and MVC Patterns, Code First, EF and Unit Testing.Entity Framework is a set of technologies in ADO.NET that support the development of data-oriented software applications. Architects and developers of data-oriented applications have struggled with the need to achieve two very different objectives. They must model the entities, relationships, and logic of the business problems they are solving, and they must also work with the data engines used to store and retrieve the data. The data may span multiple storage systems, each with its own protocols and even applications that work with a single storage system must balance the requirements of the storage system against the requirements of writing efficient and maintainable application code [5] .Entity Framework enables developers to work with data in the form of domain-specific objects and properties, such as customers and customer addresses, without having to concern themselves with the underlying database tables and columns where this data is stored. With the Entity Framework, developers can work at a higher level of abstraction when they deal with data, and can create and maintain data-oriented applications with less code than in traditional applications.addition to supporting a designer-based development workflow, EF also enables a more code-centric option which we call code first development. Code-First Development enables a pretty sweet development workflow. It enables you to:
- develop without ever having to open a designer or define an XML mapping file
- define your model objects by simply writing plain old classes with no base classes required
- use a convention over configuration approach that enables database persistence without explicitly configuring anything
- optionally override the convention-based persistence and use a fluent code API to fully customize the persistence mapping
Repository pattern is a data access pattern that abstracts away your data access code. Using the repository pattern, your web application can interact with a data source without knowing the specifics of that data source. Meaning, your web app talks to a repository and that repository is in charge or getting or updating data. The web application doesn t know anything about the data access because the repository is in ...
