Reception System


The CBRS is developed for industrial purpose .At some point it is suitable for industries or organization that only have security post to greet visitors and employees. The system itself is meant for assisting them in daily task. This system is not for only one company but is developed to universally support any companies, industries or organizations.

In general we have to follow reception process manually and due to this it creates a burden .Instead of that cloud based reception system removes these restrictions and process is carried out smoothly without any bugs .The CBRS is used to store information arrived in the system's database. The system also stores the information about the company's visitors and the information will be saved in the company.

This system is mostly used by the employees/ Visitors or guest of the company .Before entering the company the visitors or employees must have to enter their details as required .If the employees are entering then they have to scan their unique cards provided by the company .These cards are unique only for employees.

If the guest or visitors enters the company. Also the visitors needs to fill the required details .The system will automatically captures their photo .System will store the visitors details along with the photo into the database.

The administration can access the record and even it can fetch the records whenever needed. Though our mobile application is offline but whenever data needs to be transfer from application to website then Cloud Synchronization technology is used.

LIST OF TABLES

TableNo. Table Description PgNo.
5.6.1
Stores overall details of employees 30
5.6.2
Stores daily details of employees 30
5.6.3
Stores employees allocated free slots 30
5.6.4
Stores employees login detail before entering free slots 31
5.6.5
Stores visitors details 31
5.6.6
Stores appointments details 31
5.6.7
Stores the admin side details 32
5.6.8 Software Specification of the project 39

LIST OF FIGURES

Figure No. Figure Description PgNo.
1
Shows the life cycle of incremental model 5
2
Shows the chart for project scheduling 7
3
Entity Relationship diagram
17
4
4.1
4.2
4.3
4.3.1
4.3.2
4.3.3
4.3.4 Data Flow Diagram
Context Level
Level :1
Level :2
Employee Verification
Visitor Verification
Appointment Generation
Administration
18-20
5
Use Case Diagram 21
6
6.1
6.2
6.3
6.4
Sequence Diagram
Employee
Visitors
Appointment
Administration

22-25
7
7.1
7.2
7.3
7.4
Activity Diagram
Employee
Visitors
Appointment
Administration

26-29
8
User Interface
33

LIST OF SYMBOLS, ABBREVIATIONS AND NOMENCLATURE

LIST OF SYMBOL

Symbol Description
Use Case


Actor


Flow

Entity

Process
Data Store


Attribute

Relationship/
Decision

Terminator

Start


End


Document
LIST OF ABBREVIATION

Name Abbreviations PgNo.
1. CBRS Cloud Based Reception System 3
2. CBS Cloud Based Reception System 3
3. BIS Bureau of Indian Standards 13
4. ISI Indian Standard Institute 13
5. ISO International Organization for
Standardization 13

TABLE OF CONTENT

PART I INTRODUCTION
1
Chapter : 1 ORGANIZATION PROFILE 1
1.1 Company Detail 1
1.2 Company Objective 1
1.3 Brief History 2
1.4 Domain 2
1.5 Tools and Technology 2
Chapter : 2 INTRODUCTION TO PROJECT 3
2.1 Background 3
2.2 Definition 4
2.3 Abstract 4
PART II SYSTEM ANALYSIS AND DESIGN
5
Chapter : 3 PROJECT PLANNING 5
3.1 Scope of the System 5
3.2 Software Process model 6
3.3 Project Team 6
3.4 Project Schedule 7
Chapter: 4 SYSTEM ANALYSIS 8
4.1 Leteracture Survey 8-11
4.2 Fact Finding 11
4.3 Feasibility Study 12-13
4.4 System Requirements Engineering
a) Requirement Analysis
b) Requirement Specification
i) Functional Requirements
ii) Non-functional Requirements
c) Requirement Definition 13-15
Chapter : 5 SYSTEM DESIGN 16
5.1 Design Principles 16
5.2 ER & DFD 17-20
5.3 Use Case Diagram 21
5.4 Sequence Diagram 22-25
5.5 Activity Diagram 26-29
5..6 Database Design 30-32
5.7 User Interface Design 33
PART III IMPLEMENTATION DETAILS
34
Chapter : 6 PROGRAMMING FUNDAMENTALS 34
Chapter : 7 SCREEN LAYOUTS OR USER MANUAL 35-38
PART IV TOOLS AND TECHNOLOGIES
39
PART V APPENDIX
40
A- Project Tracking 40
B- Limitations & Future Enhancements 40-41
C- Bibliography 41
D-References 41

PART I INTRODUCTION

Chapter: 1 Organization Profile

1.1 Company Detail
A.live Mind is a dynamic and fast-paced start-up. We are a small, dedicated team working from what we consider a home, more than an office, in the vibrant city of Vadodara. We make Smartphone apps which have very simple, down-to earth ideas, but are of immense utility to consumers.
It is at that junction between technology and creativity, at that very thin line, where innovation lies. We aim to work along that line. So let's share and spread the smile! Welcome to A.live Mind.
We make our presence felt in three basic areas ' in the smartphone industry, on the web and amongst the youth. While creating apps, the focus is on making it look good, having a smooth interface and most importantly, making it as user-friendly as possible.
Although not our primary function, we occasionally, take up web design and development project from outside clients. The only requirement is, the project must push our designing and technology skills to a new level.
Also, since we are a nascent company ourselves, it is the youth that we want to engage with. A suit-and-tie corporate hotshot with years of experience under his belt would not be our cup of tea. Here at A.live Mind, we look to bridge the gap between you young people and the industry, thereby enabling you to have a smooth transition.
Contact details:
A.Live Mind
26, Harinagar Society,
Gotri Road,
Vadodara 390007
Gujarat, India
hello@alive-mind.com
+91-8511747769

1.2 Company Objective
Our vision is straightforward, really. We start with the simplest of ideas. However, these ideas require a lot of thinking from a variety of perspectives and often, they don't really remain 'simple' any more by the time the product reaches you. And we do whatever it takes to avoid that.
1.3 Brief History

Alive mind was started in the year 2011 with a team of 5.Mr. Bheshaj Joshi and Mr. Nakul Vakil were the founders of the company. Rob a shop was the first product which was started as pilot project in baroda. Marketing was started in USA, Canada, UK and Southafrica and with in a short time the projects started flowing with which company has recruited developers on all platforms like iOS, Android, Windows and PHP. The current team is of 18. Apart from Web development and Mobile apps, Company concentrates on IT Infrastructure Projects like IT Audits, IT Services.

1.4 Domain
Alive mind pvt ltd is an Information Technology [T.T] based company.

1.5 Tools and Technology
Alive Mind pvt ltd provides the training of the languages such as Android, PHP, .Netjava .Advanced java. Ios, Windows.

Chapter: 2 Introduction to project

2.1 Background

The Cloud based reception System (CBRS/CBS) is universal system that can be implemented in any of the industries or organizations. At some point it is suitable for industries or organizations that only have security post to greet visitor and delivers. The system itself is meant for assisting them in daily task.
The application is used to create secure and protective environments for industries. The project also used to provide authorization and authentication of employees of company and visitors or guest.
As we have to follow reception process manually. These create the heavy load on receptionist. Instead of that Cloud Based Reception System removes this restriction and process is carried out smoothly without any bugs. The cloud Based Reception System (CBRS) is used to store information arrived in the system's database .The System also store the information about the company's visitor's information will be saved in system database.

' Problem Summary :
' Manual entries of records
' Lack of security
' Need of Integrated circuits[IC]
' Burden on receptionist
' Time consuming systems/process

' Scope
' This project works at two sides
1. Client side (Android application)
2. Server side (PHP system)
' To provide authorization and authentication of employees, visitors or guest
' It captures group of users with specific functionalities.

' Expected Outcome
' To keep track of Employees/Visitors/Guest
' Appointment Fixing
' Report Generation
' Attendance Calculating Employees
' Salary Calculation of employees
' The Cloud Based Reception System (CBRS) is expected to be utilized universally, that is in any company, industries or organizations. This system also carries hope that the development of the system will bring better cause for all users.

2.2 Definition:
CBRS/CBS is a universal system that can be implemented in any type of industries/organization

Aim
To keep track of Employees and visitors records, as well as attendance & salary calculation of employees and appointment generation for visitors.

Objectives & goals:
' Provides a friendly environment to maintain records
' To maintain strong security system
' To provide appointment

2.3 Abstract

The CBRS is developed for industrial purpose .At some point it is suitable for industries or organization that only have security post to greet visitors and employees. The system itself is meant for assisting them in daily task. This system is not for only one company but is developed to universally support any companies, industries or organizations.

In general we have to follow reception process manually and due to this it creates a burden .Instead of that cloud based reception system removes these restrictions and process is carried out smoothly without any bugs.
The CBRS is used to store information arrived in the system's database. The system also stores the information about the company's employees and visitors.
This system is mostly used by the employees and Visitors of the company .Before entering the company the visitors or employees must have to enter their details as required .If the employees are entering then they have to scan their unique cards provided by the company .These cards are unique only for employees. Employees attendance and salary will be automatically calculated when they scan their cards.
If the guest or visitors enters the company. Also the visitors needs to fill the required details .The system will automatically captures their photo .System will store the visitors details along with the photo into the database. Also visitors can fixed their appointments according to their suitable time.
The administration can access the record and even it can fetch the records whenever needed. Though our mobile application is offline but whenever data needs to be transfer from application to website then Cloud Synchronization technology is used.

PART II SYSTEM ANALYSIS AND DESIGN

Chapter: 3 Project planning

3.1 Scope of the System
This application is used to create secure and protective environment for industries .The project also used to provide authorization and authentication of employees of company and visitors or guest.
Our Application provides appointments to the clients. The Administration can keep a track of all the records and can access the records whenever required. It works on client side as well as server side. It captures group of users with specific functionalities.

3.2 Software Process model
' Incremental Model :
In incremental model the whole requirement is divided into various builds. Multiple development cycles take place here, making the life cycle a 'multi-waterfall' cycle. Cycles are divided up into smaller, more easily managed modules. Each module passes through the requirements, design, implementation and testing phases. A working version of software is produced during the first module, so you have working software early on during the software life cycle. Each subsequent release of the module adds function to the previous release. The process continues till the complete system is achieved.


Fig: 1

' Advantages of Incremental model:
' Generates working software quickly and early during the software life cycle.
' More flexible ' less costly to change scope and requirements.
' Easier to test and debug during a smaller iteration.
' Customer can respond to each built.
' Lowers initial delivery cost.
' Easier to manage risk because risky pieces are identified and handled during it'd iteration.
' Disadvantages of Incremental model:
' Needs good planning and design.
' Needs a clear and complete definition of the whole system before it can be broken down and built incrementally.
' Total cost is higher than waterfall.

3.3 Project Team
Group Members:
1. Nilam V.Desai
110413116001
L.Y-I.T[B]
9662818086

2. Niyati M. Mevada
110413116008
L.Y-I.T[B]
8460845106

3.4 Project Schedule
Project Schedule is the process of creating a network of the software engineering tasks that will enable the job done on time. After list out the number of modules and requirement, I had scheduled the project
' Decided appropriate model.
' Estimate the amount of work and divided it into specific time iteration.
' Deciding Deadline.

' Scheduling:
I have scheduled my project as per Software Development Life Cycle Technology. Based on the phases of SDLC. I have performed activities for my project.

' Importance:
The interdependencies in the complex systems are very difficult to handle and understand which became easy with proper scheduling of project. It is impossible to track complex software project without scheduling.

Project Scheduling Chart:
JULY AUG SEP OCT NOV DEC JAN FEB MAR APR MAY
ANALYSIS
DESIGN
CODING
TESTING
IMPLEMENTATION
FINAL DOCUMENTATION
Fig : 2

Chapter: 4 System Analysis

4.1 Leteracture Survey
' INTRANET RECEPTION SYSTEM :

' Project Background:
The Intranet Reception System (IRIS) is universal system that can be implemented
in any type of industries or organizations that has receptionist. At some point it is
suitable for industries or organizations that only have security post to greet visitor and
receive deliveries. This system is not for only one company but is developed to
Universally support any companies, industries or organizations. The Intranet Reception
System (IRIS) has four important modules to be covered. The first one is courier
Modules, a module that covers the method of informing and storing information about
any delivery designated to any personnel in the company. The second module to cover is
the visitor module, where through this module receptionist and the company can keep
track visitor that visits the company and their activities and whereabouts in the
Company's site. The third module is appointment and reservation module. Visitor
usually came because of appointment that they have scheduled with the company. The
can even set a new appointment at receptionist counter. The worktlow is made easier
and simpler yet systematic because of the Intranet Reception System (IRIS).
The Intranet Reception System (IRIS) is a new system that has not yet been developed in any company. This idea came to me when I was undergoing my industrial training at
multinational company. The receptionist itself sometimes wonders if there was such
System. So took the liberty to developed one. This Intranet Reception System (IRIS) will
definitely smooth the company's workflow.

' Problem Statements
Problem statements can be considered as setbacks or factors of why this system
Should be developed. These factors are catalyst in building and developing reliable
system. While systems, on the other hand are meant to solve the problems detected and
make life easier. There are a few problems that support the reason of developing Intranet
Reception System (IRIS).

Delivery and Courier Notification :
Each courier or delivery that arrives can be in any type of form. It can be letters
or in forms of packages or parcels. Each of this deliveries and courier often arrives at the
receptionist counter; it is because some needs to be verified by signature and official
stamping. The complications arises when the receptionist want to inform staff about
their deliveries that just arrived. Usually either the staff themselves came to the counter
asking for their couriers or the receptionist will call them to notify them. However, the
staffs sometimes are not at their desk, cubical or office. In some situation, they will be
involved in meetings or such. Other than that, there few times when the staffs has to out
station in order complete their task. This situation adds up to the current problem. The
couriers will get piled up at the receptionist counter.

Appointments:
Appointments are how business greet and meet starts. This will lead to futures
meetings and business closure. Difficulties that arises when outsiders or visitors desires
to set an appointment, that there are no actual appointment system. In some condition,
the receptionist herself will tend to forget to do a reminder for the set appointment.
Adding worst to the situation, the receptionist did not notify and remind the staff about
their appointments. Nowadays, receptionist at a lot of companies only uses reminder
notes to confirm an appointment and stick it anywhere on the counter. Imagine what will
happen if the notes are lost and better yet the receptionist did not realize it.

Visits from Visitors, Vendors or Important Personnel:
Companies often receive a lot of visits from various companies, vendors,
suppliers and even important personnel such as Dato's or ministers and of course with
various agendas. It is complicated and sometimes hard to keep track the visitor's
movement. The numbers and types of visitor do determine the growth of the company. If
it is an important deal to be close, it would really be good to have a full contact detail of
the visitor and the company they came from. The difficulties are, it is hard to monitor
and track the visitors' movement. Other than that, receptionist these days only use log
book system to track their visitor's visit. This is clearly a tradition more that a systematic
method to store information securely. There is not any system that stores complete
information about visitors that came.

' Objectives
There are a few vivid points of objectives of the system that in all covers the
difficulties and problems that arise. The cores of each objective are pointed out together
with a brief but precise explanation.

a. To have a system that records and stores the couriers and deliveries information.
At the same time having the notification sent to the designated personnel, either
through SMS or email. This part of the system will much more practical and
systematic. The Intranet Reception System (IRIS) helps the receptionist by
keying in the appointment in the systems database, and at the same time sending
an informing message trough SMS or email. With this system the staff can
receive their message anywhere and anytime. These will make the distribution of
couriers and deliveries more efficient.

b. To have a systematic and efficient appointment system.
Comparing the future system to the current, one that does not utilizes paper notes
in whole. The future system will promise a more reliable and arrangement
Method of work system. The appointment system that is a part of the Intranet
Reception System (IRIS) will help to smooth the receptionist flow of work.

c. To have an efficient system or method for tracking visitor that visits the company
and their activities in the company. Visitors where about and activities can be monitored.
If it is a case of the company's security or the visitors' safety; the company can pin point the
Visitor's exact location. This apart of the system also covers the security issues. If
there is any criminals act that involves other than the company's personnel, then
this system can help provide an information and maybe solution to the problem.
With the Intranet Reception System (IRIS), each visitor must and will have in
their details in the system keyed in the system. This system is also a part of the
appointment system. All of the visitor's data will be stored in the system
database.

d. To a reliable information system. The system that is reliable in storing information, retrieving information and with this system, her daily task will much
simpler and faster yet efficient. All the daily task of receptionist can be completed
systematically.

However, in certain company the security post and the security guards often
receive the first visit from either visitors or registered delivery companies. The security
also sometimes acts as the producing report. In addition to it, the system itself can maintain the integrity of the information stored in the system's database. Thus, producing a complete and precise report is a must. That is one of many that Intranet Reception System
(IRIS) tries to achieve.

' Scope
The scope of the system captures a group of users with in a network with specific
System functionalities. It means that this system's function liberates what the users
require. This network has wide range of users but only reaches the users who are in this
network. This network is as intranet.

' Project Significance
Intranet Reception System (IRIS) will provide endless benefits to the users. This
is especially for first the power user of Intranet Reception System (IRIS) the receptionist. The receptionist will realize that receptionist counter. It means that the security post or counter also serve as the receptionist counter. So indirectly, these users will also share the same positive benefit that came from the Intranet Reception System (IRIS). At the same time this scenario will also change people view about security guards job.

Last but not least, the company and its whole staff; they will definitely receive the
outcome of utilizing this system, Intranet Reception System (IRIS). They will find that
the workflow of the company is becoming smoother than before.

Every appointments and meeting are scheduled timely and systematically, more over well informed. Couriers that arrive will distribute and received by the designated personnel efficiently. It is all because of the Intranet Reception System (IRIS).

' Expected Output
The Intranet Reception System (IRIS) is expected to be utilized universally, that is
in any company, industries or organizations. This system also carries hope that the
development of the system will bring better cause for all users.

' Conclusion
The projects introduction has been put out in the open. Together with the
statements of each problem that comes from the current system, new and more advanced
system will emerge. This system will definitely covers all the stated objectives as well as
ensuring that individual that falls in the system's scope will obtain the expected output.
In short, this is what the Intranet Reception System (IRIS) is meant and developed for;
to simplify daily task. In addition, this system will help in enhancing and ensuring the
company's growth. In the next chapter, a more precise and complete explanation will be
provided as well as the skeleton of the project.

The main difference between Intranet reception System(IRS) and the cloud base reception system(CBRS) is that the execting system is not developed in Android platform whereas we are developing a somehow similar type system using android platform.

4.2 Fact Finding
To study any system the analyst needs to do collect facts and all relevant information. the facts when expressed in quantitative form are termed as data. The success of any project is depended upon the accuracy of available data. Accurate information can be collected with help of certain methods/ techniques. These specific methods for finding information of the system are termed as fact finding techniques. Interview, Questionnaire, Record View and Observations are the different fact finding techniques used by the analyst. The analyst may use more than one technique for investigation.

' Interview
This method is used to collect the information from groups or individuals. Analyst selects the people who are related with the system for the interview. In this method the analyst sits face to face with the people and records their responses. The interviewer must plan in advance the type of questions he/ she is going to ask and should be ready to answer any type of question.

' Questionnaire
It is the technique used to extract information from number of people. This method can be adopted and used only by an skillful analyst. The Questionnaire consists of series of questions framed together in logical manner. The questions are simple, clear and to the point. This method is very useful for attaining information from people who are concerned with the usage of the system and who are living in different countries.

' Recordview
The information related to the system is published in the sources like newspapers, magazines, journals, documents etc. This record review helps the analyst to get valuable information about the system and the organization.

' Observation
Unlike the other fact finding techniques, in this method the analyst himself visits the organization and observes and understand the flow of documents, working of the existing system, the users of the system etc. For this method to be adopted it takes an analyst to perform this job as he knows which points should be noticed and highlighted. In analyst may observe the unwanted things as well and simply cause delay in the development of the new system.

4.3 Feasibility Study

Feasibility literally means whether some idea will work or not. It knows before hand
Whether there exists a sizeable market for the proposed product/service, what would be the investment requirements and where to get the funding from, whether and wherefrom the necessary technical know-how to convert the idea into a tangible product may be available, and so on. In other words, feasibility study involves an examination of the operations, financial, HR and marketing aspects of a business on ex ante (Before the venture comes into existence) basis. Feasibility is a multivariate concept; that is,a project has to be viable not only in technical terms but also in economic and commercial terms too. Moreover, there always is a possibility that a project that is technically possible may not be economically viable. The tests of feasibility are: Economical, Technical, Operational and time Feasibility.

' Economical feasibility:

The objective of economical feasibility is to ascertain whether the proposed project will be financially viable in the sense of being able to meet the burden of servicing debt and whether the proposed project will satisfy the return expectations of those who provide the capital. While conducting a financial appraisal certain aspects has to be looked into like:
- Investment outlay and cost of project
- Means of financing
- Projected profitability
- Break- even point
- Cash flows of the project
- Investment worthiness judged in terms of various criteria of merit
- Projected financial position

' Technical feasibility:

The issues involved in the assessment of technical analysis of the proposed project may be classified into those pertaining to inputs, throughputs and outputs.
' Input Analysis: Input analysis is mainly concerned with the identification, quantification and evaluation of project inputs, that is, machinery and materials. You have to ensure that the right kind and quality of inputs would be available at the right time and cost throughout the life of the project
' Throughput Analysis: It refers to the production/operations that you would perform on the inputs to add value. Usually, the inputs received would undergo a process of transformation in several stages of manufacture. Where to locate the facility, what would be the sequence, what would be the layout, what would be the quality control measures, etc. are the issues that you would learn in greater details in subsequent lessons.
' Output Analysis: this involves product specification in terms of physical features- colour, weight, length, breadth, height; functional features; chemical material properties; as well as standards to be complied with such as BIS, ISI, and ISO etc.

' Time feasibility:

Time Feasibility is a determination of whether a proposed software will be completed within given time or not.

4.4 System Requirements Engineering

a) Requirement Analysis :

Requirements analysis in systems engineering and software engineering, encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements

Requirements analysis is critical to the success of a systems or software project.[3] The requirements should be documented, actionable, measurable, testable, traceable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.

Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. In software engineering, such requirements are often called functional specifications. Requirements analysis is an important aspect of project management.

Requirements analysis involves frequent communication with system users to determine specific feature expectations, resolution of conflict or ambiguity in requirements as demanded by the various users or groups of users, avoidance of feature creep and documentation of all aspects of the project development process from start to finish. Energy should be directed towards ensuring that the final system or product conforms to client needs rather than attempting to mold user expectations to fit the requirements.

Requirements analysis is a team effort that demands a combination of hardware, software and human factors engineering expertise as well as skills in dealing with people.

b) Requirement Specification

i)Functional Requirements : It includes the following modules .

' Employees verification :
To keep track of employees activities. Maintain complete information about employees of organization that arrives and leaves. The Employees have to enter their details as well they have to scan their unique card provided from the company. Also the employees attendance will be calculated by the system. While entering, the employees needs to give all their detail like name, email_id , barcode number, entry & exit time etc.

' Visitors verification :
To keep track of Visitors activities and movements . Maintain complete information about visitors as they arrives and leaves .As soon as the visitor enters the company System will captures the visitor's photo. They have to enter their details before entering the company.The Visitors enter their details such as visitor's name , date & time , purpose , the person whom visitor wants to meet etc.

' Appointment :
The System has a option for providing the appointment. The clients has to enters his/her .If appointment is available a notification is send on users clients mobile phone by the receptionist.. He/she has to enter the details such as client's name, designation , purpose ,date & time , Employee name to whom clients wants to meet.

' Administration :
Administration can access the records which are stored in tab/mobile via cloud synchronization Also can fetch specific entries about employees and visitors .After accessing the records ,the Admin can also generate the report about all entries as per their requirements.

ii) Non-functional Requirements:

' Performance Requirements:
The primary performance requirement is speed of the network and the various notifications should be timeliness and relevant.
' Software Quality Attributes:
The primary attribute of this application will be usability given the large amounts of data and information that will be presented on such a small screen, as well as the user's ability to input data into the device in a reasonable manner that should not be that much more difficult than if they were at an actual computer. As usability is hard to quantify, substantial user testing will be needed and feedback gathered in order to determine if the application can generally be considered usable.

Because this application will be on a phone, portability is also important. We don't want it to take up so much space or be too slow causing the user's to not be able to fit it on the device.
Interoperability is something that is specifically not important, at least at the beginning. The Android device is being used because both of its popularity and the ability for the code to be open-source. This is in contrast to other phones, like the iPhone, which would not allow for open source application development and would go against the goals of the overall project. However, in the future, the ability to use this on other phones that support the goals of the project would be nice, but that is also outside of the scope of this project.

c) Requirement Definition:
A software requirements definition is an abstract description of the services which the system should provide and the constraints under which the system must operate. System requirements may be either functional or non-functional requirements. There are three types of major problem with requirements definitions written in natural language:
' Requirements confusion,
' Lack of clarity
' Requirements amalgamation
Some organizations try to produce a single specification to act as both a requirements definition and a requirements specification. When a requirements definition is combined with a specification there is often confusion between concepts and details.
The most useful approach to writing a readable requirements definition is to invent a standard format and to ensure that all requirements definitions adhere to that format.

Chapter : 5 System Design

5.1 Design Principles

Following are the System Design Principles: The design process should not suffer from 'tunnel vision'. A good designer should consider alternative approaches.

' The design should be traceable to the analysis model.
' The design should not reinvent the wheel. Time is short and resources are limited! Hence use well tested and reusable s/w components.
' The design should 'minimize the intellectual distance' between the S/W and the problem as it exists in the real world. That is, the structure of the software design should (whenever possible) mimic the structure of the problem domain.
' The design should exhibit uniformity & integration. A design is uniform if it appears that one person developed the whole thing.
' The design should be structured to accommodate change. Upcoming modifications and improvements should not lead to drastic changes or redesign of software.
' The design should be structured to degrade gently, even when aberrant data, events, or operating conditions are encountered. Use message/progress bars whenever possible.
' Design is not coding, coding is not design.
' The design should be assessed for quality as it is being created, not after the fact.
' The design should be reviewed to minimize conceptual (semantic) errors.

' Model :

' ER Diagram:


Fig: 3
' Data Flow Diagram

4.1 Context Level:


4.2 Level : 1



Level : 2

4.3.1 Employee Verification

4.3.2 Visitor Verification

4.3.3 Appointment Generation

4.3.4 Administration

5.3 Use Case Diagram

Reception System :


Fig :5.1
Employees :


Fig :5.2

Visitors :


Fig :5.3

Administrator :

Fig :5.4

5.4 Sequence Diagram

Employee:


Fig : 6.1

' Visitors:


Fig : 6.2

' Appointment:


Fig : 6.3

' Administration


Fig: 6.4

5.5 Activity Diagram :

' Employees


Fig : 7.1

' Visitors


Fig: 7.2

' Appointment:


Fig: 7.3

' Administrator :




Fig: 7.4
5.6 Class Diagram :


5.7 Database Design :

5.6.1 emp_details :
Field Name Data Type Description
Empid Varchar(10) It is unique serial ID number.
barcodeno Varchar(500) It is unique ID number.
Ename Varchar(50) It stores the employee name
Desg Varchar(50) It stores the designation of employee in company
Ephno Int(12) It is the phone number of employee
Email Varchar(50) It is the email address of employee
Eadd Varchar(50) It is a residential address of employee

5.6.2 empscan:
Field Name Data Type Description
Scanno Int(200) It automatically generates the unique scan number.
Barcodeno Varchar(600) It is unique serial ID number
Empname Varchar(100) It stores the employee's name.
Curdate date It stores the current date.
Entrytime time It stores the entry and exit time of employees
Flag Int(11) It stores either 0 or 1 value
Hrdiff Int(200) It stores the hour's difference of the same date.

5.6.3 emplogin
Field Name Data Type Description
user name Varchar(25) It stores the user name for employees
password Varchar(25) It stores the unique password for employees
empname Varchar(25) It stores the employee's name

5.6.4 empmng:
Field Name Data Type Description
Empno Int(200) It is unique ID number of employees.
Barcodeno Varchar(600) It is unique ID number.
Empname Varchar(500) It stores the employee's name
month1 Varchar(20) It stores the attendance month wise.
Halfday int(30) It stores the total half days of employees in whole month.
Fullday Int(30) It stores the total full days of employees in whole month.

5.6.5 empslot :
Field Name Data Type Description
Empname Varchar(50) It stores the employee's name.
date1 date It stores the date in which employees want to allocate their freeslot.
from1 time It stores the starting time from which the slot is allocated.
to1 time It stores the ending time from which the slot is allocated.

5.6.6 Visitor_details:
Field Name Data Type Description
Vid Varchar(6) It stores the unique ID for visitors
Vname Varchar(50) It stores the name of visitors
vcno Int(12) It stores the arrival contact number of employees
Veid Varchar(50) It stores the visitors email address.
curdate Date It stores the current date.
ptyp Varchar(50) It stores the purpose type.
purpose Varchar(100) It stores the purpose of the visitor why he/she came to the company.
photo Varchar(100) It stores the path of the visitor's photo
idproof Varchar(100) It stores the path of the visitor's id proof.

5.6.7 app_sch:
Field Name Data Type Description
Eid Varchar(50) It stores the unique employee id.
Empname Varchar(100) It stores the name of employees.
Dt Date It stores the allocated dates of employees.
from1 Time It stores the allocated starting time.
to1 Time It stores the allocated ending time.
Vname Varchar(100) It stores the name of visitors.
Vcont Varchar(600) It stores the contact number of visitors
Vmail Varchar(20) It stores the email address of the visitors.

5.6.7 Amin_tbl :
Field Name Data Type Description
Adminid Numeric It stores the id number of admin
Username Varchar(20) It stores the user name for admin
Password Varchar(20) It stores the password for admin
Emailadd Varchar(20) It stores the email address for admin
Phno
Numeric It stores the contact number of admin

5.8 User Interface Design :


PART III IMPLEMENTATION DETAILS

Chapter : 6 Programming Fundamentals

Android is a software stack for mobile devices that includes an operating system, middleware and key applications. Android is a software platform and operating system for mobile devices based on the Linux operating system and developed by Google and the Open Handset Alliance. It allows developers to write managed code in a Java-like language that utilizes Google-developed Java libraries, but does not support programs developed in native code.

The unveiling of the Android platform on 5 November 2007 was announced with the founding of the Open Handset Alliance, a consortium of 34 hardware, software and telecom companies devoted to advancing open standards for mobile devices.

When released in 2008, most of the Android platform will be made available under the Apache free-software and open-source license.
In July 2005, Google acquired Android Inc., a small startup company based in Palo Alto, CA. Android's co-founders who went to work at Google included Andy Rubin , Rich Miner , Nick Sears , and Chris White . At the time, little was known about the functions of Android Inc. other than they made software for mobile phones.
Hardware Requirement: The system requires the Android Operating System with the minimum version 1.6. It also uses the SDK version 4. The System can also be execute on either laptops or personnel computer with the requirement of 2GB RAM and 356 HDD.
Software Requirement: The System requires the Android platform for App and PHP platform on web based app. The database SQLite is used for Android and MySQL is used for PHP. The Application can be run at either client side or server side whereas the web based application is run at server side.

' Test Cases :
A test case, in software engineering, is a set of conditions or variables under which a tester will determine whether an application, software system or one of its features is working as it was originally established for it to do.

The mechanism for determining whether a software program or system has passed or failed such a test is known as a test oracle. In some settings, an oracle could be a requirement or use case, while in others it could be a heuristic.

It may take many test cases to determine that a software program or system is considered sufficiently scrutinized to be released. Test cases are often referred to as test scripts, particularly when written - when they are usually collected into test suites

' Formal test Cases :
In order to fully test that all the requirements of an application are met, there must be at least two test cases for each requirement: one positive test and one negative test.

If a requirement has sub-requirements, each sub-requirement must have at least two test cases. Keeping track of the link between the requirement and the test is frequently done using a traceability matrix.

Written test cases should include a description of the functionality to be tested, and the preparation required to ensure that the test can be conducted.

A formal written test-case is characterized by a known input and by an expected output, which is worked out before the test is executed. The known input should test aprecondition and the expected output should test a postcondition.

' Informal test Cases
For applications or systems without formal requirements, test cases can be written based on the accepted normal operation of programs of a similar class.

In some schools of testing, test cases are not written at all but the activities and results are reported after the tests have been run.
In scenario testing, hypothetical stories are used to help the tester think through a complex problem or system. These scenarios are usually not written down in any detail.

They can be as simple as a diagram for a testing environment or they could be a description written in prose. The ideal scenario test is a story that is motivating, credible, complex, and easy to evaluate. They are usually different from test cases in that test cases are single steps while scenarios cover a number of steps of the key.

1. Admin
SR NO. LABEL DESCRIPTION EXPECTED RESULT ACTUAL RESULT
1 Password When password is correct after the system is logged on Message will be generated 'enter valid password' Test is successfully completed
2 Name Unique field provided to admin Authentication Test is successfully completed
3. Add ,Edit & delete employees details Admin can add new employees as well as edit & delete previous
details Adding,
Updating & deleting records Test is successfully completed
4. Searching Search for employees &
visitors Fetching employees & visitors details Test is successfully completed

2. Employees

SR NO. LABEL DESCRIPTION EXPECTED RESULT ACTUAL RESULT
1 Name Unique field provided to User Authentication Test is successfully completed
2 Password When password is correct after the system is logged on Message will be generated 'enter valid password' Test is successfully completed
3 Registration Admin registers all users after login Message will be registration first. Test is successfully completed
4 Verification Checks whether the employee's barcode is authenticated or not Message will be displayed as valid or invalid barcode Test is successfully completed
5 Slot Allocation Employee allocates their feasible slots for visitor's appointment Message will be the appointment time period for some duration Test is successfully completed
6. Attendance & salary calculation Calculates daily attendance & monthly salary Message will be the employee sattendance & salary Test is successfully completed

3. Visitors :

SR NO. LABEL DESCRIPTION EXPECTED RESULT ACTUAL RESULT
1 Name Unique field provided to User Authentication Test is successfully completed
2. Registration Visitors registers all their important
details Message will be registration first. Test is successfully completed
4 Verification Checks whether the visitor is authenticated by capturing their image and scanning ID proof Message will be displayed as valid
user Test is successfully completed

' White-box testing

White-box testing and test cases are primarily concerned with achieving the broadest possible coverage of the source code. Therefore, the testers must be familiar with the logic of the application and use this knowledge to create test cases that execute as much of the code as possible. Again, the goal is to break the system.

White box test cases test different control flow paths in a program. The test cases also test decision points (true and false), execute loops, and check internal data structures of the application. Basis path testing, equivalence partitioning, and boundary value analysis are all used to create white box tests. Equivalence partitioning divides the set of possible input values into equivalence classes. Only a value from each of the equivalence classes needs to be tested. Boundary value analysis looks at testing around a set boundary.

Chapter : 7 Screen Layouts or User Manual
' CBRS is a system which can be used by either employees or the visitors



' . As soon as the system starts two options are available as shown below.

' The employees must have to scan their unique cards. As well as they can allocate their free slots as shown.

The first option is scanning which allows the employees to scan their unique id card.If the barcode is valid then only the employee is able to enter the company.Similarly for exit he/she has to scan their ids.


' Before allocating slots the employee must have to login with their username and password for their verification purpose

' The employee can select their free slots using this calender as shown .





' The Visitors before entering the company has to fill their details and they have to scan their ID proof.The system even automatically captures the visitor's photoes. The visitor can also get the appointnments as shown.

' For entering the company , Visitors should be registered by the following details.


' After filling the form , the system captures the photo of the visitors as well it captures the image of visitor's identity proof such as licence, voterid card etc.

' For getting the appointments , the visitors are provided several options for checking the avability.As well as they have to fill their detils for acheving appointments.

' The visitor can check the avability by just enetring the employee's name.If the avability is there list will be displayed.user can fixed the suitable appointnment



' For fixing the appointnment the user has to fill their details .If the appointnment is provided to the visitor then a message or mail is sent to the visitor.

Screen Layouts of websites :

' The Website is only for the admin purpose.The Administrator can handle the database as well as he/she can keep a track on employees & visitors. Admin needs to enter his/her unique username and password as soon as they login.


' Two options are provided in the admin home page.The first is Employee log and the second is the search option.This is shown below

' The Admin can Add an employee in the employee master table using the add option provided in the Employee log.

' Similarly the admin can edit the employees details in the its master table as shown below.



' The employees unwanted records or details using the delete option in employee log.

' The admin can search their desire employees records just by selecting the employees name.


' The Employees list of appointment will be shown as below.And by export option ,the admin can get a report of that employee details.


' Similarly the admin can keep a track of visitors details by entering the dates.All date wise records will appear.


The Admin can even get the report for the visitor's who had visited in the company by using the Export option .

PART IV TOOLS AND TECHNOLOGIES

' Hardware specification

' Required devices :
1. Tab/Mobile with android operating system(min.)
Android version 1.6
SDK version 4
2. Laptops/Personal computers with (min.)
2GB RAM
356 HDD

' 5.6.8 Software specification

contents Tab/Mobile Application Web based application
(server side)
Platform Android PHP
Database SQLite MySQL
Run at Client side, server side Server side

PART V APPENDIX

A. ProjectTracking:
Project Tracking refers to the management of projects, which includes but is not limited to measuring and reporting the status of milestones, tasks and activities required in achieving the pre-defined project results. Project Tracking can also refer to Project Management software, which automates the tracking of tasks, assignments, events and activities related to the project.
One of the key components of Project Management is controlling. Typically, the needs of the project determine the level of detail at which you need to track progress. In example, you may track simple milestones to ensure that they have been reached, or you might track the number of hours each resource has spent on a task and the associated costs. Project tracking requires a careful balance of monitoring to ensure that you will achieve the results and respond to any incidents or roadblocks, while avoiding micro management and reducing team member's ability to make decisions.
Duration of a project's terminal element is the number of calendar periods it takes from the time the execution of element starts to the moment it is completed. Project duration is the measure of the elapsed months that a project is completed in.
As with most aspects of the software development process, software duration has many influencing factors.

As discuss before the analysis phase should be completed in month of September but originally it was completed in December. Designing and half coding portion was completed in month of April. And the final report was developed in month of starting December.

B. Limitation & Future Enhancements

' Limitations :

1. Security : A unique card is required for employee verification .After scanning that card , employees are allowed to enter the company. Any unauthorized person can enter the company using that unique card.Thus it shows the lack of security.

2. Device Limitation : Another drawback is device limitation.The device needs android platform to execute the applications.

' Future Developement required :

Only the attendance calculation process is included in this system. On the basis of these attendance we can also calculate the employees salary. In other words , payroll system can be included in the CBRS.
The system has the limitation of lack of security. So the security can be improved by using different techniques such as retina scanning, biometerics etc.

C. Conclusion :
The projects introduction has been put out in the open. Together with the statements of each problem that comes from the current system, new and more advanced system will emerge.

This system will definitely covers all the stated objectives as well as ensuring that individual that falls in the system's scope will obtain the expected output.

In short, this is what the Intranet Reception System (IRIS) is meant and developed for ;to simplify daily task. In addition, this system will help in enhancing and ensuring the company's growth.

D. Bibliography

http://www.google.com
http://www.att.com
http://en.wikipedia.org
http://www.americanbar.org/publications
http://www.trrproject.com
http://www.gammacom.co.uk

E. References :

1. Mark Murphy (2010) Decent Android References-The Busy Coder's Guide to Android Development_ Version 3.1

2. CJ - "Java in a nutshell but on Android will be good'-volume 5.

Source: Essay UK - http://doghouse.net/free-essays/information-technology/reception-system.php


Not what you're looking for?

Search:


About this resource

This Information Technology essay was submitted to us by a student in order to help you with your studies.


Rating:

Rating  
No ratings yet!


Word count:

This page has approximately words.


Share:


Cite:

If you use part of this page in your own work, you need to provide a citation, as follows:

Essay UK, Reception System. Available from: <http://doghouse.net/free-essays/information-technology/reception-system.php> [22-02-19].


More information:

If you are the original author of this content and no longer wish to have it published on our website then please click on the link below to request removal:


Essay and dissertation help

badges