STUDENT ATTENDENCE MANAGEMEN

SYSTEM
Project report Submitted in partial fulfillment of the requirement
For the award of the degree of

Bachelor of Computer Application

To
Mahatma Gandhi University, Kottayam
Guided by
Mrs. Lumy Joseph
Submitted by:
1. MARIYA WILLSON (140021044818)
2. REMYA REGHU (140021044829)

Marian College Kuttikkanam

Batch (2014-2017)

DECLARATION
We, MARIYA WILLSON (Reg. No 140021044818) and REMYA REGHU (Reg. No
140021044829) certify that the Minor project report entitled STUDENT ATTENDENCE
MANAGEMENT SYSTEM is an authentic work carried by us at Marian College
Kuttikkanam. It has not formed the part of any other project work submitted for award of any
degree or diploma to the best of my knowledge and belief.

Signature of the Student

1)

Mariya Willson (Reg. No 140021044818)

2)

Remya Reghu (Reg. No 140021044829)

Date:

CERTIFICATE
Certify that the project report entitled STUDENT ATTENDENCE MANAGEMENT
SYSTEM done by Mariya Willson (Reg. No 140021044829) and Remya Reghu (Reg. No
140021044818) is completed under my guidance. . It has not formed the part of any other project
work submitted for award of any degree or diploma to the best of my knowledge and belief.

Name and Signature of the Guide

Name and Signature of the HOD :

Department Seal

External exam Date: Signature of external examiner

TABLE OF CONTENTS
Title
ACKNOWLEDGEMENT
ABSTRACT
1. INTRODUCTION
1.1 About the Organization
1.2 About the project
2. PROBLEM DEFENITION AND FEASIBILITY ANALYSIS
2.1 Introduction
2.2 Problem definition
2.3 Feasibility Analysis
2.3.1 Economic Feasibility
2.3.2 Operational Feasibility
2.3.3 Technical Feasibility
3. SOFTWARE REQUIREMENT SPECIFICATION
3.1 Introduction
3.1.1 Purpose
3.1.2 Scope
3.2 General Description
3.2.1 User Characteristics
3.3 Special Requirements
3.3.1 Behavioral Requirements
3.3.2 Software Requirements
3.3.3Performance Requirements
3.3.4 Design Constraints
4. SYSTEM DESIGN- PRELIMINARY
4.1 Introduction
4.2 Basic Design Approach
4.3 User Interface Design
4.4 Database Design
4.5 Data Flow Diagram
5. SYSTEM DESIGN- DETAILED
5.1 Introduction
5.2 Modules-Purpose and Description
5.3 Exception Handling
5.4 Security

Page No

6. TESTING AND IMPLEMENTATON

6.1 Testing
6.1.1 Unit Testing
6.1.2 Integration testing
6.1.3 Validation Testing
6.2 Implementation
7. CONCLUSION AND FORESEEABLE ENHANCEMENTS
7.1 Conclusion
7.2 Foreseeable Enhancements
BIBLIOGRAPHY
APPENDIX A

SAMPLE SCREENS

ACKNOWLEDGEMENT
Gratitude is a feeling which is more eloquent than words, more silent than silence. In
undertaking this project work we need the direction, assistance and co-operation of various
individuals and organizations, which is received in abundance with the grace of God, without
their unconstrained, the project could not have been completed.
We express our sincere gratitude to our manager Rev. Fr. Ruban. J. Thannickal and Principal
Dr. Fr. Roy Abraham Pazhayaparambil for permitting to do the project. Next we express our
heartiest thanks to Dr. Rajimol A, HOD of Department of Computer Applications, Marian
College Kuttikkanam for her valuable suggestions and guidance throughout the project.
Next we express our heartiest thanks and gratitude to our internal guide Mrs. Lumy Joseph,
Lecturer in the Department of Computer Applications, Marian College Kuttikkanam, for her
guidance and her keen interest shown in helping us to complete the project.
With great enthusiasm, we express our thanks to all the teachers in the Department of Computer
Applications for the support given throughout the project. Here also we would like to thank nonteaching staff for their support. We express our thanks to all our friends who supported and help
us in many ways. Special thanks to all who left no stone unturned in the completion of this
project.
Without the support of our family it is not possible for us to do anything. So we express our
sincere gratitude to our family for their support, encouragements and prayers for the completion
of our project successfully.

MARIYA WILLSON
REMYA REGHU

(Department seal)

ABSTRACT
In the existing attendance record management system, every college department follows manual
Procedure in which faculty enters information in a record book. At the end of each month/session
faculty calculate leaves of every student, which is a time taking process and there are chances of
losing data or error in the records. Attendance Management System will help for daily student
attendance entry in college. It deals with the maintenance of the student attendance details. It
generate the attendance of the student on the basis of presence in the class. It is maintenance on
the daily basis of their attendance. The staffs will be provided with the separate username and
password to make the student status.
The staffs handling the particular subject responsible to make the attendance for all student
only if the student present on that particular period. The student attendance report is based on
weekly and consolidate will be generated. This system will also help in evaluating attendance
eligibility criteria of a student. The purpose of developing this software is to generate the desired
report automatically at the end of the session.

INTRODUCTION

1. INTRODUCTION
1.1 ABOUT THE ORGANIZATION

In Marian college kuttikanam there the BCA department have three batches, 1st year, 2nd
year, 3rd year. There around above 180 student studying in BCA department. The teacher should
have attendance register in each semester. The teachers are remark the roll number on the
attendance register. They can be difficult to access which student was absent and difficult to
calculate attendance percentage.
Objective:

To take daily attendance.

To calculate percentage of attendance

To calculate percentage monthly and semester wise.

1.2 ABOUT THE PROJECT

This Project aims to reduce the paper work and saving time to generate accurate results from
the students attendance. The system provides with the best user interface. The efficient reports
can be generated by using this system. The project Attendance Management System will help
for daily student attendance entry in college. It deals with the maintenance of the student
attendance details. It generate the attendance of the student on the basis of presence in the class.
It is maintenance on the daily basis of their attendance.

Visual Basics 6.0 is used as the development tool and Microsoft SQL server Management Studio
as data base.

Existing System
The Existing system is a manual entry for the students. Here the attendance will be carried out in
the hand written registers. It will be a tedious job to maintain the record for the user. The human
effort is more here. The retrieval of the information is not as easy as the records are maintained
in the hand written registers. This application requires correct feed on input into the respective
field. Suppose the wrong inputs are entered, the application resist to work. So the user Find it
difficult to use.

Proposed System
To overcome the drawbacks of the existing system, the proposed system has been evolved. This
Project aims to reduce the paper work and saving time to generate accurate results from the
students attendance. The system provides with the best user interface. The efficient reports can
be generated by using this proposed system.
Advantages of Proposed System:

It is trouble-free to use.
It is a relatively fast approach to enter attendance
Is highly reliable, approximate result from user
Best user Interface
Efficient reports

PROBLEM DEFINITION
AND FEASIBILITY ANALYSIS

2. PROBLEM DEFINITION AND FEASIBILITY ANALYSIS

2.1 INRODUCTION
System study means gathering information from the existing system. The one who does it must
know that what information is to be gathered, where to find it, how to collect it and how to make
use of it. Proper use of tools in gathering information is the key to successful analysis.
2.2 PROBLEM DEFINITION
3366

2.3 FEASIBILITY ANALYSIS

Feasibility analysis begins once the goals are defined. It starts by generating broad possible
solutions, which are possible to give an indication of what the new system should look like. This
is where creativity and imagination are used. Analysts must think up new ways of doing thingsgenerate new ideas. There is no need to go into the detailed system operation yet. The solution
should provide enough information to make reasonable estimates about project cost and give
users an indication of how the new system will fit into the organization. It is important not to
exert considerable effort at this stage only to find out that the project is not worthwhile or that
there is a need significantly change the original goal. Feasibility of a new system means
ensuring that the new system, which we are going to implement, is efficient and affordable.
There are various types of feasibility to be determined. They are,

2.3.1 Economic Feasibility

Development of this application is highly economically feasible. The only thing to be done is
making an environment with an effective supervision. It is cost effective in the sense that has
eliminated the paper work completely. The system is also time effective because the calculations
are automated which are made at the end of the month or as per the user requirement
.2.3.3 Operational Feasibility
The system working is quite easy to use and learn due to its simple but attractive interface.
User requires no special training for operating the system. Technical performance include issues
such as determining whether the system can provide the right information for the Department
personnel student details, and whether the system can be organized so that it always delivers this
information at the right place and on time using intranet services. Acceptance revolves around
the current system and its personnel.
2.3.2 Technical Feasibility
The technical requirement for the system is economic and it does not use any other additional
Hardware and software. Technical evaluation must also assess whether the existing systems can
be upgraded to use the new technology and whether the organization has the expertise to use it.
Install all upgrades framework into the .Net package supported widows based application. This
application depends on Microsoft office and intranet service, database. Enter their attendance and
generate report to excel sheet.

SOFTWARE
REQUIREMENT
SPECIFICATION

3. SOFTWARE REQUIREMENT SPECIFICATION

3.1 INTRODUCTION
Attendance Management System software should be compactable with the candidate
system. Only then the software can be run smoothly. Proper analysis is conducted to select the
platform on which the software is to Developed. Attendance Management System software is
designed such that it is compactable with ordinary system.
3.1.1 Purpose:
The purpose of developing Attendance Management System is to computerized the
tradition way of taking attendance. Another purpose for developing this software is to generate
the report automatically at the end of the session or in the between of the session.
3.1.2 Scope:
The scope of the project is the system on which the software is installed, that is, the
project is developed as a desktop application. But later on the project can be modified to operate
it online.

3.2 GENERAL DESCRIPTION

Since ATTENDANCE MANAGEMENT SYSTEM software is newly designed system
it must be simple to use. The user must understand what the key features are. The new system
must match with the user expectation.
3.2.1. USER CHARACTERISTICS
The user characteristics of proposed College Handler software are:

Time Saving: Since this software manage the attendance management. So

effectively a lot of time can be saved for payment calculation and filtering of
information.
Cost Efficient: The software can run on systems with basic configuration. Also it
can fully restrict the pen and paper usage.
Ease of work: The herculean task of organizing a placement drive can be
reduced
Easy Data Access: Since the information is stored in an organized pattern, data
can be easily retrieved.
Future Reference: The well-formatted reports are useful for future references.
Efficient: The Attendance Management System software is very much
effective than the existing manual system.

3.2 SPECIAL REQUIREMENTS

The different necessities for development of the proposed software are behavioral
requirements, software requirements, hardware requirements, and performance
requirements.
3.3.1 Behavioral Requirements
It indicates the natural in which we are working with the project. It incorporates the Visual
Basics 6.0 in which we are making the front end and SQL in which we are making the back end
for the project.
3.3.2 Software Requirements
Operating System : Windows 10
Front End

: Microsoft visual basics 6.0

Back End

: MS-SQL Server

Visual Basics
Visual Basics is a third-generation event-driven programming language and integrated
development environment (IDE) from Microsoft for its COM programming model first released
in 1991. Microsoft intended visual basics to be relatively easy to learn and use. Visual basic was
derived from BASIC and enables the rapid applications development (RAD) of graphical user
interface (GUI) applications, access to database using Data Access Object, Remote Data Object,
or ActiveX Data Object, and creation of ActiveX controls and objects.
A programmer can create an application using the components provided by the Visual Basic
program itself. Over time the community of programmers have developed new third party
components, keeping this programming language to modern standards. Programs written in
Visual Basic can use the windows API, which requires external function declarations,
Furthermore, new third party functions (which are open sources) using part VB6 source code
and part embedded machine code, make the Visual Basic 6.0 applications faster than those
designed in c ++.

ActiveX Data Object (ADO)

The data access engineering is a quick, abnormal state interface into the OLEDB application
programming interface. ADOs advantages incorporate cutting edge, data-access determination
with the instance of an interface like the Data Access Object (DAO) syntax. ADO is not
difficult to utilize, dialect autonomous, have negligible system movement furthermore have few
layers between the customer application and data source. ADO connection utilizes either ODBC
or OLE DB connection is made by making a supplier utilizing Microsoft jet and after that
proclaiming a connection by utilizing this supplier. Once the connection is open then we utilize
record sets to get to the tables in this connection. Through the Visual Basic front interface we
can get to the database and store or recover data utilizing the tables as a part of the database.
Crystal Report
Crystal Report is a business intelligence application, currently marketed to small businesses
by SAP SE. It is used to design and generate report from a wide range of data source. Crystal
report is a power full program for creating custom report, lists and labels from the data in the
application database. When crystal report connect to the database, it reads values from the fields
selected and place them into a report, as part of a formula that generates more complex values.
Crystal Report are created to enable both technical and non-technical users to create customize
report quickly and easily from a verity of database. There are two unique methods used to
connect database. Data File and SQL ODBC.
SQL
Structured Query Language is a special-purpose programming language designed for
managing data held in a relational database management system (RDBMS), or for stream
processing in a relational data stream management system (RDSMS).
Originally based upon relational algebra and tuple relational calculus, SQL consist of a data
definition language and a data manipulation language. The scope of SQL includes data insert,
query, update and delete, schema creation and modification, and data access control. Although
SQL is often described as, and to a great extend is, a declarative language (4GL), it also include
procedural elements.
SQL was one of the first commercial language for Edgar F. Codds relational model, as
described in this influential 1970 paper, A Relational Model of Data for Large Share Data
Banks. Despite not entirely adhering to the relational model as described by Codd, it became
the most widely used database language.

3.3.3 PERFORMANCE REQUIREMENTS

Evaluating a system includes the hardware and software as a unit. It requires an analysis of
several performance categories

System availability

Compatibility

Cost

Usability

Performance

The programming language and its suitability to the users

Ease of installation and training

3.3.5 DESIGN CONSTRAINTS

System design is an approach to the creation of a new system. It provides the understanding
and procedural details necessary for implementing the system recommended in the feasibility
study. Emphasis is on translating the performance requirements in to design specification. Design
goes through logical and physical stages of developments.
The interface of the software is the major design constraint. The logical part of the software is
easy but validating is the software is a tough task.

SYSTEM DESIGN
PRELIMINARY

4. SYSTEM DESIGN PRELIMINARY

4.1 INTRODUCTION
The design phase focuses on the detailed implementation of the system recommended in the
feasibility study. Emphasis is on translating performance specification into design specification.
The design phase is a transition from a user- oriented document to a document oriented to the
programmers or data base administrator.
In the design phase of Attendance Management System, the solution to the identified
problems in the feasibility analysis are extracted. A new system with all necessary modules
required to manage the entire marketing and payment activity is required. It also involves the
creative design of the database.
4.2 BASIC DESIGN APPROACH
System design goes through two phases of development: logical and physical design. When
analysis prepares the logical system design, they specify the user needs at the level of details that
virtually determines the information flow into an out of the system and the required data
resources.
The design covers the following:
1. Reviews the current physical system.
2. Prepare output specification.
3. Prepares input specification
4. Prepares edit, security, and control specification.
5. Specifies the implementation plan.
6. Prepares a logical design walkthrough of the information flow, output, input, controls,
and implementation plan.
7. Reviews benefits, costs, target dates, and system constraints.

12.
Following the logical design is the physical design. This produces the working system by
defining the design specification that tells programmers exactly what the candidate system must
do.
Physical system design consists of the following steps:
1. Design the physical system
2. Plan system implementation.
3. Devise a test and implementation plan and specify any hardware/software
4. Update benefits, costs, conversion date, and system constraints.
4.3 USER INTERFACE DESIGN
The basic component of the user interface of a visual basic application is a form. A form is a
window that contains several different objects. Depending on how the form has been constructed
can be used for data entry, data display or a combination of both.
All objects in the form are controls, the labels, textboxes, command the designer can place
buttons and other controls on the form. We are free to design a form and to include any controls
that are required by the applications users. We have several different forms in the user interface,
each of which performs some task required by the application such as data entry, data display etc.
Building a form requires nothing more than adding a new form to the project and then dragging
controls on them on the forms design surface. We can set several properties for each of the
controls as well as for from itself and the code attached to the form and its controls specify how
the form actually works. Attendance Management System software has links spreading over
form to form.

4.4 DATABASE DESIGN

File design refers to how the logical data structures are to be physically stored in the storage
device. The design of files includes decision making on the nature and content of the files such
as it is to be used for storing master details, transaction details, or reference information. The
other type of files include input files, transfer files, output files etc. various factors are considered
during the file design phase of the system analysis. Some of them are purpose of the file
availability of the hardware method of access file, activity file, size, output requirements, input
requirements, file organization.
File design also deals with the design of physical data base. A key field determines how the
access is to be implemented. Suitable key fields are identified for various files and are coded
appropriately. The type, width and size of the fields are identified. Techniques of file
organization are studied so that the most appropriate storage device can be selected and an
efficient data base design can be achieved. The interface between the system data bases are
identified by specifying the data flow between them.

4.4.1. ADMINLOGIN TABLE

Primary Key: username
Field
Username
Password

Datatype
Var char
Var char

Size
25
25

Description
Username
Password

Size
25
25

Description
Username
Password

Size
20
30
10
10

Description
Student id
Student Name
Course Name
Semester
Date of Birth
Address of the student
Phone Number
Email-id
Status

4.4.2. USERLOGIN TABLE

Primary key: username
Field
Username
Password

Datatype
Var char
Var char

4.4.3. STUDENT TABLE

Primary Key: id
Field
Id
Name
Course
Semester
Dob
Address
Phone
Eid
Status

Datatype
Var char
Var char
Var char
Var char
Date
Var char
Numeric
Var char
Var char

30
10
30
20

4.4.4. TEACHER TABLE

Primary Key: tid
Field
Course
Batch
Sem
Tid
Tname
subname
Password

Datatype
Var char
Numeric
Var char
Var char
Var char
Var char
Var char

Size
15
10
10
30
30
25
20

Description
Course
Batch
Semester
Teacher id
Teacher Name
Subject Name
Password

4.4.5. ATTENDANCE TABLE

Primary Key: id
Field
Class
Atsem
Date
Hour
Subject
id
Name
Present

Datatype
Var char
Var char
Date
Numeric
Var char
Var char
Var char
Var char

Size
10
5
2
20
20
20
5

Description
Class
Semester
Date
Hour
Subject
Attendance id
Name
Present

Normalization
BCNF was developed by Boyce and Codd. It was designed to overcome the drawback of Third
Normal Form. Numerous normal forms have been designed, First, Second and Third Normal
Forms. Some First Normal Form relations are also in Second Normal Form, and some Second
Normal Form relations are also in Third Normal Form.
Codds original definition of Third Normal Form suffered from certain problems.
A stronger definition due to Boyce and Codd was developed to overcome these problems and
was called the BCNF. Subsequently Fagin defined a new Fourth Normal Form and more recently
another Normal Form which is called Fifth Normal Form or Projection joint Normal Form.
With the use of different normal forms in the database design, the problem of storing redundant
data in different tables is avoided. The use of normal forms permits storage of data only once in
the database, thereby saving space and avoiding the problem of redundant data storage.

4.5 DATA FLOW DIAGRAM

A data flow diagram (DFD), also known as a bubble chart, has the purpose of clarifying
system requirements and identifying major transformations that will become programs in system
design.

So it is the starting point of the design phase that functionally decomposes the

requirements specification down to the lowest level of detail. A DFD consists of a series of
bubbles joined by lines. The bubbles represent data transformations and the lines represent data
flows in the system.
There are certain rules which are to be followed while constructing a DFD. Such as:

The different processes should be named and numbered. The name of a process should be
representative of the process.

Direction of flow of data should be from top to bottom and from left to right. Usually
data flow from source to destination.

When a process is to be exploded into lower details, the sub processes are numbered.

The name of the source, destination and data stores should be in capital letters, and, the
starting letter of the process names and the names of the data flow should be in capital.

DFD Symbols:
1. A square defines a source (origin) or destination of system data
2. An arrow identifies data flow data in motion. It is a pipeline through which information
flows.
3. A circle or a bubble represents a process that transforms incoming data flow into outgoing
data flow.
4. An open rectangle is a data store

Symbols

Meaning

1.

Source or destination of data

Data Flow

2.

3.

Or

4.

Or

Process that transforms data

Data store

SYSTEM DESIGNDETAILED

5. SYSTEM DESIGN-DETAILED
5.1 INTRODUCTION
System design can be defined as the process of developing specifications for a candidate system
that meets the criteria established in system analysis. A major step in system design is the
preparation of input and the design of output reports in a form acceptable to the user. Input
design is the process of converting user originated inputs to a computer- based format.
5.2 MODULE-PURPOSE AND DESCRIPTION
There are several modules included which are designed to manage the process. The main
modules of the system is as below,
1. Taking Attendance
Attendance can take in systematic way. Attendance can be marked in this software easily
it can be managed and accessed in systematic way.
2. Attendance report
By the user name and password teachers can access the software. They can get the report
according to their need.
5.3 EXCEPTION HANDLING
Almost all error handling routines in Visual Basic programs follow three steps
1. Trap the error and redirect program flow to the error handler
2. Handle the error
3. Direct the program flow out of the error handler back to the main body.
The VBA engine is constantly looking for problems and immediately notifies it and handles it
when something unexpected happens. Visual basic normally handles most errors. After an error
occurs, the VBA engines normal operation is suspended. Normal execution is directed to the
error handler and further error trapping within the error handler is inactive. After the error has
been managed by the code, the program flow is redirected to another location within the
procedure.

5.4 SECURITY
All the information are to be maintained securely. Data should be lost under any circumstance.
All the data in Attendance Management System are securely stored. Since Attendance
Management System is designed to be used on a single computer by a single user, unauthorized
access can be prevented by preventing unauthorized access to the computer. No data is corrupted.
Data is stored as tables of values. For this SQL is used, which is a highly reliable platform to
ensure data security.

TESTING AND
IMPLEMENTATION

6. TESTING AND IMPLEMENTATION

6.1 TESTING
No program or system design is perfect; communication between the user and the designer is
not always complete or clear, and time is usually short. Inadequate testing or non-testing leads to
errors that may not appear, until months later. Thus testing is vital to the success of the system.
System testing makes the logical assumption that if all the parts of the system are correct then the
goal will be successfully achieved.
6.1.1 UNIT TESTING
Unit testing is testing changes made in an existing or a new program. Thus unit testing is done
to see whether the system will produce the correct outputs. No other test can be more crucial.
Attendance Management System has undergone through unit testing which is very crucial
effectively. Each module has successfully undergone the testing process.
6.1.2 INTEGRATION TESTING
Integration testing is the phase of software testing in which individual software models are
combined and tested as a group. The purpose of integration testing is to detect any
inconsistencies between the software units that are integrated together or between any of the
assemblages and the hardware. All the modules of Attendance Management System are
combined and tested. The software run effectively. It follows unit testing and precedes system
testing.
6.1.3 VALIDATION TESTING
System validation checks the quality of the software in both simulated and live environments.
First the software goes through a phase known as alpha testing in which errors and failures based
on simulated user requirements are verified and studied .The modified software is then subjected
to phase two called beta testing in the actual user site or environmental. The system is used
regularly with live transaction.
24.

6.2 IMPLEMENTATION
An important aspect of a system analysts job is to make sure that the new designers
implemented to established standards. The term implementation has different meanings, ranging
from the conversion of a basic application to a complete replacement of a computer system.
There are three types of implementation.
1. Implementation of a computer system to replace a manual system.
2. Implementation of a new computer system to replace an existing one.
3. Implementation of a modified application to replace an existing one, using the same
computer.

CONCLUSION AND
ENHANCEMENT

7. CONCLUSION AND ENHANCEMENT

7.1 CONCLUSION
It can be concluded that Attendance Management System is very much effective
software to manage the college activities. It reduces the use of paper works to zero
as everything related to attendance. By the use of Attendance Management
System software. The system has reached a steady state where all bugs have been
eliminated. The system is operated at a high level of efficiency and all the teachers
and users associated with the system understands its advantage. The system solves
the problem. It was intended to solve as requirement specification.
7.2 ENHANCEMENT
The system is designed in such a way that addition of new modules can be
done

much difficulty. Introducing distributed database can make further extensions to this

system .The reconstruction of the system will increase the flexibility of the system. The system
has been developed as a versatile and user-friendly as possible keeping in mind the advanced
features in this technology. Using Visual Basic 6.0 an MS-Access, the system was developed and
tested with all possible samples of data. As a whole, the system was well Planed and designed.
The performance of the system is proved to be efficient. All the customers, office people and
students receive the benefit through the system .The system provides flexibility for incorporating
new features, which may be necessary in future.

BIBLIOGRAPH
1. Elements of system Analysis and design, Marvin Gore, 4th Edition, Tata McGraw Hill
Publication, 1993
2. System Analysis and Design, Elias M Award
3. Guide to Visual Basic 6.0, Peter Norton
4. Ramesh Elmasri, Shamkant B. Navath Data Base Management System Pears
Publications, Sixth edition, 2014
5. www.systemdesign.com