Project Planning

3.1 Project Definition

E-Music Library refers to systems that will enable
the client to
mobilize its business through buying the different music related items in
the website. Once the User pay using payment option they buying it online
at their shipping address with greater privacy.

Project Title

E-Music Library System)

Front End Tool

Advanced Java(Jsp and Servlet)

Back End Tool

MYSQL Community Server

Modules of EMLS
Following are the modules of E-Music Library system:
1. Registration
2. login
3. Music Administration
4. Feedback
5. Queries
6. List of Movie Songs
7. Add to cart
8. Purchase Music CD
9. Billing Generation
10. payment

Modules Handled
Billing

3.2 Preliminary Investigation

3.2.1

Feasibility Study

System feasibility analysis is conducted with the following objective in mind:

SLDCCA

Project Planning

Identify the users need

Evaluate the system concept for feasibility
Perform economic and technical analysis
Allocate functions to H/W, S/W, people, database and other System
analysis
Establish cost and schedule constraints
Create system definition that forms the foundation for all subsequent
software work.
Three specific tests were carried out on the system to test its feasibility
namely, Operational, Technical and Economical.

3.2.1.1

Technical Feasibility

3.2.1.1.1

Team Qualification

The team working on the project is qualified enough to carry out the task.
All the members are familiar with the technologies to be used for the
development of the software. The team consists of 1 member. And Before
beginning of the project I went through the rigorous training of the 15 days
to make familiarize with the organization technologies and standards from
the expert.
3.2.1.1.2

Availability of Technical Resources

This system is technically feasible because all required technologies

are available today in market. System to be developed requires 3-tire
client/server technologies. The technologies we using in this system
are listed below:
MVC Framework
Jsp and Servlet
Google chrome

3.2.1.2

SLDCCA

Operational Feasibility

Project Planning

Any project proposed can be beneficial only if it satisfies the organizations

requirements. This system is operationally feasible if all Users are satisfied
with system. The following points have been proved to declare the
proposed system as operationally feasible.
The newer system will accommodate all the requirements of the
management.
The newer system will fit to its existing system and perform more
function then manual system.
The user of the system will get the information at the time when they
need it, and also speed up the transaction processing.
The system will work when it is developed and installed and there are
no major barriers to its implementation. This accounts for the
operational feasibility of the proposed system.

3.2.1.3

Economical Feasibility

As requirements of the application were not so high thats why we do not have
to worry about the Economical Feasibility. Everything was under control. The
application was economically feasible to the organization.
Thus at the end of Feasibility Study it is understood that the project is viable
and I start doing the Analysis for the same to identifying the Requirement.

3.3 Project Development Strategy

The Project Execution Methodology addresses all phases of the Software
Development Life Cycle (SDLC). Projects follow the Modified Waterfall Model
that facilitates parallel execution of phases. This means that as soon as inputs for
starting any phase activity are available, work on that phase can commence.

SLDCCA

Project Planning

To reduce the amount of rework involved when high-impact requirements arise

late in the SDLC, the following strategies are adopted:
Dividing large projects into smaller units (based on the application or
functional areas), so that each unit can be executed and implemented
separately.
Prototyping is done if required, to gather feedback on TCS deliverables for
look and feel, navigation, ascertain technical feasibility and functionality check
of the system.
Planning a deliverable for each unit.
Submitting the deliverables early in the project life cycle to ensure the
simultaneous incorporation of the users feedback.
Based on our understanding of requirements and proposed solution, the
following Project Approach and Methodology is proposed which will provide
the set of organized activities needed to successfully execute this
engagement.
Following are the phases proposed in the project.
Project Startup
Detailed Requirements Study and Analysis
Development and Unit Testing
System Testing
Acceptance Testing
Implementation
Warranty Support
Details of the activities carried out in each phase are mentioned below:

3.3.1

SLDCCA

Project Startup

Project Planning

The project would kick-off on award of contract with preparation of a detailed

project plan. The plan will be discussed and mutually agreed between the
Developer and the Client. The project plan will be continuously updated
throughout the execution of the project.

3.3.2
This

Requirement Study
phase

covers

activities

directed

towards

confirming

the

user

requirements. The user requirements are finalized based on detailed study of

the business needs along with the Client. The requirement analysis team
would also reconfirm assumptions made and revisit the technical environment
proposed. Two locations would be taken as referral points from where the
User Requirements would be obtained.

3.3.3

System Design

System Design phase starts with defining the design objectives and low level
process flows for the proposed system. The components constituting the
software system are identified, the system architecture is finalized and the
design of the database system to be adopted is finalized.

3.3.4

Development & Unit Testing

During this phase, the developed design representation will be transformed

into programs. Also unit test cases will be developed on the basis of which the
screens and reports developed will be tested. Also a code walk through will be
done.

3.3.5

System Testing

The purpose of this phase is to demonstrate that the software developed

satisfies all software requirements in the requirement document. This phase
includes system integration and testing for system level functionality, security,

SLDCCA

Project Planning

performance, external interfaces, usability and integration of the different

modules. System testing is to be performed as per the System Testing Plan.

3.3.6

Acceptance Testing

Here in the Developer would provide support during this phase to help the
Client carry out acceptance testing.

3.3.7

Implementation

On successful completion of the Acceptance Testing, the system will be

implemented in production. The application will be implemented at the client
side so that the users can use the system.

3.3.8

Training

Here in this phase the Developer will provide training to the users as per the
training rules at the Developers end. This training will be provided at the
Clients location.

SLDCCA

Project Planning

Requirem
ent
System Design
Analysis
Prototype
Development
Development

Testing

Implementation

Maintenance

Warranty

Figure : Shows a pictorial representation of the Project Phases. Also shows the
phases completed and the phase currently going on.

Strengths of waterfall model:

More flexibility than the pure waterfall model.
If there is personnel continuity between the phases, documentation can be
substantially reduced.
Implementation of easy areas does not need to wait for the hard ones.

SLDCCA

Project Planning

Weaknesses of waterfall model :

Milestones are more ambiguous than for the pure waterfall.
Activities performed in parallel are subject to miscommunication and
mistaken assumptions.
Unforeseen interdependencies can create problems.

SLDCCA