1.

Organization Profile

Accenture
Accenture is a global management consulting, technology services and
outsourcing company. Its "high performance business" strategy builds on its expertise
in consulting, technology and outsourcing to help clients perform at the highest levels
so they can create sustainable value for their customers and shareholders. Using our
industry knowledge, service-offering expertise and technology capabilities, we identify
new business and technology trends and develop solutions to help clients around the
world:
Enter new markets.
Increase revenues in existing markets.
Improve operational performance.
Deliver their products and services more effectively and efficiently.
Among the much strength that distinguishes Accenture in the marketplace are:
Extensive industry expertise.
Broad and evolving service offerings.
Expertise in business transformation outsourcing.
History of technology innovation and implementation, including our research
and development capabilities.
Commitment to the long-term development of our employees.
Proven and experienced management team.
Our Core Values have shaped the culture and defined the character of our
company, guiding how we behave and make decisions:
Stewardship: Building a heritage for future generations, acting with an owner
mentality, developing people everywhere we are, and meeting our
commitments to all internal and external stakeholders.
Best People: Attracting and developing the best talent for our business,
stretching our people and developing a "can do" attitude.
Client Value Creation: Improving our clients' business performance, creating
long-term, win-win relationships and focusing on execution excellence.
One Global Network: Mobilizing the power of teaming to deliver consistently
exceptional service to our clients anywhere in the world.
Respect for the Individual: Valuing diversity, ensuring an interesting and
inclusive environment, and treating people as we would like to be treated
ourselves.
Integrity: Inspiring trust by taking responsibility, acting ethically, and
encouraging honest and open debate.
Purpose Of The Project:

Stores are required for the following purposes :-

1. Capital works
2. Operation and Maintenances Works
3. Other Commercial activities like hiring equipment etc..,

The Stores Management System is targeted to automate the almost all of
the processes mentioned above to reduce the clerical labor of the staff
working in Stores both technical and as well as Accounts departments
using the software Industrys latest technologies and cost effective tools
there by providing the better control to the management by avoiding
manual errors etc..,

In this project modules under study are Material Issues module, Reports
module.

Material Issues module deals with the Issues functionality of the application. It
mainly contains two operations namely Material issues i.e. Issues issued to works
based on field requisitions and Inter stores issues i.e. material issues to other stores
based on inter store requisitions. For these two operations, we have to issue the
gate passes for both types of operations.

Reports module deals with the Reports provided by the application. This
module contains various reports namely Monthly SRB Report, Monthly SIB
Report, Monthly Section Wise Issues Reports, Priced Ledger, Monthly
Stores Abstract, Monthly Work Order wise Details and Monthly Stock
Report.


















Scope Of The Project:
The proposed system is Stores Management System . This system

is GUI based system and is user friendly. Stores Management System is
accessible through the internet. Stores are required for the following
purposes.

1. Capital works
2. Operation and Maintenances Works
3. Other Commercial activities like hiring equipment etc..,

The Stores Management System package is targeted to automate the
almost all of the processes mentioned above to reduce the clerical
labour of the staff working in Stores both technical and as well as
Accounts departments using the software industrys latest technologies
and cost effective tools there by providing the better control to the
management by avoiding manual errors etc..,

This application discusses the initial screens like login, logout and main
menu of the application. The application can be accessed by typing the
URL in the address bar of the web browser like Internet Explorer. The
URL is of the format http://localhost:8080/contextname on which it will
invoke login screen.





The stores operations as per the stores manual have been described as
two different processors owing to the complexity and tediousness of the
operations by effective division of labour as physical receipts and issue
has been the responsibility of Accounts section.

To solve the problem using computer systems for which the complexity
and tediousness is not an issue, the pricing is calculated at the time of
receiving the materials itself and stock price will be fixed then and there
and fetching that price while issuing the material.

The software package is described in detailed below. The package
provides three basic functionalities

1. Material Receipts Module
2. Material Issues Module
3. Different Reports serving the Quantity ledgers, Priced ledgers and
material indexing and ledger folio indexing etc.

In this project Issues module and Reports module have been handled.

FEASIBILITY STUDY

The existing system is clearly understood the next step is to conduct the
feasibility study, which is a high level capsule version of the entire System
Analysis and Design process. The objective is to determine whether the
proposed system is feasible. The three tests of feasibility have been carried
out:
2.4.1. Technical Feasibility
2.4.2. Economical Feasibility
2.4.3. Operational Feasibility
2.4.1. Technical Feasibility
In technical feasibility study, one has to test whether the proposed system
can be developed using existing technology or not. It is planned to
implement the proposed system using Windows 2000 Professional, JSP
and Apache Tomcat Wed Server. The Organization already possesses
Windows 2000 Professional Operating System. It is evident that the
necessary hardware and software are available for the development and
implementation of the proposed system. Hence the solution is technically
feasible.

2.4.2. Economical Feasibility

As part of this, the costs and benefits associated with the proposed system
are to be compared and the project is economically feasible only if benefits
outweigh costs. The Organization has already its own satellite link, and a
host of SUN FIRE 6800 servers. So it need not invest newly for the internet
connection and also the organization initiated to use Open Source in
project development, hence there is 0 additional cost incurred for the tools
that will be used.

2.4.3. Operational Feasibility:

This test of feasibility checks if the system works with least difficulties when
it is developed and installed. The technical staff has sufficient knowledge of
the tools being used and the users need just to know how to access and
run the programs in the Apache Web Sever. Hence it is concluded that the
system is operationally feasible.





Requirements Analysis
Requirements Analysis Process : Requirements Elicitation, Analysis and Specification
Requirements Analysis is the process of understanding the customer needs and expectations from
a proposed system or application and is a well-defined stage in the Software Development Life
Cycle model.

Requirements are a description of how a system should behave or a description of system
properties or attributes. It can alternatively be a statement of what an application is expected to
do.

Given the multiple levels of interaction between users, business processes and devices in global
corporations today, there are simultaneous and complex requirements from a single application,
from various levels within an organization and outside it as well.

The Software Requirements Analysis Process covers the complex task of eliciting and
documenting the requirements of all these users, modeling and analyzing these requirements and
documenting them as a basis for system design.

Software Requirements Analysis and Documentation Processes are critical to software
project success. Requirements engineering is an emerging field which deals with the
systematic handling of requirements.
Why is Requirements Analysis necessary?
Studies reveal that inadequate attention to Software Requirements Analysis at the
beginning of a project is the most common cause for critically vulnerable projects that
often do not deliver even on the basic tasks for which they were designed. There are
instances of corporations that have spent huge amounts on software a project where the
end application eventually does not perform the tasks it was intended for.

Software companies are now investing time and resources into effective and streamlined
Software Requirements Analysis Processes as a prerequisite to successful projects that
align with the clients business goals and meet the projects requirement specifications.
5.1.1 Requirements Elicitation
Information is gathered from the multiple stakeholders identified. The Requirements
Analyst draws out from each of these groups what their requirements from the
application are and what they expect the application to accomplish. Considering the
multiple stakeholders involved, the list of requirements gathered in this manner could run
into pages. The level of detail of the requirements list is based on the number and size of
user groups, the degree of complexity of business processes and the size of the
application.
Problems faced in Requirements Elicitation
Ambiguous understanding of processes
Inconsistency within a single process by multiple users
Insufficient input from stakeholders
Conflicting stakeholder interests
Changes in requirements after project has begun
Tools used in Requirements Elicitation
Traditional methods of Requirements Elicitation included stakeholder interviews and focus
group studies. Other methods like flowcharting of business processes and the use of existing
documentation like user manuals, organizational charts, process models and systems or
process specifications, on-site analysis, interviews with end-users, market research and
competitor analysis were also used extensively in Requirements Elicitation.
However in order to handle the complex and multilayered process of Requirements Elicitation
the following tools were used:
Prototypes
Use cases
User interfaces


5.2 Software Requirement Specifications
What is SRS?
Software Requirement Specification (SRS) is the starting point of the
software developing activity. As system grew more complex, it became
evident that the goal of the entire system cannot be easily comprehended.
Hence the need for the requirement phase arose. The software project us
initiated by the client needs. The SRS is the means of translating the ideas
of the minds of clients (the input) into a formal document (the output of the
requirement phase.)

The SRS phase consists of two basic activities:

1) Problem/Requirement Analysis:
The process is order and more nebuious of the two, deals with
understand the problem, the goal and constraints.

2) Requirement Specification:
Here, the focus is on specifying what has been found giving
analysis such as representation, specification languages and
tools, and checking the specifications are addressed during this
activity.

The requirement phase terminates with the production of the validate SRS
document. Producing the SRS document is the basic goal of this phase.




Role of SRS

The purpose of the Software Requirement Specification is to reduce the
communication gap between the clients and the developers. Software
Requirement Specification is the medium through which the client and user
needs are accurately specified. It forms the basis of software development.
A good SRS should satisfy all the parties involved in the system.


Purpose

The purpose of this document is to describe all external requirements for
mobile task manager. It also describes the interfaces for the system.