Академический Документы
Профессиональный Документы
Культура Документы
CHAPTER 1
INTRODUCTION
1.1. PROJECT OVERVIEW
The project titled studio management system is an application to sort out the data
storage and time management in the studio. By sorting out the drawbacks caused in the
existing system we can improve the facilities in the proposed system that is studio
management system. This makes the functioning of the studio easy.
The studio workers for whom the functioning becomes easy are receptionists,
owner (admin), photographer, editor. The customer arriving can approach the receptionists
who collect the details about the customer and store it in the database. The owner controls
the appointment of the staff and stores the details about the staff presently working in the
studio. The photographer takes and uploads the photo. And the editor does editing.
1.2. OBJECTIVE
The project aims to develop a reusable and maintainable storage of data in the studio.
This project aims at:
Page 1
CHAPTER 2
SYSTEM ANALYSIS
2.1. EXISTING SYSTEM
In the existing system, accessibility of data becomes hilarious when data to be stored
exceeds the data storage limit. Users cannot handle such huge amount of data, which will
cause errors and certain other factors of time. It becomes completely difficult to manage and
its non maintainable. The availability and usability of data are not secured in this system.
2.1.1. Drawbacks
Some drawbacks for manual system
Time consumption
Error factor
Accessibility
Security factor
Possibility of upgrading
Easy of usage
Enhanced security
Page 2
Maintainability
Operational feasibility
Technical feasibility
Economic feasibility
Page 3
the system will work when it is developed and installed. Some of the important questions
that are useful to test the operational feasibility of a project can be given below:
Is there sufficient support for the project from the management? From users? If the
present system is well liked and used to extent that the persons will not able to see
reasons for a change, there may be resistance.
Are current business methods acceptable to the users? If they are not? Users may
welcome a change that will bring about a more operational and useful system.
Are the users been involved in the planning and development of the project? If
they are involved at the earlier stage of the project dev-eloped, the changes of
resistance can be possibly reduced.
Issues that appear to be quite minor at the earlier stage can grow into major
problems after implementation. Therefore, it is always advisable to consider
operational aspects carefully.
Page 4
Does the proposed equipment have the technical capacity to hold the data required
to use the new system?
Are there technical guarantees of accuracy, reliability, ease of access and security?
Page 5
CHAPTER 3
SYSTEM SPECIFICATION
Hardware and software requirements for the installation and smooth functioning of this
product could be configured based on the requirements needed by the component of the
operating environment that works as front-end system here we suggest minimum
configuration for the both hardware and software components.
Working off with this software is requirements concrete on system environments. It
includes three phases.
Hardware Requirements
Software Requirements
RAM : 1.00 GB
Page 6
CHAPTER 4
SOFTWARE DESCRIPTION
4.1. FRONT END: JAVA
Java is
a general-purpose computer programming language that
is concurrent, class-based, object-oriented, and specifically designed to have as few
implementation dependencies as possible. It is intended to let application developers "write
once run anywhere" (WORA), meaning that code that runs on one platform does not need to
be recompiled to run on another. Java applications are typically compiled to byte code that
can run on any java virtual machine (JVM) regardless of computer architecture. Java is, as
of 2014, one of the most popular programming languages in use, particularly for clientserver web applications, with a reported 9 million developers. Java was originally developed
by James Gosling at Sun Microsystems (which has since merged into Oracle Corporation)
and released in 1995 as a core component of Sun Microsystems' java platform. The language
derives much of its syntax from C and C++, but it has fewer low level facilities than either
of them.
The original and reference implementation Java compiler, virtual machines, and class
libraries were originally released by Sun under proprietary licenses. As of May 2007, in
compliance with the specifications of the java community process, Sun relicensed most of
its Java technologies under the GNU general public license. Others have also developed
alternative implementations of these Sun technologies, such as the GNU compiler for
java (byte code compiler), GNU class path (standard libraries), and iced-tea-Web (browser
plug in for applets).
4.1.1. Java platform
The main goal of Java is portability, which means that programs written for the Java
platform must run similarly on any combination of hardware and operating system with
adequate runtime support. This is achieved by compiling the Java language code to an
intermediate representation called java byte code, instead of directly to architecturespecific machine code. Java byte code instructions are analogous to machine code, but they
are intended to be executed by a virtual machine (VM) written specifically for the host
hardware. End users commonly use a java runtime environment (JRE) installed on their own
machine for standalone Java applications, or in a web browser for Java applets.
Standardized libraries provide a generic way to access host-specific features such as
graphics, threading and networking.
A major benefit of using byte code is porting. However, the overhead of interpretation
means that interpreted programs almost always run more slowly than programs compiled to
DEPT.OF INFORMATION TECHNOLOGY
Page 7
native executables would. Just-in-Time (JIT) compilers were introduced from an early stage
that compiles byte codes to machine code during runtime.
4.1.2. Implementation:
Oracle Corporation is the current owner of the official implementation of the Java SE
platform, following their acquisition of Sun Microsystems on January 27, 2010. This
implementation is based on the original implementation of Java by Sun. The Oracle
implementation is available for Microsoft Windows, Mac OS X, Linux and Solaris. Because
Java lacks any formal standardization recognized by Ecma International, ISO/IEC, ANSI, or
other third-party standards organization, the Oracle implementation is the de facto standard.
The Oracle implementation is packaged into two different distributions: The Java Runtime
Environment (JRE) which contains the parts of the Java SE platform required to run Java
programs and is intended for end users, and the java development kit (JDK), which is
intended for software developers and includes development tools such as the java
compiler, javadoc, jar, and a debugger.
Open JDK is another notable Java SE implementation that is licensed under the GNU GPL.
The implementation started when Sun began releasing the Java source code under the GPL.
As of Java SE 7, Open JDK is the official Java reference implementation.
The goal of Java is to make all implementations of Java compatible. Historically, Sun's
trademark license for usage of the Java brand insists that all implementations be
"compatible". This resulted in a legal dispute with Microsoft after Sun claimed that the
Microsoft implementation did not support RMI or JNI and had added platform-specific
features of their own. Sun sued in 1997 and in 2001 won a settlement of US$20 million, as
well as a court order enforcing the terms of the license from Sun. As a result, Microsoft no
longer ships windows with Java.
Platform-independent Java is essential to java EE, and an even more rigorous validation is
required to certify an implementation. This environment enables portable server-side
applications.
4.1.3. Performance
Programs written in Java have a reputation for being slower and requiring more
memory than those written in C++. However, Java programs' execution speed improved
significantly with the introduction of just-in-time-compilation in 1997/1998 for java 1.1, the
addition of language features supporting better code analysis (such as inner classes, the
String Builder class, optional assertions, etc.), and optimizations in the Java virtual machine,
such as Hotspot becoming the default for Sun's JVM in 2000.
Page 8
Some platforms offer direct hardware support for Java; there are microcontrollers that can
run Java in hardware instead of a software Java virtual machine, and ARM based processors
can have hardware support for executing Java byte code through their jazelle option.
There are many databases that support the use of SQL to access their data, among them
MySQL and PostgreSQL. In other words, MySQL is just the brand of one database
software, one of many. The same goes for PostgreSQL. These two databases are very
popular among programs that run on websites (probably because they are free), which is
why you often see one or both of them being advertised in the feature lists of web hosts, as
well as being listed as one of the "system requirements" for certain web software (like blogs
and content management systems).
Page 9
CHAPTER 5
PROJECT DESCRIPTION
1. Receptionists
Customer registration
Placing order
Billing
2. Photographer
3. Editor
4. Owner (admin)
Page 10
5.2.1. Modules
5.2.1.1. Receptionists
The receptionists collect the details of the customers and store it in the database so
that it becomes easy to access. The receptionists keep the record of the clients order which
makes the accessibility time consuming. The main functions of receptionists are:
Login
Booking
View booking
Edit booking
Searching
Login
View work
Edit status
Upload photo
Update gallery
5.2.1.4. Admin
The admin does the job of appointing the staff and managing the staff details.
The admin can add and view and even edit the staff details. The functions of the admin are
as follows:
Login
Add staff
View staff
Edit staff
Page 11
LEVEL 1
ADMIN
Page 12
RECEPTIONIST
PHOTOGRAPHER
Page 13
5.4.1. Login
5.4.2. Booking
5.4.3. Staff
5.4.4. Image
Page 14
CHAPTER 6
SYSTEM TESTING
Test Plan
The Software Test Plan describes plans for qualification testing of Computer
Software configuration Items and software systems. It describes the Software test
environment to be used for the testing, identifies the test to performed, and provides
schedules for test activities.
Testing strategy
The overall strategy for Software testing is described in the following section. We
will use four different methods to test our software.
6.1. UNIT TESTING
In unit testing, the analyst tests the programs making up a system. This is also called
program testing. The software units that make up the system are modules and the routines,
which are assembled and integrated to perform a specific function in a large system. Many
modules at different levels are needed. Unit testing, independent of one another, focuses on
modules to locate error. This enables the tester to detect error in coding and logic that are
contained within that module alone. Those resulting from the interaction between modules
are initially avoided. Unit Test comprises the test of performed prior to integration of the
unit into the entire project. Four categories of test are performed on each unit.
Functional Test
The code is exercised with nominal input values for which the expected results are
shown, as well as boundary values (Minimum values, Maximum values) and values on
and just outside the functional boundaries and special values such as logically related
inputs.
Page 15
Performance Test
Performance test is done to determine the amount of execution time spent in various
parts of the unit, program throughput, and response time and device utilization by the
program unit. Some time is taken initially to link to the SQL.
Stress Test
Stress Test has been done to intentionally break the unit. This helps in the learning
about the strength and limitations of the program by examining the manner in which a
program unit breaks.
Structure Test
Structure test are done to test the internal logic of a program and traversing particular
exercise, deriving test data to exercise those paths, determining the test coverage criteria to
be used.
6.2. ACCEPTANCE TESTING
After the developers complete the system testing successfully acceptance testing is
done at the customer end. It is the customer or the end user who knows designs the test
cases. in this type of testing emphasis is on the usability of the product. Acceptance testing
is supported through alpha and beta testing. Alpha testing is done when the software is made
operational for the first time to be tested by the users at developers site. Hence it is possible
that it will involve making lot of changes to program code. Beta testing follows alpha testing
but now the testing is done at the customers site that validate the product after using it for
few days. At this stage few changes as compared to alpha testing would make to the product.
6.3. TEST CASES
The evaluation of test cases is done through test case review. And for any review, a
formal document or work product is needed. This is the primary reason for having the test
case specification in the form of document. The test case specification document is
reviewed, using a formal review process, to make sure that the test cases are consistent with
the policy specified in the plan, satisfies the chosen criteria, and in general cover the various
aspect of the unit to be tested.
Page 16
For this process, the reason for selecting the test case and the expected output are also
given in the test case specification document. By looking at the conditions being tested by
the test cases, the reviewer can check if all the important conditions are being tested. As
conditions can also be based on the output, by considering the expected output of the test
cases it can also be determined the production of all the different types of output the unit is
supposed to produce are being tested.
Page 17
CHAPTER 7
SYSTEM IMPLEMENTATION
Implementation is the process of converting a new or revised system design into an
optional one. It is the key stage in achieving a successful new system because usually it
involves a lot of upheaval in the user department. It must therefore be carefully planned and
prepared. Once the software is fully developed and implemented, the department starts to
use the software. The department also grows and more divisions may be attached, or the
database of the department can grow in size. So after sometime the software, which has to be
installed need some modification? If the software need modification all the needed to
develop new software has to be executed. The need has to be studied, the design has to be
made and the coding has to be done. The new module has to be connected to the existing
software modules Even if the software working perfectly also we have to do routine testing
and new bug if found out, has to be fixed. No software ever developed will be bug free
forever.
Page 18
CHAPTER 8
APPENDIX
8.1 SCREEN SHOT
Add customer
Booking failed
Page 19
Edit booking
View booking
Search customer
Page 20
View staff
Edit staff
Page 21
View work
Upload
Page 22
Update
Gallery
Booking failed
Page 23
Wrong login
Page 24
CHAPTER 9
CONCLUSION AND FUTURE SCOPE
This application provides a user friendly approach towards the system. The system
has been well developed and is found to satisfy all of the requirements. There is a hope that
this software will be utilized to its maximum and will do a good job in long run. This phase
gives me a good idea on developing full-fledge software satisfy the user requirements. The
programming technique used in the design of the system provides scope for further
expansion and implementation of any changes which may occur in future. The design was
developed in a java platform with NETBEANS IDE 8.0 it is expected to leave up to the
objective for which it was designed.
The application of studio management system focuses to improve the data storage
and accessing capability of the data. The system can be made to meet the requirements of
the customer at the maximum extent. The uploading, editing and checking of incomplete and
completed order details are made easy to be accessible.
The widening may be such as uploading of videos and editing the gallery contents.
Page 25
REFERENCES
Elements of system analysis -Fourth Edition, By Marvin Gore & John W Stubbe
http://en.wikipedia.org/wiki/Microsoft_Access/24/09/2014.
Page 26