Chapter-2

System Requirement Analysis and Project Management

IT- 17 System Analysis

2.1 Tools and Technology

PHP is a programming language that allows web developers to create dynamic web
applications with its content that can interact with its databases and also a general-purpose
server-side scripting language that runs on the webserver allows to accessing lots of
developers. It supports nearly all operating systems like Windows, Linux, UNIX, etc. PHP
development is simple and easy to use this language is one of the important reasons behind
the platform
PHP web development is one among several web development methods that will never fade
away. With every passing year, it has become the most trusted platform for developers and
companies for website development. The reason for such tremendous popularity of PHP is
the outcome of the continuous research and development. There is no doubt that in coming
times, PHP will reach to the newer heights as the demands for the PHP powered websites are
being expected to explode.
Presently, PHP 7 is being used for empowering websites across the world. Every version
release brings some improvement along with the opportunity to make the language even more
improved that has some drawbacks. With the passage of time, PHP has been enhanced to
support multiple platforms so that it could be run smoothly on any platform with assured
reliability. Thus, no wonder that the popular websites.

2.2 Hardware and Software Requirement

Hardware Configuration of Server Side
Processor : Intel core i3 Processor
RAM : 4 GB
Hard Disk Drive : 500 GB
Key Board : Standard 101/102 or Digi Sync Family
Monitor : Display Panel (1366 X 768)
Mouse : Serial Mouse
Internet Connection : Yes
Software Requirement for Server Side
Technology : PHP
Server : Apache
Basic Features : Html, CSS
Other Tools : PhpMyAdmin
Database : MySQL 5.1
Development IDE : Sublime,Xammp

Minimum System Configuration of Client Side

Processor : INTEL Pentium 4 or Higher
RAM : 512MB
Hard Disk Drive : 40GB

IT DEPT, GPG Page | 6

IT- 17 System Analysis

Monitor : Display Panel (1024 X 764)

Mouse : Serial Mouse
Internet Connection : Yes
Browser : Google Chrome,
Mozilla Firefox 8.0 or higher
Internet Explorer 6.0 or higher

2.3 Software Process Model

The Requirements provided by the users are converted into Users Requirement Specification
as described above. The URS documents are then revised, validated, authorized and approved
by the users. The development commences after the approval phase i.e. after the signing off
of the URS documents. Thus, the URS is concerned to be the most important document from
user and developer prospective. The Developer will try to adhere to the requirements
specified in the URS documents in order to develop the required application.
The model used in this project is Incremental & iterative development cycle. Incremental
development is a staging and scheduling strategy in which various parts of the system are
developed at different times or rates, and integrated as they are completed.
Iterative development is a rework scheduling strategy in which time is set aside to revise and
improve parts of the system. It is important to notice that neither strategy presupposes,
requires or implies the other.
The Incremental Software Process Model
The Incremental Model combines elements of the linear sequential model with the iterative
philosophy of prototyping. The incremental model applies linear sequences in a staged
fashion as calendar time progresses.
Each linear sequence produces a deliverable “increment” of the software. For example, word
processing software developed using the incremental paradigm might deliver basic file
management, editing and document production functions in the first increment; more
sophisticated editing and document production capabilities in the second increment; spelling
and grammar checking in the third increment; and advanced page layout capability in the
fourth increment.
It should be noted that the process flow for any increment can incorporate the prototyping
paradigm.
When an incremental model is used, the first increment is often a core product. That is, basic
requirements are addressed, but many supplementary features remain undelivered. The core
product is used by the customer. As a result of use and/or evaluation, a plan is developed for
the next increment. The plan addresses the modification of the core product to better meet the
needs of the customer and the delivery of additional features and functionality.
This process is repeated following the delivery of each increment, until the complete product
is produced. The incremental process model, like prototyping and other evolution
approaches, is iterative in nature.

IT DEPT, GPG Page | 7

IT- 17 System Analysis

But unlike prototyping, the incremental model focuses on the delivery of an operational
product with each increment. Early increments are stripped down versions of the final
product, but they do provide capability that serves the user and also provide a platform for
evaluation by the user.

(Fig 2.3.1 incremental model)

This model contains six task regions:
 Initial Planning/ Customer communication: Tasks required establishing effective
communication between developer and customer. During this phase the objectives,
alternatives and constraints are elaborated.
 Planning: Tasks required defining resources, timelines and other project related
information.
 Analysis and Design: A detailed analysis of the requirements gathered is assessed for
both technical and management risks. A design of the product is carefully created which
is supposed to fulfill the client specifications.
 Implementation and Testing: The actual coding starts from here according to the
prototypes proposed during the design phase. Each application module is thoroughly
tested for consistency and requirement fulfillment. Tasks required building one or more
representations of the application.
 Deployment and release: Tasks required constructing, testing, installing and providing
user support (e.g. documentation and training). Customer evaluation: Tasks required
obtaining customer feedback based on evaluation of the software representations created
during the engineering stage and implemented during the installation stage (Pressman
1997).

Advantages of Incremental Model

 Generates working software quickly and early during the software life cycle.

IT DEPT, GPG Page | 8

IT- 17 System Analysis

 More flexible – less costly to change scope and requirements.

 Easier to test and debug during a smaller iteration.
 Easier to manage risk because risky pieces are identified and handled during its iteration.
 Each iteration is an easily managed milestone.

Disadvantages of Incremental Model

 Each phase of an iteration is rigid and do not overlap each other.

 Problems may arise pertaining to system architecture because not all requirements are
gathered up front for the entire software life cycle.

2.4 Project planning and scheduling

2.4.1 Project development approach
The activities we followed for this project is listed below:
 Planning the work or objectives
 Analysis & Design of objectives
 Assessing and controlling risk
 Allocation of resources
 Organizing the work
 Database Designing
 Form Design

2.4.2 Project plan

LSS has a very long-standing relationship at client side. It has provided its expertise to
various Government agencies, working with numerous hardware and software technologies,
to improve its overall image and provide better services to its constituents. LSS will bring its
vast domain expertise in legacy and low firm project, knowledge of the best practices and
lessons learnt in various implementations at client side to this project. For this specific
requirement analysis, LSS serve with the help of designated personnel from CLIENT would
familiarize themselves with the overall structure of the office and it’s inter-linkages with
other departments/systems and branch. They will understand the broad working of the
Company and the other related departments, its functions, manpower employed, processes
etc.
LSS shall meet the representative personnel and document the detailed gaps between the
current system and the proposed solution based on the understanding of the activities and
processes, as they are currently being carried out in the office.
The gaps would be documented and analyzed, and if required and possible reengineering of
process in concurrence with CLIENT to leverage the benefits of the product would be
suggested.

Design Constraints:
IT DEPT, GPG Page | 9
IT- 17 System Analysis

Design specifications that are followed in the organization have to be followed which are as
follows:

 Programming Convention:
 Programming style should be modular in the sense that it is easy to identify the
functionality of the module and its relationship with other modules.
 Module should be predetermined and be clearly defined.
 Intercommunication within same module should be high but intercommunication
between different modules should be minimum, i.e. (Cohesion should be high but
coupling should be low.)
 Reusable routines should be used to maximize productivity.
 Code should not contain any hard-coded components.
 Program should be readable, well indented, and visible within the screen by writing
the command in a structured format and using word-wrap to next line for long
statements.
 Appropriate comments should be used to describe the purpose of the program,
statement, routines, and variables.
 User log should be maintained for concurrency control.
 The system should provide some sort of authentication for diff. categories of user.
 Look And Feel
 Look and feel of the system should be consistent throughout the system.
 Same color combination for each page as well as fonts and use of safe color for web-
based applications.
 Similar look and Standard navigation style.
 Consistent usage of caption for same purpose controls.
 Interface should be user friendly and self-explanatory.
 Appropriate use of tooltip for displaying relevant information to the user.
 Use of appropriate titles and metadata keywords/description for each page.
 Entire screen layout should be accommodated in one screen and if required should be
vertically scrolled.
 Input Output Conventions
 Take maximum input by selection and minimize text input that would help in
reducing user level data entry errors.
 System should take minimum input from user and reduce redundant data input. E.g. if
once birth date is entered system should not take age from user but it should be
calculated automatically.
 All report layouts should be formatted to accommodate printing in A4 size paper only.
 All report should have feature to view on screen and save in Excel format.

IT DEPT, GPG Page | 10

IT- 17 System Analysis

 All queries /reports should have facility to extract the data between specified filter.
E.g. Between range of dates, and complex search.
 Database Design
 Table should be normalized to have minimum redundancy and exhibit consistency.
 Relationships should be well defined, easy to identify and maintain.
 Appropriate nomenclature should be done such that it indicates what type of data it
contains.
 Fields should be of proper data types.
 Use proper data types as required. E.g. -Use date data type wherever date is required
instead of varchar.
 Proper backup strategy should be maintained, script files for the tables should be
generated.
 Primary keys and foreign key constraints should be appropriately defined.
 Indexing mechanisms should be used for faster retrieval of information.
 Use of Views should be done for security and precise output.
 Standards for Development Environment
 Centralized storage in server i.e. No client level replica
 Meaningful project name
 Meaningful main folder naming convention.
 Nature of object based separation.
 Duplicate object with different name should be avoided.
 No direct changes in database level object. Source file should be modified first.
 Final source should be migrated to central software library.
 Copy of technical document always with the source should be provided.
 Maintain a document to describe the change history date wise.
 No direct changes to the live server should be made; changes should be incorporated
first in the development and should be migrated to live only after testing and
finalizing.
 Database Connectivity
 A global file like spring config. file should be maintained for database connection
string for flexibility, updating and only reference to that file should be used while
programming.
 Quality and Testing
 Test plans and Test data should be well documented.
 Unit testing should be performed at programmer level.

IT DEPT, GPG Page | 11

IT- 17 System Analysis

 A senior programmer to check working of the system as a whole should do

integration testing.
 Functional testing and Boundary case testing should be done.
 Performance
 Minimum usage of graphics is required for fast access to pages.
 Application should be platform independent.
 Low response time and security measures for user information and other important
information.
 User information should be used to give user a personalized environment.
 System Security
 Security measures for user information and other important information.
 User should be authenticated using a common login procedure to use the system.
 A user log should be maintained in order to keep a check on proper usage of the
system.
 All the sensitive information stored in database such as password should be in
encrypted form.
2.4.3 Schedule Representation
Scheduling the project is an important activity. It involves deciding which tasks
would be taken up when .Project Manager of project has done these following tasks.

 Break down large tasks into small activities.

(Fig 2.4.3.1 Project Schedule)

IT DEPT, GPG Page | 12