CHAPTER - 1

INTRODUCTION

1.1 INTRODUCTION TO PROJECT

About Software Project Management Tool
It is well known fact that software companies undertake huge projects,
more than at a time. Hence there is a profound need for the organizations to
manage all the projects effectively and also ensure that projects cycle goes on
smoothly and they are completed on time.
During the life time of a project, the organization has to commemorate all
the projects. This tool makes it easier for the organization to monitor the projects.
It maintains the records and tracks various parameters that influence software
project development to take decisions at various stages of the product
development.
This product will assist the organization in maintaining records of every
project it undertakes. All the information relevant to the projects like size, time,
effort, departments involved, etc is maintained by this tool. Throughout this
project dealt with the three modules-Masters, Transactions, Reports. Masters is a
place where we maintain the record of the entire project undertaken, the project
employee involved with the project. Transactions is a place where we carry out
required operations with respect to parameters like size estimate, effort estimate,
reports generated, for the operations we committed, in the reports module.

Problem Definition
Manual system uses huge amounts papers and stores. Difficulty in tracking and
retrieving data from the abundant papers is quite difficult.
Time consuming process.

Objective
1. Define and highlight importance of software project management.
2. Describe the software project management activities.
3. Gives details of project managers and other individuals involved in software

1
project.
Planning oversight in the implementation of the software project management
process.

1.2 PURPOSE OF THE PROJECT

• Manual work is reduced.
• Retrieval and access of information is easy.
• Transactions are processed quickly.
• Easy tracking and communication of exigencies in monetary transactions

2
 CHAPTER - 2
SYSTEM ANALYSIS

2.1 INTRODUCTION
After analyzing the requirements of the task to be performed, the next step
is to analyze the problem and understand its context. The first activity in the
phase is studying the existing system and other is to understand the requirements
and domain of the new system. Both the activities are equally important, but the
first activity serves as a basis of giving the functional specifications and then
successful design of the proposed system. Understanding the properties and
requirements of a new system is more difficult and requires creative thinking and
understanding of existing running system is also difficult, improper
understanding of present system can lead diversion from solution.

2.2 ANALYSIS MODEL

The model that is basically being followed is the WATER FALL
MODEL, which states that the phases are organized in a linear order. First of all
the feasibility study is done. Once that part is over the requirement analysis and
project planning begins. If system exists one modification and addition of new
module is needed, analysis of present system can be used as basic model. The
design starts after the requirement analysis is complete and the coding begins
after the design is complete. Once the programming is completed, the testing is
done. In this model the sequence of activities performed in a software
development project are: -
1 Requirement Analysis
2 Project Planning
3 System design
4 Detail design
5 Coding

3
 6 Unit testing
7 System integration & testing
Here the linear ordering of these activities is critical at the end of the
phase and the output of one phase is the input of other phase. The output of
each phase is to be consistent with the overall requirement of the system.
Some of the qualities of spiral model are also incorporated like after the
people concerned with the project review completion of each of the phase the
work done.
WATER FALL MODEL was being chosen because all requirements were
known beforehand and the objective of our software development is the
computerization/automation of an already existing manual working system’s
system.

Changed
Requirements
Communicated
Requirements

Requirements
Specification
Requirements
Engineering

Design
Specification
Design

Maintenance
Executable
Programming Software Modules

Process
Integrated
Software Product
Integration

Product
Product
Input Output Delivered
Software Product
Delivery

Fig 2.1: Water Fall Model

2.3 STUDY OF THE SYSTEM

GUI’S
In the flexibility of the users the interface has been developed a graphics

4
concept in mind, associated through a browses interface. The GUI’S at the top
level have been categorized as

1. Administrative user interface

2. The operational or generic user interface

The administrative user interface concentrates on the consistent information that
is practically, part of the organizational activities and which needs proper
authentication for the data collection. The interfaces help the administrations with
all the transactional states like Data insertion, Data deletion and Date updating
along with the extensive data search capabilities.
The operational or generic user interface helps the users upon the system in
transactions through the existing data and required services. The operational user
interface also helps the ordinary users in managing their own information in a
customized manner as per the assisted flexibilities.

2.4 EXISTING SYSTEM AND DISADVANTAGES

In a competitive business climate organizations ability to efficiently align
resources and business activities with strategic objectives can mean the difference
between succeeding and just surviving. To achieve strategic alignment,
organizations are increasingly managing their activities and processes as projects-
in essence, projecting their business –to monitor performance more closely and
make better business decision above their overall work portfolio. By planning and
tracking projects with clarity and precession, organizations can respond with
greater ability to the demands of fast changing business environment. Making
strategic goals or reality requires technology that is robust enough to support your
core business and yet flexible enough to accommodate your existing processes.
The Microsoft office Enterprise Project Management (EPM) is one of the existing
tools that are helpful for software project management.
The primary purpose of any tool is to improve productivity, reduce cycle’s times,
decrease costs and increase Quality.

2.5 PROPOSED SYSTEM

5
 For any software project the primary parameters that should be taken into
account are time, size, and effort. The existing tools do not consider all the
factors that affect a project directly. The entire process is built upon just one or
two parameters which do not gives us complete and desired results. So we need a
system where we can deliver the correct results that would ultimately lead to a
position where the overall cost and time will be consolidated. Hence the
organization which implements such a process can produce better results.
Project management is the application of knowledge, skills, tools, and
technologies to project activities to meet project requirements.

2.6 INPUT AND OUTPUT

The main inputs, outputs and major functions of the system are as follows
Inputs:
• Sellers can register themselves by providing all their details like
address and the site photograph.
• Buyers can register themselves by providing all necessary details.
Outputs:
• Seller can receive their user Id and site Id.
• Buyer can view all details about sites like apartments, buildings etc

6
 CHAPTER - 3
REQUIREMENT ANALYSIS

3.1 SOFTWARE REQUIREMENTS

Operating System : Windows
Programming Language : Java
Front End Tool : Java Server Pages
Web Applications : Jdbc, Servlets
User Interface : HTML
Client side Script : Java script
Back End Tool : Oracle 9i

3.2 HARDWARE REQUIREMENTS

Processor : Pentium III
RAM : 256MB
Hard Disk : 40GB

7
 CHAPTER - 4
FEASIBILITY REPORT

Preliminary investigation examine project feasibility, the likelihood the

system will be useful to the organization. The main objective of the feasibility
study is to test the Technical, Operational and Economical feasibility for adding
new modules and debugging old running system. The system is feasible if they
are unlimited resources and infinite time. There are aspects in the feasibility study
portion of the preliminary investigation:
1 Technical Feasibility
2 Operation Feasibility
3 Economical Feasibility

4.1 TECHNICAL FEASIBILITY

The technical issue usually raised during the feasibility stage of the
investigation includes the following:
1 Does the necessary technology exist to do what is suggested?
2 Do the proposed equipments have the technical capacity to hold the data
required to use the new system?
3 Will the proposed system provide adequate response to inquiries, regardless
of the number or location of users?
4 Can the system be upgraded if developed?
5 Are there technical guarantees of accuracy, reliability, ease of access and data
security?
Earlier no system existed to cater to the needs of ‘Secure Infrastructure
Implementation System’. The current system developed is technically feasible. It
is a web based user interface for audit workflow at NIC-CSD.
Thus it provides an easy access to the users. The database’s purpose is to

8
create, establish and maintain a workflow among various entities in order to
facilitate all concerned users in their various capacities or roles. Permission to the
users would be granted based on the roles specified. Therefore, it provides the
technical guarantee of accuracy, reliability and security. The software and hard
requirements for the development of this project are not many and are already
available in-house at NIC or are available as free as open source. The work for
the project is done with the current equipment and existing software technology.
Necessary bandwidth exists for providing a fast feedback to the users irrespective
of the number of users using the system.

4.1.1 About Java:

The term Java actual refers to more than just a particular language like
Core Pascal. Java encompasses several parts, including:

A high level language – the Java language is a high level one that at a glance
looks very similar to C and C++ but offers many unique features of its own.

Java byte code - a compiler, such as Sun's javac, transforms the Java language
source code to byte code that runs in the JVM.

Java Virtual Machine (JVM) – a program, such as Sun's java, that runs on a
given platform and takes the byte code programs as input and interprets them just
as if it were a physical processor executing machine code.

9
 Fig 4.1: Architecture of Java Virtual Machine

4.1.1.1 Features of Java:

 Platform Independence
o The Write-Once-Run-Anywhere ideal has not been achieved (tuning for
different platforms usually required), but closer than with other languages.
 Object Oriented
o Object oriented throughout - no coding outside of class definitions,
including main ().
o An extensive class library available in the core language packages.
 Compiler/Interpreter Combo
o Code is compiled to byte codes that are interpreted by Java virtual
machines (JVM).
o This provides portability to any machine for which a virtual machine has
been written.
o The two steps of compilation and interpretation allow for extensive code
checking and improved security.
 Robust
o Exception handling built-in, strong type checking (that is, all data must be
declared an explicit type), local variables must be initialized.
 Several dangerous features of C & C++ eliminated
o No memory pointers
o No preprocessor
o Array index limit checking
 Automatic Memory Management
o Automatic garbage collection - memory management handled by JVM
 Security
o No memory pointers
o A program runs inside the virtual machines and box.
o Array index limit checking
o Code pathologies reduced by

10
  byte code verifier - checks classes after loading
 Class loader - confines objects to unique namespaces. Prevents
loading a hacked "java.lang.SecurityManager" class, for example.
 Security manager - determines what resources a class can access
such as reading and writing to the local disk.

 Dynamic Binding
The linking of data and methods to where they are located is done at run-time.

o New classes can be loaded while a program is running. Linking is done

on the fly.
o Even if libraries are recompiled, there is no need to recompile code that
uses classes in those libraries.
o This differs from C++, which uses static binding. This can result in
fragile classes for cases where linked code is changed and memory
pointers then point to the wrong addresses

 Good Performance

o Interpretation of byte codes slowed performance in early versions, but

advanced virtual machines with adaptive and just-in-time compilation and
other techniques now typically provide performance up to 50% to 100%
the speed of C++ programs.

 Threading

o Lightweight processes, called threads, can easily be spun off to perform

multiprocessing.
o Can take advantage of multiprocessors where available
o Great for multimedia displays.

4.1.1.2 Java server pages:

Introduction to JSP:
JSP (Java Server Pages) technology provides a simplified, fast way to create

11
dynamic web content. JSP technology enables rapid development of web-based
applications that are server-independent and platform-independent.
JSP simply puts Java inside HTML pages. JSP is being turned into a Java file,
compiled and loaded. This compilation only happens once, so after the first load,
the file doesn't take long to load anymore. Every time you change the JSP file, it
will be re-compiled again.
Every JSP page will have a corresponding servlet which is generated by ‘JSP
Engine’ (which is a part of web container and itself is a servlet) Corresponding
servlet for JSP is generated only once when JSP is requested for the first time.

Request IS
No
CLIENT JSP VAL
ID

Text COMPILE
Yes
Response
SERVLET

Class

Fig 4.2: Block Diagram for JSP

12
The following are the jsp tags that are used for the implementation of the current
project.
TYPE OF SYNTAX DESCRIPTION
TAG
Script let tags <% code %> These are inserted into the
servlets service () method
Expression <%= and %> encloses java expressions,
tags which are evaluated at run time
Declaration <%! Java code %> for processing the request
tags outside of the service() method
Comments <%--comment-- %> A jsp comment, ignored by jsp
to script let translator
<!-- Comment --> A HTML comment.

Table 4.1: The used JSP tags

4.1.1.3 Introduction to JDBC:

JDBC (Java Database Connectivity) is an API developed by Sun
Microsystems that provides a standard way to access data using the Java
programming language. Using JDBC, an application can access a variety of
databases and run on any platform with a Java Virtual Machine.
It isn't necessary to write separate applications to access different
database systems (Oracle and Sybase, for example). Using JDBC allows you to
write one application that can send SQL statements to different database systems.
SQL is the standard language for accessing relational databases.
The JDBC API defines a set of Java interfaces that encapsulate major database
functionality, such as running queries, processing results, and determining
configuration information. Because JDBC applications are written in Java,
applications work on any platform.
The JDBC API makes it possible to do three things:
• Establish a connection with a database or access any tabular data source
• Send SQL statements

13
• Process the results
Jdbc Drivers:
Today, there are four types of JDBC drivers in use:
• Type 1: JDBC-ODBC bridge
• Type 2: partial Java driver
• Type 3: pure Java driver for database middleware
• Type 4: pure Java driver for direct-to-database
In this project we are using Type4 driver which provides best database
connectivity for internet based application.
Native-protocol/all-java driver:
The native-protocol/all-Java driver (JDBC driver type 4) converts JDBC calls
into the vendor-specific database management system (DBMS) protocol so that
client applications can communicate directly with the database server. Level 4
drivers are completely implemented in Java to achieve platform independence
and eliminate deployment administration issues.

Client
Machine
Net- Server
protocol/ Machine
Data
all-Java
driver Base
Server

Fig 4.3: Native-protocol/all-Java driver

Web Application Archives:
Web clients are packaged in web application archives. In addition to Web
components, a Web application archive usually contains other files, including the
following:
• Server-side utility classes (database beans and so on).
• Of the these classes conform to the JavaBeans component architecture
• Static Web content (HTML, image, and sound files, and so on).
• Client-side classes (applets and utility classes).
The top-level directory of a WAR is the document root of the application. The

14
document root is JSP pages, client-side classes and archives, and static Web
resources are stored.
The document root contains a subdirectory called WEB-INF, which contains the
following files and directories.
• web.xml: The Web application deployment descriptor
• Tag library descriptor files.
• Classes: A directory that contains server-side classes: servlets, utility Classes
and JavaBeans components.
• Lib: A directory that contains JAR archives of libraries (tag libraries and any
utility libraries called by server-side classes).
War file is created like this way
Jar cvf archiveName.war.

4.1.2 About Oracle:

Oracle is a relational database management system, which organizes data
in the form of tables. Oracle is one of many database servers based on RDBMS
model, which manages a seer of data that attends three specific things-data
structures, data integrity and data manipulation.
With oracle cooperative server technology we can realize the benefits of
open, relational systems for all the applications. Oracle makes efficient use of all
systems resources, on all hardware architecture; to deliver unmatched
performance, price performance and scalability.

4.1.2.1 Distinct features of oracle:

Oracle is Portable:
The Oracle RDBMS is available on wide range of platforms ranging from PCs to
super computers and as a multi user loadable module for Novel NetWare, if you
develop application on system you can run the same application on other systems
without any modifications.
Oracle is Compatible:
Oracle commands can be used for communicating with IBM DB2 mainframe
RDBMS that is different from Oracle that is Oracle compatible with DB2. Oracle

15
RDBMS is a high performance fault tolerant DBMS, which is specially designed
for online transaction processing and for handling large database applications.
Multithreaded Server Architecture:
Oracle adaptable multithreaded server architecture delivers scalable high
performance for very large number of users on all hardware architecture
including symmetric multiprocessors (sumps) and loosely coupled
multiprocessors. Performance is achieved by eliminating CPU, I/O, memory and
operating system bottlenecks and by optimizing the Oracle DBMS server code to
eliminate all internal bottlenecks.

4.1.2.2 Features of oracle:

Most popular RDBMS in the market because of its ease of use

• Client/server architecture.
• Data independence.
• Ensuring data integrity and data security.
• Managing data concurrency.
• Parallel processing support for speed up data entry and online transaction
processing used for applications.
• DB procedures, functions and packages.

Database Design:

Database design is an important phase in designing a system. During this phase

care should be taken to avoid redundancy of information storing into a database,
since it leads to wastage of memory space. For this purpose a normalization
technique has been applied here exhaustively to design the databases.

Normalization:
Normalization is a process of simplifying the relationship between data elements
in a record. Through normalization a collection of data in a record structure is
replaced by successive record structures that are simpler and more predictable
and therefore more manageable.

16
 It is a process of converting a relation to a standard form. The process is
used to handle the problems that can arise due to data redundancy i.e. repetition
of data in the database, maintain data integrity as well as handling problems that
can arise due to insertion, updating, deletion anomalies.
Decomposing is the process of splitting relations into multiple relations to
eliminate anomalies and maintain anomalies and maintain data integrity. To do
this we use normal forms or rules for structuring relation.
Insertion anomaly - Inability to add data to the database due to absence of other
data.
Deletion anomaly - Unintended loss of data due to deletion of other data.
Update anomaly - Data inconsistency resulting from data redundancy and partial
update
Normal Forms:
These are the rules for structuring relations that eliminate anomalies.
First Normal Form
A repeating group, the recurrence of a data item or group of data items with in a
record is actually another relation.
A relation is said to be in first normal form if the values in the relation are
atomic for every attribute in the relation. By this we mean simply that no
attribute value can be a set of values or, as it is sometimes expressed, a repeating
group.

Second Normal Form

Second normal form is achieved when a record is in first normal form and each
item in the record is fully dependant on the primary key distinguishes the records.
A relation is said to be in second Normal form is it is in first normal form
and it should satisfy any one of the following rules.
1) Primary key is a not a composite primary key
2) No non key attributes are present
3) Every non key attribute is fully functionally dependent on full set of
primary key.

Third Normal Form

17
Third normal form is achieved when transitive dependencies are removed from a
record design.
A relation is said to be in third normal form if their exits no transitive
dependencies.
Transitive Dependency: If two non key attributes depend on each other as well
as on the primary key then they are said to be transitively dependent.

The above normalization principles were applied to decompose the data in

multiple tables thereby making the data to be maintained in a consistent state.
List of SQL statements that can be issued against an Oracle database schema are:
• ALTER-Change an existing table, view or index definition(DDL)
• COMMIT-Make all recent changes permanent(DML-transitional)
• CREATE-Create new database objects such as tables or views
• DELETE-Delete a rows from a database table(DML)
• DROP-Drop a database object such as tables, view or index(DDL)
• INSERT-Insert new data into a database table(DML)
• SELECT-Retrieve data from a database table(DML)
• UPDATE-Change the values of some data items in the database table (DML)

4.2 OPERATIONAL FEASIBILITY

Proposed projects are beneficial only if they can be turned out into
information system. That will meet the organization’s operating requirements.
Operational feasibility aspects of the project are to be taken as an important part
of the project implementation. Some of the important issues raised are to test the
operational feasibility of a project includes the following: -
1 Is there sufficient support for the management from the users?
2 Will the system be used and work properly if it is being developed and
implemented?
3 Will there be any resistance from the user that will undermine the possible
application benefits?
This system is targeted to be in accordance with the above-mentioned
issues. Beforehand, the management issues and user requirements have been

18
taken into consideration. So there is no question of resistance from the users that
can undermine the possible application benefits.
The well-planned design would ensure the optimal utilization of the computer
resources and would help in the improvement of performance status.

4.3 ECONOMIC FEASIBILITY

A system can be developed technically and that will be used if installed
must still be a good investment for the organization. In the economical feasibility,
the development cost in creating the system is evaluated against the ultimate
benefit derived from the new systems. Financial benefits must equal or exceed
the costs.
The system is economically feasible. It does not require any addition
hardware or software. Since the interface for this system is developed using the
existing resources and technologies available at NIC, There is nominal
expenditure and economical feasibility for certain.

CHAPTER-5
DESIGN ANALYSIS

5.1 FUNCTIONAL REQUIREMENTS

5.1.1 Input design:

19
Input design is a part of overall system design. The main objective during the
input design is as given below:
 To produce a cost-effective method of input.
 To achieve the highest possible level of accuracy.
 To ensure that the input is acceptable and understood by the user.
Input stages:
The main input stages can be listed as below:
 Data recording
 Data transcription
 Data conversion
 Data verification
 Data control
 Data transmission
 Data validation
 Data correction
Input types:
It is necessary to determine the various types of inputs. Inputs can be categorized
as follows:
 External inputs, which are prime inputs for the system.
 Internal inputs, which are user communications with the system.
 Operational, which are computer department’s communications to the
system?
 Interactive, which are inputs entered during a dialogue.
Input media:
At this stage choice has to be made about the input media. To conclude
about the input media consideration has to be given to;
 Type of input
 Flexibility of format
 Speed
 Accuracy
 Verification methods
 Rejection rates
 Ease of correction

20
 Storage and handling requirements
 Security
 Easy to use
 Portability
Keeping in view the above description of the input types and input media,
it can be said that most of the inputs are of the form of internal and interactive.
As Input data is to be the directly keyed in by the user, the keyboard can be
considered to be the most suitable input device.

5.1.2 Output design:

Outputs from computer systems are required primarily to communicate the
results of processing to users. They are also used to provide a permanent copy of
the results for later consultation. The various types of outputs in general are:
1 External Outputs, whose destination is outside the organization
2 Internal Outputs, whose destination is within organization and they are the
user’s main interface with the computer.
3 Operational outputs whose use is purely within the computer department.
4 Interface outputs, which involve the user in communicating directly.
Output Definition:
The outputs should be defined in terms of the following points:
Type of the output
 Content of the output
 Format of the output
 Location of the output
 Frequency of the output
 Volume of the output
 Sequence of the output
It is not always desirable to print or display data as it is held on a
computer. It should be decided as which form of the output is the most suitable.
For Example
 Will decimal points need to be inserted
 Should leading zeros be suppressed.
Output Media:

21
 In the next stage it is to be decided that which medium is the most
appropriate for the output. The main considerations when deciding about the
output media are:
1 The suitability for the device to the particular application.
2 The need for a hard copy.
3 The response time required.
4 The location of the users
5 The software and hardware available.
Keeping in view the above description the project is to have outputs mainly
coming under the category of internal outputs. The main outputs desired
according to the requirement specification are:
The outputs were needed to be generated as a hot copy and as well as queries to
be viewed on the screen. Keeping in view these outputs, the format for the output
is taken from the outputs, which are currently being obtained after manual
processing. The standard printer is to be used as output media for hard copies.

5.1.3 Error Avoidance and Detection:

At this stage care is to be taken to ensure that input data remains accurate form
the stage at which it is recorded up to the stage in which the data is accepted by
the system. This can be achieved only by means of careful control each time the
data is handled.
Error detection:
Even though every effort is make to avoid the occurrence of errors, still a
small proportion of errors are always likely to occur, these types of errors can be
discovered by using validations to check the input data.

5.1.4 Data validation:

Procedures are designed to detect errors in data at a lower level of detail.
Data validations have been included in the system in almost every area where
there is a possibility for the user to commit errors. The system will not accept
invalid data. Whenever an invalid data is keyed in, the system immediately
prompts the user and the user has to again key in the data and the system will
accept the data only if the data is correct. Validations have been included where

22
necessary.
The system is designed to be a user friendly one. In other words the
system has been designed to communicate effectively with the user. The system
has been designed with popup menus.

5.2 PERFORMANCE REQUIREMENTS

Performance is measured in terms of the output provided by the
application.
Requirement specification plays an important part in the analysis of a
system. Only when the requirement specifications are properly given, it is
possible to design a system, which will fit into required environment. It rests
largely in the part of the users of the existing system to give the requirement
specifications because they are the people who finally use the system. This is
because the requirements have to be known during the initial stages so that the
system can be designed according to those requirements. It is very difficult to
change the system once it has been designed and on the other hand designing a
system, which does not cater to the requirements of the user, is of no use.
The requirement specification for any system can be broadly stated as given
below:
 The system should be able to interface with the existing system
 The system should be accurate
 The system should be better than the existing system
The existing system is completely dependent on the user to perform all the duties.

5.3 NUMBER OF MODULES

 Administrator process
 Project manager view
 Report generation
 Display Status
Initially to sign in the user whether it is administrator or project
manager he /she are to use his username and password.

23
 CHAPTER-6
SYSTEM DESIGN

6.1 INTRODUCTION
Software design sits at the technical kernel of the software engineering
process and is applied regardless of the development paradigm and area of
application. Design is the first step in the development phase for any engineered
product or system. The designer’s goal is to produce a model or representation of
an entity that will later be built. Beginning, once system requirement have been

24
specified and analyzed, system design is the first of the three technical activities
-design, code and test that is required to build and verify software.
The importance can be stated with a single word “Quality”. Design is the
place where quality is fostered in software development. Design provides us with
representations of software that can assess for quality. Design is the only way that
we can accurately translate a customer’s view into a finished software product or
system. Software design serves as a foundation for all the software engineering
steps that follow. Without a strong design we risk building an unstable system –
one that will be difficult to test, one whose quality cannot be assessed until the
last stage.
During design, progressive refinement of data structure, program
structure, and procedural details are developed reviewed and documented.
System design can be viewed from either technical or project management
perspective. From the technical point of view, design is comprised of four
activities – architectural design, data structure design, interface design and
procedural design.

6.2 SYSTEM WORKFLOW - CONTEXT DIAGRAM

Login
Login P
A Change Password R
D Add Manager O
Submits Details
M View Allocated Project J
I Allocate Project Software E
N C
I Select Technology T
Project
S View Project Status And Team Members
T M
R View All Projects
Management A
A N
T Tool A
O G
25 E
R
R
 Assign task to Team
Members
Log Out
View Project Status

U
p
V d
a L
i
t o
e
L e g
w
o
g S O
T
i t u
a
n a t
s
k t
u
s

TEAM MEMBER

Fig 6.1: System Work Flow – Context Diagram

6.3 UML DIAGRAMS

6.3.1 Use-Case diagrams:

26
 Login

<<uses>>
Adds manager
<<uses>>
<<uses>>
Allocates project

<<uses>> <<include>>
View project status
<<uses>>
Administrator <<uses>>
View all projects

<<include>>
login

<<uses>>
Changes password
<<uses>> Id number

<<uses>> View project details

Project
Manager <<uses>>
<<include>>
<<uses>> Select technology and team members

<<uses>>
Assigns task

<<uses>> Views project Status

Team Member <<uses>>

Login

Views task
<<uses>>
<<uses>>

Updates Projects Status

Logout

Fig 6.2: Use-Case Diagram

6.3.2 Class diagram:

customer

27
 Administrator
Project Manager
+ Project Manager Id
+ New Project
+Project Details + Project Id
+ Team Id

+Views Project ()
+Build Team
+ Adds new manager ()
+Adds new project ()

Team Member

+Task Id
+Project Status

+Views Task ()
+Update Project Status

Fig 6.3: Class Diagram

6.3.3 Activity diagram:

28
 Start

Login

Verif NO
y

YES

Administrator
Project Manager Project Manager

Adds New Manager

Change Password Change Password

View Task Adds New Project

Views Project

Select Technology and View Project Details

Team Members

Update Project Status

Views Project Status
Assign Task

View Project Status

Stop

Fig 6.4: Activity Diagram

6.4 E – R DIAGRAMS

29
  The relation upon the system is structure through a conceptual ER-Diagram,
which not only specifics the existential entities but also the standard relations
through which the system exists and the cardinalities that are necessary for
the system state to continue.

 The entity Relationship Diagram (ERD) depicts the relationship between the
data objects. The ERD is the notation that is used to conduct the date
modeling activity the attributes of each data object noted is the ERD can be
described resign a data object descriptions.

 The set of primary components that are identified by the ERD are

 Data object  Relationships

 attributes  various types of indicators.

The primary purpose of the ERD is to represent data objects and their
relationships.

Views
Assigns
project Project
Manager Details
Id
Manager Adds
name project

Administrator Manager Project

Details

Fig 6.5: Administrator E-R Diagram

30
 Build team
View
Project
Select Status
Change
technology
Password

Project Manager Project

Manager Details

Fig 6.6: Project Manager E-R Diagram

Change
Password Views Task
Update
Project Status

Team Member Project

Member Details

Fig 6.7: Team Member E-R Diagram

6.5 DATA FLOW DIAGRAMS

1) A Data Flow has only one direction of flow between symbols. It may flow in

31
 both directions between a process and a data store to show a read before an
update. The later is usually indicated however by two separate arrows since
these happen at different type.
2) A join in DFD means that exactly the same data comes from any of two or
more different processes data store or sink to a common location.
3) A data flow cannot go directly back to the same process it leads. There must
be at least one other process that handles the data flow produce some other
data flow returns the original data into the beginning process.
4) A Data flow to a data store means update (delete or change).
5) A data Flow from a data store means retrieve or use.
A data flow has a noun phrase label more than one data flow noun phrase can
appear on a single arrow as long as all of the flows on the same arrow move
together as one package.
Data Store
1) Data cannot move directly from one data store to another data store, a process
must move data.
2) Data cannot move directly from an outside source to a data store, a process,
which receives, must move data from the source and place the data into data
store
3) A data store has a noun phrase label.
Source or Sink
The origin and/or destination of data. Data cannot move directly from a source to
sink it must be moved by a process. A source and /or sink has a noun phrase land

32
 Login Project Manager
Login Details Data Base
Add
Apartment
Administrator
Manager
Add
New Project

Project
Data Base

Project

Fig 6.8: Administrator Data Flow Diagram

Manager Projects
Details Data Base
Login
Views
Manager
Project
Project
Task Data Base

Adds Team
Team Data Base
Members

Status
Task

Views Task

Fig 6.9: Project Manager Data Flow Diagram

33
 Buyer Sitereg
Login Details Data Base
Views
Apartment

Apartment

Views
Building

Sitereg
Data Base

Building

Fig 6.10: Team Member Data Flow Diagram

6.6 DATA DICTIONARY

After carefully understanding the requirements of the client the entire data
storage requirements are divided into tables. The below tables are normalized to
avoid any anomalies during the course of data entry.

Column Name Constraint Data Type

PMID NOT NULL VARCHAR2(10)
PMNAME VARCHAR2(20)
PASSWORD VARCHAR2(15)
Table 6.1: pmanager

Column Name Constraint Data Type

PID NOT NULL VARCHAR2(10)

34
PNAME VARCHAR2(25)
PMID VARCHAR2(10)
PDURATION NUMBER(3)
PCOST NUMBER(12)
DIT DATE
STAGE VARCHAR2(15)
DOC DATE
Table 6.2: project

Column Name Constraint Data Type

RID NOT NULL VARCHAR2(10)
RNAME VARCHAR2(20)
TECHNO VARCHAR2(10)
REXP NUMBER(3)
STATUS VARCHAR2(15)
PASSWORD VARCHAR2(10)
Table 6.3: source

Column Name Constraint Data Type

TAID VARCHAR2(10)
RID VARCHAR2(10)
PMID VARCHAR2(10)
DOA DATE
DESCRIP VARCHAR2(400)
PRIORITY VARCHAR2(15)
EHOC NUMBER(3)
STATUS VARCHAR2(15)
Table 6.4: Task

Column Name Constraint Data Type

TID NOT NULL VARCHAR2(10)
PNAME VARCHAR2(20)
TECHNO VARCHAR2(10)
TSIZE NUMBER(3)
PMID VARCHAR2(10)
Table 6.5: tt (select group)

Column Name Constraint Data Type

RID VARCHAR2(10)
TID VARCHAR2(10)
RNAME VARCHAR2(20)
Table 6.6: ttt (update task status)

35
 CHAPTER-7
IMPLEMENTATION

7.1 NUMBER OF MODULES

 Administrator process
 Project manager view
 Report generation
 Display Status
Initially to sign in the user whether it is administrator or project
manager he /she are to use his username and password.

7.1.1 Module description:

36
Administration process:
In this process Administrator will add a new project to the existing list of
projects .Here he /she can also open an existing project for viewing the details of
projects along with the teams working for that project including its present status.
The administrator can add new manager to the list of managers.
Project manager view:
In this the project manager can assign a project to a group with some team
id where this team of crew will be set only for that project. Project manger can
also view the present status of all the projects under him.
Display Status:
This process is for checking the project status at the time of project
construction. This shows the days left for completion if not completed, else gives
information in response to the date of checking status.
This product will assist the organization in maintaining records of every
project it undertakes. All the information relevant to the projects like size, time,
effort, and departments involved, etc is maintained by this tool.

7.2 USER INTERFACE DESIGN

It is essential to consult the system users and discuss their needs while
designing the user interface:

User interface systems can be broadly classified as:

1. User initiated interface the user is in charge, controlling the progress of the
user/computer dialogue. In the computer-initiated interface, the computer
selects the next stage in the interaction.
2. Computer initiated interfaces
In the computer initiated interfaces the computer guides the progress of the
user/computer dialogue. Information is displayed and the user response of the
computer takes action or displays further information.
User-initiated interfaces:
User initiated interfaces fall into tow approximate classes:
1. Command driven interfaces: In this type of interface the user inputs
commands or queries which are interpreted by the computer.

37
2. Forms oriented interface: The user calls up an image of the form to his/her
screen and fills in the form. The forms oriented interface is chosen because it
is the best choice.
Computer-initiated interfaces:
The following computer – initiated interfaces were used:
1. The menu system for the user is presented with a list of alternatives and the
user chooses one; of alternatives.
2. Questions – answer type dialog system where the computer asks question and
takes action based on the basis of the users reply.
Right from the start the system is going to be menu driven, the opening
menu displays the available options. Choosing one option gives another popup
menu with more options. In this way every option leads the users to data entry
form where the user can key in the data.
Error message design:
The design of error messages is an important part of the user interface
design. As user is bound to commit some errors or other while designing a
system the system should be designed to be helpful by providing the user with
information regarding the error he/she has committed.
This application must be able to produce output at different modules for
different inputs.

CHAPTER-8
SECURITY SYSTEM

8.1 INTRODUCTION
The protection of computer based resources that includes hardware,
software, data, procedures and people against unauthorized use or natural
Disaster is known as System Security.
System Security can be divided into four related issues:
1 Security
2 Integrity
3 Privacy

38
 4 Confidentiality
System Security refers to the technical innovations and procedures applied to the
hardware and operation systems to protect against deliberate or accidental
damage from a defined threat.
Data Security is the protection of data from loss, disclosure, modification and
destruction.
System Integrity refers to the power functioning of hardware and programs,
appropriate physical security and safety against external threats such as
eavesdropping and wiretapping.
Privacy defines the rights of the user or organizations to determine what
information they are willing to share with or accept from others and how the
organization can be protected against unwelcome, unfair or excessive
dissemination of information about it.
Confidentiality is a special status given to sensitive information in a database to
minimize the possible invasion of privacy. It is an attribute of information that
characterizes its need for protection.

8.2 SECURITY IN SOFTWARE

System security refers to various validations on data in form of checks and
controls to avoid the system from failing. It is always important to ensure
that only valid data is entered and only valid operations are performed on
the system. The system employees two types of checks and controls:
Client Side Validation
Various client side validations are used to ensure on the client side that only valid
data is entered. Client side validation saves server time and load to handle invalid
data. Some checks imposed are:
1 VBScript in used to ensure those required fields are filled with suitable data
only. Maximum lengths of the fields of the forms are appropriately defined.
2 Forms cannot be submitted without filling up the mandatory data so that
manual mistakes of submitting empty fields that are mandatory can be sorted
out at the client side to save the server time and load.
3 Tab-indexes are set according to the need and taking into account the ease of

39
 user while working with the system.
Server Side Validation
Some checks cannot be applied at client side. Server side checks are necessary to
save the system from failing and intimating the user that some invalid operation
has been performed or the performed operation is restricted. Some of the server
side checks imposed is:
1 Server side constraint has been imposed to check for the validity of primary
key and foreign key. A primary key value cannot be duplicated. Any attempt
to duplicate the primary value results into a message intimating the user about
those values through the forms using foreign key can be updated only of the
existing foreign key values.
2 User is intimating through appropriate messages about the successful
operations or exceptions occurring at server side.
3 Various Access Control Mechanisms have been built so that one user may not
agitate upon another. Access permissions to various types of users are
controlled according to the organizational structure. Only permitted users can
log on to the system and can have access according to their category. User-
name, passwords and permissions are controlled o the server side.
4 Using server side validation, constraints on several restricted operations are
imposed.

CHAPTER-9
SYSTEM TESTING

9.1 INTRODUCTION
Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding. In fact, testing
is the one step in the software engineering process that could be viewed as
destructive rather than constructive.
A strategy for software testing integrates software test case design
methods into a well-planned series of steps that result in the successful
construction of software. Testing is the set of activities that can be planned in
advance and conducted systematically. The underlying motivation of program

40
testing is to affirm software quality with methods that can economically and
effectively apply to both strategic to both large and small-scale systems.

9.2 STRATEGIC APPROACH TO SOFTWARE TESTING

The software engineering process can be viewed as a spiral. Initially
system engineering defines the role of software and leads to software requirement
analysis where the information domain, functions, behavior, performance,
constraints and validation criteria for software are established. Moving inward
along the spiral, we come to design and finally to coding. To develop computer
software we spiral in along streamlines that decrease the level of abstraction on
each turn.
A strategy for software testing may also be viewed in the context of the
spiral. Unit testing begins at the vertex of the spiral and concentrates on each unit
of the software as implemented in source code. Testing progress by moving
outward along the spiral to integration testing, where the focus is on the design
and the construction of the software architecture. Talking another turn on
outward on the spiral we encounter validation testing where requirements
established as part of software requirements analysis are validated against the
software that has been constructed. Finally we arrive at system testing, where the
software and other elements are tested as a whole.

9.3 UNIT TESTING

Unit testing focuses verification effort on the smallest unit of software
design, the module. The unit testing we have is white box oriented and some
modules the steps are conducted in parallel.
1. White Box Testing
This type of testing ensures that
1 All independent paths have been exercised at least once
2 All logical decisions have been exercised on their true and false sides
3 All loops are executed at their boundaries and within their operational bounds
4 All internal data structures have been exercised to assure their validity.
To follow the concept of white box testing we have tested each form .we have

41
created independently to verify that Data flow is correct, All conditions are
exercised to check their validity, All loops are executed on their boundaries.
2. Basic Path Testing
Established technique of flow graph with Cyclamate complexity was used to
derive test cases for all the functions. The main steps in deriving test cases were:
Use the design of the code and draw correspondent flow graph.
Determine the Cyclamate complexity of resultant flow graph, using formula:
V (G) =E-N+2 or
V (G) =P+1 or
V (G) =Number of Regions
Where V (G) is Cyclamate complexity,
E is the number of edges,
N is the number of flow graph nodes,
P is the number of predicate nodes.
Determine the basis of set of linearly independent paths.
3. Conditional Testing
In this part of the testing each of the conditions were tested to both true and false
aspects. And all the resulting paths were tested. So that each path that may be
generate on particular condition is traced to uncover any possible errors.
4. Data Flow Testing
This type of testing selects the path of the program according to the location of
definition and use of variables. This kind of testing was used only when some
local variable were declared. The definition-use chain method was used in this
type of testing. These were particularly useful in nested statements.
5. Loop Testing
In this type of testing all the loops are tested to all the limits possible. The
following exercise was adopted for all loops:
1 All the loops were tested at their limits, just above them and just below them.
2 All the loops were skipped at least once.
3 For nested loops test the inner most loop first and then work outwards.
4 For concatenated loops the values of dependent loops were set with the help
of connected loop.
5 Unstructured loops were resolved into nested loops or concatenated loops and

42
 tested as above.

Each unit has been separately tested by the development team itself and all the
input have been validated.

CHAPTER-10
OUTPUT SCREENS

43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
 CHAPTER-11
CONCLUSION

Software project management tool is a fundamental part of the Software

Engineering lifecycle process. Effective use of a tool is will lead to a more
structured approach throughout the development lifecycle, resulting in a higher
quality product while also reducing development and support costs.

64
 CHAPTER-12
FUTURE ENHANCEMENT

Now by making use of software project management tool we are able to deal the
projects in small companies and institutions, but in future we can adopt this tool
for MNC’s with further resources according to future requirements.

65
 CHAPTER-13

BIBLIOGRAPHY

• Java Server Programming

By Subramanyam Allamaraju, Cedric Buest.
• ORACLE
By Evan Byross
• HTML Black Book
By Steven Holzner.
• HTML Complete Reference
• Software Engineering
By Pressman

66