Development of an IS database for a construction company. IBS has developed an integrated capital construction management system

08.03.2020 TVs (Smart TV)

Introduction3 CHAPTER 1. DESCRIPTION OF THE SUBJECT AREA5 1.1. Study and system analysis of the subject area "Construction organization"5 1.2. The main stages in the formation of requirements in the design of an information system8 CHAPTER 2. DEVELOPMENT OF THE CONCEPT OF THE INFORMATION SYSTEM "HOTEL BUSINESS"10 2.1. The choice of methodology for modeling the subject area10 CHAPTER 3. DESIGN OF THE INFORMATION SYSTEM "BUILDING ORGANIZATION"18 3.1. Development and approval of terms of reference18 3.2. Development of a case diagram22 3.3. Development of a contextual class diagram 29 3.4. Development of a sequence diagram33 3.5. Development of an Activity Diagram34 3.6. Development of a design-level class diagram35 3.7. Development of the placement diagram38 3.8. Creating a database39 3.9. Logical database model implemented in ERwin.40 3.10. SQL queries to the created database41 Conclusion43

Introduction

A construction organization is engaged in the construction of various kinds of objects: residential buildings, hospitals, schools, bridges, roads, etc. under contracts with customers (city administration, departments, private firms, etc.). Each of the listed categories of objects has characteristics that are unique to this or several categories: for example, the characteristics of residential buildings include the number of floors, type of building material, number of apartments, for bridges, the unique characteristics are the type of span, width, number of traffic lanes. Structurally, a construction organization consists of construction departments, each construction department works on one or more sections, headed by section chiefs, to whom a group of foremen, foremen and technicians is subordinate. Each category of engineering and technical personnel (engineers, technologists, technicians) and workers (masons, concrete workers, finishers, welders, electricians, drivers, locksmiths, etc.) is also characterized by attributes characteristic only of this group. foremen. Foremen are selected from among the workers, foremen, foremen, heads of sections and departments are appointed from among the engineering and technical personnel. One or more facilities are being built at each site, and one or more teams are working at each facility. Having finished the work, the team moves to another object on this or another site. The construction department is assigned construction equipment (cranes, excavators, bulldozers, etc.), which is distributed among the facilities. The construction technology of an object involves the implementation of a certain set of types of work necessary for the construction of this type of object. For example, for a residential building, this is the construction of a foundation, brickwork, laying water supply, etc. Each type of work at the facility is performed by one team. To organize work at the facility, work schedules are drawn up, indicating in what order and in what time frame certain works are performed, as well as an estimate that determines what building materials and in what quantities are needed for the construction of the facility. Based on the results of the work, a report is drawn up indicating the timing of the work and the actual costs of materials. The purpose of the course work is to study the methods and tools for designing information systems and technologies, modeling the information system of a construction organization, which provides effective management and development of the enterprise. To achieve this goal, the following tasks were solved. Analysis of proposals in the field of improving the system of enterprise indicators to identify trends in this area. The choice of key indicators as attributes of the information model of the activity of a construction enterprise. Development of UML diagrams to perform modeling of an information system. The subject of the study is the performance indicators of a construction company that provide effective management mechanisms. The object of the study is a construction company that performs capital construction, major repairs (repair of buildings, repair of facades), reconstruction of residential and industrial buildings and premises.

Conclusion

As a result of the course work, using the software, a UML diagram of the business processes of a construction company was designed. The analysis of business processes carried out in companies makes it possible to optimize or reorganize business processes in order to increase the efficiency of the company's activities and increase its competitiveness. When solving the tasks of the work, the following results were obtained: the identification of business processes of a construction company was carried out. The identification process was to identify and list all the processes that were of key importance to the company. Also, in the identification process, scientific knowledge on business process modeling and practical knowledge gained from employee surveys and from personal experience in the company were used. a top-level process model has been developed. a UML diagram was developed for planning the functionality of an accounting information system for a construction enterprise. The use of information systems for accounting activities provides a reduction in the timing of work, reducing the risks of financial risks and risks associated with the timing, automating some functions.

Bibliography

1. Bocharov, E.P. Integrated corporate information systems. Construction principles. Laboratory workshop based on the Galaktika system. Proc. allowance / E.P. Bocharov, A.I. Koldin. - M.: Finance and statistics, 2005. - 581 p. 2. Gartvich, A.V. Planning of purchases, production and sales in 1C: Enterprise 8 / A.V. Hartwich. - St. Petersburg: Peter, 2007. - 452 p. 3. Davydova, L.A. Information systems in the economy in questions and answers: textbook. allowance / L.A. Davydov. – M.: TK Velby, Prospect Publishing House, 2004. – 280 p. 4. Dick, V.V. Methodology of formation of decisions in economic systems and tools for their support / V.V. Dick. - M.: Finance and statistics, 2002. - 560 p. 5. Ivasenko, A.G. Information technologies in economics and management: textbook. allowance for universities / A.G. Ivasenko, A.Yu. Gridasov, V.A. Pavlenko. – M.: KNORUS, 2005. – 160 p. 6. Isaev, D.V. Information technologies of management accounting. Educational-methodical complex / D.V. Isaev, T.K. Kravchenko. - M.: GU-HSE, 2006. - 297 p. 7. Karminsky, A.M. Informatization of business / concepts, technologies, systems: A.M. Karminsky, S.A. Karminsky, V.P. Nesterov, B.V. Chernikov; ed. A.M. Karminsky. - 2nd ed., revised. and additional - M.: Finance and statistics, 2004. - 624 p. 8. Kozyrev, A.A. Information technology in economics and management: Textbook. 2nd edition / A.A. Kozyrev. - St. Petersburg: Publishing House of Mikhailov V.A., 2001. - 360 p. 9. Kolesnikov, S.N. Planning the activities of a manufacturing enterprise. From industrial financial planning to MRP II / S.N. Kolesnikov. - M.: 1C-Publishing, 2006. - 602 p.

When developing the solution, IBS specialists used the best world practices of construction project management implemented in foreign information platforms and all the experience of implementing management systems in construction organizations, taking into account the needs of Russian customers and local requirements in the field of overhaul and construction.

Unique difference IBS CMP IM is that IBS specialists managed to link into a single information loop all the functional units involved in the implementation of capital repairs and construction projects (accounting, economic service and production units) throughout the entire construction cycle of the facility - from the investment phase, work planning to provision of resources and control of works, their accounting and closing.

In particular, at the investment phase, the system allows you to maintain the main characteristics of the objects of work, contracts for these objects (including general contracting, subcontracting), see the calendar schedule for the performance of work under the contract.

At the stage of work planning, users can maintain calendar-network schedules in a single system, which are compiled taking into account information about the availability of resources, as well as taking into account estimated restrictions. The system allows you to upload estimates (implemented integration with the main estimate systems) and generate resource sheets, technological schedule, needs for personnel, construction machines and mechanisms on their basis. The integration of processes and data in a single system makes it possible to eliminate dispatching conflicts in terms of the availability of equipment and personnel during the implementation of plans.

During the construction process, the system makes it possible to monitor and analyze the progress of work and the achievement of economic indicators, allowing you to compare construction costs in three main ways - estimated, planned (based on the calendar and network schedule), and also according to actual costs. The system monitors the process of procurement, receipt and write-off of materials at a specific facility in relation to the completed construction work. Forms for writing off materials (M-29) in the system are formed in accordance with the acts of work performed (KS-2), which allows you to track abnormal consumption of materials (deviations from estimates in kind and value terms), control the discipline of accounting and economic indicators of the object in the process of implementation construction project.

It is possible to track the actual load of equipment at the facilities, take it into account when planning construction work, thanks to the specialized functionality of the system. The solution allows you to plan, dispatch and record the work of construction machines at specific construction sites in relation to specific operations, analyzing the compliance of needs with estimates, and, thus, keep a detailed account of the costs of machines and mechanisms (while usually construction companies take into account the costs on construction machines and mechanisms by the “boiler method”). Also, the consumption of fuels and lubricants is recorded and controlled, taking into account the mileage, season, etc.

In general, the experience of implementing the system shows that its use can give a real economic effect, both by improving information exchange and by more efficient organization of business processes, since the solution contains an effective operational model for managing construction and installation works.

“The experience of large construction projects in recent years has shown that there is a huge potential for improving the quality of construction management in Russia. The solution we offer allows you to increase the economic efficiency of projects by controlling the construction process. IBS CMP IM helps to see deviations from the estimated norms associated with the overspending of materials, construction machines and mechanisms, personnel, control the timing of work, and adjust estimates in the process of performing work on the project. This is not just an accounting system - we offer a certain model of business processes, which is built on the requirements of the Ministry of Construction, state standards, traditions of rational management and best practices of construction companies and our expertise,” explained Petr Sychev, Lead Consultant of the IBS Production Department.

The solution will primarily be useful to organizations that carry out major repairs and construction at several sites on their own or with the involvement of subcontractors, and who use cost estimates to determine the cost of these works. This may include companies in the construction, industrial production, chain retail, energy, communications, etc.

“This is a high-readiness solution and requires minor adjustments to suit the specifics of each customer's activities. However, according to experience, along with the implementation, organizational changes are required in the customer's company - improving the methodology for managing construction and installation works and introducing a new production culture that our solution brings with it. For construction companies, the system will increase transparency and reach a new level of economic efficiency,” said Marina Denisenko, Head of EAM and MES Solutions Department of IBS Production Department.

SUBSCRIBE TO OUR PAGES.
WE ARE IN

Send your good work in the knowledge base is simple. Use the form below

Students, graduate students, young scientists who use the knowledge base in their studies and work will be very grateful to you.

Send your good work in the knowledge base is simple. Use the form below

Students, graduate students, young scientists who use the knowledge base in their studies and work will be very grateful to you.

Posted on http://allbest.ru

1. Apache information system

1.1 Description of Apache

2. Information systems for a construction company

2.1 Information system 1C: Trade and warehouse

2.1.1 Description of the program

2.1.2 Working with distributed infobases

2.1.3 Reliability and safety

2.1.4 Flexibility and customization

2.1.5 Interface

2.1.6 Openness and accessibility

2.1.7 Working with shop equipment

2.2 CRM information system

2.2.1 Business process automation

2.2.2 Customer information management

2.2.3 Sales management

2.2.4 Product Portfolio Management

2.2.5 Working time management

2.2.6 Workflow automation

1. Information systemApache

There are a huge number of web servers in the world. They differ from each other in functionality and purpose. In this work, one of the most popular hosting providers installed on most servers will be considered. The Apache server meets almost all the needs of modern web development, but at the same time it is simple enough that programmers install it to debug their programs.

In 1994, an employee of the National Center for Supercomputing Applications at the University of Illinois (NCSA) Rob McCool published the first web server, which was called the NCSA HTTP daemon. The server gained popularity in narrow circles, but in mid-1994 McCool left the university, and development ceased.

A small group of interested webmasters started working together on the product. Communicating on the discussion list by e-mail, they developed "patches" and innovations for the server. It was they who created the Apache Group, which developed the first version of the Apache server. It happened in April 1995, when all existing "patches" were applied to the base (NCSA Server 1.3). This is how the first official public release of Apache 0.6.2 appeared.

Work on the server did not stop for a day, and very soon it became one of the most popular. After numerous tests, version 1.0 appeared on December 1, 1995, stable and reliable. Throughout all these years and to this day, Apache has remained completely free. Perhaps this also determined the success of the server, because, according to NetCraft, Apache is currently installed on 67% of all servers in the world.

1.1 DescriptionApache

At the moment, two branches of Apache are being developed in parallel - versions 2.0 and 1.3. The second version has undergone a significant number of changes, which primarily affected the core of the program and some important modules. Since modules written by third parties for version 1.3 will not work in version 2.0, the "old" Apache is also supported. However, if you install Apache for the first time, then you should take a closer look at the new version.

Apache is a full-featured, extensible web server that fully supports the HTTP/1.1 protocol and is open source. The server can run on almost all common platforms. There are server executables available for Windows NT, Windows 9x, OS/2, Netware 5.x, and several UNIX systems. It is also very easy to install and configure. Apache is configured using text-based configuration files. The main parameters are already configured "by default" and will work in most cases. If there is a lack of functionality of the regular "Apache", then you should take a closer look at the redistributable modules written by the Apache Group and third-party developers. An important advantage is that the creators actively communicate with users and respond to all error messages.

The simplest function that Apache can perform is to stand on a server and serve up a normal HTML site. When a request is received for a particular page, the server sends a response to the browser in that page. When typing the address, the page opens - everything is simple.

The function is more complicated, which is embedded in the HTTP / 1.1 protocol - user authentication. Using the standard tools of the Apache server, it is possible to restrict access to certain pages of the site for different users. This is necessary, for example, in order to make an administrative interface to the site. For this, the .htaccess and .htpasswd files are used, as well as the mod_auth and mod_access modules. Users can be divided into groups, and each of them can be assigned their own access rights.

To separate the design and functional part of the site, as well as to simplify the change of static objects, there is SSI * technology. It allows you to put all the repetitive information in one file (for example, top.inc), and then insert a link to it into the pages. Then, if you need to change multiple lines of this information, you only need to change them in one file. The Apache server supports this technology and allows you to use server-side inclusions to their full extent.

If there are several users on the same server with the installed operating system of the Unix family and the Apache server, then each of them can create a separate directory. More precisely, it will be created automatically along with the alias. This is done using the mod_userdir module and the UserDir directive. So, for example, you can match the public_html folder in the user's home folder with the address www.site.ru/~user. In general, this is done on the servers of most sites that provide free hosting. The server administrator can allow or restrict certain users from creating homepages, using SSI, and other server features. Full-fledged hosting usually provides for the creation of a separate virtual server for each user.

The Apache server was one of the first servers to support virtual servers (hosts). This feature allows you to host several full-fledged sites on one physical server. Each of them can have its own domain, administrator, IP address, and so on.

If you need to host the domain.ru and domain.com domains on the server, then first you need to make sure that they are assigned an IP address in the DNS system. After that, in the Apache configuration file, create two directives , where you describe each virtual host. Thus, the server will know which folder to "send" the incoming request to.

At the moment, most Internet pages are dynamic. This means that their appearance and content is formed using a software script written in one of the "languages"; they cannot be fully called languages, the definition is rather arbitrary. At the moment, the most widely used technologies are CGI and PHP. Of course, Apache has support for both, plus the ability to include other languages.

The mod_cgi module allows hosting CGI scripts on the server. These are just executable files written in one of the accepted programming languages. They can be contained both in a compiled form, for example, they do this if they write CGI in C ++, and in the form of source text if Perl is installed on the server, then the programmer can put such files. Sometimes they have a .pl extension.

Based on the Apache server, you can create not only simple amateur sites, but also resources that require serious cryptographic protection of transmitted data. The SSL/TLS protocol was developed specifically for this purpose, and its support was built into Apache 2.0. Using a special module, you can perform authentication based on named certificates, which makes it possible to almost certainly guarantee the authenticity of the user.

The Apache server can keep a log of all actions performed on it. The administrator can choose the level of detail of the protocol. Logs are maintained separately for errors, for successful operations, and for each virtual host. .

2 . Information systems for a construction company

2.1 Information system 1C: Trade and warehouse

2.1.1 Program description

"1C: Trade and Warehouse" is the Operational Accounting component of the "1C: Enterprise" system with a standard configuration for automating warehouse accounting and trade.

The "Operational Accounting" component is designed to account for the availability and movement of material and cash resources. It can be used both standalone and in conjunction with other 1C:Enterprise components.

"1C: Trade and Warehouse" is designed to account for any type of trading operations. Thanks to its flexibility and customizability, the system is able to perform all accounting functions - from maintaining directories and entering primary documents to receiving various statements and analytical reports.

Automation of any trade and warehouse operations

"1C: Trade and Warehouse" automates work at all stages of the enterprise.

The typical configuration allows:

Maintain separate management and financial records;

Maintain records on behalf of several legal entities;

· Maintain lot accounting of inventory with the ability to choose the method of writing off the cost (FIFO, LIFO, average);

Maintain separate accounting of own goods and goods taken for sale;

· to make purchase and sale of goods;

· to make automatic initial filling of documents on the basis of earlier entered data;

Keep records of mutual settlements with buyers and suppliers, detail mutual settlements under individual agreements;

· to form the necessary primary documents;

· draw up invoices, automatically build a sales book and a purchase book, keep quantitative records in the context of CCD numbers;

· to carry out reservation of goods and control of payment;

Keeping records of funds in current accounts and at the cash desk;

Keep records of commodity loans and control their repayment;

Keep records of goods transferred for sale, their return and payment.

In "1C: Trade and Warehouse" you can:

Set the required number of prices of different types for each product, store supplier prices, automatically control and quickly change the price level;

Work with related documents;

Perform automatic calculation of write-off prices for goods;

Quickly make changes using group processing of directories and documents;

Keep records of goods in various units of measurement, and cash - in various currencies;

Receive a wide variety of reporting and analytical information on the movement of goods and money;

Automatically generate accounting entries for 1C: Accounting.

apache information program automation

2.1.2 Working with distributed infobases

The main purpose of the tools for working with distributed information bases is the organization of a unified automated accounting system at enterprises that have territorially remote objects: branches, warehouses, stores, order acceptance points and other similar units that are not connected by a local network:

maintaining an unlimited number of autonomously working information bases;

full or selective data synchronization;

setting up the composition of synchronized data;

Arbitrary order and method of transferring changes;

The use of distributed infobase management tools does not restrict the actions of system users. The system tracks all data changes automatically and transfers them in accordance with the described synchronization rules.

The "Distributed infobase management" component is supplied separately

2.1.3 Reliability and security

"1C: Trade and Warehouse" contains means to ensure the safety and consistency of information:

· Possibility of prohibition to users of "direct" deletion of information;

· special data deletion mode with cross-reference control;

Possibility to prohibit users from editing data for past reporting periods;

setting a ban on editing printed forms of documents;

· "Locking" the system by the user during a temporary stoppage of work.

2.1.4 Flexibility and customizability

"1C: Trade and Warehouse" can be adapted to any accounting features at a particular enterprise.

The system includes the Configurator, which allows, if necessary, to configure all the main elements of the system:

edit existing and create new necessary documents of any structure

change the screen and print forms of documents

create journals for working with documents and arbitrarily redistribute documents among journals for efficient work with them

edit existing and create new directories of arbitrary structure

edit properties of directories:

· change the composition of the details, the number of levels, the type of code, the range of verification of the uniqueness of the code and create registers for accounting for funds in any necessary sections; create any additional reports and information processing procedures; describe the behavior of the system elements in the built-in language.

2.1.5 ANDinterface

"1C: Trade and Warehouse" follows modern user interface standards:

- "tips of the day" will tell you effective methods of work and convenient features of the system

Service windows can be "attached" to the boundaries of the main program window

The main menu of the system contains "images" of commands - the same images are placed on the buttons of the toolbars

toolbar buttons can be labeled not only with pictures, but also with text.

2.1.6 Openness and accessibility

"1C: Trade and Warehouse" contains a variety of tools for communication with other programs.

The ability to import and export information via text files will allow you to exchange data with almost any program.

In addition, the built-in language contains tools for working with DBF files.

Also, "1C: Trade and Warehouse" supports modern application integration tools: OLE, OLE Automation and DDE. Using these tools allows you to:

manage the work of other programs using the built-in language "1C: Trade and Warehouse" - for example, generate reports and graphs in Microsoft Excel

get access to "1C: Trade and Warehouse" data from other programs

insert objects created by other programs into documents and reports "1C: Trade and Warehouse" - for example, place a company logo in primary documents

Place drawings and graphs in documents and reports.

1C:Trade and Warehouse supports open standards: commercial information exchange (CommerceML) and payment document exchange (1C:Enterprise - Bank Client).

This makes it possible: to generate and upload commercial offers to Web-showcases that support the standard; to organize the electronic exchange of catalogs, price lists and documents with their counterparties; to exchange payment documents (payment orders and statements) with the Client-bank systems database of the UNISCAN/EAN Russia Association.

2.1.7 Working with commercial equipment

"1C: Trade and Warehouse" provides work with commercial equipment: cash registers, receipt printers, scanners and barcode printers, electronic scales, data collection terminals, customer displays and other types of equipment.

"Intellectual" interaction with the trade equipment allows, for example, filling out documents by reading the barcodes of goods with a scanner.

Additional components and techniques for working with commercial equipment are supplied separately.

The cost of installing the implementation of this software varies from the number of jobs. Installation will require additional costs for the purchase of a database management system.

This paper considers a construction company in which 40 jobs are organized, the average cost of one job for 2016 with the installation, implementation and purchase of keys to the workplace is ~ 17.5 thousand rubles

2.2 Information systemCRM

There are discrepancies in the concept of CRM (Customer Relationship Management): someone under this letter combination sees a business methodology, and someone sees software for automating work with clients. Both those and others are right. But let's put the right emphasis.

CRM is a strategy. The term Customer Relationship Management can be translated into Russian as "customer relationship management".

This literal translation is quite true, but does not paint an obvious picture.

In fact, CRM is a specific approach to doing business, in which the client is at the forefront of the company's activities.

That is, the CRM strategy involves the creation in the company of such mechanisms for interacting with customers, in which their needs have the highest priority for the enterprise.

Such a customer focus affects not only the overall business strategy of the company, but also the corporate culture, structure, business processes, operations.

The main goal of implementing a CRM strategy is to create a pipeline for attracting new customers and developing existing customers.

Relationship management means attracting new customers, converting neutral customers into loyal customers, and turning regular customers into business partners.

A CRM system is the embodiment of CRM strategy automation. Information technology plays a very important role in bringing the CRM strategy to life.

CRM software is a specialized system designed to automate the very business processes, procedures and operations that are implemented in the form of a company's CRM strategy.

As a key tool for winning and retaining customers, CRM applications minimize the human factor in dealing with customers and increase transparency in sales, marketing and customer service.

At the same time, it is important to realize that automating the customer relationship process is an important, but not the only or primary step in building a customer-centric company.

A software product is a convenient tool that will support existing regulations and processes and will develop together with the company.

2.2.1 Business process automation

Putting all the work processes on the shelves, formalizing them is a non-trivial task solved by business analysts.

If all employees act according to regulated processes, the number of errors decreases, the work of the company accelerates, and the results of work become more predictable.

If the execution of processes is transparent to managers, it is much easier for them to identify weaknesses in the work and direct the efforts of employees in the right direction.

These tasks can be solved by automating processes using a CRM system.

To formalize, automate the execution and control of processes, Terrasoft CRM offers special tools. A business analyst will appreciate a convenient visual editor that allows you to build a description of algorithmic processes of any complexity in the CRM system.

Managers will be able to specify the performers and participants of the tasks in the process, fix the time spent on the performance of a particular task, and managers will be able to analyze the effectiveness of both the business processes themselves and the work of employees.

By providing automation and operational control over the progress of the company's business processes, the CRM system increases the likelihood of their timely and high-quality execution.

New employees get up to speed faster, communication between departments improves. And the means of evaluating the effectiveness of business processes contribute to the optimization of the company's activities as a whole.

2.2.2 Customer information management

The "heart" of any CRM system is a database of both individuals and legal entities that interact with your company as part of the enterprise's activities. These are not only customers, but also company branches, partners, suppliers, competitors.

A customer database is a valuable asset in itself, and proper data management in a CRM system allows you to use information in your work with maximum efficiency.

The client base is consolidated, the organization receives complete information about its clients and their preferences, and, based on this information, builds an interaction strategy.

A single database of customers and a complete history of relationships with them, together with powerful analytical CRM tools, allows you to retain and develop existing customers, identifying the most valuable ones, as well as attract new customers.

2.2.3 Sales management

The main function of a CRM system is to help managers plan sales, organize transparent transaction management and optimize sales channels.

The system stores a complete history of communication with customers, which helps sales departments to analyze customer behavior, create suitable offers for them, and win loyalty.

Sales planning in the CRM system is organized in various sections (by regions, managers, areas, etc.). The manager draws up a plan based on data on his clients, taking into account the probability, and the manager, having analyzed the volume of confirmed payments, can make an incentive plan for the manager.

Managers make special demands on CRM. With the help of CRM-system tools, managers can control the quality indicators of the work of managers (sales funnel), the implementation of sales plans, compliance with payment and delivery deadlines.

The system allows you to evaluate the volume and probability of transactions, manage sales business processes, monitor the status of the transaction and analyze the actions of competitors.

One of the most important tasks that the CRM system helps to solve is the organization of cross-sales, up-sales.

The system allows you to create a cross-sales matrix and a product-segment matrix, group customers according to various parameters and identify their potential interests.

Offering tools for forecasting and analysis, automating the interaction of employees with customers and among themselves, the CRM system forms the preconditions for optimizing existing sales channels and increasing the company's profits.

2.2.4 Product Portfolio Management

It is important for any commercial organization to provide high quality products and services at competitive prices, constantly improve product lines.

CRM-system allows you to structure the nomenclature and manage the full catalog of goods and services of the company. CRM capabilities provide tracking of special prices and discounts, data analysis and relationships to offer customers the best package of services and identify popular products.

2.2.5 Time Management

Efficient time management and time tracking have a positive impact on all business processes of the company. The CRM system allows employees of the organization not only to record the use of the current working time, but also to plan the load for future periods.

CRM-system tools offer convenient access to the schedule, in which an employee can plan their own working time, note the results of the planned tasks, view the schedule of colleagues. In turn, at the disposal of management are tools for monitoring the workload and performance of subordinates.

Thanks to the ability to associate all tasks with the relevant counterparties, contacts, transactions, a history of work with each client is formed and accumulated.

Generation of 80% of tasks automatically according to the business process allows you to free employees from routine operations, most rationally allocating working time, and not to forget about a single important matter.

2.2.6 Workflow automation

The CRM system provides all the necessary tools for managing both external and internal document management of the company. These tools provide tools for automatically generating documents from templates, preparing printed forms of documents, supporting versioning of documents, quickly searching for documents in the system, creating an electronic document repository, and much more.

When maintaining documentation in CRM, it is possible to organize collective work with documents with flexible differentiation of access rights, electronic approval, as well as accounting for the relationship between documents.

2.2.7 Analytical capabilities of the programCRM

It is impossible to increase the profitability of an enterprise without a deep analysis of information about customers, their value and profitability, identifying "bottlenecks" in the company's business processes, and analyzing the sales system. The CRM system allows the company to obtain statistical information, conduct complex data analysis, which is necessary for making strategically important business decisions.

More than 100 standard system reports provide an opportunity to analyze and control all typical business tasks. Using the built-in report builder, you can create analytical forms that meet the specific needs of each enterprise.

In addition, on the dashboard of the CRM system, you can track KPIs (Key Performance Indicators), the analysis of which will allow management to evaluate the performance of each employee.

This software is installed in a construction company together with software 1C. To develop configurations, write a program, install it, integrate it into 1C and implement it, ~ 10 thousand rubles will be spent per workplace.

Featured on Allbest.r

...

Send your good work in the knowledge base is simple. Use the form below

Students, graduate students, young scientists who use the knowledge base in their studies and work will be very grateful to you.

Hosted at http://www.allbest.ru/

Table of contents

Introduction
2.2 Normal forms
2.5 Synthesis algorithm
2.8 Creating a data schema
2.9 Choice of development tools
3. Development of an information system
3.1 User mode of operation
3.2 Investor mode of operation
3.3 Mode of operation of the manager
3.4 Mode of operation of the director
4. Safety and sanitary and hygienic working conditions at the workplace of a PC user
4.1 Characteristics of sanitary and hygienic working conditions
4.2 Ventilation
4.3 Calculation of the lighting installation
4.4 Working hours
4.5 Requirements for the organization of the workplace
4.6 Electrical safety
conclusions
5. Calculation of the economic efficiency of the project
5.1 Marketing plan
5.2 Goals, objectives and methods for evaluating investments
5.3 Selection and description of the development and alternative options
5.4 Calculation of investments at the stage of development and debugging of the main version
5.5 Calculation of investments at the stage of development and debugging of an alternative option
5.6 Calculation of investments by years of the operation stage
5.7 Final indicators of technical and economic efficiency
conclusions
Conclusion
Appendix 1DB creation script inMySQL

Introduction

Market relations, having destroyed the existing planning and distribution order, led to the formation of new forms of relationships, changed some of the links in the building complex, filling them with new content. The diversity of participants in the construction of the facility turned the production process into a complex economic mechanism, which, along with the duration of the investment cycle, contributed to the emergence and formation of new organizational forms of construction management. For example, investment and construction companies (firms) were formed - integrated developers that perform work in a closed production cycle: investment - design - construction - commissioning - sale of finished construction projects. Investment and construction companies are mainly engaged in housing and social construction and have a number of advantages over general construction firms. In such organizational structures, there are complex problems of investment, planning, design, management and direct construction of facilities that require a system-technical approach to their solution, which is possible with the use of modern software and information technologies. However, the use of computers in the construction industry is mainly focused on automating numerous labor-intensive calculations, while practically not solving managerial tasks that require logical thinking.

Computerization of construction in technical terms means the creation of automated workplaces equipped with computer technology. The complexity of the management tasks to be solved makes it necessary to develop and use in investment and construction activities the processes of developing and implementing programs that implement specific computer technologies using currently available technical means. The computerization of construction increases the level of knowledge and skills among managers and performers, makes management personnel effectively use the available computer equipment with construction software in their daily activities.

In investment and construction companies, engineering systems engineering of construction is widely used, namely: automated construction management systems (ACS), computer-aided design systems (CAD), automated data processing and documentation systems (ASOD) and others, which contribute to improving the efficiency and quality of management.

The introduction of software products for a unified information network requires the company to develop a culture of management management, large capital investments for implementation, staff training and maintenance.

Computers used in management information technologies do not require special, professional training from users. Therefore, it became possible to automate new management tasks such as managing office information, preparing documents, organizing teamwork and workflow via e-mail, planning and operational analysis of information, creating databases with online access from any workplace. Currently, a new generation of information systems is being actively developed, created on the principle of maximum information availability, which enable the end user to take a direct part in the formation and use of the information space of an investment and construction company. Thanks to the Internet, investment and construction companies have been able to interact with partners in a virtual way, use information channels to promote their construction products, and also make commercial transactions using a computer.

Thus, in a competitive environment in a market economy, investment and construction companies constantly need information management systems. The creation of such a system is the goal of this work.

1. Designing an information system

1.1 The essence of the information system

The information management system of an investment and construction company is a mechanism that ensures the movement of financial, material and information flows. A change in the organizational structure and composition of the tasks to be solved in the course of the activity of an investment and construction company automatically causes the need for changes in the information support of the management system. The importance of information support has increased dramatically in a market economy and competition among similar companies and holdings in construction. The information management system for an investment and construction company involves the introduction of new information technologies, the improvement of information management methods, the modernization of outdated computer and telecommunications equipment, the creation of information data warehouses, and the installation of software.

From the point of view of using the information management system, it is necessary to continuously change its software, consistent with the passage of time, the goals of the investment and construction company and changes in the market economy. From the point of view of the usefulness of the information system, it should be managed to ensure the required return on capital investments invested in its acquisition. Since any management information system requires constant investment in updating it, modern construction companies are forced to spend significant financial resources almost annually on maintaining and developing management systems, equipping employee workplaces with new software and increasingly powerful computer equipment.

Information management of an investment and construction company requires a systematic approach to the presentation of investment project resources and management processes. An integrated approach to the information management of an investment and construction company ensures the creation of a single information space for all users and allows you to take into account a large number of various features of the investment and construction activities of the company, which change over time and depending on market economic relations.

1.2 Functional specification

The system should provide independent work for the following categories of users: director, managers, investors and clients.

The main screen of the application displays general information about the company, its history, details, built and under construction real estate. This screen is primarily intended for potential customers of the company. Also on this screen there is a button to enter applications for authorized users.

The director can set information on objects, clients and managers. The director plans the construction and attracts clients by negotiating the amount of investment. Further, he appoints a construction manager from among the free ones. The manager is considered free when the construction of the object under his control is completed. The decision to complete the construction is made by the Director.

Investors finance and monitor construction progress. Each object can have several Investors, and one Investor can finance several real estate objects.

automation information system custom

Managers supervise construction. One Manager can be responsible for one property at a time. Managers are also involved in the supply of building materials and the involvement of builders who are not currently employed at another facility. A builder is considered free if the object he is building is ready.

Builders are engaged in the construction of the facility under the direction of the Managers. Each Builder has his own speciality.

Materials necessary for construction are supplied in the required quantity, and their cost is the main item of the Company's expenses.

1.3 IC design approaches

The problem of complexity is the main problem that has to be solved when creating large and complex IS. No developer is able to understand the entire system as a whole. To date, there are two approaches to the development of IS, which are due to different principles of system decomposition:

Functionally modular or structural - based on the principle of functional decomposition, in which the system is described in terms of the hierarchy of its functions and the transfer of information between individual functional elements

· Object-oriented approach - uses object decomposition. The system is described in terms of objects and connections between them, and the behavior of the system in terms of the exchange between them.

The appearance of the first computers marked a new stage in the development of computing technology. Special programming languages have appeared that allow converting individual computational operations into program code. Over time, the development of large programs became a serious problem, and required breaking into smaller fragments. The basis for such a division was procedural decomposition, in which individual parts of programs or modules were a set of procedures for solving a certain set of tasks.

Structured programming methodology emerged. The basis of this methodology is the procedural decomposition of the software system and the organization of individual modules in the form of a set of executable procedures.

In the second half of the 80s, the methodology of object-oriented programming appeared

The main disadvantage of the structural approach is that processes and data exist separately from each other, and the design is from processes to data. Thus, in addition to functional decomposition, there is also a data structure that is in the background.

In the object-oriented approach, the main category of the object model - the class - combines both data and operations. Compared to processes, data is a more stable and relatively infrequent part of the system. One of the founders of the object-oriented approach formulated the benefits as follows:

“Object-oriented systems are more open and easier to change because their design is based on stable forms. This allows the system to develop gradually and does not lead to its complete processing, even in the case of significant changes in the initial requirements.”

This graduation project uses the methodology of an object-oriented approach to describe the business processes of an enterprise.

1.4 Unified Modeling Language UML

Currently, the Unified Modeling Language (UML) is a visual modeling language that allows system architects to present their vision of a system in a standard and easy-to-understand manner. In addition, UML provides an efficient mechanism for sharing design decisions and developers interacting with each other.

Forming a vision of the system is an extremely important moment. Before the advent of the UML, the development process was often based on guesswork. The systems analyst had to assess the needs of the clients, formulate the problem in a form understandable to the specialist, transfer the results of his analysis to the programmer and hope that the final software product will be exactly the system that the client needs.

Since the system development process is largely dependent on human activity, errors can occur at any stage. The analyst may misunderstand the client and create a document that is incomprehensible to him. The results of the analyst's work may not be obvious to programmers who will create a program that is difficult to use and does not allow the client to solve the original problem.

A well-thought-out plan is the key to the development process these days. The client must understand what the development team is going to do, and must be able to make adjustments if their tasks are not being fully resolved.

The world around us is becoming more and more complex. Therefore, the computer systems that reflect it also become more complex. Often they consist of a large number of software hardware components that interact with each other over long distances and are associated with databases that contain a huge amount of information.

A key aspect of the design process is its proper organization, when analysts, clients, programmers and other specialists involved in the development of the system are able to understand each other and come to a common opinion. The UML language provides such an opportunity.

Another hallmark of the modern systems development process is the lack of time to complete the work. If deadlines for subsystems are piled on top of each other, then ensuring the continuity of the development process becomes a vital necessity.

The need for a quality development process necessitates the creation of standard conventions. The UML is just such a notation.

Pre-release versions of the UML began to be used in software development, and significant improvements were made based on customer feedback. Many corporations have felt that the UML can be useful in achieving their strategic goals. This led to the formation of the UML consortium, which included companies such as DEC, Hewlett-Packard, Intellicorp, Microsoft, Oracle, Texas Instruments, Rational, and others. In 1997, the consortium developed the first version of UML and submitted it to the OMG (Object Management Group) for consideration, in response to its request for proposals for a standard modeling language.

After the expansion of the consortium, version 1.1 of the UML was released, which the OMG adopted in late 1997. After that, OMG began to maintain UML and released two new versions of it in 1998. The UML has become the de facto standard in software development. Currently, this language continues to develop actively.

The UML language is designed to solve the following tasks:

o To provide the user with an easy-to-understand visual modeling language specifically designed for developing and documenting models of complex systems for a wide variety of purposes.

o Provide the original concepts of the UML language with the possibility of extension and specialization for a more accurate representation of system models in the OOAD (object-oriented analysis and design) of a specific subject area.

o None of the UML language constructs should depend on the features of its implementation in known programming languages.

o Encourage the development of a market for object tools.

o Ability to improve.

o Integrate the latest and best practices

Within the framework of the UML language, all ideas about the model of a complex system are fixed in the form of special graphic structures called diagrams. In terms of the UML language, the following types of diagrams are defined:

Diagram of options or use cases (use case diagram)

Class diagram (class diagram)

Behavior diagrams

o Statechart diagram

o Activity diagram

Interaction diagrams

o Sequence diagram

o Collaboration diagram

Implementation diagrams

o Component diagram

o Deployment diagram

The list of these diagrams and their names are canonical in the sense that they are an integral part of the graphical notation of the UML. Each of these diagrams details and concretizes different representations of a complex system model in terms of the UML.

It is also worth adding that it is not always necessary to build absolutely all diagrams, the developer himself decides whether this level of detail suits him, whether it is necessary to consider the system or its part from a "different view", whether the most "difficult and slippery moments" are considered in sufficient detail. Those. tools that support UML and are designed for software modeling, allow at the development stage to check architectural solutions, the completeness of the model, its correctness, in order, among other things, to reduce the risk of "failure" of the project. Let's describe some of the graphic diagrams built during the development of our system.

1.5 CASE tool Rational Rose

Rational Rose is a powerful CASE tool for designing software systems of any complexity. One of the advantages of this software product will be the ability to use UML diagrams. We can say that Rational Rose is a graphical editor for UML diagrams.

The Rational Rose CASE tool has undergone a major evolution since its inception and has become a modern and powerful tool for analyzing, modeling, and developing software systems. It was in Rational Rose 98/2000 that the UML became the underlying technology for visualization and program development, which determined the popularity and strategic viability of this toolkit.

Within Rational Rose, there are various software tools that differ in the range of implemented features.

The fact that the package allows you to create complex software systems from conception to the creation of source code attracts not only designers, but programmers - developers. In combination with documentation tools, it gives a complete picture of the project. We highlight the following benefits from using this package:

Reduction of development time;

Reducing manual labor, increasing productivity;

· improvement of consumer qualities of created programs;

the ability to lead large projects or a group of projects;

· allows to be a language of communication between different developers.

In view of the fact that the system being developed is the creation of a database, there is no task of fully developing the automation of the modeling process, i.e. writing program codes using Rational Rose. The solution of the tasks set allows not to use it at this point in the design, but in turn is a useful launching pad for the possible further use of this developed project for implementation into any other software product. The constructed models help to more accurately understand the tasks that the system must perform and are a clear means of communicating with the customer or in further work with other developers. Consider first the functional model of our system. Our system has a number of users united by certain tasks, which allows us to divide the system into several subsystems and describe them separately without creating a large volume and redundancy. Let's take a look at some of the diagrams that have actively helped me determine most of the things that this information system will do.

1.6 Use case diagram

The development of this diagram has the following goals:

Determine the general boundaries and context of the modeled subject area at the initial stages of system design

· Formulate general requirements for the functional behavior of the designed system.

· Develop an initial conceptual model of the system for its subsequent detailing in the form of logical and physical models.

· Prepare initial documentation for the interaction of system developers with its customers and users.

The essence of this diagram is as follows: the system being designed is represented as a set of entities or actors interacting with the system using the so-called use cases. In this case, an actor or actor is any entity that interacts with the system from the outside. It can be a person, a technical device, a program or any other system that can serve as a source of influence on the simulated system in the way that the developer himself determines. In turn, the use case serves to describe the services that the system provides to the actor. At the same time, nothing is said about how the interaction of actors with the system will be implemented.

Rational Rose tools allow you to use a graphical editor to create Use Case diagrams (scenarios) to describe a functional system. Let's describe the main elements, see Table 1.1.

Figure 1.1 Case Diagram

Use case or use case diagrams are an essential tool in the software requirements phase. Each use case is a potential requirement for the system, and until it is identified, it is impossible to plan for its implementation.

Fig.1.2 Manager diagram

Diagramsstates.

State diagrams define all possible states in which a particular object can be, as well as the process of changing the states of an object as a result of the occurrence of some event. There are many forms of statecharts that differ slightly in semantics.

A state diagram can have one and only one initial state. At the same time, there may be as many final states as you need, or there may be none at all. When an object is in a particular state, various processes can be executed.

The processes that take place at this moment, when the object is in a certain state, are called actions.

The following data can be associated with a state: activity, input action, output action, and event.

An activity is a behavior implemented by an object while it is in a given state. Activity is depicted within the state itself; its designation must be preceded by the word do (to do) and a colon.

An entry action is a behavior that is executed when an object enters a given state. An entry action is also shown within a state, preceded by the word entry and a colon.

An exit action is similar to an entry action. However, it is carried out as an integral part of the exit process from this state. An exit action is shown inside a state, preceded by the word exit and a colon.

A transition is the movement of an object from one state to another. In the diagram, all transitions are depicted as an arrow starting at the initial state and ending at the next one.

Transitions can be reflexive. An object can change to the same state it is currently in. Reflexive transitions are depicted as an arrow starting and ending at the same state.

Fig.1.3 State diagram of the "Object of construction"

Diagramactivities

An object is selected, the data about which must be stored in the database.

Activity (activity) diagrams are a special case of state diagrams. Each state is the execution of some operation and the transition to the next state. Activity diagrams are especially useful in describing behavior involving a large number of concurrent processes. The biggest benefit of activity diagrams is their support for concurrency. This makes them a powerful tool for modeling workflows and essentially parallel programming. Their biggest drawback is that the links between actions and objects are not very clear.

Rational Rose tools allow you to use a graphical editor to build Activity diagrams (activity) to describe a functional system.

Activity diagrams are best used in the following situations:

use case analysis. At this stage, we are not interested in the relationship between actions and objects, but only to understand what actions should take place and what are the dependencies in the behavior of the system. The binding of methods and objects is done later using interaction diagrams;

Analysis of workflows (workflow) in various use cases. When use cases interact with each other, activity diagrams are a powerful way to represent and analyze their behavior.

Fig.1.4 Activity diagram "Creating an object"

One important application of activity diagrams is related to business process modeling. The activity of any company also represents a set of individual actions aimed at achieving a particular result. However, in relation to business processes, it is desirable to associate the execution of each action with a specific department. In this case, the department is responsible for the implementation of individual actions, and the business process itself is represented as transitions of actions from one department to another.

Interaction Diagrams

Interaction diagrams describe the behavior of interacting groups of objects. Each diagram describes the behavior of objects within only one use case. The diagram shows objects and the messages they exchange with each other. Three types of messages are defined:

informational (informative) - messages that provide the recipient object with information to update its state;

messages - requests (interrogative) - messages requesting the issuance of information about the recipient object;

· imperative (imperative) - messages requesting the recipient object to perform an action.

There are two types of interaction diagrams:

sequences (sequence diagrams);

cooperative (collaboration diagrams).

In a sequence diagram, an object is shown as a rectangle on top of a dotted vertical line. This vertical line is called the object's lifeline. It is a fragment of the life cycle of an object in the process of interaction.

Each message is shown as an arrow between the lifelines of two objects. Messages appear in the order they appear on the page, from top to bottom. Each message is tagged with at least the message name; if you wish, you can also add arguments and some control information and, in addition, show a self-delegation (self-delegation) - a message that an object sends to itself, with the message arrow pointing to the same lifeline.

Fig.1.5 Sequence diagram "Assigning a builder to an object"

Diagram output: entity objects (list of users, object, list of builders) and boundary objects - pages (password entry window, current object window) are selected.

The second type of interaction diagram is the cooperative diagram. Similar to sequence diagrams, cooperative diagrams depict the flow of events through a specific use case scenario. Sequence diagrams are ordered by time, while cooperative diagrams focus on relationships between objects.

Fig.1.6. Cooperative diagram "Assigning a builder to an object

Algorithm of working with the system through the WEB-interface

The following diagram shows the sequence of transitions between screens through which the user interacts with the system. The availability of certain screens depends on the permissions of the currently working user.

A class diagram is used to design a site.

Rational Rose includes an Add In called Web Modeler for website design.

The sequence of actions when creating a Web application:

ь Connect Web Modeler using the menu item Add In - Add In Manager - Web Modeler. A new item Web Modeler will appear in the Tools menu

b Change default settings Tools - Options - Notation - Default Language - Web Notation

A special stereotype is used to highlight html pages. Based on the created diagram, related html pages are automatically generated.

Fig.1.7 Algorithm for working with the program

2. Database design

2.1 Database requirements

1) Minimal redundancy. The data stored in the computer memory can contain both useful and harmful redundancy. Harmful redundancy always occurs when each user is forced to create a separate set of data for their applications. If several users would require the same data, then they would be repeated in each set. Such redundancy is often referred to as unmanaged redundancy, since individual users may not be aware of its existence. Useful redundancy includes periodic copies of the data stored in the database. This redundancy is easily controlled. Moreover, it is necessary, for example, to restore data destroyed during random computer failures. Thus, the requirement of minimum redundancy should be understood as the elimination of harmful (uncontrolled) and minimization of useful (controlled) redundancy.

2) Data integrity. Data integrity is about maintaining the correctness of the data. It is provided by data recovery after destruction as a result of random computer failures, as well as the elimination of data inconsistency, which consists in the appearance of different instances for the same attributes. Inconsistency may appear when updating redundant data if the update is performed on only part of the data.

3) Security and secrecy. Provides data protection from hardware and software failures, from catastrophic and criminal situations, as well as from incompetent access to them.

4) Data independence. Provides the ability to change the structure of the database without changing user applications. It is understood in two aspects, namely, as logical and physical independence.

Logical independence offers the possibility of changing the logical structure of databases without affecting application programs.

Physical independence implies the same possibility of the physical structure of databases, including both ways of placing data on physical media and methods of accessing data (that is, operations of searching, reading and writing data to computer memory). Ensuring data independence is the main goal pursued when creating a database.

5) Productivity. It is characterized by the response time of an information system using databases to user requests. At the same time, requests for data must be satisfied at such a speed as is required for the use of data.

6) Flexibility and expandability. It is understood as the ability of a database to grow data, as well as increase the number of possible applications and expand the functions within each application.

2.2 Normal forms

A relational database designed in accordance with the conceptual scheme may have a number of serious shortcomings, for example, contain information redundancy, and (or) various anomalies may occur during data processing. To eliminate these shortcomings, i.e. to make a database "good", it is necessary to bring all relations of the database into "strong" normal forms.

Several normal forms are currently known. The first normal form (we will denote 1NF), then - as it "strengthens" - 2NF, 3NF, Boyce-Codd normal form (BCNF) and 4NF. Practice shows that bringing the database to at least 3NF makes it possible to avoid almost all the shortcomings in most cases.

First normal form (1NF).

A relation with a schema R and a set of functional dependencies F is in 1NF if any instance of the schema R satisfies the following conditions:

each R schema attribute has a unique name;

elements of tuples with the same name must be defined on the same domain;

domain elements must be atomic, i.e. not represent, in turn, some set of values;

each element of the tuple must have a single value, repeating groups of values are not allowed;

relation must not have duplicate tuples.

Second normal form (2NF).

A relation with a schema R and a functional dependency set F is in 2NF if it is in 1NF and every non-key attribute is functionally fully dependent on any possible primary key of the relationship schema R.

However, the relationship scheme found in 2NF also has disadvantages. In particular, the set of dependencies defined in this diagram may contain transitive dependencies, which may lead to undesirable consequences (deletion anomalies).

Third normal form (3NF).

A relation schema R with a set of functional dependencies F is in 3NF if it is in 2NF and every non-key attribute is directly, not transitively, dependent on any possible key of the relation schema.

However, 3NF can also have disadvantages related to key attributes. In the above example, the resulting 3NF does not cause anomalies in data processing, since the resulting decomposition subschemes do not have dependencies of key attributes on other attributes. If this condition is violated, then data processing anomalies are possible.

Boyce-Codd Normal Form (BCNF).

Boyce-Codd normal form is more "strong" than third normal form. A relationship schema R with a set of functional dependencies F is in BCNF if the left side of each dependency (XA) F, where A X, is a primary or candidate primary key.

If a relation is in BCNF, then it is in third normal form, but not vice versa.

In the theory of relational databases, it has been proved that any relation can be replaced by a set of decomposition subschemas, each of which will be in 3NF, and the decomposition will have both the property of connection without information loss, and the property of preserving the original set of functional dependencies. When reduced to BCNF, in the general case, only the feasibility of the connection property without loss of information is guaranteed.

2.3 Normalization of relationship patterns

To build a relational implementation of the conceptual database schema, which was in at least 3 NF, you can use two methods:

decomposition method, which consists in sequential partitioning of the initial and intermediate relationship schemes until the resulting relationships satisfy the specified properties;

a synthesis method consisting in the construction (synthesis) of a set of decomposition subschemes that satisfy certain properties from a given set of attributes of the selected subject area based on a given set of functional dependencies linking these attributes.

Both methods must ensure that the resulting decomposition preserves both the lossless connection property and the functional dependency preservation property.

In practice, the synthesis method is more often used, since the decomposition method has a number of serious drawbacks. Let's note the main ones.

The complexity of the algorithm is higher than polynomial.

The number of generated decomposition subcircuits may turn out to be much larger than necessary, while information about them must be saved at each partitioning step, and the partitioning algorithm itself is rather complicated.

When decomposing a relationship schema, partial dependencies may arise, which can also result in unnecessary decomposition subschemes.

2.4 Integrating custom views

Cross-referencing custom views to the main data types used by the database application

Essences	Director	Manager	Investor
object (real estate object)
investor (investor)
investing (investing)
employee (employee)
material (material)
delivery (delivery)
building (construction)

Integratedperformanceusers,submittedVformdiagrams

2.5 Synthesis algorithm

The initial data for the operation of the synthesis algorithm are the set of attributes U and the set of functional dependencies F defined on U.

The result of the algorithm is a diagram of an automated control system in the form of a set of decomposition subcircuits (R 1 , R 2 ,., Rp) that satisfy the following conditions.

Each subcircuit Ri with a database must be at least in the ZNF with respect to the set of functional dependencies F and, respectively, G.

The synthesized information system contains a minimum set of decomposition subschemes Ri, I == 1,., P. This condition protects the information system from redundancy.

For any instance r (DB) that satisfies F, the relation holds. This condition ensures that the connection property is satisfiable without information loss.

A diagram of an automated control system that satisfies conditions 1,2 and 3 is called a complete diagram of an automated control system.

Consider the steps of the algorithm.

Step1 . We build an extended set F of functional dependencies, which has the following dependency structure:

F = ( (X I - > Y I) | (X I - >Y I) F, Y I = X I + \ X I ). This step is done in order to construct an irredundant or conditionally non-redundant cover F, which will allow satisfying condition 3 to some extent. It will be possible to fully satisfy condition 3 after introducing the concept of equivalence of functional dependencies into consideration at step 5.

Step 2. We build an irredundant cover F, excluding unnecessary dependencies from F in any sequence.

Obviously, this coverage is not canonical.

Step3 . If among the functional dependencies from F" there is no dependency that includes all the attributes from U, then we add to F" the trivial dependency U-> Sh.

Step4 . Let's transform the obtained non-trivial dependencies to an elementary form (without unnecessary attributes in the left parts).

Dependency X I - > Y I is elementary if there are no attribute sets X J X I such that (X j - > Y I ) . If - exists, then the dependency X I - >Y I is replaced by the dependency (X J - >Y I).

Step 5. We divide the set of obtained dependencies into equivalence classes. This is done in order to leave one representative in each class at the next step, thereby minimizing the number of decomposition subschemes in the resulting database and fully satisfy condition 3.

Dependencies X I - >Y I and X J - > Y J will be called equivalent if

, i.e. the minimum rank has a dependency that contains all attributes from U, and if it does not exist, then the trivial dependency U - > Sh. We assign the same rank to all dependencies from the same equivalence class. We assign ranks to incomparable dependencies arbitrarily.

Step6 . In each class of equivalent dependencies, we leave one representative. We draw a ranked dependency diagram so that dependencies with a higher rank are depicted under dependencies with a lower rank and arcs indicate direct occurrences of the attributes of one dependency in another.

Step7 . We perform a transitive reduction of dependencies with a higher rank to dependencies with a lower rank. Moving along the diagram from the bottom up (from dependencies with a higher rank to dependencies with a lower rank), for each current dependency, we exclude from the right parts of all dependencies located above the current one those attributes that are contained in the right part of the current dependency (for a trivial dependency, attributes are excluded from its left side).

Step8 . Based on the resulting diagram, we construct a relational implementation of the conceptual scheme of an automated control system that satisfies the conditions of the algorithm, as a set of the following decomposition subschemes, consisting of uncrossed out attributes of each.

A bunch ofattributes:

U = (mNo, mName, mCost, count, oNo, oAddress, oType, oStoreys, oState, eNo, eName, ePost, eState, eSalary, sum, iNo, iName, iPhone)

A bunch offunctionaldependencies:

F = (mNo®mName, mNo®mCost, mName®mNo, mName®mCost,

(oNo, mNo) ®count,

oNo®oAddress, oNo®oType, oNo®oStoreys, oNo®eNo, oNo®oState, oNo®oCost

eNo®eName, eNo®ePost, eNo®eState, eSalary

iNo®iName, iNo®iPhone,

(iNo, oNo) ®sum )

Step 1. Expanded set of functional dependencies:

mNo + =mNo, mName, mCost =>mNo® (mName, mCost)

mNo + =…=>mNo®…

(oNo, mNo) + =oNo, mNo, count=> (oNo, mNo) ?®count

oNo + =oNo, oAddress, oType, oStoreys, oState, oCost, eNo =>oNo® (oAddress, oType, oStoreys, eNo,oState, oCost)

oNo + =…=>oNo®…

eNo + =eNo, eName, ePost, eState, eSalary=>eNo® (eName, ePost, eState, eSalary)

eNo + =…=>eNo®…

iNo + =iNo, iName, iPhone=>iNo® (iName, iPhone)

iNo + =…=>iNo®…

(iNo, oNo) + =iNo, oNo, sum=> (iNo, oNo) ®sum

(mNo, oNo, iNo, eNo) + =mNo, mName, mCost, count, sum, oNo, oAddress, oType, oStoreys, iNo, iName, iPhone, eNo, eName, ePost, eState, eSalary, oState, oCost

=> (mNo, oNo, iNo, eNo) ® (mName, mCost, count, sum, oAddress, oType, oStoreys, oState, iName, iPhone, eName, ePost, eState, eSalary, oCost)

F= (mNo® (mName, mCost), mNo®…, (oNo, mNo) ?®count, oNo® (oAddress, oType, oStoreys, eNo, oState, oCost), oNo®…, eNo® (eName, ePost, eState, eSalary), eNo®…, iNo® (iName, iPhone), iNo®…, (iNo, oNo) ®sum, (mNo, oNo, iNo, eNo) ® (mName, mCost, count, sum, oAddress, oType, oStoreys, oState, iName, iPhone, eName, ePost, eState, eSalary) )

Step 2: Overcoating

F"= (mNo® (mName, mCost), (oNo, mNo) ?®count, oNo® (oAddress, oType, oStoreys, oState, oCost, eNo), eNo® (eName, ePost, eState, eSalary), iNo® (iName , iPhone), (iNo, oNo) ®sum, (mNo, oNo, iNo, eNo) ® (mName, mCost, count, sum, oAddress, oType, oStoreys, iName, iPhone, eName, ePost, eState, eSalary) )

Step 3 Trivial Dependency

There is no need to add a trivial dependency, since there is a dependency that contains the full set of attributes.

Step 4. Elementary type of dependencies

All dependencies are elementary.

Step 5. Dependency equivalence

There are no equivalent dependencies.

Step 6. Dependency ranking

We divide the set of obtained dependencies into equivalence classes. This is done in order to leave one representative in each class at the next step, thereby minimizing the number of decomposition subschemes in the resulting database and fully satisfy condition 3.

Dependencies X I Y I and X J Y J will be called equivalent if (X I Y I) = (X J Y J).

We rank the obtained dependencies according to the following rule rang (X I Y I) > rang (X J Y J), if (X I Y I) (X J Y J).

We assign the same rank to all dependencies from the same equivalence class. We assign ranks to incomparable dependencies arbitrarily.

Step 7: Ranked Dependency Diagram (2NF):

In each class of equivalent dependencies, we leave one representative. The table shows that in this case there are no equivalent dependencies.

We draw a ranked dependency diagram so that dependencies with a higher rank are depicted under dependencies with a lower rank and arcs indicate direct occurrences of the attributes of one dependency in another.

We perform a transitive reduction of dependencies with a higher rank to dependencies with a lower rank as follows.

Moving along the diagram from bottom to top (from dependencies with a higher rank to dependencies with a lower rank), for each current dependency, we exclude from the right parts of all dependencies located above the current one those attributes that are contained in the right part of the current dependency (for a trivial dependency, we exclude the attributes from its left side).

Step 8. Obtaining a set of decomposition subschemes

After passing the algorithm, 6 tables were obtained with the corresponding primary keys:

R1 = oNo, oAddress, oType, oStoreys, oState, oCost, eNo with key oNo

R2 = eNo, eName, ePost, eState, eSalary with key eNo

R3 = oNo, mNo,count with key (oNo, mNo)

R4 = mNo, mName, mCost with key mNo

R5 = iNo, iName, iPhone with key iNo

R6 = iNo, oNo, sum with key (iNo, oNo)

Rational Rose Data Modeler database design tool

The authors of Data Modeler primarily focused on creating a tool for designing a physical data model. At the same time, there was no rejection of UML as a means of data modeling, and in some way the emphasis was shifted: now UML is supposed to be used to build a logical model. In fact, the logical model is the same object model, consisting of objects - entities. The transition from the logical model to the physical and vice versa in terms of data modeling is provided automatically by Rational Rose. To do this, the correspondence of model elements is introduced.

Table 2.1 Correspondence of the elements of the logical and physical model

Logic Model	Physical model
Class (Class)	table
Operation	Constraint
Attribute (Attribute)	Column
package	Scheme (Scheme)
Component (Component)	Database
Association (Association)	Relationship
	Trigger
	Index (Index)

Thus, conceptually, the Data Modeler module is not a replacement for UML in some of its subsets, but only provides object technology adherents with a powerful tool for effectively building physical database schemas.

The list of main features of Data Modeler includes:

1. Data Modeler supports most of the features of structural CASE tools in terms of physical data modeling;

2. Data Modeler provides the generation of an efficient physical structure of the database that supports mechanisms for ensuring referential integrity;

3. Data Modeler is tightly integrated with Rational Rose, and the Data Model diagram naturally fits into the overall software development technology using the Rational Software Corporation product line;

4. You can choose not to integrate Rational Rose with other physical model generation tools.

5. Conceptual correspondence of data modeling and object models is provided, which allows more efficient software design.

Create a logical model

The main components of a Data Modeler diagram are entities, attributes, and relationships. Each entity is a set of similar individual objects, called instances. Each instance is individual and must be different from all other instances. An attribute expresses a particular property of an object. At the physical level, an entity corresponds to a table, an entity instance to a row in a table, and an attribute to a table column.

The work of Data Modeler is based on the well-known mechanism for mapping an object model into a relational one. The result is the construction of an "entity-relationship" diagram and the subsequent generation of a database description in SQL.

Class diagram (class diagram) serves to represent the static structure of the system model in the terminology of object-oriented programming classes. The class diagram can reflect, in particular, various relationships between individual entities of the subject area, such as objects and subsystems, and also describes their internal structure and types of relationships. This diagram does not provide information about the time aspects of the system operation. From this point of view, the class diagram is a further development of the conceptual model of the designed system.

Development of an IS database for a construction company. IBS has developed an integrated capital construction management system

Send your good work in the knowledge base is simple. Use the form below

Similar Documents

Send your good work in the knowledge base is simple. Use the form below

Similar Documents

Send your good work in the knowledge base is simple. Use the form below

Introduction

The introduction of software products for a unified information network requires the company to develop a culture of management management, large capital investments for implementation, staff training and maintenance.

Thus, in a competitive environment in a market economy, investment and construction companies constantly need information management systems. The creation of such a system is the goal of this work.

1.1 The essence of the information system

1.2 Functional specification

The system should provide independent work for the following categories of users: director, managers, investors and clients.

Investors finance and monitor construction progress. Each object can have several Investors, and one Investor can finance several real estate objects.

1.3 IC design approaches

The problem of complexity is the main problem that has to be solved when creating large and complex IS. No developer is able to understand the entire system as a whole. To date, there are two approaches to the development of IS, which are due to different principles of system decomposition:

Functionally modular or structural - based on the principle of functional decomposition, in which the system is described in terms of the hierarchy of its functions and the transfer of information between individual functional elements

· Object-oriented approach - uses object decomposition. The system is described in terms of objects and connections between them, and the behavior of the system in terms of the exchange between them.

Structured programming methodology emerged. The basis of this methodology is the procedural decomposition of the software system and the organization of individual modules in the form of a set of executable procedures.

In the second half of the 80s, the methodology of object-oriented programming appeared

The main disadvantage of the structural approach is that processes and data exist separately from each other, and the design is from processes to data. Thus, in addition to functional decomposition, there is also a data structure that is in the background.

In the object-oriented approach, the main category of the object model - the class - combines both data and operations. Compared to processes, data is a more stable and relatively infrequent part of the system. One of the founders of the object-oriented approach formulated the benefits as follows:

“Object-oriented systems are more open and easier to change because their design is based on stable forms. This allows the system to develop gradually and does not lead to its complete processing, even in the case of significant changes in the initial requirements.”

This graduation project uses the methodology of an object-oriented approach to describe the business processes of an enterprise.

1.4 Unified Modeling Language UML

A well-thought-out plan is the key to the development process these days. The client must understand what the development team is going to do, and must be able to make adjustments if their tasks are not being fully resolved.

A key aspect of the design process is its proper organization, when analysts, clients, programmers and other specialists involved in the development of the system are able to understand each other and come to a common opinion. The UML language provides such an opportunity.

Another hallmark of the modern systems development process is the lack of time to complete the work. If deadlines for subsystems are piled on top of each other, then ensuring the continuity of the development process becomes a vital necessity.

The need for a quality development process necessitates the creation of standard conventions. The UML is just such a notation.

The UML language is designed to solve the following tasks:

o To provide the user with an easy-to-understand visual modeling language specifically designed for developing and documenting models of complex systems for a wide variety of purposes.

o Provide the original concepts of the UML language with the possibility of extension and specialization for a more accurate representation of system models in the OOAD (object-oriented analysis and design) of a specific subject area.

o None of the UML language constructs should depend on the features of its implementation in known programming languages.

o Encourage the development of a market for object tools.

o Ability to improve.

o Integrate the latest and best practices

Within the framework of the UML language, all ideas about the model of a complex system are fixed in the form of special graphic structures called diagrams. In terms of the UML language, the following types of diagrams are defined:

Diagram of options or use cases (use case diagram)

Class diagram (class diagram)

Behavior diagrams

o Statechart diagram

o Activity diagram

Interaction diagrams

o Sequence diagram

o Collaboration diagram

Implementation diagrams

o Component diagram

o Deployment diagram

The list of these diagrams and their names are canonical in the sense that they are an integral part of the graphical notation of the UML. Each of these diagrams details and concretizes different representations of a complex system model in terms of the UML.

1.5 CASE tool Rational Rose

Rational Rose is a powerful CASE tool for designing software systems of any complexity. One of the advantages of this software product will be the ability to use UML diagrams. We can say that Rational Rose is a graphical editor for UML diagrams.

Within Rational Rose, there are various software tools that differ in the range of implemented features.

Reduction of development time;

Reducing manual labor, increasing productivity;

· improvement of consumer qualities of created programs;

the ability to lead large projects or a group of projects;

· allows to be a language of communication between different developers.

1.6 Use case diagram

The development of this diagram has the following goals:

Determine the general boundaries and context of the modeled subject area at the initial stages of system design

· Formulate general requirements for the functional behavior of the designed system.

· Develop an initial conceptual model of the system for its subsequent detailing in the form of logical and physical models.

· Prepare initial documentation for the interaction of system developers with its customers and users.

Rational Rose tools allow you to use a graphical editor to create Use Case diagrams (scenarios) to describe a functional system. Let's describe the main elements, see Table 1.1.

Interaction Diagrams

Interaction diagrams describe the behavior of interacting groups of objects. Each diagram describes the behavior of objects within only one use case. The diagram shows objects and the messages they exchange with each other. Three types of messages are defined:

informational (informative) - messages that provide the recipient object with information to update its state;

messages - requests (interrogative) - messages requesting the issuance of information about the recipient object;

· imperative (imperative) - messages requesting the recipient object to perform an action.

There are two types of interaction diagrams:

sequences (sequence diagrams);

cooperative (collaboration diagrams).

In a sequence diagram, an object is shown as a rectangle on top of a dotted vertical line. This vertical line is called the object's lifeline. It is a fragment of the life cycle of an object in the process of interaction.

Fig.1.5 Sequence diagram "Assigning a builder to an object"

Diagram output: entity objects (list of users, object, list of builders) and boundary objects - pages (password entry window, current object window) are selected.

The second type of interaction diagram is the cooperative diagram. Similar to sequence diagrams, cooperative diagrams depict the flow of events through a specific use case scenario. Sequence diagrams are ordered by time, while cooperative diagrams focus on relationships between objects.

Fig.1.6. Cooperative diagram "Assigning a builder to an object

Algorithm of working with the system through the WEB-interface

The following diagram shows the sequence of transitions between screens through which the user interacts with the system. The availability of certain screens depends on the permissions of the currently working user.

A class diagram is used to design a site.

Rational Rose includes an Add In called Web Modeler for website design.

each element of the tuple must have a single value, repeating groups of values are not allowed;