DEVELOPMENT A SYSTEM FOR MONITORING ACCESS TO BUILDINGS.

D. oi1, A. Mici2.
1. Faculty of Scienes, Kosovska Mitrovica, Serbia
2. Faculty of Technical Sciences, Kosovska Mitrovica, Serbia

RAZVOJ SISTEMA ZA NADZOR PRISTUPA ZGRADAMA.

D. oi1, A. Mici2.
1. Prirodno-matematiki fakultet, Kosovska Mitrovica, Srbija
2. Fakultet tehnikih nauka, Kosovska Mitrovica, Srbija

In this paper we were developed a system for monitoring access to buildings. Software package MS Project, which
have geat features, was used for developing a project for managing a realization such a complex task.

Introduction
In everyday life we manage various types of projects. Some of them are obvious,
as you account for their performance received from direct supervisors, such as the project of
introducing a new information system, or placing a new product to market. On the
other hand, there are projects that are not so obvious, and with which we encounter every day:
going to the supermarket or organization vacation for you and your family.
Understanding what all projects, regardless of how much their size, have a
common understanding is the basis of everything that they can do projects for our daily lives.
All
projects are: general
objective, the
manager, individual
tasks, time
constraints, resources and budget. Project management is, in simple terms, be seen as a process of
managing all
elements
of the
project,
regardless of
its
size [1].
Research must begin by analyzing the problem, ie. to break down problems into parts that we can
understand and with which we try to resolve. A key component is the development
of communication
between
the
customer and the
designer, if the
communication failure experienced the same thing will happen to the system. In order
to eliminate a lot about nedumica realization, we need to do a detailed plan [2]. The aim of this
work, the plan of planning and project management system for monitoring access to
buildings. Inour case should be provided access only to authorized persons and keep a record of
access to the building.

The systematic approach includes the analysis and synthesis: breaking the problem into
parts, the formulation of solutions for each part and assembling these parts into a
coherent whole. Breaking into parts of our project would give the following results:
Review of system
Requirements analysis,
Design,
Construction,
Testing,
Install,
Maintenance,
Education of users,
Preparation of documentation.
Business start working with customers and potential customers that we understand their
wants and needs. At the same time check whether they are satisfied with our knowledge of their
needs. Exactly this is the first step in our project review system.
Records of requirements
Understanding the function and purpose of the system begins by examining the
request. Requirements analysis involves more than simply recording what the client wants. It is
necessary to find the demands around which we can agree with the client and for which we
can formulate test procedures. The access control system for
the building plan collection requirements are decomposed to collect user requirements:
Interview,
Analysis of the facility,
Processing of documentation,
Documentation of tasks.
The analysis, discussion and defining user requirements:
Analysis of the user requirements,
Planning to collect additional user requirements,
The collection of additional user requirements,
Defining user requirements,
Summarize all user requirements,
Documentation of user requirements,
Confirmation of user requirements by users and managers.

We distinguish between functional and nonfunctional requirements. Functional

requirement describes the behavior of the function of necessary activities. Functional
requirements define the boundaries that surround the solution to our problem, while the nonfunctional requirements, the demand for quality. The design constraint is the decision made in
advance, for example, the choice of platform or interface components, which limits the set
of possible solutions to the considered problem. Process constraint is the constraint that refers to
the techniques and resources that can be used in building systems.

Staff on the project

In order to determine the deadlines for the project and assess the needs and
expenses, traba know peoplewho will work on the project, on what works, as well as specialty and
experience that they must possess to overall performance of assigned tasks. Regardless of
the model, there are certain activities that are necessary in any project that in his work contains part
of the software.
The key activities include:
Requirements analysis,
System design,
The design of the program,
Implementation of the program,
Testing,
Training,
Maintenance,
Quality Assurance.
Assign tasks of workers depends on the size of the project, experience and training of staff. There is
a great advantage assigning different responsibilities to different groups of people,
thus enabling checks and balance, which provides error detection in the early stages
of development. After making decisions about the roles of project team members, it is necessary
to make a decision about the people who are for each of them needed. In a development project, the
development team members communicate with clients and with the client.
Required work
One of the turning point of view of planning in the management system is the
understanding about how the project would cost. Cost overruns could lead to abandonment
of the project, while underestimating the costs can force the project team that a lot of
time spent without financial compensation. Good cost estimates early in the project helps the
project manager to determine the number of people needed to develop and agree that
appropriate personnel are available precisely when needed. From the budget of the
project covers more types of costs: funds, personnel, methods and tools. Cost
of funds include: hardware, space, furniture, telephones, modems, heating and air
conditioning, cables, disks, paper, pens, copiers and all other items that make up the physical
environment in which they will work the project team.
Other project costs include the purchase of software and tools to support development
activities. In addition to tools for designing and coding system for the project can be
acquired and software for processing, organization, documentation,

testing and tracking code changes, and generate test data, and support group meetings and so
on.
The project plan
To transfer the results to clients of the risk analysis and proposed management of, anticipated
costs in connection with the project, terms and organization of this system, we make a project
plan. Written planincludes customer needs / requirements regarding our intentions and to
meet those needs / requirements.The contracting authority analyzes the plan to get information on
activities during the development process, which allows him to easily monitor progress of the
project. The plan also could be grounds for confirmationcommitted assumptions, especially those
related to costs and deadlines. After completion of work related to the consideration
of system requirements, and staff to determine the start of project planning work will
continue designing software structures, where we find the following phases (activities).
1. Development of specifications of the system:
The development of functional specifications,
The development of the behavior of the system (diagram)
The development of data models,
The development of non-functional specifications,
Creation of a preliminary user manual.
2. Designing the structure of the system:
Designing the structure of the software,
Defining the interface software with the appropriate environment,
Defining the resources required to realize software
Designing the hardware structure,
Defining the hardware interface with the environment,
Defining the resources required for implementation of hardware,
Designing the structure of the network,
Defining the resources required for the network,
3. Development of the system:
Designing the system to control access to buildings,
Designing the system for authorization,
Design of the central management,
Designing the control system output,
Designing the system to identify the areas of management powers.
With
this system we
have
defined boundaries, and these define what
will encompass
the system and what isnot. It guarantees the Employer that we understand what the project
requires. Time limits can be expressedthrough the structures of work and deadlines, to
show what will happen at any point during the project lifetime.Gantt chart is useful to illustrate
the parallel nature of some tasks in the development process. So the parallel phase
of construction includes planning and overseeing the development of software and hardware
development.
Software development includes:
Presentation of the plan and division of tasks,

 Verification of the developed structure of the software,

Design and implementation of software (detailed structure of the software),
Design and implementation of databases,
o Design and implementation of software for authorization and access control,
o Design and implementation of software to work with the cards
(issuance, modification and destruction of cards)
o Design and implementation of software for working with reports, schedules, and archives,
o Design and implementation of software for security and monitoring,
o Design and implementation of software for automatic control devices,
Design and implementation of network software,
Coding software,
A

preliminary assessment of software functionality,

Testing of software modules,
The identification of errors,
Change the code
Testing of the revised code.
Technical description contains hardware and software, including compilers, interfaces,
and equipment orspecial purpose software. The process of developing hardware would
include the following stages: acquisition of hardware, the hardware implementation of the system,
testing of system hardware, design and implementation of network infrastructure and network
infrastructure testing. In the event that the system sets the requirements for safety, sometimes it
is necessary and a special security plan. Security includes confidentiality, availability and
integrity, and therefore the plan must explain how each of these segment saffect the development
of the system. To test it effectively, you must be well planned. Therefore, the project plan should
include a comprehensive approach to testing in the project. Or testing the system for monitoring
access to buildings include: the implementation of the new system in hardware
infrastructure, parallel operation of old and new systems, suspension of work of the old system.
During the development phase, several documents will be generated, especially in the case of
large projects in which information about design solutions must be available to all project
team members. The project plan lists the documents that need to be developed, who
will explain them when you make, and also in accordance with the configuration
management plan, describes how to edit documents.
To make the training process started immediately after the delivery system, and
sometimes before, usually for training courses and supporting documents prepared under
development, rather than after delivery systems. The project plan defines the manner of
conducting the training, course content, supporting software and documentation, as well as
the necessary background of each student, ie. installation, user training and maintenance.
Finally, if the project team will maintain the system after delivery, the project plan should
consider the responsibility for editing code, hardware repairs and updating of supporting
documentation and training materials.
Management Plan
Project managers are taking steps to ensure that their projects are completed on time and within
theconstraints of work and costs. However, governance involves far
more monitoring and prematurely. We needto determine whether an adverse event may
occur during the development or maintenance, so make plans to avoid these things, or, if they

are unavoidable, minimize the negative consequences. We need to engage in risk management to
understand the differences and manage them in your project.
There are two main sources of risk: risks and general risks that are specific for the
envisaged project. The general risks are risks that are common to all projects in your area contain
software, such asmisunderstanding of requirements, the departure of key employees, or
insufficient time for testing. Risks specific to the project are the threats that are a consequence of
the weak points of a specific project.
Computer software can contribute significantly to the risk management and managed the
project, as a tool for recording, calculating, analysis, presentation preparation itself to
help connect the project details. Microsoft Project (MS Project), Figure 1, is a management
software program that is designed to assist project managers in developing plans,
assigning resources to tasks, tracking progress, managing budgets
and analyzing workload [3].

Figure 1. Microsoft Project.

But can not produce, nor guarantee a successful project plan. However, in many ways, can
be invaluable in planning and managing projects. It helps us to develop a good plan. Since the
software required to accurately determine the tasks necessary to meet the objectives of the
project, we must carefully consider the details of the project. The discipline imposed on an
understanding of these details helps us to organize a good plan. Display screens provide an
organized presentation of details of the plan, which facilitates us to visualize, organize and
refine the plan.
Microsoft Project makes calculating much easier and more reliable projections. Based on the
information we provide, which calculates the project schedule, showing when each task
should start and finish when I have the resources (including people, equipment,
facilities etc..) arranged to perform certain tasks. If you have provided all necessary
information, this schedule also shows the likely costs of the project [4].
In this way we are enabled to easily test various "what-if" scenarios. The project allows us to
experiment with different elements of the plan to get us to the best plan. The
project detects when sources take more time than is available or when
the far end deadlines impossible to meet the constraints that we have entered [5].
Conclusion
The system for monitoring access to buildings helps us to justify the plan to others. The
project provides printed reports and facilitate the approval of our plan by the client or senior

management. Similarly, the project plan makes it easier exposition of supervisors to

workers, to simplify obtaining their consent and cooperation.
MS Project helps us to monitor progress and detect potential problems. Once
the project started, working on tasks that begins and ends, the date for the tasks in the
schedule replacing the actual dates. Software update schedule so you enter the actual
dates and end dates, provides a new project and its costs. The new
forecasts provide valuable warning us about potential delays or cost overruns. However, it must
be emphasized that the project management software, like any other software, useful only
as reliable complete data that we have entered.
Another very important fact must be emphasized for the system to control access to buildings,
which is designed to provide access only to authorized persons and keep a record of access to the
building in several categories, with very small corrections we can use for different sizes of
buildings and business property.

Acknowledgment
This work is supported by Ministry of Science and Technological Development, Republic
of Serbia, under Grant No. III 47016.
References
1. Stoki, M. Pojam upravlanja projektima.(2008) Preuzeto sa: http://www.linkelearning.com/dlmaterijali/materijali//Project_2007/SadrzajNJpdf/PRJ_01.pdf
2. Shari L. P., & Joanne M. A. Sftvrsk ininjrstv (tri i prks), Prvd: vnvi, S.,
Gnd, J., i dr nkvi, R., Cet, Bgrd 2006.
3. Wikipedia, World Geodetic System. Preuzeto sa:
http://en.wikipedia.org/wiki/Microsoft_Project
4. Chatfield, C., & Johnson, T. Microsoft Project 2010 korak po korak, CET i Portalibris,
Beograd 2010.
5. Leti, D. i Jevti, V. Upravljanje softverima, metode i softver. Zrenjanin 2007.